Database Info

[Q] issues installing liquid smooth rc7

I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum

try formatting system after the data wipe, then flash rc7.

dmalikyar said:
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
Click to expand...
Click to collapse
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)

droidstyle said:
try formatting system after the data wipe, then flash rc7.
Click to expand...
Click to collapse
Tried that and it made no difference.

dmalikyar said:
Tried that and it made no difference.
Click to expand...
Click to collapse
try using odin......just remember after you odin back to the root66 image, you have to reinstall CWM and doesn't hurt to make sure ur bootloader is unlocked using the 1.2 version of the ez unlock then flash again

digitalsynner85 said:
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
Click to expand...
Click to collapse
I'll try the Odin route. I'll go back to root66 and try it from there.

dmalikyar said:
I'll try the Odin route. I'll go back to root66 and try it from there.
Click to expand...
Click to collapse
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid

digitalsynner85 said:
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
Click to expand...
Click to collapse
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.

imklaho your
droidstyle said:
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
Click to expand...
Click to collapse
I Odin'd root66 and installed the ez unlocker as well as clockworkmod via rom manager. I went into recovery and wiped data/factory reset/wiped cache/wiped dalvik cache. I then installed LS RC7. It went through the installation and indicated that it completed. After I reboot, I briefly see the Samsung logo, then the screen is completely black. No boot animation. I let it set for over 20 mins. and nothing happens. This is absolutely bizarre. I've tried 3 different downloads. I'm at a loss. Is there a way to convert the zip to an img and odin it on?

KT747-Kernel-AOSP-JB-VZW-10-31-2012.zip
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?

dmalikyar said:
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
Click to expand...
Click to collapse
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications

shangrila500 said:
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.

dmalikyar said:
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
Click to expand...
Click to collapse
Have you tried TWRP recovery as opposed to CWM?

shangrila500 said:
Have you tried TWRP recovery as opposed to CWM?
Click to expand...
Click to collapse
I installed twrp and I really like the interface but it didn't resolve the issue of flashing RC7. I've installed paranoid android and can install aokp and cm10 with no problems. I can't install RC7 or slim beans.

Cannot install Liquid Smooth
Yah the guy at Liquid Smooth is kind of a butt wipe. I understand the desire to have a screen capture and a logcat but if the user can't even install the flash how is a screen capture going to help. Maybe a logcat could. But either way why be an A hole about it.
I am having the same issue, I even formatted my system and still LiquidSmooth says it flashed but it just refuses to boot. I have used Odin to install the stock JB 4.1.1 from Poland but I still get the same problem. I do believe it has something to do with having tried CaponMod4NSS_3.0 the day before. Still I would think formatting the system would resolve that.
Any ideas? I will try to install the Samsung 4.1 ROM with Odin to see if that helps.

[Q] Bootloop after flashing TWRP. Please help.

I was on locked on stock OTA JB.
I unlocked a few days ago, then last night flashed TWRP. Created a nandroid, then rooted.
Today I've spent several hours downloading ROMs, doing Titanium backups, surfing forums, backing up my personal files etc. i.e. using my tablet normally without problems.
I decided it was time to flash a ROM so booted in TWRP to create a fresh nandroid. Then when it finished I rebooted the system with the plan to copy the nandroid to my pc.
The tablet booted, but then after 30s or so rebooted. It's now stuck in this boot loop. So I tried a cold boot, and then restoring the latest nandroid and the problem persists. I'm currently trying to restore the pre root nandroid I made.
To recap - I am on stock OTA JB, with TWRP v2.3.1.0 recovery. Any thoughts?
Ok just to update - the pre root nandroid seems to be stable at the moment. So... What to do?
Should I reflash the recovery? Try a different recovery?
Any ideas why the nandroid would be borked when the system seemed stable when I created it?
Sent from my Galaxy Nexus using Tapatalk 2

Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.

No it doesn't, it just replaces stock recovery and allows you to gain root.
You could start your own thread. Or, you could read the thread in Android Development that gives clear instructions for noobs to gain root and install TWRP or CWM.
Sent from my Galaxy Nexus using Tapatalk 2

which ROM were you trying to flash? was it a JB rom?
bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
After you install TWRP, you just need to flash a root zip file with TWRP to gain root..

bshpmark said:
Question: Does TWRP actually root the TF300? Mine is unlocked but I am looking for the easiest way to root the device.
Click to expand...
Click to collapse
Flash a rooted custom rom. ull gain root + rom easily

mike-y said:
which ROM were you trying to flash? was it a JB rom?
Click to expand...
Click to collapse
Since this thread got immediately hijacked i'm not sure but I'm going to assume this part of your post was aimed at me...
I wasn't trying to flash a ROM at all. I hadn't even got that far. All I'd done was flash the recovery, root it and then create a nandroid. It was creating the nandroid that seemed to trigger the boot loop, even though that makes zero sense.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

can you get back into fastboot connected to your PC?
I'd try to re-flash TWRP. Also make sure you are using the JB version, not the ICS version.
http://teamw.in/project/twrp2/97
I just unlocked and flashed TWRP on my tf300 (with the OTA JB update) this morning, and everything is working fine. I also flashed a root file without any issue.

I reflashed TWRP and re-rooted it seems to be OK.
Then I found I couldn't get any ROMs to work - they all froze at the boot screen. The solution to that problem lies in flashing the US update of JB rather that the WW. Now I'm running Hydro with Untermensch's kernel.
One thing I did notice with TWRP 2.3 is I get the error "can't mount /storage" in the log whenever I do anything. A bit of research suggests this might be an issue with TWRP 2.3, not present in 2.2. I wonder if that is what was causing the boot loop issue I had previously.
I can't seem to find a blob of 2.2 to downgrade to so I'm living with it for now and hope it's not going to cause problems down the line.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Good that TWRP always using the same names for a DL Link. So here is the 2.2 for JB Bootloader
If you are looking for ICS just edit the dl link .
http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.2.2.0-tf300tg-JB.blob

[Q] Razr HD Update - 9.18.79.en.US - Failed

Razr HD Maxx on Verizon.
I am rooted, unlocked bootloader, Team Win recovery, stock OS.
3 times I attempted to install the latest update (9.18.79.en.US). Each time it reboots into Team Win recovery. I then reboot the system and once the desktop loads, it reboots immediately into Team Win recovery. I can never get into the OS anymore because it immediately displays "Powering off" and loads the Team Win recovery screen. So, each of the 3 times I attempted to install, I ended up reverting back to my backup.
What am I doing wrong? Do I need to remove Team Win? Is the update not compatible with my current setup? Or, do I need to do it manually? i.e. download the update and install it using Team Win recovery.
Thoughts? Thank you in advance for reading and attempting a resolution. If I end up figuring it out, I'll post an update. :good:

Fix for Reboots
Too Fix Just go on Teamwin Recovery and select wipe Data>Advance Wipe Data> and only wipe cache and dalvik cache..
that should fix y;our reboots..
as for the update.... no sure yet

Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX

thanks to both responses.
quick update: i located the downloaded update via /cache. i attempted to install it when TWRP came up. "Failed". I wiped cache/dalvik, and that did not work either. It fixed the boot problem initially, but then it just prompted for the update again and the reboot cycle repeated. except I was in a factory state with my apps. (i.e. i had to go through the initial prompts of setting up my phone.)
So, I will attempt to do the following:
deeje00 said:
Your phone has to be stock with all apps in tack to take a ota. So yes you need to be using the stock recovery and preserve and remove root with voodoo.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
and see what happens.
Thanks again.

Installing new Razr HD Verizon update
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:

I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app

Andrewl62 said:
I did everything except root recovery with voodoo now I have ota update to 9.18.926 bootloader unlocked but can't get root... Do I have to start over with rsd?
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053

