Develop Bugs

Dual Boot KF - Unrooted itself???

So I setup my KF using FireFireFire Entended multi-boot bootloader. I'm running a kang ICS rom as my main and a "fixed" copy of the stock rom as the alternate. All instructions and alt rom came from: http://forum.xda-developers.com/showthread.php?t=1615093
This morning it did some update script on the stock (alternate) rom, now it boots straight into the stock rom.
Ideas? Settings>Device says 6.3.1

This is/was my main ROM:
http://forum.xda-developers.com/showthread.php?t=1614004
Looking for KFU to put on this computer so I can access shell commands.

When trying to plug it into the computer to use adb, I get the following message:
"The process android.process.acore has stopped unexpectedly. Please try again."
I can't get it to register a connection to the computer to do anything.
It doesn't recognize my user to download apps from the Amazon App Store.
It DOES have AndroXplorer on it (from some backup???).
It does NOT give me any options to enter TWRP, and seeing as I can't connect it to the computer, I dunno what to do.
This is freaking frustrating.

It now connects to the computer to move files back and forth.
Device manager shows drivers loaded correctly.
KFU and adb do not detect any device.
I'm running Windows 7 Professional.
Install Unknown Apps is turned On.
Am I just going to have to wipe and start over? I blame the alt-stock rom for this headache.

make it easy on yourself simply flash modaco on the nonroot side you dont have to be rooted to flash it http://forum.xda-developers.com/showthread.php?t=1439916 as long as you have twrp now I dont know what this means according to your dual boot that you may have to investagate good luck if you have access to recovery its possible

Yeah, didn't have access to TWRP. It was weird, the TWRP folder was there, but the device acted like a regular un-rooted KF, although with lots of process force closes.
I finally "Reset to Factory Defaults" and started fresh. Really sucked losing all my ICS apps, but oh well.
modaco? Gonna look into that, thanks. That will install as the Alternate Boot?
I have my ICS as the Normal Boot and the stock rom as Alternate. Simply because I like this ICS build and there's not an Alt Boot version of it that I've found.

It unrooted itself again this morning.
Both the ICS and the 6.3 were installed fresh, with no additional modifications. It's like something associated with the clock triggered it.
If I could get a nice ICS build that's built to run on the Alt partition, I'd do MoDaCo and that.

Im just guessing that with dual boot you have the option to flash to a preferred partition? Maybe address your question to someone who uses dual boot as well. Unrooting itself is just wierd.

information on any Clockwork recovery that can load via extSD

USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....

So far i got ahold of the previous Clockwork before the touch came out but it doesnt have options for external and internal im still allowed to mount externalSD card but whats the for if you cannot ADB with clockwork nor install from exernal SD?
Thanks for your time guys
xgp0006 said:
USA Tmobile Galaxy S3
Ok so i soft bricked my phone after i flashed a rom and a kernel at the same time. They had originally worked one by one(flashing and rebooting one at a time) but i was fliddling around and decided to go back and flash them both at once with one reboot....well now i get a black screen after the galaxy S3 logo....and it hangs.
I have acess to recovery
I can ODIN but since that happened no flashed kernels or roms have made a difference
(all connections and flashes are successful in ODIN)
I have reverted to stock recovery and can access ADB through ADB shell in the SDK BUT i dont have permission to push files or even see inside data folder.... <su> issues a Segmentation fault, and <adb root> root all it does is restarts the session, ID's the port says successful and then issues a device not found and reverts to adb shell access to phone without permissions....
(should i flash a factory PIT file or maybe fix the partition tables? i say this because i assume a segmentation fault is the result of that?)
and where do i find a factory USA Tmobile Galaxy S3 Pit file? i found all these international ones in another thread but that doesn't help
So I have a recovery file on my SD card, Is there a Clockwork Recovery installation that has the ability to flash recoverys from the external SD? (this new touch version lets me mount the external SD but it doesnt pull any files up its formatted FAT32, but do i need to create certain folder names for CWM to see it?)
so that's where im at, In a nutshell:
Cant push via adb because no root permission, i have a recovery on an external SD that CWM does mount but doesn't pull it up and none of the Roms, and kernels i flash through odin(albeit successful without a hitch) make a difference on my boot situation.
thanks for any input i have over 19 flashes on my counter, and 2.5 days of 8-10 hours researching various things ive no decided to ask the community for help....
Click to expand...
Click to collapse

