Related
This will be an often-updated guide to all the latest successes of getting a quality port of CyanogenMod, a custom Froyo based Android distribution.
This thread was originally intended to be specific to the Coby Kyros, but since most issues relate to all Telechips tablets, it may prove useful to owners of other such devices as well.
Things we have working: Touchscreen, Screen Roation, WiFi (Connects to AP and Ad-Hoc), Market, Texting via Google Talk.
Things we have kinda working: WiFi can be a little wanky, but if you disable and re-enable it works fine.
Things that do not work/Issues: Some apps not working (like Angry Birds) due to sdcard not being properly addressed, video play back, sound recording is very nasty, missing on screen volume controls, occasionally the input box is not updated with what you're typing, but when you hide the keyboard the text is there.
Further Reading:
Most of the development for the Kyros 7015 has taken place in this thread.
and the developement of Cyanogen for Telechips tablets has taken place in the thread (on slatedroid.com).
Also check out my tutorial for Getting the Most Out of Eclair (Android 2.1) for this same device.
Instructions
1. Download and install ClockworkMod .
2: Preparations. If you have not already, install Android SDKto your PC. Download bootimage and system image. Create a "Cyanogen" folder in the clockwork/backup folder on your SD card and unzip both files into this folder. I also renamed and placed my recovery.img in here.
Contents of /Cyanogen
Code:
boot.img
nandroid.md5
recovery.img
system.img
3: Getting Some Files from Eclair. Connect your tablet to your PC and issue the following commands using ADB (Note: This step is to be done from Android 2.1, not from a previous version of CyanogenMod. If you already have CyanogenMod install, please revert to Android 2.1 to retrieve these files)
Code:
adb pull /sys/class/input/input1/calc_table calc_table
adb pull /data/softmac softmac
This should copy the calc_table and softmac files to the directory where ADB is located. Leave them where they are, and place build.prop and sensors.tcc92xx, from COBY7015-fixpack in there as well.
4: "Restoring" CyanogenMod. Boot into recovery mode (hold down front button and press the reset button on back of device). You should now be in ClockworkMod. IF YOU HAVEN'T ALREADY, MAKE A BACKUP! Choose "Wipe data / factory reset" and then "backup and restore." Restore from Cyanogen folder.
5: Restoring Some Key Files. With your tablet connected to your PC, issue the following ABD commands, taking care to keep your tablet awake:
Code:
adb remount
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb push calc_table /system/etc/
adb shell chmod 644 /system/etc/calc_table
adb push sensors.tcc92xx.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/sensors.tcc92xx.so
adb push softmac /data/softmac
adb shell chmod 644 /data/softmac
adb reboot
After your tablet finishes rebooting, you should notice you have a working touch screen.
6: Enabling Google Apps. Download gapps-mdpi-tiny-20101020-signed.zip and MarketUpdateFroyoHdpi.zip. Place onto your SD card and reboot into recovery.vChoose "Install Zip from SDcard" and install gapps-mdpi-tiny-20101020-signed.zip and then MarketUpdateFroyoHdpi.zip. Reboot and accept the terms of the market!
7: Texting using Google Voice. Here is how to text with Google voice. You will need a working android phone (probably needs to be rooted) with Titanium Backup installed. Set up Google Voice on the phone-- make sure you opt for the Google phone number as that is the number you will be texting from. Once up and running, back up the program using Titanium. On the tablet, install Titanium Backup and use it to restore the Google Voice program (App+Data) to your tablet. (You may have to copy the backup files to the Titanium directory on the INTERNAL drive.) Once Google Voice Launches, switch back to Titanium Backup-- do not try to set up Google Voice. Titanium backup will then restore the data for Google Voice. You should now be able to text from your tablet.
This is all I have right now, more to follow.
Wouhou, first post!
thanks for that thread. Really great idea. I'll contributed at the best of my knowledge. Really like what you guys are doing and hope to have CyanogenMod fulling (or almost fulling) working.
stoned99 said:
Wouhou, first post!
thanks for that thread. Really great idea. I'll contributed at the best of my knowledge. Really like what you guys are doing and hope to have CyanogenMod fulling (or almost fulling) working.
Click to expand...
Click to collapse
Hope this helps, and I hope we can get everyone working on Cyanogen for the 7015 over to this thread to keep from getting this and the 2.1 root/mod project from getting too intermingled/confused.
Thanks. Finally had 15 minutes to install it and test it. Your procedure worked like a charm!
Only thing: Just add to fun_'s proedure for build.prop a shell like this
adb shell chmod 644 /system/build.prop
Great guide!
stoned99 said:
Thanks. Finally had 15 minutes to install it and test it. Your procedure worked like a charm!
Only thing: Just had to fun_'s proedure for build.prop a shell like this
adb shell chmod 644 /system/build.prop
Great guide!
Click to expand...
Click to collapse
Thanks, I got that error fixed.
I uploaded 12/12 build. to avoid confusion, old build was removed.
please update #2.
sorry for this inconvenience.
Fun_
So are the files under the obsolete folder now on that website.
Also wondering if someone can do a clockworkmod of the image
with most of the files edited I think for new peeps this will make it easier.
I have not flashed mine yet as I use it for video alot and
if that isn't working then it doesnt do me much good right now
adamdietrick could you modify your procedure for the new one and also add to do a nandroid backup as some new people with Android might not know it's important. I tested the procedure it's working fine.
so globally it would be something like that. Please modify it so it can be more easily to follow:
1) clockwork
2) Backup your nand: ClockworkMod recovery, backup and restore, backup
3) When booted in Eclair (stock rom):
adb usb
adb pull /sys/class/input/input1/calc_table calc_table
adb pull /data/softmac softmac
*be sure to know where the files are copied to your pc because you'll need to add them back on your device later.
4) Copy all files (system.img, boot.img, nandroid.md5) in the clockwordmod backup folder on sdcard
5) Restore from backup, choose Cyanogenmod
6)adb remount
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb push calc_table /system/etc/
adb shell chmod 644 /system/etc/calc_table
adb push sensors.tcc92xx.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/sensors.tcc92xx.so
adb push softmac /data/softmac
adb shell chmod 644 /data/softmac
**at some point, you might loose connectivity with the device and waking up from sleep might not help, just unplug the usb cable, plug back in and type adb usb in the command prompt window
adb reboot
... continue with your current step 6 to 8 (install Gapps, market update and Google Voice)
Procedure was mostly taken from the readme file of fun_ so all credits go to him.
stoned99 said:
adamdietrick could you modify your procedure for the new one and also add to do a nandroid backup as some new people with Android might not know it's important. I tested the procedure it's working fine.
so globally it would be something like that. Please modify it so it can be more easily to follow:
1) clockwork
2) Backup your nand: ClockworkMod recovery, backup and restore, backup
3) When booted in Eclair (stock rom):
adb usb
adb pull /sys/class/input/input1/calc_table calc_table
adb pull /data/softmac softmac
*be sure to know where the files are copied to your pc because you'll need to add them back on your device later.
4) Copy all files (system.img, boot.img, nandroid.md5) in the clockwordmod backup folder on sdcard
5) Restore from backup, choose Cyanogenmod
6)adb remount
adb push build.prop /system/
adb shell chmod 644 /system/build.prop
adb push calc_table /system/etc/
adb shell chmod 644 /system/etc/calc_table
adb push sensors.tcc92xx.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/sensors.tcc92xx.so
adb push softmac /data/softmac
adb shell chmod 644 /data/softmac
**at some point, you might loose connectivity with the device and waking up from sleep might not help, just unplug the usb cable, plug back in and type adb usb in the command prompt window
adb reboot
... continue with your current step 6 to 8 (install Gapps, market update and Google Voice)
Procedure was mostly taken from the readme file of fun_ so all credits go to him.
Click to expand...
Click to collapse
Starting work on it now (that I'm not sleeping). This is what happens when fun_ brings out new version at bed time!
LOL
don't worry, you can do it after your sleep. It's just that if some people moved to CyanogenMod with the current guide, they'll need to restore their eclair nanddroid backup to their device to grab the calc and software or use linux to mount system.img and extract calc_table and softmac. I can provide you the linux procedure in case you want to add it (for people who don't want to restore their eclair rom)
stoned99 said:
LOL
don't worry, you can do it after your sleep. It's just that if some people moved to CyanogenMod with the current guide, they'll need to restore their eclair nanddroid backup to their device to grab the calc and software or use linux to mount system.img and extract calc_table and softmac. I can provide you the linux procedure in case you want to add it (for people who don't want to restore their eclair rom)
Click to expand...
Click to collapse
That would be great to have. I had to restore mine last night to run this procedure.
Weird, the procedure I used to use with my Android file with my iphone (I had dual boot IOS and Android) doesn't work. I might not be the same systemfile. I'll try something else and let you know if I solve it
Just out of curiosity, (as I don't have time to read through the slatedroid forum) Has there been anything figured out on:
1. video playing on cyanogen
2. games loading full size ( if I change the lcd density it solves this problem but then everything is way too large, is there a way to make it to where the density changes for the games and only the games?)
3. Games that install to the sd card having problems i.e. angry birds, and asphalt?
I know these have probably been answered over on slatedroid but like I said I just don't have time to read through over 200 pages, especially where most of it is stupid newbie crap that is probably making it very hard for asure, venomous, and fun_ to get any actual feedback on stuff.
I was able to mount the system and ramdisk. Unfortunately it seems the files (calc_table and softmac) are not in there. I see a folder called sys and a folder called data in the ramdisk but don't see any files inside. Maybe it's in the kernel. I was able to extract the kernel from the boot.img but can't mount it. Oh well, people will have to restore from their nandroid backup if they want to pull the files.
Sorry
stoned99 said:
I was able to mount the system and ramdisk. Unfortunately it seems the files (calc_table and softmac) are not in there. I see a folder called sys and a folder called data in the ramdisk but don't see any files inside. Maybe it's in the kernel. I was able to extract the kernel from the boot.img but can't mount it. Oh well, people will have to restore from their nandroid backup if they want to pull the files.
Sorry
Click to expand...
Click to collapse
softmac may be in data.img of eclair nandroid backup.
calc_table is only in live system. please restore eclair firmware and reboot.
dhadlock said:
1. video playing on cyanogen
Click to expand...
Click to collapse
no hardware decoding yet. please use rockplayer for armv6+vfp (consume CPU power...)
dhadlock said:
2. games loading full size ( if I change the lcd density it solves this problem but then everything is way too large, is there a way to make it to where the density changes for the games and only the games?)
Click to expand...
Click to collapse
try Compatibility off in SpareParts
dhadlock said:
3. Games that install to the sd card having problems i.e. angry birds, and asphalt?
Click to expand...
Click to collapse
I have no idea.
I'm suffering where/how to talk worthfully
(here is OK, of course
fun_ said:
no hardware decoding yet. please use rockplayer for armv6+vfp (consume CPU power...)
try Compatibility off in SpareParts
I have no idea.
I'm suffering where/how to talk worthfully
(here is OK, of course
Click to expand...
Click to collapse
Just to let you know, I have tried the disabling the compatibility setting with no success.
adamdietrick said:
Just to let you know, I have tried the disabling the compatibility setting with no success.
Click to expand...
Click to collapse
what app "no success"?
recently some tablets with large screen are sold from major company. it may make things better with app update... (just my hope, sorry)
fun_ said:
what app "no success"?
recently some tablets with large screen are sold from major company. it may make things better with app update... (just my hope, sorry)
Click to expand...
Click to collapse
The only two I have had issues with. Kitchen timer, raging tunder.
Call me what ever you want, but it's too late...
I have a US WiFi Zoom and I accidentally deleted the "framework-res.apk" in /system/framework/, but I do have a backup in /mnt/sdcard/
Fastboot is still working, but I can no longer boot in recovery (I have/had CWM installed).
The normal startup get stuck on the boot screen.
As far as I understand you cannot flash a file directly from fastboot, but need a .zip file made in Linux for this purpose.
As I do not have skills, nor a Linux OS to build this, I would very much appreciate if someone could help out here, or direct me how to flash a file directly from fastboot.
Thanks in advance,
arc
Get wifi system image and fastboot flash system system.img
Or if you have USB debugging enabled, just use adb to copy the framework-res
Thanks, sangreal06,
I believe the USB debugging is only getting me into the /mnt/ folder.
But, if I understand you right, I can grab roebeet's root-prepped and updated HRI66 system.img here:
http://forum.xda-developers.com/showthread.php?t=995785
and flash it by:
Code:
fastboot flash system system.hri66.rootprepped.img
fastboot reboot
After the device reboot, you will need adb to fix su permissions:
Code:
adb remount
adb shell chmod 6755 /system/bin/su
is this correct?
Yes, but that file is for 3G. It is not compatible with wifi model
Thanks, sangreal06, for catching that one, it probably saved me a lot of grief. I guess the one to use will be Scourge1024's:
Stock MZ604 (Xoom Wi-Fi) recovery.img
or, am I better way of waiting for the stock SBF, announced to arrive within short?
Also, will this require that I re-root?
Thanks in advance,
arc
Boot into clockworkmod and flash the zip below.
How to get back into recovery: http://forum.xda-developers.com/showthread.php?t=1041192
File: http://dl.dropbox.com/u/18315605/XDA/Framework.zip
Thanks so much bwcorvus,
I'll d/l the recovery.img at [RECOVERY] ClockworkMod Recovery v3.0.2.5
and....
It worked perfectly, I'm back! I guess that's a mistake I wont do again. I really owe you one, put it on my tab.
arc
I ran into bit of a problem with my HTC One m7 and I have to return to a stock ROM. There are a couple issues with this as there are no RUU files for a Bell Mobility (Canada) phone but there is a stock nandroid backup http://forum.xda-developers.com/showthread.php?t=2428276
So I downloaded the nandroid backup and attempted to restore it through CWM. Problem is I cannot seem to locate the unzipped folder in CWM restore when running the recovery on my phone. I have a mac so adb commands are slightly different and I am unsure to how to properly push the folder into the CWM backups. I also tried in Android File Transfer but the backups folders are hidden. Could anyone possibly direct me on how to properly attempt to do so? It would be much appreciated.
Thanks
RobotRob said:
I ran into bit of a problem with my HTC One m7 and I have to return to a stock ROM. There are a couple issues with this as there are no RUU files for a Bell Mobility (Canada) phone but there is a stock nandroid backup http://forum.xda-developers.com/showthread.php?t=2428276
So I downloaded the nandroid backup and attempted to restore it through CWM. Problem is I cannot seem to locate the unzipped folder in CWM restore when running the recovery on my phone. I have a mac so adb commands are slightly different and I am unsure to how to properly push the folder into the CWM backups. I also tried in Android File Transfer but the backups folders are hidden. Could anyone possibly direct me on how to properly attempt to do so? It would be much appreciated.
Thanks
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Too bad the M7 doesn't come with a card slot. If it did, you could have made a "last known bad" backup with CWM to make CWM create the appropriate backup folders on the MicroSD and then dump the right backup into that folder. Ah well.
I would adb push the backup files, one by one to internal storage (something like /sdcard, can "adb shell" to poke around for the right path), and then "adb shell" in to copy/move the files to the right CWM backup folder (I used TWRP for so long, I forget the full path).
But then again, i looked for the guide you may have followed:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [GUIDE] Return to stock for Canadian HTC One Users
You need to have TWRP, not CWM, to read this nandroid.
Follow the steps in the first post, and you should be good to go (any questions can go in that thread as well). Hope this helps.
joel.maxuel said:
Hello, and welcome to XDA!
Too bad the M7 doesn't come with a card slot. If it did, you could have made a "last known bad" backup with CWM to make CWM create the appropriate backup folders on the MicroSD and then dump the right backup into that folder. Ah well.
I would adb push the backup files, one by one to internal storage (something like /sdcard, can "adb shell" to poke around for the right path), and then "adb shell" in to copy/move the files to the right CWM backup folder (I used TWRP for so long, I forget the full path).
But then again, i looked for the guide you may have followed:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [GUIDE] Return to stock for Canadian HTC One Users
You need to have TWRP, not CWM, to read this nandroid.
Follow the steps in the first post, and you should be good to go (any questions can go in that thread as well). Hope this helps.
Click to expand...
Click to collapse
Hey man thanks for replying. So I flashed the TWRP (which I actually had previously) and now I am just having trouble locating the actual backup folder, it seems to be no existent. I did step 4 so the Backup folder should be created then right? Now im on step 6 but I cant find the folders. Maybe im missing soemthing..
RobotRob said:
Hey man thanks for replying. So I flashed the TWRP (which I actually had previously) and now I am just having trouble locating the actual backup folder, it seems to be no existent. I did step 4 so the Backup folder should be created then right? Now im on step 6 but I cant find the folders. Maybe im missing soemthing..
Click to expand...
Click to collapse
If you are on a custom ROM, your /sdcard/ folder may be called something else. Trace your steps by doing this from a console on your PC (with the cable connected between, and ADB debugging enabled):
Code:
adb shell
cd /sdcard
ls
cd TWRP
ls
cd BACKUPS
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
You may get stuck on line two, maybe along the lines of "No such file or directory". If so, replace step two with:
Code:
cd /storage
ls
cd <OUTPUT FOLDER of LAST COMMAND - should start with sdcard>
All this will give you the path in which to push the files to.
Also, don't be afraid to use the experts found in that guide by posting there. I don't have an M7 so I am basing my thoughts off different devices.
Hope this helps.
joel.maxuel said:
If you are on a custom ROM, your /sdcard/ folder may be called something else. Trace your steps by doing this from a console on your PC (with the cable connected between, and ADB debugging enabled):
Code:
adb shell
cd /sdcard
ls
cd TWRP
ls
cd BACKUPS
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
cd <OUTPUT FOLDER of LAST COMMAND>
ls
You may get stuck on line two, maybe along the lines of "No such file or directory". If so, replace step two with:
Code:
cd /storage
ls
cd <OUTPUT FOLDER of LAST COMMAND - should start with sdcard>
All this will give you the path in which to push the files to.
Also, don't be afraid to use the experts found in that guide by posting there. I don't have an M7 so I am basing my thoughts off different devices.
Hope this helps.
Click to expand...
Click to collapse
Hey man, thanks for your help. I was able to find the correct path by doing a backup, just of boot.img in recovery and that shows where the file is stored /data/media/0/TWRP/BACKUPS/serial number/backup#.
So now I am trying to access the path through adb shell (so I can push the stock files) but I am geting "Permission denied".
Do I need S-Off to go about doing this??
RobotRob said:
Hey man, thanks for your help. I was able to find the correct path by doing a backup, just of boot.img in recovery and that shows where the file is stored /data/media/0/TWRP/BACKUPS/serial number/backup#.
So now I am trying to access the path through adb shell (so I can push the stock files) but I am geting "Permission denied".
Do I need S-Off to go about doing this??
Click to expand...
Click to collapse
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
joel.maxuel said:
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
Click to expand...
Click to collapse
I entered shell. Then entered su , but it still says Permission denied..?
joel.maxuel said:
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
Click to expand...
Click to collapse
Sorry I... I uninstlaled supersu app by accident so that makes sense... Re-installed it and will try to push files.
joel.maxuel said:
Just need to enter "su" (without the quotes, for super user) after entering shell, before copying the files. Hope this helps.
Click to expand...
Click to collapse
I can reach the path no problem now in su with adb shell /data/media/0/TWRP/BACKUPS/serial#/backupfolder/
but what is the proper command to copy the unzipped nandroid backup files to the phone?
RobotRob said:
I can reach the path no problem now in su with adb shell /data/media/0/TWRP/BACKUPS/serial#/backupfolder/
but what is the proper command to copy the unzipped nandroid backup files to the phone?
Click to expand...
Click to collapse
Hi,
That would be (while outside of the unzipped folder):
Code:
adb push <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
e.g: (example partially modified for my smartwatch)
Code:
adb push 2015-11-09-LCA43 /data/media/0/TWRP/BACKUPS/04a0e5ac02a27e76/
Then when you are in TWRP, look for the name of the unzipped folder.
EDIT: BTW, you may have permission errors this way like you did before in the exploring phase. So you may need to:
Code:
adb push <name of unzipped folder> /data/media/0/
adb shell
su
mv <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
joel.maxuel said:
Hi,
That would be (while outside of the unzipped folder):
Code:
adb push <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
e.g: (example partially modified for my smartwatch)
Code:
adb push 2015-11-09-LCA43 /data/media/0/TWRP/BACKUPS/04a0e5ac02a27e76/
Then when you are in TWRP, look for the name of the unzipped folder.
EDIT: BTW, you may have permission errors this way like you did before in the exploring phase. So you may need to:
Code:
adb push <name of unzipped folder> /data/media/0/
adb shell
su
mv <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
Click to expand...
Click to collapse
I still get permission errors when trying to push it to /data/media/0/
Ill try doing it to /sdcard/ , then adb shell , su , mv <name of unzipped folder>/data/media/0/TWRP/BACKUPS/<serial#>/
joel.maxuel said:
Hi,
That would be (while outside of the unzipped folder):
Code:
adb push <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
e.g: (example partially modified for my smartwatch)
Code:
adb push 2015-11-09-LCA43 /data/media/0/TWRP/BACKUPS/04a0e5ac02a27e76/
Then when you are in TWRP, look for the name of the unzipped folder.
EDIT: BTW, you may have permission errors this way like you did before in the exploring phase. So you may need to:
Code:
adb push <name of unzipped folder> /data/media/0/
adb shell
su
mv <name of unzipped folder> /data/media/0/TWRP/BACKUPS/<serial#>/
Click to expand...
Click to collapse
Thanks so mucb man! I had to adb push to /sdcard/, for some reason pushing to /data/media/0/ was still giving me permission denied. Once pushed, I did the following to move it to the correct path;
adb shell
su
mv 'nandroid backup unzipped folder' /data/media/0/TWRP/BACKUPS/serial#/
Then ran recovery and restored the stock backup.
Worked.
One big problem... I had to restore because my IMEI was gone when I flashed custom ROM. So after all of this, my IMEI is still unkown and lost. I do know what my IMEI nukber is though because I wrote it down. Is there anway I can get it back??
RobotRob said:
Thanks so mucb man! I had to adb push to /sdcard/, for some reason pushing to /data/media/0/ was still giving me permission denied. Once pushed, I did the following to move it to the correct path;
adb shell
su
mv 'nandroid backup unzipped folder' /data/media/0/TWRP/BACKUPS/serial#/
Then ran recovery and restored the stock backup.
Worked.
One big problem... I had to restore because my IMEI was gone when I flashed custom ROM. So after all of this, my IMEI is still unkown and lost. I do know what my IMEI nukber is though because I wrote it down. Is there anway I can get it back??
Click to expand...
Click to collapse
So your EFS partition got borked. That's not good.
Unfortunately, even with the IMEI number known on paper, there is very little you can do to get that repaired. I will suggest this thread:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [Q] No IMEI or Baseband
Read it head-to-toe before adding a post, so you have an idea as to which are the right questions to ask. EFS is unique to the device, and once it's gone, (in almost all cases) it can only be rebuilt through a warranty service unfortunately. Which is why I do full block backups before I really mess around with a device. But, hindsight is 20/20.
Sadly there is nothing else I can suggest. Glad you made it this far though.
Best of luck!
joel.maxuel said:
So your EFS partition got borked. That's not good.
Unfortunately, even with the IMEI number known on paper, there is very little you can do to get that repaired. I will suggest this thread:
> HTC One (M7) > One (M7) Q&A, Help & Troubleshooting > [Q] No IMEI or Baseband
Read it head-to-toe before adding a post, so you have an idea as to which are the right questions to ask. EFS is unique to the device, and once it's gone, (in almost all cases) it can only be rebuilt through a warranty service unfortunately. Which is why I do full block backups before I really mess around with a device. But, hindsight is 20/20.
Sadly there is nothing else I can suggest. Glad you made it this far though.
Best of luck!
Click to expand...
Click to collapse
Ok thanks for all your help. I had only wanted to get it back to stock so I could unlock the phone from the carrier and put a new im card in it.
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Shedopen123 said:
I have a Samsung galaxy tab 2.One day as I decided to wipe everything,i noticed a message in the recovery mode saying unable to mount efs.I cant open my tablet or anything.After looking on the internet,people were telling me to flash a custom recovery like CWM.In order to do that I need to root my tablet.To root my tablet I need to enable USB debugging,which I can't because I can't access it.Can you help me please?
Click to expand...
Click to collapse
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Boot to download mode and flash CWM or TWRP for your model number via Odin. Then you boot into CWM or TWRP and flash SuperSU.zip to root your device. I suggest TWRP instead of CWM.
Then, if you have TWRP you can use the built in file manager in TWRP to pull a copy of your build.prop file from /system, then copy it to PC then open build.prop in a text editor then find these lines in it:
persist.service.adb.enable=1 persist.service.debuggable=1 persist.sys.usb.config=mtp,adb
Change these lines in your build.prop to match the example above. You may not have all of these lines, change the ones you have and/or type the lines you don't have in for yourself then save the edited build.prop then adb push that copy back to /system to overwrite the existing unedited build.prop. Reboot the device and USB debugging should be enabled.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Shedopen123 said:
I'm having trouble flashing Supersu.zip.Everytime I flash,i type SU into the Terminal and it always says SU not found.Do I have to use adb from now on in order to replace efs?I also can't find the build.prop file that you are referring to in your comment.Thank you
Click to expand...
Click to collapse
You don't flash SuperSU.zip with adb/fastboot.
Move the SuperSU.zip file to your device's internal storage or put it on an external sdcard, then boot into TWRP and choose the "install" option, then browse to where you stored SuperSU.zip and flash it.
In my first reply to you, I didn't say anything about flashing SuperSU.zip in a terminal, I told you to boot into TWRP and flash SuperSU.zip. Pay attention to what is told to you, word for word.
You could have easily done some searching to understand those instructions. Learn to search for answers.
You need to be rooted first, then you can find and edit build.prop.
Build.prop is very easy to find, again, learn how to search for answers.
Build.prop is located in /system/build.prop. It's in system partition, not in your internal storage.
Try using adb pull to get a copy of build.prop then edit the copy, save the copy and adb push it back to its location in /system/build.prop.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers
Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work
so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right
Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done
I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes