Hello to you all.
Noob ):
Ok, so I speak Hebrew, and Hebrew and Arabic I think are the only two languages that are being written from right to left.
This created a mess in Gmail and text messaging.
I emailed a friend, and he emailed me a revised Framework.jar file that fixed it on his vibrant. Cool.
So, I was doing everything according to procedure (see bellow), but got a stuck display on the boot screen "Galaxy S - Cynogen". Before my MIUI Rom booted.
This made me very sad, and I had no idea what to do. I went to recovery again and went to re-flashing my MIUI ROM
It worked and the phone booted again after it re-installed the zip MIUI - and everything is back to normal.
This means that something is not right with the Framework file or something?
Really not sure, I am really not good when it comes to this. Just followed directions.
Please help ):
Here is what I was told to do:
c:
cd tmp
dir
(Make sure you see the framework.jar file after you typed the "dir" command)
this will reboot your phone into recovery:
adb reboot recovery
after you are in recovery run this:
adb pull /system/framework/framework.jar framework_org.jar
This will backup your original file..
adb push framework.jar /system/framework/
This will copy the new file over..
After this reboot your phone either using the recovery menu options or by typing the following command:
adb reboot
Here is the revised Framework.jar file that I replaced with the "Stock" file
Related
Hello all.
Well, here is my problem. I was searching for some theme to change the "colors" of the menu of my device. SInce i couldn't find one, i just started to read a lot, and try to do it myself.
Well, I followed the instructions... and finally got my framework-res. The only problem was that the size of the file was lower thatn the original one. Anyway, I just went to root explorer, took my new framework-res.apk and replaced it on framework folder in internal storage.
The problem is that now my device won't start, I mean... it's stuck on the samsung logo, doing the animation over and over and over. Well I tried to get to the original framework-res, but I don't know how since I cannot replace things because I can't use a file explorer.
I searched some themes on the forum, thinking that maybe the framework-res would be replaced for the new one, and then it would work. Well it doesnt.
I have kph rom, and tried with "Dark simplify theme" and "circle battery kph" couse it's supposed to be stock theme with the circle battery...
Now, I dont know what to do, I dont know how to make an update.zip myself (I tried searching and learning but i just don understand).
I think i would reflash my system but, My internal partition was transformed to ext4 with cf-root, and I read a lot that If i want to flash any other rom, I have to change it to rfs first, but i can't do it couse i can't get to the ext4manager application.
So any ideas? please?
Thanks in advance.
ps: okay, i was a little desesperated when I wrote this (i still am). I searched for some with ext4 compatiblity. I have just tried gingerReal now. It's working. I'm gonna change the internal storage to rfs again, and flash kph.
Bootloop is really common here
you don;t need to reflash, if you have working framework-res.apk you just need to raplace it..
copy framework-res.apk to your sdcard
connect your phone to computer when in recovery
mount system partition using CWM
then using adb follow this command
adb shell
su
cd /sdcard
cp framework-res.apk /system/framework/
reboot
done
also if you reflash your ace using odin to stock one, ext4 partition automatically reverted to rfs
seilent said:
Bootloop is really common here
you don;t need to reflash, if you have working framework-res.apk you just need to raplace it..
copy framework-res.apk to your sdcard
connect your phone to computer when in recovery
mount system partition using CWM
then using adb follow this command
adb shell
su
cd /sdcard
cp framework-res.apk /system/framework/
reboot
done
also if you reflash your ace using odin to stock one, ext4 partition automatically reverted to rfs
Click to expand...
Click to collapse
Hi thanks for the answer. About the adb, that is supossed to be used in a pc, right? (sorry I never used it, i have just used terminal emulator in the device itself). I mean, I enter cmd, write adb shell and i'm in? (i have already installed sdk and all the neccesary things)
About the ext4 to rfs, well thanks! nice to know that ahaha . I have already flashed kph again, so it's all working now. But the next time, I'll do what you say. I guess I already know about adb shell, but I dont know how to use it (i get easily confuse when it comes to apply commands). Well, that's what I love of all of this. You screw things up, you get really nervous, but then you know you can solve it and it is the best ahaha.
Thank you!.
today i deodexed my /system/app/ and /system/framework/ successfully.
used root explorer to copy and paste the framework directory in place.
before i could do the same for the app directory - multiple errors resulting in a reboot to a bootloop
i have tried for a few hours now to create a update.zip with the odexed files to return to a working environment.. what i get on the screen is.. installing update.zip.. installation aborted... no errors or anything. (this is with the stock samsung recovery)
i do have a copy of the the original odexed files and the deodexed files.
clockwork recovery isnt supported for this phone yet so i can't go that route
i can't adb push the files because i need to grant adb superuser permissions from the phone.
so basically i have a nice fancy brick with a rotating droid animation on the screen.
the phone is a Samsung Gravity Smart SGH-T589
any suggestions?
btw - the firmware hasn't been released yet for this phone or i'd attempt a fix with odin.
Last I checked you may have to go a custom route to install a custom recovery. That step is always the weirdest, and it's never been the same for any of my phones. Especially if the phone isn't going to start up the conventional way...
Here are two places with more information that I found, maybe you didn't.
http://androidforums.com/samsung-gravity-smart/395877-yay-gravity-smart-forum.html
http://forum.xda-developers.com/showthread.php?p=17354030
hey thanks guy
i actually started both those threads a while back =)
i'm making progress with my update.zip
got it to install finally but still bootlooping
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
Hi all-
I have unknowingly renamed the framework-res.apk file to framework-res.bak, following the suggestion of a website (who had said to copy the file over, not rename it). I had no idea that would make the phone instantly useless, and render everything inoperative
I was rooted. All I need to do is copy the backup back over, but how?
I am able to get into CMM-based Recovery v5.0.2.7 and can mount the system directory and see it on my PC, but for some reason the framework directory is invisible. There is talk on the web about getting to a prompt and typing:
adb push framework-res.apk /system/framework/framework-res.apk
But how in the world do you get to a prompt? I don't see it on any menu, anywhere and the adb command is unrecognized on my OS.
Hoping I'm not ruined...... thanks for any advice.
Samsung Captivate Glide Android 2.3, Ubuntu
To get ADB, you first have to install the Android SDK.
http://developer.android.com/sdk/index.html
Then, you have to put ADB in the PATH variable.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that, you can just type adb in the command prompt and it should work.
Hi,
I downloaded the SDK tools and got the adb command, but when I mount the phone with recovery I still don't see any framework directory.
I got to DOS and navigated to the directory where my copied framework-res.apk file was, and ran:
c:\adb\adb push framework-res.apk L:\framework\framework-res.apk
it replied with:
1319 kb/s (7979827 bytes in 5.905s)
However, then I rebooted the phone and it won't get past the SAMSUNG screen at all, it just sits there forever.
- why can't I see the framework directory, even though I have mounted it through CWM based recovery?
- can I see it using the ADB tools?
- has just copying the copied file back over, destroyed the cell phone? I can't possibly see how.
Thanks for any help
OK I found out the problem.
you need to use forward slashes and put the whole pathname in:
C:\adb\adb push framework-res.apk /system/framework/framework-res.apk
Thats assuming you have the adb command in the c:\adb directory.
It seems the phone is working again.
WHEW! Man that file is dangerous. be warned.
[FONT="]4 - Way Reboot Menu for Nabi2 KK 4.4 ( De-Odexed )[/FONT][FONT="]Well it's that time again after getting a needed update for our tablets. This is the extended Reboot Menu only and not a "Power Menu". I do not recommend flashing to Custom Roms as the ROMs may contain special permissions/policies ( if added ) that the Rom Developer may have implemented or even may be require so the Custom Rom may run or function properly. None are known [/FONT][FONT="]for the Nabi2 ATM so I guess we are safe LOL. [/FONT] Unlike the previous version that went through the Power Button menu, this one has a dedicated Reboot Button eliminating the extra
"Power Off "at the bottom of the Reboot Menu going through the Power Button menu.
[FONT="]The Extended Reboot Menu Includes:[/FONT]
[FONT="]REBOOT[/FONT]
[FONT="]( Normal Complete Reboot after Shutdown )[/FONT]
[FONT="][FONT="]SOFT RE[/FONT]BOOT[/FONT]
[FONT="]( Quick Reboot for restarting the Android Shell only, No Shutdown )[/FONT]
[FONT="]BOOTLOADER[/FONT]
[FONT="]([FONT="] Bootloader [/FONT]Mode / Fastboot Mo[FONT="]de [/FONT])[/FONT]
Working after it's plugged in to Computer via USB Cord ( see post#2 for Youtube link )
[FONT="]RECOVERY[/FONT]
[FONT="]( Restarts[FONT="] t[/FONT]ablet [FONT="]strai[FONT="]gh[FONT="]t to[/FONT][/FONT][/FONT] Recove[FONT="]r[/FONT]y after Shutdown )[/FONT]
=========================================================================================================
=========================================
=========================================================
[FONT="]===================================================================[/FONT]
[FONT="]DISCLAIMER:[/FONT]
===================================================================
===============================================
=========================================
[FONT="]By YOU, the USER, flashing this file or manually pasting to modify your Android System, YOU understand and know what YOU are [/FONT]
[FONT="]doing. I nor [/FONT][FONT="]anyone will be held liable nor responsible for YOUR doing if your phone bricks. As always, as is suggested by many and [/FONT]
[FONT="]myself, please make [/FONT][FONT="]sure you perform a complete[/FONT]
[FONT="]NANDROID BACKUP[/FONT]
[FONT="]before flashing and/or modifying your OS or the mentioned stock .jar file. I also suggest YOU keep a separate copy of the stock .jar file [/FONT]
[FONT="]handy, [/FONT][FONT="]like in your External SDcard, if the phone decides not to boot up. Knowing this, YOU assume all responsibility for what happens [/FONT]
[FONT="]as YOU, the USER, know and comprehend what YOU are doing and understand the consequences or severity of damages that can be [/FONT]
[FONT="]brought to your [/FONT][FONT="]device by flashing or modifying your OS incorrectly. [/FONT]
[FONT="]YOU[/FONT][FONT="] Have Been Warned !![/FONT]
=========================================================================================================
[FONT="]What's Needed / Recommended:[/FONT]
[FONT="]Rooted Device [/FONT][FONT="]( to extract the needed files Manually for backup )[/FONT]
[FONT="]Custom Recovery ( TWRP for Flashing the ZIP and/or using the File Manager or a Custom Aroma File Manager)[/FONT]
[FONT="]If you can do it via ADB Commands then all power to you.....[/FONT]
[FONT="]I provided [/FONT][FONT="]BOTH[/FONT][FONT="] , the stock NABI2 [/FONT][FONT="]( Stock NABI2 KK jar )[/FONT][FONT="] and modded NABI2 .jar [/FONT][FONT="]( android.policy.jar )[/FONT][FONT="] files and [/FONT]
[FONT="]will make a flashable zip [/FONT][FONT="]( coming soon )[/FONT][FONT="] below[/FONT]
[FONT="]What To Do:[/FONT]
[FONT="]You have two choices on installing the .jar file. You can either Flash the ZIP in TWRP ( which at the moment is not available ) or manually copy & paste or push the .jar file to system/framework/. If you decide to do this manually, you will then need to set the file permissions to the modified android.policy.jar file to 0644. Before manually pasting the file in the framework folder, you can rename the stock android.policy.jar file with " .bak " ( ex. android.policy.jar.bak ) at the end so you don't have to delete it from the framework folder if you so choose. Now using TWRP you can either use the built in File Manager and set permissions via the terminal with chmod commands or Install/Flash the Aroma File Manager in recovery to use like a simple File manager where you can hold down on the file to get a popup window to copy/paste or set permissions manually.[/FONT]
======================================================================================
[FONT="]Words of caution.....[/FONT]
[FONT="]if you attempt to do this manually and are still actively booted in your Android OS while modifying or deleting the .jar file, there is the highest probability that your tablet will immediately reboot and you will not be able to boot up the OS again and remain stuck on the Nabi boot screen as the android.policy.jar is no longer visible to your OS. This is why you need to do this before booting up like in recovery.[/FONT]
======================================================================================
[FONT="]Thanks and credits go out to :[/FONT][FONT="]@[/FONT]tdunham
[FONT="]@[/FONT]CNexus
[FONT="]@kahvitahra[/FONT]
[FONT="]for the knowledge gained over the years and information gathered on the How-Too's and the files needed for this MOD. If I missed someone please PM me or let me know.....[/FONT]
[FONT="]Enjoy! [/FONT]
Change Log
Android Policy v1:1. Unlike last from JB, this KK Reboot Menu has it's own button instead of going through the Power Button.
2. Problem with Bootloader Button not working, not going into Bootloader.Android Policy v2 ( 02/28/15 ): 1. Reboot Menu has it's own button instead of going through the Power Button as before.
2. Soft Reboot ( Quick Reboot ) using smali command of "setprop stl.restart zygote" instead of "pkill -term -f system_server" for those
that do not want to or honestly need to install BusyBox to simlink pkill if not already done so. Change will not affect anything.
3. Some more smali edits to try and get Bootloader button working. Forum member n3wt discovered when attempting to go into Bootloader mode,
after reboot and staying stuck at the nabi boot logo screen, plugging in the USB cord while USB connected to computer would then switch the
Nabi to Fastboot Mode. --- link to youtube video bellow.
http://youtu.be/Qo9ShihfCqY
Any problems ...... let me know.
.
Thanks. I get error flashing zip from TWRP. I copied the jar to /system/framework and set perms to 644 but I don't see the new options even after reboot. Also the attachment says v1. Where is v2?
If you are saying its not available from the power button how do you get to the menu?
lev777 said:
Thanks. I get error flashing zip from TWRP. I copied the jar to /system/framework and set perms to 644 but I don't see the new options even after reboot. Also the attachment says v1. Where is v2?
If you are saying its not available from the power button how do you get to the menu?
Click to expand...
Click to collapse
Sorry for not responding right away, notification was not set. The zip is not a flashable. I never got around to making one. Better one knows where it's going and one backs up their original before attempting.
You get the reboot option when pressing on "Reboot". Normally, the Nabi2 stock jar does not come with a reboot option which is what I added.