You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?

I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
B-Naughty said:
You said you can ODIN, so ODIN the stock ROM and/or kernal does not work?
http://forum.xda-developers.com/showthread.php?t=1737855
Have you tried a simple wipe cache and dalvik, fix permissions?
Click to expand...
Click to collapse

xgp0006 said:
I had tried a stock rom ealier. I shall try a stock rom and kernel in a few again and wipe caches and fix permissions and see what i get.
thanks for throwing that out there at least ill give this and another suggestion i got a shot and reply with my results....
Click to expand...
Click to collapse
If you're already running CWM, try the wiping and fix permissions before ODIN flash to stock with the TMobile image

[Q] Sideloading stock ROM problems on ClockworkMod Recovery

Howdy -- I was given a SGH-I747 formerly on AT&T. This was a hand-me-down from a coworker that doesn't know what the prior owner actually did to the thing.
It appears that the phone boot-loops for a bit until it lands in into ClockworkMod Recovery v6.0.4.7. The CyanogenMod logo appears at initial boot.
This recovery tool seems to have no external microSD card access. I already have ADB on my Win7 machine and was able to install a driver for the S3 to allow me to sideload via command prompt.
I attempted to do this with a copy of the stock ROM without root access.
Initially I was forced to update a line on the script to bypass the invalid number of arguments roadblock, but later encountered this:
Code:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
I presume something has changed on the primary partition that it wasn't expecting, but I haven't the slightest idea where to go from here.
Thanks for the brainpower

I don't think you can sideload as I have never seen a Samsung phone that supports ADB.
Try updating the recovery to latest version of Philz Touch from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Philz is flashable in Odin under the PDA option and is based on the latest CWM release.

I seem to have successfully applied philz_touch_6.26.6-d2lte, yet the phone continues to boot into the CyanogenMod logo screen and proceed no further. Thoughts? Screenshot attached.
Edit:
Alright -- I've got the menu up:
PhilZ Touch: 6.26.6
Clockworkmode v6.0.4.8

Download a custom ROM (I use Validus 13 myself) to an SD card, insert the card into the phone, boot into recovery, flash the ROM, wipe the cache, Dalvik, data, and reboot the phone.

Success! I did try loading up the stock ROMs that I'd grabbed off the internal card with the same results as when I was trying to sideload it. Sideloading would indeed have worked it would seem, but the scripts just aren't working for this device it would seem.
Validus 13 went on just fine. I'm sure the wife could do without the killer clowns every time she rebooted, but, well...
Thanks again for the assistance!

You can easily change the boot animation either before installing the ROM or after by replacing the boot animation zip.
I believe that side loading isn't possible on Samsung phones as they don't support fastboot commands.
Side loading works in my Motorola and nexus but fastboot commands never work on my Samsung.

Interesting.
So, I'd actually like to give this another go since it looks like I flashed a slightly out of date version of this onto the phone. Do you happen to know what the process is to update the boot/shutdown animation in the package beforehand? Actually, going to give Slimkat a shot --

audit13 said:
You can easily change the boot animation either before installing the ROM or after by replacing the boot animation zip.
I believe that side loading isn't possible on Samsung phones as they don't support fastboot commands.
Side loading works in my Motorola and nexus but fastboot commands never work on my Samsung.
Click to expand...
Click to collapse
sideloading works fine on my S3 with philz recovery installed, i use it to fully format my internal card to blank then sideload a rom/gapps/update.zip since i don't have an external card to put into it.

