Rom Flashing error, recoverylog attatch - Android

http://pastebin.com/49i3epeN (line 93?)
^^Recoverylog.txt
http://pastebin.com/k6Fnxxw8
^^Updater-script
flash fails, goes back to recovery menu without any confirmation
sdcard wont mount afterward, doesnt find anyfiles on sdcard
CWM2.5
whats wrong?

Related

Vibrant acting odd

I finally flashed a custom rom Bionix 1.9 Jacs/OC/UV/VOODOO. Later i decided to flash a different custom battery icon. After i flashed the icon my phone would not stop reading/scanning my SD cards. It just kept goin in a loop. I decided to run my back up i made on Rom manager. That just soft bricked my phone. I attempted a factory reset but that failed as well. Then i tried to flash the Bionix rom again but it wouldnt run all the way. Later i was advised to use ODIN. I followed all the steps correctly when using ODIN. That didnt help either. Sooo after all that and my phone still being soft bricked i decided to try the factory reset again and then i installed the Bionix rom again. That seemed to work. My phone turns on and functions. Feels a lil slow and when i try to install an app it says i need to free up space on my SD card. (there isnt anything on either SD cards)
Some of the errors i recieved:
When trying to flash Bionix i get this:"failure at line 80:" "copy_dir PACKAGE:data DATA: Installation aborted.
Oh and when i tried the restore option it says the following: Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure
Restoring cache... sd-ext.img not found. Skipping restore of /sd-ext/.
Restore complete!
No no app2sd partition found. skipping format of /sd-ext.
E:Failer at line 79
Help this noob out please. Id appreciate help from some knowledgeable ppl.
You must disable Voodoo before flashing anything. So that is why you got into a soft brick When you Odin'd, did you follow the steps below? It was highly advised by Sombionix to read his whole post before flashing.
Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
Fix 1:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Fix 2: (use only if you know how to use adb commands)
1. Place the 'disable-lagfix' file in your sdk>tools directory
2. Get into clockwork recovery like you normally would
3. Follow these adb commands to push the 'disable-lagfix' file to you sdcard>voodoo
adb push disable-lagfix /sdcard/voodoo
4. File should now be on your sdcard in your voodoo folder.
5. Reboot phone and with luck, you should hear Linda the robot telling you your file system is being converted back to rfs.
6. Because your system directory has already been wiped, you'll still get a black screen when you reboot, but your file system is back to rfs. Just pull the battery, and reflash whatever rom you want. Then reboot again.
Hope that helps

[Q] Boot Loop

I have the 10.1 16 Gb / Us version rooted with "in Paris" ROM and after using the option to hide the User Bar and after unhidding it the theme went black (not the first time) and the power menu become unaccesible because every time i hitted it, the screen turns off but without locking so pushed the power button for 10 second and restared but now it just boot loop, im able to acces clockwork recovery and odin but dont know what to do. I tryed erasing cache, dalvik, wipe data, etc but nothing seems to work. So anyone willing to help me?
zaror1992 said:
I have the 10.1 16 Gb / Us version rooted with "in Paris" ROM and after using the option to hide the User Bar and after unhidding it the theme went black (not the first time) and the power menu become unaccesible because every time i hitted it, the screen turns off but without locking so pushed the power button for 10 second and restared but now it just boot loop, im able to acces clockwork recovery and odin but dont know what to do. I tryed erasing cache, dalvik, wipe data, etc but nothing seems to work. So anyone willing to help me?
Click to expand...
Click to collapse
Have you gone into CWM and just reflashed the ROM?
I would recommend that once you get back up and running, you flash back to stock, flash the stock recovery on there and do a full wipe. Then follow the procedure to get CWM and a clean install of "In Paris". Then DO A BACKUP in CWM. Next time you will just have to restore your backup should something like this happens. (You backup/restore thru CWM)
i cant flash any rom because i cant acces the /sdcard because only after booting up it can be mounted, since it wont boot i cant mount it.
BTW: im a total noob regarding ADB but i installed the SDK and i couldnt push files because it says "/shbin/sh "command" doesnt exist"
im spanish so my english is not perfect, sorry for that
update: I managed to push two .zip's to "/sdcard" and "/mnt/sdcard" but when trying to "install zip from sdcard" in CWW it says "no files found", so i pushed the same .zip but with the name of update.zip and tryed "apply update from sdcard" and it says "failed to open /sdcard/update.zip (No such file or directory"
i tryed the adb command "adb shell mount /sdcard" and it says "cant find /sdcard in /etc/fstab" and the same thing with /mnt/sdcard
so my guess is that /sdcard its not mounted because when trying to install the .zip it doesnt even let me browse the sd
Please help im desperate
solved
after many hours of searching i realized that when pushing files i did not write it correctly
what i did:
adb push update.zip /sdcard
what should be:
adb push update.zip /sdcard/update.zip
i dont know why CWM didnt let me browse for .zip files in sdcard but i dont care sinc i fixed it. thanks anyway
zaror1992 said:
after many hours of searching i realized that when pushing files i did not write it correctly
what i did:
adb push update.zip /sdcard
what should be:
adb push update.zip /sdcard/update.zip
i dont know why CWM didnt let me browse for .zip files in sdcard but i dont care sinc i fixed it. thanks anyway
Click to expand...
Click to collapse
sorry i couldn't get back to you sooner, i'm glad you got it all squared away.

Frozen static screen help!

