Related
How would I use the emulator provided in the sdk to test run a modified framework-res.apk ? I am not familiar with emulator use...I googled it a bit but didn't find anything specific to my question.
Stericson
Use adb commands just like a real device. Failing that you can directly mount the system image file and modify it yourself.
jashsu said:
Use adb commands just like a real device. Failing that you can directly mount the system image file and modify it yourself.
Click to expand...
Click to collapse
How would I mount the image file and modify it? I tried the adb commands, pushing the file, and then I tried to reboot, or turn it off, and turn it back on but it wouldn't. So I closed it and started another emulator with no change.
Stericson
The emulator is run off a system.img that is found in the SDK directory somewhere.
That's a yaffs3 file system that you can open with the appropriate program.
Koush said:
The emulator is run off a system.img that is found in the SDK directory somewhere.
That's a yaffs3 file system that you can open with the appropriate program.
Click to expand...
Click to collapse
Blarg. I hate it when the forum marks something as read when you haven't actually read it. Anyway Koush is right. My sdk dev environment is Windows, and the path to the corresponding directory is
\android-sdk-windows-1.0_r2\tools\lib\images
However you probably want to be in Linux if you want to mount the yaffs2 filesystem.
Thanks to FollowingInsanity for editing the build.prop file to get it working corectly, and thanks to Maxisma for the Droid dump. Thanks to everyone else who pitched in on this whole thing. Really all I did was realize the exact line that needed to be changed....everyone else did the rest
Here are instructions on how I got the new maps w/ Navigation to work via adb. I'm running the official rooted 1.6 build, but this should work for anyone.
(if you don't know how you use adb, go to the here
Next, you need to uninstall the old maps.apk file and here's how I personally did it since you can't just go to "uninstall" from the Application Settings(these instructions start already in the ADB shell):
# mount -o rw,remount /dev/block/mtdblock3 /system
# cd system
# cd app
# rm xxxxxxx (this is whatever your maps.apk is titled. sometimes is just maps.apk, but it could also be com.android.google.maps.apk or somethin like that)
# exit
Click to expand...
Click to collapse
Now you've uninstalled the google maps. You can then do these next steps outside of adb.(for instructions purposes i'm using my own Android location):
C:\android\tools> adb pull /system/build.prop C:\Android
C:\android\tools> adb pull /system/build.sapphire.prop C:\Android
The 2nd may not be may be build.trout.prop or something to that effect...build.xxxx.prop
Click to expand...
Click to collapse
Next, change those 2 file names on your PC from build.prop to build-backup.prop and build.xxxx-backup.prop(if you have one) so that you don't lose those files in case anything stupid happens in the mean time lol.
Make a 2nd copy of build.xxxx-backup.prop and rename it is build.xxxx.prop. So now you should have a build.xxxx.prop AND a build.xxxx-backup.prop
Now you'll need the build.prop file to use
build.prop
(IF you are running a sapphire build, you can also use the build.sapphire.prop file located there and skip down to "re-loading prop files")
I saved that file to the same location that I saved my original files.
open build.xxxx.prop in notepad. look for where it says:
ro.build.description=kila-user 1.6 DRC83 14721 ota-rel-keys,release-keys
ro.build.fingerprint=xxxxxxxxxx:user/ota-rel-keys,release-keys
# end build properties
Click to expand...
Click to collapse
you'll need to delete the line that says ro.build.fingerprint=xxxxxxxxxx:user/ota-rel-keys,release-keys but DO NOT delete the line that says #end build properties
replace the line you deleted with the following:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
Reloading Prop Files
next, back in your command line window do the following:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Click to expand...
Click to collapse
then restart your phone
while the phone is restarting, go back and rename your build.prop and build.xxxx.prop files to build-update.prop and build.xxxx-update.prop, then change your build-backup.prop and build.xxxx-backup.prop to build.prop and build.xxxx.prop
After it restarts you'll want to locate your maps.apk file(the new one) and go back into your command line and type:
c:\android\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
c:\android\tools> adb install c:\android\maps.apk
(install crap...if it doesn't install correctly then don't do whats below)
Click to expand...
Click to collapse
Go check your google maps, type in two locations and click "go" and on the next screen you should see a button that says "Navigate"
go back to your command line screen and type:
Sorry if this is confusing, anyone who could make it more simple, please feel free to give it a try, but this is the best I could offer so people wouldn't have to go looking though the whole think tank thread to get everything they need to get it working
IF THE INSTALL GAVE YOU AND INVALID_UPGRADE ERROR THEN TRY THIS:
(again these instructions are using my own android sdk location, replace the
c:\android\tools with YOUR sdk location
from the command line type the following:
c:\android\tools> adb shell
# mount -o rw,remount /dev/block/mtdblock3 /system
# exit
c:\android\tools> adb pull /data/system/packages.xml c:\android\
Click to expand...
Click to collapse
BACK UP THIS FILE BEFORE EDITING IT
Once that's done, open that xml file in a text editor hit ctrl+f and search for maps, the first one will probably say auth.sitemaps, ignore that, keep searching untile you get to something to the effect of com.android.google.maps.apk or something like that. when you see that, you'll want to delete everything from "<packagename=" to "</package>" for the google maps app. BE VERY CAREFUL!!!! you don't want to accidentally delete something else, thus the reason for the back up.
after you've done that, go back to your command prompt and type:
c:\android\tools> adb push c:\android\ /data/system/packages.xml
c:\android\tools> adb install c:\android\maps.apk
Click to expand...
Click to collapse
it should then install perfectly fine. thats what I had to do to get it to work for me
I love you guys! will try this when I get home from work!
it does not appear to be 100% working....yet...
as posted by dwang, http://forum.xda-developers.com/showpost.php?p=4921655&postcount=275
dwang said:
If you push the old build.prop files back, after a while, the nav option disappears.
Click to expand...
Click to collapse
which I can confirm. About midnight last night it was working okay, and this morning it was gone.
followinginsanity says he will work on it today. http://forum.xda-developers.com/showpost.php?p=4921665&postcount=278
followinginsanity said:
Confirmed... will work on it tomorrow.....
Click to expand...
Click to collapse
may not want to rush to get it working only for it to not work a few hours later...but ..like most people here...that probably won't stop many
I edited the build.prop file...and now it will only work with Sapphire builds. For CM builds, build.prop file that FollowingInsanity created
Code:
c:\android\tools> abd push c:\android\build.prop /system/
c:\android\tools> abd push c:\android\build.xxxx.prop /system/
Should be
Code:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Takenover83 said:
Code:
c:\android\tools> abd push c:\android\build.prop /system/
c:\android\tools> abd push c:\android\build.xxxx.prop /system/
Should be
Code:
c:\android\tools> adb push c:\android\build.prop /system/
c:\android\tools> adb push c:\android\build.xxxx.prop /system/
Click to expand...
Click to collapse
Changed lol. thanks
where can i get the new maps apk? the old one fails to install
i get error
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
ahronzombi said:
where can i get the new maps apk? the old one fails to install
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=4921092&postcount=196
That's the one I did, it also has all the needed files just grab the files from there and you should be able to use them for these instructions
ahronzombi said:
i get error
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
Click to expand...
Click to collapse
When that happens you need to:
adb push <path to>/Maps.apk /system/app
adb shell
# install /system/app/Maps.apk
# exit
hey hey hey
could you or somone who got this to work try to make a video tuturiol on this so we can all clearly see how it works!!! please someone make an post it on youtube if possible thanks!!!!!!!!!
navigation doesn't work outside of the US at the moment right?
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
seaweeduk said:
navigation doesn't work outside of the US at the moment right?
Click to expand...
Click to collapse
Nope, not until the big G says so.
mianosm said:
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
Click to expand...
Click to collapse
what rom are you using?
mianosm said:
I was able to get the new maps.apk to install - and it is clearly a different application (with the new layers), but no navigate button. : (
Click to expand...
Click to collapse
You might have to try editing your packages.xml file even though it didn't give you an install error. Also, if you push your original build.prop's back, you lose navigation after a few hours. I guess the quick solution to that would be to keep the new build.prop's, but I'm not sure what the problems that might or might not create for other apps.
I'm using CM-4.2.3.1 with the edited build.prop and the build.sapphire.prop files.
# mount -o rw,remount /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
A quick shortcut is to drop the device from this command. As you're re-mounting, the kernel knows the device name. Like this:
# mount -o rw,remount /system
Click to expand...
Click to collapse
Wow dude your the bomb, I did it a different way but it worked perfect. I just took a dount rom extracted it, deleted the maps.apk, then I took the droid dump maps app and put it into the donut rom. Then I made the changes to the build.trout.prop so that it recognized the g1 as the verizon phone, used your downloadable build.prop, of course I just deleted the original build.prop in the donut build, I resigned the donut rom, flashed it like it was brand new, and bingo everything worked perfectly. Wow good job dude. I would upload my rom but I dont want to get into any trouble.
I am using "AOSP1.6_r1.4+ADP DRD20 ROM". Maps on here is called "GoogleMaps.apk". I also do not have just a build.prop. I have a build.sapphire.prop and build.trout.prop. I modified both and replaced according to the first post. When I rebooted, GoogleMaps.apk was reinstalled, so I had to uninstall it again.
I did get the error described in post #8, but was able to get around it with the help of post #10.
But for some reason my network is completely down so I can't do nothing. Wifi and Cellular network. Hmmmm.
Edit: Replacing the files I backed up with the originals, brought my networks back.
sorry guys forgive my dumpness but i downloaded theme from the topic . after i replaced the apk files through root explorer and made restart to the device after that my x10 couldnt start i reflashed root steps but i really still want to change this stupid blue colore is there any easy way to do it . i wanna use the themes that already made from devlopers it comes like normal apk files........thanks in advance
Sent from my X10i using the XDA mobile application powered by Tapatalk
see Here *10chars*
What files do you have exactly? framework-res.apk? Phonebook.apk? Phone.apk
This thread as given above is taken that you have ADB installed on your computer.
http://forum.xda-developers.com/showthread.php?t=714288
If you do not have ADB, visit this thread first.
http://forum.xda-developers.com/showthread.php?t=532719
Feel free to ask if you have more questions
xGary said:
What files do you have exactly? framework-res.apk? Phonebook.apk? Phone.apk
This thread as given above is taken that you have ADB installed on your computer.
http://forum.xda-developers.com/showthread.php?t=714288
If you do not have ADB, visit this thread first.
http://forum.xda-developers.com/showthread.php?t=532719
Feel free to ask if you have more questions
Click to expand...
Click to collapse
i have framework-res.apk? Phonebook.apk? Phone.apk
and i know about adb commands but i wonder what is the diffrences it's all about replacing apk files and i manged that with root explorer and the guide is too hard it's all about modfications of the system files but it didn't tell us how to use an exsiting theme files ....is it all about the remount command that make us have to use adb ??? thanks in advance
h.boushi1987 said:
i have framework-res.apk? Phonebook.apk? Phone.apk
and i know about adb commands but i wonder what is the diffrences it's all about replacing apk files and i manged that with root explorer and the guide is too hard it's all about modfications of the system files but it didn't tell us how to use an exsiting theme files ....is it all about the remount command that make us have to use adb ??? thanks in advance
Click to expand...
Click to collapse
Not sure if ADB is required but thats the only method I know of. A step by step guide (Might want to double check with advanced users)
1) Install ADB and set the environment variables, etc.
2) Go to the folder (Should be c:/android-sdk-windows/tools) and open adb.exe (If it flashes and auto closes, open up cmd [Start>Run>cmd] and drag the adb.exe into the cmd and press enter)
3) Put Phone In Debugging Mode Settings>Applications>Development>USB Debugging
In ADB, type these commands
*Note that the commands are case sensitive*
Pull the files you are about to replace with the following commands:
cd c:/anrdroid-sdk-windows/tools
adb pull /system/framework/framework-res.apk framework-resk.apk
adb pull /system/app/Phonebook.apk
adb pull /system/app/Phone.apk
4) Now framework-res.apk, Phonebook.apk, and Phone.apk should be in your tools folder where your adb.exe is. Put these files somewhere safe.
5) Now drag your new framework-res.apk, Phonebook.apk, and Phone.apk into the tools folder.
6) Go back to adb and type the following command:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
7) Now these commands will move your new theme files to the sdcard:
adb push framework-res.apk /sdcard/framework-res.apk
adb push Phonebook.apk /sdcard/Phonebook.apk
adb push Phone.apk /sdcard/Phone.apk
8) Now these commands will install the new theme files in the sd card from the previous step:
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
adb shell dd if=/sdcard/Phonebook.apk of=/system/app/Phonebook.apk
adb shell dd if=/sdcard/Phone.apk of=/system/app/Phone.apk
9) Now your phone will restart (If not, manually restart) and your theme should be installed.
Gary~
thanks a lot man ... you are the best i'll try that and report back but any way you still the best.....
Sent from my X10i using the XDA mobile application powered by Tapatalk
why every time i put the mount command it tells me "the device not found"
and the pull commands don't seems to work
i tried adb devices command but it seems it doesnt found my device
Mmm...maybe its sound dumb, but I'm a noob in this. How do you change the battery icon? Thx
rein_hiryu said:
Mmm...maybe its sound dumb, but I'm a noob in this. How do you change the battery icon? Thx
Click to expand...
Click to collapse
You pull the framework-res.apk file and open it with 7-zip. Inside should be some folders and there should be a folder (forgot which one) with a bunch of pngs. Replace the battery icons with desired ones.
Gary~
Im trying to push a file over using the adb and Im getting a read only file system error. I check to see if I have SU permission and I do. Googling it but its getting me no where. Heres a screenshot to show you what I mean. Any ideas? I have an updated MMS.apk, but I cant get it pushed.
Idk if this would help, but have you tried root explorer or es file explorer to change system from read only to write?? Again, not sure if that would help, I am still, and always will be, a noob .........
ahhhhh...........gone todash..............
1. Use Root Explorer or adb shell to check and/or modify your (root)/default.prop to say:
Code:
ro.secure=0
2. Run the command:
Code:
adb remount
3. Push your app again.
suksit said:
1. Use Root Explorer or adb shell to check and/or modify your (root)/default.prop to say:
Code:
ro.secure=0
2. Run the command:
Code:
adb remount
3. Push your app again.
Click to expand...
Click to collapse
Very strange. I have root access but the ro.secure=1, I changed it to ro.secure=0, I wont have time to check it again until I get home, but I'm sure that was the problem. Thanks.
suksit said:
1. Use Root Explorer or adb shell to check and/or modify your (root)/default.prop to say:
Code:
ro.secure=0
2. Run the command:
Code:
adb remount
3. Push your app again.
Click to expand...
Click to collapse
I think this will not work b/c the default.prop file gets regenerated every boot. Is this correct?
skola28 said:
I think this will not work b/c the default.prop file gets regenerated every boot. Is this correct?
Click to expand...
Click to collapse
It will work until the next boot
Sent from my Nexus S using XDA App
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.