Related
How to get back to RC29? by modifying the update script?
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
assert getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,release-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC29/115247:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC28/114235:user/ota-rel-keys,test-keys"
|| getprop("ro.build.fingerprint") == "tmobile/kila/dream/trout:1.0/TC4-RC19/109652:user/ota-rel-keys,test-keys"
Click to expand...
Click to collapse
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
fluke.l said:
I' chose to update to RC30 while didn't know that update fixed up the permission problem.
I wanted to roll back to RC29 then I tried to do update to the RC29 package.
Failed at the first line of update script:
I'm gonna try to append one condition to this line: "|| 1"
But is there any side effect by doing this?
And, I don't know if this will work, since I don't quite know the update package's format.
I think is kind of sun's jar file, and plus a update script in META-INF folder, two cert files(one of this also keeps the sha1 of the manifest file's sha1sum).
Can someone give me some advice?
Click to expand...
Click to collapse
As soon as you change one byte in the update.zip folder, the update won't verify against the signature, and will fail.
I've tried.
How did you modify the update.zip?
Did you package it in jar way -- which will count the sha1sum of each file and put into MANIFEST.MF?
How do the phone verify the update.zip? by cert files or just check the sha1sum?
Question: what happens, if I try to apply rc29 from SD card (i.e. signed-kila-ota-115247-prereq.TC4-RC19_RC28) after getting RC30 OTA on my G1?
1. update fails
2. update bricks the phone
3. I can have my root back
Does the name _really_ mean that TC4-RC19 is the only thing it will install over?
What checks are actually made before it bootstraps a SD card update.zip?
Can someone comment on the likely result before I get impatient and discover it is #2, please
Doesn't work but doesn't brick
I just tried it. The update will fail, but you won't brick the phone.
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
dagentooboy said:
this may be a dumb question but why can't the modded RC30 update just be signed with the OTA keys and then used as an update.zip from the SD card?
Click to expand...
Click to collapse
Because only {Google,T- Mobile,HTC} have the OTA private keys needed for creating an OTA signed file.
I guess the only hope is google/t-mobile releasing a full update
Downgrade from RC30 to RC29
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Nice to know. Thanks
so if i let it reboot after it installed the update than im pretty much screwed for now?
ChrisAshton84 said:
I have been reading up on the modded RC30 and haven't seen anyone mention this, so here it goes:
My phone had been taking forever to get OTA updates - I didn't get any notifications until the 11th. I wanted to keep root access so I never applied it, but downloaded the RC29 update and installed that manually. I was planning on updating to the modded RC30 once I had some free time. This morning I accidentally allowed the OTA update - damn thing popped up as I was clicking something else. I figured I was stuck with the official RC30 update.
At the end of the first part of the update it gives you the normal recovery prompt - reboot, install update from sdcard, or show/hide text, so I figured I'd try to install RC29 over RC30 (even though I'd heard it's impossible). It worked! I guess until the phone has fully installed the update, you can re-flash whatever update you have on the card. This probably won't help too many people, but if you accidentally allow the OTA update like I did and still have an update on the card this could save you!
Click to expand...
Click to collapse
U Said your Phone taking foreever to get Update
This means you must be on RC19 and phone was trying to get Full RC30 from google.
Becuase of Full update it paused some where and ask you to reboot, Becuase Patch RC30 Update dont ask for it.
Please Explain you Full Situation !!
yup i got stuck with the RC30 update about an hour ago. was dialing a number and it popped up and i accidentally pressed update now! it bites, oh well
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
I'm mad that I didn't decline the update to rc30!!!!!!!
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
Thanks for your reply
hmm, possible reasons
it seems to me (very close to a complete moron) that the updates get copied to a "ramdisk"(4 lack of a better term) then when you see that arrow going into the chip after reboot is when its written from this "ramdisc" to the flash?
maybe its just the hash talkin take it for what it is an educated guess... AKA a theory.
bhang
ChrisAshton84 said:
I had a great reply written up but the server timed out and lost it :-/
Basically:
I had RC19. I got a system update prompt on the 11th, which led me to think it was the RC30 update. Not wanting it, and not having time to do the modded RC30 update, I installed RC29 via update.zip on my sdcard.
After the update to RC29, I kept getting the update prompt, further leading me to believe it was RC30. I tried to avoid the update but accidentally approved it, since the update screen can pop up at any time.
After the update was unpacked & verified, it prompted me to reboot, install from the sdcard, or hide the text (I may have hit ALT+L or whatever to show the text during the update, I can't remember). Given the option, I chose to install from the sdcard.
It went through a few steps (fewer then the initial unpack, oddly) and again had me reboot. I did, it did went through the update reboots, and when I got back to the system it was RC29. I'm still getting prompts to update, so I still think the update was to RC30 then reversed to RC29, but there's a chance I'm wrong and haven't done anything unusual here.
Short version: If you don't want the official RC30 but don't have time to install the mod, just keep RC29's update.zip on your sdcard. Even if you accidentally approve the install this will let you revert to RC29.
Click to expand...
Click to collapse
great tip this is bound to help many others, anybody by any chance know when the next update is coming out?
I tried to Simulate Same thing
1. I already had Updated the phone to Stock RC30 and
2. I Copied RC30 on to SDCard as update.zip
3. Started into Recovery Modem and Pressed ALT+S
4. The Phone Started Verifying the File
5. Then i have Format Boot, System Partition
6. Copied some thing to Phone and asked me to Press Home+Back
7. I pressed it and its flahed Radio Image and reboot in recovery ode twice and did something.
In your Case the Phone might have Extracted the Images into Ramdisk but it might didnt flashed it to phone really and between that u got that Reboot Option and Reflashed the Full RC29 again.
We can reflash the same Version as many time we like but we can not flash lower version as the Recovery command dont allow.
If we keep RC30 as Update and remove the SDCard in between and put a new Card with Update.zip of RC29 the phone unmount the SDCard and then it dont detects the new SDCard is inserted and flashes error so Simulating your Process by Swapping 2 SDcard with RC30 and later on RC29 dont work for me.
If i could place RC30 into Phone and then Try to Simulate that it got the RC30 update frmo Internet and in between flash it with RC29 from SDcard might help me. But i am still not sure.
Downgrade from official RC30 to RC29 ?
My try to change some file on my system then my font was brick . But I use recovery mode, update to official RC30 then I phone worked again. But I want to acess my phone again. Please tell me how to downgrade to RC29 from official RC30 ?
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 posted this elsewhere, but in the spirit of sharing I figured it might be of some use to folks if I posted it here as well. I decided I would take a crack at doing something more productive than uber-long overly detailed how-to posts (like here for example), so I sat down and attempted to figure out how to make the latest EP4P leak into a CWM-flashable form (thanks to hoppermi for putting the idea in my head).
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE! As an additional disclaimer - this is an early attempt at utilizing things I just recently learned. It has worked for me and a few others that were kind enough to try, but as always YMMV.
This is all pulled from either the full factory stock unrooted .tar file or the debloated .tar file, both of which I downloaded from here. I then pulled out the system and kernel stuffs, deodexed and zipaligned (the stock unrooted one, as the debloated one was already deodexed), added in/changed busybox (from here), and added in superuser/su (the latter just for the stock unrooted). I also added back in the Task Manager to the debloated version (a number of folks requested it). Truth be told, all of this was done just to see if I could do it. Now that it's done (and I have successfully used both of these to get to EP4P from stock unrooted EE4), I figured I would share them.
BEFORE flashing, MAKE SURE voodoo lagfix is completely disabled (i.e. /data, /dbdata, /cache, and /system all need to be rfs, NOT ext4). You will also need to have CWM (version 4.0.1.4 can be found here) already on your phone, and I would strongly recommend doing a data wipe/factory reset within CWM before flashing as well (that's what I've been doing at least and I have had no problems).
Installation instructions:
- Download file and place on sdcard
- Boot into CWM recovery
- Wipe data/factory reset (Recommended)
- Install the .zip you put on your sdcard
NOTES:
Flashing this should not do anything to the CWM recovery you used to flash (i.e. your recovery won't be overwritten by stock kernel/recovery). That being said, I have encountered an occasional odd issue with CWM after flashing that seems to require adb to resolve. The issue may stem from the stock kernel, or perhaps how one enters into CWM - but I'm just guessing at this point, and it likely is something completely different. Regardless, it happens from time to time...
The issue is that after flashing and then booting into recovery, I occasionally get a "can't mount /sdcard" error. Apparently that in itself is a known issue, and it is listed as such in the CWM recovery thread - which incidentally contains the 4.0.1.4 CWM version I have been using.
The fix requires you to perform the following commands using ADB:
Code:
adb shell
umount /sdcard
rm -f /sdcard
mkdir /sdcard
exit
If you do not have ADB installed and you are having the "can't mount /sdcard" error after flashing - I think I have a workaround for you (thanks bL33d for the suggestion). Download the ADBsdcardFix.zip here - then extract the folder (should be fine to extract it to your desktop) and attach your phone to the computer via USB (I did this while the phone was already in CWM). Open the newly-extracted ADB folder, and then double-click on the CWMsdcardFix.bat - something should pop up on the screen for a brief second, which is completely normal. After double-clicking the .bat file, on the phone go to mounts and storage, then select mount /sdcard - and it now should work!
Either approach here (adb code or the stuff in ADBsdcardFix.zip) has worked every time I have needed it, although again in my experience I have not been able to cull the rhyme or reason out of when that need will present itself.
For those who dabble in ADB, I noticed that adb shell seems to work "differently" on these CWM versions of the EP4P leak. Normally entering adb shell would lead to a # prompt, but with both versions here it stayed as $ - however, if you then enter su it goes to the # prompt. This also means you have to exit twice to leave shell - once for su, and once for shell. Not sure what to make of that, but I figured I would let folks know just in case.
These DO NOT include the EP4P modems - you will have to ODIN those separately if you want them. You can get just the modem update from here - its near the bottom of that post.
Please let me know if there are any problems/issues.
---CWM STOCK FILES---
BLOATED EP4P DEODEXED ZIPALIGNED ROOTED CWM .ZIP
md5: ACBBBB43C3499AC7F732756D12878C57
DEBLOATED EP4P DEODEXED ROOTED CWM .ZIP
md5: 1D12D7D269D51F65798C967A9C516B88
---ADD-ON MODS---
POWER MENU MOD
md5: C1F8E3DDD23982F62F0AF313F59A03D6
When you flash this file in CWM, the end result is 2 extra options on your power menu - Recovery and Download.
NOTE: This particular file is meant to be flashed over UNTHEMED DEODEXED STOCK EP4P - while it has worked on themed EP4Ps and Humble, you WILL see some changes in (themed) appearance. ALSO - it would follow that if flashing this over a theme messes with the theme... flashing a theme AFTER flashing this WILL CAUSE PROBLEMS. If a problem does occur, note that flashing this creates a backup (with .bak extension) of the three files it modifies, so you can always go back in and manually change back (or you can just flash this file to revert those three files back to stock). You have been warned...
That being said, there are now options for EP4P themes that include this mod. I highly recommend checking out Black and Blue or Black and Red!
---MISCELLANEOUS---
- READ DESCRIPTION ABOVE FOR HOW AND WHY TO USE THE FILE BELOW -
--- DO NOT FLASH IN CWM!! ---
ADBsdcardFix.zip
md5: 5A362D2AB8BD5D7878AC1835A4AD558E
Thanks was looking for some information about this the other day. This is the detail/links I needed.
blueis300 said:
Thanks was looking for some information about this the other day. This is the detail/links I needed.
Click to expand...
Click to collapse
Glad to help. And if you end up checking out any of the files - feedback is welcome!
Wow this is great thanks
Sent from DROID CHARGE 4G-LTE
OP updated - now includes link for power menu mod that adds recovery and download options.
Working splendid over here. I do have one request (if you didn't already do it)
Make it possible turn off the dumbass "battery full" notification. A patch would be lovely.
KingWaffle said:
Working splendid over here. I do have one request (if you didn't already do it)
Make it possible turn off the dumbass "battery full" notification. A patch would be lovely.
Click to expand...
Click to collapse
I'm pretty sure I figured out how to do this (haven't tested it yet though), but this will again have the same issues as the power mod itself in regards to theme stuffs - many themes utilize SystemUI.apk (where I believe the edits need to happen), so if you are on a theme flashing such a battery-full-disabling mod will "untheme" whatever was originally themed in that .apk, and if you theme after flashing it you will lose the disabled "battery full" notification mod (unless whatever you flashed over it has it as well of course). I'll play around with it and post something if it works.
I prefer stable over pretty, so I typically don't theme. Same reason I switched back from Humble.
dwitherell said:
I posted this elsewhere, but in the spirit of sharing I figured it might be of some use to folks if I posted it here as well. I decided I would take a crack at doing something more productive than uber-long overly detailed how-to posts (like here for example), so I sat down and attempted to figure out how to make the latest EP4P leak into a CWM-flashable form (thanks to hoppermi for putting the idea in my head).
I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS (GOOD OR BAD) AS A RESULT OF FLASHING OR ATTEMPTING TO FLASH WHAT IS POSTED HERE! As an additional disclaimer - this is an early attempt at utilizing things I just recently learned. It has worked for me and a few others that were kind enough to try, but as always YMMV.
This is all pulled from either the full factory stock unrooted .tar file or the debloated .tar file, both of which I downloaded from here. I then pulled out the system and kernel stuffs, deodexed and zipaligned (the stock unrooted one, as the debloated one was already deodexed), added in/changed busybox (from here), and added in superuser/su (the latter just for the stock unrooted). I also added back in the Task Manager to the debloated version (a number of folks requested it). Truth be told, all of this was done just to see if I could do it. Now that it's done (and I have successfully used both of these to get to EP4P from stock unrooted EE4), I figured I would share them.
BEFORE flashing, MAKE SURE voodoo lagfix is completely disabled (i.e. /data, /dbdata, /cache, and /system all need to be rfs, NOT ext4). You will also need to have CWM (version 4.0.1.4 can be found here) already on your phone, and I would strongly recommend doing a data wipe/factory reset within CWM before flashing as well (that's what I've been doing at least and I have had no problems).
Installation instructions:
- Download file and place on sdcard
- Boot into CWM recovery
- Wipe data/factory reset (Recommended)
- Install the .zip you put on your sdcard
NOTES:
Flashing this should not do anything to the CWM recovery you used to flash (i.e. your recovery won't be overwritten by stock kernel/recovery). That being said, I have encountered an occasional odd issue with CWM after flashing that seems to require adb to resolve. The issue may stem from the stock kernel, or perhaps how one enters into CWM - but I'm just guessing at this point, and it likely is something completely different. Regardless, it happens from time to time...
The issue is that after flashing and then booting into recovery, I occasionally get a "can't mount /sdcard" error. Apparently that in itself is a known issue, and it is listed as such in the CWM recovery thread - which incidentally contains the 4.0.1.4 CWM version I have been using.
The fix requires you to perform the following commands using ADB:
Code:
adb shell
umount /sdcard
rm -f /sdcard
mkdir /sdcard
exit
If you do not have ADB installed and you are having the "can't mount /sdcard" error after flashing - I think I have a workaround for you (thanks bL33d for the suggestion). Download the ADBsdcardFix.zip here - then extract the folder (should be fine to extract it to your desktop) and attach your phone to the computer via USB (I did this while the phone was already in CWM). Open the newly-extracted ADB folder, and then double-click on the CWMsdcardFix.bat - something should pop up on the screen for a brief second, which is completely normal. After double-clicking the .bat file, on the phone go to mounts and storage, then select mount /sdcard - and it now should work!
Either approach here (adb code or the stuff in ADBsdcardFix.zip) has worked every time I have needed it, although again in my experience I have not been able to cull the rhyme or reason out of when that need will present itself.
For those who dabble in ADB, I noticed that adb shell seems to work "differently" on these CWM versions of the EP4P leak. Normally entering adb shell would lead to a # prompt, but with both versions here it stayed as $ - however, if you then enter su it goes to the # prompt. This also means you have to exit twice to leave shell - once for su, and once for shell. Not sure what to make of that, but I figured I would let folks know just in case.
These DO NOT include the EP4P modems - you will have to ODIN those separately if you want them. You can get just the modem update from here - its near the bottom of that post.
Please let me know if there are any problems/issues.
---CWM STOCK FILES---
BLOATED EP4P DEODEXED ZIPALIGNED ROOTED CWM .ZIP
md5: ACBBBB43C3499AC7F732756D12878C57
DEBLOATED EP4P DEODEXED ROOTED CWM .ZIP
md5: 1D12D7D269D51F65798C967A9C516B88
---ADD-ON MODS---
POWER MENU MOD
md5: C1F8E3DDD23982F62F0AF313F59A03D6
When you flash this file in CWM, the end result is 2 extra options on your power menu - Recovery and Download.
NOTE: This particular file is meant to be flashed over UNTHEMED DEODEXED STOCK EP4P - while it has worked on themed EP4Ps and Humble, you WILL see some changes in (themed) appearance. ALSO - it would follow that if flashing this over a theme messes with the theme... flashing a theme AFTER flashing this WILL CAUSE PROBLEMS. If a problem does occur, note that flashing this creates a backup (with .bak extension) of the three files it modifies, so you can always go back in and manually change back (or you can just flash this file to revert those three files back to stock). You have been warned...
That being said, there are now options for EP4P themes that include this mod. I highly recommend checking out Black and Blue or Black and Red!
---MISCELLANEOUS---
- READ DESCRIPTION ABOVE FOR HOW AND WHY TO USE THE FILE BELOW -
--- DO NOT FLASH IN CWM!! ---
ADBsdcardFix.zip
md5: 5A362D2AB8BD5D7878AC1835A4AD558E
Click to expand...
Click to collapse
I see that you theme. I was looking to depoop this phone on ep4. I was looking for a look closer to stock colors maybe like tw4 on Samsung Galaxy s2. Not necesserly the icons and all that just the colors and the pull down bar and gingerbread green battery icons, but fully depooped like this http://forum.xda-developers.com/showpost.php?p=13672499&postcount=2
That would be amazing if you could help me out. Me and my friend tried to full around with some things but the phone just boot looped. I'm running stock rooted ep4 is that right or should I get the deodexed one? Thanks in advance.
KingWaffle said:
Working splendid over here. I do have one request (if you didn't already do it)
Make it possible turn off the dumbass "battery full" notification. A patch would be lovely.
Click to expand...
Click to collapse
Ok - I think I have it figured out. I'll post an update to the OP with a link when I've finished testing it. I also figured out how to disable the low battery warnings - if interested.
trigun123478 said:
I see that you theme. I was looking to depoop this phone on ep4. I was looking for a look closer to stock colors maybe like tw4 on Samsung Galaxy s2. Not necesserly the icons and all that just the colors and the pull down bar and gingerbread green battery icons, but fully depooped like this http://forum.xda-developers.com/showpost.php?p=13672499&postcount=2
That would be amazing if you could help me out. Me and my friend tried to full around with some things but the phone just boot looped. I'm running stock rooted ep4 is that right or should I get the deodexed one? Thanks in advance.
Click to expand...
Click to collapse
I actually do not theme (at least not yet), so I am afraid I am of limited use here, at least with my current skill set. I do know that typically you want to use deodexed files when making a theme, so I would likely start there.
Great post, thanks! Can anyone confirm the color scheme? I really hope it's not poop again..
Sleek69 said:
Great post, thanks! Can anyone confirm the color scheme? I really hope it's not poop again..
Click to expand...
Click to collapse
Lol - it's stock, so unfortunately it very much is poop again.
Is there an updated market apk or zip that can be installed on the EP4P stock deodexed 2.3.6?
It's been awhile and no uodate from original market.
I tried searching but couldn't find an appropriate thread on this from my phone.
Sent from my SCH-I510 using xda premium
Make sure you are using CWM version 6.0.1.0
I am not responsible for whatever happens to your device because everyone else puts this in their threads too! get over it
Be sure to click that Thanks button if this helped you. this also appears in everyone else's thread's! deal with it
1. download the update file for your region from paugustin's thread here:
http://forum.xda-developers.com/showthread.php?t=1720157
2. unzip it inside any folder.
3. open the file called updater-script which is located at:
/META-INF/com/google/android
4. delete the line and the blank space left afterwards then save changes to the file. the line for the US version looks like this:
assert(getprop("ro.product.name") == "a700_pa_cus1");
5. highlight everything that came out of the download from step 1, zip it, and rename it to update.zip
6. place in the root of an SD card, not internal storage!
Note: a few users have recommended placing the update.zip on internal storage. i tried it again from a SD card and it worked just fine. if you're having issues with this try internal.
7. reboot to recovery mode. if you need this guide you've had to do it in the past, nuff said! :silly:
8. select Apply update.zip
9. after you select Reboot System, you will be given two options:
Yes will keep CWM recovery but you wont be able to use recovery mode at all until you unlock the bootloader again!
No will allow the update to restore stock recovery, and you will need to re-flash CWM.
10. if you chose Yes from step 9, unlock your bootloader and do the root process again. DONE!
if you chose No, unlock your bootloader, flash CWM again, and do the root process again. DONE!
there are already guides on how to do that.
BONUS FOR USA TAB OWNERS!
This is ONLY FOR UPDATING FROM the Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zip file from the link in Step 1 at the top of the page.
If you are on any other version, and / or from any other country, DO NOT TRY THIS!
This is the latest update with the power option added in settings & touch sensitivity improvements, with the getprop line already deleted from the script!
A. Download this directly to your tab.
B. Reboot to recovery mode.
C. Install.
D. After selecting Reboot System you will be given two options. Refer to Step 9 above.
E. After making your choice, you will be given the option to prevent the update from deleting root :victory:
F. Unlock your bootloader again.
G. If you chose No. from Step 9, re-flash CWM 6.0.1.0
H. If you chose No. from Step E, root again if you wish.
DONE!!
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
imtheyoyo said:
I've try this, but when I do point 8 (select Apply update.zip), the update is aborded.
I'm on SDs_Acer_AV043_A700_RV07RC06_EMEA_FR.zip with the root by patched boot.
I want install Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR.zip.
I don't know why update fail.
Click to expand...
Click to collapse
i think i know why.
i revised step 5, check it out
That's what I had done, zip and rename in update.zip.
imtheyoyo said:
That's what I had done, zip and rename in update.zip.
Click to expand...
Click to collapse
hmm... did you put it on an sd card?
and what error is it giving you?
Sterist said:
hmm... did you put it on an sd card?
and what error is it giving you?
Click to expand...
Click to collapse
Yes, and the message was "Update aborted"
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
---------- Post added at 10:57 PM ---------- Previous post was at 10:52 PM ----------
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
Thanks for any advice.
CheopsChefren said:
Just a question. I have unlocked my A700 via method 2, so without CWM install.
If I follow this guide, placing the update.zip on the card, and restart with Volume-down+Power, will it execute the update.zip as well?
The update.zip in fact is the altered Acer_A700_AV043.RV07RC04_AV043.RV23RC05_WW_GEN1.zip according to the instructions.
If using Root Explorer, where would I have to place the update.zip file?
Click to expand...
Click to collapse
I'm not sure if a modified update script would run on the stock recovery. you can try it, the worst that would happen is it will decline to run the update. i would recommend you always have CWM recovery regardless of any flashing/updating plans you may or may not have.
and the location for the update.zip does not change regardless of what you use to get the file there lol it doesn't matter if you use a Toyota or Lamborghini to get to work. silly question lol..
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
CheopsChefren said:
Thanks for your answer. The problem is, an unmodified update script wont run either on my unlocked A700.
And, I am scared about using CWM, as I hear stories it will possibly brick your A700, and that is something I am not too keen about.
But, with Root Explorer compared to ES File Explorer you have more possibilities. But I agree, it was abit a silly question.
So now, how to update my unlocked A700 with the OTA delivered by Acer? That's the question.....
Click to expand...
Click to collapse
by my understanding, the CWM versions to avoid are 5.4.0.0 (something like that) and the touch version(s)
unlocking your bootloader and not installing CWM is like alcohol-free-beer... pointless.
When trying the above mentioned procedure, i first got an error 6, which i solved by editing the updater-script the second time with notepad++, so i could keep the unix-like line-ends.
Then when i tried to run the update.zip from within cwm, i got error status 7.
(On both the downloaded update file from the thread mentioned above, and from the original from Acer received OTA update file)
As far as i know, after googling error status 7 has to do with the update zip not for the system trying to update. But i am sure, as i also tried with the Acer received OTA (after deleting the first line in the updater-script), i used the correct update file.
What could cause this?
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
eman01 said:
Hi. Link for U.S. tab owners (www.sendspace.com) is dead. Can you post again?
Click to expand...
Click to collapse
LOL stupid mistake on my part
the link wasn't really dead, i just screwed up in how i posting it lol thanks for mentioningit
Got it. Thanks.
OK. I finally tried above method to update rooted U.S. A700.
Started with:
Image Acer_AV043_A700_RV07RC06_PA_CUS1
Build Acer_AV043_A700_1.029.00_PA_CUS1
CWM Recovery 6.0.1.1
I tried both methods above- initially using the update.zip specifically provided for U.S. A700 owners in the 2nd part of 1st post of this thread
IN "BONUS FOR USA TAB OWNERS!".
Tried it on 1st external SD, then internal SD.
Both ways I get RED TRIANGLE with exclamation point and message:
"Can't open /sdcard/update.zip
(bad)"
OR
"Can't open /emmc/update.zip
(bad)"
I am, of course, sure I copied the update.zip directly from Downloads to the root of the external and internal cards;
I also made sure to use "Choose zip from SD card" in CWM to find the Update.zip file right where I put it.
Not ready to quit, I tried again using the original Update zip file and modifying updater.script myself, exactly as described in the 1st part of the 1st post. I also tried this update.zip with modified updater.script on both the external and internal SD, without success.
This time I did get further, receiving:
Finding update package...
Opening update package...
Installing update...
Mount Data success
Verifying current system...
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
P.S. I verified I have the assert line deleted in the updater.script before I tried this.
I should mention that I have stock ROM, have and have NOT deleted any system apps
(I have inactivated a few like VirusScan within Android).
Luckily I was able to reboot without any problems after all these attempts, but now I am stuck.
Any ideas?
hmmm that's an error i haven't seen before. try deleting the update and downloading it again, or disabling assert check
I'm not a developer, that's the best i can suggest. you'd have to ask someone with a bit more knowledge
it might have something to do with the root method you used originally
Well, I tried yIur modified update.zip multiple times (downloaded it 3 different times, and tried both internal and external SD). As mentioned, I also tried modifying the updater.script myself (used JOTA text editor; maybe that was an issue with respect to how it saves a file, etc.).
How does one disable assert check, as you describe? A link, perhaps?
Interestingly, today I was able to flash the original1.029 update (1st A700 OTA update) after modifying it's updater.script in exactly the same fashion you describe. It put me back to stock 1.029, which I then updated to stock 1.057 (2nd A700 OTA update). I then re-unlocked bootloader, re-rooted and re-installed CWM recovery 6.0.1.1 easily and successfully as described in the threads in A700 development in this forum. Still holding out on CM ROM, as it seems fairly buggy. Thanks for trying. My way definitely took longer; don't know why your direct method would not work on my tab. Thanks.
disable asset check should be one of about 4 or 5 options to choose from, right next to ''choose from internal'' / external
it actually might not be available on this device it's been a while since I've used CWM
i do these modifications right from my tab with ES file explorer.
glad you were able to get it working
[solved] US A700 rooted OTA update
hi all,
after few days of messing about I finally managed to update a rooted US A700. I will try to guide you through what I did.
After initially booting up the A700 I upgraded it OTA to AV043_A700_RV07RC06_PA_CUS1 and after that rooted it using method #2 in the rooting thread (method #1 didn't work for some reason)
Got OTA notification saying that AV043.RV23RC03_PA_CUS1 was available (performance update, 35.72MB in size) but that wouldn't install giving error Status 7.
Installed CWM 6.1.1, still tthe same results, it wouldn't even install any of the other ROM's that are posted in this forum.
I probably should mention that I saved the original OTA update for installation later.
here is the solution (at least in my case)
Downloaded ROM Acer_A700_AV043.RV00RC00_AV043.RV07RC06_PA_CUS1.zi p from http://forum.xda-developers.com/showthread.php?t=1720157
Extracted boot.img and flashed via fastboot flash boot boot.img
Rebooted into CWM recovery and flashed the earlier saved OTA update no problem (was saved on internal memory but external memory card should work as well)
Then all that needed to be done was to root the A700 again (I used method #2 again)
Hope that helps someone.
eman01 said:
OK. I finally tried above method to update rooted U.S. A700.
assert failed: apply_patch_check_("EMMC:\dev\block\platform\sdhci-tegra.3/by-name/LNX:4065536:95
Then a bunch of letters/numbers
E:Error in sdcard/update.zip
(Status 7)
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
You are not using the original bootloader so checking failed.
Simply delete this line to fix it (it happened to me last week when I created my homemade OTA update). Don't forget to unlock your bootloader after that !
So, I do have the newest TWRP installed, but I get a "Status 7" error message anytime I want to flash a new Jelly Bean rom. I'm on AOKP 4.2.1 right now. Can anyone help me?
Here is the error message:
Code:
--Installing: /sdcard/aokp_tf300t)_unofficial_20120625_2002_build-40.zip
Finding Update package...
Opening Update package...
Installing update...
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf30
0t"
E:Error in /sdcard/aokp_tf300t_unnoficial_20120625_2002_build-40.zip
(Status 7)
Installation aborted.
Frank11 said:
So, I do have the newest TWRP installed, but I get a "Status 7" error message anytime I want to flash a new Jelly Bean rom. I'm on AOKP 4.2.1 right now. Can anyone help me?
Here is the error message:
Code:
--Installing: /sdcard/aokp_tf300t)_unofficial_20120625_2002_build-40.zip
Finding Update package...
Opening Update package...
Installing update...
[B][COLOR=Red]assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf30
0t"[/COLOR][/B]
E:Error in /sdcard/aokp_tf300t_unnoficial_20120625_2002_build-40.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Your problem shown in red. updater-script tested your build.prop for tf300t and did not find that. If your unit is tf300t then edit updater-script and remove the assert lines.
Inside the zip you will find /META-INF/com/google/android/updater-script. Edit with notepad or notepad++; not word, wordpad, or other. Save rezip and flash.
tobdaryl said:
Your problem shown in red. updater-script tested your build.prop for tf300t and did not find that. If your unit is tf300t then edit updater-script and remove the assert lines.
Inside the zip you will find /META-INF/com/google/android/updater-script. Edit with notepad or notepad++; not word, wordpad, or other. Save rezip and flash.
Click to expand...
Click to collapse
Okay, thanks, so I deleted that first line...But the update still failes, yet a I don't get an Error Code anymore.
Frank11 said:
Okay, thanks, so I deleted that first line...But the update still failes, yet a I don't get an Error Code anymore.
Click to expand...
Click to collapse
Sorry for the long delay! Search is still down here on XDA.
I'll have to ask questions I would have searched for.
The rom you are trying to flash is 20120625. That is very old and I can't remember any JB aokp roms on XDA during that time. I didn't catch the date earlier because the assert error was staring at me.
Is this from XDA? Give me some info about the rom or better yet a link. I feel that is an ICS rom with a date that old. Maybe that is not actually a date but appears so. With a link to the rom I might be able to find your current issue.
Note: your recovery you are flashing with should be twrp 2.4.1.0 JB.
XDA search is alive again.
This is an ICS rom. Choose a JB rom and try again I think you will have success.
Good Luck!
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
mikep2323 said:
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
Click to expand...
Click to collapse
Did you do your editing with notepad or notepad ++?
Error 6 is usually files that were edited with wordpad or word. It can also be an editing error such as not completely removing the line or partially deleting or editing a line that is still included.
Note: Wasn't blsckbean 6 ICS?
mikep2323 said:
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
Click to expand...
Click to collapse
Not sure but was blackbean 6 an ics rom? I've not looked to see for myself but I have ran 7 and it's great!
Sent from my SAMSUNG-SGH-I747 using xda premium
I unziped it on tablet and edited it with a text editor from tablet then reziped it.If it was a ics one that would make sense but on goo site it says blackbean 6 jbl so I assumed that the jbl meant jellybean boot loader.I also opened the bb7 zip and in that script updater it doesnt have the few lines with the build prop stuff,so after I deleted the first few lines in the bb6 zip it looked exactly like bb7 script updater.I don't think I left any of the lines there.After I edited the stuff I went down to the next line and pressed back button to move the rest of the lines up.If the jbl doesn't mean jellybean loader and it was for icecream sandwhich then I would assume that's why it isn't working.Thanks for writing back.Ive tried almost all the roms for tf300t and like that one the most but without ability to move my game data to microsd card I can't use it.I guess ill have to wait till they can figure out how to make directory bind workwork with jb 4.2.
I also just looked it up and bb6 is for jb bootloader.
mikep2323 said:
I unziped it on tablet and edited it with a text editor from tablet then reziped it.If it was a ics one that would make sense but on goo site it says blackbean 6 jbl so I assumed that the jbl meant jellybean boot loader.I also opened the bb7 zip and in that script updater it doesnt have the few lines with the build prop stuff,so after I deleted the first few lines in the bb6 zip it looked exactly like bb7 script updater.I don't think I left any of the lines there.After I edited the stuff I went down to the next line and pressed back button to move the rest of the lines up.If the jbl doesn't mean jellybean loader and it was for icecream sandwhich then I would assume that's why it isn't working.Thanks for writing back.Ive tried almost all the roms for tf300t and like that one the most but without ability to move my game data to microsd card I can't use it.I guess ill have to wait till they can figure out how to make directory bind workwork with jb 4.2.
I also just looked it up and bb6 is for jb bootloader.
Click to expand...
Click to collapse
I'm downloading it now, when finished I'll see what I can do and give you an update.
tobdaryl said:
I'm downloading it now, when finished I'll see what I can do and give you an update.
Click to expand...
Click to collapse
Thanks I would appreciate the help,I've searched for endless hours and everything always points back to editing those lines..If you need anymore info let me know.I've also tried to download diffrent times.Bb7 flashes fine and hydro and clean rom and blue rom but bb6 wont.I even flashed bb7 then tried to flash bb6,same error as frank got.I also made sure my build prop said tf300t for the errors.I've tried many combonations and wipes.I'm on blue rom now if that matter
mikep2323 said:
Thanks I would appreciate the help,I've searched for endless hours and everything always points back to editing those lines..If you need anymore info let me know.I've also tried to download diffrent times.Bb7 flashes fine and hydro and clean rom and blue rom but bb6 wont.I even flashed bb7 then tried to flash bb6,same error as frank got.I also made sure my build prop said tf300t for the errors.I've tried many combonations and wipes.I'm on blue rom now if that matter
Click to expand...
Click to collapse
OK. Sorry for the delay, I've been recovering my tablet. I edited the updater-script, flashed BB6. Stuck on bootanimation, flashed again, stuck on bootanimation, restored my previous backup, stuck on bootanimation. Flashed stock rom back to a working tablet.
I can't suggest you install the rom but I have uploaded updater-script.
For the future I also edit on the tablet. I suggest jota free on the playstore, it does not add extra characters that cause errors. Example most editors end a line with both linefeed and carriage return which will not work for these files.
Good Luck!
Thanks for getting back to me,I will probably try this at some point,if it didn't work on your tablet then maybe it wont work on mine as well.I do have a few backups and all my apps on titanium back up so maybe ill give it a try.Maybe I just might have to wait till they make directory bind work with jb 4.2 to flash Bb7.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
mikep2323 said:
Thanks for getting back to me,I will probably try this at some point,if it didn't work on your tablet then maybe it wont work on mine as well.I do have a few backups and all my apps on titanium back up so maybe ill give it a try.Maybe I just might have to wait till they make directory bind work with jb 4.2 to flash Bb7.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You're welcome. Sorry my results weren't better.
tobdaryl said:
OK. Sorry for the delay, I've been recovering my tablet. I edited the updater-script, flashed BB6. Stuck on bootanimation, flashed again, stuck on bootanimation, restored my previous backup, stuck on bootanimation. Flashed stock rom back to a working tablet.
I can't suggest you install the rom but I have uploaded updater-script.
For the future I also edit on the tablet. I suggest jota free on the playstore, it does not add extra characters that cause errors. Example most editors end a line with both linefeed and carriage return which will not work for these files.
Good Luck!
Click to expand...
Click to collapse
Can you upload an updater-script for Gingerbread MT6575 models ? Also the link is not working.