I have accidentally deleted the batterystats-checkin.bin. I have tried to flash stock firmware , but it seems flashing stock firmware was not able to restore the file. can anyone share the batterystats-checkin.bin file .it is located at the root folder of /data/system.
Related
i just flashed zimage.tar via odin s i can root my gingerbread rom JV6 but it seems nothing is happening. see below image. its been an hour already! pls help i cant use my fone. i need to root it so i can restore my apps using TB. my fone is still in dwnload mode the yellow android image
You don't have to flash the zimage file. Instead flash the .tar file which you get after you extract the downloaded .zip file. When extracting, don't select extract here instead select extract to folder -- the latter would get you .tar file while the former gets you not-for-flashing zimage file.
Hi,
i was doing the kitkat SD card fix but i think i messed up my platform.xml file and now i cant connect to anything.
i cant connect bluetooth to transfer original file, wifi doesnt work, 3g not working, every app p keeps crashing.
i connect it to my PC and it doesnt show the files. just blank folder not even normal download/picture files.
plz help asap
Restore your backup. And fixed that quickly.
If you don't have a backup, that is a bad habit that you ought to change immediately. One good reason is staring you in the face.. the ability to revert changes or recover from unexpected problems.
In the alternative and presuming that you also neglected to save an original copy of the platform.xml file.. you can extract the original platform.xml from the full, stock firmware image. And use that to fix your issue. You can write the file to your handset using the command line or via an ADB shell. Or you could start over if you have other reasons for wanting to do that i.e. write a full stock firmware image with Odin. But replacing one file would make more sense in most situations.
fffft said:
Restore your backup. And fixed that quickly.
If you don't have a backup, that is a bad habit that you ought to change immediately. One good reason is staring you in the face.. the ability to revert changes or recover from unexpected problems.
In the alternative and presuming that you also neglected to save an original copy of the platform.xml file.. you can extract the original platform.xml from the full, stock firmware image. And use that to fix your issue. You can write the file to your handset using the command line or via an ADB shell. Or you could start over if you have other reasons for wanting to do that i.e. write a full stock firmware image with Odin. But replacing one file would make more sense in most situations.
Click to expand...
Click to collapse
Can you give me original files for the
G900F model which go in the permision folder.
Thanks
aniqpirzada said:
Can you give me original files for the
G900F model
Click to expand...
Click to collapse
No. I own the 900T model and would need to extract the 900F file from the stock firmware image. And you can do that as easily as I could. Just download the firmware image and use winrar to extract the file for you. Easy peasy.
.
fffft said:
No. I own the 900T model and would need to extract the 900F file from the stock firmware image. And you can do that as easily as I could. Just download the firmware image and use winrar to extract the file for you. Easy peasy.
.
Click to expand...
Click to collapse
i will try to extract it but if it doesnt work:
if i flash the FW using ODIN would it wipe out all my data from the phone.
or should i flash the FW using CWM
i tried flashing the official FW with odin and it didnt fix it. plz help ;(
Hi,
Yes. I screwed up
copied over a new build.prop to /system but I didn't change permission or might have made a mistake. So now my phone doesn't boot into android, or TWRP!
The only thing I can go into is the Samsung S4 Downloading window, I think it's the Odin screen.
I have Odin 3.0.7 (I have i337m)... and wouldn't it be possible to just flash a tar file or a zip file that can do the following:
delete /system/build.prop (The one I screwed up)
rename /system/build.props.bak to build.prop
That is all I need to do to fix my bricked phone!! OTherwise I guess I would have to flush using odin the while Samsung thing and might lose root and reflash kankapop!!!
Any help would be appreciate in the file I need to use.
I noticed Odin has a File [Dump] .. maybe I can use that?
Thanks,
You would need to flash a custom recovery through Odin, then you would have to create a flashable zip for flashing through the custom recovery. In the flashable zip would be the original, unmodified build.prop, the updater binary, and the updater script. The script would issue the command to copy the new build.prop over the old one and set its permissions.
AFAIK, you can't use Odin to send single files like that.
If you have checked out, downloaded and flashed RaymanFX's latest CM13 Unofficial Nightly ROM for Note 4 N910C/H/U users here: http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878 chances are you failed miserably at getting back to Samsung's Stock Firmware as you have encountered a series of unending bootloops. The bootloops exist because your downgrading from Android 6.0.1 Marshmallow (CM13 ROM) back to Android 5.1.1 Lollipop (Your previous Original Samsung Stock Firmware), however if you've received the Android Marshmallow Update for your Note 4 model number and region as an OTA Update from your device or Manually by downloading it from sammobile.com or any other external link and have flashed it before flashing CM13 no need to worry you won't need a backup of your Samsung firmware (Unless you want one) as you can perform a clean install of your Samsung Marshmallow Firmware via Odin v3.10.7 Here is where the fix lies; i have compiled a series of posts from 2 very helpful XDA Members from the community because from my experience i have managed to rescue my device using their methods which i will mention below.
Firstly if you have made an Efs partition backup from your previous Original Samsung Stock Firmware in the form of a .tar or .img file e.g "efs_backup_2015-06-01_02-37-16.tar" or "efs.img" respectively then you are good to go if not leave this thread.
Also you will need to download a Note 4 N910C/H/U Pit file corresponding to the region of your Samsung Firmware so here is a link to a selection of pit files. You will need to create an account at sammobile or simply sign if you have a current account to see the download links here: http://www.sammobile.com/forum/showthread.php?t=30022
Follow FR34K-B1B0's helpful post on getting back to stock here: http://forum.xda-developers.com/showpost.php?p=65414257&postcount=39 Skip the 1st Step since we are restoring our IMEI using our backed up Efs file and we will be using a different method to restore this backup.AND AFTER ODIN IS DONE FLASHING THE SAMSUNG FIRMWARE there is a chance that your phone will boot to the Stock Recovery and you will notice a message down there saying: "dm verification failed" so simply wipe data/factory reset and wipe cache and then reboot. Afterwards your phone should boot properly. Now close he's post and carry on down here.
After your phone boots up and you have set it you will notice that your mobile is not connected to your specific mobile carrier and you will see the Emergency calls only text on your lockscreen hence the Not registered on network error. Go to Settings--->About device--->Status and scroll down and you will search and find that your IMEI is literally not the one your phone has and that your Serial number is of an Android Serial number given to you from flashing CM13( Since it's a pure stock android software). If you want you can download the Phone INFO App from the Playstore to verify your device's information and if you do so you will notice that your Samsung Serial number is a bunch of 0's like this: 0000000000 or it's not even present hence wiped.
HERE IS THE MOST IMPORTANT PART FOR RECLAIMING YOUR MOBILE NETWORK CONNECTION, your IMEI is wiped and so you must restore it using your Efs backup file which i mentioned previously above. To do so you will need to root your device and the guaranteed way of rooting your device is using Chainfire's CF-Auto-Root Method.
Here are the links to the Odin flashable MD5 files based on your Note 4's Model Number that you must download ---> For SM-N910C: https://download.chainfire.eu/559/CF-Root/CF-Auto-Root/CF-Auto-Root-trelte-treltexx-smn910c.zip For SM-N910H: https://download.chainfire.eu/577/CF-Root/CF-Auto-Root/CF-Auto-Root-tre3g-tre3gxx-smn910h.zip For SM-N910U: https://download.chainfire.eu/557/CF-Root/CF-Auto-Root/CF-Auto-Root-trhplte-trhpltexx-smn910u.zip After downloading the file on to your computer simply load the file through Odin, power off your phone and boot it to download mode then connect your device to your computer and flash the md5 file. After it's done flashing your device will boot to a custom screen with a red android logo then it will boot.
Right now your device is rooted and you will see the Supersu app in your app drawer. Next if your Efs backup is stored on your computer and is of the format .tar simply open it with 7zip or Winrar you will find the .img present then extract it your desktop. In order to restore your IMEI with this .img file we will need an update package that we can flash from a custom recovery(CWM or TWRP). Here is the link to civato's awesome flashable update package: http://forum.xda-developers.com/showthread.php?t=2331853 and you'll find the package down in the attachment. After downloading the attached file, rename your Efs backup file from "efs.img" to "EFS.img" then extract the contents of the downloaded update package to a folder with the same name of the package, copy your EFS.img file to it and use 7zip or Winrar to add the files to an archive(.zip).
Last but not least copy the new repackaged flashable zip to your external or internal sd card. Run Odin and flash your desired Custom Recovery(CWM or TWRP). Boot to the custom recovery and flash the update package and finally reboot system. After booting your phone will have it's Efs partition restored; your IMEI and Samsung Serial number will be back and your mobile network will be back on again. :fingers-crossed:
Special thanks to FR34K-B1B0 for he's helpful post on getting back to stock firmware
And Many Many Thanks to civato for he's really useful Efs restoring update package! :victory:
And last but not least thank you Chainfire for your great CF-Auto-Root Method that helped root our device(s).
Lot of confusion please help i want to go back to stock for my gear VR
According to
this thread where i posted photos of my phones INFO
I downloaded N910F( UK BTU) 6.0.1 firmware (.ZIP) file
When i tried to flash using TWRP it says ZIP file is corrupted.
I downloaded it from two website
sammobile
and
samsung.org
both are corrupted(it should not be i think)
When i look into it it has only one file .tar.md5
i tried to extarct it using winrar and it says file is corrpted
\BTU-N910FXXS1DQFA-20170726090446.zip: The archive is corrupt
Although it extracted the N910FXXS1DQFA_N910FBTU1DPL1_N910FXXS1DQA1_HOME.tar.md5
In both files i got the same result same
i dont know what to do now
I tried Odin and it stuck at "there is no pit file partition" or something like that
(yes i wiped out cache and system delvik etc.)
I also tried inserting PIT file but no luck
i would prefer without Odin if possible
As I can go into TWRP recovery
Please guide me or at least answer a few question
1. Is it even possible to flash stock rom using twrp like i flash other roms?
2. Can i install extracted .md5 file from that zip? will it be the same like stock zip?
3. Why my Both zip files are corrpted? your opinion?
4. Should i download again same stock rom?
5. Can / Should i flash or download and /or downgrade Stock firmware (same 6.0.1 )but different release date?
6. Am i downloading the right firmware for my device here is my device details posted??
Lot of confusion please help i want to go back to stock for my gear VR
Based on the amount and type of questions, I believe you need to read up on basic Note 4 flashing/customization knowledge first. Go and read up on the stickies.
Without knowledge and experience, we can tell you how to do a brain surgery, but doesn't make you a surgeon.
No, twrp cannot be used to flash stock rom. Stock rom are most of the time md5 files, used by ODIN only.
Since you downloaded the zip files, use the "Test" function to see if it is corrupted?
Maybe you should just flash a stock based custom rom with VR and be done with it.
https://forum.xda-developers.com/no...om-bob4-devbase-multi-csc-safe-bloat-t3033881
---------- Post added at 01:13 PM ---------- Previous post was at 01:05 PM ----------
Oh, according to your screen shots, DBT is in a carrier in Germany?
I installed BTU (UK) stock rom and it is is working fine (using odin)
nicholes said:
Lot of confusion please help i want to go back to stock for my gear VR
According to
this thread where i posted photos of my phones INFO
I downloaded N910F( UK BTU) 6.0.1 firmware (.ZIP) file
When i tried to flash using TWRP it says ZIP file is corrupted.
I downloaded it from two website
sammobile
and
samsung.org
both are corrupted(it should not be i think)
==================================================
Check your Winzip version. It may be old and doesnt handle large zipfiles too well. I had the same problem but I know the file was good as I downloaded it at work, and Winzip worked just fine; but when I got home, winzip failed on my pc - old 8.1 version. I used the trial version just fine to unzip.
Click to expand...
Click to collapse
Flashing Rom
"I downloaded N910F( UK BTU) 6.0.1 firmware (.ZIP) file
When i tried to flash using TWRP it says ZIP file is corrupted.
I downloaded it from two website "
Did you keep the ROM as a Zip file when you loaded it in to Odin?
Do not unzip the ROM file.
Try again.
Fool2242 said:
"I downloaded N910F( UK BTU) 6.0.1 firmware (.ZIP) file
When i tried to flash using TWRP it says ZIP file is corrupted.
I downloaded it from two website "
Did you keep the ROM as a Zip file when you loaded it in to Odin?
Do not unzip the ROM file.
Try again.
Click to expand...
Click to collapse
As far as I remember it was zip file