I was running Liquidsmooth 2.9. Wanted to try out the newest leak from Liquid running KitKat.
Downloaded everything, new gaps, etc. Went to install and received a (Status 7) error twice. Updated o the latest TWRP and tried again.
Received the (status 7) again, tried one more time for good measure and it worked.
Immediately noticed that this build was not stable or suitable for a daily driver and tried to go back to my previously made backup.
For whatever reason it wasn't recognized in recovery even though I could see it when navigating in the files.
I tried desperately to move the back up so it could be recognized but to no avail.
Decided to just download the official 2.37 build of Liquidsmooth and the old gaps and reflash. I have done this now three times successfully but
can't get past the splash screen.
Back up isn't working, flashing rom isn't working, now I'm stuck with a soft bricked device and getting extremely frustrated. What is my next move?
1967ls2 said:
I was running Liquidsmooth 2.9. Wanted to try out the newest leak from Liquid running KitKat.
Downloaded everything, new gaps, etc. Went to install and received a (Status 7) error twice. Updated o the latest TWRP and tried again.
Received the (status 7) again, tried one more time for good measure and it worked.
Immediately noticed that this build was not stable or suitable for a daily driver and tried to go back to my previously made backup.
For whatever reason it wasn't recognized in recovery even though I could see it when navigating in the files.
I tried desperately to move the back up so it could be recognized but to no avail.
Decided to just download the official 2.37 build of Liquidsmooth and the old gaps and reflash. I have done this now three times successfully but
can't get past the splash screen.
Back up isn't working, flashing rom isn't working, now I'm stuck with a soft bricked device and getting extremely frustrated. What is my next move?
Click to expand...
Click to collapse
Wrong thread buddy
Lol
Retail N3
Related
Here are my problems:
1st and more important most roms wont boot in my u8800pro. I started with official 2.2.2 that came with the phone. I rooted the phone and installed recovery 5.0.2.7. Later I decided to try a different rom. I downloaded CM 7, kalo's, ics, MIUI (both gingerbread and ics). I installed CM7 first. After the update finished I rebooted the phone. It got stuck on the CM start/splash screen. Rebooted and the phone run. Unfortunately it kept powering off or rebooting on its own.
After that I tried all the other gingerbread ones. All of them get stuck on the start/splash screen. The one after the huawei flower thing.
All of the ICS ones load but I get no network for some reason.
Just to point it out I wiped data and cache and calvik everytime and I followed the instructions I found in the roms forum posts.
Atm am stuck with CM 7 and the random power off/reboot issue.
And that is problem no2. I dont mind using CM 7 if that can be fixed.
Any suggestions welcome
Well I managed to install stock 2.3.5 using the instructions in the #9 answer of this post http://forum.xda-developers.com/showthread.php?t=1405375&highlight=cm7+reboot+problem
Hey guys, I'm suffering massively after flashing faux's kernel. It started off when I rebooted the device and it took me to device setup. I thought it was a malfunction, so I went back into recovery and flashed my backup that I had made minutes before. But the same thing happened. It took me back to the setup screen. So I decided to wipe and flash the ROM again (pa 2.5). And everything seemed fine until I checked the kernel status. It still had the same kernel as before (faux123). I thought I had made a mistake somewhere so I decided to download and flash a new kernel. I downloaded it but after I went into recovery I couldn't find the downloaded file... So I rebooted and downloaded the kernel onto my PC and transfer it to my tab via USB. I rebooted into recovery and flashed the kernel over fastboot... But to no avail. When I rebooted the device it took me to setup again. This is when the screen went crazy. It started flashing and and going nuts. I thought it was the kernel I just flashed, So I rebooted and the tab was fine but it took me to setup again. I went through the rigmarole of setting up a 4th time and checked my kernel status and guess what? Still faux123. Now I really don't know what it wrong. I've tried using the nexus root tool kit v1.5.2 but still to no avail. I've tried manually pushing the files over adb but still Nothing... I've sent faux a message asking for help but haven't received a reply yet.
Any help would be great guys.
Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
fadentales said:
Very very strange I've never seen this before, so I was just doing my typical day walking around at work and all of a sudden I feel my phone got hot, pulled it out of my pocket and it was stuck on boot screen. So I did a battery pull to get it back to the rom and it just stopped at the bootscreen, after that I tried a dirty flash, then a clean flash...all I see is a bootscreen never gets past it. Recently updated to new firmware 2 weeks ago and did notice it was strange when I flashed the GE Rom kept asking me to Install SU. Anyone got any idea how to fix this? Only issue i noticed was during the install of the rom i get a unable to mount /preload but besides that everything completes fine
Click to expand...
Click to collapse
Use odin to go back to full stock, upgrade to MF9, do a factory reset, later root the device install recovery, do a full wipe install GE rom fix permissions. Report back on what happens. (Keep in mind this will wipe internal memory MAKE BACKUP!)
Sent from my SPH-L720
First of all, hello all!
I'm a new member here.
So, what's the problem? Well, I recently rooted my Galaxy Tab 4 SM-T530 (WiFi only version) with Kingroot. Then I installed Cyanogenmod from the thread listed at the ROM section. All was working fine up until I decided to flash the GApps.
I chose the newest versions (both Zero and Mini for 6.0) but none of them worked.
Flashing went well. The problem was after booting.
After the first boot, I'd get caught in an endless loop of errors stating that "Unfortunately, Setup Wizard has stopped working". I couldn't do much other than rebooting. But then, I was greeted with yet another problem: it was stuck in a boot loop. Basically, after saying that it "Prepared Google App" and some others, the tab would repeat the process in an infinite loop. I left it for half an hour to do so, but the problem persisted.
Keep in mind the fact that I installed the newest version of Mini GApps package provided from that thread.
If any of you can help me out with this, I'd be very thankful, since this is the same time I install a custom ROM, and I really don't want to come back to the old Samsung ROM
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
This is from where I installed all things needed.
Try again, this time flash both zips at the same time and not doing anything in the middle of both flashes. The usual cause of the same error in my other s3 is booting the ROM up, going back to recovery, then flashing GApps.
I never did anything else. Now I wiped data/dalvik/system/cache, reflashed the ROM and now just finished reflashing both zips in TWRP (first Mini then Zero, can't do them at the same time).
Now, I'm pretty much 'fingers crossed', as this is what an error told me. Pretty much tried to flash the zips without wiping anything/reflashing the ROM. That's why I went for a clean install.
EDIT: it didn't work at all. Still caught in the same "Preparing app x" boot loop. Now I'll let it run for 6 hours and see if not my own impatience is the problem.
EDIT 2: For some reason it took ages to boot up. Now, when I finished booting, I saw that the Play Store, Quick Search Bar and the Google Services weren't working at all. I tried to manually update them, but ended up in an agonizing loop of "Unfortunately, Google Services Framework has stopped" errors. Again, this leads me into thinking that the GApps from that thread aren't working.
Never mind. Solved after a LOT of trial and error.
----
I have a Zenfone ZE552KL in a weird predicament. I was running the Unofficial Lineage OS rom for a while. It initially had a bad bug that made it unusable (couldn't use the keypad while on a call, phone would crash). I finally got around to installing an updated version of the rom which fixed that issue, but then the battery was lasting barely 8 hours (instead of the usual 20+ hours). I decided to give up and go back to stock. I followed some instructions and installed the MM stock rom, went back to stock boot and recovery, then tried to update to stock Nougat, and I can't do that. Every time I try flashing from the SD card in the stock recovery, I get "E: Failed to verify whole-file signature" and the installation aborts. I've tried every fix imaginable (re-downloading, downloading different versions, trying different SD cards, etc), and I just can't get it to work.
So right now my options seem to be use LOS with an 8hr battery life, or use an old buggy MM stock experience.
Can anyone point me in the right direction so I can have something usable? Is there a LOS specific version that doesn't have major battery issues AND has a working phone? Is there anything I can do to get the stock OS back to Nougat?
<sigh>
A
TWRP recovery allows you to toggle "zip verification" when installing roms. Flash TWRP and then flash your Rom while making sure "zip verification" box is unchecked.
I finally made progress today. I was able to flash the stock Nougat FW using TWRP, but only after flashing LOS to it first. I have no idea why. But it works and I'm done playing with it. It's just too buggy and there isn't enough of a dev community for it.