Not sure if this is a fix or not, but its worked for me more than once now. I was really hating how I would get the static screen or blank screen just before the bootanimation after flashing the Bonsai Rom. It made for a very slow boot up compared to how fast boot up is running stock. i know this seems like a lot of steps to take for something so minimal. But it was bugging the hell out of me and this is what I did to fix it.
Here's what I did to fix the issue.
1.) I flashed Bonsai as usual and got everything setup how I wanted it.
2.) I made a nandroid backup through cmw
3.) I flashed back to stock with the 3.1 OTA (thanks pershoots)
4.) Booted that up, then powered down
5.) Put my tab into download mode and flashed the retail recovery
6.) Factory reset (stock recovery does a couple extra things that cmw does not do)
7.) Booted up, then powered back down
8.) Put into download mode, Flashed cmw recovery through Odin
9.) Then I restored the backup that I made of bonsai previously
10.) Hit reboot and done, no static or blank screen anymore
Not for sure that this will work for everyone, but I just thought I should share.
http://youtu.be/WfycAi3Clq0
Related
Timeline:
Flashed Onyx 4.2
Flashed EugeneKernel A11
Installed OCLF through Clockwork
---everything was working fine, but im anal about my phone and decided i wanted to nandroid restore back to 2.1, so heres that time line:
Disabled OCLF
Factory Wiped
Installed JAC-OV/UV Kernel (2.1 compatible)
Went to Nandroid Restore
I noticed that the restore finished way more quickly than usual, but clockwork said it finished successfully. so i went to reboot and it rebooted into stock recovery. odd. so i chose "reinstall packages" to flash back into clockwork, and now everytime it says "replacing recovery with Clockworkmod recovery" it then goes to "Vibrant" screen, and boots back into stock recovery. (same thing happens if i simply try to reboot, i always get sent back to stock recovery)
So is this happening because Clockworkmod LagFix edition is not compatible with my 2.1 kernel?? If so, is there a way to correct this WITHOUT using Odin?? ( i tried to adb push my old clockworkmod update.zip, in hopes that it would just overwrite the current one, it pushes successfully but same symptoms still occur)
Thanks ahead! (also, since i just backed up my sdcard today, id be more than willing to wipe my sdcard, if theres a way to do that through ADB without needing to be in ADB shell)
Hey guys, I have a weird issue. I recently (re)aquired a MyTouch 3G Slide after selling my old one. The other I rooted back when rooting was still super-hard. I bought it the day it came out, and had CyanogenMod7 running beautifully and everything.
The "new" mytouch 3g slide I aquired was factory reset (s-on) on 2.1. I tried to update to 2.2, but HTCs website doesnt seem to have the files anymore. So I rooted it using UniversalAndroot. I tried to run RomManager to flash recovery, but as you know, it no longer supports 2.1 and below, so that sucked.
I found an old version on here, flashed it as update.zip, and everything was good.
Now that I'm rooted I flash CyanogenMod7 and GAPPS. Everything installs fine, except GAPPS didn't. So I reboot into recovery, and I see it's stock again. Hmmm, strange. I install update.zip again, recovery comes back, I flash GAPPS again, this time only the market installs. Fine with me.
I reboot into recovery to make a back-up after installing everything. Strange...stock recovery AGAIN. Install update.zip, everything is fine, create my backup, reboot and I update CWM through RomManager, everything's good. Reboot into recovery. STOCK RECOVERY AGAIN.
It seems the only way to get into CWM is to flash update.zip (luckily only takes a few seconds), but is there anyway to make it stick? I had to force update SuperUser as well, and a few other things.
So my question is, if I downgrade to stock 2.2 from HTC, root, then reupgrade to Cyanogenmod 7, would all my issues be fixed?
Update.zip will NOT change the recovery; it will only allow you to use the custom recovery for that certain time. You must obtain the recovery image(recovery.img) and then boot into fastboot(press vol-down+power, then press power) and, on your computer, move the recovery.img to the same directory as fastboot and then, still on your computer, type fastboot flash recovery recovery.img, and there you go
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
uglyjohny said:
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
Click to expand...
Click to collapse
I don't have access to a micro sd card reader if the file must be placed on the micro SD card. I already have flashed the stock rom supposedly via TWRP, so I shouldn't have to flash it again, I wouldn't think. If I do, I guess I'll have to get a reader.
Yes. Micro sd. Rename it. You have guodes gere on xda. Im hoping it will help you.
poslato sa elmag radija
It didn't work. Still in same state as before.
I also have access to fastboot if that would help.
m27frogy said:
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
Click to expand...
Click to collapse
Babsector should still work - you would need t do a search for it
It seems to have worked properly, sort of. Flashing FLEXReaper results in an "Encryption failed." prompt at boot, which the button, of course, does not work. Wiping everything works except that the prompt notes "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4" Trying to reflash V8 with TWRP with the V8.bat file fails at format. More help?
My tablet is still displaying "Encryption failed", the button still doesn't work, and I still love my a500. Help?
Anyone?
I guess I'm screwed, then.
In the end, I think my data partition failed. Formatting or wiping data fails and when installing FlexReaper, it reports /data size as -1. Unless anyone knows how to fix flash memory, I think I'm stuck.
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
SebringTech said:
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
Click to expand...
Click to collapse
Have you tried wiping dalvik and cache through recovery? If that doesn't help maybe do a factory reset before restoring the factory image?
Sent from my SM-T330 using Tapatalk
Edit: I think this might be what you need
http://forum.xda-developers.com/showthread.php?t=3176668
I tried to wipe cache and dalvik - still gets stuck at the Samsung logo... Tried to do a factory reset from TWRP and after rebooting from recovery it continues to get stuck. I'll try flashing the kernel but I don't understand why that would have gotten messed with from flashing the recovery and installing the SuperSU part.
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
SebringTech said:
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
Click to expand...
Click to collapse
You're very welcome. Good luck.
Sent from my SM-T330 using Tapatalk
Ok, so I've been Resurrection_Remix_LP_v5.4.6-20150530-hlte.zip for quite some time now, probably since not long after it's release, and it pretty much liked it. Except for the occasional seemingly random "auto reset" of android/app settings and preference (such as forgetting all my saved wifi ssid) after a random crash/reboot.
Starting last week, the camera became problematic, often failing to start entirely (error message, "could not connect to to camera"), or could connect to the back camera, but freezes when i try to switch to front camera. I tried wiping data with TitBak and it worked again, but the problem comes back a while later. Is this a software or hardware problem?
Anyway, I finally decided to upgrade the the latest RR and wanted to upgrade TWRP from 2.8.5 as I go along. Since the existing version fits the requirement for TWRP install...
Code:
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
... I went ahead and did it, with the standard 3 wipes (couple of times) and then the recovery flash. Turns out it didn't work and the phone just keeps freezing at the first screen with Note3 logo and the red/blue/yellow test at the top left saying booting to recovery. It never did!
I then tried to reflash the recovery using odin with the .tar file, it flashed fine and auto re-booted back into the launcher (everything's gone of course). But I still needed to go back into recovery mode to either flash a higher version of TWRP, or install the newer RR.
Still, it gets stuck and wont go to recovery no matter i used the hardware button method, or recovery button in the power menu, or adb reboot recovery.
What's wrong!?!??!
c'mon guys, give me something.
You have flashed newer RR how it goes back to older version after you odin twrp?. Or you mean currently it's the latest, just in the future you need to update to the newest?. Did you flashed the correct rom zip for your phone?. I mean hlte for n9005 and the rest for other variants. I haven't flash 'google like' roms for long not sure it's still different zip for each variants.
Sent from my SM-N920C
I haven't even got to the point of flashing the ROM so it's still on the old RR.
I need to know how to upgrade to the latest TWRP first.
Then why 3 wipes?. If you wipe system you have no rom in the phone.
Sent from my SM-N920C