Hi, First I'm not a clever man, nor do I know what I did to brick it but, I used
"LCD Density Modder" on the market and bricked my phone.
https://play.google.com/store/apps/details?id=com.birdapi.android.dpi&hl=en
My phone is bricked, it won't load anything past "Google", I've taken out the battery and put it back in MULTIPLE times, I've tried to reboot into Recovery Mode and get a red Triangle with an error.
I'm on 4.1.1 GSM model, Rooted and Stock ROM.
Is there anyway to fix this issue without completely wiping out my phone? The last backup I did was a week ago by hand, with click and drag.
Thanks for any help, I would appreciate it.
That's not bricking. And the red android is the stock recovery. Your going to need to flash a recovery and flash another ROM.
Sent From My Toro+ via White Tapatalk
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
First off, your device is not bricked. Bricked means it is irreparable.
Second, all you have to do is get a hold of the stock build.prop file for your ROM build and replace what you currently have with it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or this
Sent From My Toro+ via White Tapatalk
Oh, wow, thanks, and that will save my files?
Is there a step by step process? I...am not a clever man =| or if there's a keyword I can search. Thanks...
I'm asking because I can't transfer files via USB to my Galaxy Nexus, nor does my computer detect it.
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Ignore the post I just made,
I found it manually, and rebooted the phone but it's still black screen when I pushe d it to the phone.
"build.prop /system/" sounds wrong though...but I am still shocked I was able to pull it.
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
smartedpanda said:
I hate double bumping but "efrant" instructions, I pushed it via your manner, which still boots into the black screen via build.prop /system" and it goes to black screen...and I tried pushing to "/system/build.prop" still doesn't work.
Any assistance?
Click to expand...
Click to collapse
So what did you do exactly? Did you pull the file from your ROM first, modify it, and then push it back?
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
smartedpanda said:
So, I'm not using ADB kit, I'm using Galaxy Nexus Tookit v 7.4. I pull it through there, and modify it from 241 to 320 by hand. Save the file. Push it back up using the toolkit, and it's not sticking to the ROM.
I push it up, reboot, and check it by re-pulling it making sure it stucks but I keep seeing the 241 density not the corrected 320.
Should, I be pushing to /system/build.prop or "build.prop /system/" ?
Both methods aren't sticking to /system/build.prop
Click to expand...
Click to collapse
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
It's to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
efrant said:
I don't provide support for toolkit use. Either do it the way I mentioned or ask in the toolkit thread for support if you want to use a toolkit.
Click to expand...
Click to collapse
- Didn't know it was a hassle, my apologizes. I'll try to do it the old school method.
trevd said:
Its to do with the permissions that get set on the file when you push it back to the device. it needs to be read only for the group and world
It baffled me for a good while. After pushing the file, do the following.
Code:
adb shell chmod 0644 /system/build.prop
Hope that helps
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I had a feeling it was a permissions issue, but wasn't sure how to fix it.
I'll start pulling up the command prompts...wish me luck, thanks for all the help so far guys. I'll do two backup a week from now on, instead of weekly.
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
smartedpanda said:
Finally got adb in cmd setup, I get a "failed to copy 'build.prop' to '/system/build.prop': Read-Only file system
I'll try it again, I'm pretty sure I forgot a step.
Click to expand...
Click to collapse
Probably missed this step:
efrant said:
In the CWM menu on your device, navigate the mounts menu and click mount /system
Click to expand...
Click to collapse
efrant said:
Probably missed this step:
Click to expand...
Click to collapse
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
smartedpanda said:
LOL, yeah I did, got that, did everything from scratch per your instructions, got up to the lovely adb reboot...and nothing, at all, black screen.
I re-pulled it, to make sure the DPI was changed to 320...and it was, and still black screen...=[ I'm really sad now.
Click to expand...
Click to collapse
Did you change the permissions like trevd suggested?
While booted in CWM with /system mounted:
adb shell chmod 0644 /system/build.prop
If that still doesn't work after a reboot, I suggest you re-flash grab the system image for 4.1.1 from Google's site, extract the system.img, reboot your device into the bootloader, and type: fastboot flash system system.img. It won't wipe your device, but it should fix anything that was messed up. (It will also remove root and busybox and whatever else you have installed on the system partition.
)
FINALLY! SUCCESS! I forgot the permission like you mentioned, but it didn't work the first two times, guess I mistyped something, it worked the third time.
I honestly appreciate all the help, and all the inputs. My phone is at 100%, and I'm doing a backup as we speak now.
efrant said:
Download CWM, rename it to cwm.img and place it in the same directory as your fastboot.exe file on your PC
Boot your device into the bootloader
Type: fastboot boot cwm.img
In the CWM menu on your device, navigate the mounts menu and click mount /system
Type: adb pull /system/build.prop
Open it up in a text editor, change the value in the ro.sf.lcd_density to 320 and save it.
Type: adb push build.prop /system/
Type: adb shell chmod 0644 /system/build.prop
Type: adb reboot
Click to expand...
Click to collapse
I know this thread is dead but I would like to say that this is the single most useful post I've seen in ages! I was looking around for nearly an hour and every post resulted in saying "reflash rom"...
Then I saw this, and worked!! My phone is her old self again
thumbs up!
Related
How would it be able to do this? I've seen terminal codes floating around, but none of them look like they'd be replacing the proper files for a cupcake build (old RC33 builds I believe, long lost now!)
I'm running TheDude's 1.3 RC2. I've seen plenty of ADB commands, however I've never been able to get ADB to work on my computer, and I don't feel like putting more pointless hours into it
So how would the terminal commands work, and what would the pre-requisites for the files have to be? Thanks!
http://forum.xda-developers.com/showthread.php?t=467693 Im pretty sure all you need is fastboot not adb for splash1 the animated splash just requires you to resign an update.zip http://forum.xda-developers.com/showthread.php?t=467693
crotalusfreak said:
http://forum.xda-developers.com/showthread.php?t=467693 Im pretty sure all you need is fastboot not adb for splash1 the animated splash just requires you to resign an update.zip http://forum.xda-developers.com/showthread.php?t=467693
Click to expand...
Click to collapse
I'm pretty sure it uses ADB, hence why I'm asking...Fastboot IS ADB
yea fastboot is the only other way that I know of!!
this is where i downloaded the tools for creating your own boot image!
http://www.modmygphone.com/forums/downloads.php?do=file&id=1471&act=down
this is the link that teaches on how to make one and im pretty sure there is one here in the forums!
http://modmygphone.com/forums/showthread.php?t=10461
if you need help PM me ill take you step by step!
or email [email protected]
lukekirstein said:
I'm pretty sure it uses ADB, hence why I'm asking...Fastboot IS ADB
Click to expand...
Click to collapse
it wont use ADB, fastboot is like an alternate route...
Drizzy Drake Rogers said:
yea fastboot is the only other way that I know of!!
this is where i downloaded the tools for creating your own boot image!
http://www.modmygphone.com/forums/downloads.php?do=file&id=1471&act=down
this is the link that teaches on how to make one and im pretty sure there is one here in the forums!
http://modmygphone.com/forums/showthread.php?t=10461
if you need help PM me ill take you step by step!
or email [email protected]
Click to expand...
Click to collapse
Step number two of those directions: "2. Get ADB setup and working. Read here. "
Let's clarify. I cannot get ADB to work, at all, on my computer. Fastboot doesn't work because I can't get ADB to work. Moreso, I just realized that I can't even find my data cord.
Either way, the point of my post is to find a way to change the boot animation at start up, without having to use anything but the phone and maybe some photo editing software.
So how can we do this?
You do not have to have the whole sdk(adb etc..) for fastboot to work you do have to have a driver running for android found in the sdk or here http://dl.google.com/android/android_usb_windows.zip .
The boot animation is found in /system/framework/framework-res.apk/assets/images,android-logo-mask.png and android-logo-shine.png are the images you wanna edit.Dont believe you can get it back on your phone without the sdk set up with adb working though as you will either have to resign an update or push the edited files back somehow.
Edit:without a data cord I think this is an impossibility I dont think you can go through the process needed on your phone,dont hold me to that though good luck man.
crotalusfreak said:
You do not have to have the whole sdk(adb etc..) for fastboot to work you do have to have a driver running for android found in the sdk or here http://dl.google.com/android/android_usb_windows.zip .
The boot animation is found in /system/framework/framework-res.apk/assets/images,android-logo-mask.png and android-logo-shine.png are the images you wanna edit.Dont believe you can get it back on your phone without the sdk set up with adb working though as you will either have to resign an update or push the edited files back somehow.
Edit:without a data cord I think this is an impossibility I dont think you can go through the process needed on your phone,dont hold me to that though good luck man.
Click to expand...
Click to collapse
Alright, I just confirmed the location on the phone. So if I upload a file onto my SD card, and overwrite it through Terminal, what do you think that'll do? I'm not big into the Themes section, I'm into the Development section, so I'm not sure what overwriting will do to my phone.
Actually you might be able to get away with that.Try backing up framework res in terminal type:
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cp -r /system/framework/framework-res.apk /sdcard
Now the .apk you want is on your sdcard root pull that onto a computer unzip it with 7zip.In the framework-res folder there are some more folders go to assets then images edit those two images to your liking.Then go back to your framework-res.apk that you backed up add .zip to the end,right click it and choose open or explore navigate back to the images folder and paste your edited boot images in there.Now remove .zip so it is framework-res.apk again put that back on your sd cards root.Go to terminal and type
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cp -f /sdcard/framework-res.apk /system/framework
#reboot
If all goes well that should work.
crotalusfreak said:
Then go back to your framework-res.apk that you backed up add .zip to the end,right click it and choose open or explore navigate back to the images folder and paste your edited boot images in there.Now remove .zip so it is framework-res.apk again put that back on your sd cards root.
Click to expand...
Click to collapse
Lost you at naming it as a .zip. I can't explore or open the file, as Windows Vista doesn't know how to handle it. Any ideas?
lukekirstein said:
Lost you at naming it as a .zip. I can't explore or open the file, as Windows Vista doesn't know how to handle it. Any ideas?
Click to expand...
Click to collapse
right click-> open with -> WinRAR
Or go to Folder Options and uncheck "Hide extensions for known filetypes" (you should do that for all folders.... its a bad idea not to because a virus may look like *.doc instead of *.doc.exe anyways its also more convenient)
does anyone know how to change the boot image for a rogers g1 none of these things work for me i bricked my last phone a week ago cause someone said it would work
jokefox said:
does anyone know how to change the boot image for a rogers g1 none of these things work for me i bricked my last phone a week ago cause someone said it would work
Click to expand...
Click to collapse
Well if you're bricking phones, I wouldn't recommend trying it again
I've had a bit of trouble with pushing my bootanimation.zip to my phone. I got a .zip from here and modified it a bit so it would last longer and I wouldn't end up with a black screen for 20 seconds every time I booted. I did:
adb shell
got su
mounted rw on /system
exited adb shell
pushed the bootanimation.zip to /system/media
got confirmation
went back to adb shell
mounted ro on /system
exited
Now, I restart my phone to confirm it worked, but I just get a black screen until my lock screen loads. I attached the .zip to this post.
I don't know if I need to sign it or zip it with something other than 7zip or whatever. Can someone with more experience with adb help me out with this?
Well I looked at your desc txt file, and it was a little off from what I've seen so I changed it, hope it works; and in adb do it this way, a lil faster
adb remount
adb push bootanimation.zip /system/media
adb reboot
Thank you. I'm trying it now.
EDIT: I didn't work...
I think that should work.
What are you running for a ROM? If you are on a Sense based ROM, it needs to go in system/customize/resource.
Sent from my HTC EVO 4G with Tapatalk
I'm running Salvage MOD 1.0. It's AOSP GB.
Maybe try using root explorer to go in and replace the file. That's how I usually change boot animations. This should accomplish the same thing as using ADB push but it's worth a try.
Sent from my HTC EVO 4G with Tapatalk
Towleeeie9613 said:
I'm running Salvage MOD 1.0. It's AOSP GB.
Click to expand...
Click to collapse
Did it work?
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
re: install apks
TheArtiszan said:
Was just wondering if there is a way to replace the framework with just using root without a custom recovery for the stock Rom?
On my s3 I couldn't do it with just root don't know if that would work on this or if I might have missed something.
Sent using xda premium.
Click to expand...
Click to collapse
All you need is to be rooted, it does not matter if you have custom recovery or not.
You can install any apk's since you do not need to go into recovery to install apks.
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
re: install apk
TheArtiszan said:
When I tried with root only before on a different phone I used root explorer to replace.
But when I went to paste it in the folder the phone locked up and rebooted.
Was that not the right way to do it?
Maybe using adb terminal would be better and not cause it to lock and reboot when I paste over the existing framework-res.apk.
Being in the system directory causes some issue with being that is also a constant used file.
Sent using xda premium.
Click to expand...
Click to collapse
The framework-res.apk should be installed like any other app
unless the OP of wherever you got it from gives instructions
to "copy" it to the /system/app folder.
Why not do it the default normal way? just double click on it
when you are in root explorer and it should install like any
other app. If it gives an error, then you can copy it.
If you "copy" it you have to fix permissions and you have to
change the attributes of the /system/app folder so it's "read and write".
NOTE: if there is an existing framework-res-apk in /system/app
delete it with root explorer before doing any of the above.
Framework-Res.apk must reside in system directory. /system/framework to be exact.
Easiest way to do it without locking up is with adb.
You were right OP that it locks up because it's consistently being used. When I make my mods and such to the framework, this is how I quickly get it to the device.
adb remount (if the kernel supports it in other words, anything but stock)
Turn phone screen on
Adb shell stop (your phone should now have a black screen. This command stops all running threads except the one for adb)
Adb push framework-Res.apk /system/framework
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
You should now see the boot animation then the prompt "android is upgrading"
If you do not have adb remount option (it returns with permission denied)
Copy new framework Res apk to root of internal sd card.
Adb shell stop
Adb shell mount -o remount,rw /system
Adb shell cp /sdcard/framework-Res.apk /system/framework/framework-Res.apk
Adb shell chmod 644 /system/framework/framework-Res.apk
Adb shell start
Just a pointer, disregard my capitalization. Only capitalize when needed.
This method should get everything copied successfully. Any issues just post back!
Sent from my SGH-M919 using Tapatalk 2
Oh thank you very much.
I will give that a try and sounds exactly like what I was looking for.
Sent using xda premium.
Not sure if this is really relevant but...
When I had the samsung vibrant, I used root explorer to make a copy of my framework-res.apk. I extracted the entire thing, found my battery icon files, replaced them with different images given the same name, then repacked the file. Then I copied it back to the original folder to replace the original apk and my phone immediately shut off and rebooted. When it came back I had my new battery icon working just as I had hoped. I was rooted running stock.
Wait... Are you saying that I can simply copy the framework-res.apk from SlimKat and use it on a Google Play Edition ROM?
I'm going to try it!
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable TWRP recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
I've created an easy installer for all you Windows folks!
Download this: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/easy-twrp-e98010g.zip
Extract it to somewhere on your computer.
Enable USB debugging on your phone, if you need the drivers I've included them in the "files/drivers" folder in the zip
Run the 'install.bat' script.
Check for any errors, if it was successful, you can 'adb reboot recovery' or use an app on your phone to get you into TWRP now!
Profit! (and realize that this was pretty easy!)
(thanks to hkfriends for pointing out the errors in my script!)
OR..
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-twrp-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-twrp-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have not tested external SD cards, since I don't have one with me at work.
I have also not tested backups or restores in TWRP yet.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
hkfriends
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
This is killer, I love twrp. So this will just over flash the cwm currently added earlier of course correct? Awesome work m8:thumbup:
EDIT: Not sure why but the Loki flash file downloads as a. Txt file for me
Sent from my LG-E980 using Tapatalk 2
maybe i am doing something wrong, but when i get into twrp the touch does not work
Very nice work there
testing back up and restore now
rbf351 said:
maybe i am doing something wrong, but when i get into twrp the touch does not work
Click to expand...
Click to collapse
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
sorry for the "newbie" question...but the file to download are getting to the phone right?
thecubed said:
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
Click to expand...
Click to collapse
yup, AT&T version, but it happens when i type in adb reboot recovery
Everything works so far tried backing up restore flashing and external sd... very nice work I will keep playing to see if i find any bugs
rbf351 said:
yup, AT&T version, but it happens when i type in adb reboot recovery
Click to expand...
Click to collapse
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
thecubed said:
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
Click to expand...
Click to collapse
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
rbf351 said:
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
Click to expand...
Click to collapse
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
thecubed said:
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
Click to expand...
Click to collapse
i have the following
ADB Interface
Android Sooner Single ADB Interface
edit, that wasn't while i was in recovery mode
in recovery mode i have
other devices
LG-E980 with an exclamation
I was able to flash and get into recovery without any issues. Excellent work! Thecubed and djrbliss, you guys are awesome!
here is the pastebin
http://pastebin.com/XPYi0v44
rbf351 said:
here is the pastebin
http://pastebin.com/XPYi0v44
Click to expand...
Click to collapse
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
thecubed said:
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
Click to expand...
Click to collapse
CWM works perfectly, i can navigate through all the menus using the softkeys
TWRP working perfectly here for me also! thank you for this! :good:
verry nice work........would be nice to have a kind od "how to" when thing get all set.....:good:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Gotroot said:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
yeah ...but i have all the file....does i have to put the phone in download mode??
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Rhatfield25 said:
Like a dummy I tried to rename framework-res while using my nexus so I could replace it with an edited one (deb rooted, stock 4.4.4 rom, franco -17 kernel)
Now Im trying to ADB in to rename the original file so it will boot again.
I'm connected to the nexus in ADB but when I try to pull or rename the file I always get some sort of error.
I was able to adb push a framwork file I downloaded on my computer but it still wouldnt boot. Im assuming it was bad.
Any help is much appreciated!
thanks!
Click to expand...
Click to collapse
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
SwoRNLeaDejZ said:
The reason it would not boot with the one you pushed to the device is probably because you have to set permissions correctly after the push. Framework res should probably be set to rw-r--r--
Run this after the push, or if the file is still on the phone, run it now.
Code:
adb shell
su
chmod 644 /system/framework/framework-res.apk
Click to expand...
Click to collapse
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Rhatfield25 said:
I will give it a shot the second I get home! Thank you so much for the help. So by default files pushed to the system do not have full read and write permissions?
Thanks again!
Click to expand...
Click to collapse
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
SwoRNLeaDejZ said:
Yes, most of the time, pushed files will copy with bad permissions. Every time I've ever edited a system APK, I've had to subsequently set permissions before it would act correctly. Might not be 100% your issue, but it's definitely worth a shot.
Click to expand...
Click to collapse
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Rhatfield25 said:
Well now Ive run into a new problem. When I SU to get root access it tells me that /sbin/sh isnt found.
I rooted the n7 with cf autoroot.
this would be a whole lot easier if twrp would mount the tablet so I could just upload and flash a zip to update it.
Click to expand...
Click to collapse
What about trying to use the terminal emulator in twrp?
Rhatfield25 said:
Well I was able to sideload the boot animation herehttp://forum.xda-developers.com/showthread.php?t=2591471 just to confirm that sideload was working. I rebooted and it worked but still will not get past the boot animation.
The framework file simply needs to be put in /system right? so the command would look like
abd sideload framework-res.apk /system
Is that right?
Click to expand...
Click to collapse
You need to fix the framework file before you can boot. Try running the permission command without su first.