I had a NT that was running CM11 well.
It ran CWM 6.0.4.5 from internal memory.
Decided to try CM12.1
Wiped cache and delvik
Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip and GAPPS
CM12.1 booted but ran very poorly. Tried various things. Each time I installed
there was a message when exiting CWM "Root access possibly lost. Fix?".
At first I responded no, then finally Yes. Since them Android won't boot.
It always boots to recovery now.
Tried again after updating to CWM_6.0.4.8_chrmhoffmann.zip
No luck.
Installed TWRP 2.6.3.1 and tried to install various versions of CM.
During the install I get error messages, Unable to mount '/bootdata'.
If I try to mount /bootdata directly with TWRP it fails. Even tried to create
the folder with Terminal.
Guidance is appreciated.
So I got boot Android to boot again. Created a bootable SD with TWRP v2.8.5.2.
Replaced the recovery.img in a v2.6.3.1 .ZIP file with v2.8.5.2 image.
Loaded the zip so TWRPv2.8.5.2 now loads from Internal Recovery.
CM12.1 and gapps install and load with this TWRP but it behaves poorly.
Lots of pauses and a few spontanious reboots.
Reloaded cm-11-20141112-SNAPSHOT-M12-acclaim.zip and gapps. Seems to run
cleanly.
Wish CM12.1 would behave.
Boot loop with Nook Tablet Acclaim 16gb
I tried installing the latest snapshot: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip
I used this gapps: open_gapps-arm-5.1-pico-20150923
This is the recovery: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim-recovery
I first downloaded and used the tablet to install this snapshot. Continuous boot loop.
Then I tried the usual manual mode erasing everything that needed it and still continuous boot loop ???
Is there something that I am doing wrong ??????
I had to revert to the previous snapshot and everything is back to normal.
HELP ?!?!?!?!?!?
nandroid123-
I copied http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.8.5.2-acclaim-sdcard.img over the recovery.img of my bootable sd.
Wiped/FactoryReset and installed CM with it. It fixed my no load of Android problem for both CM11 and CM12.1 but CM12.1 was not stable so I reverted to CM11 (cm-11-20141112-SNAPSHOT-M12-acclaim.zip).
I then installed http://techerrata.com/file/twrp2/acclaim/openrecovery-twrp-2.8.5.2-acclaim.img internally.
Boot looping
So no resolution for the boot looping on this latest snapshot !??!?!?!
nandroid123 said:
So no resolution for the boot looping on this latest snapshot !??!?!?!
Click to expand...
Click to collapse
Is your device boot loop to recovery? If so, see http://forum.xda-developers.com/showthread.php?p=21381141#post21381141 for potential cause and solution.
Digimax my 16gb Acclaim will boot loop when this: "" cm-12.1-20151117-SNAPSHOT-YOG7DAO1K6-acclaim.zip "" is installed.
When I revert back to the previous snapshot it works normally ??????
I will check out your link.
Thanks
Dennis
ETM said:
CM12.1 booted but ran very poorly. Tried various things. Each time I installed
there was a message when exiting CWM "Root access possibly lost. Fix?".
At first I responded no, then finally Yes. Since them Android won't boot.
It always boots to recovery now.
...
Installed TWRP 2.6.3.1 and tried to install various versions of CM.
During the install I get error messages, Unable to mount '/bootdata'.
If I try to mount /bootdata directly with TWRP it fails. Even tried to create
the folder with Terminal.
Click to expand...
Click to collapse
So here is the trick, I actually needed both.
Start with TWRP (SD version) to cleanup the system for clean install, etc...
Then, boot CWM, use its menu system to remount the bootdata partition <-- I think there was a typo thats tripping things up there
Then, boot with TWRP again, and get your installs in.
You can load a copy of Superuser from the SD while you're in there to be certain its rooted.
Related
So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Do I need to manually flash the boot.img file or should I only need to transfer the zip to my phone and install after wiping/doing a factory reset?
Well, that didn't work either as the zip file failed completely during install. So I downloaded the latest "stable" version just for giggles and wiped everything again and did an install. Just like before, the install was successful and on reboot it locks up on the boot screen. I am at a loss on what to do.
Hey buddy, i had cm10 running on my HOX, when i did it i had to flash the boot img through fastboot as well.
I found a tutorial on youtube by cursed forever helpful, sorry I'd post a link but my thread counts not high enough yet
My TMo springboard became almost useless, so - with TWRP installed - I decided to reformat system, data and cache, in the hope that the external SD would suffice to boot out of or mount a new image. No go.
I am now stuck in a loop, as follows:
- Huawei main logo
- Original lock screen
- slide to unlock
- message: "encryption unsuccessful... Data on your tablet no longer available... To resume using your tablet you must performance à factory reset...", which I opt for (choice named "reset tablet")
- Huawei mediapad logo
- teamwin splash screen
- TWRP trying to mount all sorts, but fails on all, of course
- back to Huawei mediapad
- back to Huawei main logo... and repeat all of the above
Any way I could break this cycle, by making an image available to TWRP? How? I don't seem to be able to use any touch screen or buttons to stop and a better change the options of TWRP. It just keeps trying to mount the default assumed partitions, nowhere to be found...
Sent from my SGH-T999 using Tapatalk 2
netfortius said:
My TMo springboard became almost useless, so - with TWRP installed - I decided to reformat system, data and cache, in the hope that the external SD would suffice to boot out of or mount a new image. No go.
I am now stuck in a loop, as follows:
- Huawei main logo
- Original lock screen
- slide to unlock
- message: "encryption unsuccessful... Data on your tablet no longer available... To resume using your tablet you must performance à factory reset...", which I opt for (choice named "reset tablet")
- Huawei mediapad logo
- teamwin splash screen
- TWRP trying to mount all sorts, but fails on all, of course
- back to Huawei mediapad
- back to Huawei main logo... and repeat all of the above
Any way I could break this cycle, by making an image available to TWRP? How? I don't seem to be able to use any touch screen or buttons to stop and a better change the options of TWRP. It just keeps trying to mount the default assumed partitions, nowhere to be found...
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you have TWRP installed you can simply download one ROM (CM10, CM10.1 or AOKP) in zip format and flash it from TWRP.
Just follow instructions on the DEV board.
GuZuRa said:
If you have TWRP installed you can simply download one ROM (CM10, CM10.1 or AOKP) in zip format and flash it from TWRP.
Just follow instructions on the DEV board.
Click to expand...
Click to collapse
Thank you. This is what I was hoping to hear
Would that work with an image from the external SD card (i.e. would the TWRP "see" the SD card and search for the zip file on it)? I am asking vs just trying it, because I only have one microSD, which is presently in my SGIII, so I thought of checking this before I start backing up my SD, clean it up, getting the CM 10.1, putting it on ... )
Thx again!
netfortius said:
Thank you. This is what I was hoping to hear
Would that work with an image from the external SD card (i.e. would the TWRP "see" the SD card and search for the zip file on it)? I am asking vs just trying it, because I only have one microSD, which is presently in my SGIII, so I thought of checking this before I start backing up my SD, clean it up, getting the CM 10.1, putting it on ... )
Thx again!
Click to expand...
Click to collapse
Replying to myself - I did copy the zip file to the microSD, but TWRP keeps trying to mount - at least apparently, to me - only the "known" partition (/data), then just fails and the mediapad goes back into reboot. Is there a sequence of keys that force TWRP to stop, and point it to the microSD, instead?!?
Any pointers will be appreciated.
R: Springboard w/out system or data
netfortius said:
Replying to myself - I did copy the zip file to the microSD, but TWRP keeps trying to mount - at least apparently, to me - only the "known" partition (/data), then just fails and the mediapad goes back into reboot. Is there a sequence of keys that force TWRP to stop, and point it to the microSD, instead?!?
Any pointers will be appreciated.
Click to expand...
Click to collapse
Try this:
1 reinstall TWRP with after_silence automated installer (shouldn't be necessary but... who knows?)
2 turn completety off MP by pressing on/off switch for a while (MP will shortly vibrate and turn off)
3 format a microsd in fat32 with a PC windows or linux
4 put the zip file of one of the ROM in dev board on the SD through the PC
5 insert microsd into MP
6 boot into TWRP. From device turned off, turn it on pressing on/off switch and volume up and keep volume up pressed until you see TWRP logo
7 reinstall Rom following instructions in the Dev board
Let me know....
Inviato dal mio Huawei MediaPad con Tapatalk 2
GuZuRa said:
Try this:
1 reinstall TWRP with after_silence automated installer
<snip>
Click to expand...
Click to collapse
Thank you for the reply. I pretty much already did all the steps you previously posted, except for "1." (reinstalling TWRP). I did a search for after_silence automated installer, but could not find any links to such - could you, please, post one?
Thx...
netfortius said:
Thank you for the reply. I pretty much already did all the steps you previously posted, except for "1." (reinstalling TWRP). I did a search for after_silence automated installer, but could not find any links to such - could you, please, post one?
Thx...
Click to expand...
Click to collapse
And I just noticed that TWRP continues running OpenRecoveryScript every time, which ends up trying to mount /data (unsuccessfully), wiping cache, reformating ext4fs, end then rebooting ...
netfortius said:
And I just noticed that TWRP continues running OpenRecoveryScript every time, which ends up trying to mount /data (unsuccessfully), wiping cache, reformating ext4fs, end then rebooting ...
Click to expand...
Click to collapse
One more update - I was able to get the system enough to run a:
$ fastboot flash system system.img.ext4
which worked just fine, but upon reboot TWRP takes over and starts again ... mount /data ... failure ... reformatting ...
Any ideas here on how to break this cycle?
huawei boot loop, fastboot mia
I followed the after silence cm install steps but failed at using fastboot to install the twrp image
adb connects fine & triggers a reboot into fastboot, then fastboot can't communicate so I installed the twrp recovery via goomanager
booted into twrp, made a backup, wiped system / cache / data (oops?)
tried to install cm10.1 and it said error in file
tried to reboot into recovery and now stuck on huawei logo, fastboot still kaput
anybody know why fastboot won't communicate or what I can try next???
update:
got back into twrp by holding power and vol up buttons until it reset, then releasing power while continuing to hold vol up
it appeared to loop several times then booted into twrp
Formatting the data partition was the culprit, methinks. I managed that, too.
You need to flash the third bootimg from After Silence´s Toolkit, not CWM and not TWRP. Then you can flash stock roms via a dload folder on the sdcard. Reflashing the already installed Comec v2 lite caused the aforementioned encryption error and before ending with an unrooted stock rom i tried CleanICE v1.5. Worked. Whether this rom is buggy or there just went something wrong during install, it didn´t contain the system app "networklocation.apk", so no wifi or 3g based localization would work, only gps, which is unavailable in my home. So i installed TWRP again and could successfully flash AOKP. Flashing AOKP directly after bricking wouldn´t fix the brick.
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.
So, I was able to successfully unlock my bootloader, got TWRP 2.6 on it, and put a few different ROMs on my machine; however, I have yet been able to install a ROM and get it to move past the boot animation.
I have tried the latest nightly ROMs for CyanogenMod 10.1 and 10.2 for my TF201, both of which get stuck in CM's boot animation. I just tried the same with the newest Baked ROM, only to be stuck in its boot animation as well.
I'm trying to figure out if there was something I forgot to do. I have been able to revert to a backup of my stock Jellybean 4.1.1 that I stored using TWRP, but haven't been able to use anything else.
Are there any thoughts on this? Have I missed something? I was able to use the unlocker utility and each boot offers the confirmation in the top-left that my bootloader is unlocked. I am able to enter TWRP from the recovery mode. Shouldn't it be as simple as selecting a ROM's zip archive and installing it from TWRP?
Have you done a full wipe before installing, including cache and dalvik cache partitions?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Try installing twrp 2.5. AS I just read in another thread there are problems with 2.6..
Sent from my MB526 using xda app-developers app
Factory reset
After flashing CM 10.1 nightly last night i had the same issue. I booted into my recovery console (flatline cwm) and performed a factory reset. This seemed to clear whatever issue was bothering the tablet. Still sat there for about five minutes on the animation after the reset but then progressed into setup.
Doubt if it makes a difference but mine was connected to the dock too.
If you're still stuck the method that worked for me yesterday was:
Used Flatline CWM as the recovery, installed using fastboot
Used an external memory card to copy the relevant zip files to my sdcard, recovery couldnt find them otherwise using adb push
Installed from zip using Flatline CWM
Installed gapps using Flatline CWM
Booted, got the issue you had
Booted into recovery, performed a factory reset
Told recovery to restart the machine
Booted into setup screen after loading for a few minutes
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!