Related
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
michaelm718 said:
I just tried flashing the new wimax update and it went through and succeeded, but now my phone reboots after a minute or 2 once it's fully booted. If I'm in recovery mode it doesn't have that problem at all. I'm using baked 1.5.
Click to expand...
Click to collapse
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Noxious Ninja said:
Have you tried the standard "wipe cache and data, then reflash your ROM"?
Click to expand...
Click to collapse
I have re-flashed the wimax radio and wiped the dalvik/regular chache and did a factory reset.
did you wipe? that will solve most of your problems with out the need of a thread being made.
DomSim said:
did you wipe? that will solve most of your problems with out the need of a thread being made.
Click to expand...
Click to collapse
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
michaelm718 said:
First of all, mods please move my topic to Q&A. I did not mean to post this in this forum. Also yes I've wiped everything about a million times.
Click to expand...
Click to collapse
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
xHausx said:
Did you try flashing an older version or a nandroid? If you are using clockwork make sure signature checking is turned on too, you could have a corrupted file.
Click to expand...
Click to collapse
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Edit: I fixed it by restoring google proprietary stuff(forgot the name) and restored nand. Which one fixed it? I have no idea, but it basically restored me to factory 2.1, but with root access. Mods please lock/ delete this. It's in the wrong forum and I apologize. Thank you
michaelm718 said:
I tried flashing an older version and that didn't work either. What is this thing about nandroid? How do I go about that?
Click to expand...
Click to collapse
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
xHausx said:
A nandroid is a backup of your system you can make from the recovery, it's always a good idea to make one before you flash anything. I'm not sure if that covers your radios though.
Do you use titanium backup or anything? Without knowing how your phone is set up (what recovery you are using, etc) the only thing I can think of would be to flash the engineering bootloader. That should fix it but you would have to reinstall your ROM afterwards.
Click to expand...
Click to collapse
The nandroid restore worked because I had a backup I made while following the guide. I fixed it doing that, but while trying to update the radio to the current one again figuring if it messed up I can restore it and again the same problem came up, but this time nandroid restore wont work and it's telling me to use adb restore, but adb says your device is not found.
BTW all of my phones stuff come directly from the idiot proof guide(recovery etc)
bump... I'm sorry I'm sitting here with a semi broken phone. Is it possible to download someone else's nandroid back up and install it on mine? I know it will fix my problem as it already did, but for some reason now it's telling me to do it with adb, but my usb seems to not be working either.
Hi,
I have a problem. i currently have Codename ROM and I tried to flash new clock app from 4.2. I kept doing force close, so I wanted to restore my backup and it does not work - it says "MD5 mismatch", I cannot even make another backup, it looks like recover reboots. When I wanted to flash Codename again it said to me "Installation aborted, symlink: some symlinks failed (status 7)". Any idea how to get it all back to work?
Thank you!
EDIT: Great! Now I cannot even boot the system.
devcager said:
Hi,
I have a problem. i currently have Codename ROM and I tried to flash new clock app from 4.2. I kept doing force close, so I wanted to restore my backup and it does not work - it says "MD5 mismatch", I cannot even make another backup, it looks like recover reboots. When I wanted to flash Codename again it said to me "Installation aborted, symlink: some symlinks failed (status 7)". Any idea how to get it all back to work?
Thank you!
EDIT: Great! Now I cannot even boot the system.
Click to expand...
Click to collapse
Do you have a working Nandroid on your computer that you can push back into your phone and then restore (after wiping and formatting everything)?
dirtygoldfish said:
Do you have a working Nandroid on your computer that you can push back into your phone and then restore (after wiping and formatting everything)?
Click to expand...
Click to collapse
I managed to flash Codename ROM again but it seems that my recovery has problem with backuping and restoring. In fact my backups has around 25MB. It is a problem with backing up. I found this thread but I absolutely don't understand how to fix it. http://forum.xda-developers.com/showthread.php?t=714114
devcager said:
I managed to flash Codename ROM again but it seems that my recovery has problem with backuping and restoring. In fact my backups has around 25MB. It is a problem with backing up. I found this thread but I absolutely don't understand how to fix it. http://forum.xda-developers.com/showthread.php?t=714114
Click to expand...
Click to collapse
this has been covered in several threads.
the newer version of CWM (6.x +) create BLOBS and use a combination of BLOBS and your backup data to perform backups and restores.
if you deleted the BLOB folder from clockworkmod directory, that would be your problem. stating that you think the reason your backups are broken because of the filesize is just plain wrong.
also, md5 mismatch usually has to do with having invalid spaces or characters in the backup name.
Pirateghost said:
this has been covered in several threads.
the newer version of CWM (6.x +) create BLOBS and use a combination of BLOBS and your backup data to perform backups and restores.
if you deleted the BLOB folder from clockworkmod directory, that would be your problem. stating that you think the reason your backups are broken because of the filesize is just plain wrong.
also, md5 mismatch usually has to do with having invalid spaces or characters in the backup name.
Click to expand...
Click to collapse
In fact I do not know what BLOB folder is so I suppose I did not delete it. i did not even give my names to the backups. Sooo... what shall I do? I mean, I have wiped out the ROM and now getting everything back from scratch but I think I won't be able to make backups Thanks
Try the non touch versions of cwm or twrp.
Sent from my i9250
bk201doesntexist said:
Try the non touch versions of cwm or twrp.
Sent from my i9250
Click to expand...
Click to collapse
Thanks, man! That helps. Pushing thanks button
I wanted to tryout cm10 nightly build for my s3. I backed it up and installed the rom. After playing with it, I went to restore and now it says no files found?????
Any clue how to find it?
---
Created another backup, so I was able to put my original backup in the new backup folder and restored it from cwm recovery. Worked.
Your post contains no information anyone could use to help you. Please explain with great detail what steps you took and what happened.
Aerowinder said:
Your post contains no information anyone could use to help you. Please explain with great detail what steps you took and what happened.
Click to expand...
Click to collapse
Sorry, was a bit shocked when it happened.
Well i found the back up, but when I go to CWM to restore it says no files here. But I can access them when I connect my s3 to my computer. Whats an alternate of way restoring this backup?
Where is the backup supposed to be? I have a feeling this is an emulation issue.
Aerowinder said:
Where is the backup supposed to be? I have a feeling this is an emulation issue.
Click to expand...
Click to collapse
Its supposed to be in Internal Storage/S3/Clockwork Mod/Backup
When i try to boot into recovery and restore from there it says
"Couldnt open directory"
No files found
What version of CWM are you using? Check /storage/emulated/0 and /storage/legacy/0.
Hi there,
I have spent hours trying to fix my issue that i am trying to fix and i was wondering if you guys could help me out?
A few weeks ago i went to go and plug my phone in as it was completely flat but for some reason it began some kind of boot loop where it would reach the lock screen for a few seconds and then power off again because it did not have enough power.
I left this on over night in the hope that it would charge my phone but when i tried to power it on in the morning it just got stuck at the Samsung logo. I did a quick web search and they suggested leaving your phone at the Samsung logo, clearing you cache/dalvic cache and finally resetting it. After all of the above failed i thought that maybe a a full restore in odin would work, the same thing happened when i tried to power it on.
I then went back into the stock recovery after the reset to find the error "E: failed to mount /efs (invalid argument)".
After quite some research into this i found a possible zip that may fix the issue from people having a similar issue but of coarse it diddn't work.
It seems as if the /efs folder/partition may be corrupted in some way.
I am really stuck on this now and i am reluctant to pay lots of money to someone to fix it
Do you have any ideas?
Many thanks,
Shenstone
EDIT: The phone has CWM recovery installed and i have attemped to flash the stock firmware with both Kies and Odin
Bro, maybe flash stock firmware will solve the prolem
exorcistz said:
Bro, maybe flash stock firmware will solve the prolem
Click to expand...
Click to collapse
Sorry forgot to mention that, i have flashed stock firmware with both odin and kies but both do not work, same process still occurs
Any other ideas? :/
Do you have the original EFS folder backed up? If so, then try restoring it and flashing a stock ROM... If you don't have your EFS backed from earlier you might have some problems, I don't know if it's possible to fix it then...
librapt said:
Do you have the original EFS folder backed up? If so, then try restoring it and flashing a stock ROM... If you don't have your EFS backed from earlier you might have some problems, I don't know if it's possible to fix it then...
Click to expand...
Click to collapse
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
shenstone said:
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
Click to expand...
Click to collapse
See this, http://forum.xda-developers.com/showthread.php?t=2420881
shenstone said:
I didn't specifically backup the EFS folder, however I performed a full backup in CWM recovery. Do you know if there is a backup of the EFS folder there?
Just a quick question, is it possible to re-create a EFS folder or not?
Many thanks!
Click to expand...
Click to collapse
I use this,
http://forum.xda-developers.com/showthread.php?t=2269318
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.