I already update it via fastboot (I got Amon recovery 1.5.2H).
But I need to change the font DroidSan to get correct font display.
Can anybody help me to solve it?
Thanks
so you are trying to restore the original fonts? did you back them up? if not, google droidsans.ttf and droidsans-bold.ttf and download them. or get them from a nandroid somewhere... they shouldn't be hard to find.
then, in cmd/terminal go to the folder they are in and (assuming you have all your fastboot/adb paths setup) and type the following:
fastboot push droidsans.ttf system/fonts/DroidSans.ttf
fastboot push droidsans-bold.ttf system/fonts/DroidSans-Bold.ttf
If you are just playing around with new fonts i suggest you grab the old ones first so you can easily revert:
go to a safe backup location and type:
fastboot pull system/fonts/DroidSans.ttf ./
fastboot pull system/fonts/DroidSans-Bold.ttf ./
Thank but there is no command fastboot push.
I run it and fail.
Also, I could not use adb remount because no permision.
that's weird - do any adb/fastboot commands work?
adb devices
adb shell
fastboot devices
do any of them work?
are you on a win xp/7, linux or osx machine?
I am on XP but when use adb shell it is ok
but use adb remout so have no permission.
ntphuong said:
I am on XP but when use adb shell it is ok
but use adb remout so have no permission.
Click to expand...
Click to collapse
You're using the ROM from this RUU right?
AFAIK, It's not rooted yet so those commands will not work.
Just watch that thread and wait for someone to post a rooted ROM.
If you can't wait, Cursor has put together an update to his Sense ROM.
asero said:
You're using the ROM from this RUU right?
AFAIK, It's not rooted yet so those commands will not work.
Just watch that thread and wait for someone to post a rooted ROM.
If you can't wait, Cursor has put together an update to his Sense ROM.
Click to expand...
Click to collapse
Yes.
I need the rooted ROM and I don't know how to root the ROM
Previous post is wrong...
You must use:
adb push local remote
like...
adb push droidsans.ttf /system/fonts/DroidSans.ttf
adb push droidsans-bold.ttf /system/fonts/DroidSans-Bold.ttf
march83 said:
fastboot push droidsans.ttf system/fonts/DroidSans.ttf
fastboot push droidsans-bold.ttf system/fonts/DroidSans-Bold.ttf
Click to expand...
Click to collapse
5[Strogino] said:
Previous post is wrong...
adb push droidsans.ttf /system/fonts/DroidSans.ttf
adb push droidsans-bold.ttf /system/fonts/DroidSans-Bold.ttf
Click to expand...
Click to collapse
oops, thank you for correcting me, i'm a douche...
That's right but no result because not rooted ROM
ntphuong said:
That's right but no result because not rooted ROM
Click to expand...
Click to collapse
If you've recieved - "read-only", so you can remount /system
adb remount
Thank all,
I use rooted ROM of Cursor, so everything is done now.
Related
I am on fresh 1.1 but i dont like the clear lockscreen. Is there a way i can change it??
yes try looking
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Thank You thedudejdog it worked perferct
You can take the HtcLockscreen.apk out of the /system/app dir of any ROM you like to get that rom's lockscreen going.
thedudejdog said:
just push this to system/app
you can use the fresh kitchen or adb
btw you can take apps out of any rom.zip on your computer, that's where i got this
Click to expand...
Click to collapse
am a newly rooted hero owner. read/re-read/followed the steps to do it on this forum and am grateful to those who lent their knowledge/expertise.
want to have the original hero lockscreen and downloaded this HtcLockScreen.apk file.
i searched online to see if i could find instructions to push this but can't seem to figure it out.
i've done the following:
- copied HtcLockScreen.apk to the root of my sd card.
- opened a command prompt
- got to "C:\android-sdk-windows\tools>"
from here am i supposed to type:
- "adb shell"
- "su"
'cause i think to push this is the command, right:
- "push /sdcard/HtcLockScreen.apk /system/app/"?
help please!
thank you.
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
I thought I saw on here a little while back that showed you how to remove just the image from the lockscreen so all you have is the grey bar. Does anyone know where that is because I thought that that was kinda cool.
thedudejdog said:
ok, put the file that you want to push in your tools directory of the sdk (c:\sdk\tools) these are the commands to push the file using adb
make sure you are in the command prompt and in your android sdk/tools directory.
you can copy/paste these one line at a time
i always do a
Code:
adb devices
first just to make sure adb sees your phone. if your phone shows up then continue
then mount system read/write
Code:
adb remount
then push the new lockscreen (this will overwrite the one that is there now)
Code:
adb push HtcLockScreen.apk /system/app
then close the cmd prompt window
Code:
exit
or you can use the fresh kitchen for a nice gui that does all the dirty work for you.
then reboot and there ya go, new lockscreen (or whatever)
i've never used the shell to push files, but i assume those commands that you listed should work for that, but you have to remount the filesystem first.
Click to expand...
Click to collapse
thank you! it worked...
so i followed some debug tut to install some custom lockscreen on my sprint hero and i dont want it anymore.. the codes i followed were
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
how do i get RID of the lock screen ?????
Warrior 3000 said:
so i followed some debug tut to install some custom lockscreen on my sprint hero and i dont want it anymore.. the codes i followed were
REPLACE LOCKSCREEN - WORKS
cd C:\android-sdk-windows\tools
adb remount
adb shell
cd /system/app/
rm HtcLockScreen*
exit
reboot phone
how do i get RID of the lock screen ?????
Click to expand...
Click to collapse
put HtcLockScreen.apk on your c:\ drive
plug your phone into your pc and:
Code:
adb remount
adb push c:\HtcLockScreen.apk /system/app
adb reboot
where do i get HtcLockScreen.apk ?
do you still have the update.zip that you downloaded to flash your rom?
if so, open it and look in system/app. it is located there.
Warrior 3000 said:
where do i get HtcLockScreen.apk ?
Click to expand...
Click to collapse
If you've downloaded any roms there will be one inside it.
Actually NVM, here you go
View attachment HtcLockScreen.apk
Warrior 3000 said:
where do i get HtcLockScreen.apk ?
Click to expand...
Click to collapse
Almost any custom rom has it, including the one you flashed. I also attached it below if you need it.
*edit* Neb beat me.. =)
Dank,
did you post in my thread? It's on page 4 atm, I needs a bump!!
ps. the bottom line in my sig will take you to it
*edit - Thanks Dank!
I know you had to push a reboot file to get it working on some Hero ROMs. What about the EVO version?
The Hero way works.
FIRST, install Quickboot from the market. Run it and enable it in the superuser permissions screen.
Download the reboot.txt file I attached and rename it to "reboot" (take off the ".txt"). Move it to where ever your "android-sdk-windows/tools" folder is.
Connect your phone to your computer (make sure it is "charge only") and boot into recovery...
Code:
adb shell
reboot recovery
Start your "Windows-recovery.bat" (if using windows) and let it do it's thing in the CMD prompt. Keep that prompt open.
In a CMD prompt OTHER THAN the one opened by recovery.bat type...
Code:
adb shell
mount /dev/block/mtdblock4 /system
exit
This will keep your system mounted but get you out of shell. Now type...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
Once you're back up, run Quickboot and choose either reboot or recovery (both will now work). It takes about 5 seconds to start rebooting but it does work.
What does this do? does it make recovery stick?
watzone69 said:
The Hero way works.
Download the reboot.txt file I attached and rename it to "reboot".
Once you're in recovery...
Code:
adb push reboot /system/bin
adb shell
cd /system/bin/
chmod 755 reboot
reboot
EDIT: It takes about 5 seconds to start rebooting but it does work.
Click to expand...
Click to collapse
Woo! Thanks!
Edit: Didn't seem to work for me. Damn.
joeavery2 said:
What does this do? does it make recovery stick?
Click to expand...
Click to collapse
No, this just lets you use the QuickBoot app from the Market to reboot your phone.
TheBiles said:
Didn't seem to work for me. Damn.
Click to expand...
Click to collapse
Code:
adb shell
cd /system/bin/
ls
See if the reboot file actually got pushed to the directory. If so, try this:
Code:
chmod 755 /system/bin/reboot
The only other thing I can think of is that I installed Quickboot BEFORE doing all of this. Did you get the SU permission screen when you tried to run it?
Any luck??
Did I mention that the Quickboot "recovery" button works also? Much easier than opening a shell and typing it in.
Of course you still have to run the recovery.bat to get the custom recovery but at least it's one less step.
Still no dice. I also already had QuickBoot installed and granted it root permission prior to pushing the reboot file.
any update to this?
thanks
joey3002 said:
any update to this?
thanks
Click to expand...
Click to collapse
It doesn't work for you?
I updated my earlier post to give more instructions for getting into recovery and pushing the "reboot" file. I hope it helps!
I have a ROM ready to go that changes a couple icons and quickboot works with no probelm. Wifi tether is the only thing I don't have working. I can post it if you would like. I also removed sprint apps and some widgets
I made an update zip that got Quickboot working for me. This is using watzone69's reboot file.
Run from Toast's recovery. http://forum.xda-developers.com/showthread.php?t=690762
watzone69 said:
It doesn't work for you?
Click to expand...
Click to collapse
yes i got it working last night by reading this thread from top to bottom.. then repeated.. thanks
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~
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
360fifa said:
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
Click to expand...
Click to collapse
RUU 3.20.502.52
Thank you kindly for taking the time to respond and also help.
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
360fifa said:
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
Click to expand...
Click to collapse
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Gizmoe said:
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Click to expand...
Click to collapse
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
360fifa said:
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
Click to expand...
Click to collapse
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
http://tau.shadowchild.nl/attn1/?cat=6
Gizmoe said:
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
Click to expand...
Click to collapse
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
360fifa said:
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
Click to expand...
Click to collapse
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Gizmoe said:
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
360fifa said:
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
Click to expand...
Click to collapse
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Gizmoe said:
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Click to expand...
Click to collapse
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu before attempting this or remain as is? Also, do I need cmw recovery installed or can i remain on twrp 2.6.0.0?
Thanks again bro..
360fifa
360fifa said:
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu or remain as is?
Thanks again bro..
360fifa
Click to expand...
Click to collapse
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Gizmoe said:
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Click to expand...
Click to collapse
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
360fifa said:
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
Click to expand...
Click to collapse
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Gizmoe said:
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Click to expand...
Click to collapse
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
360fifa said:
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
Click to expand...
Click to collapse
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
360fifa said:
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
Click to expand...
Click to collapse
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Gizmoe said:
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Click to expand...
Click to collapse
Okay.. I am going to try that now, I swore I did that as well but lets see.
360fifa said:
Okay.. I am going to try that now, I swore I did that as well but lets see.
Click to expand...
Click to collapse
Here's what it said "failed to copy '/data/local/tmp/boot.img' to ' ./boot.img': Permission denied