I am getting a failure message when I try to back up the original system before trying to flash a custom ROM.
What am I not doing correctly?
I loaded a screenshot here but I don't see it.
Related
I'm fairly new to rooting and flashing, but I can figure things out usually after a bit of research. This has me completely stumped though because I have no idea what to attribute my problem to:
I rooted my Evo a few weeks ago and flashed CM7. The problems I had after flashing CM7 was my GPS and I had 1x instead of 3G. Note: I have also updated my CM7 with the recent updates.
I researched some fixes for the GPS/1x issue, which meant I needed to flash to a sense-based rom. I tried flashing a sense-based rom (several different ones) on several occasions via Clockwork/Rom Manager and I had no luck- it would just reboot to the white screen over and over.
The problem I'd like to resolve in this thread is how to figure out why I am unable to flash to *any* rom. I just attempted flashing KingsRom (via Rom Manager) and everything seemed to be going quite well until the very end where it scrolled so fast I could barely catch what the error was- and it seemed to be something with the "boot image."
Side note: During one of my previous attempts at flashing a different rom, which of course was unsuccessful, I was unable to flash a restore of my CM7 backup and I received this error: "error while flashing to boot image." However after just going at it over and over again I managed to flash a fresh CM7
I'd really appreciate any help as it seems a simple flash is giving me a lot of trouble. If any details about my phone are needed to help resolve this please let me know (I don't know what would be necessary to post).
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
plainjane said:
Try swapping recoveries to Amon Ra. You should be able to do this through Rom Manager. If not you'll have to do it manually.
Reboot into recovery, go ahead and do a backup if you'd like, and then wipe everything in the wipe menu except the SD card. Then try flashing the rom again. If you need more details or if it doesn't work, let me know.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
+1 on what Jane said. You can use rom manager to flash RA recovery (alternate recovery) but don't use it for flashing roms. Just wipe like she said and flash the zip manually through RA.
Sent from "The EVO" using XDA Premium
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
subjectdelta said:
I just tried flashing a friend's Stock rom and this was the error I got:
--------
E: Error finishing BOOT
E: Failure at line 81:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
--------
I am now working on flashing CM7 just to see if that one works. I don't know if the error I received above is relevant to the problem I've been having.
Update on flashing CM7: I tried flashing CM7/Gapps and hit reboot system then it would show an icon, boot into the white HTC screen, then boot back into the recovery mode. Am I not installing CM7 correctly?
Click to expand...
Click to collapse
Are you wiping fully between installs? It seems like your boot partition may be corrupt... or getting there, if that's possible. Try wiping everything, boot included, and flashing again. The only other thing I can think to do is unroot & go back to stock, then reroot & try again...?
Hi My GNex is rooted.... and I've been running a Modoco ROM for 3 months with no problems. Recently I flashed his latest after a wipe and reset.... it worked fine for a day until this morning when I get continual reboots!
I wiped again completely tonight and installed AOKP ROM and it was fine for an hour or so, now its started rebooting again... what should I do?
Should I try and return it to Samsung... I'm guessing I'll have to flash stock and unroot (if thats possible?)
Thanks
What stage does it get to before it reboots again? (Google Logo or Animated splash or in the OS?)
mine on stock done it and now on google logo, re flashing stock images now, takes the piss abit.
These things happen. Frequent nandroid backups are highly recommended
It boots to the OS, then its fine for 30 minutes... reboots, then typically the reboots start to become more and more common!
I've just tried the superwipe script and reflashed again. I'll try going to stock otherwise.
I did a Nandroid by when trying to recover it said there was a check-sum error or something!
Did it say there was an error restoring data?
This happened to me, essentially the data partition had become corrupted, and no amount of custom ROM flashing would help. I had to flash stock images to fix, as I could not restore any back ups I had made.
Make sure you back up your SD card contents, as it's wiped during a factory image flash.
Sent from my Galaxy Nexus using XDA App
I think that's what I'm going to have to do
Though I don't get any messages saying there's an error restoring data!
It sounds like you have an issue with your recovery. Reflash CWM see if that fixes it and make sure its the right version GSM or CDMA!. I'm 90% sure that will fix it. (After that flash rom and wipe data.)
If its a corrupted data partition then MAYBE fastboot oem lock and then oem unlock may fix it.
Just back up your sdcard contents first.
If that doesn't do it then flash the stock images.
I use rom manager premium and the touch recovery. I'm having issues installing and restoring roms. First problem is i'll download a rom, try to install, and for some reason it either completely boot loops or just goes back to cwm recovery after trying to reboot. Then when I try to restore to the backup I just made of the working rom it gives me an md5 mismatch error. I did not rename the backup file or put it into a different folder.
Twice I have gone back to complete stock, unrooted and then rooted again and tried and this same issue has come up.
I feel like this all may have started either with me trying an AOKP rom or trying a new 4.0.4 rom.
Any insight on this?
Thanks!
Try using a standard CWM recovery i.e NOT Touch! IIRC it caused a few issues in certain Circumstances
Was on 4.4.2 stock NJ2...Odin'ed a custom recovery like TWRP...rebooted.....NO IMEI and BASEBAND. That's about as simple, yet complex it gets. Tried reverting back to stock recovery in Odin, only to find that NO IMEI and BASEBAND still shows up. THE ONLY way I've successfully kept the IMEI/BASEBAND....is by keeping everything stock, from recovery to rom. Why would this be? I've even tried restoring the EFS folder....to no avail!!!! I'M FRUSTRATED!!!! My end goal is to be able to flash a rom, use TWRP/CWM, and KEEP the IMEI/BASEBAND!!!
ANY HELP? ANYONE having the same issue or fix?
THANKS!!!!!!:good:
Possible fix...
Make sure you have not used device encryption on the rom prior to your desired rom...
If you have then a device full wipe script is needed to clean up the phone prior to flashing the new rom...
(don't forget to check your SD card for encryption or data files that may be affected)...
Flash TWRP version 2.8.6.0 and flash your new rom....
Higher TWRP versions have been buggy for me...
Best I've got atm....g
It's because you are using TWRP 3.0.0.1, that one is broken
Relatively new user here, requesting assistance with an odd TWRP issue. I'm attempting to create a nandroid backup and am getting an error message which states createTarFork() process ended with ERROR=255.
Device: Pixel 3 XL, Google version, unlocked bootloader, rooted via Magisk
TWRP version: 3.2.3-3-crosshatch running from an image via fastboot boot
I was able to ADB pull the recovery.log and am attempting to figure out what is causing the 255 error, but I can't make heads or tails of what I'm seeing. Here are the previous several lines before the error in the log.
I:addFile '/data/vendor_ce/0' including root: 1
==> set selinux context: ubject_r:vendor_data_file:s0
failed to lookup tar policy for '/data/vendor_ce/0' - 'ae2a034a0014e5c2'
I:Error adding file '/data/vendor_ce/0' to '/data/media/TWRP/BACKUPS/8AAY0GHR3/1970-03-18--19-18-39_PQ1A181105017A1/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/TWRP/BACKUPS/8AAY0GHR3/1970-03-18--19-18-39_PQ1A181105017A1/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
Anyone have any insight as to what is going on here...? I'd greatly appreciate the help. Thanks!
Axelay.mk3 said:
... Anyone have any insight as to what is going on here...? I'd greatly appreciate the help. Thanks!
Click to expand...
Click to collapse
Were you at any time running a custom ROM, or have you been stock all along? Why were you backing up the Vendor partition if stock? The dedicated TWRP thread would be a much better place to ask this.
v12xke said:
Were you at any time running a custom ROM, or have you been stock all along? Why were you backing up the Vendor partition if stock? The dedicated TWRP thread would be a much better place to ask this.
Click to expand...
Click to collapse
Thanks for the response. This phone has been running a stock ROM ever since I got it (and I don't currently have any plans to go for a custom ROM). All I have done was to get the TWRP image running from the bootloader so that I could get Magisk installed and rooted. The first attempt at getting Magisk installed resulted in a complete failure and bootloop, so I had to wipe and reinstall the whole OS from a Google downloaded image. My last several phones were all running custom ROMs, so I've never actually run a TWRP backup without including every partition. Should I not be including that if this is a stock ROM...? Why would having a stock ROM prevent me from backing up a nandroid? Sorry is this is a stupid question.
Axelay.mk3 said:
Thanks for the response. This phone has been running a stock ROM ever since I got it (and I don't currently have any plans to go for a custom ROM). All I have done was to get the TWRP image running from the bootloader so that I could get Magisk installed and rooted. The first attempt at getting Magisk installed resulted in a complete failure and bootloop, so I had to wipe and reinstall the whole OS from a Google downloaded image. My last several phones were all running custom ROMs, so I've never actually run a TWRP backup without including every partition. Should I not be including that if this is a stock ROM...? Why would having a stock ROM prevent me from backing up a nandroid? Sorry is this is a stupid question.
Click to expand...
Click to collapse
It's early days for TWRP on the P3 and there are still some new challenges. As long as you stick to the stock ROM you should be ok with boot, data and system image partitions. Most ppl having problems are restoring back to stock from a custom rom. Again, please look in the dedicated TWRP thread I linked above for more on this.