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.
Related
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,
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:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.
Delete Data from Google Framework Apk and then start the Update Checker.
UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:
Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...
I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"
chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.
chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...
chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh
Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )
format c:\ said:
Hello all!
Newly registered here, has been lurking around for some time though.
I just received my replacement OnePlus due to the death of the first one and wanted to do a custom recovery and install Oxygen or Carbon for a little better battery life and back up possibilities.
My problem is: I can't get the phone to boot into recovery.
I did some research and people mentioned trying TWRP and PhilZ's recoveries - those had no result for me.
I have followed official video from OnePlus and also tried C4ETech's way for those two mentioned above.
The ones I tried were PhilZ's 6.50.2 and 6.58.8, for TWRP I used 2.8.5.1 and 2.8.4.1
Tried to do it with OPO toolbox and that didn't work either (TWRP, CWM, PhilZ tested)- all the functions would work, but once I flash the phone - it would boot into stock CM11.
When I try to boot it into recovery, it would stay on the first logo for 7-8 seconds, after that vibrates again and goes into stock CM11.
The same would happen if I go to advanced boot and boot into recovery.
I have changed the options under Developers folder as required already.
I have tried flashing the phone on two computers - win7 x64 and Win 8.1 x64.
Any help would be appreciated.
I have the phone for almost two weeks already and still can't ring myself to setting it up because of previous experience of data loss. (not worried about pictures - those are on Gdrive )
Click to expand...
Click to collapse
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.
Heisenberg said:
Are you checking the md5 of the recovery files after downloading to ensure that they haven't become corrupt during the download? Exactly which recoveries have you flashed (full filenames please)? Also, is the flash with fastboot definitely succeeding? I'd suggest not using a toolkit because they inevitably cause problems.
Click to expand...
Click to collapse
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Forgot to add philz_touch_6.50.2-bacon and philz_touch_6.58.8-bacon were used.
format c:\ said:
I did verify the checksums for TWRP recovery files. They matched.
The ones I used: openrecovery-twrp-2.8.4.1-bacon and openrecovery-twrp-2.8.5.1-bacon
I was not able to find md5 data for PhilZ files, just certificates.
I tried toolkit after going through command prompt. I'm not sure if it is succeeding, nothing happens as far as phone rebooting by itself. The process seems to run and say that it was successful in the prompt.
Do you want me to go though it and post the screenshot?
I've tried not doing "fastboot reboot" command, as it was mentioned in the "Noobs" section - still no result.
Click to expand...
Click to collapse
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
https://dl.twrp.me/bacon/twrp-2.8.7.0-bacon.img.html
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?
Heisenberg said:
Is there any reason you're flashing older versions of TWRP? They're pretty outdated now. Grab the latest version from here:
As long as it says it's successful in the terminal window it should have flashed ok. What build of CM is currently on your phone?
Click to expand...
Click to collapse
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!
I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1
format c:\ said:
It did work! Now I'm a happy camper Trying to install Oxygen right now.
It was on 11.0. My old phone was running that OS as well, but it was having issues with screen artifacts I have upgraded to 12.0 and system was running fine for 2 day, after that screen died completely. Buttons at the bottom of the phone were working, but it looked like just the back light was on.
Huge thanks to you, Heisenberg!
Click to expand...
Click to collapse
format c:\ said:
I was flashing older versions, because I found only those from the official video link. It sent me to techerrata page and the latest one over there was and still is 2.8.5.1
Click to expand...
Click to collapse
Awesome, very glad to see you got it working. I realised after my post that your current CM version is in the title of the thread, lol, oops. That Techarrata site doesn't get updated anymore as they have a new site now, so the latest builds can always be found here:
https://dl.twrp.me/bacon/