Related
Okay so I went and got the latest working updates from everything and put it in a convenient package for you.
One Click Root Apk: Version 0.1.0
Radio: 2.42.02.10.29
HBoot: 1.47.0000
Kernel: 2.6.29.6 (up to 768 Mhz and its stable )
ClockworkMod Recovery: 3.0.0.5
CynanogenMod: 6.2 - No longer needed
S-OFF
Step by Step Instructions below.
The instructions are only for people running CynanogenMod and ClockworkMod recovery.
Unzip everything.zip to your sdcard
Also put Kernel.zip on your sdcard
You HAVE to install these in a specific order otherwise some things won't work.
Flash CynanogenMod 6.2 if you havent already. It has the latest kernel in it already which goes up to 768 Mhz. http://forum.xda-developers.com/showthread.php?t=731659 here's the new link
Install Rom Manager and flash ClockworkMod recovery 2.5.0.1. Now you MUST backup with it.
Run the ruu included in the zip. this will give you the latest HBoot.
Boot into hboot mode (volume down and power button) and look to make sure it installed HBoot 1.4.7.0000
reboot
install heroroot010.apk
run heroroot.apk and it will give you darchstar's recovery and put a file on your sdcard called rootme.zip
reboot
reboot into Darchstar's recovery
flash rootme.zip
reboot
you now should have root and should have the super user app. if you dont then something went wrong and you should try again.
if you have root, download rom manager and flash ClockworkMod 2.5.0.1
restore your backup with ClockworkMod recovery
reboot
reboot to recovery
flash radio.zip
it will tell you to reboot after it is done.
this boot will take a while so be patient
reboot again
reboot into recovery
wipe dalvik
flash kernel.zip
reboot
reboot recovery
warning: there is no hboot s-on for the cdma hero YET. they are working on it though.
flash S_OFF.zip
reboot
you now have hboot s-off
reboot into recovery
plug phone into computer
run the following code in adb:
adb shell
mount sdcard
flash_image recovery /sdcard/CWMR3.0.0.5.img
exit
adb reboot recovery
reboot
done!
Update: Heres the link to Everything.zip and Kernel.zip: http://www.mediafire.com/?tj5a734t7n6gi
Thanks to jcase for the root apk
Thanks to theimpaler747 for the new radio
Thanks to Whosdaman for the ruu with the new hboot in it
Thanks to Decad3nce the updated kernel
Thanks to regaw_leinad for the S-Off
Thanks to aosp and ClockworkMod for the recovery
Thanks for all the info Deke -- is there some sort of package that is included with this? I don't see anything...
AboveUnrefined said:
Thanks for all the info Deke -- is there some sort of package that is included with this? I don't see anything...
Click to expand...
Click to collapse
yeah sorry. im having troubles uploading it. it will be on here as soon as posible
Edit: Everything.zip is now uploaded! enjoy!
CynanogenMod: 6.2 ?
When did this happen ?
PTown599 said:
CynanogenMod: 6.2 ?
When did this happen ?
Click to expand...
Click to collapse
bout a week ago
6.2 has been around since mid to late December... if not earlier.
P.S. You may wish to give people credit where credit is due.
You're a hero with a hero -- saved me boat loads of time!
I don't see anything named cyanogenmod 6.2 in the zip or the provided link...
Squiggy45 said:
I don't see anything named cyanogenmod 6.2 in the zip or the provided link...
Click to expand...
Click to collapse
Isn't there a lot of places that can be found?
A lot of places? I have 't found one. The contents of everything.zip is:
CWMR3.0.0.5.img
heroroot010.apk
Radio.zip
RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe
S_OFF.zip
No cyanogenmod...
Squiggy45 said:
A lot of places? I have 't found one. The contents of everything.zip is:
CWMR3.0.0.5.img
heroroot010.apk
Radio.zip
RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe
S_OFF.zip
No cyanogenmod...
Click to expand...
Click to collapse
Here's at least one CM 6.2 build
http://forum.xda-developers.com/showthread.php?t=731659
You really need to credit the people who made this stuff in your op unless you want to get infracted or banned. Also this is a pointless thread as these things can be easily found by searching. And you haven't developed anything here so this should be in another forum, not development. Seems like you just keep making threads in development of other peoples work for no reason. Way to go.
sent from my hero, which no longer sucks ass
Squiggy45 said:
A lot of places? I have 't found one. The contents of everything.zip is:
CWMR3.0.0.5.img
heroroot010.apk
Radio.zip
RUU_Hero_C_Sprint_2.31.651.7_signed_release.exe
S_OFF.zip
No cyanogenmod...
Click to expand...
Click to collapse
i didnt put it in everything.zip cuz i didnt have time. I put the wrong link.. sorry. i just updated the link so try it now.
il Duce said:
You really need to credit the people who made this stuff in your op unless you want to get infracted or banned. Also this is a pointless thread as these things can be easily found by searching. And you haven't developed anything here so this should be in another forum, not development. Seems like you just keep making threads in development of other peoples work for no reason. Way to go.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Im putting on the credits now and this is just a package that has everything in it so people DONT have to search for it so it saves them a lot of time plus it has step by step instructions 4 people who dont know how.. and there is no where else to put it otherwise i would.
Q & A would be a tad more appropriate since nothing is being developed here.
kk. will do next time. and if u guys want anymore of these packages pm me da details. itll be in q and a from now on
Since when is there a CM 6.2? The last stable release is 6.1. Anything else is unstably/nightly/unofficial
http://forum.cyanogenmod.com/files/category/17-htc-hero-cdma/
its been out for a while dude. just look at the link i posted. completely stable. idk why they havnt updated they're site yet. http://forum.xda-developers.com/showthread.php?t=731659
That's not 6.2, that's some custom build. Don't know why it's called 6.2, as there never was a 6.2, they went straight into 7
EGOvoruhk said:
That's not 6.2, that's some custom build. Don't know why it's called 6.2, as there never was a 6.2, they went straight into 7
Click to expand...
Click to collapse
Some phones did get pushed to 6.2, the jaybob build was synced with basically the last of the 6.x Hero source.
thanks go to damien667 for the method, brswattt and ladios for being brave and testing.
DOWNLOAD:
View attachment clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Instructions:
unzip the recovery image and use your specific devices installation procedure for recovery.
This is a custom clockworkmod recovery 2.5.1.7 that allows you to finally turn off your phone and allow it to charge instead of it booting right back into clockwork.
a detailed explanation on how this is acheived is HERE
This recovery only has a modified ramdisk, functionality and use is the same as clockworkmod 2.5.1.7 official.
enjoy.
now i'm off to fix the DHD recovery.
EDIT: manually installing is the only option at the moment, thanks gruss.
stupid s-on.
ROM MANAGER should have the latest recovery image available with a fix for powering off and charging, thread will stay up for hostorical reference but these images are no longer required, it is always recommended to upgrade to the current version of rom manager and cwm that your rom requires
amazinglarry311 said:
I need one experienced user to test this recovery image.
The mod performed is the same one done to the the g2 and mt4g and works flawlessly on the recovery images I have posted altering recovery to allow charge while the phone is off and not boot to clockworkmod.
If you do not know how to flash recovery images manually through fastboot or from a rom do not continue.
If you do not know how to recover from a bad recovery flash do not continue.
This image is untested as I do not have access to an aria. Be warned.
Danger should be low, please understand I do not accept liability in the very very small chance something goes horribly wrong.
If you are not sufficiently scared yet, please test and let me know if it works, if not working please stand by, flash back to your previous recovery image, and I will post a fix.
Thanks go to damien667 for figuring it out.
View attachment 562769
if people are using cwm 3.x i can modify that as well.
Click to expand...
Click to collapse
Lots of views - no takers yet...
I'm sure many would find this very useful. If anyone has a "spare" Aria, or is really brave (I have neither a spare nor the guts), please check it out.
.
Bad recovery flash won't kill your phone.
Oh well.
we cant replace the recovery with out unrooting and redoing unrevoked
still need s-off
I thought you could do a temporary flash that doesn't stick. I suppose that's problematic as the device has to be turned off to test the mod. Go figure. The threads here for when someone wants to try it out, I can only think of two potential issues that would cause this not to work. Does anyone have a link to an OTA recovery image in img form for the aria? I'll google it, but if anyone knows please answer.
Flashed, not working. When it booted into recovey, it stayed on the htc screen, no menu was shown. `adb devices` showed that it's in recovery mode, though. Used adb shell to look around, everything's there but no /etc/fstab... can't mount anything.
hk-froyo-ota-recovery-image.zip md5sum: 0d44b10cbb8f1d6d40e68b522e578042
Although I did unroot in order to flash it, I think it might be ok to run unrevoked on sense 2.1 or 2.2 rom to do the job.
edit: wow, ota pops up! never throught i would see that again.
INFO/htcCheckinService(80): Started a new update download: http://fotadl.htc.com/OTA_Liberty_F...4_P_release_138425_15969388mnzxpm7szkle1k.zip
ladios said:
Flashed, not working. When it booted into recovey, it stayed on the htc screen, no menu was shown. `adb devices` showed that it's in recovery mode, though. Used adb shell to look around, everything's there but no /etc/fstab... can't mount anything.
hk-froyo-ota-recovery-image.zip md5sum: 0d44b10cbb8f1d6d40e68b522e578042
Although I did unroot in order to flash it, I think it might be ok to run unrevoked on sense 2.1 or 2.2 rom to do the job.
Click to expand...
Click to collapse
Thank you for testing this, Ladios!
Awesome, thanks for the test. I'm guessing it's the ueventd binary that isnt needed. i'll know in about five seconds after i pull apart the OTA recovery.
Thanks for testing, i'll have another one up in a jiffy.
yup. init.rc was calling a binary (ueventd) that isnt required.
try this one out:
EDIT: removed see bottom of the post
Sorry guys, this would be way easier if i had one.
These are the same changes aligned with the other mods i've done:
basically the OTA recovery contains four binaries not found in CWM
detect_key
power_test
offmode_charging
choice_fn
the init.rc on the original OTA recovery calls these binaries when plugged in and off, the recovery kernel should load but keeping the phone off and in a charging state. adb will should available in this mode as well.
a better explanation was in the mt4g thread: http://forum.xda-developers.com/showpost.php?p=12513699&postcount=3
EDIT: removed, found resources needed.
please test. and thank you. this mod is in response to a request by gruss at the CM forum to see if the same mod could be applied.
EDIT: the OTA recovery that was posted did not contain some resources, give me five minutes... i found the original RUU and the recovery image there has everything i need. filesize increase is due to inclusion of offmode_charging_images that i found in the original OTA recovery.
EDIT: REMOVED - test succesful see first post.
this one really should work. i have pretty good faith in it..
If not, it looks like the mod works with some recoveries and not all. i may attempt one more time, but i dont want to waste people's time here.
amazinglarry311 said:
yup. init.rc was calling a binary (ueventd) that isnt required.
try this one out:
EDIT: removed see bottom of the post
Sorry guys, this would be way easier if i had one.
These are the same changes aligned with the other mods i've done:
basically the OTA recovery contains four binaries not found in CWM
detect_key
power_test
offmode_charging
choice_fn
the init.rc on the original OTA recovery calls these binaries when plugged in and off, the recovery kernel should load but keeping the phone off and in a charging state. adb will should available in this mode as well.
a better explanation was in the mt4g thread: http://forum.xda-developers.com/showpost.php?p=12513699&postcount=3
EDIT: removed, found resources needed.
please test. and thank you. this mod is in response to a request by gruss at the CM forum to see if the same mod could be applied.
EDIT: the OTA recovery that was posted did not contain some resources, give me five minutes... i found the original RUU and the recovery image there has everything i need. filesize increase is due to inclusion of offmode_charging_images that i found in the original OTA recovery.
View attachment 563263
this one really should work. i have pretty good faith in it..
If not, it looks like the mod works with some recoveries and not all. i may attempt one more time, but i dont want to waste people's time here.
Click to expand...
Click to collapse
This does indeed work The screen is a little dim though when it's charging.
brswattt said:
This does indeed work The screen is a little dim though when it's charging.
Click to expand...
Click to collapse
Excellent, I will update the first post. About the screen being slightly dim - the stock aria recovery image used to actually load pictures showing the charging status while the phone is off, this would draw the images on the phone and the background was never a solid black, go figure. Cwm doesn't display them correctly as the resources are there but it was never written into the recovery itself or it's a frame buffer issue our something along those lines.
EDIT: see first post for download.
amazinglarry311 said:
thanks go to damien667 for the method, brswattt and ladios for being brave and testing.
DOWNLOAD:
View attachment 563834
Instructions:
unzip the recovery image and use your specific devices installation procedure for recovery. TESTERS - see below.
This is a custom clockworkmod recovery 2.5.1.7 that allows you to finally turn off your phone and allow it to charge instead of it booting right back inot clockwork.
a detailed explanation on how this is acheived is HERE
This recovery only has a modified ramdisk, functionality and use is the same as clockworkmod 2.5.1.7 official.
enjoy.
now i'm off to fix the DHD recovery.
TESTER NEEDED: Now the instructions to install the recovery are to do it manually and unzip the file. the zip itself is actually flashable, i just need to know if the capability exists for the aria to flash a recovery image while booted into recovery. The way that some OTA updates usually work (or used to) allowed raw images to be flashed while in recovery. I know the nand is locked when you are booted, but does the same apply to recovery? My assumption is no. if someone would like to test the zip from their current recovery and flash it, and reboot to recovery, turn off and try to charge to see if it sticks. possible things that can happen testing this: it doesnt stick and you keep your old recovery and flash manually, or you lose your recovery image (doubtful and highly unlikely)
it occurs to me that the flashable might not work, are your devices the kind that write the recovery image every time the phone is turned off?
Click to expand...
Click to collapse
Cannot flash the zip:
Code:
-- Installing: SDCARD:2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Opening update package...
I:Update file path: /sdcard/2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
Installing update...
I:Trying update-binary.
E:Error in /sdcard/2Flash/clockworkmod-2.5.1.7-liberty-offmode-charging.zip
(Status 0)
Installation aborted.
I tried to use flash_image before, it can't be read/write. Except one time, unrevoked failed its attempt and stopped right before its last couple of stages, flash_image worked for once. In other times, it failed and then rebooted, left me no chance to run flash_image.
for now manual flash looks like the way to go. you can check the OP again, there's a slim possibility a LIBEIMG.zip will load from hboot. it's in the first post. this kind of thing works for mt3g/dream/g2/mt4g but these suckers are all s-off as well. sigh. lame.
amazinglarry311 said:
for now manual flash looks like the way to go. you can check the OP again, there's a slim possibility a LIBEIMG.zip will load from hboot. it's in the first post. this kind of thing works for mt3g/dream/g2/mt4g but these suckers are all s-off as well. sigh. lame.
Click to expand...
Click to collapse
Hboot loaded the zip, showed a vertical status bar on the top-right corner, said checking the zip, and then stopped.
Seems unrevoked is the only way...
yeah i just finished updating the original post. thanks to everyone who tested.
s-on sucks big time.
just to be clear though the image is reported to work and charge while off.
Thanks for all the work.
Sent from my Liberty using XDA Premium App
amazinglarry311 said:
yeah i just finished updating the original post. thanks to everyone who tested.
s-on sucks big time.
just to be clear though the image is reported to work and charge while off.
Click to expand...
Click to collapse
So if I understand this correctly:
1. Connect phone to computer whilst booted up
2. Run Unerevoked, but use the included ".img" file from the OP file
3. Install the new recovery image
4. Reboot phone (if it doesn't do it on its own)
Or do I flash the entire .zip file from the phone's recovery menu?
Sorry if these are "dummy" questions...
Thanks for this little modification of the recovery! I actually see a little battery on the screen when charging now. However, Recovery still says 2.5.0.7, but charging while off works with no problems. I also flashed CM7 using the recovery I downloaded in this thread, so the recovery has no issues as well! Thanks again!
DanGeorges said:
So if I understand this correctly:
1. Connect phone to computer whilst booted up
2. Run Unerevoked, but use the included ".img" file from the OP file
3. Install the new recovery image
4. Reboot phone (if it doesn't do it on its own)
Or do I flash the entire .zip file from the phone's recovery menu?
Sorry if these are "dummy" questions...
Click to expand...
Click to collapse
I actually had to first unroot before Unrevoked actually installed the new recovery image. Something is weird about the Aria about not flashing recoveries directly...
foreign_legion said:
I actually had to first unroot before Unrevoked actually installed the new recovery image. Something is weird about the Aria about not flashing recoveries directly...
Click to expand...
Click to collapse
So if I unroot, then use Unrevoked, how do I get unrevoked to use the new recovery? Is there a file somewhere on my computer that should be swapped out first?
Hi all.
I found this look through the Kindle thread.
I didn't know it existed until now.
Check it out...looks interesting.
http://www.youtube.com/watch?feature...&v=xMdj_QzfGmw
http://teamw.in/project/twrp2
Naice! Just read about this on AndroidPolice but didn't see that video, nice to see it working right off the bat on a Gtab
wow neat! I wonder what android kernel version this is based of off...
fosser2 said:
wow neat! I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
Yeah..I bit the bullet and DL it and followed directions.
I couldn't boot into recovery.
It hangs at the birds.
Normal boot runs the underlying ROM fine though.
I'm on a 1.2BL. Was running a series of FB from 8.0 to 10.1 without NVFlashing.
I had only factory reset and wipe and booted into Beasty/Clem Ultimate as the latest ROM. (This FROYO is very fast and stable btw...)
Tried the TWRP 2.0 but couldn't get it to work either.
It's on the YT video though. Obviously it works
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
qkster said:
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
Click to expand...
Click to collapse
Works fine on the 1.1 bootloader.
rajeevvp said:
Works fine on the 1.1 bootloader.
Click to expand...
Click to collapse
Yup, confirmed by Jazzruby.
only for 1.1 BL.
JR did emailed TeamWin re: possible 1.2BL application
thanks..
how do you like it btw?
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
aabbondanza said:
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
Click to expand...
Click to collapse
will give it a try...thanks
fosser2 said:
I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
It's a (newly compiled) stock VS kernel for 1.1 and a clemsyn kernel for 1.2 bootloaders.
---------- Post added at 09:02 PM ---------- Previous post was at 08:45 PM ----------
qkster said:
JR did emailed TeamWin re: possible 1.2BL application
Click to expand...
Click to collapse
It's easy enough to insert a 1.2 kernel into any recovery partition since the both the boot and the recovery partition on the gTab has an identical structure (necessarily so).
1. Download any of pershoot's kernel zips.
2. Replace the kernel/zImage file in the zip file with either a stock 1.2 kernel from an existing recovery image (Or, just use pershoot's 1.2 kernel).
3. Edit META-INF/com/google/android/updater-script and
a) get rid of the lines involving /system
b) change the string "boot" to "recovery" in the first run_program() and the write_raw_image() directive.
4. Pack everything up into a zip file and then just flash it.
how do you like it btw?
Click to expand...
Click to collapse
Works as advertised.
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
timbck2 said:
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
Click to expand...
Click to collapse
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
rajeevvp said:
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
Click to expand...
Click to collapse
Ah, I see. Did they give any indication when you contacted them that they were going to fix this? I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
timbck2 said:
Did they give any indication when you contacted them that they were going to fix this?
Click to expand...
Click to collapse
Haven't contacted them--I'm running on a 1.1 bootloader, and, as I said, the problem is easy enough to fix on your own.
I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
Click to expand...
Click to collapse
You don't need any tools if you have a 1.2 kernel ready; otherwise you need the unpackbootimg program.
See post #9 and just use a pershoot 1.2 kernel.
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
timbck2 said:
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
Click to expand...
Click to collapse
Same here...
I had NVflashed back to 4349.
Comfirmed the stock 4349 worked.
Booted into cwm.
Wiped everything in cwm. Partition 4096 then back to 2048/0
Aplied the twrp update.
Booted into recovery.
TWRP 2 looks great. The menu and screen is responsive.
Tried wiping with it...looks good
I then flashed a rom with it...Beasty/Clem Ultimate to be exact.
Installation reported complete.
Booted up and...got the birds....nothing else...
Tried going back in recovery... recovery is also gone too...
Soft bricked...
Good thing I know how to nvflashed back to stock but for someone new to gtablet, twrp2 may be bad news.
I saw a few post with people having twrp2 installed...has anyone successfully install a rom with twrp?
I have gone total brick (no boot, no recovery) twice and both times TWRP2 was loaded. I can't prove it is the cause, but I never had that problem before even with heavy duty flashing of ROMs etc.
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
That has fixed it with no data loss every time for me.
Meanwhile, I've gone back to cwm.
Oh, I should say that TWRP2 did work most of the time. But sometimes I would reboot and just hang permanently until MSC gets reflashed.
I liked it in general, although it looked on the internal SD and not external like the version of CWM I have does. Would be nice to either pick or have a 2nd version. But if it keeps corrupting MSC and hanging the box, it isn't worth the trouble. CWM is clunky but fine.
wd5gnr said:
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
Click to expand...
Click to collapse
It's better to wipe it clean using the ``--format_partition'' flag to nvflash instead of relying on someone else's partition images.
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
jpearn said:
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
Click to expand...
Click to collapse
go finding a original recovery dump,and flashing it in fastbootmode.
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
1
californiarailroader said:
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
Click to expand...
Click to collapse
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
lsnc said:
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
Click to expand...
Click to collapse
Thanks! However, the US Version doesn't have an update for it, at least not yet, and I haven't been able to find a stock US A700 ROM.
So we would need to rename the install-recovery.old back to install-recovery.sh in /system as this was disabled in CWM ??
So has anyone managed to successfully put on the stock recovery ?? !!
jpearn said:
So has anyone managed to successfully put on the stock recovery ?? !!
Click to expand...
Click to collapse
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Moscow Desire said:
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Click to expand...
Click to collapse
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
californiarailroader said:
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
Click to expand...
Click to collapse
Sounds like a plan I'll keep things working for now, thanks !
jpearn said:
Sounds like a plan I'll keep things working for now, thanks !
Click to expand...
Click to collapse
View attachment updater-script.rar
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
I don't understand these instructions. What original file is being replaced? What update.zip are you referring to?
EDIT
Well, I tried to swap out the update script that came in the ROM: SDs_Acer_A700_AV043.RV00RC00_AV043.RV07RC04_EMEA_CUS1, with the one provided above and seemed to have made some progress...I put on an external SD card and renamed to update and then flashed it through the CWM recovery and it completed. A random offset was noted and then the SD update completed note. However, when I rebooted the device it stuck at the Acer logo and never went any further.
EDIT
So, it then occurred to me that the flash through CWM was probably only partially successful - maybe the replacement of the recovery worked. So, I took the same ROM I noted above, unmodified, placed on the external SD card, renamed, etc. and flashed it and it worked - I never saw any signs of CWM during this process. I hope this helps others too.
EDIT
Looks like I spoke too soon...the flash never got past a 1/4 of the progress bar. Looks like I still have a non-functioning device.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
Hi, I'm a A510 user. I used the CWM to wipe data/factory reset, after that i cant flash any zip, and even cant enter the system. When i turn on the tab, it stuck on 'iconia tab' LOGO, I tried to hard reset, then i got a 'Unrecoverable bootloader error (0x19000008)'
I enter the fastboot and flash the stock recovery back. next i use the recovery to flash update.zip as usual, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway!
every time the flash stuck in the same place of the whole progress bar, i guess it is not an accident! After read your solution, I check the script in my zip, then i delete 2 lines about 'format' command. I think this time will be ok! but to my surprise the green turtle fell down when flashing.
I think the idea is great, but it maybe make the script incomplete, so it cant be flash in.:crying:
So we were trying to update my friend's Tab 2 to a 4.4.2 ROM. We got CWM 6.0.2.3 installed, and tried a ROM. Well this failed, and appeared to break other stuff as it now boot loops to CWM. Actually I think it's going every other book to CWM. Right now it's saying battery depleated. I've got it plugged intoa charger, hopefully it'll take a charge.
I did later realize we weren't using a new enough version of CWM, but regardless, any ideas how to recover from this? It does not appear to be able to go into download mode. It only goes to CWM. I've tried flashing other ROMs but that doesn't seem to be working either.
So...kinda stuck for the moment.
Thanks!
colema19 said:
So we were trying to update my friend's Tab 2 to a 4.4.2 ROM. We got CWM 6.0.2.3 installed (...)
Click to expand...
Click to collapse
We have a winner... the next one who didn't pay any attention - i.e. reading the OP post of the ROM thread.
ClockworkMod Recovery 6.0.x.y is ONLY for flashing CyanogenMod up to 10.1.3.
For flashing OMNI ROM or CyanogenMod 11 (both Android 4.4.2 at the time of writing) you _NEED_ to use TWRP (recommended for OMNI) or PhilzTouch Advanced Recovery or ClockworkMod Swipe Edition (recommended for CM11). See AndroidAndi's file repository to obtain a copy of the correct recovery for your particular model of the Tab 2.
Next thing to do: Download and install ODIN, install the "Samsung USB Drivers" (Google's your buddy), download the .tar.md5 of the recovery you want to flash (see above and make a choice), put the tablet into download mode, flash the recovery.
If that worked flash the custom ROM of choice (+gapps if CM11, +SuperSU if OMNI) through the custom recovery you just installed and be glad you didn't turn the tablet of your friend into a paperweight.
BoneWithABeagle said:
We have a winner... the next one who didn't pay any attention - i.e. reading the OP post of the ROM thread.
.
Click to expand...
Click to collapse
Speaking of not reading OPs and paying attention...I already said I realized that was the issue, and that I can't seem to get it to go into download mode, so that's likely paperweight land?
colema19 said:
Speaking of not reading OPs and paying attention...I already said I realized that was the issue, and that I can't seem to get it to go into download mode, so that's likely paperweight land?
Click to expand...
Click to collapse
If you're down to "can't get it into download mode anymore" (I start to assume the attempt to flash some 4.4.2 ROM through CWM 6.0.x.x may overwrite partitions it's not supposed to overwrite) the only way left to breathe life back into the tablet is to resort to JTAG (UART port connection, CASUAL restoration package, USB Jig to force the tablet into UART mode).
If you search on XDA you will discover tons of threads by AdamOutler dealing with that topic, maybe that's useful to you in any way to figure out if that's an option for you.
Does it stay in CWM once it boots? If so you can copy a TWRP 2.7.0.x zip file to your SD card and install it from there.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Does it stay in CWM once it boots? If so you can copy a TWRP 2.7.0.x zip file to your SD card and install it from there.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
I'll keewp looking, but if you have a location I can get a flashable zip that will work for this, that'd be very helpful!
Thanks
Found a flash, flashed TWRP and got CM11 on it and working.
Thanks!