Related
Alright, now I know this question has almost certainly been asked before, but before you start raging at me, I have spent a good few hours looking around on here and other places, but I haven't found all of the information I'd like. Also, I find that people giving you their personal experience directly is more helpful anyway.
So, I got given a G1 the other day, and immediately started thinking about modding and rooting it, etc. The stock 1.6 was alright, but it wasn't too snappy and I wanted to try out different versions anyway. So I went ahead and:
Rooted my phone
Installed Amon_Ra's Recovery Image v.1.7.0
Flashed the radio to 2.22.19.26i
Installed DangerSPL
After I'd done all that, I went ahead and installed CyanogenMod 5, to try out 2.1 first. It seemed OK, but it was definitely slower than 1.6 by a fair amount. I then flashed to CM 6 and found it to be quicker, but still too slow for my liking. So I flashed to CM 4 instead, which was definitely more like it. I don't actually find myself missing many features from Android 2.0+ if I'm honest, but the OS STILL isn't as fast as I'd like. I know I can get it quicker.
I've removed all of the apps that I don't use (including some of the Google ones - I forgot to mention that I installed Google Apps too) to help free up some of the internal memory. I have a Kingston 4GB class 4 microSDHC card, but I understand that running apps from the SD card is going to be slower than from the internal ROM, so I'd rather keep all the apps on there.
I bought SetCPU, but I can't figure out how to configure it properly. The maximum speed I can set the CPU to is 528MHz, which is stock speed.
I'm using the stock launcher (which seems to have inserted 5 home screens - I only need 3) because I don't know if ADW Launcher or LauncherPro will be quicker. I have a few widgets and shortcuts, but not a ton. I use Opera Mini for browsing as I found Opera Mobile to be too slow when scrolling about and so on, and the stock browser to be even slower.
So basically my question is this: what things have you guys done to speed up your G1?
One thing I should mention is that I'm fine with most of the features of 1.6, but obviously I will upgrade to a later version of Android if there is a ROM/configuration that will be nice and snappy.
Thanks in advance, and sorry for the very long post.
if you are italian, there is a rom called padronfroyo that i find it the fastest one!
netterharrison said:
if you are italian, there is a rom called padronfroyo that i find it the fastest one!
Click to expand...
Click to collapse
Thanks for the reply, unfortunately I am British though.
Try froyo by lazlo, very fast and stable rom.
Try overclocking to 576 mhz in the rom performance settings. Also, try tweaking the performance settings(compcache, jit, vm heap size, etc) until you find the fastest ones. I also use an app called cache cleaner to remove all the cache on my phone from the browser and such. I also use sdext to install apps on my sd and run them from there as well.Personally, I use adw ex because it has all the cool features and it is amazingly fast. I'm currently using cos-ds gingerbread and my phone is snappy as hell. But in your case try froyo by lazlo, in the g1 development forum.
Sent from my HTC Dream using XDA App
im using a donut rom with the latest radio and it flyyys
Thanks for the replies guys. I think I'll try Froyo by Lazlo first, but how would I go about switching? Nandroid will backup my current ROM right? And then I will need to backup my apps with Titanium Backup or similar, and my contacts, etc.
When I wipe the system using the recovery, which options do I use? Because I remember there are several options for what you can wipe, but I'm not sure which ones I need to use.
And then I can just go ahead and flash the ROM using "flash zip from SD card" or whatever the option is called?
EDIT: Oh, and what's this about the SPL and the radio? I have DangerSPL installed and the radio is 2.22.19.26i
ellisbodds said:
Thanks for the replies guys. I think I'll try Froyo by Lazlo first, but how would I go about switching? Nandroid will backup my current ROM right? And then I will need to backup my apps with Titanium Backup or similar, and my contacts, etc.
When I wipe the system using the recovery, which options do I use? Because I remember there are several options for what you can wipe, but I'm not sure which ones I need to use.
And then I can just go ahead and flash the ROM using "flash zip from SD card" or whatever the option is called?
EDIT: Oh, and what's this about the SPL and the radio? I have DangerSPL installed and the radio is 2.22.19.26i
Click to expand...
Click to collapse
you wont be able to flash froyo by lazslo on that radio.. you need 2.22.27.09/28.25 and hboot 1.33.0013d
and if you have your apps saves to the ext partition of your sd than nandroid will back it up, or just do a bart backup!
when you install a new rom you want to wipe all data!! ALL DATA!! lol wipe data, cache, dalvik cache, sd partition, etc.. be sure to repair sd also.
ldrifta said:
you wont be able to flash froyo by lazslo on that radio.. you need 2.22.27.09/28.25 and hboot 1.33.0013d
and if you have your apps saves to the ext partition of your sd than nandroid will back it up, or just do a bart backup!
when you install a new rom you want to wipe all data!! ALL DATA!! lol wipe data, cache, dalvik cache, sd partition, etc.. be sure to repair sd also.
Click to expand...
Click to collapse
OK. Well, I think everything's backed up now.
When I choose to wipe SD:ext partition though, will that wipe all the data on my SD or just the ext folder or something? What does the ext folder even contain?
Which radio would I need for a UK G1? Or how do I find out which one I need? And how do I flash the radio and hboot?
Thanks
ellisbodds said:
OK. Well, I think everything's backed up now.
When I choose to wipe SD:ext partition though, will that wipe all the data on my SD or just the ext folder or something? What does the ext folder even contain?
Which radio would I need for a UK G1? Or how do I find out which one I need? And how do I flash the radio and hboot?
Thanks
Click to expand...
Click to collapse
Best way to wipe for a clean install is using Ohsaka's Superwipe here Wiping sd:ext affects the ext partition only. If you are using appstoext, or magpie, you can store apps on ext.
The latest radio is 2825. Flashing radio and hboot is best done through fastboot,lower chances of bricking, much2 safer than flashing em through recovery. The guide on how to flash the radio and hboot is at my signature, try to read the instruction a few times and fully understand it before you start flashing, gluck!
Sent from my G1
azrash said:
Best way to wipe for a clean install is using Ohsaka's Superwipe here Wiping sd:ext affects the ext partition only. If you are using appstoext, or magpie, you can store apps on ext.
The latest radio is 2825. Flashing radio and hboot is best done through fastboot,lower chances of bricking, much2 safer than flashing em through recovery. The guide on how to flash the radio and hboot is at my signature, try to read the instruction a few times and fully understand it before you start flashing, gluck!
Sent from my G1
Click to expand...
Click to collapse
Excellent, thanks.
I still have a couple of questions though.
Do I need to flash the recovery image? The version in that thread is recovery-RA-dream-v1.7.0-cyan.img, and I think mine is the same (it's definitely v1.7.0) just without the "cyan" bit on the end.
I'm a bit confused as to what radio I need to use. I'm in the UK, using a UK G1, and I thought I needed a different radio to US users? Am I using this one?
New Alternative radio: RADIO-2.22.28.25.img
Click to expand...
Click to collapse
Or do I use 27.08?
How do I do this?
3) flash the files and other operations via fastboot
Click to expand...
Click to collapse
I can't find a console or anywhere to input the data when in fastboot. I'm currently using 1.33.2005.
Do I wipe everything before flashing the radio and hboot, or in between doing that and installing the new rom?
Cheers
EDIT: Oh, and Froyo by Laszlo says that I need an ext4 partition. Is this on my SD card or on the phone? And how do I create one? Thanks
ellisbodds said:
Excellent, thanks.
I still have a couple of questions though.
Do I need to flash the recovery image? The version in that thread is recovery-RA-dream-v1.7.0-cyan.img, and I think mine is the same (it's definitely v1.7.0) just without the "cyan" bit on the end.
Click to expand...
Click to collapse
yes you would still need to flash a recovery. the cyan bit at the end just denotes a cyan themed recovery, the exact same recovery but blue. you can flash the normal amonra 1.7 recovery
I'm a bit confused as to what radio I need to use. I'm in the UK, using a UK G1, and I thought I needed a different radio to US users? Am I using this one?
Or do I use 27.08?
Click to expand...
Click to collapse
use the 2825 radio, it is the latest and works everywhere. remember to follow the guide step by step, do not skip/change the steps, it must be done in order
How do I do this?
I can't find a console or anywhere to input the data when in fastboot. I'm currently using 1.33.2005.
Do I wipe everything before flashing the radio and hboot, or in between doing that and installing the new rom?
Click to expand...
Click to collapse
fastboot is done via PC from command prompt, check here for a guide on how to setup fastboot http://forum.xda-developers.com/showthread.php?t=532719
it might seem tedious and long but trust me, it is very useful, you will use it a lot. just do a superwipe after you have upgraded the whole radio+hboot thing. remember to power down first once you have superwiped
EDIT: Oh, and Froyo by Laszlo says that I need an ext4 partition. Is this on my SD card or on the phone? And how do I create one? Thanks
Click to expand...
Click to collapse
ext is in sd card. this is done in recovery, go to partition SD, enter your desired size(depending on your sd card size, 200mb for ext should be enough, im using an 8gb sd card, so i set my ext to 600mb) and once you have partitioned, just select upgrade ext2 to ext3 and then ext3 to ext4. partitioning will erase your entire sd card, so remember to copy the content to your PC first
hope it helps
azrash said:
yes you would still need to flash a recovery. the cyan bit at the end just denotes a cyan themed recovery, the exact same recovery but blue. you can flash the normal amonra 1.7 recovery
Click to expand...
Click to collapse
Even though I already have normal 1.7 installed I need to flash it again?
use the 2825 radio, it is the latest and works everywhere. remember to follow the guide step by step, do not skip/change the steps, it must be done in order
Click to expand...
Click to collapse
Gotcha
EDIT: The 28.25 radio is in a zip which contains the .img and a bunch of other stuff as well. Do I just need the img or do I need to dump the whole zip on my SD?
fastboot is done via PC from command prompt, check here for a guide on how to setup fastboot http://forum.xda-developers.com/showthread.php?t=532719
it might seem tedious and long but trust me, it is very useful, you will use it a lot.
Click to expand...
Click to collapse
EDIT: ADB and fastboot are now up and running on my system.
just do a superwipe after you have upgraded the whole radio+hboot thing. remember to power down first once you have superwiped
Click to expand...
Click to collapse
superwipe = go through all of the options and wipe all of them, I guess?
ext is in sd card. this is done in recovery, go to partition SD, enter your desired size(depending on your sd card size, 200mb for ext should be enough, im using an 8gb sd card, so i set my ext to 600mb) and once you have partitioned, just select upgrade ext2 to ext3 and then ext3 to ext4. partitioning will erase your entire sd card, so remember to copy the content to your PC first
Click to expand...
Click to collapse
So when would I do this then? After flashing the radio and SPL and before flashing the ROM, I would imagine?
EDIT: What size would you recommend for a 4GB card?
hope it helps
Click to expand...
Click to collapse
It did help, and you've been very helpful in all your posts. There's just so much I have to learn.
ellisbodds said:
Even though I already have normal 1.7 installed I need to flash it again?
Click to expand...
Click to collapse
No if you already have Amon Ra 1.7 recovery on your phone then you dont have to reflash it. But if you want to reflash it, it wont hurt to do so.
ellisbodds said:
Gotcha
EDIT: The 28.25 radio is in a zip which contains the .img and a bunch of other stuff as well. Do I just need the img or do I need to dump the whole zip on my SD?
Click to expand...
Click to collapse
No just the dump the whole zip file on to your sd card.
ellisbodds said:
EDIT: ADB and fastboot are now up and running on my system.
superwipe = go through all of the options and wipe all of them, I guess?
Click to expand...
Click to collapse
superwipe is this:http://forum.xda-developers.com/showthread.php?t=834812&highlight=superwipe
Download version two, and put the whole zip file onto your sd card. You would flash this through the "flash a zip file" option in recovery.
It allows you to wipe everything instantaneously. Make sure to make a Nandroid backup before you flash it though.
ellisbodds said:
So when would I do this then? After flashing the radio and SPL and before flashing the ROM, I would imagine?
Click to expand...
Click to collapse
Yes you are correct.
ellisbodds said:
EDIT: What size would you recommend for a 4GB card?
Click to expand...
Click to collapse
*Remember to backup your entire sd card to your computer because it will be entirely wiped out.
These are my recommended partiton sizes:
It's best if you dont get swap, i find it slow,but if you want swap you can repartition it later,so use this:
fat 32: 512 mb (place where apps are stored, should be plenty of room)
swap: 0 mb
then the rest of the memory is saved on to your ext 2 partition
After your done partitioning your sd card, you must upgrade to ext 4.
So, go to upgrade ext2 to ext 3, then once its done, go to upgrade ext3 to ext 4 and then there you are done! You have ext4 on your sd card!
*Dont forget to place all the files you backed up onto your computer back onto the sd card because you will need to flash superwipe next, and then your rom.
You can do this by plugging in your phone thru usb to your computer, then choose the option "usb-ms toggle" in recovery,and it will mount the sd card so you can place the files back onto your sd.
Thanks for the reply.
When I flash superwipe, does that actually activate it, or do I need to flash it and then go somewhere else to use it? Also, do I need to download SuperWipe.conf as well?
This is what I have now:
Flash radio + hboot
Backup SD card data
Partition SD card:
512MB FAT32
The rest as ext2->ext3->ext4 (no swap)
Boot into recovery
Place files back on SD card
Flash superwipe
Power down/restart
Flash froyo rom
Click to expand...
Click to collapse
Also, as for the radio, it says to enter these commands:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
So I guess I will just enter "flash radio update_2.22.28.25_S.zip" instead?
ellisbodds said:
Thanks for the reply.
When I flash superwipe, does that actually activate it, or do I need to flash it and then go somewhere else to use it? Also, do I need to download SuperWipe.conf as well?
Click to expand...
Click to collapse
When you flash Superwipe, it unzips the file, and does what it tells it to, which is wipe everything. So you dont need to go anywhere to activate it, when you flash it, you are activating it.
No, you dont need the Superwipe.conf. Thats only if you want to change the things Superwipe will wipe.
ellisbodds said:
This is what I have now:Flash radio + hboot
Backup SD card data
Partition SD card:
512MB FAT32
The rest as ext2->ext3->ext4 (no swap)
Boot into recovery
Place files back on SD card
Flash superwipe
Power down/restart
Flash froyo rom
Click to expand...
Click to collapse
You are partioning your sd card through recovery, so you wont need to reboot your phone after your partitioning your sd card just go ahead and place your backedup sd card files back onto ur sdcard.
NOTE:When you are done flashing superwipe, it will tell you to power off ur phone before proceding.So, power off your phone, and then manually power back on to recovery by pressing home + power button at the same time, hold them until phone boots on. Then you are back into recovery and you can flash the Rom.
ellisbodds said:
Also, as for the radio, it says to enter these commands:fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
So I guess I will just enter "flash radio update_2.22.28.25_S.zip" instead?
Click to expand...
Click to collapse
Yes, you are correct.
Awesome, wish me luck then!
ellisbodds said:
Awesome, wish me luck then!
Click to expand...
Click to collapse
Good Luck! Let me know how it goes. Have fun with your new rom!
OK, so I got as far as flashing the recovery image again, which worked fine, and then I tried to flash the new radio, which didn't work fine.
I try typing:
fastboot flash radio update_2.22.28.25_S.zip
Click to expand...
Click to collapse
but all I get is:
sending 'radio' (9440 KB)... OKAY
writing 'radio'... FAILED (remote: image update error)
Click to expand...
Click to collapse
And now I don't know what to do
ellisbodds said:
OK, so I got as far as flashing the recovery image again, which worked fine, and then I tried to flash the new radio, which didn't work fine.
I try typing:
but all I get is:
And now I don't know what to do
Click to expand...
Click to collapse
hmm i think its displaying that mesage because its looking to update from the 2708 radio.
My only guess is to try flashing the 2708 radio instead of the 2825 radio.
maximo360 said:
hmm i think its displaying that mesage because its looking to update from the 2708 radio.
My only guess is to try flashing the 2708 radio instead of the 2825 radio.
Click to expand...
Click to collapse
And that will work here in the UK and stuff?
If I'm honest, I don't actually know what the "radio" does, but I hear the word and immediately think of some little chip inside the phone which communicates with the mobile network.
EDIT: 2.22.27.08 flashed okay. Now to move on
Hi,
I was happily using my blue-dot NC with CM7 Nightly-177, as suddenly it started to boot ONLY to recovery (CWM 3.2.0.1).
I had used the NC, then put into a neoprene type cover, and put all in a soft bag, and carried it in the car and when I wanted to power the NC on, I was in recovery..
SDCard was intact, could read and copy the contents in my PC.
Tried everything including trying to install CM7 from the sdcard anew multiple times.
It boots from the sdcard, I wipe data, I wipe cache, I wipe dalvik cache, I find and install zip, I install gapps, everything goes OK.. I power down, take the sdcard out. I powerup.. I have the green logo, then the recovery...
What could I be doing wrong?
I'm really pissed off, and thanks for any help.
I wouldn't have wiped data. (I hope you have a backup.) Since it will boot into recovery off the eMMC, put a nightly on a non booting SD card and try again and only wipe Davlik. Normally when updating with ROM Manager that is all you need to wipe. You also might want to flash the gaaps .zip again if you find the market missing after you get back into CM7.
Seemed like you flashed ROM manager into eMMC.
patruns said:
I wouldn't have wiped data. (I hope you have a backup.) Since it will boot into recovery off the eMMC, put a nightly on a non booting SD card and try again and only wipe Davlik. Normally when updating with ROM Manager that is all you need to wipe. You also might want to flash the gaaps .zip again if you find the market missing after you get back into CM7.
Click to expand...
Click to collapse
Well, I had asked the same question at androidtablets.net, few days ago, and I was told do take this route, wiping the data and all.
BTW, I have a backup yes..
votinh said:
Seemed like you flashed ROM manager into eMMC.
Click to expand...
Click to collapse
So? How do I use this comment to help my problem?
velizet said:
So? How do I use this comment to help my problem?
Click to expand...
Click to collapse
Did you try what I suggested in the 2nd post?
patruns said:
Did you try what I suggested in the 2nd post?
Click to expand...
Click to collapse
Yes, multiple times with different zips..
It is always, the green Cyanogen logo, says loading, a little flicker, and the amber menu..
That is very odd. Possibly you have a corrupted image on your card. Have you tried creating the bootable image all over again?
Dumb question..... is it fully charged?
patruns said:
That is very odd. Possibly you have a corrupted image on your card. Have you tried creating the bootable image all over again?
Dumb question..... is it fully charged?
Click to expand...
Click to collapse
It is even on the mains.
I have tried creating the bootable drive more than once. The image is the one that I have used for the first time..(1gb_clockwork-3.2.0.1-eyeballer)
I will try reverting to stock, and then install once more. If not, I will try to boot from the sdcrad (double boot).
Either I am missing some very basic step, or it is really odd..
velizet said:
It is even on the mains.
I have tried creating the bootable drive more than once. The image is the one that I have used for the first time..(1gb_clockwork-3.2.0.1-eyeballer)
I will try reverting to stock, and then install once more. If not, I will try to boot from the sdcrad (double boot).
Either I am missing some very basic step, or it is really odd..
Click to expand...
Click to collapse
Patruns, now I have a nook color e-reader ver 1.2..
Before trying once more I want to check with you which image, which nightly, and which gapps should I use, and maybe from where to download..
I have a 4 GB Sandisk sdcard.
Do you want to install CM7 to the internal memory (eMMC) or just running it off the uSD?
You have to know what you want to do first.
velizet said:
It is even on the mains.
I have tried creating the bootable drive more than once. The image is the one that I have used for the first time..(1gb_clockwork-3.2.0.1-eyeballer)
I will try reverting to stock, and then install once more. If not, I will try to boot from the sdcrad (double boot).
Either I am missing some very basic step, or it is really odd..
Click to expand...
Click to collapse
votinh said:
Do you want to install CM7 to the internal memory (eMMC) or just running it off the uSD?
You have to know what you want to do first.
Click to expand...
Click to collapse
Of course I would like to install to emmc..
I assume you have a brand-new (or like brand-new) v.1.2 NC and you don't want to deal with its partitions.
1. I never try that 3.2.0.1 from eyeballer, but it should be good. Just make sure you not get the corrupted one during download
2. Get the Win32DiskImager old version, r0.15 or something
3. Create flashable uSD (i'm sure you know how to)
Make sure it's good (there should be 4 files in the boot uSD)
4. Get the stable CM7 7.1 and the latest Gapps (0811 or 0821)
5. Drop both in the uSD
6. Fire the NC up.
7. It should get into the CwM R, from there
a. format /system
b. format /data
c. format /cache
Note: I didn't format /boot when doing mine.
d. install CM7 first
e. then install Gapp
8. perform wipe data/factory reset
9. after done, remove the uSD before reboot system.
Give it some times during the first boot.
If after 10' and still not up, then force reboot.
Keep fingers crossed.
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (www.goo-inside.me/gapps/gapps-ics-20120317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get...e-cm-9-20120520-NIGHTLY-vibrantmtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/showthread.php?t=1447303
...and to think that I've "lost" a Vibrant about a year ago because such tecniques had not developed yet (back then we had no CM and the modding scene was all about samsung roms).
If that works, "thanks" on behalf of all those which are in the position that I was in. If only I still had the phone, I would had probably made it working one way or another
Yea luckily for me the phone's internal died about 3 days ago.
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
ferhanmm said:
Hmm... oddly enough the internal started working again.
Click to expand...
Click to collapse
Good news about this. You are back full and completely. Can you please go to this thread and read the OP and post your findings in it?
The error came up from a phone that was boot looping that was running stock kb5 with the "stock + voodoo kb5" kernel.
I tried flashing stock jfd then ics in attempts to fix the unmountable internal SD data. After that I did receive the encryption bug but only with the initial fix that I applied. But after the second fix I applied the internal was surprisingly brought back to life so I haven't had to deal with the encryption issues yet and I hope never again lol.
Regardless, I'll run those adb commands for you and post them when I see her again. Which should be soon.
ferhanmm said:
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
Click to expand...
Click to collapse
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
McBang2023 said:
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
Click to expand...
Click to collapse
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
ferhanmm said:
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
Click to expand...
Click to collapse
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
McBang2023 said:
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
Click to expand...
Click to collapse
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
ferhanmm said:
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
Click to expand...
Click to collapse
absolutely. and thanks again
Bump for interest of knowing if anyone else recovered internal memory after doing these steps
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
accordex said:
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
Click to expand...
Click to collapse
If you can access your internal sd after flashing stock jfd, then yes your phones storage is fine.
If you flashed eugenes jk2, check storage if it lists as unavailable then yes its messed up.
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
McBang2023 said:
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
Click to expand...
Click to collapse
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
fishman0919 said:
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
Click to expand...
Click to collapse
i would be willing to try it....but the link is broken. so no valid download.
EDIT: i found a workaround. downloading and flashing now. i will post results later.
EDIT 2: after flashing, the phone does similar to if i flashed stock jfd. the only difference is it will restart after showing the vibrant splash scfeen back to the splash screen. on stock, it completely shuts down.
anybody ever try something like this with samsung tab sph-100..?
or think i could try this? what would i need to change?
I received this tab from someone over ebay and have never once been able to get past samsung boot screen.
I have the same errors in recovery mode, have tried a lot in odin but i came to believe from other xda members that there must be some internal memory / nand chip damage.
I just got an sd card in hopes i could try something with sd card.
Is this what i'm looking for?
mind, I've never worked with android before this.. noob status still.
sender said he never had any issues with it before sending, hoping to take his word for it, i think i can return it if nothing ends up working, but he's caught in hurricane at the moment, so i am willing to work on it a few more days.
wonder if somehow magnets thru shipping could have done something?
I doubt magnets messed anything up. My suggestion is go to the section here in xda for your device and ask your question there. I would also find out if the previous owner had a custom ROM?, if so which ROM. Is it rooted and does it have a custom recovery?
All will be important info to find a fix.
Sent from my SGH-T959 using xda premium
Basically what I need is to use this mod to boot my experimental builds on the external sd w/t wiping my main ROM (which would be installed to my phone). Is that possible?
So that whatever happens I could always boot back to stock (what I will have installed in my phone), with some minor tweaking through adb shell of course. It sounds doable, ain't it?
I haven't had Safestrap since they switched to TWRP, I haven't had a rooted Bionic with a custom ROM in months due to some issues I won't get into. Now I'm lost. I don't know how to activate safe system. And the recovery won't let me Install anything, I'm guessing because I'm not in Safe System. I went through all the Recovery Menus but can't figure out how to actually activate Safe System. I have a ROM that I really want to install and can't. Can anyone point me in the right direction and give me any tips on Safestrap with the TWRP interface?
lemonoid said:
I haven't had Safestrap since they switched to TWRP, I haven't had a rooted Bionic with a custom ROM in months due to some issues I won't get into. Now I'm lost. I don't know how to activate safe system. And the recovery won't let me Install anything, I'm guessing because I'm not in Safe System. I went through all the Recovery Menus but can't figure out how to actually activate Safe System. I have a ROM that I really want to install and can't. Can anyone point me in the right direction and give me any tips on Safestrap with the TWRP interface?
Click to expand...
Click to collapse
To get into the safestrap system you have to do the folllow steps.
1. Create a rom slot
2. Activate rom slot
3. Install custom rom
4. Then boot into the rom slot that you created.
.
Sent from my BNTV250A using xda app-developers app
Is this slot created on the sdcard instead of sdcard-ext? because I went to make a rom slot and I didn't have enough free space. It said I was wanting to use 1924 mb and only had 1724 available, I went and deleted a bunch of stuff from sdcard-ext, and moved some stuff to sdcard, went back to safestrap to make the ROM slot, and now its saying I have 995mb instead of the previous 1724mb
I don't think its setup for SD storage yet just device storage. I thought I heard hash was working on it though. Also all I use is 1 gb per slot and that seems to be sufficient.
Sent from my DROID BIONIC using xda premium
lemonoid said:
Is this slot created on the sdcard instead of sdcard-ext? because I went to make a rom slot and I didn't have enough free space. It said I was wanting to use 1924 mb and only had 1724 available, I went and deleted a bunch of stuff from sdcard-ext, and moved some stuff to sdcard, went back to safestrap to make the ROM slot, and now its saying I have 995mb instead of the previous 1724mb
Click to expand...
Click to collapse
The rom slot is created on the internal sd card. You need to move all apps, videos, pics and music to your ext SD and also delete "lost.dir"
Sent from my BNTV250A using xda app-developers app
got it working. thanks.Try Wizzed ROM, it is sick. And works as a daily driver. I been using it since last night and I absolutely love it. The only problem I have had was a little data issue earlier today where I could only get 1x in a 4G area
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)