Related
Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.
Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?
Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App
velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App
LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse
scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse
Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.
The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
It depends what device you have. Different things can cause different devices to brick. Usually a "bricked" device is caused by a bad kernel (more so by over clocking or overvolting), (If you have an HTC device) a bad HBoot, flashing a leak that is incomplete or flashing an update (RUU, Odin, whatever) for the wrong device, or flashing a package for the wrong device or one that is improperly coded.
You CANNOT brick your device by flashing custom roms and recoveries or anything like that, and permanent, unfixable, hard bricks are VERY rare and are usually because someone did something stupid.
If you're worried about installing a custom ROM or something, don't worry, it won't brick you.
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
Bricks happen when you try something not meant for your phone.
Sent from my U8150 using XDA
Thank you so much for clarifying this to me...
I am not total beginner, i possess Galaxy GT-I9001, for 4 months and i installed CWM last week, with complications, i used Odin 4.03 what one guy instructed to me, beside 4.43. First 4.03 failed and my phone failed to boot, I was worrying i could lose the phone. Then i used 4.43 from the Wiki tutorial what fixed the things...
Now i want to Root the phone, so this previous experience scared me, now i am not confident about it so I used to ask here...
So to clarify:
- rooting
-CWM
-flashing - installing custom ROMS
in proper way and following instructions won't brick my phone?
Is it possible that the dev/alpha/beta ROM versions could brick my phone?
How hard brick happens I am interested?
Is soft brick always fixable?
Sorry for bothering with this stupid questions, I am just not too confident, and i don't wanna destroy the phone, i've got no money for another
Thanks again and sorry if bad English
bricked= corrupted bootloader
a really bricked phone is like "dead' and the only way to solve this problem is to flash a new-and-happy bootloader by hardware tools like Medusa jtag jig also you can't solve bricked phone by PC software if yo do so then your phone is not really bricked
I don't know anything about hard/soft bricked what's that ??
you can't brick a phone by flashing a beta rom if you don't touch bootloader but you can destroy or cause hardware damage by flashing a rom/kernel not made for your phone so that's very important to know !
to prevent bricking your phone:
1. never use a flashing tool not made for your phone
2.when flashing bootloader made for your phone only use a stable PC connection/cable and is better to use a laptop on battery
3.about ROM Manager :if you don't see your phone in list never use it to flash recovery/rom
rooting means to get root access this is like your Administrator account in Windows OS well, it happens because by default phones come out from manufacturer with root disabled to protect the phone and their business
CWM is a custom recovery in fact this is a little OS that works like Safe Mode in Windows it can help you to flash a rom/update/theme etc
CWM recovery is different compared to stock recovery because it gives you the chance to flash custom things to your phone I mean you have to give a package a digital signature in order to flash it to your phone and stock recovery is restrictive it allows you to flash only signed-by-manufacturer things like roms/updates/themes and here is the place where CWM comes it allows to flash self-signed packages
Follow tutorials and you won't brick your phone. Stick to your device forum. E.g ,Just because something worked on the galaxy ace doesn't mean you can use that tutorial on a galaxy mini.
Soft bricks can be fixed,those are just installation errors.
Sent from my U8150 using XDA
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
Why would you want to remove cwm? Its a custom recovery, without it you can't go custom. Use cwm to create a nand backup. To go back to stock recovery, you are correct, but make sure you have correct files etc in Odin. Pulling out your USB cable in Odin without completed will brick your phone, I know cuz I did it. The wrong files can do the same. CWM doesn't change the ROM, just the recovery. I have also heard of bricks from Samsung kies mini. Yes you need to wipe/ factory data reset when flashing a new ROM. If you are only updating a custom ROM, going from (ROM name) v 1.2 to (ROM name) v 1.3 it is not always necessary to do factory data reset but follow the instructions per developer of ROM/thread. Get root, put custom ROM on sd, in recovery make a nand backup, wipe cache, wipe dalvik cache, factory data reset, install zip from sd, reboot.
Also sometimes when flashing a ROM it might not boot first time. Don't panic, pull battery out/in 3 button to recovery, install zip again, reboot and enjoy.
Hope this helps....if so hit thanks button!
sent courtesy of the pony express
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
No,your stock rom is not changed,just your recovery. You'll need clockworkmod do install custom roms since stock recovery lacks the features needed to install non-manufacturer roms.
If you are concerned about altering your current rom,you can make a backup using clockworkmod recovery, and store it somewhere like your PC.
Yes,just to be safe, it is better to wipe data. Unless it's an update of the same rom which again, isn't always guaranteed. Just to be sure your safe,backup your apps and clear everything.
Clockworkmod is removed in the bootloader by swapping it out with something else(like amon-ra).
Sent from my U8150 using XDA
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
TwinHeadedEagle said:
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
Click to expand...
Click to collapse
It is possible to reset the phone fully to stock. This removes clockworkmod recovery and your custom rom and allows you to claim warranty. So far only Sony is the one I'm aware void your warranty permanently if you unlock your bootloader using their 'official' method. They keep you on record,so even if you relock it you're outside warranty.
Sent from my U8150 using XDA
How To Unbrick my Kindle Fire?
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
lcharrisej said:
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
Click to expand...
Click to collapse
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
@ Allanitomwesh
You didn't tell me how to reset phone fully to stock
I am assuming you haven't started playing with your phone.
Dial *#1234# and write down the three ID Strings PDA, CSC & PHONE ID
They'll be useful later. Just for paranoia, use adb to save your IMEI details (adb is for windows PC's don't worry)
Install Samsung Keis in same PC. Make sure it recognises your phone. Always check this before running Odin.
Always do a full backup (apps, data,settings) before resetting to stock or just any flashing.
Odin will install custom roms on your phone,and it will also take you back to stock if need arises. This is done by 'flashing' stock rom into your phone.
You can follow this tutorial
http://forum.xda-developers.com/showthread.php?t=1345671
Where the rom is the stock one. You can get the right one here http://www.sammobile.com/firmware/?page=1&t=2 Clockworkmod and root access will be lost.(those come with custom roms,don't worry)
When using Odin, a few tips,
1.always run as administrator (right click on icon>run as administrator)
2.Odin runs better without sim card and SD card. You can take them out before entering download mode
3.NEVER EVER interrupt a flashing process,its a guaranteed soft brick.It takes about 10 minutes. If you're impatient, walk away. Also for paranoia,better to have a ups.
4. Perform factory reset before and after flashing. * Menu* Settings* Privacy* Factory data reset* Reset phone& Erase everything. Before and after.
If your rom doesn't boot try this
http://forum.xda-developers.com/showthread.php?t=1660596
Sent from my U8150 using XDA
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
xmond said:
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
Click to expand...
Click to collapse
Ask here for better assistance
http://forum.xda-developers.com/forumdisplay.php?f=1211
Sent from my U8150 using XDA
Thanks
Allanitomwesh said:
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
Click to expand...
Click to collapse
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
lcharrisej said:
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
Click to expand...
Click to collapse
Not necessarily, but it does sound like you went abit overboard with clearing data.
Try and restore stock rom on your kindle. The method where you lose root preferably.
Sent from my U8150 using XDA
I am looking for some guidance and assistance in the following matter.
Did a standard over the air update to JB and from what I can see I lost all my user data from my internal storage.
All my custom directory are gone, DCIM empty.
Been out of the country, not that it matters where I was, and the standard HTC One X device prompted me of a system update. (I have not rooted nor flashed any custom firmware on this puppy yet.)
All seemed to go smooth and the phone started normally. Although I lost all my data.
Android Version:4.1.1
Software Number : 3.14.401.31
First I wanted to ask if anyone has seen this behaviour before?
I tried to do some date recovery with Recover my Files v5 but now see that there is an internal SD mount issue with JB.
What would the best way be to proceed as I am only interested in trying to recover my data?
Thanks in advance.
Internal SD data has been lost or corrupted for some people (including myself a couple times) while flashing custom ROMs. Don't think anybody ever figured out exactly why, but it seemed related to the phone itself (rather than custom recovery or the ROMs themselves). So it wouldn't surprise me if this is the same or similar issue.
Not sure how to recover your data. There was a similar post (maybe last week) and I think somebody mentioned a couple market apps that might be able to recover the data in this situation (since JB can't mount as mass storage to use PC programs like Recuva).
Solved
Thank you Redpoint for your thoughts. I hoped that I would find an easy reply to solve my problem but in the end this is what I knew I ultimately had to do.
Quick summary:
Unlocked Bootloader via HTC Dev.
Flashed Recovery, Team Win Recovery Project 2.4.1.0
Mounted SD as a drive via Recovery.
Ran RecoverMyFiles v5 and recovered the files that I lost.
Now to go ROM shopping and start again. This time I will listen to my own warning and keep a copy online.
Nobody wanted to suggest that because all that stuff includes writing to the sd card which could overwrite your files. Glad you got some recovered
Sent from my VENOMized HoxL
Regalrip said:
Unlocked Bootloader via HTC Dev.
Flashed Recovery, Team Win Recovery Project 2.4.1.0
Mounted SD as a drive via Recovery.
Ran RecoverMyFiles v5 and recovered the files that I lost.
Click to expand...
Click to collapse
Ah yes, I always forget that the SD can be mounted as mass storage in recovery.
Nice job. IMO, unlocked bootloader is a great thing. Just probably a bit stressful under the circumstances!
Hi all, I'm newly registered here, however, I have been coming here to XDA for over two years now as unregistered to browse and become more knowledgeable regarding rooting, unlocking and ROMing my phones. I would like to use the Casual Root/Unlock/Recovery AIO Toolkit and finally have more freedom over my locked down Verizon Galaxy S3. I am currently running MF1 and I'm completely 100 percent stock. I've downloaded Casual, have all the Samsung drivers installed and am anxious to pull the trigger. I just want to confirm I'm on the right page and do diligence first. After I run Casual and Root, unlock the bootloader and install TWRP, would it be wise to immediately boot into recovery and then backup the rooted MF1 firmware and then back up my imei by copying the efs folder to the SD card and my PC? Is this method correct for backing up the imei or is there a specific program for it? I have searched through many custom ROM's and I am planning on flashing Beanstown106's Jelly 'Beans' Build 19 ROM, as I love the fact it's AOSP themed but has a lot of features from Touchwiz. Does this ROM happen to back up the imei automatically by chance? I've already backed up my contacts and important information, so are there many things I'm missing or am I on the right track? Before flashing Jelly 'Beans', would I need to wipe the cache / davlik at all? Or is that only when coming from a different ROM? Any help wouwould be greatly appreciated and many thanks in advance for your time!
K20Z1 said:
Hi all, I'm newly registered here, however, I have been coming here to XDA for over two years now as unregistered to browse and become more knowledgeable regarding rooting, unlocking and ROMing my phones. I would like to use the Casual Root/Unlock/Recovery AIO Toolkit and finally have more freedom over my locked down Verizon Galaxy S3. I am currently running MF1 and I'm completely 100 percent stock. I've downloaded Casual, have all the Samsung drivers installed and am anxious to pull the trigger. I just want to confirm I'm on the right page and do diligence first. After I run Casual and Root, unlock the bootloader and install TWRP, would it be wise to immediately boot into recovery and then backup the rooted MF1 firmware and then back up my imei by copying the efs folder to the SD card and my PC? Is this method correct for backing up the imei or is there a specific program for it? I have searched through many custom ROM's and I am planning on flashing Beanstown106's Jelly 'Beans' Build 19 ROM, as I love the fact it's AOSP themed but has a lot of features from Touchwiz. Does this ROM happen to back up the imei automatically by chance? I've already backed up my contacts and important information, so are there many things I'm missing or am I on the right track? Before flashing Jelly 'Beans', would I need to wipe the cache / davlik at all? Or is that only when coming from a different ROM? Any help wouwould be greatly appreciated and many thanks in advance for your time!
Click to expand...
Click to collapse
To backup your imei/eri check the synergy rom thread. They have a zip to back them up. It's in the attachments. It only takes a few seconds but will save you a world of headache. If you want my opinion that's the first thing you should do once you root, unlock and have your custom recovery. Store that zip on your SD card, PC and cloud(Dropbox, Copy, Box, Mediafire, etc).
Sent from my SCH-I535 using Tapatalk 4
TheAfroSamurai said:
To backup your imei/eri check the synergy rom thread. They have a zip to back them up. It's in the attachments. It only takes a few seconds but will save you a world of headache. If you want my opinion that's the first thing you should do once you root, unlock and have your custom recovery. Store that zip on your SD card, PC and cloud(Dropbox, Copy, Box, Mediafire, etc).
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I greatly appreciate your insight and input TheAfroSamurai. I will check that thread out and get that zip to backup the imei / eri.
K20Z1 said:
I greatly appreciate your insight and input TheAfroSamurai. I will check that thread out and get that zip to backup the imei / eri.
Click to expand...
Click to collapse
Here you go : http://forum.xda-developers.com/attachment.php?attachmentid=1281376&d=1345868740
Once you get root and unlock the bootloader, backing up your EMEI is recommended (I did not until I flashed my first ROM). There is a great
thread that the previous poster may have pointed you too (if so, sorry for the repost): http://forum.xda-developers.com/showthread.php?t=1852255
Previously you were pointed to the Synergy method (B). But A is very easy too, requiring you to have a terminal emulation app on your phone (I have Rom Toolbox Pro, which has a terminal emulator). Type in the two commands as instructed and it reboots. I then did B and hopefully I am doubly covered.
After that, flash your preferred ROM (lots of really good ones, I use BoneStock 3.4) and you are ready to go.
TheAfroSamurai said:
Here you go : http://forum.xda-developers.com/attachment.php?attachmentid=1281376&d=1345868740
Click to expand...
Click to collapse
Ahh, thanks very much for the link, even easier to find.
Nomad1600 said:
Once you get root and unlock the bootloader, backing up your EMEI is recommended (I did not until I flashed my first ROM). There is a great
thread that the previous poster may have pointed you too (if so, sorry for the repost): http://forum.xda-developers.com/showthread.php?t=1852255
Previously you were pointed to the Synergy method (B). But A is very easy too, requiring you to have a terminal emulation app on your phone (I have Rom Toolbox Pro, which has a terminal emulator). Type in the two commands as instructed and it reboots. I then did B and hopefully I am doubly covered.
After that, flash your preferred ROM (lots of really good ones, I use BoneStock 3.4) and you are ready to go.
Click to expand...
Click to collapse
I greatly appreciate your help and advice as well, it's nice to know of other possible options backing up the imei. Something else I just thought of, once I root, unlock and get recovery using Casual, should I expect to see a message from Verizon stating that the software running is not official and to visit one of their stores? I have seen others mentioning this, but I'm not sure if and why that pops up. If it does, does it continue to pop up or stay on the screen at all? Or is it something that you can dismiss and you don't see it again?
Do you guys know if terminal emulator comes already installed on the Jelly beans rom by chance? Because that seems the easiest way to do it just by typing in those two commands. However, I would still download that .zip tool from Synergy as backup. Or would that not be needed at all if I was to use terminal emulator?
TheAfroSamurai said:
To backup your imei/eri check the synergy rom thread. They have a zip to back them up. It's in the attachments. It only takes a few seconds but will save you a world of headache. If you want my opinion that's the first thing you should do once you root, unlock and have your custom recovery. Store that zip on your SD card, PC and cloud(Dropbox, Copy, Box, Mediafire, etc).
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
After using casual, do I just place that zip on my sdcard pc and cloud and then run it if and only when the imei is lost? Or run it prior to placing it on the SD card and such? Sorry for all the newb questions.
K20Z1 said:
After using casual, do I just place that zip on my sdcard pc and cloud and then run it if and only when the imei is lost? Or run it prior to placing it on the SD card and such? Sorry for all the newb questions.
Click to expand...
Click to collapse
After you finish casual place the zip on your external sd card. If you haven't flashed a custom rom with boot to recovery menu you'll have to get to your recovery the hard way. Power down phone, hold vol up and home button at the same time you press power. Keep holding home and vol up key and let power button go. Phone should boot to your custom recovery, either CWM or TRWP depending on what you choose to use. Next go to install and navigate to the Synergy zip and choose install just like flashing a rom, kernel,etc. It will place a Synergy folder on your external sd. That folder will contain the backup zip you'll need in case you lose your IMEI/ERI. Make at least a couple backups of that.
Awesome! I really appreciate the help and quick responses. So once I've done that, if my imei should become lost, I would open that synergy folder and use the backup to restore the imei?
K20Z1 said:
Awesome! I really appreciate the help and quick responses. So once I've done that, if my imei should become lost, I would open that synergy folder and use the backup to restore the imei?
Click to expand...
Click to collapse
If you should ever need to just flash the zip in the Synergy folder, hopefully you won't ever need to. Once I got mine restored I haven't had to yet...fingers crossed.
Ok, perfect. That really sums it all up for me. Yea, hopefully you won't ever need it.
K20Z1 said:
Hi all, I'm newly registered here, however, I have been coming here to XDA for over two years now as unregistered to browse and become more knowledgeable regarding rooting, unlocking and ROMing my phones. I would like to use the Casual Root/Unlock/Recovery AIO Toolkit and finally have more freedom over my locked down Verizon Galaxy S3. I am currently running MF1 and I'm completely 100 percent stock. I've downloaded Casual, have all the Samsung drivers installed and am anxious to pull the trigger. I just want to confirm I'm on the right page and do diligence first. After I run Casual and Root, unlock the bootloader and install TWRP, would it be wise to immediately boot into recovery and then backup the rooted MF1 firmware and then back up my imei by copying the efs folder to the SD card and my PC? Is this method correct for backing up the imei or is there a specific program for it? I have searched through many custom ROM's and I am planning on flashing Beanstown106's Jelly 'Beans' Build 19 ROM, as I love the fact it's AOSP themed but has a lot of features from Touchwiz. Does this ROM happen to back up the imei automatically by chance? I've already backed up my contacts and important information, so are there many things I'm missing or am I on the right track? Before flashing Jelly 'Beans', would I need to wipe the cache / davlik at all? Or is that only when coming from a different ROM? Any help wouwould be greatly appreciated and many thanks in advance for your time!
Click to expand...
Click to collapse
Man i was right there with you. Not quite two years, but maybe two months of reading, researching, watching vids, etc. I downloaded the casual too because i am not great with adb commands, etc. I will tell you from personal experience exactly what my opinion is of what you should do. Someone else more experience may have a better way but now that i have become a serial flashaholic hindsight is always 20/20.
1. Find the stock firmware for the Verizon Samsung Galaxy S3 any version whether is be VRBMF1 or older and download Odin. That way if anything happens short of a hard brick you can ALWAYS Odin back to stock if you are completely out of options.
2. Run CASUAL to (a) Root (b) Unlock the Bootloader and (c) download TWRP ; I have used Clockword Mod and TWRP and I personally found TWRP much easier to use
3. First thing I would do is download the Synergy HWkeys backup zip and flash it while you are still stock rooted to backup the imei. Thank God i haven't lost the imei before i backed mine up but that way you have plan b and plan c, etc.
4. Make a TWRP Nandroid backup of your stock rom that way you can always restore back up stock.
After you do that you are good to flash away my brotha. And a note too, remember that for most roms you need to flash gapps separately. I freaked my first flash and thought i broke my phone because i had no google apps but that was noob stuff on my end.
I hope this helps but all these roms and everything are really cool. the reason i came to android in the first place. and i dont donate as much as i should but you gotta give it up to these developers. anyways. later man
happy flashing
Synergy backup works. I recently lost mine and had to restore it. It was super easy to do, but I wasn't sure at first if it was going to work. Couldn't tell you what caused it because I am super careful to download all the correct files to flash Roms. Also all AOSP Roms require you to download the GAPPS for whatever version of android it is running. All TW based Roms already have the GAPPS included in the ROM zip file. Just be careful when switching back and forth between AOSP and TW Roms. A good practice is to wipe everything 3 times to make sure you got everything. Sometimes also there are residual files and/or folders left over from AOSP Roms when switching back to TW so I have a practice of wiping internal storage before I switch back to TW. Just move whatever files you want to save to your external SD card. I switch Roms often so I usually don't have to move very much. I also don't restore apps or data from titanium backup. This most likely can cause problems if you're restoring data from a different ROM.
Sent from my SCH-I535 using Tapatalk 4
Hello all,
Been a long time dweller and avid reader here. I fell off for a while with my t700. Made the mistake of not checking which TWRP I was on before flashing. So, though everything appeared to
go okay, the OS didn't load. So then I realized my mistake (I was on TWRP 2.6.3-that3) and figured the way around it might be to flash an older ROM, then update TWRP, then go from there. So
I flashed CROMi- XENOGEN 4.7.0. And it also went into a never ending load. I think because I can still get into recovery there is a way out of this? A simple-ish way? Any help would be greatly appreciated.
Sorry to get into this issue with such a stupid newb mistake.
Thanks all,
Macros
p.s. I should mention the ROM I was trying to flash was ZOMBI POP 5.1.1
Macros746 said:
Hello all,
Been a long time dweller and avid reader here. I fell off for a while with my t700. Made the mistake of not checking which TWRP I was on before flashing. So, though everything appeared to
go okay, the OS didn't load. So then I realized my mistake (I was on TWRP 2.6.3-that3) and figured the way around it might be to flash an older ROM, then update TWRP, then go from there. So
I flashed CROMi- XENOGEN 4.7.0. And it also went into a never ending load. I think because I can still get into recovery there is a way out of this? A simple-ish way? Any help would be greatly appreciated.
Sorry to get into this issue with such a stupid newb mistake.
Thanks all,
Macros
p.s. I should mention the ROM I was trying to flash was ZOMBI POP 5.1.1
Click to expand...
Click to collapse
You could go here and update your twrp:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Follow the instruction on the first post how to install the twrp.....
When you have the latest twrp, you may want to format your /data partition because I believed that it is corrupted while installing the previous ROMs. The format may take a very long time so let it finishes before install your prefer ROM. You should be up running with the new ROM of your choice.... Good lucks,....:fingers-crossed:
Thank you for the help. With a little reading and a couple of failed attempts I got the new TWRP on there. And now it doesn't see the external SD card.....which is where the ROM is. Any ideas about that? I double
checked the card to make sure it didn't get fried. It seems to be fine. And the old TWRP saw the contents just fine. If there isn't a way to activate that, can I somehow transfer the ROM to internal memory instead? Although I hate the idea of not being able to use the SD card for flashing.
Thanks again,
Already been a huge help.
Macros
LetMeKnow said:
You could go here and update your twrp:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Follow the instruction on the first post how to install the twrp.....
When you have the latest twrp, you may want to format your /data partition because I believed that it is corrupted while installing the previous ROMs. The format may take a very long time so let it finishes before install your prefer ROM. You should be up running with the new ROM of your choice.... Good lucks,....:fingers-crossed:
Click to expand...
Click to collapse
Macros746 said:
Thank you for the help. With a little reading and a couple of failed attempts I got the new TWRP on there. And now it doesn't see the external SD card.....which is where the ROM is. Any ideas about that? I double
checked the card to make sure it didn't get fried. It seems to be fine. And the old TWRP saw the contents just fine. If there isn't a way to activate that, can I somehow transfer the ROM to internal memory instead? Although I hate the idea of not being able to use the SD card for flashing.
Thanks again,
Already been a huge help.
Macros
Click to expand...
Click to collapse
Is your external uSD formatted in FAT32? Reformat it to FAT32 either in the new twrp or in window to see if it works....
Good luck,
LMK
Nevermind. Updated to the latest, latest TWRP and that fixed the issue. Now to flash the ROM.....