Whenever I try to update, it will restart. Then an android with an orange progress bar will come up but in the middle, it will stop and the Android with the triangle with exclamation point inside would appear??
any solutions?
My version is in 3.2
What are you trying to update and how?
tweak89 said:
What are you trying to update and how?
Click to expand...
Click to collapse
I think I'm updating the tablet? I'm doing it OTA when I clicked check updates on the About Tablet area?
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
gee one said:
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I'm running stock but I do have it rooted. Other than that, nothing else. I haven't even flashed recovery.
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
gee one said:
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I used the root toolkit v7 that can be foundon the development section. I'm thinking that if I unroot the transformer, the update could work?
Or maybe if I just downloathe firmware from the asus website, will it work better? Though I don't know how to install it.
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
gee one said:
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Owww. so 8659 is not the latest but the one on OTA? Will I lose root if flash that? and does root work on the newest update?
Yes, you will lose root and any custom recovery if you flash the stock image from the ASUS website. I think the tools in the dev section will still root as long as you have SBK v1 I.e., nvflash works on your tf. You rooted once, so it should be fine.
Related
Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app
New to the forums and flashing ROMs in general, so please forgive my n00b-fail. (I did, at least, search the forums for an answer first. )
Samsung Infuse 4g
AT&T
Was running stock ui, rooted
Was able to flash and restore to factory using Odin (following Jordan's http://forum.xda-developers.com/showthread.php?t=1318160)
Took file DarkROM_JVR_Infuse_10.3.rar and unpacked
Repacked using .zip format
Placed .zip on internal SD
Rebooted to CWM Recovery and wiped data/factory reset as well as cache
Selected install from zip on sd card
Selected DarkyROM_JVR_Infuse_10.3.zip
Screen currently says:
"ClockworkMod Recovery v2.5.1.3 - Voodoo lagfix
-- Installing: SDCARD: DarkyROM_JVR_Infuse_10.3.z
ip
Finding update package...
Opening update package...
Installing update..."
Been stuck like that for the past hour. Have I bricked my phone? Should I go back and follow the "UnBrick the UnBrickable Infuse4g" thread?
Thanks.
Umm....darky rom. Rar? ??? I did not pack it in rar or tar format...that's your prob....its pack as a cwm flashable zip
Sent from my SAMSUNG-SGH-I997 using xda premium
Thank you for your response.
I'm now aware that, as you put it, "...that's my problem."
I'm not sure why the file downloaded as a .rar file. Is there a specific extension to the package process that changes the code? Would not unpacking and repacking as a zip do the same thing?
After "playing with it," I got the phone to launch back into the stock ROM. So. Thanks to myself, on that one.
Problem solved.
Are u sure the file u downloaded was a .RAR file ? or it looked like pile off books that why u calling it a .RAR file ?
If you want I recreated DarkyRomV10.3.zip which is of course flashable in CWM, It has 2 fixes that the original DarkyRom doesn't have.
Darky Rom Fixes:
Dman's Build.Prop Fix
Bigfau's Battery Notification Fix
-------------------------------
Installation:
1 DOWNLOAD DARKY ROM
2 BOOT INTO CWM
3 WIPE DATA, CACHE, DALVIK CACHE
4 FLASH DARKY ROM
5 REBOOT
6 ENJOY
DarkyRomFix
Download Here: http://www.multiupload.com/3Y0BREZCFT
Inorder to fix the Superuser Update you will need to flash the SU Binary Update Fix
Download Here: http://www.multiupload.com/RIAHB3BS8C
@rkkaranrk - Very good idea, but no. I actually didn't have a program that could decompress .rar files on the system I was using. I downloaded a copy of WinRAR specifically for that.
@Axiomkid - Thank you. I'm going to try it when I get home. Now that I've had the oportunity to play around with some of the backup apps, I'm much more confident to try new ROMs.
@Axiomkid - This is a silly question, I'm sure, but how do I flash the superuser update? Do I need to?
.icereach said:
@Axiomkid - This is a silly question, I'm sure, but how do I flash the superuser update? Do I need to?
Click to expand...
Click to collapse
Flash in CWM. You should flash it as it will keep superuser up to date.
Sent from my SAMSUNG-SGH-I997 using xda premium
Winrar makes the zip file looks like RAR so the file u downloaded was very much a zip file.
Hello,
i would like flash CWM on my TF101G so i can flash a rom. I have it rootet with ViperMod but what´s the next? I have testet nvflash but it´s fail. My serialnumber begins with BA0. What can i do?
With my Galaxy S2 that´s all so easy and with the Transformer so difficult
Sorry for my bad english, i´m from germany.
Not difficult at all, everything is there jsut have to do a little research.
RecoveryInstaller
http://forum.xda-developers.com/showthread.php?t=1346180
Thank you for your help but i can not install this apk it´s parsingerror
silence84 said:
Thank you for your help but i can not install this apk it´s parsingerror
Click to expand...
Click to collapse
try re downloading it or make sure that you are rooted
Titanium Backup says i have root. Loaded again but same error. I have Android 3.0.1 on the Tablet could be this the reason?
silence84 said:
Titanium Backup says i have root. Loaded again but same error. I have Android 3.0.1 on the Tablet could be this the reason?
Click to expand...
Click to collapse
Yeah, update to the latest firmware. It should work after that.
Try OTA Root Keeper (it might save your root so you don't have to root again).
IF not just update, run ViperMod again and install RecoveryInstaller
I can not flash the update. I put the Update on the SD, the system dedects also the update but after the restart the update breaks and the system restart again.
I desperate slowly
Did you extract the file you download to get to the zip file inside? You also have to rename that extracted file. I cant recall exactly what it need to be rename to but I'll check soon as i get near a PC
baseballfanz said:
Did you extract the file you download to get to the zip file inside? You also have to rename that extracted file. I cant recall exactly what it need to be rename to but I'll check soon as i get near a PC
Click to expand...
Click to collapse
"EP101_SDUPDATE.zip" i think this is what you have to rename the file
edit: Tips from Baseballfanz For those not able to get it working, a few things to check.
1-Make sure you actually extract the WW_epad-user-8.6.x.x.zip within the zip. Inside the file you download is an Asus folder, inside that is an Update folder, inside that is the WW_epad-user-8.6.x.x.zip file you'll be working with.
2-When renaming, if your PC is set to "hide known extension", you'll not see the .zip so if you type in .zip you'll get filename.zip.zip The file manager on the TF should show you the extension
3-Make sure it's on the root of the sd card and not within any folder.
4-Check spelling of files WW_epad-user-8.6.x.x.zip EP101_SDUPATED.zip
5-Micro sd card is in FAT32 format. Try a different card or format again (after saving your stuffs)
6-File manager on the TF sdcard is internal and Removable/MicroSD is the external sd card.
THESE ARE TIPS FROM BASEBALLFANZ POST SOMEWHERE ELSE ONLY I X'ED OUT THE FIRMWARE NUMBER TO DENOTE THE NEWEST FIRMWARE.... HOPE YOU DNT MIND
Thank you very mutch for your help. I have the last update installed 8.6.6.23 but i can this not rooted. ViperMod no longer works.
YYYEEEEAAAAHH
I have root with nachoroot. CWM is already on it. Many thanks again!
That's good to hear.
Lost root after installing 9ZGgDXDi.zip.
This of course installed JB 4.1.1 but then when I go to recovery after entering fast boot menu I see a supine green robot with a red triangle with an exclamation point spilling out of its guts. (truly a horrible sight)
It also installed recovery-from-boot.p in System folder.
I know the solution is to rename recovery-from-boot.p file to recovery-from-boot.p.bak or renaming to something else or deleting, however since I lost root I don't see how I can rename or delete this file.
When I use root explorer I cannot mount r/w so cannot rename the file
Using ES File Explorer I rename the file but get the message that rename failed.
Connecting the phone via usb and turning on usb storage I can only access files from sd card and so cannot get to system folder in the parent directory.
Please can someone help destroy or rename the .p file.
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
chronophase1 said:
If I'm reading it right, you lost your root and recovery after installing the OTA, right? You can still flash a custom recovery and install SU from said recovery after flashing CWM. You would then have the ability to rename the script which replaces the custom recovery with the stock. The file, if IIRC, is called recovery.sh or something along those lines.
Click to expand...
Click to collapse
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Kitch16 said:
Refer to this guide and re-root. Probably the easiest way to solve it. http://forum.xda-developers.com/showthread.php?t=1789216
Click to expand...
Click to collapse
Tried that site, but the links to software are broken
edited to add:
oops, yes the links to software work, just didn't see the correct download for all the advertizements.
Thanks for your help but I have solved my problem by adb flash of cwr
koyanishi said:
you are reading me right.
However I cannot flash anything thanks to recovery-from-boot.p file.
Whenever I try to flash anything I get message that "installation aborted"
Click to expand...
Click to collapse
You get this from the fastboot screen?
chronophase1 said:
You get this from the fastboot screen?
Click to expand...
Click to collapse
I think its after fastboot screen - that is when I go to apply zip from sd card
However I have since solved the problem by using adb to install cwr again so I am now back to root
thanks to both of you for trying to help
I have looked for hours for the final stock recovery for Stingray. I have found 4.1.1 and updates, but not what I need to flash my Xoom back to root. Can someone point me to a copy please?
TWRP won't work? Download goomanager and have it download and install it.
rastaguy said:
I have looked for hours for the final stock recovery for Stingray. I have found 4.1.1 and updates, but not what I need to flash my Xoom back to root. Can someone point me to a copy please?
Click to expand...
Click to collapse
Are you using the stock kernel and stock ROM right now? If you are, just download the JZO54M OTA file from Google. Open the ZIP file, and go under the "recovery" folder. Put recovery-from-boot.p in /system and put install-recovery.sh in /system/etc. Set the permissions on install-recovery.sh to 544 and set ownership to root:root. Reboot and it'll flash stock recovery for you on the next bootup. :good: