Hi all,
I have looked all thought the forum and the closest thing I found to an answer was try twrp. What I have is an tf300t running 4.1.1 with stock rom, and cmw 6.0.2.3. Every time I try and create a back up I get "error while backing up boot image". I have tried backing up to external sd, internal, and even tried different SD cards. Nothing seems to be working. Has anyone else had this problem? Or any idea what it might be?
Thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
zac.wright said:
Hi all,
I have looked all thought the forum and the closest thing I found to an answer was try twrp. What I have is an tf300t running 4.1.1 with stock rom, and cmw 6.0.2.3. Every time I try and create a back up I get "error while backing up boot image". I have tried backing up to external sd, internal, and even tried different SD cards. Nothing seems to be working. Has anyone else had this problem? Or any idea what it might be?
Click to expand...
Click to collapse
Well, "Try TWRP" is indeed the right answer.
I think CWM uses the stock CM kernel and that does not expose the boot partition as a device. So CWM can neither read nor write the boot partition and an error is what you get trying to back it up.
Sent from my TF300T using Tapatalk
Thanks, I did go ahead and install twrp and it worked just fine. Should have done it from the beginning, I like it better anyway.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
Ok Here is what I did:
First I flashed temesak's unofficial CM7 bulid then I couldn't access my sd card so I went to flash another rom (Hellfire's 7.2 super tweaked)
Recovery Used : CWM 5.8 Touch (Experimental)
I flashed and then I tried to reboot and then. *BOOM* Right back to the recovery screen. I tried a few more time but with the same outcome
I flashed a couple other roms like Eagle's Blood 2.3 and Weapon G2x but still had the same problem
Thinking it was my recovery I flash the 5.2 CWM and problems still there. Then I flash back a stock backup and a stock recovery thinking I just go back to stock to solve problem. NOPE i'm looking at a box with an arrow pointing at an Android.
I'm thinking I messed with something in the phone and now the command to set to boot normally is replaced with a command to boot into recovery.
Or
My volume down button is stuck but, that's unlikely considering I can use the recoveries just fine and flash roms, wipe dalvik everything too
Please help I bought this phone off of craigslist and been having trouble with it since day one (Unrelated to the seller) just general problems with LG
Try the G2x batch cleanup tool in the dev section. Sounds like your partitions may have been messed up. And stick with CWM 5.2
Sent from my LG-P999 using xda premium
IT WORKED PERFECTLY! It's Exactly what I needed. Not only did it fix my bootloop problem, I can now access my USB storage without a SD Card reader. Thanks Bro, And thank you mansa_noob (G2x Batch Cleanup Tool)
Odogray said:
IT WORKED PERFECTLY! It's Exactly what I needed. Not only did it fix my bootloop problem, I can now access my USB storage without a SD Card reader. Thanks Bro, And thank you mansa_noob (G2x Batch Cleanup Tool)
Click to expand...
Click to collapse
Glad it worked!
Sent from my LG-P999 using xda premium
Same Problem.
I have a same problem, also wanna add that every time I connect my phone too a charger it turns on by itself, and boots to CWM Recovery.
I tried using Batch Cleanup Tool but still having same issues. Please HELP!!! I cannot afford a new phone right now.
Thanks in advance for any suggestions.
Nata, what rom are you using? Try flashing something else
Sent from my LG-P999 using xda app-developers app
Hi all,
I recently recovered from a pretty disastrous softbrick and now I'm trying to flash back some custom ROM's but can't seem to make any progress.
I had to use NVFlash to restore my bootloader three times today, because no matter what I flash (ICS or JB), it breaks it.
I'm on the stock .29 firmware atm, and I'm unable to flash anything else. I've tried CM 10, Baked #6, CM 9.1, CleanROM, and basically any others I can think of. I even tried flashing the latest JB firmware from the ASUS website but was greeted with a "FAILED: remote <>" error.
I've followed the directions on the CM wiki about performing a factory wipe before flashing, I've wiped caches and dalvik cache, still nothing.
That being said, I am able to USE my tablet but I can't change anything atm. I am rooted and unloaded with CWM recovery so I'm happier than being bricked, but I'd like to change from stock obviously.
Can anyone advise me to move forward?
I appreciate any responses, thanks.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
You could try TWRP?
Sent from my R800i using xda app-developers app
UndisputedGuy said:
You could try TWRP?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
I mean I could but at this point I don't think its an issue with the recovery I'm using. It seems to be something since my bootloader messed up.
This guy seems to be having the exact same problem I'm having, so it's odd that we both posted threads so close to each other.
Sounds like a bootloader problem to me. Sorry I don't know how to fix it.
Well, I can't seem to find a solution for your problem. I've never seen something like it before. I'm guessing you probably messed something up when wiping your device. Hope you get it fixed, though.
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Can you check your file system and see if your CWM folder has a backup? It should be Sdcard/CWM or extsdcard/CWM. If not, do you mind flashing another rom or that same rom?
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
2 questions: Which factory image did you use to restore (link to thread)? Did you change the default backup location in CWM (ie, did you backup to the external sd or the internal - internal is default)?
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Didn't unlock bootloader?
I don't know for sure. I unzipped SU plus bootloader file exactly as specified in forums/video. Had no problems until I tried installing that ROM through ROM manager. And forgive me for trying that. I hadn't rooted in over a year. But main problem now is just that I want to recover how my phone was ie settings and set up if possible.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How big are those 2 folders?
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That sounds about the right size for a backup. When you go into CWM and do the restore (or restore from external - which ever has that folder, you didn't say) it doesn't show a backup?
What version of CWM are you running?
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe after all that flashing and Odin-ing your recovery install got wanked, somehow.
Let's try this: it will re-install the latest CWM, clean and then let's see if it'll recognize your backups.
http://www.clockworkmod.com/rommanager/
download the touch image for the d2vzw (or just click here)
put that in the root of your internal sd card.
Open up terminal emulator on your phone and type the following:
Code:
su
dd if=/sdcard/recovery-clockwork-touch-6.0.2.3-d2vzw.img of=/dev/block/mmcblk0p18
reboot recovery
(partition 18 is your recovery partition)
That'll push the known good CWM to your recovery partition and boot you into it. It won't mess with any sort of data anywhere else on the phone.
Alright, thanks. I'll give this a try after I get back home from work.
Sent from my SCH-I535 using xda app-developers app
recovery
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
COuld you possibly link the file you used to get back to stock? i resently tried to root my device and it won't start.
No problem. Once again, I'm at work. I'll post it when I get home though.
Sent from my SCH-I535 using xda app-developers app
I am very new to the ROM scene. I have just recently done my second flash on a Transformer TF700t and I am completely stuck.
I flashed and it ran perfectly smoothly the first time around, except for the fact that i flashed in the wrong order and was left without gapps. I recovered to the stock ROM and tried again, this time in the correct order. I got a message that surprised and stumped me.
"Unable to locate zip file '/storage/emulated/0/goomanager/pa_tf700t-3.15-16APR2013-002620.zip'"
Anyone have any fixes or suggestions on how to remedy this? I will be actively working to solve.
Thanks,
Neb
UPDATE:
I wanted to see if it was a program/rom causing the problem.
I tried ROMManager with Cyanogen and it did the exact same thing with a separate directory.
Anyone have any suggestions?
You forgot to tell us which recovery you are using.
_that said:
You forgot to tell us which recovery you are using.
Click to expand...
Click to collapse
My apologies. I have been using twrp the entire time, and recovering off of that as well.
You forgot to tell us the version number of your recovery.
Try selecting your zip file manually with the recovery's "Install" command instead of using ROM Manager.
Are u saving it to an external SD card? If so Make sure its not formatted NTFS.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4 Beta
Thanks guys, been up for a couple hours now with a fresh mind and got it working.
I ended up just reinstalling a fresh stock JB and it seemed to download the OS fine.
Now I am running smooth and perfect on PA
Every time I try to flash the official opo aosp they made it says failed. I've flashed plenty of ROMs over the years so I know what I'm doing as far as flashing it correctly, no idea why it says that.
Sent from my One using xda premium
Uncheck mount system ?
Maybe tell us what your procedure was?
You've got to give more information when looking for help. Otherwise you waste your time and ours.
I installed it a few weeks back with no issues. Twrp 2.7.1.0, I think.
I did a factory reset and then wiped system. No problem.
NaterTots said:
Maybe tell us what your procedure was?
You've got to give more information when looking for help. Otherwise you waste your time and ours.
I installed it a few weeks back with no issues. Twrp 2.7.1.0, I think.
I did a factory reset and then wiped system. No problem.
Click to expand...
Click to collapse
Like with any ROM, I wiped and factory reset and then installed the zip and it failed. Multiple times.
Sent from my One using xda premium
C-4Nati said:
Like with any ROM, I wiped and factory reset and then installed the zip and it failed. Multiple times.
Sent from my One using xda premium
Click to expand...
Click to collapse
And yet you still gave no actual information. Have fun figuring it out.
I shall not be back.
Oh, you do know there are like 4 different recoveries floating around here right?
I'm using the most recent TWRP 2.7.1.0, the error I keep getting when it fails is "E: Error executing updater binary in zip 'it names the zip here' then says error flashing zip 'names the zip here'. No idea why, then below that it says updating partition details... and just stays stuck at that screen cause it failed, so I just always end up going back and restoring a back up. I have no idea why it's doing this.
edit- Could it have something to do with the name of the device? I have the unlocked version sold in america and etc, not the chinese version, but on the stock rom under phone name it said "one" now I just flashed a custom rom and it says A0001 or something like that.
Have you tried downloading again? Could be a bad download. A0001 is normal.
Sent from my OnePlus One
OPO forums had something about this. The latest update changed the name of the device from bacon to A0001. The update script of the AOSP ROM is looking for bacon. One guy said he removed those references from the updater-script in META-INF/com/google/android and got it to work. Same solution did not work for some other people. All the people I saw saying they couldn't flash it were coming from 33R.