Mr-Glass said:
If you still have custom recovery with and unlocked bootloader you should be able to flash the UPDATE-SuperSU-v1.41.zip... If you do not have custom recovery install TWRP/CWM so you can install the zip..
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I have stock recovery on my phone, re-enabled/unfroze all stock apps, temp unrooted with voodoo and it still won't install
Any thoughts?

woodjc01 said:
The update must be installed using stock recovery. I did this just today by temp unrooting using voodoo, installing stock recovery using razr hd utility, and then downloading and installing the update, which will boot the phone into the stock recovery to automatically finish the installation after you click install. After the phone reboots, I verified that the update installed, re-rooted using voodoo, and re-installed TWRP using the razr hd utility. After this, all is working well. :good:
Click to expand...
Click to collapse
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.

by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
Your welcome. Glad I could help.

forgot to give an update. i got the update to work with the stock recovery. i'm on newest stock os build with unlocked bootloader, root, and stock recovery. :good:

by3times1minus1 said:
This worked perfectly for me coming from 9.16. I'm now running stock 9.18.17.XT926 rooted and unlocked with TWRP reinstalled. No hiccups at all, thanks, woodjc01!
EDIT: I did unfreeze/enable all the bloatware apps I had previously disabled (zappo's, nfl mobile, real racing 2, etc) before installing the OTA update.
Click to expand...
Click to collapse
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.

My update failed to install as well. I'm rooted but NOT unlocked. Can someone point me in the right direction regarding how to restore bloatware apps? I made the rookie mistake of completely removing some of them a while back. I sincerely apologize if a solution has been posted already, as I was not able to find one so far.

s_u_n said:
My dad is getting a message to update to 9.18.x every 24 hours.
Sometimes he accidentally hits the OK/ update button and has to go back in TWRP to wipe cache and dalvik.
So, how does one freeze the Verizon update application? We have unlocked bootloader and running 9.16.x and TWRP installed along with the Voodo thing for securing root.
Click to expand...
Click to collapse
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.

iBolski said:
Why do you not want the update? Your bootloader is unlocked so you're safe to go all the way to Kit Kat.
Click to expand...
Click to collapse
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.

s_u_n said:
Well, I had asked to hold on till 4.4 is made available and that was supposed to come out in January.
But yesterday I upgraded the phone to 4.4.2 following Samurai's thread on DroidRzr forum.
Click to expand...
Click to collapse
But that's what this OTA was - the 4.4 upgrade. I guess I'm a little confused on what you were asking exactly.
Glad you are on KK now, though. And, you can go back to JB if you want to since your bootloader is unlocked.

Droid Razr HD bootloop after 1st boot

I have an XT926 with CM10.2 installed. I started clean and unlocked the bootloader, installed twrp2.6.0.0 and made a backup of my 4.1.2 stock rom. I then wipe everything multiple times, install cm10.2 and boot. It boots fine and I got everything set up. Then I go to reboot and it just hangs at the motorola logo and wont go anywhere. I have done this several times now, even with using the droid razr hd utility to go back to stock. Does anybody know why it could be doing this or any kind of a fix. Im going to try to see if it has this same problem with 4.1. But any help is appreciated.

clouse2013 said:
I have an XT926 with CM10.2 installed. I started clean and unlocked the bootloader, installed twrp2.6.0.0 and made a backup of my 4.1.2 stock rom. I then wipe everything multiple times, install cm10.2 and boot. It boots fine and I got everything set up. Then I go to reboot and it just hangs at the motorola logo and wont go anywhere. I have done this several times now, even with using the droid razr hd utility to go back to stock. Does anybody know why it could be doing this or any kind of a fix. Im going to try to see if it has this same problem with 4.1. But any help is appreciated.
Click to expand...
Click to collapse
i had this same problem until i installed the latest version of cwm 6.0.3.5 by Hashcode
you can update using this utility made by TucsTwo, updated by me.
http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar

[Q] help upgrading from 4.1 to 4.3/4

ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.

Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app

Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.

yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.

resolved. thanks guys.

Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.

CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.

jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.

CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.

The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.