Database Develop

[Q] Stuck in Boot animation after installing seeARMS ROM

Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard

Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)

No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?

I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.

I will try the wipe version

What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App

I was still on stock (froyo 2.2). Actually still on it today

You were right. The wipe version worked fine. I have now to decide to keep it or not...lol

ROM is awasome was worth well the trouble.

Glad it worked out for you - have fun with the rom
Sent from my Desire Z

CWM Recovery Boot Loop. Help!

Hi Everyone,
I have a GT-N7000 - it's been working great since I bought it 9 months ago. I was running RocketRom on it for months. I've been using RR 11 (I didn't like 12) and haven't had a problem with it. The CWM that comes with it appears to be 6.0.1.2 and I kept the stock kernel (OneNote??). Lately, my sms messages were being sent sporadically and I kept getting this same SMS pop-up over and over (every time I sent an SMS). I know it's probably a carrier issue but I thought I would boot into recovery and wipe the cache and Dalvik. I've done this several times in the past without problems.
I first wiped the cache, then I did Dalvik. For Dalvik, I got the error E:\ unavailable (I recall seeing this in the past). I select "Reboot" and the phone booted back into CWM. I've tried removing the battery and same thing.
I ended up trying to flash back to the pre-rooted GB using Odin. The flash completes and the phone reboots but, yep you guess it, CWM comes up. It's the same version. So apparently this is not being updated by Odin??? I read somewhere that this is a CW bug that does not clear a flag to boot back into Android but the fix seems overly complex and worries me (I'm not afraid of doing it if it will fix it).
I'm entertaining the idea of using Kies to do a "Firmware Upgrade" which looks like it will install the latest ICS. It successfully downloads the new firmware then asks me to connect the phone. Before I do this, I wanted to check here to see if this is my only (best) option. Or if I should try something else? Also, Kies says system and data will be initialized so will my sms logs, photos, etc be deleted as well? Not a huge issue since I save the photos to the external sd. I just want to know if the USB storage will be wiped too.
[EDIT] I wanted to add that I TRIED to install Abyss from CWM and it hangs. Same ting with installing RR again. It appears that the file system is locked or something. Pretty much nothing works in CWM. I even tried mounting the various partitions then installing Abyss. It just hangs on "installing." I suspect the problem occured when I wiped the cache or Dalvik. I just don't know what
I appreciate any input.
Thanks!

dont use abyss... try other like hydracore or speedmod 3-15

Im a noob and im afraid i may have this also..

Try to download Philz kernel for your built number, and flash the philz zip file from recovery.
or if can't flash from recovery, try to download the ODIN file for philz kernel (TAR file).
It should re-injected the CWM.
Sent from the corner of this rounded earth.

[Q] NANDROID restores: TWRP won't boot, CWM corrupts data

