Hi, I would like to start off by thanking task650 and all of the other dev's for making xda possible. It's great
So I rooted my Samsung Galaxy 10.1 (GT-P7510) and threw task 14 on it. I'm not sure what causes it but sometimes when I boot up my action bar will be gone and I can't get it back unless I reflash or restore.
The first couple times it happened was right after installing a b00sted theme. I tried everything I could think of -- I would restore a previous backup and itd be there but every time I flashed a theme itd be gone upon startup.
And since those themes rock so much I ended up wiping everything, and reinstalling the ROM from scratch again, this time the slim version. I also uninstalled the hide action bar app right after install to make sure it wasn't that. After I did that I installed a theme and voila! It stuck around.
So, today I had the cm9 4.04 ROM or whatever on just to mess around. I was done so I restored my task backup. It booted up but ended up freezing on the lock screen, the action bar was unharmed and in place. I did a hard reset and boom, it's gone again. I have no idea what's causing it but it seems like some data is getting corrupted somewhere.
Stop me if you've heard this before..
Thanks all
Edit: So, just now I rebooted into recovery to check the version (cwm-based 5.5.0.4)and all's I did was boot into recovery from the power menu. I think that's what it's called... It's where you hold power down for a second or two then you get the menu. Yeah, then I selected the reboot device option and upon start-up... No action bar!
Why not try another ROM? A factory reset or a clean flash of the same firmware, then reflash task would probably fix it. Seem's as though your Settings.apk is messed up.
Related
Apologies if this is the wrong forum.
The update notice came through on my phone yesterday afternoon. From reading on here I knew that a number of people were having problems with it. Like a meth addicted crackwhore I couldn't say no.
Before saying yes, I did make a backup.
Here's what I had on my phone beforehand:
Modified swype overlay
Modified battery icon
OCLF 2.1+
GPS fix update
I'd renamed the startup video so it wouldn't show
I'd replaced the startup sound with my own
I think that's all.
I did a nandroid backup before applying the update and even made a copy of the backup just in case.
I undid the lagfix but - perhaps stupidly - left all the other updates in place.
After applying the update my phone was stuck at the vibrant screen right after boot. No amount of waiting - 30 minutes the first time - did any good.
I've been through several rounds of flashing using the second round of steps in this thread but the best that happens is when the phone boots I see the stock home and the media,calendar,(+a few others I can't recall) FC continuously and the home shows a bunch of missing widget boxes.
If I do a nandroid restore I strangely end up with the hung vibrant screen again. It's like it's automatically applying the update or something other odd like that.
I can repartition and flash stock or the updated rom and things are working fine but I'd really rather not lose my data.
It occurred to me this morning that I might have done the backup before removing the lag fix. I'm guessing the backup won't recreate the ext2 partition and that's why things are FC'ing like mad?
I'm going to - probably pointlessly - try to re-flash, install the lag fix and do a restore to see if anything different happens.
If anyone else has a suggestion while I wait for my phone to charge enough to do the lag fix .... little tiny voice... <help?>
Well, re-installing oclf 2.1 didnt change the behavior. I've still got a brick after restoring my nandroid backup.
I've gone back to a clean ji6 install and I'm trying a titanium restore. I'll be a week out of date if this works but won't lose anything critical. If this works. I hope, I hope, I hope.
That happen to me too, had to odin back to stock then flash bionix 1.7. lost all my data
How about flashing JI6, applying OCLF, booting into clockwork recovery and selecting Nandroid-> Advanced-> (Your restore file)-> Data-> Yes.
This will reflash all your data on top of the new rom. The reason for reapplying the OCLF is because you backed up BEFORE undoing OCLF, so all your data is still in a .EXT2 file, so we have to have it expecting that before restoring.
Only thing left to do at this point is redo any themes you had installed, and your phone should be back to normal + the update.
I must have backed up after removing OCLF because I ended up flashing stock and restoring just the data. Unfortunately while the data was there, none of my apps were so the fact that the data was there was moot since I couldn't get at a lot of it.
I followed up by flashing just system and now I've got my full functionality back just without ji6.
I'll probably try again after rolling back a few more changes -such as removing the rom manager update.zip - and making another backup or three.
I wonder if the people who've rooted - like me - are having problems because of updated versions of busybox that clockworkmod installs.
Also, the titanium restore worked on stock. I haven't tried it on ji6. yet.
After all the forced learning by doing where flashing roms is concerned I decided to skip the tmo update since they can't be bothered to provide a full list of fixes. I've installed the latest bionix and couldn't be happier.
phillipxenxciel said:
That happen to me too, had to odin back to stock then flash bionix 1.7. lost all my data
Click to expand...
Click to collapse
I've found that a Titanium backup is enough to use when flashing a new rom. Do a full backup. Flash the new rom. Restore apps+data. Selectively restore the green system items (so you get all your sms msgs and contacts). Enjoy. Worked for me on Sunday as I flashed various versions of bionix to try.
Hey guys,
Just Flashed to Bionix -V 1.3.1. Trying to restore all my apps and data with Titanium but it force closes pretty much anything i try and open. Is there something I have to clear before i can restore all my apps and data?
dont restore anything that has "SYSTEM DATA"
I dont think explained myself properly the first time. I mean anything i pretty much try and open that wasnt orignally on the phone gets forced close. Carhome, Opera mini, pingchat, reddit app, most of the games. Also id like to include that most of my apps were already restored when the phone booted up for the first time. Should I just reflash the rom?
if your apps and everything were there upon first boot it sounds like you had a bad install, something in the updater script got messed up when you downloaded. Redownload and Reflash sounds like your best option.
Yeah, something is not right there. A good install would wipe your phone (none of your apps should be there).
I would personally suggest going back to stock and then flashing. Its a super easy process and I wrote a guide in my signature, may help.
OK so ive redownloaded bionix and ive put it on the internal sd card. I rebooted in recovery. disable lagfix and rebooted. now its just sitting on the Vibrant boot up screen.... for about 15 minutes now.
I thought this **** was supposed to get easier..
NVM its rebooting now. Im reflashing it now, ill let you know after the reboot how it went.
Fixed.
Just restored 229 apps. **** me.
So is everything good?
Note that usually before flashing you are supposed to do a factory reset was it? I forget but the EDT Roms had the correct procedure to do in clockwork right before you flash a ROM so that you don't get issues like this. If your issue is still not resolved, look up an EDT ROM page and look the installation procedure.
OK:
Briefly, Running fine on VEGAn 7 RC 1 with Pershoot's latest. When the Tab was running and booting, I made a full backup in CWMod.
Screwed around with some permissions and once I rebooted, ended up at VEGAn Tab pulsating Boot Screen. It would do its thing for a minute or so, screen would go blank and then return immediately to the same VEGAn Tab screen (i.e., not a full boot).
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
I searched the forums a lot, so either I am not very good at searching or this has not been addressed.
Advice would be appreciated, as this is not the first time I have been here and want to learn if there is a way to repair it (obviously, I can reflash ROM+Kernel) restore via Titanium and only have a little manual recovery left to do.
Thanks!
I had the same thing happen to me while i was changing around roms. I know its not the exact thing but regardless. Anyways, try mounting your tab in cwm as USB and pull your back up off the tabs memory. Go back to cwm and wipe everything, then repartition to advised settings. Remount your tab as usb and put the back up back on your drive and restore again. It may work.
Sent from my VEGAn-TAB using Tapatalk
iamjakecali said:
Not a problem, right? I just booted into CWMod, cleared out everything and restored my earlier backup.
No go. Same loop at the VEGAn screen.
Click to expand...
Click to collapse
If its something simple, clearing the Dalvik Cache in CWM might fix it.
I appreciate the ideas. Unfortunately i have tried then all. One of the times this has happened i was messing around with the old two taps xoom. Of i knew anything about the really technical stuff i might speculate something to do with boot loader.
Oh for anyone here who bricks, Don't freak... sometimes i do several times a day and have always come back from it ... mostly using the advice of all the brilliant people here, occassipnaly by messing around with adb, and once i let my monkey push random keys since he had already managed to compose a sonata...
Isn't my first root/unlock/rom flashing on android phones. Did my thunderbolt, rezound, and was doing my DNA. I did the unlock root and all that just fine. I am using TWRP, I was running the hatka ROM but there was a few things I didn't like about it. Decided to tyr out the Venom one. Booted to recovery, saved a backup, wiped cache factory reset, then I flashed the boot.img that was recommended. Went fine. Went to install venom ROM and got through half of it and then at the 'Extras' menu where you can select additional mods I am stuck. I clicked block ads and it check marked it. Went to click next and the screen is unresponsive. The captivate buttons vibrate on press but do nothing. Can't power down, when I hold the power or power+vol down after a couple seconds the captivate buttons just start to flash. HOW THE HELL do I get out of this?
Hmm got out of it. Gonna do another wipe of everything and reset and such and try again. WIll update after
Went through that time. I skipped any extra mods and such so not sure if that was it or something else random the first time.
So I updated to the newest software MI5. Went from that and did the root which was sucessfully. I had put on OUDHS Touch CWM-based Recovery thru ODIN which was sucessful as well. After doing all of that, I downloaded Josh Beach's Jellybomb test rom. The steps I did was booted into recovery which is the one above, factory data reset, wiped cache, and wiped dalvik, then flashed the zip. The zip looked to flash ok but when i went to reboot, it just keeps getting stuck at the samsung galaxy note 3 screen, then it will reboot then go to the same screen. Did I do something incorrect? This happened to me on this ROM and the stock MI5 ROM rooted.
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
runner77 said:
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
Click to expand...
Click to collapse
so it sounds like i cant flash any custom roms right now? Just odin back to stock and root it and leave it at that?
this probably wont help for this particular problem, or maybe it will.. but for anyone else getting a bootloop..
i just now had a bootloop experience that i got out of.. and here's how it started - i have not rooted my note 3 (i have rooted my galaxy gear though, but i don't think that would affect the note 3).. anyway, i use the nova launcher as my main launcher.. and just before i got stuck in a loop, i had been playing with a new launcher called Themer... i just started it without setting it as default.. then i went back to my main launcher and i noticed that almost all ram was used up and i thought i might as well do a restart as it has been a while... and then it just would not start.. i got to the lock screen image, and then it would restart again and again, with no sound for the animated logo.... it eventually booted up ok, but i have no idea how i got it to work... however, i held down the power button for a while longer and it would "force" a new restart and basically abort the one already in progress, and if i did that, the boot up sound would come back... i continued doing that a couple of items and then it finally worked.
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
lunchboxVA said:
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
Click to expand...
Click to collapse
And when flashing make sure to wipe dalvik/caché several times for good measure.
Sent from my SM-N900P using Tapatalk
checking in to add that i found a new solution to my own problem here.... it "magically" started the last time just by me keeping on rebooting.. but that's not really a good solution and i don't think it lasts
and for me it didn't... as today i did a new restart, and it got the same stuck in a loop again, however, i followed the first mentioned workaround in this link here and it worked perfectly.. it was really that simple in my case it seems, i have done several restarts now and the bootloop is gone!...
oops, seems i cant post any links for not having enough posts yet...
i'll just add the steps mentioned instead
1 . Remove the battery and the SD card.
2. Put the battery back in and turn on the device.
3. Try Menu > Settings > Wi-Fi > Menu > Advanced and uncheck Always allow scanning.
4. Now you should be able to turn the device off and reinsert the SD card.
5. Boot it up and your problem might be gone
i have no idea how it works though as i personally don't understand the connection between then external sd card and the setting you turn off in the wifi advanced options..
cheers!