Hey guys I just flashed Temasek's unofficial CM 7.2 ROM onto my phone. My optimus 2x says it can't find my SD card. For example, I can't open up ROM manager and I can't open up my gallery. Here's what I did:
- Rooted my phone with superoneclick
- Downloaded cm7kang and placed onto my phone (internal SD card, because I don't have an external)
This is when things got strange. I guess this is when I made my mistake, but the next instruction I got was to boot into recovery mode. I searched up how to do this for our particular device and all it said was to turn device off and press Volume down + Power at the same time. I did this, and I got this android icon after 30 seconds, but then my phone booted up with all data deleted (everything was as it was when I'd first unboxed the phone). However, what was strange was when I looked at my phone storage in my settings my internal SD had 3.42GB left, the same as it was before I tried to boot into recovery.
After this issue I just went into market and downloaded ROM manager, and subsequently flashed CWM from there. Then I booted into recovery mode using the manager and downloaded the CM7 zip.
Here I am now. The new ROM seems quite nice, but I have no idea what to do from here My storage settings still shows that I have the internal SD data stored somewhere. In fact, using a file manager, going through the pathways "mnt" and then "emmc", I can see all the data that I had before is actually there. However I cannot move it or do anything to the folder "emmc".
Can anyone please help me? I'm sorry for having to make you read through all that. Thank you.
You did nothing wrong. The Cyanogenmod uses the external sdcard as primary card, not the internal like LG's ROM.
You just need to use the following setting and everything should be back to normal:
Settings -> Cyanogenmod Settings -> Application -> Use Internal Storage
By the way, the trick to go into recovery is indeed holding volume down + power until the second LG logo appears, then release power but still hold voldown. Just try it, nothing can happen. But you don't need to go there again because ROM Manager did that for you, just of you need it in the future.
Sent from my LG-P990 using XDA
tonyp said:
You did nothing wrong. The Cyanogenmod uses the external sdcard as primary card, not the internal like LG's ROM.
You just need to use the following setting and everything should be back to normal:
Settings -> Cyanogenmod Settings -> Application -> Use Internal Storage
By the way, the trick to go into recovery is indeed holding volume down + power until the second LG logo appears, then release power but still hold voldown. Just try it, nothing can happen. But you don't need to go there again because ROM Manager did that for you, just of you need it in the future.
Sent from my LG-P990 using XDA
Click to expand...
Click to collapse
I actually realised that a couple of hours after posting this thread :L I felt so stupid.
Thanks for helping, but right now I have a couple more issues. Perhaps once again I'm not experimenting enough with my new ROM but for now I'm stuck with them.
The first is just a small issue. Even though I've enabled this in the CM settings, I can't see the time in the status bar! There's this little gap on the far right of the status bar where I'm assuming the time should appear but its blank.
The second issue is slightly bigger. I can't watch any YouTube videos at all! I haven't tried downloading the app yet but I've tried the site through the browser; it just keeps saying "Sorry, this video cannot be played. If the videos on the site don't work I don't see why I should be bothered downloading the app. I heard this might be a flash problem so I installed flash player from the market - still not working.
Thanks!
1. Change the clock color. By default is black
2. Update to latest cm7 build.
Related
Hello Nookers,
I myself and pndo1 of XDA have posted guides for dual booting CM7 and Stock 1.2. My first one was crappy, my second one was a little less crappy, and pndo1's was pretty good, but had too many steps. So yeah, I decided to clear this up once and for all. Alright, enough of that garbage, let's get on with the guide!
0. Make a CWM sd card using these instructions.
1. Download CM7 to your sd card. I recommend the latest version from here. Also, if you would like to overclock download this. Lastly, if you would like to remap Volume + and - to Menu and Back, download this too. Also, your gonna want (duh) have a copy of Nook Color Stock 1.2. This one is the best in my opinion. Also, if you would like to root Stock 1.2, get this. Now get gapps from here. Almost! Download thishere. And now the multiuboot! Grr... this is tiring... but lasties! Get it here. Put ALL the files you downloaded on your SD Card.
1. Boot into CWM. Go into Backup+Restore and create a backup. Then go into Mounts+Storage and unmount the sd card. Put in an MicroSD reader in your computer. Navigate to /sdcard/clockworkmod/ and find the backup. Copy it to your computer. You can now delete it from the SD Card. Put the SD Card back in the nook. Go into Mounts+Storage and hit "Mount sd card" Now from the same place, wipe system, data, and cache. Now go to the root menu (hit the power button once). Hit "Install zip from sd card" then "Choose zip from sd card" Select prep.dualboot.zip. Then redo the choose zip Select your downloaded 1.2 Zip. It should be called "update_nc_stock_1.2_keepcwm.zip" Flash that. Now wait for it to install. Reboot your Nook. It will boot and will ask you to setup the Nook. Set it up but if you don't have wifi, follow these instructions. After setting up, boot back into CWM using your sd card.
2. Now Choose the zip from sd again, but select ManualNooter. That will take one minute to flash. Reboot again. Make sure your root is setup. To confirm, download an app from the market. Any app.
3. Once that is done, boot back into CWM. Flash the zip "eclair-to-dualboot-0.2.zip" It will duplicate Stock 1.2 to the Second partition. Now go into Mounts+Storage, and wipe system+data+cache. Now choose zip again, but this time pick CM7. Then Choose again, pick GAPPS. Then anything else, like that KeysMod or OC kernel. Now flash Multi-Uboot-0.3.zip. Now reboot without holding anything. It should boot CM7. Reboot, but this time hold the home button. BAM! Stock 1.2. Hope it worked for ya!
To those whom it doesn't work:
yelloguy said:
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
Click to expand...
Click to collapse
Credits:
@GirLuvsDroid for the feedback and testing
@GabrialDestruir for 1.2 Manual Nooter
@Koush for ROM Manager and CWM Flashes
@yellowguy for telling us to flash prep.dualboot
@Anyone else who helped but escapes my mind at the moment
@pndo1 (Who has moved on to better things than our little NC's... aka Flyer) for this orignal project
I've been wanting to dual boot my NC for a while now, but I've read several sets of instructions and kept getting twisted up in them. I was also concerned that having a dual boot would make it difficult to impossible to continue installing the CM7 nightlies and the latest Dal kernels.
These instructions look really clear and easy to follow and I thank you for that!
I just want to clarify my understanding: both CM7 and stock 1.2 are run from eMMC, correct? And, because stock 1.2 is on the second partition, it's just business as usual to install the nightlies and the latest kernel on the first partition, right?
Again, thanks for taking the time to rework your instructions again. Your contributions are much appreciated!
Why a special uboot? Stock cm7 uboot (based on bn 1.2) already does multiboot... (hold down n on boot for info) and dalingrin's nook tweaks lets you set up default options from prefs menu...
That said, I didn't read the instructions carefully so maybe there's a reason...
@GirLuvsDroid Your welcome, and yes both run from the emmc. Flash nightlies and kernel like anything. Just nothing to the dual boot partition.
@fattire For me the CM7 Alternate boot option hangs. But again, that's me.
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
MHotovec said:
I may have just missed it, but I didn't see where in the instructions to download the Multi-Boot-Uboot-0.3.zip file.
I found and downloaded v0.4 file from this thread
http://forum.xda-developers.com/showthread.php?t=947698
and it doesn't quite work right. It boots CM7 fine, but it hangs on the Nook 'N' screen when booting into stock 1.2. I'm not sure if that's because of the v0.4 multi-boot file, or because of something else I did wrong. (It did boot into stock 1.2 correctly at the point where you said it would in the instructions).
Any thoughts, or the link to the v0.3 multi-boot zip and I'll flash that to see if it corrects the problem.
Click to expand...
Click to collapse
MH, it's the link in the OP that says this: "Last one (yes, really!) here." It's not the Multi-Boot-Uboot-0.3.zip but the eclair-to-dualboot-0.2.zip.
Disgregard this post -- I'm an idiot and apparently blind, as well.
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
MHotovec said:
Thanks GLD.
I'll reflash that one (I flashed both, just like the directions said ) and see if that makes it behave better.
Click to expand...
Click to collapse
I must be blind -- I don't see where it says to flash both. I only see the eclair-to-dualboot in the instructions.
Nevermind -- I found it. It's the last step. I stand corrected and I'm glad I do because I'm planning to do this when I get home from work tonight. Thanks for setting me straight!
Reflashing the eclair to dualboot wasn't the answer, now is doesn't even TRY to boot the stock 1.2.
Now where did I leave that drawing board....
I found the download link for the Multi-Boot-Uboot-0.3.zip:
http://api.viglink.com/api/click?fo...dified u-boot.bin based on B&N 1.2 source
GLD, if anyone tells you that you're not a goddess, you tell them that I said you are.
Of course, that didn't solve the problem. (sigh)
I ran the entire routine again, and this time used the v.03 multi-boot that you found, same problem. It will boot into CM7 just fine, but it hangs up when booting into stock.
ahhhhhh, that's just so sweet, MH!
I just went through the whole process myself and everything went perfectly right up until I tried to boot into stock 1.2. Exactly like you, it hangs on the N and won't boot up. CM7 boots just fine, though.
Well, at least I know it's not just me.
By any chance, have you run the app that changes your Nooks RAM from 'new way' to 'old way'? (1gb data, 5gb apps).
I have, I wondering if that has something to do with it (just fishing of course, it's not like I actually KNOW anything).
Yes, I had a blue dot NC that I repartioned, but I did it using the custom partition (around 2GB data).
Well, multi-boot link added.
Oh, to those whom it doesn't work (stuck on N), try flashing 1.2 zip and manual nooter without rebooting and then eclair2dualboot then wipe system,data, and cache. Then flash cm7 and goodies. Not one reboot. Try it and only then say if it works or doesn't.
I'll try this no-boot method when I get a chance tomorrow. One question for you -- assuming I get this to work, is there any reason I can't restore /data from the CWM backup of my original setup that I made before I started the dual boot process?
I get the same result with the no boot method. CM7 boots fine, Nook stock hangs on the 'N' screen.
I had the same problems as everyone else is reporting on this thread. I did this on Tuesday without the benefit of this guide but with the help of other two mentioned in the OP.
So after talking to iKingBlack via PM, I tried it again yesterday. And here is the exact sequence of events in case it helps anyone.
Install removal script for dual boot found in these forums
Install stock 1.2 from the link mentioned in OP
Boot 1.2 and register the device
Sleep 7.5 hours and then chat with iKingBlack
Install manual nooter, then the apk enabler
Boot 1.2 to check root access
(no boot from now on)
Install prep dual boot
Install eclair to dual boot
Format system, data and cache
Install CM7 nightly
Install gapps
Install multi boot
Reboot holding N and check stock works as it used to
Reboot normally, check CM7 works and set it up
Since then I have used both partitions successfully.
@GLD Yes, I think you can restore safely.
@yellowguy You don't need prep dual boot because eclair2dualboot already takes care of that. And if my instructions didn't work, try yellowguys, a slightly refined method.
I own a captivate phone but didn't bother to buy an external SD card and am cheap so I didn't bother to buy one since I'm happy with the amount of internal storage. The thing is I wasn't happy with the out of the box performance of the phone or lack of customization available. So I began to look for my options of flashing ROMs.
I searched and googled myself tired with no luck on how to do this WITHOUT an SD card, so I gave up and vaguely followed most of the wiki's I did find. I'll give you a breif overview of my process which I have been able to successfully flash Cyanogenmod 7RC1 without trouble, (I suspect you can do the same with other ROMs too)
Things you need
Root (superoneclick)
If you're running stock 2.2 3e signature failure fix script + update.zip(found it here in XDA)
Clockwork ROMmanager
Phone.
Process
Open Clockwork > Flash Clock Recover using Captivate MTD(Yes to the popups) > Download ROM(I picked Cyanogen 7 RC1 + Gapps.
DO NOT ATTEMPT INSTALL YET
Cancel out of the popup that appears after the ROM is done downloading.
Back to Clock choose >Install ROM from SD Card and find and select the .zip file the default location is clockworkmod/download/download.cyanogenmod.com/get/update-cm-7.1.0-RC1-Captivate.zip
After you choose that leave the default settings, and your phone should reboot into Recover mode with the green text indicating you're in Clockwork.
Once you're in Clockwork choose > Install zip from sdcard > choose zip from sdcard > find your update-cm-7blahblahblah.zip file. The next step your phone will begin the flashing process.
On your next reboot you'll notice a new boot screen indicating it's flashed to your choosen ROM. On your first boot open Clockwork again and choose to install ROM from sdcard again. This time find your gapps.zip file and go thru the same process to install your gapps.
Finally...
you're done.
Sorry for the poor formatting but I hope you can follow this and maybe it will help somebody else as cheap as me..
Yeah, that's how you flash any Rom. And you can flash gapps before your first reboot.
Don't know why you thought you needed an sd card to flash roms on this phone
Sent from my HTC Desire HD
sliverworm said:
I own a captivate phone but didn't bother to buy an external SD card and am cheap so I didn't bother to buy one since I'm happy with the amount of internal storage. The thing is I wasn't happy with the out of the box performance of the phone or lack of customization available. So I began to look for my options of flashing ROMs.
I searched and googled myself tired with no luck on how to do this WITHOUT an SD card, so I gave up and vaguely followed most of the wiki's I did find. I'll give you a breif overview of my process which I have been able to successfully flash Cyanogenmod 7RC1 without trouble, (I suspect you can do the same with other ROMs too)
Things you need
Root (superoneclick)
If you're running stock 2.2 3e signature failure fix script + update.zip(found it here in XDA)
Clockwork ROMmanager
Phone.
Process
Open Clockwork > Flash Clock Recover using Captivate MTD(Yes to the popups) > Download ROM(I picked Cyanogen 7 RC1 + Gapps.
DO NOT ATTEMPT INSTALL YET
Cancel out of the popup that appears after the ROM is done downloading.
Back to Clock choose >Install ROM from SD Card and find and select the .zip file the default location is clockworkmod/download/download.cyanogenmod.com/get/update-cm-7.1.0-RC1-Captivate.zip
After you choose that leave the default settings, and your phone should reboot into Recover mode with the green text indicating you're in Clockwork.
Once you're in Clockwork choose > Install zip from sdcard > choose zip from sdcard > find your update-cm-7blahblahblah.zip file. The next step your phone will begin the flashing process.
On your next reboot you'll notice a new boot screen indicating it's flashed to your choosen ROM. On your first boot open Clockwork again and choose to install ROM from sdcard again. This time find your gapps.zip file and go thru the same process to install your gapps.
Finally...
you're done.
Sorry for the poor formatting but I hope you can follow this and maybe it will help somebody else as cheap as me..
Click to expand...
Click to collapse
Thx for the ... incite?
Sent from my Fusion II powered Captivate
Umm...ok? Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
bulletproof1013 said:
Umm...ok? Lol
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol. Dunno man, just smile and nod
Sent from my HTC Desire HD
Welcome to xda silverworm¡
Sent from my SAMSUNG-SGH-I897 using XDA App
Good advice pirateghost
:nod:
Pirateghost said:
Lol. Dunno man, just smile and nod
Sent from my HTC Desire HD
Click to expand...
Click to collapse
I agree just smile and nod. It has served me well thru my life. Sometimes when you do things will randomly appear in the house but that is for a different forum
Sent from my SGH-I897 using XDA App
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
ukppete said:
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
Click to expand...
Click to collapse
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
freakymod2120 said:
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
Click to expand...
Click to collapse
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
ukppete said:
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
Click to expand...
Click to collapse
SOLVED
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
freakymod2120 said:
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
Click to expand...
Click to collapse
No Prob...
Nice to know i could help ...
Good instruction about flashing ...:good:
ukppete said:
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
Click to expand...
Click to collapse
grabbed root-stock.zip and cwm just below it (first 2 links on this page http://forum.xda-developers.com/showthread.php?t=1686384 ) carefully followed instructions, even watched videos on youtube and everything went swimmingly except after system reboot following root-stock.zip install. i must have grabbed the wrong file (dont know how, it was recommended by everyone on every other thread regarding the rooting of the t679) anyway now i need assistance, which root.zip file should i use? how do i get it onto the phone's internal "usb storage" folder? or can i use another device to grab file, transfer to ext. sd, then put ext. sd card into t679? i understand its critical at this point to make no mistakes, i believe i can recover, assuming i get competent advice...
please advise...
- zCHEMDAWGz
p.s. i am attempting to repair wifi and bluetooth errors (assuming its the drivers not loaded properly following system update 2.3.6) though im not certain of the culprit of these errors as i am the 4th owner of this device. assuming an internal battery has NOT leaked onto circuit board causing corrosion, pretty sure its software not hardware issue. phone/sms/network WAS connecting just no wifi/bluetooth. gotta have wifi cuz im out in the woods on the "EDGE" network, home network is fast as can be.
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Dvarl said:
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
hey thanks for helping me i really appreciate it. so i tried your advice, in every order possible. fix permissions, wipe (everything), load rom, reboot... wipe, load, fix, reboot... to no avail though. all results in same loop... im getting good at wiping and loading =)
also the location of the rom and cwm files prior to transferring to "usb storage" folder was "downloads" on my windows 7 pc... does this make a difference? i have noticed people saving these types of files to their desktop... just trying to find out where i went wrong... thanks again.
- zCHEMDAWGz
SIDE NOTE: i tried loading different rom "t679-root-v1.8.zip" with exact same results... however i noticed that when i load either version of the new rom when cwm begins installation, and when the progress bar at the lower part of the screen shows about 2-3% complete it is then all of the sudden finished with "complete" confirmation at the end. total time less than 5 seconds. according to instructional videos this process should take minutes, instead of seconds.... just an observation.
- zCHEMDAWGz
That's just root not a ROM. If your willing to start fresh you can try this.
Wipe everything x3
Under mounts and storage mound system and data then format both x3
Flash rooted community rom
Reboot
It should work. If you flash any recent ROM make sure you have the latest cwm or you will get status 7 error.
Sent from my SGH-T679 using XDA Free mobile app
success!! wifi/bluetooth still getting error though... tried *#*#526#*#* (wlantest engineering mode) reports "Notset Driver Loaded [NG]"
any ideas?
a-thousand thank yous
- zCHEMDAWGz
Hi,
I changed the software of my Mi Mix 6 months ago to lineage os - after the change of the os, the sound was not running properly anymore. In the forum someone did help me out with software for a firmware update. Now I updated on Lineage os 15.1 and the soundproblems are there again. Can someone tell me, if I have to update the firmware again, respectively where I can find the relevant software. Thanks for helping!
H0707 said:
Hi,
I changed the software of my Mi Mix 6 months ago to lineage os - after the change of the os, the sound was not running properly anymore. In the forum someone did help me out with software for a firmware update. Now I updated on Lineage os 15.1 and the soundproblems are there again. Can someone tell me, if I have to update the firmware again, respectively where I can find the relevant software. Thanks for helping!
Click to expand...
Click to collapse
how people gonna help you if you're not describing your problem with more details.
what is exactly the sound problem.
heindrix said:
how people gonna help you if you're not describing your problem with more details.
what is exactly the sound problem.
Click to expand...
Click to collapse
I am sorry - I have been not very precise. The sound itself is still working. But my device especially has problems to connect to myBluetooth Speaker. Maybe thats more a connection issue. There are further a bunch of small problems, I cannot explain. For example - I cannot download maps of different regions in my map app anymore. As well - I am using the yalp store to download certain apps I need - downloads or updates are not possible anymore. Half a year ago someone gave me this link for firmware updates: https://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw Is it useful to update the firmware on a newer version?
Best
First you do not need to use a firmware for LoS 15.1, just the latest nightly which is here: https://download.lineageos.org/lithium
*Second.... Do NOT use any app store beside Google Play. Because it may cause problems to your phone. Use Google Play only... Any the apps can harm your device.... I would suggest to do a full wipe on the advance wipe option in TWRP... That means everything except for USB OTG.. Make sure you are done... Make sure all data partitions (DATA, Caches) is on EXT 4 before installing. See the info below near the photo.
If your phone still have problems.....I would suggest go back to Stock Firmware by using Mi Flash (make sure you click "Clean All" without locking your phone on the bottom right of Mi-Flash) when you boot your phone to to **bootloader**. You can use Mi Flash and flash the current Global Stable or Global Developer for the Mi Mix which is on en.miui.com/a-234.html then check to see if the problem still happens on either firmwares. If there is no problem, then by all means go back to LoS 15.1. The Miui Rom Flashing tool link is right above the list of the Miui Rom Version. And again i warn you before flashing the stock firmware to click the "Clean All" only.. not "Clean All and Lock" because it will lock your bootloader. Then after your done, check for any problems.. If the phone is ok.. Then go back to LoS 15.1 to determine if these problems still happen.. If it works fine.. Then you know why your phone had problems in the first place.
The photo is for you to see what to wipe when doing a clean installation of LoS 15.1.. Wipe all except for the USB OTG before flashing anything. Repair and Change system file is to check to see if all of your partitions is on EXT 4. Just to make sure you have no errors of any kind before installing.
H0707 said:
I am sorry - I have been not very precise. The sound itself is still working. But my device especially has problems to connect to myBluetooth Speaker. Maybe thats more a connection issue. There are further a bunch of small problems, I cannot explain. For example - I cannot download maps of different regions in my map app anymore. As well - I am using the yalp store to download certain apps I need - downloads or updates are not possible anymore. Half a year ago someone gave me this link for firmware updates: https://mega.nz/#F!zlJBQJhJ!BJuv0brw0doTafuLTXJATw Is it useful to update the firmware on a newer version?
Best
Click to expand...
Click to collapse
download and flash the latest firmware i cooked from my google drive : https://drive.google.com/drive/mobile/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
if the issue still there, it's not firmware problem, maybe it's the ROM problem.
you can try CrDroid : https://forum.xda-developers.com/mi-mix/development/rom-crdroid-t3758726
or AICP : https://forum.xda-developers.com/mi-mix/development/rom-aicp-13-1-t3746648
or Resurrection Remix : https://forum.xda-developers.com/mi-mix/development/rom-resurrection-remix-t3751314
heindrix said:
download and flash the latest firmware i cooked from my google drive : https://drive.google.com/drive/mobile/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
if the issue still there, it's not firmware problem, maybe it's the ROM problem.
you can try CrDroid : https://forum.xda-developers.com/mi-mix/development/rom-crdroid-t3758726
or AICP : https://forum.xda-developers.com/mi-mix/development/rom-aicp-13-1-t3746648
or Resurrection Remix : https://forum.xda-developers.com/mi-mix/development/rom-resurrection-remix-t3751314
Click to expand...
Click to collapse
Thanks a lot for your extensive response.
One thing - out of some reason I cannot start TWRP manually (maybe cause I encrypted my hard-drive). I only can start it using adb. Once, my recovery is started, I can not connect to the phones hard-drive via my computer anymore. Am I not deleting the complete hard-drive plus OS, when I am performing an extended wipe - as you are suggesting. My problem is, that I am afraid, that I am not able to install a new OS after a wipe (since I will delete all data stored on the hard-drive and to enter my hard-drive again, I would have to start the phone...).
Ps. I never heard that it might cause problems to install apps from apps like the yalp store. Since I am not interested to have all the google surveillance software on my phone, using a costum rom without gapps seemed a good way for me till now.
H0707 said:
Thanks a lot for your extensive response.
One thing - out of some reason I cannot start TWRP manually (maybe cause I encrypted my hard-drive). I only can start it using adb. Once, my recovery is started, I can not connect to the phones hard-drive via my computer anymore. Am I not deleting the complete hard-drive plus OS, when I am performing an extended wipe - as you are suggesting. My problem is, that I am afraid, that I am not able to install a new OS after a wipe (since I will delete all data stored on the hard-drive and to enter my hard-drive again, I would have to start the phone...).
Ps. I never heard that it might cause problems to install apps from apps like the yalp store. Since I am not interested to have all the google surveillance software on my phone, using a costum rom without gapps seemed a good way for me till now.
Click to expand...
Click to collapse
Something weird happened - TWRP is not accepting my password anymore at the start. Thats strange cause my password is accepted, when I start the phone. Bad development
H0707 said:
Something weird happened - TWRP is not accepting my password anymore at the start. Thats strange cause my password is accepted, when I start the phone. Bad development
Click to expand...
Click to collapse
sorry for judging, but reading your details, i suppose you haven't learn a lot about customizing device.
if this suggestion didn't help you, i don't know anymore what will.
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash files you want to flash
heindrix said:
sorry for judging, but reading your details, i suppose you haven't learn a lot about customizing device.
if this suggestion didn't help you, i don't know anymore what will.
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash files you want to flash
Click to expand...
Click to collapse
Dear Hendrix, I am not a pro just an interested person trying to emancipate myself dealing with smartphonetechnology. Thanks a lot for your guideline. I will try your advice as soon as I find the time. Will let you know, if everything worked out! Best wishes
For what it's worth, flashing the firmware provided by hendrix fixed my lineageos 15.1 problems.
I recently moved into LineageOS coming from latest MIUI 10 by Xiaomi.eu. Initially everything worked fine except for sound when playing media files (notification sound works). The firmware flash fixed everything.
heindrix said:
sorry for judging, but reading your details, i suppose you haven't learn a lot about customizing device.
if this suggestion didn't help you, i don't know anymore what will.
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash files you want to flash
Click to expand...
Click to collapse
Dear Hendrix,
everything worked fine - the device feels like new - thanks!
If you have questions on cultural sciences (am holding a PHD in this area) you can always ask me - I for sure will not start judging you in your unprofessional first moves
H0707 said:
Dear Hendrix,
everything worked fine - the device feels like new - thanks!
If you have questions on cultural sciences (am holding a PHD in this area) you can always ask me - I for sure will not start judging you in your unprofessional first moves
Click to expand...
Click to collapse
Me too, Phone itself worked great, had NO sound from Google Assistant, no sound from headphones, no sound from speakers, but did have ring/notifications and some sound. Video was laggy and intermittent on youtube and the net..... I tried many different Roms, Many newer firmwares and the ONLY ONLY thing that worked was the suggestion to try firmware 8.1.4
After that all is working great...…………..
garythompson said:
Me too, Phone itself worked great, had NO sound from Google Assistant, no sound from headphones, no sound from speakers, but did have ring/notifications and some sound. Video was laggy and intermittent on youtube and the net..... I tried many different Roms, Many newer firmwares and the ONLY ONLY thing that worked was the suggestion to try firmware 8.1.4
After that all is working great...…………..
Click to expand...
Click to collapse
Some users said that there are problems on firmware more than 8.8.2 version, 8.8.2 still works fine. but i don't know if it will works for you too.