Has anyone had issues with getting into recovery after loading the new skyraider 3.3 sense rom?
No issues here, loaded 3.3 yesterday along with Kings BFS#5 Kernel. Just rebooted into Recovery and kicked off a nandroid backup.
most problems with 3.3 are related to not having the correct radio installed,
please be sure you are running the right "baseband" under "settings/about phone/software info"
should be 2.15.xx.xx.xx
mine is 2.15.00.07.28 and everything is working just fine
Hey thanks I got 2.05 so i need to move up where can i find the new radio?
I updated to 3.3 a few days ago when it was relased. After that recovery worked fine, however I updated to the newest (2.5.0.5) ClockWorkMod Recovery and never could get into recovery with that version. I had to reinstall a old version of the recovery. I think the newest Clockwork has the issues. Is it possible you updated to the newest CW at time of SR 3.3?
Related
Hello, I have my evo running on Fresh 3.5. Everything works great except I can't update the Baseband nor the PRI. I've tried Clockwork and the Fresh Updater with different methods; Boot into recovery, tried to get RA to boot into recovery and a bunch more. Anyone have any suggestions on updating the radios and PRI? Thank you.
After having no issues with flashing ROM's, radios etc for over 6 months i've recently encountered a problem. When trying to update to CM7.0.3 from CM7.0.1 i had a system cannot mount error and was unable to flash any new ROM as a result. To try to fix this i formatted system and restored to a CM7 ROM and everything seemed fine. From here i can flash a ROM but when booting the new ROM it does not include gapps (even when selected to install from clockwork) and the system cannot mount error occurs again.
In short, everything seems to work fine currently but as soon as i flash a new ROM i get a system cannot mount error. The same thing happened with a CM nightly and so im thinking it is not just an isolated problem with a specific build.
Any help would be much appreciated. On a side note, on the restored ROM im currently using i have a LordMod Kernel installed, not sure if this would effect anything as when the problem was first encountered i did not.
Thanks.
Restore to a working ROM using your backups.
Boot into bootloader and then into fastboot.
Download ClockworkMod Recovery 3.0.2.8 from HERE
Unzip and run install-recovery-windows.bat. This will flash the latest recovery for you.
Now try again.
Yeh that worked perfectly, thanks alot.
I currently have Clockwork Rec. version 3.0.0.5 orange. I already flashed SRF1.2 onto my Epic, but everything seems to be fine.
Also, I want to install the full loaded version. Do I just put the 7mb zip onto my sdcard and do an install from sd card without wiping/factory reset?
Thanks.
I just updated from 3006 with no problems. I also put the clean Rom on.
Sent from my Epic on Midnight or my Galaxy Tab rooted (feels naked without a ROM)
I updated to the CWM purple (3.0.2.5 i believe), flashed SRF 1.2 and did a CWM backup. After I was getting many FCs, I decided to restore my CWM backup, and now CWM has reverted back to orange. Is this a problem? Will it affect future flashing? Thanks!
I don't think data restore works between CWM versions, so be aware of that. Otherwise 3.1.0.1 (Purple) is the latest and greatest. Be aware if you flash a pre-rooted kernel with a prior version of CWM included, you may wind up with two different versions of CWM installed.
If you're going to use 3.1.0.1 I'd suggest also flashing Clean Kernel or Genocide as those are both updated with 3.1.0.1 reboot recovery.
To all people installing TWRP 2.7 and getting errors flashing and backups its because its not oficially supported not even for moto x, so i suggest to install the previous version 2.6.3, included in this thread.
http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
im writing this because so many people are recommending twrp 2.7 and later on they are ranting that backups dont work and that sometimes cant flash something, just to let you know.
im not saying it wont be a 2.7, someone will make it compatible and fully working, im just saying that by now only use the version that works, which is 2.6.3
related:
http://forum.xda-developers.com/moto-x/moto-x-qa/official-twrp-2-7-moto-x-t2681021
http://teamw.in/twrp_view_all_devices
I have 2.7.0.0 installed and have backed up and actually restored from that backup successfully. No problems for me
CrazyRussianXDA said:
I have 2.7.0.0 installed and have backed up and actually restored from that backup successfully. No problems for me
Click to expand...
Click to collapse
Same. Zero issues.
I've used 2.7.0.0 from this thread:
http://forum.xda-developers.com/showpost.php?p=51155272&postcount=294
Same here 2.7 working fine no errors
TWRP 2.7
I have had no issues either. Back up and restore work fine.
2.7 backup and restore OK, but cant install Gummy rom, now use philz_touch_6.19.3-xt1060
Gummy installed for me with 2.7
I've had no problems backing up and restoring with 2.7.0.0 on a Droid Mini. However I tried to install a recent CM nightly and it failed because the ro.product.device in TWRP was blank. I edited the CM updater-script to remove the device check and repacked the zip. After that I got it to install.
Using 2.7 - Zero Issues with All Features...
Can this post be taken down seeing as it is incorrect and misleading...?
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
VegasIdaho said:
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
v.konvict said:
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
Click to expand...
Click to collapse
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
VegasIdaho said:
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
Click to expand...
Click to collapse
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Choristav said:
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Click to expand...
Click to collapse
Thanks for your reply. After reading the response from v.konvict above, I thought that CM12 would be caf, but it isn't. I've got several more ROMs working now by using different bootstacks, but it is trial and error with some of the ROMs.