• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root TWRP - Spectrum

If you want CM10.1.2, you can flash it again.

Yeah, but I don't notice the difference. I just flashed AOKP for fun. Gonna try that for a while. But the phone issue is still there. I think it is broken no matter which rom I flash. (cannot use pauses in a phone number).

I downloaded the catlog thing. Now I just need to know how to use it. Is there anyway to reinstall the stock phone/dialer app? I wonder.....

I tried using different phone apps as well, and the problem remains. And the forum is right, might as well stay on TWRP, I love the interface, and so far everything is smooth. I forgot to do a backup though. One of these days, I am going to get myself in trouble doing that. LOL
 
If you want CM10.1.2, you can flash it again.
HI REESEBOY, I was wondering, can I flash the broken out spectrum 3.0 rom when I am using TWRP? IT seems as if the "broken out" rom is a little old, and is GB. Just wondering if there would be any problems flashing it. Thanks!

KLEMBO:D
 
I know there were issues running GB ROMs on the newer radio files(V7, V8) but I'm not sure those affected broken out. I would recommend reading the last page of posts in that thread and see what people say. If no one mentions it, ask there for the best response... I never tried broken out on the newer radio versions.

To clarify that:
The official releases from lg/vzw were full packages, replacing the recovery, ROM, and radio firmware partitions and possibly others. When you cab flash you replace it all with that version you flashed. Flashing CWM and TWRP replaces only the recovery partition, and flashing a custom ROM replaces only the ROM partition.

Edit: or what ortrigger said :)
 
HI REESEBOY, I was wondering, can I flash the broken out spectrum 3.0 rom when I am using TWRP? IT seems as if the "broken out" rom is a little old, and is GB. Just wondering if there would be any problems flashing it. Thanks!

KLEMBO:D

There shouldn't be any problem with it. I'm not sure why you would want to flash a GB rom though. GB on this phone was awful.
 
There shouldn't be any problem with it. I'm not sure why you would want to flash a GB rom though. GB on this phone was awful.

Just pure curiosity (running a GB rom). I am stymied why the use of pauses in a phone number causes the dialer to stop working and freeze up. Been in contact with someone at jira, he re-opened the bug ticket I entered. He commented that this problem is coming up everywhere, not just on specific phones.

Bottom line, I flashed the broken out spectrum 3.0 rom on my phone, and putting pauses in a phone number WORKS AGAIN!!

Next step is to do a clean install of the latest version of CM10.1.2, and logcat it for him. Next time I am off from work, I'm going to give it a try. Does anyone here have a link to directions for taking a proper logcat? I've never used it before, and want to make sure I give the correct log to him. Thanks again as usual to all of you.

P.S. ORTRIGGER, you are correct, my phone now looks like my old CRUZ VELOCITY tablet!!! with the GB rom on it. LOL :D
 
Klembo, I posted a logcat for you lastnight on a clean 10.1.3 setup, so no need to worry about the logcat.

Why, thank you!

But I would still like to go through the steps myself, so I can learn how. If I keep playing around with my phone like this, I am going to have to do these things.
 
Why, thank you!

But I would still like to go through the steps myself, so I can learn how. If I keep playing around with my phone like this, I am going to have to do these things.

logcat is done through ADB. You can find out more about it and how to use it here. To do a logcat, you would open a command line in the directory where adb is located, make sure your phone is connected, and type:
Code:
adb start-server
adb devices
adb logcat > logcat.txt

adb start-server makes sure that adb is running in your command terminal. adb devices will list connected android devices and adb logcat > logcat.txt will start the logcat and print it into a .txt file in the current directory.
 
logcat is done through ADB. You can find out more about it and how to use it here. To do a logcat, you would open a command line in the directory where adb is located, make sure your phone is connected, and type:
Code:
adb start-server
adb devices
adb logcat > logcat.txt
adb start-server makes sure that adb is running in your command terminal. adb devices will list connected android devices and adb logcat > logcat.txt will start the logcat and print it into a .txt file in the current directory.

Thanks so much ortrigger, I appreciate it. Someone else, either you or reeseboy, posted that link before, and I was hoping someone else would do it again for me. Let me go through the motions, and if anything looks unusual, I may be asking you a question or two.

My major problem is that I have to RUSH with everything. I have VERY little time, but still wish to learn more. Sometimes I have to read these posts, then wait until the next day to flash a rom. It's frustrating. But so far everyone on this forum has been more than patient and helpful. I've haven't seen such a large group of unselfish people, all in one place! It's amazing to me, it really is.
 
Pretty sure that was a CWM ported from another device. Now TWRP is building from source. Pretty sure I have a build tree repo linked somewhere in the thread....

https://github.com/yoinx/VS920_TWRP

