Related
Tried ROM Manager backup of factory ROM.
Now, I power on and get CWM recovery. Choosing reboot always returns me
to CWM recov. I read every thread in this forum that refers to
loop, brick, etc. I have various backups, but I don't know what they
are worth, best way to use them. How to get out of the boot loop?
Best outcome would be to recover my last stable state. Factory reset
would be ok. Hardbrick would be a drag.
* Bought factory unlocked G-ST6500D (no vendor) in Spain.
* Have current non-root backups of contacts, sms, media, calendar, etc. on
laptop.
* Installed CWM v5.0.2.8 with Odin (three yellow boxes appeared in odin,
FWIW), and rooted. Froze bloatware listed by some people as safe, but
did not delete any factory installed software.
* Wanted to have a stock ROM backup before I did anything else. It's
not clear to me whether it is best/possible to download one or create
an image from my device. Started reading/trying backup apps, but I
don't really know what each one does.
* Did a full backup, apps + data, to extSD, and copy to laptop with Titanium
backup (free). This wrote >1000 files.
* Did most complete (as best I could tell) backup to extSD and laptop
with Online Nandroid app. This wrote boot.img, cache.ext4.tar,
data.ext4.tar, nandroid.md5, recovery.img, system.ext4.tar. Can these
be used to restore ?
* Tried to backup the ROM with ROM Manager app, but could not find an
option to backup to ext SD, only int SD. There was only 200MB free, so
I knew this would fail. I choose this anyway, hoping it would realize
there is not enough space and offer to change the path. The phone
rebooted into CWM and began a backup. After a few minutes, it printed
an error message and told me where a log was written, and rebooted
into CWM recovery. I tried rebooting, holding buttons, removing
battery, etc. Always returns to CWM recovery. Tried the 'backup and
restore' menu hoping it would give info on the backup. Instead, it
immediately started another backup, this time showing 1GB intSD
free. This backup reported success, then reboot into CWM recov.
* Since then, from CWM, I did 'wipe cache partition' and 'wipe davlik
cache'. Did not yet try factory reset.
* Show log ends with
"skipping exectuion of extendedcommand, file not found"
I read that sometimes it is possible to exit a boot loop without
flashing anything. If that is not possible, I guess I should do
factory reset. If that does not work, then I guess I should try
restoring something somehow: Use CWM recovery to recover nandroid
backup from extSD? Or install something via Odin ? For any solutions,
I am more comfortable doing things from linux than MSWin, but I think
that is not possible. Do I have to race to solve this before the
battery runs out?
Thank you for reading.
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
midzan21 said:
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
Click to expand...
Click to collapse
Thanks. I just figured that out after a several hours of reading. Finally saw stories on the thread
introducing CWM 6.0.3.3 of people who never flashed a ROM and still had boot loops.
I was on the wrong track because I assumed it was the filled up int. SD causing the
problem. I still have to fix that, but my phone is running. It would be nice if ROM Manager or CWM calculated the space
needed and refused to start if insufficient. But, I understand that there are few good devs and much to do.
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
ukppete said:
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
Click to expand...
Click to collapse
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
freakymod2120 said:
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
Click to expand...
Click to collapse
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
ukppete said:
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
Click to expand...
Click to collapse
SOLVED
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
freakymod2120 said:
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
Click to expand...
Click to collapse
No Prob...
Nice to know i could help ...
Good instruction about flashing ...:good:
ukppete said:
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
Click to expand...
Click to collapse
Hey guys,
I was having serious issues getting my Allshare Cast dongle to work with my rooted Note 2 (N7100). It either broke off the connection because of the flash counter or (even worse), when I ran TriangleAway beforehand, always rebootet my phone.
I've dug through countless threads addressing this issue and offering all kinds of different until I was finally able to make it work - still being rooted and using a custom rom. So I thought I'd just share my solution with anybody here who may find it useful.
*Edit*
Seems like Allshare Cast still tends to be a bit picky. The first connection is stable, but a second one reboots my phone after a few minutes. Quite annoying, but at least it works.
As usual, I will not be held responsible for any damage that might occur, so don't blame me if your phone blows up itself, or your house. :angel:
This works *for me*, other phones might yield other results.
These are step-by-step instructions if you're coming either from a f%*'ed up ROM that needs major repairs anyway (like me), or from a different android version. If you're running a 4.1.2 ROM you can try to jump directly to step 2. c). Still, I'd suggest you backup everything, see below 2. a)
Here we go:
1. Things you'll need:
a) Wanamlite 3.9 (http://wanamlite.com/2013/07/19/wanamlite-mg1-v3-9-android-4-1-2-clean-stable/) by Wanam (who saved me from ruining my phone btw: tried Wanamlite 4.2 with new bootloader, and without his warning, I would've used the MK4 bootloader instead of MJ5 and would've been stuck with Android 4.3/Know forever...)
b) Adam Kernel v2.7, Odin and/or CWM version (http://wanamlite.com/2013/07/19/adam-kernel-v2-7/) by Wanam
c) Stock recovery, kernel, etc. (http://forum.xda-developers.com/showpost.php?p=31986738&postcount=7), provided by dr. ketan. I'm using this one: http://d-h.st/gwn (Stock Recovery/Kernel/Modem from XXDMB6 19th March13)
d) Mobile Odin (http://forum.xda-developers.com/showthread.php?t=1347899) by Chainfire
along with the FlashKernel file (MobileODIN_FlashKernel_N7100-v5.0.apk) further down on the same page. if v5.0 doesn't work, try v4.0 instead.
e) TriangleAway (http://forum.xda-developers.com/showthread.php?t=1494114) by Chainfire
f) I'm assuming you're already rooted and therefore have a working CWM/TWRM running.
2. What to do (step-by-step):
a) I'm being a bit paranoid by now, but for various good reasons. These instructions may be a bit overcautious, but at least your data will be safe from being accidentally erased. Trust me, you do not want that ever to happen... :crying:
Also, I always carry a ROM with me so I can repair my phone on the go. So of course, you can also do the flashing via PC Odin, but I prefer the CWM method I've described further down.
- backup everything. And I mean EVERYTHING! I did a full backup, i.e. Titanium Backup, TWRP backup, and I copied the whole contents of my internal and external SD cards to my PC. I'd even suggest you use another extSd during this process (which will save you from the hassle of copying the whole thing btw). This whole backup thing took me about 2-3 hours, but I would've gone mad if I'd lost either internal or external SD data.
- copy Wanamlite 3.9 onto the external SD your're going to use.
- power off your phone (take out the battery to be sure)
- take out your external sd to protect all your precious data. Just in case you accidentally do something wrong and end up formatting the extSd (in TWRM, this option hovers dangerously between "Factory Reset" and "Format Data")
- boot into recovery and do a full wipe (Wipe Cache / Wipe Dalvik Cache / Factory Reset / Format Data)
- power off your phone (take out the battery to be sure), re-insert the external SD
- boot into recovery and flash Wanamlite 3.9 (follow the instructions on his site). Be sure to chose Adam Kernel and checke "Allshare Cast" during the installation process. The Adam Kernel works best with TriangleAway, because (unlike the stock kernel provided with his ROM) you can reset the flash counter without rebooting.
Now you have an absolutely clean 4.1.2 rooted custom ROM running on your phone.
b) Restore your data.
- run Titanium Backup, and restore everything that's important (all user apps w/ data, call logs, messages, email etc.). I'd suggest you just leave out system apps if you're coming from another ROM. You can try to restore everything of course, worst thing to happen is that you'll habe to re-wipe and then re-flash the ROM. In my case, it was no problem, because I had made my backup from this very ROM version.
- Next, copy at least the "Android" folder (containing /data and /obb) from your backup back to your internal SD card. By default, TB doesn't backup large files and folders, so all the bigger apps (like e.g. games) are still missing. If asked to overwrite, simply say "yes". If you want to make sure everything's back to how it was before, copy your whole internal SD backup back to your phone.
c) You've spent an awful lot of time by now, and still, Allshare Cast won't work. So let's go for it:
- install Mobile Odin and the appropriate Flashkernel.apk
- install TriangleAway
- unpack and then copy the contents of "Stock Recovery/Kernel/Modem from XXDMB6 19th March13" to your internal or external SD card (doesn't matter which one).
- run TriangleAway. It should read "Counter: 1 /Binary: Custom".
- tap "Reset flash counter". TriangleAway confirms that the counter was reset to 0 and closes.
- restart the app. Now you should see "Counter:0 / Binary: Official".
- run Mobile Odin, chose the stock kernel (tap "Kernel" -> "[path where you stored the kernel.tar from the archive]")
- tap "Flash Firmware". Your phone will reboot.
Congratulations! If you did everything correctly, you should now be running Wanamlite 3.9 (JB 4.1.2) ROM with rooted stock kernel. Allshare Cast works like it should. FIFA14 or DIII4A are really fun on a 40" screen.
If you don't want to use the stock kernel all the time, flash Adam Kernel v2.7 through Mobile Odin or CWM. Allshare Cast functionality will be broken, but you have all the nice benefits of the custom kernel like STweaks or BoefflaSound. To make Allshare Cast work again, simply repeat the last five steps from above: "c) - run TriangleAway... etc."
That's it. I hope this is helpful! Suggestions are welcome. If something's missing, or if I posted anything dangerous, please feel free to scream, and I'll correct it ASAP.
Cheers,
- Alex
Thanks for the nice review. I have these and wholeheartedly recommend them as well.
does anyone know how to update Allshare Dongle via N7100?
I've had many ROMs and on every single one I have message that update was downloaded and to restart the dongle, but after I restart the dongle it connects again with the same message, so it is infinite loop. I can connect, but sometimes it laggs, so I assume that newer firmware would fix that issue.
I've even contacted Samsung's support service and they couldn't help me. They told me to wait for update, but even on the newest stock it is still the same.
If anyone knows the solution please share.
thanks
thanks for the review its really helpful
grabbed root-stock.zip and cwm just below it (first 2 links on this page http://forum.xda-developers.com/showthread.php?t=1686384 ) carefully followed instructions, even watched videos on youtube and everything went swimmingly except after system reboot following root-stock.zip install. i must have grabbed the wrong file (dont know how, it was recommended by everyone on every other thread regarding the rooting of the t679) anyway now i need assistance, which root.zip file should i use? how do i get it onto the phone's internal "usb storage" folder? or can i use another device to grab file, transfer to ext. sd, then put ext. sd card into t679? i understand its critical at this point to make no mistakes, i believe i can recover, assuming i get competent advice...
please advise...
- zCHEMDAWGz
p.s. i am attempting to repair wifi and bluetooth errors (assuming its the drivers not loaded properly following system update 2.3.6) though im not certain of the culprit of these errors as i am the 4th owner of this device. assuming an internal battery has NOT leaked onto circuit board causing corrosion, pretty sure its software not hardware issue. phone/sms/network WAS connecting just no wifi/bluetooth. gotta have wifi cuz im out in the woods on the "EDGE" network, home network is fast as can be.
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Dvarl said:
In cwm wipe cache, under advanced try wipe dalvik, then fix permissions then reboot. Please report results.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
hey thanks for helping me i really appreciate it. so i tried your advice, in every order possible. fix permissions, wipe (everything), load rom, reboot... wipe, load, fix, reboot... to no avail though. all results in same loop... im getting good at wiping and loading =)
also the location of the rom and cwm files prior to transferring to "usb storage" folder was "downloads" on my windows 7 pc... does this make a difference? i have noticed people saving these types of files to their desktop... just trying to find out where i went wrong... thanks again.
- zCHEMDAWGz
SIDE NOTE: i tried loading different rom "t679-root-v1.8.zip" with exact same results... however i noticed that when i load either version of the new rom when cwm begins installation, and when the progress bar at the lower part of the screen shows about 2-3% complete it is then all of the sudden finished with "complete" confirmation at the end. total time less than 5 seconds. according to instructional videos this process should take minutes, instead of seconds.... just an observation.
- zCHEMDAWGz
That's just root not a ROM. If your willing to start fresh you can try this.
Wipe everything x3
Under mounts and storage mound system and data then format both x3
Flash rooted community rom
Reboot
It should work. If you flash any recent ROM make sure you have the latest cwm or you will get status 7 error.
Sent from my SGH-T679 using XDA Free mobile app
success!! wifi/bluetooth still getting error though... tried *#*#526#*#* (wlantest engineering mode) reports "Notset Driver Loaded [NG]"
any ideas?
a-thousand thank yous
- zCHEMDAWGz
Hello and welcome to CM-13.0 Beta 1 !
first of all a BIG thank you to @Adrian DC wich had constributed also to this rom (he fixed the camera and helped me with the other stuffs )
Known bugs:
- sometimes the device will bootloop (only in starting phase )
USE THE FLASHABLE HOTFIX for that
- sometimes RIL may not start (on bootup)
if you encounter one of these bugs please press and hold vol+ and powerbutton to FORCE SHUTDOWN and then reboot again
Other "bug":
- selinux disabled until i patched it
Sourcecode can be found on my git:
github.com/sdtbarbarossa
How to install:
1. make sure your internal SDCard is formated to exfat (you can use Whiteneos TWRP to get that)
2. clean install the rom ( wipe cache & data & system ) [alternativeley dirtyflash.... but then dont report bugs!]
3. flash gapps (i use OPENGAPPS - ARM - 6.0 - PICO )
4. reboot
5. wait several times
Downloadlink:
https://www.dropbox.com/s/7tr42vcejk1u1js/cm-13.0-20160403-UNOFFICIAL-mint.zip?dl=0
link is up
Sent from my Xperia T using XDA Free mobile app
error executing updater binary in zip
SonyXperiakiasT said:
error executing updater binary in zip
Click to expand...
Click to collapse
Code:
ApplyParsedPerms: lsetfilecon of /system/lost+found to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
?
Got that myself, it doesn't work with TWRP 3, you need an older version, i used TWRP 2.8.6.0
(fix) flash it with philz_touch_6.12.8
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
For me installation works with TWRP from 12.1 kernel. After creation of dalvik files it never ended with "apps are starting". Killed the device (Vol+ & Power) and got never ending boot animation... tried to reinstall. Now got "Operation not supported on transport endpoint". Restored "boot" from last 12.1 nand backup, rebooted to (that funny colored) revovery, wiped again, reinstalled (BTW open_gapps-arm-6.0-pico-20160403 in queue) and now..... hey, I get a PIN screen! Wifi & Google sign in works without problem. Developer options, root access, adb shell, seems alright for now - good night and many thanks to SdtBarbarossa!
vladut.alecsandru said:
Q: how do you install supersu? It doen't work from google apps and I tried to flash it from TWRP and I got a bootloop
Click to expand...
Click to collapse
From Xperia M I know it's very tricky or nearly impossible... For me the "onboard solution" for root access is okay. (did not try yet if it really works...)
Actually you are right, I didn't enable the root access from developer options the first time.. but it works and you don't need supersu
But I had no service and after a reboot it started to bootloop again..
bootloop after a reboot
Reinstalled again.. and after each app install I rebooted to see what might cause the bootloop
For me at least, it started to bootloop after I installed and gave root access to titanium backup.
1. the bootloop is a known bug lile i said ( it is that the mediaserver dont start for a unknown reason... depending on the random queue of loading librarys )
atm i prefere everyone to reboot not often x)
bootloops should be solvable by hardboot ( vol+ and powerbutton )
then there are 2 cases:
1.lib a gets loaded before lib b => it boots
2.lib b gets loaded before lib a => it loops
there is nothing how i can controll that atm
2. if you habe trouble flashing the rom please send me a log
3. guys can it be that the no service bug only appears on first boot?
Sent from my Xperia T using XDA Free mobile app
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
I'll probably test the rom today. Keep up the good work SdtBarbarossa.
mankokoma said:
Here's an example logcat for a boot-loop. All boot loops I got were ending with that "Waiting for service media.audio_policy..."
BTW In my case has nothing to do with Titanium Backup, it seems to be random
Click to expand...
Click to collapse
yes i know... thx for the log its the same i get... this bug is just as random as i explained above... hard to find the real reason
so except for the bootup problems ... how is the rom? any other problems?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
... how is the rom? any other problems?
Click to expand...
Click to collapse
First impression's really good. Much snappier than 12.1 - expected. It was a little tricky to change the 'sdcard0' to vfat. As suggested I tried to do it with the 12.1-kernel-TWRP... first did a backup to ext-sd but after copying with TWRP-filemanager it crashed, automatically rebooted the 13-ROM, killed the dalvik and boot-looped At least sdcard0 data were transfered!
So restored kernel & data from nand backup and after successful boot, tried to format sdcard0, mentioned "corrupt" in settings-Storage&USB but ERROR occurred. So I tried with adb shell
Code:
newfs_msdos -F 32 /dev/block/mmcblk0p15
OR
Code:
mkfs.exfat /dev/block/mmcblk0p15
BOTH returned Errors (that's why I tried both) but can't remember which one was successful
In settings-Storage&USB still "corrupt", but after reboot (without problems) there was sdcard0 with 11 GB free - yeaaaah!
Pushed back all the Osmand Map Stuff and so on and now also
Camera does not complain any longer because of missing sdcard and takes photos.
GPS fix is fast and stable... That's all for now!
Ahh and yes, I can do phone calls & sms (aber das ist ja nebensächlich)
hi!
so tried last cm13 beta, thanks for your work first of all.
had same problems as @mankokoma trying to format the sdcard to vfat via WhiteNeos latest twrp (same problem I reported multiple times in the old thread if you remember), it simply does not work, sdcard stays in ext4.
then I did run the commands mankokoma suggested in adb and then I could see vfat for sdcard in twrp. but now in twrp sdcard is not accessible at all. it doesn't mount etc had to use usb otg to install cm13. and in twrp 3.0 provided with cm13, again sdcard is not accessible at all ;(
btw, I full wiped (system, cache, data and dalvik), and thanks to otg I installed cm13 beta. upon very first reboot, phone optimized all apps, but then got stuck at "Android is starting - Starting apps message" forever. I had to force shutdown and reboot, then it booted fine and could pass the wizard.
sim was detected fine.
but I see internal sdcard always damaged in settings. rebooted countless times, didn't fix the problem. and camera app FCs, probably because I don't have any sdcards available...
If I click on the sdcard damaged, and then configure and format, I get an error message, and it doesn't work.
so the rom is still not usable for me atm very sad because the rom seems very promising and so fast!
EDIT: settings do FC here when trying to enter developer settings so can't enable builtin root?!
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
seems that your issues are all because of the sdcard not formated to exfat... you can "revive" it by formatting to ext4 but then you can only use it in twrp... try again to format it to exfat
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
yes but how?? please tell me how to do that... in twrp 3.0 it keeps giving errors...
and by the way in twrp I see file system for sdcard is already vfat now! :silly:
nvm! trying again and again in twrp I always got error messages but now in settings it seems it is recognized! great! and camera started to work now will test it wonderful!
ps: FC in developer settings is still there... how did you get root? with supersu?
EDIT: and recording videos does not seem to work?
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
hamidmf12 said:
hi
tnx for rom is very good
but in my device internal stroge is not work and im format it but this not work
please help me
Click to expand...
Click to collapse
Try this, it worked for me :
http://forum.xda-developers.com/showpost.php?p=65265674&postcount=10