Greeeeetings.
Is there anyone here that owns, upgraded to Che2-L11 V100R001C636B360, and rooted their device?
The download for the version is; http://consumer.huawei.com/my/support/downloads/detail/index.htm?id=60764If true, may anyone please upload your "OEMInfo" file here? I've accidentally forgot to back it up, and completely lost it. There weren't one online for Che2-L11 that I've attempted to find.
Using "ES File Explorer Manager app" (enabled root explore within the app's settings), you can navigate to your root device, and get the OEMInfo file from the following path;
"dev/block/platform/hi_mci.0/by-name/"
May anyone upload it here? Pretty, please?
Please be careful navigating around that part of device, accidental modification to the files within the root may brick your device.
Here's the much detailed explaination of how to get it, with pictures;
First, open ES File Explorer. This is how it is like, isn't it? You can open a menu that is rotated "iii" from the top left.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, you can enable "Root Explorer" slightly at the bottom of the "Tools" drop-down category.
Next, scroll back to to the top where you'll find the "Local" drop-down category, select it, and select "Device /", which it will take you to your root.
Now, the root should be like this. Noticed that the first folder you'll see is the "dev".
That's right, from here, you have to navigate through the following folders.
"dev/block/platform/hi_mci.0/by-name/"
Or in other words, "dev => block => platform => hi_mci.0 => by-name"
Scroll slightly down within the directory, and you should able to find "oeminfo".
Hold down your finger (long press) on the "oeminfo" file, until it gets selected like this. If so, then select the vertical ". . ." at the top right to bring down a menu.
The ". . ." menu are like this. There should be "Copy To". Select it.
The "Copy To" screen should be like this. Press the backward arrow "<-" until you see "Storage/SD Card 1", this is where you should copy the "oeminfo" file into.
Bravo! should should get a pop up message that the transfer should be complete. (hopefully).
You can then get the "oeminfo" file from your SD Card and send it over.
Thanks, awaiting response.
Much sincere appreciation.
Thanks!
Related
I used the ota blocking root. The one with the video and all is well. I love my rooted Nikki and the smart minds of this community, so thanks to all. Moving on, I used the option in the computer. .bat file that gave the option of pressing the physical ''n" button key to back out to home. I don't like it because it doesn't allow me to pull up the option menus in some apps, which is important since the taskbar doesn't always show, like in emulators and I also miss the menu it pops up at home screen with the search etc.
So, i'm wondering if there is a way to return the "n" button to default without rerooting? Thanks to all who help.
Also, I can't open my keyboard setting to turn off the auto- correct feature. It's annoying. It force closes every time, even if I reboot.
This is the stock SystemUI, rename it to SystemUI.apk. Took it from the acclaim_update.zip
StockSystemUI.apk
~ Veronica
Would I just rename and drop it in the root folder from my pc?
Majinjin said:
Would I just rename and drop it in the root folder from my pc?
Click to expand...
Click to collapse
root folder? you mean to reroot? there is no need to reroot just rename the file copy it to your sdcard and then by suing ES file explorer or Root explorer Cut/move it to /system and paste it, then long press SystemUI.apk now if you used Root Explorer (not free) select permissions from the list and change it to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once done long press it again but now pick change owner from the list (scroll down is at the end of the list) and change:
Owner: 0 - root
Group: 0 - root
If you used ES file explorer (free) then long press SystemUI.apk and select properties from the list, change permissions same as in the pic i posted above.
Once done that cut/move it to /system/app folder
REBOOT to finish
~ Veronica
I will give it a try when I get some time to myself, thanks.
With the help of 7786 and lots of time spent to fix the code on the IronRom's NavBar, I have finally finished the Media/Volume Navbar for the Galaxy Tab S 8.4 for TouchWiz.
This mod not only enables the NavBar, but it is modified to change Volume for those installs where a Volume Knob is not an option like mine. Also has the Previous, Play/Pause and Next Playback functions. The Google Logo opens the Google Search when held for a second. I for one really don't care to have a Search Engine taking up valuable space on my Screen (despite the ScreenShots [emoji14])
On Certain Launchers, for example Apex Launcher, The Navbar is Transparent. I don't know what other Launchers are like this But it looks great.
Download Links Under Corresponding Photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: http://1drv.ms/1R3dyqO
Red: http://1drv.ms/1R3dA1Q
Green: http://1drv.ms/1R3dxDk
Blue: http://1drv.ms/1R3dDLk
How to Install Mod:
1. Download Zip 2. Enable Soft Keys 3. Restart Into Recovery 4. Install Zip 5. Clear Dalvik/Cache 6. Enjoy
How to Enable Soft Keys:
Section 1: Pre-requisites
You need to have root access on your device.
Install Root Explorer or ES File Explorer or any file manager with which you can access the system partition. Below steps are given for Root Explorer.
Make sure your device is at least 70% charged to avoid complications during the process.
Section 2: Procedure
Open your preferred file manager and mount the system partition as read-write in stead of read only. Grant superuser access when it prompts.
Go to the system folder present in the root of file system. i.e the path- /system
root explorer
Now open the file “build.prop” in any Text Editor. For Root Explorer users, long click on “build.prop” file and tap on “Open with Text Editor”. (Before editing this file, for a safety, copy this file to the external memory card and save as a backup.)
build.prop
Now add the following line to this file at the end:
Code:
[CENTER]qemu.hw.mainkeys=0[/CENTER]
Save and Exit.
Now reboot your device.
Voila! You now have soft keys on your device!
If soft keys are still not enabled, please check if you have typed in the exact line as above. There are some apps which do this for you with a single click. But these apps may cause boot loops. Happy Androiding!
Original MOD for the Nexus 7 2013 by 7786 can be found HERE
Hi everyone.
I've a Nexus 5 which runs Android 6.0.1 but I think the problem is not especially related to the Nexus 5, so I post here.
What happened ? Few days ago my phone crashed (I didn't use it) and was slow to boot up. So I tried to force the reboot by pressing the power button for 15/20s and it worked.
But 5/10min after I saw the "Select language" menu ... The phone performed a factory/reset by itself. I don't know why.
First, I plug my phone to my computer and I've seen that 26GB/32GB were already in use.
So I tried to recover my pictures and videos with many apps and the one which worked was "Undeleter" (5$) but it didn't recover all my data.
Yesterday, I wanted to understand what happened really. I ran "DiskUsage" which give me this result for /storage/emulated/0 :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can I access to the "System data" partition which has a size similar to the storage space used before the crash ?
Regards,
Laurent
EDIT :
Finally I backed up all my data !
Indeed, files of my memory (/sdcard) before the crash was in /data/lost+found/#1351681/0
Then, I was able to move them to /sdcard and to copy the files on my PC.
How to ?
Make sure your phone is rooted and install a file explorer such as Root Browser.
Open Root Browser and navigate until /data/lost+found/#xxxxx [in my case, with a Nexus 5 it was 1351681/0]
(Look for the directory which corresponds to your previous "sdcard".)
Now, you can see the files but you can't open them. So move (not copy!) them to /sdcard (I suggest you to do that folder by folder).
Great, you've recovered your files ! But now, transfer them to your computer to prevent damages (I was forced to do that and remove files after to continue because the storage was full).
You can do it in connecting your phone to your computer and via the explorer or you can use adb (adb pull /sdcard/directory_to_move path_to_a_dir_of_your_computer)
I hope it will be useful.
Laurent
Hello everyone...
I find the phone with the non-working tuch ..
From the recoveri mode I managed to make a complete backup of the phone on sd and generated these 3 files:
userdata_20160101_000035.backup
userdata_20160101_000035.backup1
userdata_20160101_000035.backup2
is there a possibility to extract the content ???
I would be interested in contacts.
I state the phone is a Majestic
Thank you.
recovering contacts is not easy. you need SQLite Forensic Explorer to view the database file. the database is separated in many different tables, each table has a column "raw_contact_id" which contain always the unique id-no of contacts (one table contains phone nos, another table contains names, etc... you must query tables by id).
once you have extracted the backup, the file "contacts.db" is located "/data/data/com.android.providers.contacts/databases/"
from the backup I made, how do I extract the contacts.db file ??
remove the checksum(s) and merge the files. you need linux
don't be scared, i will explain you step by step. first step: do you have linux? if yes, press CTRL + ALT + T this is the terminal where you can do it. if no, please download unetbootin and prepare a bootable usb stick. you can run ubuntu on your pc without installing. don't hesitate to ask if you need help regarding unetbootin
scacco728 said:
finally I was able to understand something of the terminal in place ..
I move to the folder where the files are, I open the terminal I enter the commands and I generate this error .. why do you think ???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
"dd" does not accept wildcards. press <TAB> instead of * for word completion. you must type the full file name. remove the stars in this example code.
edit: i will answer in this thread, because this are linux basics. so lets open a "beginner" thread here, and leave the other thread open for more advanced questions. finally, your goal is to extract contacts, what we should not discuss in main thread
I renamed the phone S9+ to something different on 8. Updated to beta 9 and everything stuck. Google showed the name of the device online to what I renamed it to. No problems.
Factory reset the device, renamed device under the about settings area. Under bluetooth, there isn't an option to change device name or anywhere else I have looked. Computers see it as Galaxy S9+, Google online sees it as Samsung Galaxy S9+.
What am I missing here? Is there another setting or renaming somewhere so the phone 'Identifies' as what I name it?
Anyone?
Try doing the following:
Go to "settings" and then "About Phone"
On the top should be the words "Galaxy S9+" and a little button under it labled "edit"
Press the edit button and little window appears. The window informs you that the name you enter will be shown on other devices when your phone is available to connect using Bluetooth, Wi-Fi Direct and other methods.
Enter the name you want to be shown and press done.
I've done that. Google still identifies it as the device, not the renamed device. So online using the find device feature, it still shows the device. Not the renamed device name.
Does this make sense?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4714566View attachment 4714567View attachment 4714569
There's rename option on the application.
Yes. This too, I am aware of. However, before, when I renamed on Android 8, it renamed it automatically across the board. Now on 9, it doesn't.
sarjarim said:
There's rename option on the application.
Click to expand...
Click to collapse
skygear said:
Yes. This too, I am aware of. However, before, when I renamed on Android 8, it renamed it automatically across the board. Now on 9, it doesn't.
Click to expand...
Click to collapse
Maybe, just maybe, Samsung doesn't give the right for the application to read the device name. Or google use the one registered first, no update. The point is there's sollution for your problem, manual but effective.