Sorry for this being lengthy, I wanted to make sure I gave enough info.
Neither of the two most popular recovery tools are working for me. They both state the backups are successful but the restores have flaws. Is anyone experiencing the problems I am? If so, does anyone know what to do about them?
CWM Recovery Touch (and non-touch): Data restores leave certain things not working. I'm not sure what processes are stopping because it flashes and disappears to fast. I know that it causes the ROM Manager for CWM, Titanium Backup Pro, Google Play, and likely more to crash (disappear) immediately upon opening. Chrome browser *might* bright up the keyboard on the first click but it won't work then it will disappear and not come back (but the keyboard does work in other areas, I use Swype Keyboard). I've tried clearing cache and/or data on all 3, uninstalling them then re-installing via APK and various other things. This occurs regardless of whether a factory reset (data/cache) wipe is performed before the restore. However, if I restore with CWM Recovery *then* do a factory reset, Google Play will work and nothing crashes, nor are their long delays.
TWRP does not boot after a restore. It will pass the initial screen showing the phone model, the phone carrier splash screen, then sit on Samsung with the LED solid bright blue and hang.
My goal is to simply trust my backups. The CWM Recovery problem is workable in a terrible situation since my Titanium backups will get my phone *almost* to where it was (barring widgets, which are pain to re-setup, and a few other things).
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone? Since I use the Swype keyboard I removed the other once, did a restore with CWM, had the problem so I did a factory reset and my stock keyboard was missing still (I think it's a Samsung keyboard)
App Details:
CWM Recovery Touch 6.0.4.7 (for Samsung Galaxy S3 LTE (GT-I9305))
TWRP 2.6.3.0 (for Samsung Galaxy S3 LTE (International i9305))
Phone Details:
Carrier: T-Mobile (Germany)
Model number: GT-I9305
Android Version: 4.3 (stock from Kies, so I do have Knox and it's disabled via SuperSU 1.91 from chainfire)
Baseband version: I9305XXUEMK1
Kernel version: 3.0.31-2051278
Build number: JSS15J.I9305XXUEML5

Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone?
No a Nandroid backup wipes the phone .
make a Nandroid then in recovery format system sdcard data cache .
You now have an empty phone and restoring the Nandroid should return exact same state .
All this reads as you are doing something wrong .

JJEgan said:
All this reads as you are doing something wrong .
Click to expand...
Click to collapse
I hope it is as simple as that. I'm booting up in recovery mode (Volume Up + Home + Power) choosing the backup or restore option, then backing up to the External SD card. Then on the restore I'm doing the same except selecting restore from the SD card (I've re-created the CWM problem 5 times, once was with advanced restore of just data the rest were basic restores doing everything). I'm not really sure what I could be doing wrong.
I have the 4.3 stock ROM before I did any custom stuff to the phone (which installed KNOX). I used chainfire's tar.md5 auto root image with Odin 3.09 in download mode when I root the phone, and I've installed CWM Recovery with ROM Manager and with an Odin tar flash in download mode. The install of TWRP was from an Odin 3.09 tar flash in download mode too.
With regard to the TWRP and CWM Recovery, I'm not really sure how easy it is for me to have messed up that part. Do you have this same model phone? Is it possible KNOX is involved in my issues? Maybe I should downgrade one of the recovery tools?

Downgrade your recovery and try again.

jonesjw362 said:
Downgrade your recovery and try again.
Click to expand...
Click to collapse
That's what I was thinking might be the best solution. Since the flaw in the restores with CWM Recovery are workable for me, I figured I may just wait until I have a need to restore to do that though. Once I do, I'll probably do a bunch of tests until I find something that works solid.
I've already restored my backups and widgets etc. a couple of times and don't really want to do it over again only to test. If there's a way to restore all of that without my having to set it up myself then I'll do it. Right now my Titanium restores don't include wallpaper (except lock screen), most of my widgets (maybe all, can't remember), and I think there was one other thing.

Advanced restore in recovery restore data only .

JJEgan said:
Advanced restore in recovery restore data only .
Click to expand...
Click to collapse
I tried that once, that's why I believe the CWM Recovery issue to be specifically with data. I'm going to do it again right now though and if things are messed up again I'm going to try jonesjw362's suggestion.

Downgrading didn't help (6.0.3.6 had a constant barrage of 4-5 apps re-crashing over and over again during the process).
I tried the following with CWM Recovery Touch 6.0.3.6, 6.0.4.5 and 6.0.4.7:
Factory reset wipe, open and test Google Play (more things break but that's the one I chose to test). Reboot into recovery mode and backup to the SD Card (not the external). Immediately advance restored data only (no wipe). Booted up, Google Play crashed, rebooted back into recovery and factory reset (data/cache) and advance restored data again with the same result.
I didn't try a downgraded version of TWRP (probably won't for now). I'm back to 6.0.4.7 and restoring my backups to get my phone back fully. Hopefully CWM Recovery comes out with a new version sometime in the near future that works for me or someone has some insight into what I can do to fix it with the existing (I'm out of ideas).

Issue Samsung stock 4.3 ROM
I ended up switching to CM 10.1.3 (was going to hold off until 11 was stable) but the Samsung stock 4.3 ROM was destroying my battery. After switching, I tested a NANDROID backup and restore with CWM Recovery Touch 6.0.4.7 (same version I was having problems with). The restore worked as it should, no problems.
End Result: As far as I can tell, the cause of the CWM Recovery data partition problem is due to the Samsung 4.3 ROM.
Edit: I was going to mark the post Resolved but I can't seem to find the drop down to do so (at least not in the same place I thought it was).

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

No Mobile Data after Nandroid Restore

I don't think I can edit the title so I'll write it here for anyone who wants to help: This problem is SOLVED. (Y)
So the matter is a bit complicated and I can't guarantee I even remeber everything I did but I'll try to include as much detail as I can:
I had the Stock Rom (OOS4.0.0) running, OEM unlocked & rooted when the OOS4.0.1 OTA notification kept nagging in the back of mind. I thought I should just leave it ago because I already had a feeling it would go wrong...
So I download the Full .zip and flashed it through TWRP 3.03-1 and after that it was stuck on the boot screen for more than 15 minutes or so. So I restarted it again and this time it booted butall my data was deleted and it gave me an error about the encryption having failed. But as you probably know, one can't flash anything on an encrypted phone so I checked back in TWRP and it was really encrypted. Checked back in the phone's settings: Also encrypted. I then used a tool to force decryption (it also wipes all the data) and I was back to square one.
From that moment on I tried: 1. restore nandroid (all partitions included [that includes EFS]). It got me to the booting screen, but when I unplugged it shut down and a reboot got me to the battery screen. I had 72% left so at this moment I thought it had nothing to do with it not booting at 72%. Then I wiped everything (checked every box in TWRP) and was left without any OS. Then I let my phone charge to 100% and re-restored the nandroid OOS4.00 and it worked but I had the Unlock-Bug, I was able to fix that. Then it booted but it wasn't able to recognize any SIM cards, so I fixed that by re-re-restoring with TWRP 3.03-0 (which automatically replaced 3.0.3-1 after the nandroid) and everything worked fine. until I went out today and realized I had no mobile data. I doubt it has something to do with EFS because everything else is working fine (calling, checking IMEI wih *#06#).
I then proceeded to check the APN and it looked ok, I then tried another SIM card (from the same provider) and it didn't change anything.
My provider is the german company 1&1 (1und1) but it uses vodafone APN.
I have no clue what to do right now so I am asking you guys for help.
Thanks in advance!

Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.

Inciter said:
Well, first things first. On rooted devices with stock rom always flash a full/complete zipped image - never, never, never use an official partial image. And always wipe Dalvik/Art and common cache before reboot.
In your case now I would probably try to clean re-flash the current OOS image version (4.0.1). You'll find guides and downloads in the guides and rom section of this forum. Clean flashing your device requires you to completly wipe the data partition before flashing (the internal partition remains untouched). Don't forget to wipe Dalvik/Art and cache before rebooting. This will hopefully completly reset your device.
Click to expand...
Click to collapse
First of all: Thanks for your reply.
I don't know if there was a misunderstanding but I only ever flashed the full 1,4gb .zips.
Also I am running 4.00, because I had to restore it as the 4.0.1 flash ruined my phone. Just now I flashed 3.03-1, wiped dalvik & cache and flashed the 4.02 .zip which I got from this [https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074] thread but it left me stuck on "patching image uncoditionally" or something and then I rebooted and now I am stuck on the +1 booting screen (not even the animation, just the +1 logo witht he "powered by android" signature in the bottom).
I have the feeling it's a software bug not related to what I did with my phone. it was just luck that I did not havfe that problem prior to my nandroid restore or something. I mean: Looking at it from a logical perspective: When you restore your phone with a full nandroid backup it should be exactly the same phone, shouldn't it?

Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.

Inciter said:
Well, flashing the TugaPower rom might break the alert slider. To fix this you have to simply backup and recover the data partition. I don't know why this is happening but I believe that sometimes permissions to files and folders remain untouched in certain situations. Maybe someone else knows more details on this topic.
If you are absolutly sure that your nandroid contains all required partitions just try to wipe all cashes, data and system partition before recovery. But like I said before I would then clean re-flash your current OOS image version. In your case the error might possibly be some error resulting from faulty permission on configuration data. If it was a common bug more people would have reported it already.
If something broke and it can't be easily fixed... trying to return to point zero and resetting everything to defaults will possibly your best chance.
Click to expand...
Click to collapse
I have no problem with that, but my device does.
I can't flash anything because TWRP (bot 3.03-0 and 3.03-1) will be stuck at "patching system image unconditionally", ( I tried the full 4.02 .zip and the ful 3.54 .zip that I am 10000% sure used to work, because I used it before the Nougat release).
Wiping everything but Internal and USB OTG changes nothing.
If you have any idea how I can get to a fresh start, I would really appreciate it.
EDIT: I am sorry, I don't know what you mean by TugaPower Rom. I never installed anything like that - atleast not knowingly.

Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.

Inciter said:
Due to encryption returning to OOS 3.X after having upgraded to Nougat is difficult. Just flashing wouldn't do. There's still an option to format data - not just to wipe it. Was boot, EFS and firmware partition included in your nandroid? Does the recovery still work now? Another Approach would be to use the Unbrick Tool.
Click to expand...
Click to collapse
So, I have the means to decrypt my device through a tool I found here on the forums last month. It does wipe all your data, though. Anyways: I was able to restore mobile data through an older nandroid backup (and yes: all my back ups include all partitions; glad I was smart enough to do that haha). That worked for me and made me come to the conclusion that the back up I used first was somehow corrupted. Then I restored the data partition using my most recent nandroid back up and now I am back in the game. Thanks for all your help so far!
The only thing that kind of makes me worry is that I only get ~60mbit/s through speedtest even though I should get 200. I know I was able to get 200Mbit/s at some point using that phone, but I don't remember if it was with OOS 3xx or the OOS 4.00 update. So I can't tell whether it has something to do with me restoring the phone, my WiFi connection (a speedtest with my lan-connected desktop gave me 200) or just an android bug.
I'll wait until weekend when I have the means to test it with another 200k connection - and imho 60k is enough for anything I do with my phone anyways and I don't plan on reselling the phone in the future, so it won't kill me even if it is nandroid-related.

Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.

Inciter said:
Linux/Android backups aren't always that satisfying. I often experienced diffences between what was saved and what or how it was restored. Most problems resulted in faulty permissions or missing file execution attributes.
Nevertheless, I'm glad your devices is working again. Keep that backup save, you'll might need it again... or hopefully not.
Click to expand...
Click to collapse
Thank you, I just checked the wifi-speed with an iPhone 6 and it even got lower results (>30k) so I assume it has something to do with the WiFi itself at the moment and not with the OP3t.
And even if the backups are not always satisfying: I want to quote someone I read on some forums doing my research to fix this phone: "The seasoned user knows: A backup makes the difference between an awesome phone and a beautiful brick." That is a most evident truth to me now haha.