Related
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
I apologize if this has been covered already, but the search feature finds more noise than signal and I just don't see it.
I have safestrap on my xt860 with cm9 on the safe side of things, and I have a messed up and broken "stock" on the unsafe side. I'm pretty happy with cm9 in general, however there are still some known limitations, so I'm thinking of putting something else on the non safe side. Obviously I'd rather not break cm9 in the process.
Is doing this as simple as switching back to non safe and flashing the zip for what I want to try? Or is it more complicated than that?
You got to put back bootstrap. I think though that safe mode backs up to your internal storage so you should be good.
Sent from my XT862 using XDA
I believe that, when you have switched into non-safe mode, safestrap will not allow you to select the "install zip from sdcard" menu option. I am running safestrap 1.08d tweaked and just tried to do it. It says ".zip install is only available while safe System is enabled."
I don't think rick has gotten non safe flashing functional on any version.
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
That's how I do it anyways
Sent from my XT860 using xda premium
Endoroid said:
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
Click to expand...
Click to collapse
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
LaZiODROID said:
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
Click to expand...
Click to collapse
Yeah, got the SBF loaded. Still have no idea why i couldn't get CM9 in to my non-safe. right now though I seem to have a bigger issue, for some reason my recovery can no longer mount my SD card (though the OS can) I've tried bootstrap, and safestrap, neither can read from my external SD... it's rather odd!
I found with safestrap 1.08f (ricks version) it wouldnt mount mine either.
I started from scratch and installed 1.08d and it works just fine.
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Sent from my XT860
thanks for the tip about 1.08f... maybe that's it, I'll investigate...
LaZiODROID said:
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Click to expand...
Click to collapse
I know sticking to safe is safer, but sometimes I don't want "safe" I want functional. seems a waste to me to have stock loaded on non-safe when I don't plan to ever, under any circumstances, use stock.
I like CM9, I'm quite happy with it as my every day rom. I'd like to put it in non-safe so that I can play with new ones in safe. unfortunately I'm not having much luck with that right now...
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
ve6rah said:
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
Click to expand...
Click to collapse
There is indeed a sbf. Theyre called fastboot now. There's a thread for it
Sent from my XT860 using xda premium
LaZiODROID said:
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
Click to expand...
Click to collapse
well, others have reported success, but none of them seem to be using CM9 in the non-safe, so maybe it's something specific about that one rom?
I think I'll give it one more try today before giving up and going back to root/cm9 so that I don't end up without a phone for the next 2 weeks until I have time to play again!
seems to me that the trick is to find a bootstrap/recovery that is NOT safestrap, install it, install whatever you want, uninstall it, install safestrap, and go on with life as usual.
Unfortunately I can only find one non-safestrap recovery, and it doesn't seem to work too well. most are dead links now as everyone moved to safestrap.
Anyone have a link to a non-safestrap recovery I can try?
I have uploaded 2 bootstrap versions to DepositFiles. Sometimes when you root, a complete version of BusyBox isn't included, so:
1) Root
2) Install Busybox Installer from the market (it's free)
3) Run BusyBox Installer and install whatever highest version installs successfully. (I found that after using the Bell SBF, the highest version wouldnt install properly, so I just chose the next one in the list)
4) Install whatever bootstrap app, and click its button to do the recovery install.
Droid3 Bootstrap:
Link: http://depositfiles.com/files/5qcaay2e7
(This one's for the Droid3 - I believe that if you're using an XT860, the only way this will boot is if you have USB plugged in!)
Milestone3 Bootstrap
Link: http://depositfiles.com/files/o248gldkm
(For the XT860, this should just boot normally, without USB cable)
Well, the solution continues to elude me.
With Milestone3 Bootstrap I simply can't get cm9 to boot. it flashes ok, but then it just freezes on the motorola logo and won't go any further.
With Droid3 Bootstrap (and USB plugged in) I can boot in to cm9, but USB has to be plugged in EVERY time you boot up (not much of an option for an every day phone)
After getting cm9 working under Droid3 bootstrap though I decided to try to change to safeboot. Unfortunately that way it boots up to "android is upgrading... optimizing applications" followed by "starting applications" and it never gets past there.
I think part of the problem is that I have no way to uninstall the droid3 bootstrap before installing safestrap. anyone have any ideas how to do that properly?
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
LaZiODROID said:
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
Click to expand...
Click to collapse
yes CM9 worked on Droid3 Bootstrap. but not once I installed safestrap (without tweaking anything in safestrap.)
it doesn't so much "freeze" as it decides to "optimize applications" and then just can't seem to get past there. (only solution is a battery pull at that point) I do get the safestrap flashscreen, and can get in to safestrap.
After wiping cache, dalvik cache, and data (factory reset) I reboot, go through the safestrap boot screen, and get to... nothing. blank screen, refuses to boot further.
So something obviously went wrong between when I had Droid3 Bootstrap loaded, and when I installed safestrap. I'm just not sure what other option I have at that stage to make things go more smoothly. theoretically if it works under the Droid3 bootstrap, then it should work as the non-safe for safestrap, but it just doesn't, and I have no idea why.
well, still didn't figure out CM9 in the non-safe... so I've gone a different route.
I now have mavrom in the non-safe, and I'm in the process of installing steeldroid in safe...
Nice. So there was nothing special you had to do after your fresh MavROM install to get safestrap going?
Sent from my XT860
No, went smoothly.
- SBF to stock
- root
- install milestone3 bootloader
- flash mavrom
- remove miletone3 bootloader
- install safestrap
- switch to safe
- install steeldroid
Am I doing something wrong, I have flashed a few custom ROMs on my nexus 7 and all works perfectly.
Yet I think I'm doing it right on my note, yet I haven't managed to get any of the custom ROMs to run without restarts, lag and other blips to happen, the only ROM that runs perfectly is my backup ICS stock with Hydra.
Basically I Boot into recovery
Wipe data, cache and davlik
Install ROM from zip
Reboot a few times
Use for a day or so
Sent from my Nexus 7 using xda app-developers app
THUDUK said:
Am I doing something wrong, I have flashed a few custom ROMs on my nexus 7 and all works perfectly.
Yet I think I'm doing it right on my note, yet I haven't managed to get any of the custom ROMs to run without restarts, lag and other blips to happen, the only ROM that runs perfectly is my backup ICS stock with Hydra.
Basically I Boot into recovery
Wipe data, cache and davlik
Install ROM from zip
Reboot a few times
Use for a day or so
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What exactly are the roms you're mentioning? (I'm assuming 4.2.2 ones, right?) are you also flashing a custom kernel afterwards X or Y rom? which one?........ almost any rom has some (more) some (less) lag issues within it, and some others are known to happen random reboots with certain kernels... a little more information could help............ btw, you should try Chasmodo's Asylum, a pretty neat one in all aspects.
Just been out for a run and the Note restarted on my (thought was Trusty) ICS backup ROM, only thing I can think of is it seems to happen when accessing the Ext SD card, perhaps its where i have flashed a few different roms from CM10 to sammy etc...and they use the SD in different ways, so I have just formatted the Ext SD card and will try Chasmodos wonderful rom, does look good
Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
cm 10.2.1 works great in rom slot 2 on my droid4, but not in the stock slot. Is there something different I have to do?
I activated the stock slot, did a Factory Reset, installed cm and gapps. It boots, shows the safestrap splash screen, then goes to a black screen with the backlight on. Nothing after that.
I can connect with adb and see the logs, there are repeated heap dumps from something crashing, but I don't see a line saying what. It appears to be trying to start AndroidRuntime and dalvik (same thing?) over and over. Does this give anyone a clue?
I also tried wiping /system after a factory reset, but it just hangs on the black screen, no change.
Before this, I had the latest OTA in the stock slot, and I was running eclipse rom 1.0.8 (or something) in slot 1. I am able to restore my safestrap backup of the stock slot and the stock rom still works.
You can only safely install Cyanogen in ROM-Slot 1. Never try to install to the stock ROM slot. Slots 2 and 3 are touch and go. It's best to just stick with ROM-Slot 1.
If you've already installed it in the stock ROM slot, then you'll likely have to restore your phone using SBF/fastboot files and start the whole process over from a stock system. :\
NeoPhoenixTE said:
You can only safely install Cyanogen in ROM-Slot 1. Never try to install to the stock ROM slot. Slots 2 and 3 are touch and go. It's best to just stick with ROM-Slot 1.
If you've already installed it in the stock ROM slot, then you'll likely have to restore your phone using SBF/fastboot files and start the whole process over from a stock system. :\
Click to expand...
Click to collapse
The note on the cyanogen site says "Builds older than 09/01/2013 must be installed on rom-slot1." I've read threads where people are using cm and aokp in the stock slot, so I thought it would work.
Any idea why it can't work in the stock slot? Safestrap seems to create image files for virtual filesystems of system, cache, and userdata which are obviously just imitating the stock partitions. I guess you need to bypass that logic, so can I just tweak the fstab or something? I'm curious what other magic safestrap is doing (or the cm/aokp roms) that needs to be adjusted for stock.
Nevermind, I figured out my mistake. I was on an old version of safestrap. Upgraded to safestrap-maserati-3.65, flashed latest nightly cm11 to stock slot, and it works. Great job cyanogenmod!