Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Gorkytje said:
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Click to expand...
Click to collapse
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
tallman43 said:
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
Click to expand...
Click to collapse
Thanks for your help! Because of you I tried PhilZ, which then told me it couldn't successfully open/read the rom from the SD card. (Something twrp didn't tell me).
I then changed my SD card for another one I had laying around and it worked. (Strange the old one failed since I formatted it atleast a few times)
Once again, thanks for your tip!
This is now solved!
Related
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Try this
SarahAnne said:
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
Click to expand...
Click to collapse
Try this : http://www.mediafire.com/?4s77jvehqvsuruu
1)Download it
2)put the files ( flashing.boot Mlo etc...) on your sdcard,
3)completely turn off your nook ,
4)put your sd card on nook and turn it on.
5) press the ''N'' button when you see ''cyaogenboot'' (it also saids press ''n'' button for BOOT MENU)
6) in Boot Menu just choose option #1 (Internal Boot) it should boot into cm10
I had the same issue, but after a time (after making some supid things) i bricked my tablet, I figured this out with some help, It worked for me so it should work for you too.
So I was able to randomly boot into the bootloader and boot into CM but now it keeps rebooting into clockwork.
I have also attempted installing CM10 using the following link including using the flashable_fix_bootloop.zip that I cannot sadly can't link to due to being a new user
and the only difference is that now CWM went from blue accents to orange.
The function of flashable_fix_bootloop.zip is to reset BootCnt counter and BCB flag (see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1) in the event they do not get reset properly in some installation/recovery process. It seems that your "recovery boot-loop problem" might have a different underlying root-cause, hence re-setting these counter+flag by itself will not cure the problem.
Which particular build version of CM10 and AOKP ROM did you try?
Also, did you do "wipe data & factory reset" & "wipe cache" as part of the ROM installation?
Have you tried reflashing the ROM once you're in CWM? (As I underestand you may have, but just making sure!)
Maybe download it again (or try another one) and the flash it again (after the usual wipes) with your new recovery.
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
SarahAnne said:
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
Click to expand...
Click to collapse
When you boot from the SD card have you tried holding down 'n' to get to the menu then selecting SDC boot? It should boot cm10.1. Try selecting SDC recovery also and see what it does. You might be doing something wrong during the process.
You can also try renaming your boot file for cm10.1 to altboot. Then try it.
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
SarahAnne said:
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
Click to expand...
Click to collapse
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
DavDoc said:
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
Click to expand...
Click to collapse
6.0.3.1
SarahAnne said:
6.0.3.1
Click to expand...
Click to collapse
Still may be a shot in the dark, but try downgrading CWM to an earlier version, but not so early as to be unable to flash CM10. Maybe 6.0.2.5 to 6.0.2.9
Not ensuring this will work but it may be worth a shot. At least it won't put you in any worse condition than what you are in now.
Good Luck
Another thought, did you make a backup of your last ROM before flashing CM10? If you did I would assume you tried flashing your backup already, but have to ask.
It looks like you may have used two different builds of CWM based on one of your earlier posts - change of font color.
You also try the repart image if you don't have a stock backup. Find it on raywaldo site. It will re write your internal storage with stock ROM. Then flash cm afterward.
Woot I got the factory rom reinstalled, time to install cynogenmod again
I had the same problem
This worked:
digixmax said:
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Click to expand...
Click to collapse
However I was still unable to install any 4.2.2 ROMs + gapps.
I was on cwm 6.0.2.8 (or whatever the exact numbers are)
updated to cwm 6.0.3.7
wipe data
install rom
install gapps
wipe cache
wipe dalvik
everything works now.
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
I recently formatted my internal storage because I felt like I needed a clean wipe. After doing so, flashing anything and rebooting into it will make it hang on the Samsung logo. I flash everything through TWRP v2.5.0.2 and I never had problems until I formatted. Now to get anything to work, I have to "format data" through TWRP and flash after that in order to boot into anything (every single time). And even after booting into it, I can't flash anything (or even simply reboot) without having to see the stuck screen again. Any ideas? My phone is MDK.
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
WhoNeedszzz said:
You need to update TWRP. Latest is 2.6.3.1. Older twrp doesn't use the proper symlinks for the internal data partition that changed in 4.3.
Click to expand...
Click to collapse
Thanks! I think that worked
I'm looking for some help with flashing CM 12.1 on a Nook Tablet. It was a gift from a workmate and I thought I would give it to my wife, but wanted to give her a full blown Android tablet, not a Nook device.
I have CWM recovery flashed on the device and I can boot to recovery no problem.
I had flashed CM 12.1 a few days ago with a version of GAPPS, but it was crashing routinely so I wanted to reflash with a different GAPPS version.
I think I may have done something wrong. Here's the procedure I used. In CWM I reset to factory, formatted the cache, and formatted the Dalvik cache. I also formatted the data, rom, system, and all other partitions OTHER than boot. I did not format boot as I know this would brick the device.
Now that the device was totally wiped clean, I mounted the internal USB to my computer while in CWM and brought over my CM 12.1 zip and GAPPS zip.
I then unmounted and flashed both zips without any errors. I then rebooted. During the reboot, I get a flash of white and then I'm right back to recovery. I tried flashing again and same thing. I'm not sure where to go from here. I think what I'm going to try is putting the zip files on an external SD card and flashing from there but I don't think that's going to change anything.
Any help is much appreciated. Thanks!
Well, tried a couple of things last night. I tried flashing the CM 12.1 snapshot from 11-17-15 from the internal SD partition without GAPPS and got the same result. After reboot, just brings me right back to recovery after a flash of white.
Next I tried installing the 10-07-15 snapshot from an external SD without GAPPS and got the same result.
Do you think I hosed something when I formatted all partitions other than the boot partition? From everything I read about CWM, it seemed safe to do so. I know of course not to wipe the boot partition, but didn't think that wiping the other partitions could brick the device.
I'm sorry, this should be in the Q&A section. Mods, please move if possible.
Thank you!
Try the process at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ to unbrick and return to stock.
See http://forum.xda-developers.com/showthread.php?t=2575489 for more info & tips.
I've been trying to find a recovery fix short of flashing back to stock as the new version of TWRP flashed in flashify caused my device to not want to boot past the logo screen of the recovery mode for TWRP. I tried flashing the 2.8.7 version to no avail. The only recovery that partially works right now is the CM13 nightly I tried in order to factory reset and look at my options. Does anyone have any suggestions to get recovery working again?
EDIT:
fix was easier than I thought, simply factory reset in cm13 nightly, flashed 2.8.4 then 3.00 and good to go.
Had the same problem. Try removing the SD card, if you have one. That did it for me. You might have to reformat it in a computer to get it working again.
j4g3rb0mb3d said:
Had the same problem. Try removing the SD card, if you have one. That did it for me. You might have to reformat it in a computer to get it working again.
Click to expand...
Click to collapse
This fixed my problem. :good: