Hi, my problem is can get into stock recovery but download mode shows a blank screen and Android OS will not boot. I had TWRP 3.0.2.0 as my recovery, but stupidly re-flashed the stock recovery so I could do a factory reset too see if it changed anything as I did soft brick the device by modding the boot partition to attempt to get a systemless root prior to flashing the stock recovery back over TWRP. I have a full nandroid backup from TWRP before I did any flashing or changes to the boot or system partitions. Any help or guidance would be appreciated.
Problem solved, I fixed it myself, close this thread. Q&A, Help & Troubleshooting section, more like no one gives a f**k, just repair the issue yourself, we can't be bothered to help, looks like I know not to turn to XDA for help with any issue in the future.
You could explain how he got back?
I have made a backup with TWRP 3.0.2-0 but when trying to reinstall it gives me the error extractTarFork () process ended with error : 25
luispelau said:
You could explain how he got back?
I have made a backup with TWRP 3.0.2-0 but when trying to reinstall it gives me the error extractTarFork () process ended with error : 25
Click to expand...
Click to collapse
I have had 0 problems restoring or backing up on my device when I was testing prior to uploading, however some questions for you since my brain and google is turning up nothing on the error but it does show extractTarFork () error 255.
Is there enough space on the /Data partition? < related to error 255 according to Google
Has the backup been successfully verified using a md5 checksum?
Any chance that the tar files were corrupted or the backup was half complete due to no space left on the chosen storage device? - Like you ran out of space while backing up and thought it was done?
I back up on a memory card 64 Gb, it was successful and trying, without leaving the recovery, reinstall the backup was not possible. I do not know that it could fail.
Related
***************SOLVED*******************
Hey, hoping some android gurus can help me out here.
I had the latest version of Obsydian on my phone and have not had any issues. Yesterday, my battery on the phone died, and when it started up again I was getting forcecloses all over the place. Tried reinstalling the rom and go errors, tried a different rom and got errors. So I ODINed the Voodoo RFS fix, followed by stock+Voodoo-Froyo-T959-UVJL5.tar , and didn't get anywhere.
I thought there might have been something wrong with the data on the phone so i tried clearing and formatting everything through Clockwork recovery. Then I tried the partition SD Card through clockwork recovery. I assumed it was the EXT-SD it was formatting so i chose 128mb ext, 32 swap, and left the rest for fat32. However, I'm starting to think it might have been the internal SD card.
I tried ODINing back to stock stock using this guide: http://androidspin.com/2010/08/09/h...droidSPIN+|+Your+No.1+source+for+Android+news.)
I get the phone in ODIN and it flashes, no errors in ODIN, but when the phone leaves download mode and goes to installation it gives a few errors:
Code:
MBR Checksum Error
Movinand Checksum Confirmation Fail
Then it continues installing, and I get another error:
Code:
Wiping data
Formatting Data
[B]Data Wipe Fail[/B]
Formatting Cache
It still acts like it completely finishes the installation, reboots, I get the Tmobile boot and then Galaxy S, and then I get a black screen with all 4 of the lights/buttons on the bottom of the screen on. It can sit like this for 30 minutes, it doesn't do anything.
I still have access to download mode, and I still have access to recovery, however it's no longer ClockworkMod recovery, it's the stock recovery, and it seems to only work for a few moments before going to a triangle with an exclamation point and the android logo.
Any ideas on what I can do to make this phone functional again, or acceptable for a warranty return?
I appreciate any help.
Welcome to the club
Check out my post http://http://forum.xda-developers.com/showthread.php?t=887837
Post #3 it might help if it does let me know so we know for sure if it works
Yes welcome to the club!!! glad you could join us!
Anyways here is what I have learned/done, my only working rom currently is the eugene froyo, can use the phone and data BUT cant download anything or install anything. You can adb push apks into the rom though. Heres the link for it
Use Odin, pit=512, pda=eugene..tar Run this to get semi working rom
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
Once here I have access to my Sd card, this is where I placed the clockwork recovery on as an "update.zip" Link to this is posted below
http://forum.xda-developers.com/showthread.php?t=734164
Boot into recovery, note this will take you to stock recovery. REINSTALL update, may have to do this twice but itll get you to the Clockwork recovery....
After this I tried to install two different roms and both times I get some sort of data error, and installation aborted....hopefully this will help a few people
Yeah a bit more google searching for "vibrant mbr checksum" brought me to the same conclusion, that I needed to ODIN the eugene's froyo - it's flashing right now. Will see where that gets me.
It's my belief that using the SD partition in CWM is what caused the MBR issues and the Data Wipe Fail, as others said they messed with a partition in either CWM or something else prior to this happening
And that's a no go. It just reboots back into the stock recovery every time after odining it, with some new errors.
update media. please wait.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:copu_dbdata_meda:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
I take it back - i did the wrong one apparently.
Had to use the files located on the link you sent, inside of the Eugene_2E_JK2_Froyo.zip file. Apparently there are a few different download files on the first post of that link. This one took longer than all the others I'd tried ODINing, about 5-6 minutes, compared to 2-3 for the others. I had also updated my Odin3 to v1.7, from the v1.3 I was using before.
When it booted up, it gave me an issue with my external SD card, said it was formatted incorrectly, so i formatted it from the phone - it says I have 13gb memory and 1.86 on the ext-SD.
Was able to download and install ROM manager from the market. Attempting to install Nero v3 now.
*** SOLVED ***
I've succesfully installed a rom other than Eugene's froyo, and did not receive any installation errors! Got Nero V3 up and running, very happy.
Note that the MBR checksum error still appeared but did not affect installation at all. Thanks everyone for their help - hopefully this helps the others.
Hei,
I was running 4.3.1 Dirty Unicorns and wanted to flash Smartdroid.
So, flashed Devil recovery and tried to flash the ROM.
It gave me message that there's an error in the zip file.
I was just playing with the options available in the recovery and selected some option, which I don't remember now.
After that, the went into bootloop. "Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
This loop continued.
The phone could be put in Download mode.
Then, I flashed CWM 6.0.4.4 and flashed 4.1.2, which I downloaded some time back.
It went on well. I could boot the phone and had set it up.
However, I couldn't connect to network.
The IMEI was some default one.
Rooted the phone and tried to restore the backup of efs folder using HC-Ktool.
After restore, when I booted the phone, it didn't boot.
"Samsung Galaxy S3 I9300" appears on the screen and the phone reboots again and again.
I tried flashing the ROM again, CWM again etc etc.
Nothing worked.
In one occasion, after installing CWM 6.0.4.4, I restored from NANDROID backup. Restore was successful.
But, it wouldn't boot.
Same "Samsung Galaxy S3" appears on the screen and the phone reboots again and again.
Once, I flashed Dirty Unicorns ROM from zip via CWM. Still the same.
What is happening and how to solve it?
Any help is greatly appreciated.
Regards,
Babloo
Wipe Data/Factory Reset -> Download mode
Flash latest Android 4.3 from Sammy through Odin, preferably XXUGMK6 or newer.
Hei,
This worked!!!
Thanks.
Why flashing 4.1.2, Dirty Unicorns didn't work and this one worked?
If you can explain, that will be helpful to all.
Now, though the phone is booting, the efs folder is corrupted.
IMEI number is not what it should be.
I have a backup of the efs folder taken using HC-Ktool long back.
So, the ROM on which efs folder was backedup will be different that the ROM I have now. (Does it make any difference?)
Can I just root and restore that efs folder using HC-Ktool?
Thanks for the help!!
Regards,
Babloo
Edit:
If I flash CWM Recovery 6.0.4.4 and restore the NANDROID backup that I took before I started screwing my mobile, will everything be fine?
Sounds like you tried to flash a corrupt file, always check the md5 before you flash.
EFS is totally separate to the rom, format the partition, restore your backup then factory reset should return your imei on the current rom.
Nandroid will not fix the efs, unless you used a custom backup process that included the partition -the default settings would not do this.
Hei,
"format the partition, restore your backup"
For this, can I just root the phone and use Ktool to restore backup?
If you suggest any other procedure, pls give me more info.
-Babloo
Hei,
After the previous post, I could restore my phone from NANDROID backup that I took yesterday, before the whole mess.
After that, I tried to restore the efs folder using HC-Ktool from efs.img.
It gives the message that restore is completed.
But, after reboot, the IMEI remains the same wrong one (the generic 004999...)
The size of efs.img is 20.48 MB.
I tried to restore using the terminal method.
With the command "unmount /efs" I get error message "sh: unmount: not found"
How can I restore the efs and get back my IMEI?
When I tried to "open" the img file in Windows, it couldn't open. It says that the file is corrupted.
Could it have been really corrupted or it is just that Windows is unable to open it?
I restored the efs using the same backup file.
Why is it not working now?
-Babloo
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Hei,
boomboomer said:
You are trying to skip essential stages and hurry to finish, but your partition is still corrupt -you can't restore anything to a corrupt partition.
Search and read someone who has succeeded doing the same thing, follow their guide exactly.
Click to expand...
Click to collapse
I have been searching for a proper procedure to format the efs partition since your post.
Whatever I found didn't work for me.
Can you please point me to any post that you know?
-Babloo
Guys,
Any ideas?
-Babloo
I tried to do a full nandroid backup but it failed saying that "error while making a backup image of /data". The progress bar while taking backup of data went from 0% to 90%, then paused for some time, and then went to 100% and then I got the error. In the clockworkmod folder, I saw that two files related to data were made, one of around 500MB and the other of around 0.9GB. So the backup seems to fail in the end. Some History: Last time some months ago, I had tried to restore a backup but was getting md5 mismatch so I had edited the file and put the correct md5 for one field, others were correct. Then the restore was successful.
I am also attaching the log and other details:
Phone: Samsung galaxy Note N7000
ROM: CM11 of June, 2014
Log is attached with the name of "recovery.rar" and here's the link to the log as well:
http://paste.ubuntu.com/8520572/
usman farhat said:
I tried to do a full nandroid backup but it failed saying that "error while making a backup image of /data". The progress bar while taking backup of data went from 0% to 90%, then paused for some time, and then went to 100% and then I got the error. In the clockworkmod folder, I saw that two files related to data were made, one of around 500MB and the other of around 0.9GB. So the backup seems to fail in the end. Some History: Last time some months ago, I had tried to restore a backup but was getting md5 mismatch so I had edited the file and put the correct md5 for one field, others were correct. Then the restore was successful.
I am also attaching the log and other details:
Phone: Samsung galaxy Note N7000
ROM: CM11 of June, 2014
Log is attached with the name of "recovery.rar" and here's the link to the log as well:
http://paste.ubuntu.com/8520572/
Click to expand...
Click to collapse
I'm not the best at reading logs (stll learning), but the one thing that sticks out to me is the fstab errors. Have you used a mod /app / script to swap your storage points perhaps?
If you haven't done anything like that, then I would suggest checking out another recovery and see if you have the same issue. Either Philz, which is based off of CWM, or TWRP (my favorite).
Hello i have messed up real bad, i flashed a philz recovery which I had used in a stock based rom and the backup was successful but then the phone couldn't boot up. So i restored the boot patrition from a previously made backup. This way i successfully booted up my phone and got previous recovery. So far so good. Now i knew that the problem is in recovery. I also had a raw kernel file which I had used to flash the cm11 rom so i flashed that kernel. But then i restated device to find out that i have now lost root access. I tried flashing super su via raw kernels twrp recovery but I saw no effect despite it being flashed. I cannot flash the recovery because the curreny twrp recovery crashes when i try to flash that.
Current situation is that I am getting constant unlimited, system process is crashed, errors and I can see no signal from mobile operator. Wifi is working fine.
Sounds like it might be wise to restore to stock and start over.
Tried to flash a latest version of cm11 and now booted up correctly. root checker says I am rooted.
got latest cwm as well
Now I need to take backup to see if the initial problem is there or not.
Good deal. Glad you're back up and running again.
I was trying out some ROMs. At first it was fine. Then when I flashed a particular ROM, I started getting "INVALID IMEI" and could not connect to the network anymore.
Luckily I had a full backup of the phone taken with TWRP. I could not see my backup listed in the TWRP that came with the present ROM. So I flashed the Recovery with which I backed up the phone. (TWRP_v2.7.1.1_P780_ROW_KK_Corrected found in stympy's KK rooting tutorial) Then I could see the Backups listed.
When I tried to restore it, it failed with this error:
Code:
Unable to mount '/data'
I guess the partitioning changed. Anyways, I could restore 'Nvram' alone and the INVALID IMEI got replaced by "EMERGENCY CALLS ONLY".
How do I fix this? Can I somehow restore the backup (by fixing Unable to mount /data)?
This is what I am intending to do. Flash a working ROM again (http://www.needrom.com/download/ultralight/), but using my old partition table (the corresponding scatter file would be one among the three provided by stympy in his KK rooting tutorial), and then attempt a restore from TWRP.
daltonfury42 said:
I was trying out some ROMs. At first it was fine. Then when I flashed a particular ROM, I started getting "INVALID IMEI" and could not connect to the network anymore.
Luckily I had a full backup of the phone taken with TWRP. I could not see my backup listed in the TWRP that came with the present ROM. So I flashed the Recovery with which I backed up the phone. (TWRP_v2.7.1.1_P780_ROW_KK_Corrected found in stympy's KK rooting tutorial) Then I could see the Backups listed.
When I tried to restore it, it failed with this error:
Code:
Unable to mount '/data'
I guess the partitioning changed. Anyways, I could restore 'Nvram' alone and the INVALID IMEI got replaced by "EMERGENCY CALLS ONLY".
How do I fix this? Can I somehow restore the backup (by fixing Unable to mount /data)?
This is what I am intending to do. Flash a working ROM again (http://www.needrom.com/download/ultralight/), but using my old partition table (the corresponding scatter file would be one among the three provided by stympy in his KK rooting tutorial), and then attempt a restore from TWRP.
Click to expand...
Click to collapse
Update TWRP!
Link Here! TWRP 2.8.4.0 rev.2
stympy said:
Update TWRP!
Link Here! TWRP 2.8.4.0 rev.2
Click to expand...
Click to collapse
I've tried TWRP_v2.7.1.1_P780_ROW and TWRP_v2.7.1.1_P780_ROW_KK (using the scatter which came with the ROM, ultralight) and they give the same error during backup.
daltonfury42 said:
I've tried TWRP_v2.7.1.1_P780_ROW and TWRP_v2.7.1.1_P780_ROW_KK (using the scatter which came with the ROM, ultralight) and they give the same error during backup.
Click to expand...
Click to collapse
I think your storage partition is corupted!
Try to flash again your stock firmware!
[HELP] failed TWRP restore,
now no wifi, no recognised sim,
have factory reset but as no recognised sim or wifi unable to activate then starts to boot loop .
if restore old data and system and EFS. still no wifi or recognised sim
history of problem:
i was on original miui that shipped with phone. had a failed update (OTA) yesterday and lost root. was trying to get root back. but was getting lots of errors so restored system then first restore failed.
not sure if it has deleted the modem partition which needs to be restored but not sure what that partiition is called in miui.
any ideas?
I think there was a problem restoring the 'firmware' partition that caused the problem.
Just flash firmware file and then restore... (Never restore firmware)
I would flash a MIUi ROM via fastboot to make sure that you have a "clean" installation.
Restoring wouldn't work.
Eventually downloaded a new ROM (globe ROM) and installed it
AbuYahya said:
Restoring wouldn't work.
Eventually downloaded a new ROM (globe ROM) and installed it
Click to expand...
Click to collapse
when u reflashed the globe rom did the wifi and sim card work already? i have similar issue
just download the modem files. flash the zip through twrp. everything will be back.
Yo, I've made an How To fix it.
LINK
Hi All,
I see a eye or ra symbol with loading fire on my phone after custom rom installation. could you some one help me what does this means and the phone not starting.
update--
This symbol is of crDroid operating system. Now the problem is i cannot goto TWRP and the system is not booting up.
There is some problem with crDroid operating system. Its been an hour the same eye or ra symbol loading and not booting up. How to stop this can anyone help me on this.
Thanks