Seeking help directly from developers as posting in general section has not yielded any help past few days.
I flashed ZCKPL Chinese stock rom from here
Rooting was quite a trouble as 2 methods of rooting both were breaking some of its features hence a member on xda @chongns ported a fresh CF root & that finally worked.
Since then I am having a strange problem & have flashed & re flashed over 30 times in various combinations but nothing is solving the problem on ZCKPL.
Summary of the problem
Whenever I call a contact or they call me, their names are not showing up and only numbers show as if they are not in my contact list (And I don't have a clue on who is calling). But if I check my call logs later, I can see their number along with their name. I want to see their names while they are calling. How do I do it in my case? As I recall there was some GB firmware it has this issue but was sorted out too.
I had backed up my contacts using super backup & restored using the same, on earlier many times of zckpl installs & never faced any issues with other rooting methods they had other issues though but not this bug.
Ganesh CF root does not work at all for ZCKPL
Bam kernel v15 breaks call recording
VurrutKER_stock_v9.1 breaks wifi
Amit Bagaria CF universal root breaks wifi,
A brief summary of resolutions I tried but failed every time
1. ZCKPL factory reset without formatting the internal card, this keeps the CF root rest all apps go away, signed to google account it started sync then installed super backup> restored contacts they give the same problem.
2. ZCKPL factory reset + formatted the internal card, all aps including CF root gone then signed to google account it started sync then installed super backup> restored contacts they give the same problem. (This was to root out if Cf root has created this issues or not)
3. Installed DDLF full rom with 3 files > then without adding any google account restored the backup from Super backup, all worked fine on DDLF2 no problems now all contacts name show when number is called.
4. DDLF2 factory reset + formatted the internal card > flashed ZCKPL then added 1 phone contact & called it works fine on ZCKPL, then the contact called that too worked fine. All this while no goggle account added as yet.
5. ZCKPL factory reset + formatted the internal card once again then without adding any google account restored the backup from Super backup, all contacts show but when i call they don't show calling number, when someone else calls they still don't show but call logs show them all.
6. So at this step I exported contacts to external SD card using contact import/export to .vcf file.
7. ZCKPL factory reset + formatted the internal card once again then without adding any google account restored the backup this time by importing them from .vcf file(no super back this time) but the problem remains as it is called number does not show at all where as on stock zckpl if I add manually then it does work as usual.
8. ZCKPL factory reset + formatted the internal card once again then CF root applied I manually added contact & called surprisingly the called number now does not show. Deleted the contact & imported from .vcf file & contacts show in contact list but when I call a contact they don't show any name of the called person.
9. Installed DDLF full rom with 3 files > factory rest+wipe data
10. then once again Installed DDLF full rom with 3 files > factory rest+wipe data
11. installed ZCKPL added a contact manually asked them to call me it works fine
12. applied the new CF root & flashed the gapps in recovery
13. tried calling the same contacts now the name does not show
so something wrong is happening with gapps/ google account & CF root
14. This time I was advised by @SikanderKeynes
Restore your backup with superbackup then take backup again with mybackupro. delete all your contants and restore contacts with mybackuppro. Remember in Mybackupro menu>options>uncheck "Google contacts" before doing anything.
Click to expand...
Click to collapse
15. Installed DDLF full rom with 3 files > factory rest+wipe data
16 installed ZCKPL + CF root & restore contacts with mybackuppro.
This time I took a backup from google contacts & deleted all contacts from my google account then followed the same procedure, even then it fails the same way.
So I am now getting to believe that CF root right from amit baragia version may have some bug which is indeed contributing in some or the other way in displaying the contacts name.
I cant find the code to change CSC to INU its set to CHN that might be one of the issue.
So the finding concludes the following.
1. CF root may or may not have anything to do with this bug,
from steps 2-7 all this while the phone was not rooted at all
2. Google sync is not creating this problem as I didn't even add any account from step 3-7
3. Super backup could be creating some issue the format in which it does the backup, which has then been inherited by other backup methods.
4. ZCKPL itself without root does not show this problem if I add the contacts manually
Now I have a kies backup too but I really don't want to install that stupid software & mess my system, its just a pain whenever I had to deal with it. So I rather prefer that I add contacts manually which will take me many days to do so as there are over 2000 contacts.
Can any of experienced developers help me to sort this problem, 1st we need to find the source of the problem & then you may need to mod some file/setting to make it work correctly.
Looking forward to hear from the developers.
Update
When I am getting calls from number in other states (outside my local area) whose number is not saved in international format +91-10digitmobile no. That time I see some Chinese location name on the caller name.
But when I have other numbers calling whose format is in correct international format +91-10digitmobile no even then its not showing name of the caller.
Is it a problem with contacts app?
is it a problem of format in which numbers are saved?
is it a problem that CSC (CHN) is not able to read the contact format at the time of the call but after call logs show the name?
Please help someone must be knowing the answer to this problem.
sgsI9003 said:
Update
When I am getting calls from number in other states (outside my local area) whose number is not saved in international format +91-10digitmobile no. That time I see some Chinese location name on the caller name.
But when I have other numbers calling whose format is in correct international format +91-10digitmobile no even then its not showing name of the caller.
Is it a problem with contacts app?
is it a problem of format in which numbers are saved?
is it a problem that CSC (CHN) is not able to read the contact format at the time of the call but after call logs show the name?
Please help someone must be knowing the answer to this problem.
Click to expand...
Click to collapse
i suspecting the CFRoot sqllite is causing the problem.
cause after you flash the cfroot, there are few lib file been overwrited.
Oh so you also believe that CF root may be contributing to this problem.
Can we do something to sort this out or is it inherited from amit bagaria base version?
I tried my best to go step by step so I could reach some conclusions.
sgsI9003 said:
Oh so you also believe that CF root may be contributing to this problem.
Can we do something to sort this out or is it inherited from amit bagaria base version?
I tried my best to go step by step so I could reach some conclusions.
Click to expand...
Click to collapse
Try this mod ramdisk from BAM CWM Universal RC15 but using ZCKPL original kernel
this is aim to remove CF-root mod, replace with CWM but retain ZCKPL zimage so you can use 2 way call recording.
ZCKPL kernel file size is bigger, it have 7mb, usually those CFroot size is about 6.5mb.
didn't know is it can cause bootloop or not, but if i'm not mistaken our Kernel max size is 8mb
Oh great that was fast I will be able to try this after 3 hours from now. Will update by then. Keeping fingers crossed hope it works.
I flash ZCKPL & then apply this modified CWM then restore contacts all this while I wont sign in to google account ....is that right procedure?
sgsI9003 said:
Oh great that was fast I will be able to try this after 3 hours from now. Will update by then. Keeping fingers crossed hope it works.
I flash ZCKPL & then apply this modified CWM then restore contacts all this while I wont sign in to google account ....is that right procedure?
Click to expand...
Click to collapse
1. clean flash ZCKPL
2. factory reset using *2767*3855*
3. flash this CWM
4. test those issue before you flash gapps
1. installed ZCKPL & factory reset using the code *2767*3855# then added 1 contact called that number & the name shows without any problem. Everything working fine.
2. restored contacts with .vcf file which I had exported from the contact book itself, called the number everything working fine names show but additionally it shows above the contact name Xinjiang Tulufan seems some kind of China telecom operator.
3. Restarted the phone called again to double check everything working fine with call recording & caller names, (all this while no Google account no rooting as yet)
4. flashed CF root ZCKPL-CWM-08-08-2013.tar & Call names disappear now called names are not showing for incoming /outgoing any calls. So its indeed CF root which is doing mischief. CWM reports you are using some older version kernel hence some features are disabled No gapps no google account as yet.
5. Repeated step 1-2 then flashed older CF root which you had provided ZCKPL-CWM-29-07-2013.tar that also not displaying caller names but surprisingly its shows Xinjiang Tulufan
6. installed ZCKPL again without factory reset so root files are gone & my older contacts /logs remained as it is caller name again shows & working perfectly fine.
So Its the CF root which is over writing some of these files hence its breaking this feature. I cant take back of these stock rom files since phone is not rooted so its a catch 22 situation.
I flash ZCKPL to check on you issue. the below is what i found
my flashing step
1. flash ZCKPL on Odin 1.85 on PDA
2. reset using code *2767*3855#, than testing.
4. change CSC to CHN by code *#272*[imei nuber]#, choose CHN than install. phone reboot
3. flash ZCKPL-CWM-08-08-2013.zip
4. Phone auto reboot (do you have this?)
5. testing again
Click to expand...
Click to collapse
1. installed ZCKPL & factory reset using the code *2767*3855# then added 1 contact called that number & the name shows without any problem. Everything working fine.
confirm
Click to expand...
Click to collapse
2. restored contacts with .vcf file which I had exported from the contact book itself, called the number everything working fine names show but additionally it shows above the contact name Xinjiang Tulufan seems some kind of China telecom operator.
confirm for the called number and ID, but the Xinjiang Tulufan not showing anyway for me
Click to expand...
Click to collapse
3. Restarted the phone called again to double check everything working fine with call recording & caller names, (all this while no Google account no rooting as yet)
confirm
Click to expand...
Click to collapse
4. flashed CF root ZCKPL-CWM-08-08-2013.tar & Call names disappear now called names are not showing for incoming /outgoing any calls. So its indeed CF root which is doing mischief. CWM reports you are using some older version kernel hence some features are disabled[/COLOR] No gapps no google account as yet.
my caller name is showing for incoming and outgoing.
BTW, ZCKPL-CWM-08-08-2013.zip have removed the cfroot patch for replacing the stock lib files. so it should not replace any file in the system folder.
CWM will show that warning cause i not using cfroot kernel
{
"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
5. Repeated step 1-2 then flashed older CF root which you had provided ZCKPL-CWM-29-07-2013.tar that also not displaying caller names but surprisingly its shows Xinjiang Tulufan
cant confirm, the Xinjiang Tulufan not showing up anyway for me
Click to expand...
Click to collapse
6. installed ZCKPL again without factory reset so root files are gone & my older contacts /logs remained as it is caller name again shows & working perfectly fine.
So Its the CF root which is over writing some of these files hence its breaking this feature. I cant take back of these stock rom files since phone is not rooted so its a catch 22 situation.[/QUOTE]
my caller name is showing for incoming and outgoing.
Click to expand...
Click to collapse
In the screen shot you posted it does not show caller name only showing the number which you have masked with white.
In my case there are 3 lines as follows (cant take screenshot as I am not rooted)
Xinjiang Tulufan
caller name
caller number
BTW, ZCKPL-CWM-08-08-2013.zip have removed the cfroot patch for replacing the stock lib files. so it should not replace any file in the system folder.
Click to expand...
Click to collapse
Then I have no clue what is happening during CF root that name stops showing after that, I remove it by re flashing ZCKPL the name start showing again.
May be there is a way telecom company servers detect the global mobile numbers & its being read from some hard code in the system which is getting replaced when applying Cf root.
Can you think of any other reason of this bug?
Thanks for all your time & effort in trying to solve my problem.
sgsI9003 said:
In the screen shot you posted it does not show caller name only showing the number which you have masked with white.
Then I have no clue what is happening during CF root that name stops showing after that, I remove it the name start showing.
May be there is a way telecom company servers detect the global mobile numbers & its being read from some hard code in the system which is getting replaced when applying Cf root.
Can you think of any other reason of this bug?
Thanks for all your time & effort in trying to solve my problem.
Click to expand...
Click to collapse
the SS you taken form my short, is the one without contact detail in phone book, i tried with and without contact detail in phone book to check on it.
the Photo with contact start from 33*** is the one i import from .vcf after flash the CWM 08-08-2013.zip.
edit: maybe you try my flash step 4 to see will it help
2. reset using code *2767*3855*, than testing.
Click to expand...
Click to collapse
In my case this code does not work I have to use # instead * at last *2767*3855#
4. change CSC to CHN by code *#272*[imei nuber]#, choose CHN than install. phone reboot
Click to expand...
Click to collapse
This is what I want to do but this code is not working for me which gives a list of CSC codes may be I need to change this to INU since I am in India
3. flash ZCKPL-CWM-08-08-2013.zip
4. Phone auto reboot (do you have this?)
Click to expand...
Click to collapse
This flashing happens in download mode via odin so the phone reboots & then I get normal samsung logo & boot animation & full menus visible after that, at this stage should it reboot again? if yes then I am not sure that after full booting did it reboot or not.
I will try to make a zip file for the CSC from DDMF1 for to inject into the system CSC
sgsI9003 said:
In my case this code does not work I have to use # instead * at last *2767*3855#
opps, u r right, my typo error.
Click to expand...
Click to collapse
This is what I want to do but this code is not working for me which gives a list of CSC codes may be I need to change this to INU since I am in India
This flashing happens in download mode via odin so the phone reboots & then I get normal samsung logo & boot animation & full menus visible after that, at this stage should it reboot again? if yes then I am not sure that after full booting did it reboot or not.
Click to expand...
Click to collapse
chongns said:
I will try to make a zip file for the CSC from DDMF1 for to inject into the system CSC
Click to expand...
Click to collapse
CSC for DDMF1 attached
Do I flash this UPDATE-CSC-DDMF1.zip in recovery mode?
Then apply CF root once again
or should apply CF root then apply this CSC?
4. change CSC to CHN by code *#272*[imei nuber]#, choose CHN than install. phone reboot
Click to expand...
Click to collapse
Ok finally I managed to get the CSC list menu it only shows CHZ & CHN.
CHN is selected as of now I assume once I update the UPDATE-CSC-DDMF1.zip it will show me India codes too which I select & apply.
Awaiting your reply before I move out then will try this in the late evening.
sgsI9003 said:
Do I flash this UPDATE-CSC-DDMF1.zip in recovery mode?
Then apply CF root once again
or should apply CF root then apply this CSC?
Click to expand...
Click to collapse
flash after CF root, else you wouldnt have CWM recovery to flash this zip, right ?
chongns said:
flash after CF root, else you wouldnt have CWM recovery to flash this zip, right ?
Click to expand...
Click to collapse
Silly me dint think of that will apply this in the evening when I return back.
sgsI9003 said:
Silly me dint think of that will apply this in the evening when I return back.
Click to expand...
Click to collapse
ok, I found problem on ZCKPL-CWM-08-08-2013.zip, the /data somehow not able to mount correctly.
i revert to BAM ramdisk fully. please find below download.
beside i flashed my region CSC (DXKP9) and gapp, also converted to ext4 every thing is good.
*bonus a zip to revert to samsung boot screen
Download
ZCKPL-CWM-09-08-2013
Gapps
Talk
EXT4 Converter
Samsung Ori Boot Screen
Thanks to XDA_Bam for the Ram disk and amit for the ext4 convertor app
I am starting to flash just need to confirm
ZCKPL > then restore contacts > CF root CWM-09-08-2013
do I need to flash CSC-DDMF1.zip or not?
Related
Ok I've searched for a while and couldn't find anything. I couldn't get the SDK workaround to work.
I put the wrong patten in too many times and now it's asking for my gmail username/password. I've put in everything I can think of but it never works. I NEED some of the texts on there and yadda yadda. Is there ANYWAYS to get around this?
Put in your Gmail and type "null" for your password
Sent from my GT-I5800 using XDA App
Do I need to be connected to the internet? My account is under @Yahoo so would I need to sign in with that?
Thanks for the help..
Update: Null doesn't work =/
Ok. I'm offering $20 to the first person who can help me fix this. I'm on Froyo (latest version) on an HTC HD2. I just NEED to get past this unlock issue. Resetting the phone is out of the question
i'll give it a try, maybe $20 will buy me a new scarf.
so you forgot both your pattern AND your google account? or did you not have a google account on there? or what.
I have a gmail account on there and I've tried every possible combination I would use and it doesn't let me on. I'm out of ideas here
Are you putting in the whole gmail address or just the first part before the @ ?
I'm putting both
It's [email protected] and I've tried @yahoo - @gmail [email protected] Etc..
Nothing works.
This really shows why its important to remember what account you put on the phone even if its not the email you use.
Sent from CM6 on my T-Mobile Mytouch 4g via Tapatalk.
Yes.. Yes I know that.
The thing is that I've tried EVERY gmail account I have.. That's only two though. I've read that there's a bug that causes me to not be able to log in or something?
Is there ANY way to set the default to Disk Drive instead of charge only? If I could do that I could use the adb method..
Anyone? =/
Try factory resetting
Sent from my GT-I5800 using XDA App
One possible solution...
Did you have root?
If you hopefully did,
1) install a custom recovery using adb
2) reboot phone into recovery mode
3) create a nandroid backup (not with ext)
4) wipe data, cache, dalvik-cache, rotate settings and battery settings, NOT SD-EXT
5) restore nandroid backup and phone will be restored.
6) reboot
siidheesh said:
Did you have root?
If you hopefully did,
1) install a custom recovery using adb
2) reboot phone into recovery mode
3) create a nandroid backup (not with ext)
4) wipe data, cache, dalvik-cache, rotate settings and battery settings, NOT SD-EXT
5) restore nandroid backup and phone will be restored.
6) reboot
Click to expand...
Click to collapse
YES! I'll look into this. Thank you!
Fix from the Android issue tracker
It seems during an incoming call, you can back out to Home & access settings to disable the pattern lock or reset your phone's designated email account. There are a bunch of workarounds posted in the Android issue tracker, bug 4784 - try to see if any suggestions help you:
h ttp ://code. google.com/p/android/issues/detail?id=4784
The workaround in comment #35 worked for me, I disabled the pattern lock altogether.
hth,
- C
Stock Jelly Bean Factory Images with Root, Custom Recovery, Unlocked Bootloader and No Data Wipe
{
"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"
}
Description: This is a guide that will help you flash a 99% stock factory image for the official Jelly Bean leaks for Verizon Galaxy S III overwriting every partition on the device to stock. The ONLY major change I have made is for your convenience it keeps all your data/apps/settings and internal storage partition in tact. In addition to that I have also provided a small mod in the image that allows the following options below as optional flashes.
Flashing ClockworkMod or TWRP Recovery
Adding SuperSU (Rooting your ROM)
Unlocking your Bootloader
Minor Warning: Please note that if you had any special mods that you had to manually flash before or move on the system partition (like Google Wallet, AOSP 4.2 apps like camera and gallery, etc...) they will be lost as you are overwriting your system partition to factory stock. Please make sure to do the needful with your mods before following this guide (for example resetting the Google Wallet app).
Frequently Asked Questions
I have just received the Jelly Bean OTA and all I'm looking to do is root it. What do I do?
I have created a new thread for such a method. Please refer here: Link
Does this method trip the flash counter?
Yes and no. The only time your flash counter gets tripped is when you flash a custom kernel or recovery. Since the factory image in Step 1 contains the original kernel and recovery partitions, your flash counter should not be tripped. However, after flashing the custom recovery in Step 2, that will indeed increase the counter (no way to escape that since you are flashing a custom recovery).
Solution? Download the TriangleAway app from this thread or from the Play Store after you have completed Step 3 and reset the counter. That easy!
I get an "MD5 hash value is invalid" error when I load the ODIN file. What do I do?
This usually happens whenever your downloaded file is corrupt and has not transferred properly to your computer and your best bet is to try to redownload the file and try once again.
However, there are certain cases where you download the file multiple times and still get the error. In that case there is a small workaround. Firstly, you should see an MD5 that I have posted for each ODIN file in the downloads below. Download this MD5 Checker application to your computer and verify that the MD5 value I have listed for the accompanying download matches the file you have download. If it does not, redownload the file again until you get a match (not safe to flash it in ODIN until you do). However, if the MD5 does match and you still get the same error, all you have to do is rename the file and remove ".md5" from the end of the filename and it will flash. But take note, ONLY do that if the MD5 matches the one I have listed. Otherwise you are running the risk of flashing a corrupt image in ODIN and you can hard brick your device in some cases.
Do I need to flash kernel, radio, or RPM separately?
Not necessary at all. What makes my guide different from your everyday ROM is that these are complete factory images. What that means is that the image file contains every single updated partition for that build that you would need to bring your entire device to the latest build. Normally most ROMs that you flash in recovery only include System and sometimes Kernel partitions.
However, these ODIN images includes every single partition that exists on your device (kernel, radio, RPM, system, aboot, and over 15+ other hidden partitions you normally don't see or have access to). So upon flashing these images you do not have to flash any other partition as these will all automatically be upgraded after completing all three steps in my guide.
I'm coming from a completely stock device. Will this guide work for me too?
Absolutely! This guide was exactly intended with stock devices in mind. Flash with no worries and at the end of all three steps you will be on the latest Jelly Bean build, rooted, and with an unlocked bootloader.
I can't find Blocking Mode that was added to Jelly Bean on every other Galaxy S III. Where is it?
For some unknown reason Verizon decided to leave us out in the cold with Blocking Mode just as they didn't have the All-Share Cast option in ICS. They have done the same thing with the Galaxy Note II and recently a small workaround has been found to activate this feature. Please check this thread for details.
After flashing this image I no longer see the lockscreen notification bubbles for missed calls and text messages that I had in ICS. Where did they go?
For one reason or another Samsung and Verizon intended to remove the lockscreen missed notifications with the Jelly Bean upgrade so what you are seeing is normal. There is a small workaround to get them back but then you will have a small bug if you do that. For the workaround, if you use Root Explorer to look in "/system/csc" you should see a file named "customer.xml". Rename it to "customer.xml.bak" and this is brings back the lockscreen notification bubbles. However, upon doing that you will notice that this message will now never go away. The helper text for that specific notification will never go away because that notification is not supposed to exist in Jelly Bean so it doesn't know how to clear it properly after you've completed the action. The only thing you can do is by the disabling the "Help" app in your Application manager ("All" tab), which will stop showing all helper text. The workaround is reversible so the choice is up to you.
If I have <your build or ROM version here>, can I flash this image to get back to stock?
Absolutely. That is exactly what these factory images are intended for. They will reset your device to a complete build as official from Samsung and Verizon. Go right ahead.
Click to expand...
Click to collapse
Main Downloads
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
SuperSU (Root) - Link
Verizon Galaxy S III Unlocked Bootloader - Links (1, 2)
SuperSU + Unlocked Bootloader - Link
Click to expand...
Click to collapse
VRBMB1 Image Downloads
Stock VRBMB1 Factory Image with No Data Wipe - Link
MD5: b4507fd5bfdf59dbeedf51ff1a6afc7c
VRBLK3 Bootchain with ClockworkMod Touch Recovery 6.0.3.1 - Link
MD5: 99f65a8ce3f93fa46ddad2e02fc0e9f9
VRBLK3 Bootchain with TWRP Recovery 2.5.0.0 - Link
MD5: 7245c10c1daa94b95d633f58547e77c1
Click to expand...
Click to collapse
Step-by-Step Procedure
Step 1 - Flashing the Factory Image
Download and Install USB drivers (Main Download #1)
Download and extract ODIN v3.07 (Main Download #2)
Download the Stock Factory Image with No Data Wipe (Image Download #1)
Boot phone into ODIN mode (See here for how-to)
Flash the flash the factory image using ODIN v3.07 (See here for guide on flashing)
After reboot you should now be on Jelly Bean with all your apps, data, and storage contents in tact
Step 2 - Installing a Custom Recovery
If you would like ClockworkMod Touch Recovery (Image Download #2)
If you would like TWRP Recovery (Image Download #3)
Boot phone into ODIN mode (See here for how-to)
Flash the flash the recovery image using ODIN v3.07 (See here for guide on flashing)
After reboot you should now be able to boot into you recovery of choice using the button combos (See here for how-to)
Along with that the original bootchain for the factory image will be restored as well
Step 3 - Rooting Your ROM and Unlocking Your Bootloader
If you would like Root Only (Main Download #3 to your SD Card)
If you would like Unlocked Bootloader Only (Main Download #4 to your SD Card)
If you would like Both Root and Unlocked Bootloader Main (Download #5 to your SD Card) ***RECOMMENDED***
Boot phone into Recovery mode (See here for how-to)
Flash the download you chose from above using your custom recovery
After reboot your ROM will now be fully rooted and your bootloader fully unlocked to allowing additional flashing of custom kernels/recoveries
Click to expand...
Click to collapse
Credits
Credit goes to "source requested to remain anonymous" for providing the original VRBMB1 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBMA2 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBLK3 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBLK1 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBLJ1 leak (via PM)
Credit goes to scrosler for providing the extracted VRBLI5 tarball (Original Link)
Credit goes to jucytec for providing the original VRBLI5 leak (Original Post)
Credit goes to cnlson for providing ftp filehosting (via PM)
Credit goes to scrosler for providing ftp filehosting (via PM)
Credit goes to AdamOutler and African-Canadian Sock Monkey for providing the Verizon Galaxy S III Unlocked Bootloader (Original Post)
Credit goes to invisiblek for providing the VRALEC Bootchain allowing custom recovery flashing (Original Link)
Credit goes to Chainfire for creating SuperSU (Original Post)
Credit goes to Koush for creating ClockworkMod Recovery (Original Link)
Credit goes to Dees_Troy for creating TWRP Recovery (Original Post)
Credit goes to alexcolodner for merging SuperSU/Unlocked Bootloader into one file and providing filehosting (via PM)
First, thanks!
Sent from my SCH-I535 using xda app-developers app
Very nice, will have to give this a try.
I guess going back to the HE ROM would still work if you do a CWM Backup first?
One reason why I was reluctant to try I5 was having to reinstall all my apps and settings.
Does this also include the I5 radio baseband, or does that still have to be flashed separate? Some have reported the HE baseband is working better than the I5 one. Either way, it's easy to flash those zip.
Thank You
Just flashed it, and missing is any Camera or Gallery app, either the Samsung one or the (new) Android 4.2 one.
FAUguy said:
Just flashed it, and missing is any Camera or Gallery app, either the Samsung one or the (new) Android 4.2 one.
Click to expand...
Click to collapse
Please note that mods you have applied to the system partition will have to be reinstalled after flashing the image. Since Camera and Galley are both mods that affect the system partition and you manually flashed onto it, you will lose them normally. Wallet is another example as well so make sure to reset your Wallet app before flashing this image. But you should still see the original Camera and Gallery apps show up that are part of the stock firmware. Please double check that they are not hidden in your launcher or disabled (see the bottom of your Application Manager for disabled apps) from a previous mods perhaps you disabled them before flashing the 4.2 apps. I can personally confirm after multiple testing that Camera and Gallery are both included in this firmware.
I know this is going to be a stupid question... but is the stock (untouched) image not able to be rooted/unlocked? Only reason I ask is because I like having a factory image to flash that does wipe data so it acts as a "start fresh" approach. Thanks for this guide and the joined root/unlock. That's good stuff.
indyssee said:
I know this is going to be a stupid question... but is the stock (untouched) image not able to be rooted/unlocked? Only reason I ask is because I like having a factory image to flash that does wipe data so it acts as a "start fresh" approach. Thanks for this guide and the joined root/unlock. That's good stuff.
Click to expand...
Click to collapse
If you'd like to do a data wipe all you have to do after the image flashes is go into Settings > Back up and reset > Factory data reset. This does the same exact process. I highly don't recommend using the Original Untouched image or it is a much more complicated process to restore root and custom recovery after that. Hence this is why I created this modified image and this guide. The only reason I am linking to that image is for reference purposes only to any developers who want to explore and compare.
Thank you have been waiting for this.
Sent from my SCH-I535 using xda premium
Excellent write up. Thank you very much for your contribution.
open1your1eyes0 said:
Please note that mods you have applied to the system partition will have to be reinstalled after flashing the image. Since Camera and Galley are both mods that affect the system partition and you manually flashed onto it, you will lose them normally. Wallet is another example as well so make sure to reset your Wallet app before flashing this image. But you should still see the original Camera and Gallery apps show up that are part of the stock firmware. Please double check that they are not hidden in your launcher or disabled (see the bottom of your Application Manager for disabled apps) from a previous mods perhaps you disabled them before flashing the 4.2 apps. I can personally confirm after multiple testing that Camera and Gallery are both included in this firmware.
Click to expand...
Click to collapse
When using the HE ROM, I only had the included Samsung Camera and Gallery app, I did not install the separate Android 4.2 app. So when I used ODIN to flash this I5 ROM, I noticed that the Camera and Gallery are not listed in the app drawer. I went into Settings/Applications, and they are still listed, but doesn't have an option to open them. Also went into Titanium Backup, to restore them from a backup of apps I did a few weeks ago. Even after restoring them, they still were not listed and could not be opened. I'm not sure why these two apps were having a problem, but after trying it for a day, I used CWM and restored my HE backup. Now the camera and gallery apps work again, as they should, but now I get a Visual Voicemail error each time the phone turns on. So I had to force stop that app from loading.
FAUguy said:
When using the HE ROM, I only had the included Samsung Camera and Gallery app, I did not install the separate Android 4.2 app. So when I used ODIN to flash this I5 ROM, I noticed that the Camera and Gallery are not listed in the app drawer. I went into Settings/Applications, and they are still listed, but doesn't have an option to open them. Also went into Titanium Backup, to restore them from a backup of apps I did a few weeks ago. Even after restoring them, they still were not listed and could not be opened. I'm not sure why these two apps were having a problem, but after trying it for a day, I used CWM and restored my HE backup. Now the camera and gallery apps work again, as they should, but now I get a Visual Voicemail error each time the phone turns on. So I had to force stop that app from loading.
Click to expand...
Click to collapse
Darn, it seems like your all mixed up over there now. My recommendation ONLY in your case is start fresh using the below process:
Backup your internal SD Card contents to your computer
Save your HE backup in safe place on the computer as well
Flash the Original Untouched Data Wipe image ***REMEMBER THIS WILL WIPE EVERYTHING***
Ensure that everything is working fine upon reboot, setup your phone and make sure all apps are working (Camera, Gallery, etc...)
After that follow my guide from the start to the finish (flashing the No Data Wipe image first!)
Confirm you are rooted, unlocked bootloader, have custom recovery and everything is working
Use "Advanced Restore" in to restore only your "data" partition from your HE backup
If everything is good you can now restore your internal SD Card contents back to your device. Let me know what happens in each step.
I see some of my dropbox links are starting to be suspended due to the heavy traffic. I'd like ask if anyone would like to make some mirrors (especially the No Data Wipe image) please kindly PM me and I will add them to the OP.
open1your1eyes0 said:
Darn, it seems like your all mixed up over there now. My recommendation ONLY in your case is start fresh using the below process:
Backup your internal SD Card contents to your computer
Save your HE backup in safe place on the computer as well
Flash the Original Untouched Data Wipe image ***REMEMBER THIS WILL WIPE EVERYTHING***
Ensure that everything is working fine upon reboot, setup your phone and make sure all apps are working (Camera, Gallery, etc...)
After that follow my guide from the start to the finish (flashing the No Data Wipe image first!)
Confirm you are rooted, unlocked bootloader, have custom recovery and everything is working
Use "Advanced Restore" in to restore only your "data" partition from your HE backup
If everything is good you can now restore your internal SD Card contents back to your device. Let me know what happens in each step.
Click to expand...
Click to collapse
I ended up using CWM and restoring one of the first HE backups that I did a few weeks ago, then tried the I5 (no wipe) install method again.
This time around, it did work, and the Samsung Camera and Gallery apps are there and working, as are all my apps.
The only thing I had to do extra was install the TW JB Google Wallet and 4.2 Keyboard after.
FAUguy said:
I ended up using CWM and restoring one of the first HE backups that I did a few weeks ago, then tried the I5 (no wipe) install method again.
This time around, it did work, and the Samsung Camera and Gallery apps are there and working, as are all my apps.
The only thing I had to do extra was install the TW JB Google Wallet and 4.2 Keyboard after.
Click to expand...
Click to collapse
Excellent! Glad to hear you're up and running. :good: I had a feeling it was something in your latest data partition that was messing with it.
open1your1eyes0 said:
Excellent! Glad to hear you're up and running. :good: I had a feeling it was something in your latest data partition that was messing with it.
Click to expand...
Click to collapse
The only difference between the two HE backups is that there is a few weeks between them, which some app updates were installed through Google Play, the Google Wallet hack, and the Android 4.2 keyboard. So something in there had to cause the Samsung Camera/Gallery app not to work with the I5 (no wipe) ROM. But going to the older HE backup (which is before all those apps were updated) and without Wallet and Keyboard 4.2, then installing I5, the camera/gallery works.
By the way, I remember seeing last week a post (somewhere in here) that was just the I5 Kernel zip.
I did a search, but can't find it.
I want to try the KT747 Kernel, but would like the I5 Kernel to have as a flash backup.
Found the link, but looks like your DropBox is getting slammed
http://forum.xda-developers.com/showthread.php?p=33625822&highlight=kernel#post33625822
FAUguy said:
The only difference between the two HE backups is that there is a few weeks between them, which some app updates were installed through Google Play, the Google Wallet hack, and the Android 4.2 keyboard. So something in there had to cause the Samsung Camera/Gallery app not to work with the I5 (no wipe) ROM. But going to the older HE backup (which is before all those apps were updated) and without Wallet and Keyboard 4.2, then installing I5, the camera/gallery works.
By the way, I remember seeing last week a post (somewhere in here) that was just the I5 Kernel zip.
I did a search, but can't find it.
I want to try the KT747 Kernel, but would like the I5 Kernel to have as a flash backup.
Found the link, but looks like your DropBox is getting slammed
http://forum.xda-developers.com/showthread.php?p=33625822&highlight=kernel#post33625822
Click to expand...
Click to collapse
Attached it for you. Extract the tarball from the zip and flash in ODIN.
open1your1eyes0 said:
Attached it for you. Extract the tarball from the zip and flash in ODIN.
Click to expand...
Click to collapse
Thanks.
I've also been reading about an RPM file in some other threads, but Inc's link is dead. Is that something that should be installed?
FAUguy said:
Thanks.
I've also been reading about an RPM file in some other threads, but Inc's link is dead. Is that something that should be installed?
Click to expand...
Click to collapse
It's included in the image since it's the complete factory package.
EDIT: However also attaching the tarball zip in case you want to mess around with it. Flash in ODIN as well.
By the way, I haven't seen anyone mention it yet but this image finally unlocks the promised "Global Roaming" capabilities that Verizon promised via OTA. You can now use AT&T/T-Mobile/Other GSM carrier microSIM cards and run on their network. AKA: phone is now technically unlocked.
I am usingSamsung Galaxy Y pro Duos. GT 5512.
To install Whatsapp+ I had to uninstall whatsapp. I am not able to install Whatsapp+ (and Yes I am installing GB variant of Whatsapp+). It shows "Application not installed".
Now when I have installed original Whatsapp. I am asked to restore from the backup. When I tap on restore, it Crashes at 84% and shows a error. I don't want to lose the backup.
PS1: I have managed to solve the crashing problem' see the solution in the posts down.
PS2: I am still unable to get Whatsapp+ installed. It says "Application not Installed. Can anybody help in this regard?
It's advised to restore to the same backed-up version of Whatsapp
shikhar623 said:
I am usingSamsung Galaxy Y pro Duos. GT 5512.
I had to uninstall whatsapp. Now when I have installed it, I am asked to restore from the backup. When I tap on restore, it stops at 84% and shows a error. I don't want to lose the backup.
Click to expand...
Click to collapse
Try to uninstall Whatsapp & install once again, or if you prefer to check older versions: http://whatsapp-messenger.en.uptodown.com/android/old
It it doesn't help- leave only the latest backup file + 'msgstire.db.crypt' in the 'Database' folder of whatsapp. Other option is to check if you got
several whatsapp folders stored in device's external/internal storage, and leaving the newest one
shikhar623 said:
I am usingSamsung Galaxy Y pro Duos. GT 5512.
I had to uninstall whatsapp. Now when I have installed it, I am asked to restore from the backup. When I tap on restore, it stops at 84% and shows a error. I don't want to lose the backup.
Click to expand...
Click to collapse
sasan_blue said:
It's advised to restore to the same backed-up version of Whatsapp
Click to expand...
Click to collapse
Hi,
This issue is interesting and I have been looking for options, so you can solve your problem. If the problem is the version, as sasan_blue says, you can go to the Aptoide web, and search the old versions of whatsapp there. I was able of download different versions of whatsapp on my PC from that web.
I can't paste urls...
EDITED: Sorry, I was writing this thread while amirTor gives his answer. The English is not my language mother and take long to write. I think is best the amirTor solution.
Saludos
Thanks Guys. I got it solved by completely uninstalling whatsapp using Titanium backup app, and installing it again. It was a problem of incomplete uninstallation. (I had rebooted the device before the uninstall process finished). The problem persisted because I have been uninstalling using regular method. Also it was not a problem of a corrupted backup in my case( as I had thought).
PS. I had installed an older version too. It asked me to check my date settings. it didn't peroceed any further. I guess it was becoz of the outdated version.
HI, i have installed and rstored whatsapp a million times or so, when flashing and switching between roms. last night i tried something funny, and it cost me tooo much.
I tried to install whatsapp for another number(my phone is dual sim), while sms verification was happening, it got registered via my previously registered whatsapp no. Now even after i deleted the new no. account,i am still not able to get my old account back. when i give my old number, it doesn ask for sms verification, and goes to local backup directly, but fails there and throws error. on the other hand, i can verify the account, but cannot restore all my messages.
Please help, as my msgs are quite important..!
il hit the thanks button..!
srinikethan1392 said:
HI, i have installed and rstored whatsapp a million times or so, when flashing and switching between roms. last night i tried something funny, and it cost me tooo much.
I tried to install whatsapp for another number(my phone is dual sim), while sms verification was happening, it got registered via my previously registered whatsapp no. Now even after i deleted the new no. account,i am still not able to get my old account back. when i give my old number, it doesn ask for sms verification, and goes to local backup directly, but fails there and throws error. on the other hand, i can verify the account, but cannot restore all my messages.
Please help, as my msgs are quite important..!
il hit the thanks button..!
Click to expand...
Click to collapse
You can solve this problem by registering your new number again and restoring your old number's chats.
Once you are able to restore your old number's chat by registering on the new number. You can now change the number officially by using the 'change number' feature in the WA settings.
See if this trick works for you.
Good luck.
shikhar623 said:
You can solve this problem by registering your new number again and restoring your old number's chats.
Once you are able to restore your old number's chat by registering on the new number. You can now change the number officially by using the 'change number' feature in the WA settings.
See if this trick works for you.
Good luck.
Click to expand...
Click to collapse
Hey thanks for the response,
Things arent way the its supposed to...even if im trying to sign up using another account, still the verification is not being done and whern restoring is trying to happen, it force closes or shows a message that it cannot restore msgs in the server
if u know any solution please let me know, its pretty annoying without whatsapp for a week and i need those old messages..its pretty important.
I have done flashing roms a 100 times and never faced this issues, and now it aint going at all..
Ok. copy the backup database some where safe.
Delete your new number account ( from within the WA account settings)
Remove the WA using titanium backup. (you need to be rooted for TB to work)
Reinstall the WA.
See if you are able to register your new number.
Use WhatsApp recovery app to restore you account information, the tool is available free of cost.
If no chats are being restored while reinstalling Whatsapp and you want to restore from a local backup... Try to uninstall and reinstall Whatapp and simply take a local backup of the empty chats and copy the entire filename (Ex: msgstore.db.crypt12) and delete this backup file.. Now paste the backup file from where you want to restore the chats in the Whatsapp databases folder and rename it with the name that was copied from latest backup file (msgstore.db.crypt12).
Clear WhatsApp data (from Settings -> Apps-> WhatsApp-> Clear Data). When you launch Whatsapp now, it will prompt again for the verification details etc. Skip the google drive step and Whatsapp will restore all your chats from your desired local backup. But please make sure you have lot of free space on your device. I cleared about 3gb of data from device memory in order to get this working.
It worked for me when I finally was about to give up after trying for 3 days..
shikhar623 said:
I am usingSamsung Galaxy Y pro Duos. GT 5512.
To install Whatsapp+ I had to uninstall whatsapp. I am not able to install Whatsapp+ (and Yes I am installing GB variant of Whatsapp+). It shows "Application not installed".
Now when I have installed original Whatsapp. I am asked to restore from the backup. When I tap on restore, it Crashes at 84% and shows a error. I don't want to lose the backup.
PS1: I have managed to solve the crashing problem' see the solution in the posts down.
PS2: I am still unable to get Whatsapp+ installed. It says "Application not Installed. Can anybody help in this regard?
Click to expand...
Click to collapse
Hello, i'm having exactly the same problem in the same place (84%), I have not rooted my phone what makes impossible the solution with titanium. Any Ideas?
The backup folder has a lot of directories, should i delete some of them?
app_download_internal
app_minidumps
app_textures
app_webview
cache
code_cache
databases
files
lib
no_backup
shaders
shared_prefs
is there any log to check the error messages?
thank you.
Nelson
PS1. Erasing some directories, now i can get the 97%
unable to restore whatsapp messages
i switched to a new phone. I copied whatsapp folders- Databasse and media to the laptop. The database file has correct name as suggested by whatsapp faq- msgstore.db.crypt and it is version 12 only. But when i install whatsapp it does not take that local backup and asks to check google drive. I don't have backu on google drive. Later i tried new idea- I disconnected internet after verifification of mobile number and yes so it prompted - >backup found- Restore> i tapped restore, but still my chats didn't backedup, the restore processing also did not took lace, i turned on internet after tapping restore. what's the matter? please help. I have some really important stuff. You all are tech enthusiast here. i hope you can help me in this minor problem. I have local Backup, i have mobile, i have aplication. What else is needed??
---------- Post added at 05:35 PM ---------- Previous post was at 05:30 PM ----------
Sweetz123 said:
If no chats are being restored while reinstalling Whatsapp and you want to restore from a local backup... Try to uninstall and reinstall Whatapp and simply take a local backup of the empty chats and copy the entire filename (Ex: msgstore.db.crypt12) and delete this backup file.. Now paste the backup file from where you want to restore the chats in the Whatsapp databases folder and rename it with the name that was copied from latest backup file (msgstore.db.crypt12).
Clear WhatsApp data (from Settings -> Apps-> WhatsApp-> Clear Data). When you launch Whatsapp now, it will prompt again for the verification details etc. Skip the google drive step and Whatsapp will restore all your chats from your desired local backup. But please make sure you have lot of free space on your device. I cleared about 3gb of data from device memory in order to get this working.
It worked for me when I finally was about to give up after trying for 3 days..
Click to expand...
Click to collapse
hi! can you please help me. I am unable to restore chats. when i ta skip for google drive ption it directly takes me to enter name screen and then empty chats apear(only groups in which i am added). it does not restore from local backup. Only once when i turned off internet, it tried to restore as it found 1.6 GB local backup but soon it cancelled the procedure as i turned on internet during the restoring(whatsapp told to turn on internet) and later it came on screen that 0 message restored also google drive option returns after turning on internet. please help. how you did it?
What’s this about?
WhatsApp was driving me nuts the other day! Why? Because it would not restore my message backup without a reason.
When I take the time and read the following will it help me?
Well, maybe. That depends on what you did. I wanted to restore my WhatsApp encrypted backup file (FILE! not Google backup) and it worked out.
When will the following maybe help me?
you have a WhatsApp backup file (encrypted, e.g. crypt12 -> msgstore.db.crypt12)
you wiped your phone’s data
you have a backup of your phone (TWRP or similar) or already have the WhatsApp key
What happened to you?
I changed from stock ROM to custom ROM (CyanogeMod in my case). Because I did a clean flash I made some preparations in advance. I backed up my WhatsApp messages and copied the whole folder to my SD card. I wiped my phone using TWRP (system, data, cache...). After the custom ROM flash I installed WhatsApp and wanted to restore my messages. Didn’t worked out.
What happened?
I did a little bit of research and little did I know the message file was encrypted. Because WhatsApp is super smart it stores the key for the decryption not in the WhatsApp folder (okay, this would really be stupid). As soon as you wipe your data the key will be erased. Good bye key! So, I am not an expert and it could be that there is a way easier method to restore you messages but I didn’t found one. I just want to share my experience so hopefully someone can save a lot of time. I would have been happy if I found something like this earlier or if I would have at least known about the key. Now I know.
NOTE
Without a backup of your phone, to be more specific, of your phone’s data or the WhatsApp key the following will be useless!
NOTE
Your phone can get broken! I am not responsible for that. Everything you do is on your own risk! Also, I’ll try to help but I am not a 24/7 support technician.
NOTE
Read everything first before you start! Maybe I messed something up. So, take a look first!
So, what to do?
1) Retrieve the key from your phone’s data backup.
a) Because we are all smart we do a full backup before we flash crazy stuff on our phone, right?! I did that with TWRP. Any other backup might work as well. You’ll have to find out on your own. The TWRP backup file is something like “data.ext3.win000”, “data.ext3.win001”. Copy it to your computer. Add the extension .tar or .tar.gz (“data.ext3.win000.tar”, “data.ext3.win001.tar”). In my case both worked. If you can already browse your backup file continue with e).
b) Download and Install 7-Zip.
c) With the 7-Zip file manager you can open and search inside the renamed TWRP files.
d) 7-Zip doesn’t recognize if your data is stored in more than one file. I guess if you pick the right file extensions it would. But, like I said, I am not an expert. So, in this case the win000-file has other files in it than the win001-file. If you don’t find the key in the first one, open up the next one.
e) Open the first file. There will be some kind of blank folder. Open it and you’ll see your phones data. Navigate to \data\data\com.whatsapp\files\.
f) There you should see a file named key. If so, start yell “hurray!”. In my case I saw two key files. I don’t know why but every file was doubled (maybe someone can explain that to me).
g) One of the files was about 158 Bytes. That should be it. To be sure extract the first key file. Open it with the windows editor. If there are letters in it that you can read it’s the wrong file.
h) Extract the other one and open it, too. You see some gibberish? Congratulations, this should be your key! Copy the file to your phones SD card or something similar.
2) Restore your backup
a) Install WhatsApp if not already happened. If you already activated the app go to settings, apps, select WhatsApp and erase all data (NOTE! Your own risk! All data will be gone!). This is necessary because WhatsApp will only ask once after the activation if the backup should be restored. Maybe there is another way but I don’t know it.
b) Copy the whole WhatsApp folder to your phone (the backed up one from the SD, see above). Or just put the backup file into \WhatsApp\Databases\. If you have an older backup file like msgstore.db-2016-01-01.crypt12 rename it into msgstore.db.crypt12. As far as I know only the last named file will be restored.
c) Start WhatsApp and activate it.
d) STOP! WhatsApp will ask you if it should restore the backup. Don’t do it! If you did it and it failed start again from a). Just leave the screen like that, don’t do anything. Turn off your phone! Yep, you heard right. WhatsApp will remember the state it’s in.
e) Boot into TWRP. If you have a file manager that can access your phones data you could use that one, too. I think root will be required for that. I just had the limited stock file manager. The latest TWRP has a file manager integrated without restrictions (check for yourself first!). I used that one (complicated maybe, I know!).
f) Open the file manager (Advanced - File Manager) and navigate to your key-file. Tap on it and select copy.
g) Navigate to \data\data\com.whatsapp\files and copy the key-file into this folder (just tap the blue folder at the right bottom of the screen).
h) Reboot you phone. Start WhatsApp. It should open up and directly ask you if you want to restore your backup. Try to restore it. If you’re lucky it’ll work. For me it did! Congratulations.
Endnote
I didn’t know about the key when I erased my phone’s data. Next time that one will be backed up, too. So I can save a lot of time.
This whole thing here might be very complicated and I guess there is a lot better way to do it. But I didn’t found it. So, I just want to at least share my experience. Maybe someone will profit.
Another thing you need to know here;
The file named key should have a UID WhatsApp for user and group permissions.
You can set these using TotalCommander via Properties
and you should set these while whatsapp is killed/down and while the key is already in the /data/data/../files/ dir.
I also had a case where in the last stage, so before the final boot to restore the database, I had to do a Wipe Cache and Dalvik cache. If I did not do that, whatsapp would skip the restore question and continue activation as if it was a new one, and then *overwrite* the key file I had put there, no matter what I tried!
You don't have to do any of this if you haven't changed your cell number!
1) Copy your latest crypt 12 file to /sdcard/WhatsApp/Databases/
2) Install / Activate WhatsApp
3) WhatsApp will retrieve the key from their server and restore your backup.
This only works if you haven't changed numbers, but it's easy as 1, 2, 3!
I tried this but it didn't work out for me. Thats the reason I wrote this. So far couldn't find another way to restore the backup. Maybe in newer WhatsApp versions this works?!
TripCode said:
You don't have to do any of this if you haven't changed your cell number!
1) Copy your latest crypt 12 file to /sdcard/WhatsApp/Databases/
2) Install / Activate WhatsApp
3) WhatsApp will retrieve the key from their server and restore your backup.
This only works if you haven't changed numbers, but it's easy as 1, 2, 3!
Click to expand...
Click to collapse
That's actually not true. I followed their instructions to the letter, but they failed. I did not get a Restore prompt, and it actually erased the entire whatsapp cryptxx file.
The official way probably fails when you upgrade from LL to MM, but I'm not so sure about even that, because it also failed a long time ago on my htc desire just changing from rom to rom (with a clean /data/data dir).
jult said:
That's actually not true. I followed their instructions to the letter, but they failed. I did not get a Restore prompt, and it actually erased the entire whatsapp cryptxx file.
The official way probably fails when you upgrade from LL to MM, but I'm not so sure about even that, because it also failed a long time ago on my htc desire just changing from rom to rom (with a clean /data/data dir).
Click to expand...
Click to collapse
Sounds like you have had a bad experience. I do a lot of dev work with WhatsApp. I have swapped between several devices as low as API7 to API24. I have never had an issue restoring WhatsApp via the official 3 step method. My devices use a selection of stock / custom roms. As long as you got it working that's the main thing, but I would advise people to try the official restoration procedure before they venture into anything more technical as the official procedure will work most of the time.
Hi, I googled and came to this page.
I hope someone can help in restoring either local .crypt12 backup file or from google drive backup.
It started when my phone got no space and WhatsApp crashed.
For the first time, I clicked restore but it couldn't restore as got no space and WhatsApp closed the app itself.
I was carelessly when starting WhatsApp again and didn't click "restore from previous database" on the 2nd time.
I searched online for the WhatsApp help and deleted some apps to free up space.
Then, I uninstalled WhatsApp and reinstalled again. However, the problem came when after re-installation and needed to authenticate my old WhatsApp number by SMS.
As I just kept using the old WhatsApp number that was originally from a prepaid SIM card which I bought years ago and I didn't top up the stored value for a few years back, so I couldn't receive voice and SMS from that old WhatsApp number as it was properly become a dormant mobile number .
Is that a way I can restore from, for I made a copy of the crypt12 database before uninstalling WhatsApp (I didn't copy the key before uninstalling & reinstalling, and I am not sure if I had a copy of the key before, that I tried to backup using windows explorer to copy to my computer long ago.
Many thanks.
TripCode said:
Sounds like you have had a bad experience. I do a lot of dev work with WhatsApp. I have swapped between several devices as low as API7 to API24. I have never had an issue restoring WhatsApp via the official 3 step method. My devices use a selection of stock / custom roms. As long as you got it working that's the main thing, but I would advise people to try the official restoration procedure before they venture into anything more technical as the official procedure will work most of the time.
Click to expand...
Click to collapse
hi i used yowhatsapp and try to use the original whatsapp app i get messages back but cant see old pictures and cant here old voice messages they were imported somehow to the new package named com.yowhatsapp istead.
could someone point me in the right direction on how i can restore whatsapp with mediafiles`? my mediafiles are all there but just working with yowhatsapp
lycca said:
Hi, I googled and came to this page.
I hope someone can help in restoring either local .crypt12 backup file or from google drive backup.
It started when my phone got no space and WhatsApp crashed.
For the first time, I clicked restore but it couldn't restore as got no space and WhatsApp closed the app itself.
I was carelessly when starting WhatsApp again and didn't click "restore from previous database" on the 2nd time.
I searched online for the WhatsApp help and deleted some apps to free up space.
Then, I uninstalled WhatsApp and reinstalled again. However, the problem came when after re-installation and needed to authenticate my old WhatsApp number by SMS.
As I just kept using the old WhatsApp number that was originally from a prepaid SIM card which I bought years ago and I didn't top up the stored value for a few years back, so I couldn't receive voice and SMS from that old WhatsApp number as it was properly become a dormant mobile number .
Is that a way I can restore from, for I made a copy of the crypt12 database before uninstalling WhatsApp (I didn't copy the key before uninstalling & reinstalling, and I am not sure if I had a copy of the key before, that I tried to backup using windows explorer to copy to my computer long ago.
Many thanks.
Click to expand...
Click to collapse
Did this yesterday but this will only work if your number has not changed, first uninstall whatsapp, if you have a copy of your latest. msgstore.db .crypt12 file, (found on your Whatsapp folder in your SD card under Databases) copy it from there to your internal memory Whatsapp Database folder. Please note that any existing msgstore.db .crypt12 file must first be deleted. Go to your SD card whatsapp folder named backup and copy the backup crypt file as well to the internal memory whatsapp folder only after deleting the existing folder. Install whatsapp and authenticate the install , do not accept the backup prompt. Once installed go to Chats and run a backup to google drive. Your key is in the DB files and will be uploaded to google drive along with all backuped data. Uninstall Whatsapp and reinstall, this time accept the backup prompt. Verify that the two files that you copied still exist in both the SD and internal memory, allow a normal backup to occur at 4am and check in the morning. All files should be recovered and the old key should be reinstalled.
Thank you very much for your guide. I upgraded a phone to a custom rom and even though I made a recent in-app backup and never used another phone number/sim card, Whatsapp was not able to restore the data.
Glad I made a complete NAND backup just to be safe....
@sexler (what a name )
THX a lot for your guide!
I changed from Android 7 (LineageOS) to Android 8.1 (CarbonRom) without using Google-Apps anymore. So no Backup from the cloud would be possible.
Only the "c) Start WhatsApp and activate it." was not possible with my Whatsapp. But I just did the activation later and after that he noticed that there where a backup.
Your guide helped out of my 7 days quest
THX THX THX!
Greetings by Idijt
@I_did_it_just_tmrrow
You're welcome!
It’s very nice to know that almost three years later the instructions can help someone. Thank you for your feedback.
Have a nice weekend.
Is the method still working?
timenewroman said:
Is the method still working?
Click to expand...
Click to collapse
Why not, the crypt is the same and there are some tools on versioning sites like github/gitlab who offer de-crypter.
Should work. Give it a try and tell us.
I'm trying to use this method to restore old 2015-16 WhatsApp chats to a BlueStacks virtual Android machine. I haven't had much luck.
NB though I did copy over both the key file and the msgstore.db to the com.whatsapp folder (as well as having the crypt12 file available)- I'm gonna try now while just copying over the key, once Whatsapp decides I'm not a robot and sends me verification again
EDIT: tried again, with msgstore.db.crypt12 and key only. Followed the procedure closely, and used BSTweaker to copy over the key file at the appropriate stage into BlueStacks. No luck. Failed to restore. I noticed that the permissions on the key file are different (RW for Owner, Group and Others).
Can anyone help me figure this out? Do I need to change the permissions or something? Any help would be appreciated!
EDIT2: SOLVED!!!!! Praise God! I managed to transfer my old conversations, profile pictures and media using this method: https://forum.xda-developers.com/android/general/whatsapp-reencryption-crypt12-backup-t3779487
TL;DR - I copied over, from one Bluestacks Android VM (v0.8 - ancient, from 2015), to antother Bluestacks Android VM (v4.180.0.1005 - latest as of writing) the following files/folders:
/data/data/com.whatsapp/databases/msgstore.db << (unencrypted database - requires ROOT)
/data/data/com.whatsapp/files/Avatars/[a couple of files that were obviously un-named jpg profile pictures] << (profile pics - requires ROOT)
/storage/emulated/0/Whatsapp/ << (Whatsapp media folder)
I didn't need my encryption key or crypt12 database at all; all the methods I'd tried to restore using these failed miserably (including the one in the Original Post here). Whatsapp "detected a problem" on reloading the app, and restored my old conversations from years ago - so happy!
i wanna share my experience when Whatsapp refused to restore using .crypt12 file. There's like 10 of the .crypt file in my phone, but all seems corrupted. So restoring using CRYPT12 file is out of question here.
all this happen when i'm trying to move my Whatsapp from old OP3T to new OP5. I thought it wont take more that 1 hour to complete. I was wayyyyyy wrong.
Please note that I'm using custom ROM based on Android 10 (Q).
I already have some Titanium Backup of my Whatsapp. So what I do is extract msgstore.db from the Titanium Backup .tar file (data/data/com.whatsapp/databases). What important is the SELINUX permission/setting on that msgstore.db file. Use any file manager that allows SELINUX context changes, such as Root Explorer.
The key file from /data/data/com.whatsapp/files also important, because I have 2 of it (one from my old OP3T, the other from OP5). The key from OP3T can be used to restore msgstore.db on my OP5.
Its really painful lesson to me, as I can't use Whatsapp from May 1st until today (May 10). That's 10 freaking day without Whatsapp!!
I could just continue using Whatsapp fresh like new, but the old chat messages is really valuable to me.
To those who having any kind of issue, don't stop trying. Never quit! There's always solution, sooner or later.
This is also a useful link for understanding how whatsapp
files function
Hi, I am having the same problem as with restoring my Whatsapp history and wondered if any kind soul can help me to restore my Whatsapp history?
What I had done :
I had my S8 rooted. The whole phone was wipe when it was rooted. I hope this step is correct.
My encrypted backup (crypt12 and crypt14) was saved already before I rooted and I also need a backup of my phone (just not the application data because the Dr Fone software mentioned that my S8 needed to be rooted before I can backup my application data)
But I couldnt find the folders you mentioned here :
/data/data/com.whatsapp/databases/msgstore.db << (unencrypted database - requires ROOT)
/data/data/com.whatsapp/files/Avatars/[a couple of files that were obviously un-named jpg profile pictures] << (profile pics - requires ROOT)
/storage/emulated/0/Whatsapp/ << (Whatsapp media folder)
Can anyone guide me pls?
Hey guys need your help actually i mistakenly deleted a chat for that i thought I would delete my WhatsApp and reinstall it and use the backup of last night and restore it..
But it turned out while installing it asked for Google drive but i haved created any backup file on my Google drive and only had it on my internal storage but WhatsApp didn't got the local file and said no backup found after that all my chat was deleted.
It rewrite all my WhatsApp folder and now it is showing just one encrypt file and all other data and backup got deleted.
I also checked com.whatsapp file in Android > media > com.whatsApp but it is deleted from there as well.
Those msgs were really important any help would be appreciated.
Thank you
Hello guys, about this subject.
I've tried a few stuff but i can't restore it like in the pass.
My s10e, it's clean, no custom rom, only default. When i did (like in the past without knowing about the key stuff) was to copy manually all my media photos/stickers/etc., and the conversations, all those crypt files. So now i have 2 clean crypt file with my last conversations. I really want to recover all of it.
Please tell me there's a way without rooting , i've read and see so many videos but i can't find a good way to restore it.
I was thinking maybe using an old phone, put the crypt files on the sd card, change the chip, try to restore it with and old whatsapp version(?).
I really need my conversations back. It's really important. Any ideas?
Hello everyone,
today i switched from the german XEG MM Firmware to the latest BTU Nougat one, all with CSC change factory reset and re partition to get the CSC into effect. Had to factory reset anyways, since i always do it after some months, so why not update and test Nougat, while at it.
While everything except VoLTE/WifiCall (which are to be expected not working) works perfectly, i do however have a small problem with 1 App only, namely WhatsApp.
I've done a Cloud and Local Backup before the Update and neither are restoring on the Nougat OS, tested with older / same and even a newer beta from the APK itself.
The backup is recognized in size and according to the SQL extract should not be corrupted, haven't seen through every chat though (Cloud Backup size 660MB, chat file 22MB <- too big maybe?).
So my question is, does anyone have the same problem as i do? Is it a Nougat Filesystem / WhatsApp Database Key change due to the upgrade?
If you had the problem aswell, did you solve it without a downgrade or am i alone with it? The MM Key works on local backup, though i haven't yet pulled a "new" key to verify yet.
Tried:
Install various APK's, older/newer and same version
Factory Reset w/ clearing cache via recovery mode after flashing
Give the app permissions before launching
Remove Google Account to restore from local backup
Since i now have to wait 13h to verify with their servers again due to my personal troubleshoot, i figured i could ask here
I'm grateful for any tips, otherwise i might downgrade to MM again and hope the problem fixes itself, though i'd like to have the features of Nougat now and not in 2-3months, given previous release schedules of my carrier.
edit:
- I've just had an idea, while you use your phone number to verify. Mine does not display under the phone settings -> Device information -> Own Number. This might be due to the CSC change, but should not be relevant, since the actual process is done via messaging right?
Some additions to above text.