That should be what you need for the build tree if you intend to build it from source.
Hey Yoinx. Your custom 2.6 build continues to work great. Any word on getting the vs920 onto the official devices list? I see 2.6.1 and 2.6.3 are out for official devices.

Thanks for getting us 2.6 building from source!
 
Hey Yoinx. Your custom 2.6 build continues to work great. Any word on getting the vs920 onto the official devices list? I see 2.6.1 and 2.6.3 are out for official devices.

Thanks for getting us 2.6 building from source!

Tbh, they had us locked out for official releases before I got underway. It would be trivial for someone to clone my build tree, and build it. They're pretty laid back on getting official status... Just gotta join the IRC chat and talk to someone.
 
i flashed TWRP a while ago on my spectrum and was going to flash CM10.1.3 RC2 and i found i cant install any zip. i get an error status 7 on all zip files. sucks because i wiped the phone without a back up...

I can mount the the usb and push files to the sdcard. adb sideload just will not work.

on v2.4.0.0 Alpha not even sure where i got that version from
 
Status 7 typically means that the ROM you're trying to install doesn't match up with the model currently being listed in TWRP/CWM. My guess is that you grabbed the recovery mentioned in this post.
http://androidforums.com/spectrum-all-things-root/673547-twrp-spectrum-3.html#post5864281
Grab the .zip file listed at the end of this post, flash it (which will update your TWRP) and then try flashing your ROMs again. If you still have issues, then you have corrupt ROM downloads.
Dev-Host - TWRP_2.6.0.0.zip - The Ultimate Free File Hosting / File Sharing Service
 
Thanks Neph, really.

i got stuck in a data center and i needed web access. i forgot that I cant tether yet with my LG G2. just so happen to bring my spectrum to fix it and good thing i did. used the G2 and grabbed that twrp zip, grabbed abd, put it on my work laptop. pushed the zip, flashed it, flashed CM. swapped in the sim card. bam unlimited tethering again. I didnt bother with my work LG Lucid...last i tried it didnt work either.

ill be doing a live youtube feed this weekend at car show and chances are ill be using the spectrum to handle the the stream...unless by chance CM is developed this week for the G2
 
If anyone who has a build environment already set up wants to make updated builds, it's pretty simple. I would do it, but RL has me really busy lately.

Clone the TWRP tree, copy it into your build directory. I believe the CWM stuff is in bootable/recovery. You just need to replace the files there with the TWRP ones.

Clone my recovery device tree, and replace the existing one.

Then just make -jx recoveryimage

It should only take like maybe 20-30 minutes to build, ideally. Rename it and toss it into the zip to flash.

I don't really see where they would've changed anything drasitcally enough that the build tree wouldn't still work.
 
If anyone who has a build environment already set up wants to make updated builds, it's pretty simple. I would do it, but RL has me really busy lately.

Clone the TWRP tree, copy it into your build directory. I believe the CWM stuff is in bootable/recovery. You just need to replace the files there with the TWRP ones.

Clone my recovery device tree, and replace the existing one.

Then just make -jx recoveryimage

It should only take like maybe 20-30 minutes to build, ideally. Rename it and toss it into the zip to flash.

I don't really see where they would've changed anything drasitcally enough that the build tree wouldn't still work.

Yeah I'll try and get an updated build since I have some extra time on my hands, maybe sometime this week
 
TWRP 2.7 should be experimental. You'll need to build off the 2.6.3 tree. That *should* work fine with the device tree I had posted before.
 
Anyone having any luck with 2.6.3?

I've never done an android build myself, but I've been thinking about giving it a try for this (and/or while waiting for CM 10.2 official nightlies). I've used Git, C, and C++ before, but never repo nor much Java. Is anyone still planning to take a stab at 2.6.3?
 
Ill see if I can't build it sometime tomorrow if there's actually interest in it. from what I was reading before though, people are having mixed experiences on 2.6.3

If there's a dev type willing to maintain it... It shouldnt be all that hard to get 'official' support for it since we have a working build.


*edit*

Looks like my build environment ate it... :(
 
....Interesting. I got the build done... But it's building as 2.6.1.0, wonder what I have to do to get the 2.6.3.0.

I'm going to be trying to find out what's up with that from the guys in #twrp. On a side note, you DO have to modify the build tree that I posted before if you're compiling off of CM10.2 sources. I'll try and get that synced later.

For now, here's a link to the .img. You'll need to manually DD this to your phone or setup a flashable zip. https://dl.dropboxusercontent.com/u/1659941/TWRP_2.6.1.0.img

This boots, but is otherwise untested.
 
FWIW, I can confirm that it boots, mounts volumes, is able to wipe cache, davlik, and sdcard. All wipes appeared to have used rm -rf by default. Haven't tried an install or factory reset yet.
 
Back
Top Bottom