Related
Quick update of both internal and external SD supporting recoveries to v5.0.2.8
Both .img files in one package: http://www.mediafire.com/file/0auipyswgqdsiah/cwm-5.0.2.8.zip
MD5#: 4f93fab2e4e51ecdb40acc11c9a4ba99
By request a quick explanation of the difference between the two recoveries:
Usually, your recovery image will look on the external SD card for ROMs to flash, and backups to restore, and the external version here is no different. For the most part that is fine and dandy (unless you don't have an SD card I guess), however the stock O2X mounts it's internal SD card as /sdcard, which confuses ROM Manager a fair bit.
The internal version of the recovery mounts the internal storage as /sdcard as well, so ROM Manager can find backups it's made etc.
NOTE: Backups made with v5 are not compatible with earlier versions.
Source Changelog (Built 24/03/12): https://github.com/CyanogenMod/android_bootable_recovery/commits/gingerbread/
Changes by Me
None this time, as I doubt anyone uses SD-EXT or cares about the splash
Older versions:
5.0.2.7
5.0.2.6
5.0.2.3
4.0.1.5
4.0.1.4 R3
The rest: http://www.mediafire.com/?gtj2fms2edid5
All credits to Koush for a hell of a lot of hard work.
Rusty! said:
Was bored, so thought I'd be productive. Here is a build of CWM recovery that uses the internal SD card rather than the external. If you're on a stock based ROM, then this will let ROM Manager interact with the recovery properly.
http://www.multiupload.com/G8I1HD82G6
Click to expand...
Click to collapse
Coool, just what I needed.
Still havn't found time to buy a good sd-card yet
How to enter recovery?
Same as ever, ROM Manager's reboot recovery or hold power and vol- 'til you see ANDROID on the screen.
Ah thanks for your work m8 i'm no stock again and this is handy! i'll send it to my phone when i'm at home.
Hahahha, true.
Tought it will pop-up in 1 sec, but took a while
m8,this was already posted by developer...
vivmar said:
m8,this was already posted by developer...
Click to expand...
Click to collapse
This is the new version of CMW supporting internal sd
Does the usb mount work?
With external sd if something goes wrong you can take out the sd, copy the rom or kernel you want and then put it back in to flash it, you can't do that with internal memory
xmoo said:
This is the new version of CMW supporting internal sd
Click to expand...
Click to collapse
support internal and also external sd?
vivmar said:
support internal and also external sd?
Click to expand...
Click to collapse
Dunno havn't tried yet. But Internal yes, don't know also external.
Rusty! said:
Same as ever, ROM Manager's reboot recovery or hold power and vol- 'til you see ANDROID on the screen.
Click to expand...
Click to collapse
heh... i have not 'ANDROID' on the screen, like it was at 3.0.2.8, only 'LG' on screen again with little background...
vivmar said:
support internal and also external sd?
Click to expand...
Click to collapse
Only internal, I've just tried mounting external to _ExternalSD, but it wont browse it. I'm probably doing something wrong though heh
In the event of a horrible disaster, you'd have to NVFLash the external SD CWM I guess.
does this recovery wipe the internal sd card when flashing a new rom and when a wipe is needed.
sorry 4 my english
Nope, only /data like the external version.
ok sorry, but i'm a noob n english not in android. but how can i undersand only /data. on ly the system gets killed? all my datas like pictures and gameloft games ..... won't be deleted. i want to flash a recovery, but also i heard that the recovery will delet the whole internal sd card.
ok i have to say it i herad it from the first recovery for the 2x.
/data is where all things like apps, email, texts etc and are stored, this is what's wiped during a factory reset.
I've never used the stock recoveries wipe, so I don't know if that blitzes the internal SD card, but Clockwork doesn't.
ok thanks than let's flash.
i only have to run install-clockworkmod-windows.cmd? in other recoverys it is .bat.
.cmd is the same as .bat
Updated to fix a couple of bugs.
Updated to include both internal & external builds and move to version 3.2.0.1
Hi
I am thinking to swtich to TWRP and I have some past CWM backup. So I want to make sure that I can use my past backups with the new manager.
thanks
I don't think it works like that
But you can use titanium backup and backup every thing there
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
hajkan said:
Hi
I am thinking to swtich to TWRP and I have some past CWM backup. So I want to make sure that I can use my past backups with the new manager.
thanks
Click to expand...
Click to collapse
They are definitely NOT compatible. You cannot use your CWM backups with TWRP, unfortunately. You could, however, flash your recovery back to CWM when needed. It's not like going to TWRP is one-way, with no way back to CWM.
go twrp all the way. why would you want old backups? just create new one to be safe with twrp after you flash recovery.
hajkan said:
Hi
I am thinking to swtich to TWRP and I have some past CWM backup. So I want to make sure that I can use my past backups with the new manager.
thanks
Click to expand...
Click to collapse
Nope...each are only compatible with its files. Why are you moving to TWRP...just curious?
Kinda related ...
Is it possible to have CWM as the recovery boot option **and** TWRP as the alternate recovery boot option? I think I could rename a few files uRecImg and uAltImg (or similar) on my nook Color, but I have yet to see something similar for the HD+.
Thanks in advance!
-SUO
SUOrangeman said:
Is it possible to have CWM as the recovery boot option **and** TWRP as the alternate recovery boot option? I think I could rename a few files uRecImg and uAltImg (or similar) on my nook Color, but I have yet to see something similar for the HD+.
Thanks in advance!
-SUO
Click to expand...
Click to collapse
No, it does not work that way on the HD/HD+. You must choose one or the other.
Sent from my Nook HD+ running CM10.1 on emmc.
the answer
Hi ive found out how to do it as I had same prob. Its an apk called nandroid manager.. just play with setting an add twrp or cwm as a source folder and you can restore like that..
Reason for Choosing TWRP
dvschnk said:
Nope...each are only compatible with its files. Why are you moving to TWRP...just curious?
Click to expand...
Click to collapse
I would like to respond, i have tried all variants of CWM available for my Xolo Q700, and TWRP i would choose only because it gives you an option to see how much space you actually need on the SD card and how much you have.
with CWM the availabel space in storage is shown but after waiting 10-15minutes for all data to be backed up, you end up getting an error message 2.5GB of free space wasnt enough. it tries to save each data file one by one and after all space is taken up, it fails
please correct me if there is an update to CWM which attends to this issue.
being a newbie to rooted phone flashing (i started playing around just about an year back and i am now in a position to root, unroot or unbrick few phones....)
other than that, i would like to choose cwm because i see more development there than TWRP...
and CTR v2.4 though it uses CWM 6.0.4 , an older version, seems to be good with full touch control and optional aroma file manager...
rajeshontheweb said:
I would like to respond, i have tried all variants of CWM available for my Xolo Q700, and TWRP i would choose only because it gives you an option to see how much space you actually need on the SD card and how much you have.
with CWM the availabel space in storage is shown but after waiting 10-15minutes for all data to be backed up, you end up getting an error message 2.5GB of free space wasnt enough. it tries to save each data file one by one and after all space is taken up, it fails
please correct me if there is an update to CWM which attends to this issue.
Click to expand...
Click to collapse
Each device is different and requires different amounts of space to back up the device. Also it depends on how many apps you have installed. It could be that 2.5GB was not enough for your Xolo.
Both TWRP and CWM save the data files one by one, but both also compress them into archive files for each partition. The only difference between the two is TWRP predicts how much space is needed and CWM does not. I don't think there are any plans to change that.
Sent from my BN NookHD+ using XDA Premium HD app
After installing Semaphore's ClockworkMod Recovery via Heimdall Suite my i9000 do not boot. It show the splash samsung-logo, than the screen switch to black an after 2-3 seconds the splash-logo will be showed.
I can turn on the Semaphore CWM Recovery and I could (I hope so) flash a new CyanogenMod or so BUT! But i need the data from my cellphone.
Questions:
It's possible to access in Semaphore CWM Recovery mode the data to copy them to PC via USB or to external SD-Card?
It's possible to make a backup to external SD-Card? How to mount the external card?
It's possible to flash a new zImage (like the original one) to boot normally? Where I can get this image? Heimdall works still properly.
What i can do to rescue my data.
Thank You,
MiniX1
don't worry, you won't loss anything on your sdcard when flashing new custom rom, but you will loss apps that you've already installed.
pryerlee said:
don't worry, you won't loss anything on your sdcard when flashing new custom rom, but you will loss apps that you've already installed.
Click to expand...
Click to collapse
Its sounds good!
what I need is:
a) my key of my Bitcoin-Wallet with about 1 BTC
b) what about my sms?
c) what about my What's up messages?
everything else can be restored.
MiniX1
ok read this thread http://forum.xda-developers.com/showthread.php?t=2208825
pryerlee said:
ok read this thread http://forum.xda-developers.com/showthread.php?t=2208825
Click to expand...
Click to collapse
beating around the bush mate not wise to use nandroid backup as more work involved. , just use cwm to mount USB storage and you can copy the entire SD card contents to PC or whatever yu need or move to ext SD card.
Hi there,
i'm having huge problems getting my HD+ fixed.
what happened: shut down out of nowhere, didnt boot the ROM, just TWRP recovery loops. Flashing and wiping did nothing good to the device. I always got errors when trying to install zips (data1 not found or something like this), but somehow the installation of CWM worked.
At the moment: CWM 6.0.4.5, when booting into recovery, under mounts/storage it says that system, data rom and bootdata arent mounted (but i can mount them from there).
trying to flash a new ROM or other zips doesnt work: Status 7.
I've read several threads over here, but I'm still confused and dont know how to save my HD+. Which exact files should i flash in which order? How to get rid of status 7?
Thank you so much.
Greetings
Richy
ohrenstaebchen said:
Hi there,
i'm having huge problems getting my HD+ fixed.
what happened: shut down out of nowhere, didnt boot the ROM, just TWRP recovery loops. Flashing and wiping did nothing good to the device. I always got errors when trying to install zips (data1 not found or something like this), but somehow the installation of CWM worked.
At the moment: CWM 6.0.4.5, when booting into recovery, under mounts/storage it says that system, data rom and bootdata arent mounted (but i can mount them from there).
trying to flash a new ROM or other zips doesnt work: Status 7.
I've read several threads over here, but I'm still confused and dont know how to save my HD+. Which exact files should i flash in which order? How to get rid of status 7?
Thank you so much.
Greetings
Richy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2062613
Go to section 6 and restore to stock.
ohrenstaebchen said:
Hi there,
i'm having huge problems getting my HD+ fixed.
what happened: shut down out of nowhere, didnt boot the ROM, just TWRP recovery loops. Flashing and wiping did nothing good to the device. I always got errors when trying to install zips (data1 not found or something like this), but somehow the installation of CWM worked.
At the moment: CWM 6.0.4.5, when booting into recovery, under mounts/storage it says that system, data rom and bootdata arent mounted (but i can mount them from there).
trying to flash a new ROM or other zips doesnt work: Status 7.
I've read several threads over here, but I'm still confused and dont know how to save my HD+. Which exact files should i flash in which order? How to get rid of status 7?
Thank you so much.
Greetings
Richy
Click to expand...
Click to collapse
That v6045 of CWM is causing the status 7 errors. You need an older version for older zips. Go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a. Then you can flash whatever you want, including that plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Hi,
thanks for your answers.
I made a CWM SD as described. I put it into my HD+. But how do I avoid my Nook booting into the already-installed emmc-6.0.4.5? I rebooted it several times and always landed in the 6.0.4.5, so I assume i'm not in the SD-CWM which i desperately need. I also pushed "NookHDplus-CWM-6036-for-internal-memory-rev1-(09.22.13).zip" to the internal memory and tried to flash this, but no chance - status 7.
As I see it, the problem is to get into the older CWM-SD because the 6.0.4.5 won't let me install earlier CWMs (status 7)?
ohrenstaebchen said:
Hi,
thanks for your answers.
I made a CWM SD as described. I put it into my HD+. But how do I avoid my Nook booting into the already-installed emmc-6.0.4.5? I rebooted it several times and always landed in the 6.0.4.5, so I assume i'm not in the SD-CWM which i desperately need. I also pushed "NookHDplus-CWM-6036-for-internal-memory-rev1-(09.22.13).zip" to the internal memory and tried to flash this, but no chance - status 7.
As I see it, the problem is to get into the older CWM-SD because the 6.0.4.5 won't let me install earlier CWMs (status 7)?
Click to expand...
Click to collapse
Can you boot 11? I have found my new nook won't boot from the SDcard unless I boot unmount the old card and mount the new one before booting.
Seems as if i have the problem lots of other users have encountered: http://forum.xda-developers.com/showthread.php?t=2288688&page=6
When I installed CWM/CM the first time, I didnt have any problem with this, using the exact same hardware. Is it even possible to boot right from SD with my emmc-installed 6045, or is it just bad luck like those other guys in the thread mentioned?
Sideload doesnt work neither, CWM 6045 tells me to begin sideloading, but ADB gives me the whole "help"-listing instead (as if I used a wrong command or something: adb sideload filename.zip) of a working sideload-process. When I start sideload in CWM, "adb devices" gives me "host", dont know if this is good.
jpisini said:
Can you boot 11? I have found my new nook won't boot from the SDcard unless I boot unmount the old card and mount the new one before booting.
Click to expand...
Click to collapse
You mean I should try to boot CM11 from SDcard (i assume i end up with the same problem that the Nook doesnt want to boot from SD-CWM)? Where should I unmount the card? I dont think i'm getting your idea
Thank you!
ohrenstaebchen said:
Seems as if i have the problem lots of other users have encountered: http://forum.xda-developers.com/showthread.php?t=2288688&page=6
When I installed CWM/CM the first time, I didnt have any problem with this, using the exact same hardware. Is it even possible to boot right from SD with my emmc-installed 6045, or is it just bad luck like those other guys in the thread mentioned?
Sideload doesnt work neither, CWM 6045 tells me to begin sideloading, but ADB gives me the whole "help"-listing instead (as if I used a wrong command or something: adb sideload filename.zip) of a working sideload-process. When I start sideload in CWM, "adb devices" gives me "host", dont know if this is good.
You mean I should try to boot CM11 from SDcard (i assume i end up with the same problem that the Nook doesnt want to boot from SD-CWM)? Where should I unmount the card? I dont think i'm getting your idea
Thank you!
Click to expand...
Click to collapse
On my new replacement Nook I can't boot to any SDcards no matter if they are CWM or CM unless I boot into a working OS unmount the card I have in there eject it and put another one in while still booted then do a reboot it then boots every time off the new card.
Now the stock OS is installed. But I have problems getting into the SD-CWM. At the moment, it doesnt boot at all when the SD card is my Nook. Very strange behaviour.
I don't have a second SD-card, so I can't try that.
ohrenstaebchen said:
Now the stock OS is installed. But I have problems getting into the SD-CWM. At the moment, it doesnt boot at all when the SD card is my Nook. Very strange behaviour.
I don't have a second SD-card, so I can't try that.
Click to expand...
Click to collapse
My Nook has Version 2.2 of B&N Software. I have to restore the Nook to get it to boot from SD Card. I am new so I am having issues finding the right combination of files to install the nightly build of CM11 without getting a status 7. There are so many builders and files on this forum and everything I have tested so far has been a no go. Can someone give me a specific set of files that will work with the nightly build of CM 11? It would be greatly appreciated!
Create a bootable SD card: http://forum.xda-developers.com/showthread.php?t=2062613
- format SD card with SDFormatter
- set the only partition to "active" with MiniTool Partition Wizard
- "flash"/"burn" a bootable-CWM-image, for me it OINLY worked with "NookHDplus-bootable-CWM-6028-for-stock-small-rev4-(05.15.13).zip" (boots every time to SD-CWM, using the 4GB-version didnt work even after 30+ trys
- add your CM11-zip to the SD card using your windows explorer
- add flash_recovery_ovation_CWM_6.0.4.5b_internal.zip from http://goo.im/devs/succulent/ovation/recovery
- put it in your Nook, boot it up, if you're lucky you see CWM
- flash the 6.0.4.5b CWM, then you're ready to flash the newest CM11. If you want to flash an older version of CM such as 10.1 or 10.2, you need a lower CWM version to avoid status 7 errors.
- flash CM11
That was my way to CM11, but there is one huge problem at the moment: CM won't boot, it loops the CM-bootlogo infinitely. several wipes did nothing, still looping. My CWM always says on bootup that /system/ (besides others) isnt mounted, but I can mount them without a problem, flashing the CM-ROM doesnt produce errors.
I don't know how to avoid the CM bootlogo-loop
Had to reboot about 8 times to get my nook to read 32 gig SD card.
leapinlar said:
That v6045 of CWM is causing the status 7 errors. You need an older version for older zips. Go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a. Then you can flash whatever you want, including that plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I had to reboot my nook at least 8 times to get it to read my SD card so I could install succulents 07FEB2014, using TWRP, because I was getting error 7 when installing via CWM.6.0.26 If I had known better, I would have copied the 07FEB2014 (stable) build to my internal memory and installed with TWRP from there. I somehow got into a loop where I could only boot into TWRP, finally being able to install seemed to fix this. I am loving the 07FEB2014 build. Keep up the good work gentle men and women! I really love this build.
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
-UPDATE:
Here are three solutions for updating:
a) The downloaded .zip file has to be moved to /data (if wanted, into some subfolder of your choice. ES-File Explorer needs root for that) Then flash via TWRP.
b) Use flashify, choose copy to safe location (had some FC's afterwards)
c) Use cm-recovery, update via cm-updater (not yet confirmed)
davedophin said:
Hi folks, maybe someone encounters the same problem. I installed CM13 02/12 along with opengapps, which worked fine.
I then decided to use my SD Card as internal, which also worked like a charm.
But when I tried to update, TWRP can't see the contents of the SD-Card.
So I flashed Philz, and flashed the new build via sideload (should be possible with TWRP as well). That resulted in a phone, which wont boot up and is stuck in the bootlogo.
I then flashed Rom and Gapps via sideload, the phone boots up, but Setup Wizard App (I think its called that in English) keeps on crashing, rendering the phone unusable.
(I then erased internal storage, messing up everything, and returned to CM12)
So here are the questions:
1. Did anyone succesfully update his phone, while having activated the storage merging option?
2. Does anyone know, how to stop Setup Wizard from closing? (I think, I read somewhere it is because of missing rights and that you can fiddle with some "packages.xml" to fix that)
Thanks guys!
Click to expand...
Click to collapse
1. I don't think so. For this we should need an updated recovery supporting this feature. Furthermore, the feature is not fully ready, imho
2. I don't know. Never had this problem.
Written with my XT1068 using Tapatalk on CM13
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Dieselhorst said:
Using SD card as internal storage in Marshmallow repartitions it with ext4 filesystem and encrypts it. A recovery needs to handle both support for ext4 and decrypting the files on it - which should be impossible without the correct key.
Currently you should use SD as portable/external to keep unencrypted fat file system.
Gesendet von meinem XT1068 mit Tapatalk
Click to expand...
Click to collapse
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Mavireck said:
The first part is true.
But I don't agree for the second part. This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Flashify CAN flash when during the process you choose "use provided path".
Why ? Because it stores the ROM on the data partition and with a custom script it allows the recovery to mount the data partition and the flash the ROM.
Click to expand...
Click to collapse
I believe you when you say Flashify can flash the rom. But as said, it's all way to complicated for the 'average' user. Especially because of the encryption, which causes the sd card to be unseen by, for example, your recovery or your pc. These things have to be solved first!
Written with my XT1068 using Tapatalk on CM13
Sure, that's why I say
This new option is great as long as you know how to use it and how not to loose all your data when changing ROM.
Click to expand...
Click to collapse
.
I think we should stop debate now because we think the same
Mavireck said:
On my moto g 2014 LTE (thea) with cm13 I can flash nightlies using the app Flashify even after formatting SD card as internal.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
For your other question I don't know.
Click to expand...
Click to collapse
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
davedophin said:
Hey Mavireck, thank you for that info, I will try Flashify soon! Did you flash the ROM only or ROM + GAPPS?
And I understand that there are different opinions, but for me, merging internal storage is kind of a "key" feature for substituting Link2SD. I'm hoping to see some kind of recovery, which can decrypt the SD card in the near future (or the possibilty to choose not to use encryption)!
Click to expand...
Click to collapse
The twrp team is awesome. They will find a fix.
I only tried flashing the ROM but i think you can flash at the same time gapps.
Alright, Flashify works, if you pick the option "copy to safe directory" or similar. "use provided path" doesnt work for me.
But after the update, Nova Launcher keeps crashing and titanium backup doesnt show up on the app drawer anymore, but is still installed and cant be uninstalled to reinstall. pretty weird. So for me, this option doesnt really work either.
I copy the update zip file to \Data\Media\0\twrp and i can update
Anyone knows if the SuperSU 2.60 works in the CM13 Moto G2014???
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
bhachech said:
@Poeta, I copy the zip to /data/fota which I think is a slightly more appropriate choice (fota= firmware over the air, which is exactly what this process is)... But regardless of the location, the point is to use /data partition (which is accessible from both within marshmallow os and recovery) instead of internal storage or sd card.
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I haven't used TB or Nova... CM 13 on Titan is running very well for me. As expected, in these early nightlies, some CM features are not fully implemented but that has not hindered my ability to use it as a daily driver for the past couple of weeks.
davedophin said:
Okay, so copying the files to flash on the /data partition is the key, will try that. How does your updated Android behave performancewise? Any troubles with apps like titanium backup or nova launcher (if used).
Click to expand...
Click to collapse
I use Nova and TB, no problems here
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
ygtenos said:
Hey everyone. I have a question for whomever formatted the SD as internal.
First of all, yes, it's a little buggy, but I find it extremely useful, hats off to Google!
Then, I've been having this weird problem where if I try to reboot the phone with the SD card inserted it would go into a bootloop. I usually reboot into bootloader, remove the SD card, reboot again and put in the SD card after android has fully launched.
Anyone having the same problem?
I'm using the 14/11 version of the rom (goodness. I'm outdated!) and my SD card is pretty much brand new. A 32gb sandisk class 10 U3.
Thanks in advance!
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
I've tried like 4 releases of CM13 so far, never had a problem like that. But I only used builds from december, so I would suggest you go for a newer version, after a backup of course
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
So guys, I updated to todays build by moving it to the /data partition and then using twrp. Works like a charm! Thanks everyone for your help!
davedophin said:
Heres something else I found at the CM13 thread I wanted to share with you:
Also, keep in mind that this problem might be isolated to TWRP. @LuK1337 informed me that if you:
Use CMUpdater to download ROM
Let CMUpdater "Reboot and Install" ROM directly
and have CM recovery installed
... then it works flawlessly. I have yet to try it (since no new nightlies have come out since I learned of this approach.)
Click to expand...
Click to collapse
Does not work for me (Moto Thea)