okay, where to start.
I've a Nexus 7, and im running P.A 2.54, with twrp.
i got an article from one of my news apps about getting better volume for my nex 7 BeatsLouder, followed the link and downloaded, didn't do any information gathering and consequently i believe i've flashed the beatslouder for android 4.2 it was BeatsLouder v3b8 i believe.
Either way now, my tablet just hangs at the P.A splash screen/boot logo.
needless to say, with my lack of forward planning into researching what i was flashing i didnt make a back up either..
Are there any solutions that don't even a fresh wipe?
edit: so i had a back up in twrp, when i had the forethought to do a backup prior to installing something unknown, however i'm not certain if the back up is of data or system files or both, anyway to find out? the restoring of the back up seemed to happen almost instantaneously, making me think it didnt work?
oh, also i made a backup of everything (in its current broken state) in the hopes i might be able to recover my data?
would love some responses, anything to get the ball rolling
Try dirty flash your ROM then gapps in recovery again. No wipe needed.
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?
First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
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.
NOOB HERE!!!
My quick and hopefully simple question regards installing the CM updates that are available directly on my phone. I am running 10.2 with no issues. Nearly everyday I get the icon stating there is an up to CM10. I simply click on it and install. Again, so far so good but I would like to know if simply installing these updates this way is "endangering" my phone. Is there a better way I should be installing these? I am assuming not otherwise the updates would not be present and as simple to install. Thanks for your input!
kcoop99 said:
NOOB HERE!!!
My quick and hopefully simple question regards installing the CM updates that are available directly on my phone. I am running 10.2 with no issues. Nearly everyday I get the icon stating there is an up to CM10. I simply click on it and install. Again, so far so good but I would like to know if simply installing these updates this way is "endangering" my phone. Is there a better way I should be installing these? I am assuming not otherwise the updates would not be present and as simple to install. Thanks for your input!
Click to expand...
Click to collapse
It is perfectly safe to use the built in cmupdater every day. For piece of mind it may be a good idea to occasionally make a backup manually using your recovery of choice (either TWRP or CWM).
If you ever encounter a problem after upgrading to the latest nightly, and nightlies do sometimes break features, just boot into recovery and manually flash the previous day's file (located in the /cmupdater folder)...no need to wipe anything.
I've been dirty flashing cm nightlies since June. You're fine. A clean flash doesn't hurt once in awhile though!
Thanks! I appreciate it!
I dirty flashed for a year with no problem at all untill a few days ago. I went from the 8/16 to the 8/17 to the 8/14 and lost my imei and eri once the 8/14 booted. Ive been trying everything with no luck to get the eri back. make sure you do a full (not just imei) NV back up and do a normal rom/data backup like once ever week or two. Im regretting not doing a NV backup as the only tool to fix my problem has been removed from the site due to infringing the ToS.