I'm having problem with I-8190 (s3 mini) that used to run Resurrection remix (android 5.1). I followed these instructions: https://forum.xda-developers.com/showthread.php?t=2429169 to install stock android
but the stock android did not work, it didn't have wifi available so it's stuck on 'google login' stuff and phone also spams "com.google.process.gapps" error.
That happened with few different stock android images. Then I decided to try install RR 5.1 (with odin) again, it phone remains in bootloop doing the 'optimizing application x/xx' part.
Then I re-installed twrp and tried flashing RR5.1 but install gives error, "Error executing updater binary in zip '/extern" (line break, dunno how it continues)
Could someone give some pointers on how to make phone run some operating system again..?
seegge said:
phone remains in bootloop doing the 'optimizing application x/xx' part.
Click to expand...
Click to collapse
That's not a bootloop, it's optimizing every app in the ROM. Do it again, then go watch TV until it's time to go to sleep and see if it's finished. (If not, plug in the charger and go to sleep and it should be finished by morning.)
Related
Hi everyone,
I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.
It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:
I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.
Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said
"Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!"
I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.
Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?
Thanks,
Tim
Did you try the live restore tool? (read the whole thread)
Brendo said:
Did you try the live restore tool? (read the whole thread)
Click to expand...
Click to collapse
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Verifying current system...
"/system/priv-app/ClockworkHomeGoogle/ClockworkHomeGoogle.apk" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Click to expand...
Click to collapse
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
Try a different usb cable? (ie official, not a cheap one)
My watch always took a few goes to get detected by adb
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.
Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.
Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
Hey everyone,
I'm having a problem after trying to flash CM12.1 on a i8190l.
The instructions I basically followed are the ones mentioned here: novafusion.pl/tutorials/installation-guide-golden/ and I used the rom Lollipop 5.0.2 (CyanogenMod 12.0) 20150428 stable with the Odin app to install it.
All went well up to the point 12. Click on Wipe, then use slider on the bottom to let process begin.
At this point I received a FAILED message with an error message saying below that /data couldn't be mounted. After that, I rebooted the phone, and it started loading the first android screen apparently. After a few minutes, Android threw up an error saying that it couldn't encrypt the data and had to reboot. After that reboot, the system won't stop going over a loop boot that flashes TeamWin over and over again.
I can still get to the download mode, what is the recommended step to take from here? Is it possible to recover the OS? Do I have to worry about the battery running out, or does it charge up while on download mode/other mode?
Thanks for your help
I'm a complete newbie to android phone modding, and I was really proud of myself when I was able to install the Cyanogen 12.1 and Google Apps onto my Samsung S3 Mini. However, I made the mistake of trying to put my work email on it, which requires that my phone be encrypted. Well, I guess the encryption and rooted phone didn't want to play nice together, so I got the error message that my phone would be factory reset. Boo! Well, it got worse. Instead of a factory reset, my rooted phone now is stuck in what I have now learned is called a bootloop. Basically I turn my phone on, and the Cyanogen start screen (with the text "TEAMWIN") just infinitely flashes on the screen until I pull the battery.
I have tried using Odin 3.07 and cm12.1_golden.nova.20160210.ODIN_TWRP.tar.md5. I do the three button system boot, connect the usb, run Odin, get the phone recognized, and then install the .md5 in the PDA section of Odin. It tells me that it succeeded, but when I restart my phone it's still the same bootloop. I also tried swearing, but that didn't help either.
Has anyone else out there had experience with Cyanogen and this particular error? I would love to get this phone working again... preferably with either a Lollipop version of android or back to Cyanogen 12.1.
Any info would be greatly appreciated! Thanks everyone.
So I've got an update if anyone's interested... I can't call it progress, but it's a different problem now.
I was able to download and use Odin to do what was shown on this link: http://forum.xda-developers.com/showthread.php?t=2122548&highlight=root
Everything worked in Odin, the phone rebooted, and went to the Team Win Recovery Project diagnostics screen, rebooted again, and then to the samsung logo. However, it immediately goes to the "Encryption Failed" error screen, and the only option is to 'reset device'. Of course, doing this just reboots the phone and it then has the Team Win loading screen, Team Win Recovery Project diags screen, Samsung logo, and back to the 'Encryption Failed' screen again. So now I have a new infinite loop to solve. *sigh*
any thoughts?
Have you been able to get into TWRP? If you are, maybe you could wipe everything from there and flash the recovery version of your ROM.
I was able to put the stock bootloader onto the phone using Odin, download the original tar from here: http://live.samsung-updates.com/index.php?device=GT-I8190, then used the stock bootloader to install it from the sd card. Everything went fine, but now when I boot the phone it just hangs on the Samsung Galaxy S3 mini GT-i18190 start screen indefinitely. Is this progress, or have I created a new problem now?
You're playing around with heavy stuff. I won't recommend using an upgrade flash (CM over Odin) as an full flash. Please try flashing a stock image.
If you did something wrong to the partitioning, then it's likely to not allow you to do a successfull factory reset. Maybe you can try re-flashing a stock Odin image with PIT repartitioning.
Remember to try to backup the EFS folder, doing that kind of flash might wipe it.
Hi everyone!
I am trying to root my Tab S2 (T810, Android 6.0.1). Unfortunately it ended up in a boot loop (see title).
What I did was, I grabbed the appropriate file from https://autoroot.chainfire.eu/ (fd1ea2ee91ab5569e7150610f4893565) and flashed the .md5 file using the AP button in Odin. After that, the tablet rebooted into the boot loop.
Now I'll try to flash the firmware again to make the tablet work again. So far I'm waiting for the download As far as I understood, I should not lose any data by doing this, right?
Now I wonder, what my mistake was and if the tablet will be rooted after flashing the original firmware (I guess not).
Thanks in advance for any help!
After flashing to original firmware, the tab came back to life. I didn't lose any data, but it's still not rooted.
If I try the rooting again, I get into the same bootloop again. So I guess I'm doing something wrong
I'm following this tutorial: https://dottech.org/198028/how-to-root-samsung-galaxy-tab-s2-sm-t810-on-android-6-0-1-marshmallow/
In other tutorials they also had a step for "oem unlock" on my tablet there isn't this option in the developer options.
Does anyone know how I can root my tablet?
I managed to root my tablet, but now I get the popup "Unfortunately, the process android.process.acore has stopped." every few seconds, it closes itself.
What I did was, I flashed TWRP (http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686) and from TWRP I flashed SuperSU (https://download.chainfire.eu/1012/SuperSU/SR3-SuperSU-v2.78-SR3-20161103171345.zip).
Seems to be fixed after:
Resetting app preferences (Settings/Applications/Application Manager/More/Reset app preferences)
Clearing data of contacts, chrome and calendar (including the storage apps, More/Show system apps)
Good to start saying that my current problem is a "BootLoop" caused after installing a Stock ROM.
The phone can do the following:
- Turn on in "Recovery Mode"
- Turn on in "Download Mode"
- Turn on and stay in the "Samsung" logo (the one that follows the model of the phone, first appears Samsung Galaxy Note GT-N7000 then this appears and is repeated many times)
It all started in the following way I wanted to download a Custom Rom with Android 5.1+, Due to the need to use an application that can only be used from Android 4.4.4 ... Given the circumstance I decided to install a custom rom to be able to use it, I followed each of the steps.
• Install the custom recovery using odin.
• Access the recovery mode, delete each data by doing "Wipe Data" "Wipe Factory" "Wipe Cache" "Dalvik Cache".
• Proceed to Install the Kernel (That's what the steps said) by means of the recovery.
• Restart the phone and access the recovery of the kernel (This causes BootLoop but it is normal, according to the post).
• Proceed to install the Custom Rom.zip and the Gapps.zip
• Restart the phone and use the Custom Rom!
But it happened that he was stuck in the logo of the Custom Rom. Only the logo appeared and it no longer caused anything, I left it for 10 - 20 Minutes and still did not pass the logo, I went crazy looking and no solution.
Try installing a Custom ROM, different to see if it worked and follow the same error.
I continued researching and took the option to Reinstall the Stock ROM, I am not interested in a custom devido that is the phone of my girlfriend and I was going to leave it in factory mode.
I downloaded from several sources and corroborate that they are for the model of the phone "GT-N7000", and so it was, put it in "Download" mode and proceeded to install the Stock-ROM, the first attempt the Odin showed PASS. But it stayed in a BootLoop the phone.
Try another Stock Rom from another source, and continue with the same problem.
Download the one from my country through SamMobile, and continue with the same problem.
When entering Recovery Mode it says "E: Failed to mount / efs (invalid argument)" but it does the functions correctly, after installing the Stock Rom proceeded to give it a wipe and the BootLoop still persists.
I need urgent help please.
PD: (I need accurate and serious solutions please, I do not want it to be like in other posts that only say make a Wipe Factory, download the stock of your country, do not send me things I already have, and redirect files, I already did all those things and I still can not find the fault, what I still do not try is to update the Kies.)