Thought I backed up original ROM, when I opened the file today it was blank (NVFLASH).
I did copy the internal sd and have a copy of that but its not the right file type.
I also have some image files of the ROM, can I use either of these?
How about a little more information.... what file did you open that was blank?
Do you have files that look like 09_APP_raw.img? Did you use a script or just type a bunch of stuff in at the command line?
How did you copy the internal SD card that it is not the right file type?
What are these image files of the ROM?
So many questions...
The way I copied the internal sd was in the file manager, had to click show hidden files to do it.
The blank file was a file that brk asus transformer root toolkit made. Went to do a restore with it the next day and file not found,
The image files I have are ones that another version cwm m ade doing a backup a few times that I got from the market. But that version of cwm doesnt support asus.
OK- it that helps. If you just want the stock firmware, you can get that from the ASUS website. You might have to get the 8.6.5.9 version and then upgrade to 8.6.5.13 via the ota. From there you can root again and/or install CWM if you want.
There are TF specific versions of CWM- solarnz and roach each have a version in the dev section. These might allow you to flash the data partition from your backups to restore any apps that you installed. I think brk's tool uses one of the modded versions of CWM.
As far as the internal sd card, you might have to copy those over with an external SD card/adb/ftp/etc.
If you want to restore one of the CMW images you have, that might be tricky, but you can extract them with the unyaffs tool. Google should find it for you. They might be flashable with one of the modded versions of CWM, but I think the modded versions have a slight difference in the parts that they backup/restore. You can try the "advanced restore" option to restore the data.img, but I'm not sure what would happen.
I looked at asus website for the rom, all I found were firmware and kernels are those the roms? I would prefer doing it that way.
Yup- select the android OS and pick your country specific firmware (aka ROM).
It might be tricky if you are downgrading I.e., you flashed 8.6.5.13 and want to flash the stock 8.6.5.9 firmware. I'm not sure if you can downgrade the "easy" way.
The easy way is to unzip the firmware and place the whole ASUS folder on your external SD card. Turn on the TF and insert the SD card when it is running- a notification should pop up to flash. ASUS has some documentation with pictures in the Manuals section. Look for one of the "Update SOP" files.
Let me know if that works. I've never tried to downgrade that way, so I'm not sure if it will work because you might be on a higher build number. If it doesn't, there is another way if you are rooted or you can use nvflash.
Let me get this right, do I use the firmwaree or the kernel.
Use the firmware.
Thanks, I reread the firmware aka rom. I'm in the us so the us one right! Will let you know if it works, says something about downgrading in there...
If it won't let you downgrade, then you have to do it the "hard" way.... but you have to be rooted.
Download the firmware and unzip it. It should be something like ASUS/Update/some.zip
Unzip the some.zip file and it'll contain a blob. Copy the blob to your external sd card or use adb to push it to your TF.
It would be a good idea to verify the MD5 sum of the blob. The US one that I downloaded for 8.6.5.9 is
MD5(blob)= 57d4c4342277d39e523e26b943891a1f
Use terminal on the TF or adb shell from your PC and type the following:
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
the last three characters are zero-pee-four. It's important to get this right or you could mess up your TF.
If you copied it somewhere else, then adjust the /Removable/MicroSD/blob part.
It will take a while because it's a big file, but when it's done, type "reboot" or just turn off, then turn on your TF, and it will flash you back to stock. You should see a blue progress bar that moves very slowly. Be patient, it takes a while and should reboot when it's done. You will be unrooted with a stock recovery at this point.
Afterwards, you can verify that you have the downgraded firmware and then check updates to receive the OTA to upgrade to 8.6.5.13. Lastly, clean up and remove the blob file from your sdcard- it's 521MB!
Your awsome man! You took all that time to help me out and I won't forget it gee!
So did the downgrade work, or did you have to flash the blob?
Not gonna try tonight, thats how I lost the backup as I was tired... Will try tomorrow and will let you know what workes.
I have prime on here now so I dont think that would technically be a downgrade?
Yes I am rooted.
So while I have you, will a rooted machine get OTA updates?
Yup, the updates still download, but they usually break root or won't flash because something is not stock, such as kernels.
Of course, you can mod them so they flash and keep root.
Good idea about starting fresh tomorrow.
r u Randal in Ca?
No, sorry.
No worries, just reminded me of the big guy. Will let you know how everything goes. I try to be sure before I comet to a change I can't recover from so will have to sus up everything first.
I want to thank you again for the help, I hope you get compensated for it?
Hardy har har, and I'm still in thi situation!
We will see tomorrow!
Related
This is the Stock 8.6.5.13 US update repackaged with:
* Clockworkmod support (It does not include CWM, but doesn't reflash the recovery partition either)
* Rooted (includes SuperUser.apk & su 3.0.0)
* Busybox (1.19.2)
This update worked fine on my TF101. I built it using the same method Roach2010 used to make his previous CWM-repacks so it should be ok. I have only tested this on my own tf101. Let us know when it works for yours too!
This will not work unless you have:
1. clockworkmod
2. STOCK firmware (root is fine)
3. the US or WW firmware
4. firmware 8.6.5.9
If this update will not apply, take note of which assert stopped the process. You probably applied some sort of mod to your transformer.
There was an issue in the initial release. If you downloaded it, delete it and download the new one.
CWM package for ASUS FOTA Update 8.6.5.13 US
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-proper.zip
Problems updating? Customized Transformer? Try the Update checker.
http://bellybuttonporn.com/android/transformer/kwt-cwm-8.6.5.13-checker.zip US
The Update checker will verify all of the same files that the update verifies. It will not stop on the first error. This way, you can see ALL the files which will cause errors and fix them all at once without the tedious reboot / try update / reboot / fix problem / reboot / try update loop.
Courtesy of brk:
CWM package for ASUS FOTA Update 8.6.5.13 WW (with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
Has this been tested yet??
Thanks
*Offtopic*
delete ffs
same here, stock but with xoom system UI and bloatware deleted.
Sorry, in my haste I didn't update the recovery binary.
Fixed version in testing now.
Updated first post, new zip is available here:
http://bellybuttonporn.com/transformer/kwt-cwm-8.6.5.13-proper.zip
cky2000 said:
for me, it did not work.
I tried from a fresh/clean install (nvflash) of US_epad-user-8.6.5.9. and got this error in CWM:
assert fail: getprop ("ro.product.device") == "EeePad" || getprop ("ro.product.device") "EeePad"
E:Error in /sdcard/kwt-cwm-8.6.13.zip
(Status 7)
Installation aborted.
bellybuttonporn
Click to expand...
Click to collapse
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Cordy said:
Seems you didn't edit the update-script to remove that check. Either way let me know how it goes. I made myself an cwm zip that I used to update my TF this afternoon. I didn't bother to add in SU seeing as though the update is just a patch and the TF should already be rooted.
@daoist If your new update.zip doesn't work let me know I'll upload mines and you can post it.
Click to expand...
Click to collapse
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Xerravon said:
Hi,
I am still pretty new to all of this, I have rooted my TF, right now I have a US ver 8.6.5.9 rooted with CWM and I am getting the notification to update firmware.
Is this the file I need to update my TF and keep root, it looks to me like it is but I am not 100% sure, also I am not sure how to apply the patch.
To apply this do I use CWM? The step[s I think I need to do is
1. copy the file top my SD card,
2. Boot to CWM
3. choose install zip
4. pick the zip downloaded from this thread
5. then watch and make sure works, then reboot
OH, I have the netflix patch (libnvomx) file copied over the original in my TF, should I put the original back before trying ng this?
Is this correct?
thanks for any help and the file!!
John
Click to expand...
Click to collapse
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
ryan stewart said:
You referring to the check that goes through and looks for mods and missing apps? Is it possible someone could upload a version that doesnt run that check? I replaced SustemUI and basically deleted everything I didnt need (and didnt back up individual files, just made a full backup) so it would take me a while to track down all of the APKs.
If I recall someone posted the .9 update without the check for the existing apps.
EDIT: I actually found a backup for my stock apps and copied all of them back over and its still failing. AWS.odex, first one (and its installed).
Click to expand...
Click to collapse
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
The issue is I have it back on my device, I found it, and the update is still hanging on that.
daoist said:
Yep, that's correct.
One note is because of how the TF handles storage, you want this in your /Removable/microSD. If you put it in /sdcard it's not actually in your sdcard.
When you reboot into CWM make sure to choose to pick a file from your sdcard, rather than just applying update.zip (in case you didn't actually name it update.zip)
Click to expand...
Click to collapse
Hi,
Thanks for the help! It worked like a charm, no problems at all.
I am wondering now, do I need to update my CWM recovery, or do I just leave it how it is?
thanks for the file and help!!!
Now I just have to figure out how to get rid of the notification...
Has anyone noticed the web browser performance? Is it still checkerboard on display? Where it displays the page in chunks... and is this android 3.2.1? or just firmware update?
Worked fine on mine, Thx.
daoist said:
The problem with removing the check is that this update is doing patching, rather than replacing files.
If you're just replacing files, you can skip the checks and it will work fine.
If you're patching files, if you skip the check, the patching process will not work (best case scenario). will leave your system in a quasi-updated state (middle case), or destroy the target file (worst case).
Maybe someone who's still on 8.5.6.9 can post their AWS.odex file for you to copy onto your device?
Click to expand...
Click to collapse
Would it be possible to remove the check and the patch? I am looking at the updater script, what I would love is to just remove its check and attempt at patching the bloatware.
For Example, the Check:
assert(apply_patch_check("/system/app/Finsky.apk", "19a70336522820f20a9e1d9f065ae56a714aa7cf", "690dc80af4303cb2df1991de9d52c269211e1dcf"));
set_progress(0.116486);
assert(apply_patch_check("/system/app/Finsky.odex", "fda5fbff54fc6c35b9210afd4a3b76b6a8862d83", "59412510a7d0a789b1e732dbffdc9feb3245e964"));
set_progress(0.119390);
And the Update:
apply_patch("/system/app/Finsky.apk", "-",
19a70336522820f20a9e1d9f065ae56a714aa7cf, 1070527,
690dc80af4303cb2df1991de9d52c269211e1dcf, package_extract_file("patch/system/app/Finsky.apk.p"));
set_progress(0.135043);
apply_patch("/system/app/Finsky.odex", "-",
fda5fbff54fc6c35b9210afd4a3b76b6a8862d83, 655760,
59412510a7d0a789b1e732dbffdc9feb3245e964, package_extract_file("patch/system/app/Finsky.odex.p"));
set_progress(0.138224);
If I didnt want it to update finksy (bad example but just one I grabbed) could I just delete everything above from the script? In the case of something like Zinio I dont even want the update since I nixed the underlying app.
I actually tried something like that but it failed immediately, no error. Im wondering if I havent zipped it up right.
Yeah, if you search through the update script for the name of the file that's erroring out, there's 2 places. First the assert, then the patch. Get rid of both and you're fine.
I'd google what those files are before you remove them from the script, just to be safe.
Just for example, Finsky is part of Market
Im wondering if there is something I am doing wrong or if there is a trick to zipping it back up. I tried removing those lines (for AWS, not Finsky ) and the update failed without an error (just aborted).
Im wondering, should I be leaving that set progress, zipping using a particular method?
The biggest problem I had was making sure the files were saved with unix line-endings. If you edited it in notepad or something like that it may have defaulted to windows line-endings.
Hi can you add this to 1st post:
CWM package for ASUS FOTA Update 8.6.5.13 WW
(with root and CWM recovery)
http://www.multiupload.com/KTGLKFJME5
If it gives you an error about some file check, edit update script and put a "#" before the line of that file.
I have an HTC sensation z7z10a. I purchased this phone to be able to get on AT&T's 3&4g frequencies without having to upgrade my unlimited data plan for non smart phones. So far so good, my phone gets 4g and AT$T is not aware that I have a smartphone.
Naturally after spending enough time in XDA and other phone forums to figure this out I became interested in flashing a custom ROM.
I used the revolutionary method to gain S-OFF, installed CWM, and used CWM to create a backup image. I've managed to fully wipe and then restore to my backup image, so CWM is working.
My problem is whenever I go to flash a custom rom I don't understand which file to select in recovery mode. Every zip I have downloaded, (including the one I need to finally get my phone rooted) opens up to a series of subfolders, none of which contain the files I need. The sub folders are typically : System, Data and META-INF. So I can't get rooted without being able to use the recovery mode to flash.
I used my friend's pc netbook in order to run Revolutionary and install CWM. Now I am using my Macbook Pro to download potential Roms zip files and move them onto my phones SD card. Could this be the problem?
I"ve searched and searched for and answer to this issue to no avail, please help me to figure this out. I'm stumped.
The zip you have to flash is the ROM you download...am I missing something?
You do not need to extract the zip file. Just put it on the SD card and then go to the recovery mode and select the option install zip from sd card and install it. I believe if you flash a custom rom, you would be automatically rooted, so no need to root it separately. Hope this helped
aNYthing24 said:
The zip you have to flash is the ROM you download...am I missing something?
Click to expand...
Click to collapse
Exactly- I don't understand why it won't work.
SickL1408 said:
You do not need to extract the zip file. Just put it on the SD card and then go to the recovery mode and select the option install zip from sd card and install it. I believe if you flash a custom rom, you would be automatically rooted, so no need to root it separately. Hope this helped
Click to expand...
Click to collapse
Thanks for this advice, this is my first time attempting this. I think you are right that most roms come with root access so I may be able to skip that step.
I know what you are saying, don't extract the file, just move the zip over as is. Only on my mac the files are arriving as a folder with subfolders, not a zip package. This HAS to be the problem! I will look harder for Mac info on downloaded zips to see if I can figure out why this is happening. Thanks again.
Update:
So I fixed the folder problem by going into safari settings and unchecking the open safe downloads box. No all the zip files I'm downloading are staying intact as zips.
However I just tried to flash revolution hd with no success. The full wipe zip for this rom was a failure as well. I will now try downloading the root zip again and see if rooting first helps at all.
So now I am rooted. Success!
imru88 said:
Update:
So I fixed the folder problem by going into safari settings and unchecking the open safe downloads box. No all the zip files I'm downloading are staying intact as zips.
However I just tried to flash revolution hd with no success. The full wipe zip for this rom was a failure as well. I will now try downloading the root zip again and see if rooting first helps at all.
Click to expand...
Click to collapse
Ah....Steve Jobs and his desire to prevent the user from doing anything useful strikes from beyond the grave.
This is why I won't touch a Mac. They want to do everything for you, even if it's not what you want or need to be done. On the plus side, at least you only have to push 1 button to get the Mac to do the wrong thing!
Glad you figured it out! Be careful with the ROM flashing though. It quickly becomes a life consuming obsession.
So my sister just bought a Transformer tonight, It has never been rooted or anything.
It will not detect any updates on the "search for update" OTA thing.
I also downloaded the ICS firmware directly from Asus's website, extracted it on a microSD card, and the trasnformer still doesnt show theres any update.
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
No idea whats going on.
Any help is appreciated.
Did you unzipped the file you download from Asus website? You can't leave it whole, there's another zip inside that zip.
Yep I followed all the instructions
Bawb3 said:
In the manual update guide it says put the extracted ASUS folder on the SD card, however there is no ASUS folder in the update downloaded from their site.
Click to expand...
Click to collapse
Reading that gives me the feeling that you probably didn't do it right. There is no reason it won't work.
Can you post the EXACT steps you took?
I'm having the same issue
There is no ASUS directory in the zip.
Inside the second zip there is a file called blob and a directory called Meta-Inf with a bunch if files in.
Okay, I go to asus's tf101 site, download sectiion > firmware.
Download the US SKU 4.0.3 firmware update which is ~300mb
Extract that zip which yields a file with another ZIP inside of it. There is no ASUS folder.
Like the above poster said, the second zip file looks like a recovery update script that you would flash in CWM with a meta-inf with the signatures, and a blob file.
EDIT[SOLVED]:
Okay I figured it out. I downloaded the 3.2.1 update from asus, which does have the ASUS folder. This one worked and launched the update wizard.
It seems that the update wizard looks for the directory /ASUS/Update/US_epad-user-x.x.x.xx.zip file on the root of the microSd card.
So I put the ICS update which is US_epad-user-9.2.1.11.zip into the ASUS/Update/ Directory in the microSD card that I initially extracted from the 3.2 update. Sure it enough it launched the update wizard and allowed me to select that file for the update.
ASUS Didnt properly upload the ICS update it seems.
I still dont know why the OTA didnt acknowledge an update.
OK, this is just getting dumb now.
OK, this is just getting really really stupid now. ASUS I AM SERIOUSLY STARTING TO HATE YOU.
OK I have done the following across MULTIPLE reboots and really getting ticked off now. This would NOT be an issue if the recovery mode didn't give me a damned green droid with yellow triangle with ! in the middle of it.
I have:
Way 1
-------
1 - Extracted WW_epad-user-9.2.1.11.zip from the original WW_epaduser9_2_1_11UpdateLauncher.zip from ASUS site.
2 - Copied extracted WW_epad-user-9.2.1.11.zip to EP101_SDUPDATE.zip
3 - Put both zips on root of microSD. Failed. Tried with copy on /sdcard/ as well, both with and without leaving the original 2 on the microSD.
Way 2
-------
Extracted the WW zip both to the / of the tablet and to the root of the microSD, trying both with and without leaving the originals on the microSD.
Way 3
-------
Same exact as Way 1 and Way 2 but with removing the .zip extension from both files, and with swapping removal of the extension between the 2 files on both the tablet and the microSD.
Way 4
-------
Tried all permutations of Way 1, 2, and 3 with both 8.6.5.21 and 8.6.6.21.
NONE of these ways worked.
I grabbed NVFLASH with 8.6.5.13 and that flashed just fine, except that the recovery mode is still giving me the triangular ! droid image.
I absolutely positively can not root or otherwise do anything to this tablet.
The tablet is a ASUS 32GB Transformer HD Tablet (Serial #: B50KAS#####) with a 2GB microSD formatted with FAT32. (I've tried formatting NTFS and FAT32) This is not a Prime! This is the original Transformer!
I even found an article for how to create your own and tried that as well!.
(Wow really guys? You can't post outside links?? Really? What the heck is that retardation supposed to prevent? I mean really!)
All I get for that mess is the USB connection is dropped even before NVFLASH can do anything. I have Windows 7 Ultimate, Mac OS X Lion, and several distributions of Linux (ArchLinux, Ubuntu, CentOS, Debian, and OpenSUSE). I've tried on them all!! This has been a great many hours trying to figure this out, searching like crazy through these forums. (Incidently, the 10 posts requirement in order to post in the 'experienced' area is just nuts.)
I even tried both the renaming WW portion of the zip name to US as described in other areas in this forum and it still failed! I'm a programmer by trade, and I have never run up against something as stubborn as this! The recovery mode is what is breaking all of this. I absolutely can not get a stable, working recovery mode on this tablet! Heck, I'd be happy with the stock 8.6.5.21 on here or ICS (the 9.2.1.11) without ever again attempting to root the pup! Can anyone assist in getting the recovery mode back to normal? Is there a way to use NVFLASH to write the original recovery mode back such that I stop getting that dang Droid With Yellow ! Triangle image?
Do you have CWM Recovery installed? If so, it will not do the OTA updates, but you can just go into CWM Recovery and then choose the 9.2.1.11 firmware and when it is done flashing, you will have an unrooted stock ICS (with stock recovery).
CWM
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
deryldoucette said:
Unable to root. RazorClaw tells me I'm missing the required file (though it doesn't tell me what file that its) and says Too bad!
Click to expand...
Click to collapse
Razorclaw only works on 8.6.5.19.
Not certain on which version you try to run razorclaw.
use Vipermod on 8.6.5.21 or higher.
was 8.6.5.13 which is what i was able to nvflash back to the tablet. Do you know if there is a more recent nvflash packaged 8.6? Looking to see if I can at least put 8.6.5.21 on here. Currently still running the 8.6.5.13
Mine also wont OTA, i have put the downloads in ASUS/Update and nothing... does not detect updates.
Just bought my tf101 yesterday, same problem. Called support and they told me the update was not pushed to my device yet and a manual update would probably fail.how long ago was ics released?
found it, february 24th... It should be pushed to my device by now, right?
Sent from my SPH-D700 using XDA
G'day guys,
I finally managed to get it to work for me!
TLDR Version - I have the US build version - this may or may not be relevant to these instructions:
* Use "App Backup" to backup all your apps and/or data (optional)
* Factory reset
* Choose "English (US)" from the initial setup wizard and default options for the rest (skip wifi setup)
* Plug the transformer in to your PC via USB
* Create the following folder structure exactly (including case!)
<Internal Storage>\ASUS\Update
* Copy US_epad-user-9.2.1.11.zip that you extracted from US_epaduser9_2_1_11UpdateLauncher.zip to "<Internal Storage>\ASUS\Update"
* Reboot Transformer
* Choose the triangle from the notification area
* TF should update successfully!
Long version:
I followed the instructions in this thread but still wasn't having any luck.
I don't have an external SD card so I was copying the zip from the downloaded file to internal storage\Asus\Update. The triangle was appearing in the bottom right but when I went to do the update it would reboot to the android man with an "!" on his chest. I then tried a factory reset and then recopied the update and tried again. Same "!" dude. I tried another reset but did two things different and it then worked! Instead of choosing "English (UK)" on the initial setup wizard (I'm from Aus) I chose "English (US)" (just a wild guess given its US update required for my TF. The other thing that I did differently was located the update at "ASUS\Update". Note the capitalisation of "ASUS" where previously I was using Asus. I had this idea when I noticed the first time I had both "Asus" and "ASUS" folders there simulataneously. So one or both of those things made it work for me!
If these tips worked for you please post your success (or otherwise even).
Best of luck!
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
As we now have functional recovery options on our tablets, and people will inevitably mess things up with their device, we need to get a way to get your tablets back to factory condition. But I need your help with this!
What do you want?
Here's my idea: We have all seen various ZIPs floating around, most of them leaked from somewhere. The problem with these is that you can't use OTA updates, and I'm not sure what Acer Service Center thinks of custom ROM installs. What I want is to build a list of software that is officially distributed by Acer, is OTA-updateable, etc. For this reason, I want people that have not yet modified their tablets (except root) to provide image dumps of their /system, /boot, /flexrom, and /recovery partition. It's really easy to do, and you'll help yourself and others when they get into trouble.
Can I help?
Answer all of the following questions. If at one point the answer is "Sorry, you can't help", well... You can't help
Is your device unlocked and rooted? Yes - You can help! / No - You can still help, but you need to unlock and root your device.
Do you have the original Acer ROM installed on your device? Yes - You can help! / No - Sorry, you can't help
Have you received the latest OTA updates for your device? Yes - You can help! / No - You can help as well!
Have you removed any apps or files from the /system or /flexrom partition? Yes - Sorry, you can't help / No - You can help!
Have you installed a custom recovery image? Yes - You can still help, as long as everything else is still original / No - You can help!
Okay, so I can help, now what?
If you can and are willing to help (remember, it could save your own ass one day), follow the instructions below. If you get stuck or simply don't know where to start but are willing to help, let us know in this thread and I'm sure we can all help eachother out.
This will not gather any personal data from you. Personal data is stored on the /data partition, which we don't need, so: No worries!
Root your device, if you haven't already.
Connect your tablet to your computer via ADB
Type the following command: adb shell. You are now logged into your tablet. You can exit at any time by typing exit and hitting ENTER.
Type the following command: dd if=/dev/block/mmcblk0p2 of=/sdcard/boot.img. This will copy your /boot partition to a file called boot.img on your internal storage. This one will be fast, it only has about 8MB to copy.
This step can be skipped if you have a custom recovery! Type the following command: dd if=/dev/block/mmcblk0p1 of=/sdcard/recovery.img. This will copy your /recovery partition to a file called recovery.img on your internal storage. This one will be fast as well, it only has about 6MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img. This will copy your /system partition to a file called system.img on your internal storage. This one will take a bit longer, it has about 360MB to copy.
Type the following command: dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img. This will copy your /flexrom partition to a file called flexrom.img on your internal storage. This one will take a bit longer as well, it has about 360MB to copy.
Type exit to exit the ADB shell. Copy the four .img files from your tablet (internal storage) to your computer. You might have to reboot your tablet if the files don't show up.
ZIP or RAR these files, and upload them somewhere. If you can't find a place to store them: send me a private message or reply in this thread and we'll arrange something else. If you have uploaded the files somewhere: again, send me a private message or reply in this thread.
So now what?
When I receive your files, I will package them into an update.zip that can be flashed from custom recoveries. This will then restore everything (including the custom recovery) to factory state, which can help you in getting your device back to stock.
What versions do you have already?
Acer_AV041_A510_1.044.00_WW_GEN1 (download links will follow shortly)
Acer_AV041_A510_1.098.00_EMEA_CUS1 (download links will follow shortly)
Acer_AV041_A510_1.099.00_EMEA_DE (download links will follow shortly)
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
scorpio16v said:
The idea sounds great so far. But I have a small problem to make a complete backup for my a511.
Your linked root tutorial for the procedure is only for a100/a510 and doesn't work for a511, as I understand.
The tutorial for rooting the a511 needs first to flash a CWM.
http://forum.xda-developers.com/showthread.php?t=1729432
So it isn't possible for us to backup the recovery partition, right ?
I have the stock Acer_AV041_511_1.028.00_EMEA_DE on my device.
Is it even possible to backup and recover the baseband ?
I'm very interested in your CWM recovery for a511 too, but since many guys f++++d up their device now, I want to make sure that my device will not goes the same way.
Click to expand...
Click to collapse
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
scae said:
What about if we have removed system apps (such as the antivirus that comes with the tablet). It wouldn't be a complete dump if it didn't include those.
I have root and am happy to provide a dump, but I did uninstall several of the crappier pre-installed apps that came with my tablet.
Click to expand...
Click to collapse
Then it's of no use, unless you have a backup of your pre-installed apps. Removing apps from the /system or /flexrom partition is not recommended, and you gain nothing by it: You only gain space on read-only filesystems which you won't use in 99% of situations, and you've now broken OTA's for yourself as well, as OTA's will only install when apps are present unless you start modifying OTA files.
The 'correct' way to get rid of pre-installed apps is simply freezing them, either from the settings menu or with an app like Titanium Backup. This will make it seem like they're not there (so they don't use resources at all), but the APKs don't get removed.
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
skymario said:
i can help, n my tab is rooted.
but i don understand the first step: Connect your tablet to your computer via ADB
Click to expand...
Click to collapse
Do you have ADB or the Android SDK installed?
NoThrills said:
Do you have ADB or the Android SDK installed?
Click to expand...
Click to collapse
I just learned ADB, n successful install ur CWM, later will try to dump my stock Rom to u.
My stock Rom version 1.073 ww gen1
does it matter if the system apps have been frozen or do they need to be unfrozen first?
I have flashed that remove stock recovery mod so the stock rom doesn't keep overwriting cwm on reboot. Does that disqualify me? If not I'll dump my rom for you when I get home.
I'm on this rom version:
ro.build.pandora.id=Acer_AV041_A510_RV28RC04_PA_CUS1
ro.build.flexrom.id=Acer_AV041_A510_1.076.00_PA_CUS1
I unlocked bootloader,rooted,installed cwm then backed up my stock rom.Could i restore my stock rom then be able to send you those fills
and return to total stock.
NoThrills said:
Hi, your device will not brick, I can send you a test A511 recovery if you want. Worst that can happen is that recovery won't boot, but in that case you can simply put back recovery. Send me a private message and we can work something out.
Click to expand...
Click to collapse
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
i have a a511 too with Acer_AV041_A511_1.028.00.EMEA_DE and can help with testing or something else
I have Acer AV041_A510_1.079.00_PA_CA. (Canada)
I have not done a thing to it because it is a replacement for the Galaxy Note I bricked trying to upgrade from GB to ICS, too early.
I might try again if I was sure I could get back to where I am, using your process.
I assume that your Root link is comprehensive but I also need reassurance on how to ADB.
[email protected]
Sent from my A510
blgblade said:
i think he mean that the a511 recovery doesn't work properly....you can flash a zip, but nearly all other options brick the device
Click to expand...
Click to collapse
No, as I understand, the only working methode to root the a511 is to bootloader unlock, flash the custom recovery and then the root.zip.
Maybe I'm wrong and there is another working way to root the device ?
The problem is simply, that we lost the stock recovery before we have a backup from it.
If we have another root way for a511, the backup of stock firmware is done in a few minutes and from this point we can test the a511 custom recovery from NoThrills.
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
In theory: To test, one could simply overwrite the stock recovery with my Recovery (not the other ones, they will brick your device) and then when you reboot, your device will overwrite the recovery with the stock one again. So you really don't need a backup of the recovery partition.
As long as you don't let your device fully boot (so, stay in recovery) there's plenty of time to test if the recovery works or not. If it doesn't, simply reset your device and it will flash back the original recovery (again: provided there is a install-recovery.sh in your /system partition).
So again, if anyone is willing to test, let me know
NoThrills said:
To the A511 owners: Technically, if you have a install-recovery.sh file on your device, the device will always flash recovery back from the boot.img.
Click to expand...
Click to collapse
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
NoThrills said:
So unfortunately, we can't use your dumps to restore devices to factory state. Unless, ofcourse, you've made a backup of the apps somewhere.
Click to expand...
Click to collapse
Ah damn, I did back them up via titanium but it doesn't seem to want to restore them - it just sits there say restoring app.
scorpio16v said:
I can't find a install-recovery.sh in /system partition on my a511. Search on root-explorer can't find one on the device.
Even NOT on /system/etc like on other devices.
Click to expand...
Click to collapse
Yeah, I meant /system/etc... That's weird, I'd figure Acer would use the same system on the A511... Let me check one of the leaked ROMs...
Hello,
I have an stock Acer_AV041_A510_1.098.00_EMEA_CUS1, there we go for the files
Host file is not the stock version, it was edited by AdAway.
Can you make a version without recovery overwritting ?
I thinks a lot of people want to try some roms... just for testing...
Acer_AV041_A510_1.098.00_EMEA_CUS1 boot && system && flexroom:
http :// dl.free.fr/jDEmTNSD4
Have Fun
Hello,
I have the same rom without root or unlocked bootloader or moded recovery so if the above on does not make it I'll upload mine.
Sent from my A510 using xda app-developers app