I've crawled through the development. I've flashed a ROM before, but went back to a rooted stock version because of the bugs in the builds I was using. But now, basically any time I flash something new, it bricks at the Galaxy Tab 2 7.0 screen.
I've done:
Flashed back to non-root stock firmware (newer)
Then flashed the CF Autoroot, installed Mobile Odin, flashed CWM official 6.0.2.3 for the 3113. When I install CM9, brick.
PA doesn't brick immediately but sticks at the splash with the shark.
So, I flashed back to non-root stock, CF Autoroot, installed CWM 6.0.1.1 and tried again. All ROMS besides PA hang at boot screen (like before), PA hanging at the shark.
I figured it was a kernel issue? So, I've tried both Dhollmen and AGNI. No change.
I can get it to rooted stock JB, but I don't *want* that, I want something that isn't so freaking bloated and buggy.
Ideas?
*edit*
So, after installing TWRP 2.5 on top of stock, I downloaded Rom Manager, installed CWM and CM9 through that. Got past the initial boot screen, but seem to be stuck on CM Splash. Would flashing older stock image and trying from there help?
This might seem like a dumb question since you say you have flashed ROMs before: are you doing a "clean" install? I also will wipe cache and dalvic cache AFTER each install. I only have "bricked" a device one time and that is when I tried short cuts. I also ALWAYS follow the developers instructions to the letter.
Sent from my GT-3113 running DF-2
Related
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.
xt926 with unlocked bootloader and can run 10.1 nightly from get.cm with no problem. However, when I install a 10.2 nightly - whether from get.cm, epinter, dhacker or skrilaz - even though the initial boot comes up clean, rebooting after the initial boot gets stuck on the boot logo.
I have tried different recovery images - cwm, twrp, oudhs - and different versions of each.
I have tried clean installs, full formats and dirty upgrades from 10.1.
I have tried multiple force boots from this state (power+vol up).
I have tried with and without the updated gapps and UPDATE-SuperSU-v1.51.zip.
Restoring from backup does not get past this hang. The only way out is to revert to stock (I use mattlegroff's DROID_RAZR_HD_Utility_1.21).
Does anyone have any idea how I might get past this or even get a log?
Only thing that fixed this for me was to flash back to stock 4.1.2, flash newest CWM touch recovery, then flash newest nightly, Gapps, and SU. Then, a popup comes up saying something about the ROM wants to flash your boot image, and asks if you'd like to fix this. I answered YES (fix) and been working since.
Any chance you could link where you got your recovery and SU?
Much appreciated.
Same issue here...
I've also tried everything listed above. I've done everything i can possibly think of to get cm 10.2 on my xt926. For some reason my phone just isn't making it after the first reboot. I've searched and found similar issues but none of the troubleshooting has been working for me. I hope to find a way around this. I need that 10.2!
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
GeorgeHahn said:
Same issue here. Not just CM, every 4.3 based ROM I've tried has either failed to boot or failed to boot more than once (more often than not, they won't boot at all).
I've been at this for hours, but I've had no success so far. I'll let you know if I come up with anything.
EDIT:
Here's my setup:
After every try, I flash back to stock 4.1.2 with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml. I've edited it so it doesn't flash the stock recovery and so it flashes a modified logo that doesn't show the bootloader warning. Partway through, I booted up and updated to the latest OTA, so I had to comment out the tz.mdm files as well. I was using TWRP 2.2.2.1, but I updated to 2.6.0.0 earlier.
Click to expand...
Click to collapse
one of 2 things should fix this problem,
use cwm 6.0.3.5 from here or
go to recovery/mounts and storage and format the data-media line (i know it says sd card but its internal, do not format the external ed card line or you will loose data on it)
also i updated matts utiliity to the latest ota, so you dont have to take the ota just to get the baseband. its in the dev forum. i will be updating it to a newer version if you wait until later, with the newest recoveries.
edit, btw 2.6.0.0 is not the latest twrp although i recommend using cwm as some have had issues with twrp including me.
First off, the latest TWRP seems to have fixed the problems (for me, anyway). Second, you'll need to use the most up-to-date GAPPs when you flash. Also, a lot of people have noted that mounting sytem prior to doing their wipes has solved the reboot issues.
Thanks a ton for the help. Flashed latest CWM and bumped up to 4.4 and everything's working fine. I appreciate the help!
My father has a Skyrocket and he didn't like how slow and clunky it was from stock, so I decided to flash a ROM that I knew well and would make his phone a more enjoyable experience. I flashed TWRP, put Carbon ROM (latest nightly) and the latest 4.3 Gapps on his SD Card, and flashed. Keep in mind I wiped data, dalvik, cache, and system before I flashed anything. Everything went well, phone booted, I got it configured and installed most of the apps he likes to use and it was good to go. A while earlier, I rebooted the phone normally, not into recovery or bootloader, just a normal reboot. The phone shut off, buzzed, and wouldn't come back to life. Pulling battery, button combinations, it would only go to the Battery Icon screen. PC wouldn't recognize, etc. Managed to get it into Odin, flashed stock, it hung at Samsung screen so I had to wipe data in stock recovery. It is running fine now on stock 4.1.2 but I'm really scratching my head at why a simple reboot soft bricked his phone. Used TWRP 2.6.0.0 btw.
That recovery is old to begin with. Second, 4.3 isn't the most stable right now
Sent from my HTC One using Tapatalk 4
Yea, use twrp 2.6.3.0. If you want 4.3 cm 10.2 is working pretty well right now.
Agreed, this is 100% because you used TWRP 2.6.0.0. 2.6.0.3 is the minimum required version for and 4.3 based ROM, and as mentioned 2.6.3.0 is the latest official release.
Thank you all very much. It didn't even cross my mind that the recovery version could be the issue. I guess I might try again later on the newest TWRP.
Sent from my MB886 using xda app-developers app
I have recently had a similar issue with a 4.3 ROM, and I am using 2.6.0.3. Only I could get into recovery after a battery pull and button combo. I just kept following the same steps of wiping flashing and it eventually it took and is running fine now(just jinxed myself I am sure).
Hello! I was looking for some help with flashing ROMs. I have had my A700 flashed with other ROMs before like CM and IconiaN, but for some reason, now it will only boot the stock ROM. I had CM11 on it and decided to go back to IconiaN. Well, it wouldn't boot. To try and fix this, I went back to full stock ICS with a locked bootloader and stock recovery and started from scratch. I've tried about 4 or 5 times, unlcking the bootloader and flashing CWM, but every time I try to flash anything other than an official update.zip in CWM, it just hangs at the splash screen with the animated Acer logo. I did have TWRP for awhile too, but I had CWM originally and I have it now. Thanks!
Dark_Spark said:
Hello! I was looking for some help with flashing ROMs. I have had my A700 flashed with other ROMs before like CM and IconiaN, but for some reason, now it will only boot the stock ROM. I had CM11 on it and decided to go back to IconiaN. Well, it wouldn't boot. To try and fix this, I went back to full stock ICS with a locked bootloader and stock recovery and started from scratch. I've tried about 4 or 5 times, unlcking the bootloader and flashing CWM, but every time I try to flash anything other than an official update.zip in CWM, it just hangs at the splash screen with the animated Acer logo. I did have TWRP for awhile too, but I had CWM originally and I have it now. Thanks!
Click to expand...
Click to collapse
Hey guys! Nevermind! I went back to stock again and tried another ROM first before I tried IconiaN, and it booted! So I guess it was just the .zip of IconiaN I have. Weird too because I re-downloaded the .zip. Anyway, I'm good now!
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.