So my tablet has been working great with Vegan 5.1.1 Today I went to boot and got the birds, the G-Tabdevs logo, then the VEGAN-TAB log, then a blank screen. Nothing after that. I can get to clockworkmod fine, but I would like to see if I can get back without losing everything I have downloaded and configured (including my music). Is there any quick fix, or do I have to start from scratch?
Got this fixed by doing a restore from Clockworkmod. Sometthing must have gotten corrupted.
Related
While I was playing with my TF700 the other day I accidentally put it upside down resulting in pressing (& holding) the power bottom & volume down .. the device restarted into "Safe Mode"
I tried to get rid of it, but apparently I did something stupid which resulting in boot logo loop (the device is stuck at the second ASUS screen and refuses to boot)
* Note my device is Unlocked & I'm running the latest CleanRom version and I am kinda' experienced user :silly:
Anyway I googled this and I tried the following steps with NO success:
- Cold boot
- Wiping caches
- I also tried to re-flash a rom
which left me only with formatting & wiping data, BUT I tried this thing and it actually worked!
From TWRP I restored my last back up (which was a bit old) But whatever, It actually worked! and I have no problems whatsoever, everything seems to run as before, I also tried to reboot the device and it's still working!
I felt I should share this info with you, it might help someone :highfive:
I'm just gunna give you the whole story.
I'm using TWRP Recovery.
I'm coming back to my d2vzw after a couple weeks of not using it (I got a different phone through work). I'm now back to using my GS3. I decided to update to the latest ROM version. I installed the slimROM stable that was just released, it was slow and they animations were choppy (which is really weird for slim). So I decided to try a different ROM. I've used carbon before, and I really like active display and HALO, so I decided to install that. It installed just fine, installed all my apps, rebooted. It froze on the initial splash screen, didn't even get to the boot animation. So I figured it was just a bad install, so I formatted and flashed from my external SD. Again, first boot just fine, then froze on second boot. So I put a https://plus.google.com/+AlexKruger/posts/dJGXsrAZvj4 in the ROM's community. They suggested that it might be a bug from installing it from my external. So I formatted, then moved the files over to internal, and flashed again. It booted fine, I got to the home screen and restarted before I did anything else. Froze, again. Then someone suggested, that I format, install it, boot all the way, reboot into recovery, wipe cache/dalvik and dirty flash from internal storage. Did it, froze on reboot. So I formatted one more time, and went to boot into recovery while figured out what to do, I accidentally booted into the system. It booted just fine, I went through the set up and activation screens, and it worked. So I rebooted, froze. Then someone suggested I switch recoveries, so I installed the latest CWM recovery, and tried everything all over again, still freezes on reboot.
I know I could just use a different ROM, but it's gotten to the point that I need to fix it. I want to get it to work because F*** you.
Please any help would be appreciated. Thank you.
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
So, I had the final L 5.0 flashed in my Nexus 5 when suddenly, after a poweroff, it wouldn't come back again, stuck in the flying dots boot animation. After many attemps and leaving it for the night, I tried re-flashing the L (LRX21O) back to it. No luck, still stuck in the flying dots (and yes, I did erase the cache and data partitions). I installed the 4.4.4 image and it booted; however I had some *very* weird problems, like the internal memory not being recognized (camera/gallery/appstore wouldn't open, got error about missing sd card, in the nexus 5). Then tried to update OTA from KitKat to Lollipop and got stuck in the same stage; those damn dots!! Can anyone help me "unbrick" my phone in Lollipop?
Ok, I reinstalled kitkat. While it booted up, i watched the internal storage's contents through windows explorer. I cried in joy when i finally saw the folders get created appropriately (dcim, downloads, etc.). but when I proceeded to select the phone's language, i got the message that the camera and gallery apps had stopped working. As soon as that happened, i fell in great pain as the folders had disappeared from the internal storage, which was again empty. What is going on here????
Nevermind, I solved it. Had to fix (e2fsck) the /persist partition (never heard of it before) and voilá - everything went back to normal
I was running KatKiss 4.4.4 on TWRP v2.6.3.0.
Lately it was getting extremely slow. Yesterday I removed some apps I didn't use anyway. I think I removed too much perhaps because today suddenly gapps and many other things started crashing.
I thought I'd just reinstall it, and discovered there's now a KatKiss 6.0.029:
https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496
so I downloaded it, and all the other files, rebooted into TWRP and wiped, and tried the install - it just left me with a boot loop. Ugh.
Got back into TWRP and happened to format everything. Then I installed Universal Naked Driver 0.72 in Win10.
Current behaviour:
Regular reset: boot loop.
Power+up: APX mode.
Power+down: tiny menu, then boot loop after cold boot.
Power+down+up: TWRP.
EasyFlasher asks me to go into APX, then I select one of TWRP 2.2.1 and RogueXM and Roach CWM and even the WW_epaduser9_2_1_24UpdateLauncher.zip file, but in all cases it's just the same. There's some text output, then suddenly a 0.001ms black popup disappearing before I can read it, then the regular window says OK. BUT... there is no change at all.
Any idea what I can try? I searched a lot before deciding to ask here.
The KatKiss link above assumes that the files are already inside the TF101.
How do I put the files into the TF101? What is the next step?
After mannnnnnny hours, I actually managed to install and run the Asus ROM.
I went on to TWRP 2.8.1.1, KatKiss 6.0.029 and the belonging files. Now it's booting up Android, but... not very far.
It keeps complaining with many popups "Google Play services stopped". Is that normal for a fresh ROM?
I add Wifi - then it gets stuck on Checking Connection "it can take a while". It's now more than half an hour. How long is a "while" normally?
I gave up on KitKat 6 and went back to 4.4.4 which then starts.
Still the weird frequent popups "Google Play services stopped".
Reinstalled three times now (KitKat and gapps) and still the same problem.
Could this be a hardware problem?
Well, for all you who read all the above (no one? lol), it is not a hardware problem. It's google messing up: https://forum.xda-developers.com/ee...google-play-services-update-breaking-t3555444