So I borrowed my friend's Gnex so I could send mine in for warranty. His phone is rooted, unlocked bootloader, and running 4.1.1 stock ROM. I backed up his file, and transferred my own backup img to his phone. When I tried to restore my img onto his phone, CWM tells me I have an MD5 mismatch.
I've never tried this before since I've only owned one Gnex, so I'm not even sure if this is possible (which I obviously thought it was). I've tried renaming the folder that the img is located in (as opposed to keeping it in the "backup date" format), and I'm not sure if this is what's causing an MD5 mismatch.
Any insight?
More info... what did you back up? What firmware was yours running etc? What is the .img of?
Sent from my Transformer Prime TF201 using xda premium
rice923 said:
and I'm not sure if this is what's causing an MD5 mismatch.
Any insight?
Click to expand...
Click to collapse
The file hash isn't matching, which means bits have changed since the MD5 was written into the image. That usually means that it transferred improperly, whether it was just generally corrupted during transfer or transferred improperly (say, ascii transfer mode in FTP). I'd try copying it from the original source again.
You can fix the md5 mismatch quite easily http://forum.xda-developers.com/showthread.php?t=714114
Cilraaz said:
The file hash isn't matching, which means bits have changed since the MD5 was written into the image. That usually means that it transferred improperly, whether it was just generally corrupted during transfer or transferred improperly (say, ascii transfer mode in FTP). I'd try copying it from the original source again.
Click to expand...
Click to collapse
Would me changing the folder name that the backup is located in cause the mismatch?
stinky73: I backed up my entire phone in cwm. My original phone was running 4.1.2, but the phone I'm trying to go to is 4.1.1. I don't believe that would make a difference since I'm flashing over the original anyways, or am I mistaken?
peachpuff: I will be reading that link for some brain food. Thanks for pulling it up!
In any case, I may just try to transfer the files again and give it another go.
rice923 said:
Would me changing the folder name that the backup is located in cause the mismatch?
Click to expand...
Click to collapse
Yes it very well may have caused your problem
3rdstring said:
Yes it very well may have caused your problem
Click to expand...
Click to collapse
I just used the original name for all the folders and files of my backup img, and it no longer states a mismatch MD5. However, it now says "Error while restoring /system!"
Starting to think I really gotta be on 4.1.2 in order for it to restore correctly. Any other thoughts?
Hey if you ever figure this out, let us know. I have tried to restore backups from one gnex to another with no luck. I have used CWM and TWRP. Tried leaving the files as is and also renaming them. I tried transferring them via computer as well as uploading them to dropbox and downloading from there. Someone told me a while ago it could be done but I sure couldn't get it to work when I went through several replacement phones. :/
RoyJ said:
Hey if you ever figure this out, let us know. I have tried to restore backups from one gnex to another with no luck. I have used CWM and TWRP. Tried leaving the files as is and also renaming them. I tried transferring them via computer as well as uploading them to dropbox and downloading from there. Someone told me a while ago it could be done but I sure couldn't get it to work when I went through several replacement phones. :/
Click to expand...
Click to collapse
My plan for tomorrow is to flash a current PA 2.53 ROM onto the said device, and then restore the backup from there. My theory is that the phone won't take the backup img properly because of a mismatched OS version (4.1.1 going to 4.1.2). By flashing the PA 2.53 ROM, I will then be on 4.1.2, and I can flash the backup from there (so that I don't have to reload all my apps and data manually).
That's just speculation tho, so I could very well be wrong. Will report back when I try it!
peachpuff said:
You can fix the md5 mismatch quite easily http://forum.xda-developers.com/showthread.php?t=714114
Click to expand...
Click to collapse
Nice thread, hadn't come across it, it's indeed a easy fix. Use the command all the time, well actually
sha256. 8 thanks limit per day reached.
3rdstring said:
Yes it very well may have caused your problem
Click to expand...
Click to collapse
2nd or 3rd post of the thread linked by peachpuff also said that. they dont like to read. 8 thanks limit per day reached.
rice923 said:
My plan for tomorrow is to flash a current PA 2.53 ROM onto the said device, and then restore the backup from there. My theory is that the phone won't take the backup img properly because of a mismatched OS version (4.1.1 going to 4.1.2). By flashing the PA 2.53 ROM, I will then be on 4.1.2, and I can flash the backup from there (so that I don't have to reload all my apps and data manually).
That's just speculation tho, so I could very well be wrong. Will report back when I try it!
Click to expand...
Click to collapse
Try this: format /system before restoring the backup, if /system was also backed up.
Sent from my i9250
bk201doesntexist said:
Nice thread, hadn't come across it, it's indeed a easy fix. Use the command all the time, well actually
sha256. 8 thanks limit per day reached.
2nd or 3rd post of the thread linked by peachpuff also said that. they dont like to read. 8 thanks limit per day reached.
Try this: format /system before restoring the backup, if /system was also backed up.
Sent from my i9250
Click to expand...
Click to collapse
Yes, I actually read the thread and found that response. I just happened to post my question before reading the thread.
Anywhoo, nothing has actually worked so far. I'm actually ready to cave in and just do a fresh start. Sorry to let ya down RoyJ
6.x CWM issue?
what version of CWM are you using? if you are using version 6.x did you also transfer the "/sdcard/clockworkmod/blobs" folder to the new phone?
Related
I get the error:Can't open /sdcard/.....zip(bad)
Any other solutions besides the one in the older thread. It's directions were not clear at all.
It's a bad dowload.....try redownloading....happens to me all the time when DL'in from my PC....not sure what the other responses to u were.....but that's what's happeneing
Sent from my PC36100 using XDA Premium App
Reverepats...I downloaded two different MikG Roms and neither worked, I also tried Kings Alliance it had the same error. When I ran the Rom I was running before, SalvageRom, it worked. I see you are running MikG, where did u download from?
I'm assuming that you've tried reflashing recovery? Or possibly switching recoveries?
(from... Evo/MIUI/Tapatalk)
The file corrupted, and you just need to download it again.
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
corey140 said:
No Plainjane, I didn't try flashing recoveries. I am currently using Amon RA's recovery v 2.3 I believe. Is there a newer version? If so, where do I find it to flash?
Click to expand...
Click to collapse
2.3 is the latest version. If you choose to reflash just do it via PC36IMG; though I'm positive its just a bad download.
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
corey140 said:
teh roxxorz, I tried the download from HTCEVOHacks.com and MikMik Website and they both failed. I think both were 250MB, which was bigger than usual so it is possible, but I also tried flashing the Alliance Kingdom Rom from this site and got the same error. That's why I figured it was something with my phone. I got an (Oops Error, something went wrong, when I tried to do a Nandroid Restore also. I was able to reflash Salvage Rom and it worked perfect. SO CONFUSED...LOL!
Click to expand...
Click to collapse
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
teh roxxorz said:
Well the bad zip [can't flash] means something is wrong with the zip file, the 'oops something went wrong,' means that the backup became corrupted.
http://dl.dropbox.com/u/19699565/PC36IMG.zip
Download that [ra recovery] place on the root of your sd card, boot into the bootloader, then apply update, reboot; and amon_ra 2.3 will be reflashed.
Click to expand...
Click to collapse
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
corey140 said:
I really appreciate your help!!! So this flash will enable me to perform my Back-up right. I apologize for all the questions, I just started flashing and I am learning the basics.
Click to expand...
Click to collapse
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
teh roxxorz said:
You're straight, and well, potentially. IF the recovery backup itself is corrupted, you'll get the 'oops, something went wrong' error; if it was the recovery. Though you will be able to create and restore backups.
Click to expand...
Click to collapse
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
corey140 said:
Cool, downloaded the Amon RA Recovery you posted in the link. Flashed it and it went through. Will try to perform my Nandroid backup and post results.
Click to expand...
Click to collapse
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
corey140 said:
OK, it went more than the first time, but then got the same error:
Oops... something went wrong!
Please check the recovery log!
Click to expand...
Click to collapse
Yea, unfortunately, that backup is corrupted, and you'll have to scrap it. Hopefully you have another one, or in a position to create a newer one.
Can I just Reboot and go back to what I was using?
corey140 said:
Can I just Reboot and go back to what I was using?
Click to expand...
Click to collapse
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
teh roxxorz said:
If you reboot, you'll be on whatever you were running before; as long as the backup didn't restore.
Click to expand...
Click to collapse
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
corey140 said:
Cool that's what I will do. Hopefully I can get one of the new Gingerbread Roms here(MikG Preferably) with a .zip that is not corrupted. Since you and Plainjane are pretty sure it is the file that is corrupted. THANKS for all the help.
Click to expand...
Click to collapse
Well I'm certain it is.
IF all else fails, go to the link on your evo, then download the zip from your phone, make your backup, do a full wipe, then locate it in the folder when you flash.
I'm almost certain it's an issue with your SD card. I've seen it before, but just recently remembered what the problem was. Sorry for the late reply, I was at work.
Backup everything on your card to your computer, this will erase all of your files. Also try to have a full battery, this could take some time depending on the size of your SD card, the class, and the number of files. Then, boot into recovery and select partition SD card (I can't remember where it is, sorry). If you move apps to your SD card - which I think is kind of necessary with the ginormous Sense 3.0 roms - use a larger size for the Ext partition. I never move apps to my SD card, so I set mine to the smallest option other than zero. For the swap size you can use the default 32mb - you may want to look into this more to see if there's a more recommended size.
When it finishes partitioning, go back to the main screen in recovery, plug your phone into your computer and select USB-MS toggle. This will mount your SD card so you can move files back to the SD card. If you're using Windows, it may want to scan and fix the card... just skip it. If you want to save time and/or battery, you can power down the phone and use a card reader instead. Then you can try to restore/make a nandroid backup or flash a rom - it should work.
Good luck, hope you get it fixed!
(from... Evo/MIUI/Tapatalk)
Download MikG 1.04 from http://dev-host.org/lv6fjpxaq9x4/MikG-Sense2.1-v1.04-signed.zip
After downloading the file, get an MD5 checker application such as this one: http://getmd5checker.com/download
The MD5 sum for the zip of MikG 1.04 is: fb81c61a19b5db6d4fa67acbfb17907f
When you run the MD5 check on the downloaded zip, it should match.
If it doesn't then the download is corrupted.
If it does match but you're still having issues flashing it, then there's a pretty good chance that it's the SD card. MicroSD cards are a dime a dozen nowadays so it should be pretty trivial to get some other card that you can pop in and try to flash with.
Here is a stock rom backup for the Sprint G S III. I made the backup after doing a data wipe, so the rom is pure, no lingering data, ect.
Instructions:
-unzip the .zip file
-move the backup folder into your existing CWM folder on the S III internal memory
-restore in recovery
Again, this is a stock backup as some people need it.
https://dl.dropbox.com/u/19699565/fresh_GSIII_backup.zip
From my dropbox, so hit it easy.
Nice, know of some that will appreciate this.
bizdady said:
Nice, know of some that will appreciate this.
Click to expand...
Click to collapse
Me too
Sent from my SPH-D700 using XDA Premium App
<3
Warning: if you flash this make sure you clear Google wallets data as shown in a qbking77 video so you don't brick the secure element
Sent from my SPH-L710
How is this in any way a stock rom?
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
Give him a break. At least this isn't in development.
And he at least did something that could be useful until we get a real stock rom .zip or .tar
~E.R.A.
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
You have been in every thread criticizing everyone else s contributions...what the hell have you contributed?
nabbed said:
How is this in any way a stock rom?
Click to expand...
Click to collapse
It's not, it's a backup. That's not the point, it's still useful to many users that have possibly screwed their device but still have access to recovery. Especially until something official comes out.
will there be a stock package on odin different than just the stock boot image? my phone is bricked for no apparent reason(see my thread here http://forum.xda-developers.com/showthread.php?t=1731416) and flashing the stock boot image in odin does nothing. i Also cant get into CWM to flash my backup...
pizzlewizzle said:
will there be a stock package on odin different than just the stock boot image? my phone is bricked for no apparent reason(see my thread here http://forum.xda-developers.com/showthread.php?t=1731416) and flashing the stock boot image in odin does nothing. i Also cant get into CWM to flash my backup...
Click to expand...
Click to collapse
Eventually there will be, but a lot of people [to include major developers] still don't have the phone yet, so we'll have to be patient. I looked over it, though currently are you able to get into recovery still or no? Additionally did you try re-flashing the cwm recovery in odin?
I can get into download mode but not into CWMR. The only thing i have tried flashing since it bricked is boot-stock-sprint-sph-l710.tar (which sort of worked the first time). I'm at work and don't have my phone on me so i guess i could try flashing CWMR again later but this is really weird. Thanks for the reply. This is my first Sprint phone, but on my Droid X we had a program similar to Odin where you could push a .sbf file that included everything stock and basically just reset your phone to stock. Do these exist for Sprint phones? The . SBF files were usually rather large(around 350mb or so) but the boot-stock-sprint-sph-l710.tar is around 10 or 15 mb so i know it doesn't include all the system files...
Thanks again
teh roxxorz said:
Eventually there will be, but a lot of people [to include major developers] still don't have the phone yet, so we'll have to be patient. I looked over it, though currently are you able to get into recovery still or no? Additionally did you try re-flashing the cwm recovery in odin?
Click to expand...
Click to collapse
Lol i just replied the same thing over on another thread he posted in. Stop jumping around pizzle! if you can get into Odin chances are good you can flash cwm and then restore the backup
hahaha sorry about that. When I try and boot into recovery it looks like its about to go to Recovery and then freezes on the Galaxy S III screen. I'll try reflashing CWMR when I get home...Thanks for the advice
So is a back up a nandriod?
I have made a few but never resorted one, you just flash it same as a ROM and your done?
I misplaced my stock nandroid when I flashed CM10 build 2 and my extFs SD card had to be formatted to use again, I was sure I had in on PC but can't find it.
Thanks!
So I attempted to upgrade my girlfriend's Galaxy Nexus from 4.1.2 to 4.2.2 (this is on Verizon. Was using a Xenon HD version from last August and attempted to update to the newest version).
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
All I want to do at this point is just restore a nandroid backup and start over from scratch. Any help would be greatly appreciated.... I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Thanks in advance.
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
can you boot into recovery? what do you mean you cant get things working properly
slimb9 said:
can you boot into recovery? what do you mean you cant get things working properly
Click to expand...
Click to collapse
Yeah I can get into recovery but when I try to restore nandroid it says there are no files, and I know there is a backup.
I did a half hour of searching, but thanks for the help. I must not be searching for the right thing....
so can the phone turn on? or can you only boot into recovery
slimb9 said:
so can the phone turn on? or can you only boot into recovery
Click to expand...
Click to collapse
Yeah I can turn it on. Gapps didn't install, though, so I don't have a keyboard and can't install goomanager from the play store to update recovery. I also can't move files in the file manager because it times out very time.
if you still have the old xenon rom .zip file on the phone you could just flash that after wiping/clearing everything. then from there boot into recovery and see if you can see your nandroid backup of the old xenon she was on. not sure if this will help but worth a try. looks like the new xenon rom required a full wipe so something may be messed up that you could fix by flashing an older version
Asterdroid said:
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
Click to expand...
Click to collapse
063_XOBX said:
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
Click to expand...
Click to collapse
As 063_XOBX said, sdcard/0 is supposed to exist. Considering your comment later in the thread about not being able to find old backups, it sounds like you have an outdated recovery that doesn't understand the new file structure. Update your recovery rather than screwing with Google's intended file structure.
Asterdroid said:
I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Click to expand...
Click to collapse
What driver issues? You haven't been overly clear with the actual problems that you're having. You said you had a problem with Gapps. Why not download and flash a Gapps package?
i p.m. him without a response. im sure he figured out he was doing something wrong. it helps to read instructions
Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing
Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse
small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse
installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse
Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse
UPDATE:
Flash using **CWM from Freegee**( I previously recommended Philz for the updated look and features but it is SUPER inconsistent and unfortunately unreliable, I do not mean any offense to its creator/developer, it is just too much hassle and this thread is meant for easy flashing and I was already posting the work around for the Philz bootloop issue which killed the purpose of easy flashing...)
Remember to make a nandroid/backup using CWM, if you forgot to make one, PM me to help you sideload a Rom using ADB. (will save you the hassle of going through stock and go directly to any custom rom of your preference)
Hello dear people with an E980:
I'm here to share a backup I made for my personal use to avoid the hassle of having to return to stock to flash the VUPMP stable rom and deleting the recovery folder inside the Rom, pretty much in other words it's just an "easy-to-flash" backup.
Rom comes from:
http://forum.xda-developers.com/opt...om-20140920-vupmp-gpro-sg3-stable-lg-t2902595
Here is the backup!, it is flashable so don't extract it, it includes a boot.img (kernel) so you can restore from any rom, no need to come from stock:
https://www.androidfilehost.com/?fid=95747613655048316
MD5: f50a74eb5ceb7600d0ea609192d5c258
On this particular backup, I applied the following fixes for E980:
-Volume restore fix
-Video recording fix
-Removed a system apk which seemed to be a calendar in viet (for the sake of clean and stock look).
It is highly recommended to wipe before flashing:
-Data (without wiping data/media, if you don’t know how to do this just ask in the Q&A section or PM me!!)
-Cache & Dalvik cache
-System
-Please, don't report bugs if doing a "dirty" flash.
Special thanks to:
@datphu2811 for developing such a cool ROM
@Chairizkuro for the video recording fix
anyone who contributed with this files linked above!
Remember:
Flash at your own risk!
Anyone try yet?
Anybody try this yet? Looks cool! Sounds easy.
DollarStrawz said:
Anybody try this yet? Looks cool! Sounds easy.
Click to expand...
Click to collapse
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
GreatCaesar said:
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
Click to expand...
Click to collapse
Man thanks!! I was just about to do it.
GreatCaesar said:
I did, I followed the instructions but got stuck in a boot loop and it didn't fix when I applied the aforementioned zip. I just went back to stock the normal way and everything worked out. That's just my experience though, you could have completely different results.
Click to expand...
Click to collapse
Can you describe your problem? What kind of bootloop did you get?
A) it kept booting to recovery (that's what the zero zip is for)
B) it kept stuck in the lg logo
If B)
Did you performed a full wipe of data (without data media), system and cache? Did the flash took an unexpected amount of time (2 seconds instead of 2 minutes)?
Additionally, why did you totted back? Didn't you made a backup first?, in case you made a backup, did the recovery rendered useless after flashing my backup?
Did you get any lokifying errors?
DollarStrawz said:
Man thanks!! I was just about to do it.
Click to expand...
Click to collapse
Please let the person answer those questions before walking away scares, I've tried my own backup several times and I assure you it works properly if following the instructions. Even further, it's common sense to do a backup even without being warned about it.
OK yeah thanks I will still try it. Thanks for making this. It looks super cool and easy.
DollarStrawz said:
OK yeah thanks I will still try it. Thanks for making this. It looks super cool and easy.
Click to expand...
Click to collapse
Please use CWM from Freegee, I have been getting reports from a few friends testing on how Philz touch is being inconsistent, I'm about to update main post.
Md5 Mismatch
I followed ever4ything I think. I extracted it on my desktop then copied that folder over to Clockworkmod/backup folder. After wipingt everything I went to restore and got Md5 Mismatch. What did I do wrong?
DollarStrawz said:
I followed ever4ything I think. I extracted it on my desktop then copied that folder over to Clockworkmod/backup folder. After wipingt everything I went to restore and got Md5 Mismatch. What did I do wrong?
Click to expand...
Click to collapse
Can you please manually check the MD5 sum of your downloaded file? Let me know if you don't know how to do it I can show an easy method.
Jose-MXL said:
Can you please manually check the MD5 sum of your downloaded file? Let me know if you don't know how to do it I can show an easy method.
Click to expand...
Click to collapse
I checked the re-downloaded one and they match. I used an Md5 checker?? So am I on the right track by extracting and copying that folder to clockwork backup? Then in CWM go to Mounts and Storage and format /data, format /system, format /cache and wipe dalvik. THEN restore the folder copied earlier. Just want to make sure I'm not missing anything. Thanks!!
DollarStrawz said:
I checked the re-downloaded one and they match. I used an Md5 checker?? So am I on the right track by extracting and copying that folder to clockwork backup? Then in CWM go to Mounts and Storage and format /data, format /system, format /cache and wipe dalvik. THEN restore the folder copied earlier. Just want to make sure I'm not missing anything. Thanks!!
Click to expand...
Click to collapse
Oh! OH! OH!!, I know what's going on, this is a flashable zip lol, you are not supposed to extract it, sorry if I provided misleading instructions so I can change them
AWESOME
Loving this ROM everything works great!!
Can't get LTE To Stick
Everything works great but the one thing bothering me is I can't seem to get Global + LTE to stick after following the steps:
- Input 5457#*988# from dial pad
- Find "Network Mode" set value "Global + LTE"
- Find "CDMA Subsciption" set value "USIM"
When I try to switch from NIV to USIM the phone instantly reboots and reverts the network back to WCDMA. Does anyone know how to fix this?
Jose-MXL said:
Oh! OH! OH!!, I know what's going on, this is a flashable zip lol, you are not supposed to extract it, sorry if I provided misleading instructions so I can change them
Click to expand...
Click to collapse
How is the flushable ROM running. Thinking about flashing. Any differences from other VROM