Related
Hi everyone.
I'm just creating this thread to share any issues everyone is facing with cm7. And maybe getting issues fixed. Just trying so that everyone will share their issues + known solutions if any. Please specify the CM version on what you are talking about... PLS SHARE THE THINGS..
NOTE : The below things doesn't mean that they should be present in your device. It is always better if you don't have those. Just they are the common issues faced by many people.
FAQ's
1. My GPS / Wifi is not working.
A: This is the issue which most of the people are facing. Re-flashing the radio will solve this (cannot assure this since it didn't solve for some people) . If you are going with re-flashing the radio, please make sure that you have enough battery and using recovery 2.x (the one from rom manager is also enough). And flashing the hboot and radio has the potential to brick the phone, suppose if anything goes wrong. So, better to avoid doing these things frequently.
ALTERNATE METHOD (SAFE) : This is working. First install cm7 and then make a nandroid backup of it. Then wipe everything and restore the previous nandroid backup of stock froyo rom (or any rom with working gps) and use gps to capture your location. Then again wipe everything and restore the cm7 backup. Now gps will be working. And once gps on cm7 works, then even after a hard reset it still works. This seems to be an issue only when freshly installing cm7. This is definitely a safe method.
2. USB tethering not working + I can't see usb tethering option on status bar.
A: The status bar of cm7 doesn't has the option for selecting usb tethering (like stock rom). Instead the option is present in Settings/Wireless & Networks/Tethering & Portable hotspot/usb tethering. So, access the option from here. And make sure that your pc has necessary drivers (HTCDriver_2.0.7.17.exe is enough). No need of drivers for linux.
And another important thing is, You should disable USB DEBUGGING to access usb tethering. For doing that go to Settings/Applications/Development/ . The stock htc rom will disable usb debugging automatically when tethering is selected. But on cm7 presently u need to manually disable the debugging option (for usb tethering to work).
3. I can't access MOBILE INTERNET DATA
A: Check whether you have the correct access point or not. Go to Settings/Wireless & Networks/Mobile Networks/Access Point Names/ . If this is the issue make sure to manually add APN by clicking menu and select "New APN". The settings to be told by your service provider. Or if you have the previous working nandroid backups, then u can note the settings from them to be entered in CM7 apn. The APN will be generally configured automatically, and in case if they are not, you need to manually add apn.
4. I can't see the market application.
A: Google apps package is not included in CM7 rom. Make sure u have flashed the "universal google apps package for CM7" from the recovery. It is better to flash the google apps just after flashing the rom (without a reboot gap). The process of flashing google apps is same as the process of flashing a custom rom. And login to your gmail account to access the market.
--Google apps link: gapps-gb-20110613-signed.zip
5. I can't add facebook / twitter account through settings.
A: You need to have those applications installed to add those accounts. Just after opening the market for first time, you will see a MARKET INSTALLER screen to "Choose the apps to install". This includes facebook, gmail, google goggles, google maps, google voice, twitter, youtube and some others. Either install them from this screen or install them later from market to integrate those accounts. And u can synchronize the facebook contacts on doing this.
6. Problem related to Wifi connection
A: Try to change the number of channels under Wifi Advanced settings/Regulatory domain/ .
7. I can't enable BLUETOOTH FTP
Maybe there is no option by default. But you can always enable it with third party apps like "Bluetooth file transfer"(by medieval software) .
8. I can't access root permissions
A: in 99% cases, the su binary will be there in the rom. Incase if you can't access the root permissions due to the absence of su binary, then flash this file from recovery just like flashing any other rom.
su-2.3.6.1-ef-signed.zip
9. Font issue of Google Maps
A: The newer version of google maps is somewhat laggy and has blurred fonts. Try the older version (gmm-android-google version:5.0.0) which has clear font and is more responsive.
**********************Thanks to Cyanogen Mod team for the awesome rom**********************
Nice Post. Haven't had any of those issues myself so far. Good to see some useful information though.
Yep. Not everyone has all the issues. But depends. Thank u
I don't have had any of those issues yet. All of the things you mentioned are working just fine.
mine working great so far..just my youtube videos are black screen..sound is there tho.
Random reboot, wifi dying on full signal.
Openfire ftw lol, no problems what so ever.
Sent from my wildfire using Tapatalk
I have the GPS problem too. I tried reflashing both radios, 19.25 and 20.10 but neither of them worked. Did the backup and restore method you mentioned work properly?
Sent from my HTC Wildfire using XDA App
waywardlistener said:
I have the GPS problem too. I tried reflashing both radios, 19.25 and 20.10 but neither of them worked. Did the backup and restore method you mentioned work properly?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
yes. Worked with me really.
If it works when u restore the stock rom, it will also work then on cm7 i think.
Pls post your results if u check
hi guys
i've a problem, i did the s-off method from alpha, i'd install the recovery mode clockwork-3.2.0.0, did the backup, wipe out all, instal from sd card and..........still got my stock version froyo 2.2. what hell???
plus add all the stock apps, the only thing left was the others one that i had installed. so i dont quite get it?
please help me
p.s. foret to tell im trying to install CyanogenMod 7 Nightly Builds
alexctk said:
hi guys
i've a problem, i did the s-off method from alpha, i'd install the recovery mode clockwork-3.2.0.0, did the backup, wipe out all, instal from sd card and..........still got my stock version froyo 2.2. what hell???
plus add all the stock apps, the only thing left was the others one that i had installed. so i dont quite get it?
please help me
p.s. foret to tell im trying to install CyanogenMod 7 Nightly Builds
Click to expand...
Click to collapse
Don't know, but check again ...
You are using recovery 3.x and it is correct one for cm7.
Download link for nightly version here http://download.cyanogenmod.com/?type=nightly&device=buzz
Then boot into custom recovery and select wipe data, wipe cache, wipe dalvik cache, factory reset . Then select "install zip from sdcard". Then "choose zip from sdcard". Then add the downloaded file. Takes around 5min to install. Then install the google apps package linked above. After that, reboot. Will solve i think.
I have a problem with the phone. I am on CM 7 stable. Whenever I receive a phone call, and answer, it first activates speakerphone for a second or two and then goes back to normal. Anybody else have this problem?
Sent from my HTC Wildfire using XDA App
bharatgaddameedi said:
yes. Worked with me really.
If it works when u restore the stock rom, it will also work then on cm7 i think.
Pls post your results if u check
Click to expand...
Click to collapse
For some reason my nandroid backup of the stock rom failed to restore.
Any other ideas?
Sent from my HTC Wildfire using XDA App
good job ! man
how to reflash radio my gps dont work. using clockwork recovery
What cwm you have used for your nandroid back up?
send with my wf s-off thank Alpharevx
waywardlistener said:
For some reason my nandroid backup of the stock rom failed to restore.
Any other ideas?
Click to expand...
Click to collapse
Have had something similar, and in trying to restore it, I tought I almost broke my phone :-o it would only boot up in recovery, very painfull for a moment.
I solved it by flashing the nandroid backup immages manualy with the use of fastboot.
1. Open the nandroid backup folder on your computer and you can see a boot.img, data.img and system.img
2. Copy (only) those three in the same folder where fastboot.exe is stored.
3. Reboot phone into bootloader. Select fastboot and plug the phone in your computer.
4. Open the command line on your computer and browse to the folder where fastboot is. Type "fastboot devices" and hit enter. You should see your device listed now.
5. Type
"fastboot flash system system.img" and hit enter
"fastboot flash userdata data.img" and hit enter
"fastboot flash boot boot.img" and hit enter
Note that every time you time you hit enter, you can follow the proces in the bootloader itself.
6. Type "fastboot reboot" and hit enter
It should work. Make sure you have enough battery and wathever you do, do not interupt the flashing proces.
Good luck with it,
Erwin
waywardlistener said:
For some reason my nandroid backup of the stock rom failed to restore.
Any other ideas?
Click to expand...
Click to collapse
I guess u have changed the folder name of backup folder (which will be normally in date and time). I have also once changed the folder name of that and it said md5 checksum error. But this can be flashed from fastboot flash method.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
While restoring nandroid backup through fastboot process make sure u first delete the things (you can also do these from recovery menu). The commands will be
fastboot erase boot
fastboot erase userdata
fastboot erase cache
fastboot erase dalvik-cache
fastboot erase system
Then use the commands said above by erwinP (can also include cache.img). Keep your img files in the fastboot.exe folder ( = command prompt CD folder).
And recovery version shouldn't be giving issues related to nandroid restore AFAIK.
Sent from my HTC Wildfire using XDA App
i solved my problems by myself, thanks anyway, back to cm7 - best
Fulfen said:
how to reflash radio my gps dont work. using clockwork recovery
Click to expand...
Click to collapse
Go to this thread [REF] [22/06] [MAJOR UPDATE] The Complete Wildfire Index
and download the radio from section 4. Put the zip file on sdcard.
Then you should have clockworkmod 2.x recovery for flashing this. This is because amend scripting is not supported by recovery 3.x and +. So, if you are using CWM 3.x , then you can open rom manager and select "flash recovery" which flashes 2.5.0.7 recovery as a secondary thing on the memory card. Then if you select "Reboot to Recovery" from the rom manager itself, your phone reboots into 2.x recovery for that one time only [Let us call this as secondary recovery]. Now you can flash the Radio file you downloaded. Make sure your battery is enough so as not to interrupt the process. And once you are in 2.x recovery, then select "install zip from sdcard" and then "choose zip from sdcard". Then add your zip file. (NOTE : Donot wipe the data for radio installations, not necessary)
note: For secondary recovery to work, the memory card should be mounted (Although u need it for every recovery flashing).
for me radio re-flashing dont work, or should i flash older 1? thank you.
FLASHING GUIDE<Team 3xtr3m3 | ICS333 ROM>NOTE : NOT ALL THESE STEPS ARE A MUST OR NEEDED TO BE DONE IN THIS PARTICULAR WAY, BUT IT IS BEST TO DO SO IN ORDER TO AVOID FURTHER PROBLEMS AND MAKE SURE THE FLASHING PROCESS IS AS CLEAN AS POSSIBLE.
>EVERYTHING WILL BE WIPED<
PAY ATTENTION AND TAKE YOUR TIME !
THIS ROM AUTOMATICALLY SAVES YOUR IMEI FOR RESTORING IN CASE YOU LOSE IT!
SOME MAY LOSE THEIR IMEI AFTER FLASHING ICS SO JUST USE THE GUIDE FOR
RESTORING IMEI AT THE BOTTOM OF THE PAGE!
I DO NOT ANSWER TO QUESTIONS WHICH HAVE ALREADY BEEN ANSWERED IN THIS TUTORIAL OR IN THE LINKS THIS TUTORIAL PROVIDES !
THIS IS WHAT YOU HAVE TO DO STEP BY STEP :
IT IS ALWAYS BETTER TO FLASH ICS FROM GB TO MAKE THE FLASHING PROCESS AS CLEAN AS POSSIBLE AND TO AVOID POTENTIAL ISSUES!
1. Download the GB Flash KIT which includes the following (XXJW5 2.3.6 GB ROM, PIT file, CF-Root Kernel for Odin, Odin3-v1.85 and Samsung Driver) : http://d-h.st/4nP
NOTE : It would be best to have your phone fully charged before flashing
2. If you haven`t already installed the driver, install it from the GB Flash KIT.
> Plug your phone into the PC and format internal SD
NOTE : The steps below require the know-how of download mode and clockworkmod recovery (CWM) :
For putting the phone in download mode : Keep pressed volume down + home button + power button until it goes into download mode.
For accesing CWM : Keep pressed volume up + home button + power button until the phone reboots.As soon as you see the "Galaxy S" logo, release the buttons.Now you are in CWM.
3. Enter Download Mode, open Odin, check Re-Partition, press PIT button and browse for the PIT file, press PDA button and browse for the PDA file in the ROM folder, press PHONE button and browse for the PHONE file, press CSC button and browse for the CSC file and finally press START button.Wait till it`s finished and when the phone reboots disconnect from PC.
4. When the phone has booted into the ROM and you see the wizard screen just enter download mode again, plug your phone into the PC, open Odin, press PDA button and browse for the CF-Root kernel, press START button and wait for it to finish.After the phone reboots disconnect it from the PC, let it boot and when you`re in the ROM, set your phone to mass storage mode from settings>wireless & network>usb settings and plug your phone into the PC, copy the ICS333 ROM to your internal SD root location, assuming you have downloaded it from here : http://goo.gl/LuXvH and disconnect from PC.
5. Enter CWM, Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache and flash the ROM.You will notice the phone will reboot immediately because it will switch kernels, from CF-Root to Semaphore, prior to flashing the actual ROM.As a result, it will boot loop or get stuck on Semaphore logo, so just force it into CWM using the 3 key combo (no need to take the battery out).Now flash the rom again and wait till it`s finished and > Reboot to system!.
IMPORTANT : After reboot, enter CWM, flash GAPPS provided here : http://goo.gl/LuXvH and reboot.That`s it.You`re done!.
NOTE : You may not succeed from the first try with the 3 key combo, it`s a matter of timing when releasing the buttons to enter CWM.Just make sure you release the buttons as soon as you see the Galaxy S logo.You will get passed the bootloop/Semaphore logo and enter CWM eventually!
If you still didn`t succeed, turn off phone and turn it on by using the 3 key combo to go directly into CWM.
IMPORTANT : You may encounter a Phone Encryption problem at first boot, so all you need to do is > enter CWM > flash the rom again > Reboot!
As a last resort, if every method above failed, try this :
1. Flash GB ROM
2. Flash CF-Root Kernel
3. Wipe Data/Factory Reset, Wipe Cache, Wipe Dalvik Cache
4. Flash this script : http://d-h.st/P2M
5. Flash Devil Kernel [choose any CFS_BLN_CMC version] : http://devil.haxer.org
6. Flash ICS333 ROM, don`t reboot yet
7. Flash the script again : http://d-h.st/P2M
8. Flash Devil Kernel again : http://devil.haxer.org
9. Flash GAPPS provided here : http://goo.gl/LuXvH
10. Reboot twice
>> Done!
If you are not satisfied with your modem`s performance or you end up with "Baseband Unknown", try a different one from here : http://goo.gl/R9q5l
Depending on the region you are in, modems can make a huge difference!
But usually 3G/Internet usage will discharge battery faster than Wi-Fi usage.
THERE IS NO "BEST MODEM" > you have to experiment yourselves with these modems!
You may experience soft reboots or slow downs/hangs if you mess with voltages, specific governor-scheduler combos or if you overclock.
If you are not satisfied with the stock launcher, in terms of speed and stability, I highly recommend using Nova Launcher instead, it performs better than Apex Launcher, as I`ve tested myself, it has great features and customizations and it compliments the rom, plus it looks like stock, preserving the ICS look : http://goo.gl/y479F
NOTE : For fully working H/W Decoding on video playing please use DicePlayer : http://goo.gl/4BHth
IMPORTANT : If you encounter "Low on Storage" issue just flash this via CWM and reboot! : http://d-h.st/94L
IMPORTANT : If you have problems with media storage (file detection/duplicates issues) this is what you have to do :
Go to System Settings > Apps > ALL tab > scroll down for Media Storage > Clear Data, Force Stop!
Reboot phone and give it some more time to scan for everything (especially if you have lots of multimedia files)!
Everything should be OK now.
Also, when an app FC`s, go to > Manage apps > find the app > Clear Data > Reboot!
IMPORTANT [Titanium Backup] : Before you make a backup do this : Open Titanium Backup > Tap Menu Button > Preferences > Scroll down to "Troubleshooting settings" > check "Follow all symbolic links".Done.
IMPORTANT [GPS] : Make sure you install FasterFix : http://goo.gl/660r6 > open it > choose a region/server according to your location > press GO.Now your GPS will work properly and get a lock faster.
> Tested iGO and it works just fine
NOTE [VIBER] : In order for Viber to fully work, use Root Explorer or Ghost Commander, go to > /system/build.prop > edit build.prop file > find the line "ro.product.model=GT-I9000" and replace "GT-I9000" with "Nexus S".Save and exit.Reboot!
HOW TO RESTORE IMEI [EFS Folder], IF NEEDED, USING Nitrality (free app) > http://goo.gl/9hxOB :
1. Install "Nitrality" from Google Play Store, open it, grant root acces.
2. Go to "Tools" > Restore /efs > Reboot!
3. Done!
NOTE : If for some reason Nitrality doesn`t do the job, restore your IMEI using the guides below.
HOW TO RESTORE IMEI [EFS Folder], IF NEEDED, USING Root Explorer (paid app) > http://goo.gl/xBqok :
First check if you`ve lost your IMEI : open Dialer, input *#06# and if the IMEI number starts with "049" then it means you lost your IMEI and you have to restore it.
1. After you flashed the ICS333 Rom, install Root Explorer.
2. Go to "/sdcard/backup", open "efs" folder, press "Menu" button > Multi-Select > Select All > Copy.
3. Go back to root "/", open "efs" folder and paste the contents here, when asked, check to replace all files.
4. Reboot
5. Done!
NOTE : It is important not to copy the EFS folder itself , when you want to restore IMEI, but the contents within the EFS folder, which will replace the contents of the EFS folder from the root "/EFS".
HOW TO RESTORE IMEI [EFS Folder], IF NEEDED, USING Ghost Commander File Manager (free app) > http://goo.gl/J0TF9 :
1. After you flashed the ICS333 Rom, install Ghost Commander File Manager.Open Ghost Commander File Manager > Menu button > Application > Settings > Scroll down to "Advanced" > Check "Show root and mounts", check "Automatic root mode" > Go back and hold the phone in landscape mode.Now you will have two panels (left panel next to the front camera and right panel next to the home button).
2. On the left panel, tap on "root mode", open "/efs" folder
3. On the right panel, tap on "root mode", go to "/mnt/sdcard/backup" (open folders by double tap), open "/efs" folder, select all files within the efs folder, one by one (one tap to select a file), tap on "5 copy", a windows will open saying "Copy # items to : root:/efs", which is the location you are in the left panel, tap on "OK" and all the files will be automatically overwritten.
4. Reboot
5. Done!
HOW TO EXPORT A LOG FILE (LOGCAT) FOR DEBUGGING via Android Terminal Emulator : http://goo.gl/oLRC0<by providing the logcat to the devs, you can REALLY help the debugging process when something goes wrong with the rom>
[Semaphore Kernel Users] :
1. Open Semaphore app > Kernel Features > check "Logger" > Reboot!
2. Install Android Terminal Emulator : http://goo.gl/oLRC0
3. Let the phone run for 3/4 hours > open Android Terminal Emulator > type "su" (without quotes), tap on return (enter) key, grant root if asked, now type "logcat>/sdcard/logcat.txt" (without quotes), tap on return (enter) key.
4. Now you have created a text file with the logcat.Done!
[USERS WITH ANOTHER KERNEL] :
1. If the kernel you are using, comes with an app (like the Semaphore app), search for an option which allows you to enable the logger.If you don`t have any app, most probably you have to enable the logger via CWM, just acces CWM and search where you can enable the logger and reboot.
2. Let the phone run for 3/4 hours > install and open Android Terminal Emulator > type "su" (without quotes), tap on return (enter) key, grant root if asked, now type "logcat>/sdcard/logcat.txt" (without quotes), tap on return (enter) key.
3. Now you have created a text file with the logcat.Done!
If you followed every step in this tutorial it is highly unlikely to fail this, only if you can`t read English properly.
If you have questions/problems or you just want to chat about it, go here : http://webchat.freenode.net
Channel : ##ICS333
If you found this guide helpful just press “Thanks” . Keep the thread clean and use the IRC channel!
Good Luck!
Enjoy this wonderful ROM !
Hi mate I tried flashing using your guide but I am still stuck.
My phone keeps trying to boot after I wipe for the second time (after the bootloop from changing kernels, I already sorted that out)
After flashing the rom (properly after the bootloop due to kernel change) I wipe data/cache/dalvik. That happens fine but when I boot I get the gt-i9000 startup splash then the semaphore splash stays on for a while then the phone resets. It then loops the same thing.
I took the battery out and tried to enter recovery mode but the same happens again. Turning the phone on normally result n the same thing happening.
I haven't overclocked or anything like that.
However altering your method I have it working (I did however have the same problem as I mentioned above (the bootloop between the starting screen and the kernel screen) but that came after using the rom for a few hours leaving it in my pocket.
I got it working by:
1. download the files
2. formatted internal sd
3. flashed JW5 and let it load
4. flashed cf-root
5. put ICS333, kernel cleanup script, devil kernel that you suggested and GAPPS zip files on internal sd
6. turn phone off and then boot into recovery
7. wiped data/cache/dalvik
8. run the kernel cleanup zip
9. flash ICS333 and wait for bootloop
10. get into recovery
11. flash ICS333 zip again
12. when done flash GAPPS
13. when done reboot into recovery.
14. run kernel cleanup zip for second time
15. Install devil kernel
16. reboot system
Job done.
It is currently 00:22 in the UK so I'm going to bed. I'll leave my phone running through the night and I will see if I have the same issue as before.
yep.it seems semaphore 1.1.1 version is really causing problems for some people. thanks for your feedback so people with similar issues like yours can try flashing the rom like you did as an alternative.
I faced problem with 3 keys combo recovery mod, they are not working while downloading keys working, and recovery working from CWM manager,phone stucked in boot loop after installed new ICS333 Rom. do you have idea if I can install kernel first then not go into boot loop, thanks.
gazza1988 said:
Hi mate I tried flashing using your guide but I am still stuck.
My phone keeps trying to boot after I wipe for the second time (after the bootloop from changing kernels, I already sorted that out)
After flashing the rom (properly after the bootloop due to kernel change) I wipe data/cache/dalvik. That happens fine but when I boot I get the gt-i9000 startup splash then the semaphore splash stays on for a while then the phone resets. It then loops the same thing.
I took the battery out and tried to enter recovery mode but the same happens again. Turning the phone on normally result n the same thing happening.
I haven't overclocked or anything like that.
However altering your method I have it working (I did however have the same problem as I mentioned above (the bootloop between the starting screen and the kernel screen) but that came after using the rom for a few hours leaving it in my pocket.
I got it working by:
1. download the files
2. formatted internal sd
3. flashed JW5 and let it load
4. flashed cf-root
5. put ICS333, kernel cleanup script, devil kernel that you suggested and GAPPS zip files on internal sd
6. turn phone off and then boot into recovery
7. wiped data/cache/dalvik
8. run the kernel cleanup zip
9. flash ICS333 and wait for bootloop
10. get into recovery
11. flash ICS333 zip again
12. when done flash GAPPS
13. when done reboot into recovery.
14. run kernel cleanup zip for second time
15. Install devil kernel
16. reboot system
Job done.
It is currently 00:22 in the UK so I'm going to bed. I'll leave my phone running through the night and I will see if I have the same issue as before.
Click to expand...
Click to collapse
I have the same problem, the device's bootloop & bootloop, someone help us please
chientn said:
I have the same problem, the device's bootloop & bootloop, someone help us please
Click to expand...
Click to collapse
NOTE : You may not succeed from the first try with the 3 key combo, it`s a matter of timing when releasing the buttons to enter CWM.Just make sure you release the buttons as soon as you see the Galaxy S logo.You will get passed the bootloop and enter CWM eventually!
If you still didn`t succeed, turn off phone and turn it on by using the 3 key combo to go directly into CWM.
perfect guide
Consider using Midnight-Kernel for next release. No reboots and zero FC's here.
Gesendet von meinem GT-I9000 mit Tapatalk 2
salzheld said:
Consider using Midnight-Kernel for next release. No reboots and zero FC's here.
Gesendet von meinem GT-I9000 mit Tapatalk 2
Click to expand...
Click to collapse
problems solved by reverting to semaphore 1.0.0s version.
sorry, wrong thread ;-)
psyqiq said:
NOTE : You may not succeed from the first try with the 3 key combo, it`s a matter of timing when releasing the buttons to enter CWM.Just make sure you release the buttons as soon as you see the Galaxy S logo.You will get passed the bootloop and enter CWM eventually!
If you still didn`t succeed, turn off phone and turn it on by using the 3 key combo to go directly into CWM.
Click to expand...
Click to collapse
thank you but i cannot pass the booloop, after i enter CWM and re-install the ICS rom i get bootloop again, after that, i cannot access the CWM again....
chientn said:
thank you but i cannot pass the booloop, after i enter CWM and re-install the ICS rom i get bootloop again, after that, i cannot access the CWM again....
Click to expand...
Click to collapse
flashing guide updated.
psyqiq said:
flashing guide updated.
Click to expand...
Click to collapse
Thank you for the guide
Data Network not working
Hi i installed this ROM today and it really seems flawless. I really love that it's on the SGS.
My problem is that i have never had a problem getting my data network to work when i have installed e new ROM. I have deleted and rebooted and reinstalled the APN in the mobile network settings but it's still not working.
Could someone tell me what the problem is?
elvismercado said:
Hi i installed this ROM today and it really seems flawless. I really love that it's on the SGS.
My problem is that i have never had a problem getting my data network to work when i have installed e new ROM. I have deleted and rebooted and reinstalled the APN in the mobile network settings but it's still not working.
Could someone tell me what the problem is?
Click to expand...
Click to collapse
do you have "Data enabled" checked in Mobile networks menu?
Should EFS be an EMPTY folder?
I noticed the EFS folder on this phone is empty, is that as it should be?
LazPL said:
I noticed the EFS folder on this phone is empty, is that as it should be?
Click to expand...
Click to collapse
you have lost your IMEI. EFS Folder should contain some files where IMEI is stored.
Use the guide to restore your IMEI.
Cheers ~
I just installed this rom and till now 0 problems, everything it's OK
Kernel: Semaphore ICS 1.2.0s
Modem: JVU
Just as it was, without any change....now let see how it's the battery life.
Thanks for the guide worked 100%
psyqiq said:
HOW TO BACKUP IMEI [EFS Folder] using Root Explorer :
1. After you flashed the GB Rom and obtained root, install Root Explorer.
2. Enter Root Explorer, go to root "/", long press "efs" folder and copy it to "external_sd".
4. After you flashed the ICS Rom, install Root Explorer.
5. Go to root "/", search for "/emmc", open "efs" folder you saved, press "Menu" button > Multi-Select > Select All > Copy.
6. Go back to root "/", open "efs" folder and paste the contents here, when asked, check to overwrite for all files.
7. Reboot
8. Done!
Click to expand...
Click to collapse
Is it really essential to to change anything in EFS folder unless any one face any problem related to IMEI no.
Till backup of EFS is fine but restoring EFS folder for no reason is not good thing
As i know efs folder contain very dedicated data.
If i am wrong just correct me..
Hey,hey,hey
Did you facing error while installing Full Gapps or Stock Gapps? which says installing gapps error because not enough system partition size.
Yes,i'm facing that bug too,but i have a solution for this issue.That bug can be happen because after flashing any Oreo ROM your system partition become smaller,sure that is not normal.
To fix this you need to "resize" your system partition. I almost resize my system partition using an "Extreme Way!" and if i do that maybe my phone goes bricked. Thanks to god i can found what the problem after try "try and error" method so it can be said,this solution I found because of accident.Ok enough
Ok this the simple method.
1. Download Flashable Busybox by @YashdSaraf https://sourceforge.net/projects/busybox-yds/files/Sep-06-17/Busybox-1.27.2-YDS-UNIVERSAL.zip/download original thread https://forum.xda-developers.com/android/software-hacking/tool-busybox-flashable-archs-t3348543
2. Flash your Oreo Custom ROM
3. Flash the flashable busybox.
4. Go to Wipe option
5. Check "system" partition
6. Press Advance Option > press "Resize" (don't worry,you don't need to reflash the rom)
7. Go to Wipe option again
8. Check "system" partition again
9. Press Advance Option > press "Repair"
10. Then,install the GAPPS ,and you can bit this Oreo with GAPPS berry Jam.
This method work perfectly for me.
This should work on Z00L and Z00T :good:
error 1 when repairing the partition. But it still worked. Thanks
Ichijou Raku said:
2. Flash your Oreo Custom ROM
3. Flash the flashable busybox.
4. Go to Wipe option
5. Check "system" partition
6. Press Advance Option > press "Resize" (don't worry,you don't need to reflash the rom)
7. Go to Wipe option again
8. Check "system" partition again
9. Press Advance Option > press "Repair"
10. Then,install the GAPPS ,and you can bit this Oreo with GAPPS berry Jam.
This method work perfectly for me.
This should work on Z00L and Z00T :good:
Click to expand...
Click to collapse
Hey does I need to do this every time when I installing stock gapps?? Or only for the first time??
mg712702 said:
Hey does I need to do this every time when I installing stock gapps?? Or only for the first time??
Click to expand...
Click to collapse
Same question here.
raiden_1115 said:
Same question here.
Click to expand...
Click to collapse
Bro....I just test it and yes you have to de this everytime when you installing oreo....and I didn't flash the busybox....but I successfully resize it.....then the question is what's for the busybox is??
Doing this every installing oreo is,yes...
I think,cannot resize partition is only happened when upgrading Nougat to Oreo ,because every changing an oreo rom to another oreo rom,I dont have to install busybox again..
Busybox...mmmmm try flashing oreo rom after a nougat one,then resize Partition you will facing an error code on twrp say "resize error blablablabla" (or another,im forget what it say) ,for that,im thinking why i cannot resize the partition,While still in nougat I still can resize partition without any problem..And as you know, busybox contains a number of commands that can run in the terminal, and "resizing command" is contained within the busybox ..
Oh,im not responsible with any error after trying this method,But all this time I have never experienced any errors because this method..
Im still a newbie on android,i dont have a lot experience on android..As I said ,i found this method by trying "try and error" method,trying installing nougat first then oreo,trying installing boot.img first then oreo,and much more attempt..and i still got same error hahaha.. frustrated because cannot installing large gapps..
Then i found this method,just try this method and tell me if you found an error after trying this method..
But I can be sure it will not happen just because resize the partition, because resizing partition here instead of changing the size of partition system becomes bigger,Resize here only returns the size of the corrupted partition system
i got an error when resizing and repairing on my lg v20 h918, I still followed steps and ended up with the error after gapp installation. I am back to a blinking black screen after the lg logo. I think my phone is a lost cause.
Users of TWRP 3.1 on Doogee Mix (including myself) faced the mammoth problem of an encrypted storage after unlocking the bootloader and flashing the custom recovery. This problem is not peculiar to the Doogee Mix, any other device with TWRP 3.1+ will likely face the same issue and the solution preferred here would work.
By default, your device storage is encrypted (Settings > Security > Encryption) and any TWRP from 3.1+ respects that protocol.
This means that the internal storage would be showing 0mb because it can't be mounted, (no) thanks to the encryption.
Previous versions of TWRP (eg 3.0.3) could easily decrypt the device using the default password but from version 3.1, things changed.
SOLUTION
Needed:
1. An unlocked bootloader
2. TWRP installed (download from the TWRP thread)
3. An SD CARD (or USB OTG)
4. Magisk.zip (latest version, copy it to the SD card)
NOTE: Copy/Backup your files from your internal storage into your PC as this process would wipe everything from the internal storage.
STEPS
> With the bootloader unlocked and TWRP flashed, boot into recovery.
> The screen might be dark when in recovery, just press the power button and the the vol- button, it'll turn ON. Then swipe to unlock.
> You can change the language to English by clicking on the 2nd rectangle by the right above the swipe function.
> Tick "do not show again" and the swipe to allow modification.
> Confirm device encryption by clicking "Backup" or "Install", if the storage size is 0mb or no folder is showing while trying to install, then the device is encrypted.
> Go back, click "Wipe"
> You can choose to Factory reset, Format data or Advanced wipe > tick /data. Either way, it's going to wipe EVERYTHING in the internal storage (that's the purpose of device encryption, to prevent unauthorized access to the storage). However, I recommend you choose "FORMAT DATA"
> If you chose "Format data", then type yes in the next screen and swipe to format.
> When completed, go home, click Reboot and choose Recovery to boot into recovery (very important, do not reboot the phone into system otherwise you'll start all over. Reboot into recovery, not system).
> When in the recovery, click install > select storage > SD card (or USB OTG) (note that the internal storage will display as normal but remember it is now empty following the data reset)
> Navigate to the Magisk in /Sdcard (or USB OTG) and install.
> When completed, you can now reboot safely into system.
> Complete the phone setup and Open Magisk Manager. Notice that Magisk is now installed and "Preserve force encryption" is now unticked". You can also go to Settings > Security > Encryption and notice that it will ask you to encrypt your device, meaning it is decrypted now.
> The next time you will boot into recovery, TWRP may still be in Russian language, just change it one more time and you are good to go.
> Now you can flash anything you want including Xposed (download latest version from the official Xposed thread/website).
That's all. Cheers! Happy tweaking
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
I love you broo!!
I was like 5 hours with this encryption problem without being able to solve it, Thank you very much. I LOVE YOU! Hahaha :good::victory::victory::fingers-crossed:
Cheers!
dwapking said:
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
Click to expand...
Click to collapse
How to you get OTA update when you are rooted? I can't
dwapking said:
If you try to install font, module, busybox or any other system framework/tweak without success, then change the installation mode to recovery.
Recommended:
iFont
Busybox for Android or the busybox from Magisk Repo
iFont: switch to "My" tab > Settings > Installation mode > Recovery
Busybox for Android: tap settings (top right) > Installation mode > Recovery
Click to expand...
Click to collapse
Your screenshot of the about phone page, shows you are on kernel 3.18, thought device had kernel 4.4?
Ersid Kapaj said:
How to you get OTA update when you are rooted? I can't
Click to expand...
Click to collapse
Being rooted shouldn't prevent you from getting the OTA.
OTA's arrive based on System language, region, model/variant, etc.
If you still can't get the OTA and your language is set to "English (US or UK)", then download the latest flashable ROM and flash via PC. It should help for subsequent OTA's.
If you have done this before and still stuck, then just download the local update file and install.
dwapking said:
Being rooted shouldn't prevent you from getting the OTA.
OTA's arrive based on System language, region, model/variant, etc.
If you still can't get the OTA and your language is set to "English (US or UK)", then download the latest flashable ROM and flash via PC. It should help for subsequent OTA's.
If you have done this before and still stuck, then just download the local update file and install.
Click to expand...
Click to collapse
That's the problem. When i click check for update it says "Root detected" and then it says that my system is up to date. I don't want to delete anything from my phone, that's why i don't do it via PC.
have another problem witch F2SF I cant flash any modules in magisk
Magisk.img mount failed do you have this problem?
Ersid Kapaj said:
That's the problem. When i click check for update it says "Root detected" and then it says that my system is up to date. I don't want to delete anything from my phone, that's why i don't do it via PC.
Click to expand...
Click to collapse
I have root, and I don't get any such errors when I check for updates. Perhaps you should just backup ur apps/OS (with TB & TWRP) and files in a PC then flash a clean updated ROM.
mrmazak said:
Your screenshot of the about phone page, shows you are on kernel 3.18, thought device had kernel 4.4?
Click to expand...
Click to collapse
The kernel version is correct. The 4.4 is only shown in CPU_Z app
TheSpartanM4 said:
have another problem witch F2SF I cant flash any modules in magisk
Magisk.img mount failed do you have this problem?
Click to expand...
Click to collapse
Yes... Some modules (Viper4Android, Busybox NDK) did flash successfully (though not mounted in Magisk modules section but are working just fine) while many others refused to install.
I am currently trying to verify the cause. For now, no solution yet.
dwapking said:
I have root, and I don't get any such errors when I check for updates. Perhaps you should just backup ur apps/OS (with TB & TWRP) and files in a PC then flash a clean updated ROM.
Click to expand...
Click to collapse
I have downloaded the update once but when i try to install it says the it's rooted and can't install. Since then it's the same problem.
Yes of course, before any update is installed, root integrity check is performed. Once any modifications has been detected, it will abort.
That's why I said you should flash back your STOCK SYSTEM, RECOVERY AND BOOT, since they're the partitions affected by the root.
Don't forget to wipe the data of "Wireless Update" before proceeding to install.
ok, i'm gonna give this a try once i'm properly awake. i had been trying to install magisk via adb push and it would not work, so we'll see how this does. thanks!
Does safetynet pass for anyone? MobileIron still detects the phone as rooted with Magisk installed...
I got it to work! I have TWRP installed, I have Magisk working, and Safetynet check passes. I can't post screenshots because I don't have enough posts, but I suppose I have root now! ...it's not nearly as exciting on a non-bloated phone with no available roms. But I think we're maybe ready to say we officially have root? I can't learn coding or I'd try to make my own rom.
Cheers!
Doogee Mix only reboots to Doogee Splash which warns: Orange State
Your device has been unlocked and can't be trusted. YOur device will boot in 5 seconds. Then TWRP boots in English instead of Russian. Thats all I get. Is there a custom ROM for Doogee Mix? Did I wiped the OS? Thank you for getting me out off the Encryption - loop.
Can someone please help me understand why I can only boot into TWRP Recovery now???
THANKS TO THEWH1TEAGLE FOR THE METHOD!! ALL CREDITS TO HIM!
Let's get started.
You will need:
TWRP (https://forum.xda-developers.com/galaxy-a10/how-to/how-to-root-samsung-galaxy-a10-install-t4074343).
GSI rom (https://sourceforge.net/projects/expressluke-gsis/files/) (it will be in a compressed folder, you have to extract and move the .img file to your SD Card.) [HAS TO BE A64AB]
A brain.
Installing the GSI rom...
Reboot into TWRP recovery.
Go to Wipe > Format Data > Type in "yes" > Tap the check icon on the keyboard and wait.
Go back to Wipe > Then to Advanced Wipe > And select "Dalvik / ART Cache", "Cache", and "Data".
After that's done, go to install and select Install Image and find your .img rom you downloaded.
Tap on it and select "System Image".
Then after the installation is complete, go to Wipe > Swipe to Factory Reset (at the bottom).
If your rom does not include Gapps (which it probably won't) then install it now.
Then reboot your device and enjoy!
anyone tested it ?
Mestre Samurai said:
anyone tested it ?
Click to expand...
Click to collapse
will work no matter what. when you boot into system the screen should dim then reboot, then it will boot into the rom
Downaroo said:
will work no matter what. when you boot into system the screen should dim then reboot, then it will boot into the rom
Click to expand...
Click to collapse
it didn't work here
Mestre Samurai said:
it didn't work here
Click to expand...
Click to collapse
Can you tell me what exactly you did? it should work.
Downaroo said:
THANKS TO THEWH1TEAGLE FOR THE METHOD!! ALL CREDITS TO HIM!
Let's get started.
You will need:
TWRP (https://forum.xda-developers.com/galaxy-a10/how-to/how-to-root-samsung-galaxy-a10-install-t4074343).
GSI rom (https://sourceforge.net/projects/expressluke-gsis/files/) (it will be in a compressed folder, you have to extract and move the .img file to your SD Card.)
A brain.
Installing the GSI rom...
Reboot into TWRP recovery.
Go to Wipe > Format Data > Type in "yes" > Tap the check icon on the keyboard and wait.
Go back to Wipe > Then to Advanced Wipe > And select "Dalvik / ART Cache", "Cache", and "Data".
After that's done, go to install and select Install Image and find your .img rom you downloaded.
Tap on it and select "System Image".
Then after the installation is complete, go to Wipe > Swipe to Factory Reset (at the bottom).
If your rom does not include Gapps (which it probably won't) then install it now.
Then reboot your device and enjoy!
Click to expand...
Click to collapse
(there can be a problem when installing gapps, such as ERROR 20 and ERROR 70, error 20: reflash rom or factory reset, error 70: system partition is not big enough, to fix this, go to Wipe > Advanced Wipe > Select System > Select More at the bottom > Select Resize partition, and click ok. It will say an error, so just retry the resize.)
Downaroo said:
THANKS TO THEWH1TEAGLE FOR THE METHOD!! ALL CREDITS TO HIM!
Let's get started.
You will need:
TWRP (https://forum.xda-developers.com/galaxy-a10/how-to/how-to-root-samsung-galaxy-a10-install-t4074343).
GSI rom (https://sourceforge.net/projects/expressluke-gsis/files/) (it will be in a compressed folder, you have to extract and move the .img file to your SD Card.)
A brain.
Installing the GSI rom...
Reboot into TWRP recovery.
Go to Wipe > Format Data > Type in "yes" > Tap the check icon on the keyboard and wait.
Go back to Wipe > Then to Advanced Wipe > And select "Dalvik / ART Cache", "Cache", and "Data".
After that's done, go to install and select Install Image and find your .img rom you downloaded.
Tap on it and select "System Image".
Then after the installation is complete, go to Wipe > Swipe to Factory Reset (at the bottom).
If your rom does not include Gapps (which it probably won't) then install it now.
Then reboot your device and enjoy!
Click to expand...
Click to collapse
I tried this yesterday on numerous ROM's from ExpressLuke's GSI's and was unable to get it working. The closest I got was LineageOS 16 and Resurrection Remix v7 boot animations but they never ended or got anywhere. I don't know much about android flashing, custom roms etc. but I followed instructions carefully. It would be helpful to gather some logs but I don't know how I can do that with Lineage and RR.
It possibly could be something to do with not clearing the phone properly, but I had done this numerous times in TWRP Recovery. There was also a step in afaneh92's post where he explained the internal storage was unreadable until you installed samsung-multidisabler and so this has been an issue in the past.
Also, my variant is the international variant (SM-A105FN) where the only difference from it's brother (SM-A105F) is that the international variant has dual sim slots, this will be my next step into trying to get RR or LineageOS to work, to remove my second sim.
There is not a problem with the model as I am using the same model.
Can you tell me the gapps package you are using?
I am pretty sure I know the problem..
Downaroo said:
Can you tell me what exactly you did? it should work.
Click to expand...
Click to collapse
Mmmmm... Did you tried to disable dm verifying? Flash dis
I forgot a step, after you install the GSI, you have to install a kernel, (which I will attach), then you proceed with the steps. Credits to @Chatur27 for the kernel development
Downaroo said:
I forgot a step, after you install the GSI, you have to install a kernel, (which I will attach), then you proceed with the steps. Credits to @Chatur27 for the kernel development
Click to expand...
Click to collapse
Simply edit the message. I stuck at bootloop after I followed your steps. So screen dms then it reboots. Screen dims again then it reboots. It did that for about infinity times. Before I gave up and installed lineage 18 again.
Downaroo said:
I forgot a step, after you install the GSI, you have to install a kernel, (which I will attach), then you proceed with the steps. Credits to @Chatur27 for the kernel development
Click to expand...
Click to collapse
AND I have Google android 12 gsi. How to install it using twrp? There is system.img and vbmeta.img help me pls how to install it using twrp?
can I install GSIs over a custom ROM? such as Lineage 20 running the Eureka kernel instead of the stock ROM?