I was running carbon rom and am trying to go back to TW. is there any certain thing I need to do to get this to work correctly ? I am trying to flash Hyperdrive ROM with no success. using the latest ver. of TWRP, Hyperdrive will install but won't boot properly. I can get to the first screen to select my language and then just keep getting re-boots. I tried kt747 kernel and also the stock kernel with no success.
Any ideas ?
Any input is appreciated, thank you
cjmcsw87 said:
I was running carbon rom and am trying to go back to TW. is there any certain thing I need to do to get this to work correctly ? I am trying to flash Hyperdrive ROM with no success. using the latest ver. of TWRP, Hyperdrive will install but won't boot properly. I can get to the first screen to select my language and then just keep getting re-boots. I tried kt747 kernel and also the stock kernel with no success.
Any ideas ?
Any input is appreciated, thank you
Click to expand...
Click to collapse
What's your flashing procedure? Sometimes it doesn't want to get passed that screen for any touchwiz rom, so I would try to clean flash again. Sometimes it takes 3 or more wipes and/or clean flashes to get a rom to boot when coming from 4.2 or above to 4.1.
If you're trying to move to touchwiz, I would also format your internal SD card to clear out that extra 0 folder you're going to have.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
What's your flashing procedure? Sometimes it doesn't want to get passed that screen for any touchwiz rom, so I would try to clean flash again. Sometimes it takes 3 or more wipes and/or clean flashes to get a rom to boot when coming from 4.2 or above to 4.1.
If you're trying to move to touchwiz, I would also format your internal SD card to clear out that extra 0 folder you're going to have.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
that't what I ended up doing last night was format internal memory. that fixed it. thank you.
Related
Hi guys, I'm using the CM9 ICS with my transformer and I was trying to install a different kernels without any success at all. I've booted into CWM (V5) and installed from sd card but when I restart the machine, It's always with the same kernel. Can someone suggest how to make it work?
How long does the install take? That should give some insight onto what it is doing
yosi199 said:
Hi guys, I'm using the CM9 ICS with my transformer and I was trying to install a different kernels without any success at all. I've booted into CWM (V5) and installed from sd card but when I restart the machine, It's always with the same kernel. Can someone suggest how to make it work?
Click to expand...
Click to collapse
Just to be sure, CWM v5 will not read external uSD card, only the internal storage /sdcard. May I know the kernel you are installing?
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
have u tried wiping the cache and dalvik before flashing them?
scottyf79 said:
have u tried wiping the cache and dalvik before flashing them?
Click to expand...
Click to collapse
Yes I have... no good
yosi199 said:
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
Click to expand...
Click to collapse
A minute is way too long. Kernels only take like 3 seconds cuz they are small.
Try mount /system under mounts and storage before flashing the kernel.
yosi199 said:
It takes about a minute to install.
I've tried a few:
TesteyMeh ICS 0.7
Blades
Others...
All of them seem to install fine but when rebooting I see the same kernel version and I cant OC.
Click to expand...
Click to collapse
Flashing a new kernel takes a few seconds. After reboot please pay attention to the blue indicator below the Android figure. It this not appears something went wrong with the first stage of the flashing process, invalid image/zip file etc.
Please use the customized CWM version, just not the flashed one from the Rom manager. I'v good experiences with the R2 (internal sdcard only) as well with the R1 (external micro-sdcard only). I preferred the R1 version.
Btw I'v have the best experiences with my TF101G with the CM9 build of March 29 combined with the quevor-test8 (just NOT from the guevor thread but ONLY from the thread of Richard because it's compiled for CM9) kernel, no reboots and no deep sleeps anymore while 3G and Wifi is working fine. Please do not wipe or clear something before flashing the new kernel to prevent Wifi problems. And I'v the best experiences not using the reboot system now from CWM but using power down and switch on the TF manually.
antond57:
i too have been having trouble getting kernels to allow overclocking...i flash one, all looks ok but when i get to tablettop the kernel info appears unchanged and setcpu wont clock past 1000.
could you maybe please post links to the rom and kernel you used? im having trouble locating the Richards R1 and R2 versions. i would like to see if i can repeat your success w/ these versions.
much appreciated.
I have same issue except worse yesterday. I'm on latest CM9. I tried to flash guevro test 9 and I did wipe both cache. Using roach 2 recovery. Just stayed on Asus screen. Blue bar did pop up and take a second or so but nothing. Checked md5 and all was good.
I had to totally flash ROM again after a full wipe because even a restore from recovery wouldn't go past very first Asus screen. I'm not sure what happened but I'm definitely now worried about trying a new kernel again
Sent from my Transformer TF101 using xda premium
eminembdg said:
I have same issue except worse yesterday. I'm on latest CM9. I tried to flash guevro test 9 and I did wipe both cache. Using roach 2 recovery. Just stayed on Asus screen. Blue bar did pop up and take a second or so but nothing. Checked md5 and all was good.
I had to totally flash ROM again after a full wipe because even a restore from recovery wouldn't go past very first Asus screen. I'm not sure what happened but I'm definitely now worried about trying a new kernel again
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Yap, I have the same problem. Nandroid restore did not restore to the previous state. For me, re-flash the ROM fixed the problem (no full-wipe).
Try Using clockwork recovery
I have just flashed guevor kernel as well with no problems. I'm using clockwork mod recovery. Have you tried it?
Well I haven't been on XDA in over sixth months but in my times of trouble I require help. Awhile back I flashed one of the first experimental ICS ROMs to my Xoom, it was non fuctional in many aspect but I liked it and kept it. Now, I'd like to get rid of it but I can't install ADB on my new computer (It's a Java JDK thing that I can't solve for the life of me) I tried flashing a new ROM over it but it fails half way through. So how can I get back to stock without being able to flash or use fastboot? Thanks guys.
P.S. Sorry that my terminology is rusty.
Flash a custom rom ics from teameos. It is fully functional and way better than stock. Let me know if you need help with that.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Flash a custom rom ics from teameos. It is fully functional and way better than stock. Let me know if you need help with that.
Sent from my MZ601 using Tapatalk 2
Click to expand...
Click to collapse
I already tried flashing different ROMs but it won't let me, I just get an error after it tries to install, no matter what SD card or ROM I'm using.
I'd recommend flashing this in recovery: http://goo.im/roms/TeamRogue/Xoom/Recovery/rogue_XM-recovery-1.5.0-rc3.zip
It's an updated touch recovery for the xoom, then reboot and go back into recovery and flash a new rom with that recovery, should work but let us know if you have more issues
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.
Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.
What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.
Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill
I'm running into an issue. I have at&t skyrocket (i727). I am trying to flash a rom but every time to try, it aborts. There's a message that says, "This package is for sch-i727 devices; this is a hercules"
Any advice on how to proceed?
thanks in advance.
Are you sure you don't have a t989?
jd1639 said:
Are you sure you don't have a t989?
Click to expand...
Click to collapse
I am sure. I checked behind the battery. Plus, I downloaded cm-nightly hercules version and tried to install it but it aborted.
cov3nant said:
I am sure. I checked behind the battery. Plus, I downloaded cm-nightly hercules version and tried to install it but it aborted.
Click to expand...
Click to collapse
In settings, about phone what model numbers shows up?
jd1639 said:
In settings, about phone what model numbers shows up?
Click to expand...
Click to collapse
If i recall, it says sch-i727 but i am having trouble restoring my backup.
cov3nant said:
If i recall, it says sch-i727 but i am having trouble restoring my backup.
Click to expand...
Click to collapse
Model says i727. I restored original stock firmware via Odin.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Same Problem
I am having the same problem. Is there any solution?
I am on stock rock 4.2.1
and in settings, it is showing - samsung sgh-i727
ps: it is saying this package is for sgh-i727 skyrocket, yours is sghi727
swapnilps said:
I am having the same problem. Is there any solution?
I am on stock rock 4.2.1
and in settings, it is showing - samsung sgh-i727
ps: it is saying this package is for sgh-i727 skyrocket, yours is sghi727
Click to expand...
Click to collapse
Let's see if I can help. First of all. Be sure to read Vincom's thread about how to install properly a Custom Recovery. Then, go to your custom recovery. Which most likely will be TWRP. I suggest you to Mount the USB Storage and place the CWM zip and your wanted custom rom zip with gapps into your storage. Install CWM and then reboot to recovery. It might take a little bit till CWM starts. Once you are in, delete Cache and Dalvik. Then, install the custom rom. Once you are done, you are done. Before installing gapps I'd suggest you to boot it so you make sure it's all working properly. Last time I installed at the same time (the ROM and Gapps) I saw so many pop-ups that my phone got stuck! Make sure you are using a stable version. As seen several times, nightlies often come with often more trouble than a stable version. They are nightlies for some reason! Right?
I hope it works!
Done!
FriedrichEngels said:
Let's see if I can help. First of all. Be sure to read Vincom's thread about how to install properly a Custom Recovery. Then, go to your custom recovery. Which most likely will be TWRP. I suggest you to Mount the USB Storage and place the CWM zip and your wanted custom rom zip with gapps into your storage. Install CWM and then reboot to recovery. It might take a little bit till CWM starts. Once you are in, delete Cache and Dalvik. Then, install the custom rom. Once you are done, you are done. Before installing gapps I'd suggest you to boot it so you make sure it's all working properly. Last time I installed at the same time (the ROM and Gapps) I saw so many pop-ups that my phone got stuck! Make sure you are using a stable version. As seen several times, nightlies often come with often more trouble than a stable version. They are nightlies for some reason! Right?
I hope it works!
Click to expand...
Click to collapse
Tried with latest recovery!!!
..and done!