I need help to fix my tab,
I've been running pershoots OC kernel with task's roms for several months with no problems and i've been keeping up to date with each version with out any problems.
I just rebooted my tab today and now suddenly out of the blue, the screen shows static and corrupted rbg lines after a few seconds of the samsung logo. And now it is stuck like this after repeatedly trying to turn my device on. I can get into CWM recovery but i dont a restore file on it because i moved them off my tab to my PC to save space.
Is there anyway to move the files back on to the tab to restore it or maybe move the stock kernel so i can flash it and see if that fixes it?
If you don't care about the data in your tab (all your apps and the /sdcard partition), you could try returning to stock via Odin. Here is a good guide (is the last part "Re-“Stocking” Yer System…"): The Guide
Other option (I recommend this one) is adb, in cwm just push the files you want to flash to the /sdcard .
Thanks! I'll try by android debug bridge and see if i can figure this out..
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Mercatorn said:
I have adb installed and it works but when i push the zip to /sdcard/ it doesnt show up on CWM install zip from sdcard menu option, i also tried to push it to /mnt/sdcard/ and the files doesnt show up.
I'm at a loss here the cmd prompt doesnt give any errors after the zip transfer
Click to expand...
Click to collapse
Are you mounting the partition? My guess is you forgot to do it.
Enter the follow commands (one by one) in the terminal (cmd prompt):
Code:
adb shell
Code:
mount /data
Code:
exit
Code:
adb push fileyouwanttoflash.zip /data/media
Now the file should be in /sdcard, just install it from cwm.
If at the moment you're trying to choose the zip from sdcard you get an error telling you "Couldn't open directory" and "No files found", reboot cwm.
Other way to do it is in cwm (so you don't have to do the "adb shell" and "adb mount")
In cwm, choose "install zip from sdcard", then "choose zip from sdcard", then "+++++Go Back+++++"
And from your cmd promt:
Code:
adb push fileyouwanttoflash.zip /sdcard/
Now, flash the file from cwm. (Again, if there's some error, reboot cwm).

[Q] Help with bootloop

Heu guys,
So after using cyanogenmod9, i felt like reverting tp stock.
Sp i got my kernel (xwkk2) and flashed it with odin. Now im in a bootloop. How the bejesus do i fix this?
Thanks
When I got in a boot loop two days ago all I did was wipe data, wipe cache, wipe dalvik cache and install a new ROM instead. If you don't have a removable microSD to put the ROM I suggest you look for the ADB Push tutorial. After your phone boots up try to install a stock Rom.
I don't if this helped but it worked for me.
Sent from my GT-I9100 using XDA
did you just flash a stock kernel? If so, you would get a bootloop as samsung kernels arent compatible with CM9.
Flash the entire rom instead of just the kernel.
ADB PUSH TUTORIAL (quoted from @brewtaz)
Requirements:
Unlocked Bootloader/Rooted Device
CWM Recovery flashed from fastboot.
Basic knowledge of adb/fastboot commands
Steps:
- Download your ROM of choice (referred to as ROM.zip) and place it wherever your ADB is on computer's harddrive (referred to as c:\AndroidSDK\tools)
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working SGS2 running whatever ROM you decided to flash.
I hope this HELPED.
Thanks for this information goes out to doktortaru, strker45, and torxx.
Sent from my GT-I9100 using XDA
All that or simply using cwm format system
Thanks to @brwetz for the above quoted info...!
Sent from my GT-I9100 using XDA
sweet thanks guys!
haaha it ws actually all coz didnt format /data... GAH
Thanx for tutorial...

Filesystem seems to be damaged

Every time I try to install a custom rom, my device gets bricked. I'm stuck in a bootloop and TWRP tells me, that /data is unusable and /system can't be unmounted.
Right now I get I back to life, if I change the filesystem in TWRP for /data from f2fs to ext4 and back. After that /data is empty, but usable again. To get /system back to work, I erase it with "fastboot erase system". Then I reboot TWRP and reinstall STF-L09 8.0.0.360(C432) with zxz0O0s HuRUpdater. The logfile for the installation is attached with the title "Log during installation.zip".
After the installation I do a reboot and go through all the setup stuff of Android (WLAN, do you want to use..., etc.). Then everything seems to work fine. I can use the phone and reboot without a problem. But if I start TWRP, there are error messages about it can't unmount /system. I attached that logfile with the title "Log after Installation.zip". If I try to install an OTA update it gets bricked again.
No matter, how I try to install the custom rom, or how I reset my phone after it gets bricked, seems to make a difference. To me it seems like, either a problem with the file system, or a driver problem. But I'm not sure, because I'm more experienced with PCs. If I would have such a problem with a PC, I would erase everything and do a fresh start. But I don't know how to handle this here.
Please help me, to get out of this bricking cycle, before I can build a wall.
Status Update 1:
I went back to STF-L09C432B120 (Android 7) with this method: https://forum.xda-developers.com/showpost.php?p=75084955&postcount=17
All credits to gaguga:
Rollback from 8 android to 7
1. Place the firmware files of ?any? android 7 update.zip, update_data_public.zip and update_all_hw.zip in the HWOTA8 / repack folder. (I used STF-L09C432B120)
2. Run the bat file "repack" to repackage the zip files. This will prepare our firmware
I had a problem with this and had to update the file META-INF\com\google\android\update-binary by hand.
3. Create the folder "HWOTA8" on the SD card. (Without quotes)
4. Place the archive hwota8_update.zip, STF_RECOVERY8_NoCheck.IMG (from the HWOTA8 folder) and the three update archives (update.zip, update_data_public.zip and update_all_hw.zip (from the repack folder after repackaging)) to the "HWOTA8" folder on the sd card.
5. Boot into the TWRP
6. Install the hwota8_update.zip file which lies in the HWOTA8 folder on the sd card. The phone will reboot into the recovery mode and install the update automatically.
7. After the rollback, boot into recovery and make a reset
This was the first time, that I was able use the original recovery without problems.
I think I will try to do a rebrand at the weekend.

Categories

Resources