SuperMidgetProductions said:
sideloading works fine on my S3 with philz recovery installed, i use it to fully format my internal card to blank then sideload a rom/gapps/update.zip since i don't have an external card to put into it.
Click to expand...
Click to collapse
Interesting. Didn't know this was possible. Is there a certain version of the fastboot drivers I need to use?

I just have whatever versions of crap i came across searching the first time a long time ago. Then had to learn where the sideload option was located in philz recovery and it all worked fine together
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

audit13 said:
Interesting. Didn't know this was possible. Is there a certain version of the fastboot drivers I need to use?
Click to expand...
Click to collapse
Depending on the file, yes you can sideload through recovery on this phone. I used to sideload OTA updates, on stock recovery, without root.

Phone wiped itself? And other problems.

Hello. I have a i317 Note 2, running on T-mobile. It is rooted and was running Blisspop 5.x rom. I had set my phone down and noticed it was on the Samsung screen. Figured it was just a random reboot; but it never booted up. I reboot into recovery (TWRP) to find that there is no OS installed. It says my internal storage is 0mb, my external storage is 0mb (I have a 32gb sd card). I cannot mount nor access external storage, or anything internal. I cannot format data. I am able to see my phone while it is in recovery on my computer. But once I put it in download mode, it can no longer be seen. ADB cannot see it in download mode, I cannot fastboot (unless I'm doing it wrong). I used Odin, which can see it in download mode, but it did not fix anything. Also, now the phone says it is unable to format to remove encryption.
Prior to this it had a problem where it would be unable to stat things. Is there any way to fix this? Or am I SOL?

SchusterIX said:
Hello. I have a i317 Note 2, running on T-mobile. It is rooted and was running Blisspop 5.x rom. I had set my phone down and noticed it was on the Samsung screen. Figured it was just a random reboot; but it never booted up. I reboot into recovery (TWRP) to find that there is no OS installed. It says my internal storage is 0mb, my external storage is 0mb (I have a 32gb sd card). I cannot mount nor access external storage, or anything internal. I cannot format data. I am able to see my phone while it is in recovery on my computer. But once I put it in download mode, it can no longer be seen. ADB cannot see it in download mode, I cannot fastboot (unless I'm doing it wrong). I used Odin, which can see it in download mode, but it did not fix anything. Also, now the phone says it is unable to format to remove encryption.
Prior to this it had a problem where it would be unable to stat things. Is there any way to fix this? Or am I SOL?
Click to expand...
Click to collapse
You used Odin for what? Did you try flashing stock rom? Try using the rescue option in KIES. It has saved me in the past when I had messed up my device.

NickVXD said:
You used Odin for what? Did you try flashing stock rom? Try using the rescue option in KIES. It has saved me in the past when I had messed up my device.
Click to expand...
Click to collapse
Sorry about that, forgot that bit! I used odin to flash the stock rom, and even tried a .pit repartition. Kies does not see the phone. At most, it sees it but will not connect. So there are no rescue options to be had.

I thought I made progress. I was able to do the firmware reset with Keis. The phone got to the blisspop launch screen but just stayed there. I rebooted into TWRP and it still said I had 0mb of internal storage, and still had no OS installed. ADB still didn't see the phone, either. Now the phone will no longer boot to samsung, or to recovery, or TWRP. If I hold the power button the proximity sensor shines for a moment but that's it.

Same problem here, same phone but t0lte that ran many ROMs over 4 trouble-free years . Still at the pre-Kies stage, thus still can access twrp. Tried overwriting twrp with philz or CWM - Odin says PASSED but reality say no dice - twrp is still the recovery. Tried flashing stock - Odin again said PASSED, but still have twrp reporting 0MB.
Spent 1day surfing xda to ensure I have correct files and procedures.
Wonder if there has been any solution found...

When flashing a new recovery, do not check auto reboot. Flash the recovery in Odin. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, boot into recovery. Hopefully, this method will work.

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.