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

Root TWRP - Spectrum

I need help getting back CWM. I'm having major issues with this. I've been trying to flash beta 7 of aokp and/or cm10 and it's just not going well. I could go into all the details but i'll have to type to much.

Basically it does flash but everytime there an issue. I've flashed beta 7 of aokp and/or cm10 about 6 times in the past 2 hours and never once has it booted with 0 issues. At first the market would never install with gapps, then I finally got market installed and theres no keyboard. I tried to restore my backup I made right before flashing beta 7 and it fails. I'm really hating TWRP right now and would just like to go back to CWM.

The reason I need help with going back to CWM is because I can't get it to work with cm10. And I have a feeling the sotard v7 rom isn't going to flash properly in TWRP either so if someone could tell me what I'm doing wrong in cm10 I would be very very very thankful.
 
I can confirm that TWRP will not flash SOTARD v7. I'm having a nightmare here. Can someone please help me get CWM back.

I just can't figure out how to do it on while being on cm10 or aokp41. Right now i'm on aokp 41. I would just use the cab method but I have no internet connection to do it with and I'm hoping there is a way to do it while being on cm10 or aokp41. I'm in desparate need of help right now
 
No problem dirty flashing cm10b7 over b6 here...

Dirty flash may work but wipe and flash does not. If you are brave try it. I promise you this version of TWRP we have is defective. Have you tried restoring a backup with it yet? I did and it failed. Have you tried installing GAPPS with it yet? I did and it fails. Have you tried flashing v7 with it yet? I did and it failed.

But all thats neither here nor there, I just want CWM back :p
 
Dirty flash may work but wipe and flash does not. If you are brave try it. I promise you this version of TWRP we have is defective. Have you tried restoring a backup with it yet? I did and it failed. Have you tried installing GAPPS with it yet? I did and it fails. Have you tried flashing v7 with it yet? I did and it failed.

But all thats neither here nor there, I just want CWM back :p

First off, our version of TWRP is not defective as many people use it without issue including myself if you follow the instruction.

Secondly, I put in the message of the flash-able zip, on this forum, and in the first post to not use format and to set the RM -rf option.

You have now most likely corrupted your partitions. Follow these steps if you want your phone fixed. If not, expect to see your phone start to act up within a week. I had to do the same fix because my sms database kept corrupting along with other issues.

You must have CWM Recovery 6 installed.

ADB reboot recovery
adb shell
cd sbin

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p26
e2fsck -fy /dev/block/mmcblk0p26
"repeat e2fsck until it comes back clean"

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p27
e2fsck -fy /dev/block/mmcblk0p27
"repeat e2fsck until it comes back clean"

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p28
e2fsck -fy /dev/block/mmcblk0p28
"repeat e2fsck until it comes back clean"

You will be back to a pristine condition and with no OS. Install a rom and have fun. If I ever get the mount as mass storage fixed, I will be pushing out another version of TWRP and will replace mke2fs and e2fsck from CWM into TWRP just to make sure that isn't part of the issue.
 
I'll try to take a look at the code later see if I can get something working with the gui
I found the code that needs to be changed to get UMS to work, but I can't figure out what flag it's setting. When I mount, it doesn't set anything in lun/file and that needs to happen in order for the mount point to activate. Do you have any info on UMS in recovery?
 
Nitro users have problems with twrp also. I suspect that it has a bug in the apply_patch function or the if/else logic. These functions are rarely used for roms.
 
Nitro users have problems with twrp also. I suspect that it has a bug in the apply_patch function or the if/else logic. These functions are rarely used for roms.
Can any of them provide the log from /tmp/recovery.log? I've had no issues so far so I have nothing to work off of. If there is something wrong, I can see what possibly needs to be fixed.
 
Can any of them provide the log from /tmp/recovery.log? I've had no issues so far so I have nothing to work off of. If there is something wrong, I can see what possibly needs to be fixed.

You can ask. I think there's a thread in the nitro section on xda.
 
First off, our version of TWRP is not defective as many people use it without issue including myself if you follow the instruction.

Secondly, I put in the message of the flash-able zip, on this forum, and in the first post to not use format and to set the RM -rf option.

You have now most likely corrupted your partitions. Follow these steps if you want your phone fixed. If not, expect to see your phone start to act up within a week. I had to do the same fix because my sms database kept corrupting along with other issues.

You must have CWM Recovery 6 installed.

ADB reboot recovery
adb shell
cd sbin

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p26
e2fsck -fy /dev/block/mmcblk0p26
"repeat e2fsck until it comes back clean"

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p27
e2fsck -fy /dev/block/mmcblk0p27
"repeat e2fsck until it comes back clean"

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p28
e2fsck -fy /dev/block/mmcblk0p28
"repeat e2fsck until it comes back clean"

You will be back to a pristine condition and with no OS. Install a rom and have fun. If I ever get the mount as mass storage fixed, I will be pushing out another version of TWRP and will replace mke2fs and e2fsck from CWM into TWRP just to make sure that isn't part of the issue.

actually neph I had changed it to RM -rf That was the very first thing I did when I installed it the other day. Something is definitely not right with it though, unless when I flashed it in cwm it didnt take properly.
 
actually neph I had changed it to RM -rf That was the very first thing I did when I installed it the other day. Something is definitely not right with it though, unless when I flashed it in cwm it didnt take properly.
I still recommend doing a full format and file check using the above commands. It made a world of difference on my phone and you may as well if you're at a clean status.
 
I still recommend doing a full format and file check using the above commands. It made a world of difference on my phone and you may as well if you're at a clean status.

I did what you said but I'm not sure it worked right. Here's a pastebin of my command prompt C:\Users\imuCarmen\Desktop\CWM-Root-Installer-LG-Spectrum-4G\Files>ADB reboot - Pastebin.com

Things are definitely weird on my phone now even with cwm back. I'm not having all the issues I was before but there are still some weird things happening on my phone.
 
I did what you said but I'm not sure it worked right. Here's a pastebin of my command prompt C:\Users\imuCarmen\Desktop\CWM-Root-Installer-LG-Spectrum-4G\Files>ADB reboot - Pastebin.com

Things are definitely weird on my phone now even with cwm back. I'm not having all the issues I was before but there are still some weird things happening on my phone.
Unmount /cache in CWM. That's why p27 didn't work when you tried to fix and format it. It may also be part of your issue if that partition is corrupt.
 
ok neph I went back and tried again and things seemed to work but my only concern is with the last section and how it's saying "/dev/block/mmcblk0p28: 11/115200 files (9.1% non-contiguous), 16112/460800 block
s"

The other 2 say 0.0% non-contiguous and I thought that is what I wanted. Am I right in my thinking or did it work? I'm still experiencing the issue I mentioned before so I'm concerned about what issues may still be going on.

C:\Users\imuCarmen\Desktop\CWM-Root-Installer-LG-Spectrum-4G\Files>ADB reboot re - Pastebin.com
 
ok neph I went back and tried again and things seemed to work but my only concern is with the last section and how it's saying "/dev/block/mmcblk0p28: 11/115200 files (9.1% non-contiguous), 16112/460800 block
s"

The other 2 say 0.0% non-contiguous and I thought that is what I wanted. Am I right in my thinking or did it work? I'm still experiencing the issue I mentioned before so I'm concerned about what issues may still be going on.

C:\Users\imuCarmen\Desktop\CWM-Root-Installer-LG-Spectrum-4G\Files>ADB reboot re - Pastebin.com

That is a clean scan. When I was getting bad scans, it'd be scrolling messages about fixing items for almost 10 minutes.
 
First off, our version of TWRP is not defective as many people use it without issue including myself if you follow the instruction.

Secondly, I put in the message of the flash-able zip, on this forum, and in the first post to not use format and to set the RM -rf option.

You have now most likely corrupted your partitions. Follow these steps if you want your phone fixed. If not, expect to see your phone start to act up within a week. I had to do the same fix because my sms database kept corrupting along with other issues.

You must have CWM Recovery 6 installed.

ADB reboot recovery
adb shell
cd sbin

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p26
e2fsck -fy /dev/block/mmcblk0p26
"repeat e2fsck until it comes back clean"

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p27
e2fsck -fy /dev/block/mmcblk0p27
"repeat e2fsck until it comes back clean"

mke2fs -t ext4 -b 4096 /dev/block/mmcblk0p28
e2fsck -fy /dev/block/mmcblk0p28
"repeat e2fsck until it comes back clean"

You will be back to a pristine condition and with no OS. Install a rom and have fun. If I ever get the mount as mass storage fixed, I will be pushing out another version of TWRP and will replace mke2fs and e2fsck from CWM into TWRP just to make sure that isn't part of the issue.
Will CABing back to V7 accomplish the same thing?
 
Looks good. Flashes good. Just doesn't wipe. Had to install ROM manager to get cwm back

I made sure to check that option when I first booted into twrp.

This is my favorite recovery. I'll definitely be trying it again when you post an update
 
Looks good. Flashes good. Just doesn't wipe. Had to install ROM manager to get cwm back

I made sure to check that option when I first booted into twrp.

This is my favorite recovery. I'll definitely be trying it again when you post an update
I'm confused about the "doesn't wipe" comment. What part doesn't wipe?
 
Can anyone who is currently running TWRP on the Spectrum please provide me with a reading while you're inside of TWRP.

I need to know what you have in directory /sys/devices/platform/msm_hsusb/gadget/ . You can find out by browsing with TWRP's built in file manager, or with ADB shell.

Here is my current status on USB mount, but I need to know if anyone is getting a lun besides lun2, which is what I'm getting. If everyone is getting lun2, then I'm going to hard code the change to lun2, instead of being a variable, which returns 0.

Finished running boot script.
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'mount'
I:Set page: 'usb_mount'
E:Unable to open ums lunfile '/sys/devices/platform/msm_hsusb/gadget/lun0/file': (No such file or directory)
 
I'm confused about the "doesn't wipe" comment. What part doesn't wipe?

I've grown into a habit of never dirty flashing ROMs. After I installed twrp I decided to go back to a stock base ROM then back to cm10 to see if it would fix GPS.
Wiped everything. Flashed sotard.apk. froze at 4g logo. Wiped everything. Flashed cm10. And all my apps and data from before I wiped the first time was still in my phone. I tried wiping multiple times. No errors. But nothing happens.
 
Can anyone who is currently running TWRP on the Spectrum please provide me with a reading while you're inside of TWRP.

I need to know what you have in directory /sys/devices/platform/msm_hsusb/gadget/ . You can find out by browsing with TWRP's built in file manager, or with ADB shell.

Here is my current status on USB mount, but I need to know if anyone is getting a lun besides lun2, which is what I'm getting. If everyone is getting lun2, then I'm going to hard code the change to lun2, instead of being a variable, which returns 0.

Finished running boot script.
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'mount'
I:Set page: 'usb_mount'
E:Unable to open ums lunfile '/sys/devices/platform/msm_hsusb/gadget/lun0/file': (No such file or directory)
cd to those paths in adb shell, look for the file named 'file' that has something in it. I wasnt able to find one when working on CWM. ;)
 
cd to those paths in adb shell, look for the file named 'file' that has something in it. I wasnt able to find one when working on CWM. ;)
PG, I've already gotten to that part and it properly puts the /dev/block/mmcblk1p1 into the file. The issue is that the source code calls out %d, which for some reason only picks up 0, but when I boot into TWRP, I have a lun of 2. I made a copy with the lun hardcoded, and it works, but now my script to have the phone show up as an SDcard to Windows no longer works. It's a bit aggravating right now.

Also, you won't see that path in CWM because I believe koush used the GB kernel, and the GB kernel didn't contain that path.
 
I've grown into a habit of never dirty flashing ROMs. After I installed twrp I decided to go back to a stock base ROM then back to cm10 to see if it would fix GPS.
Wiped everything. Flashed sotard.apk. froze at 4g logo. Wiped everything. Flashed cm10. And all my apps and data from before I wiped the first time was still in my phone. I tried wiping multiple times. No errors. But nothing happens.
I had that happen when I had files in the /sdcard/.android-secure/ directory. For some reason it couldn't unlink them when doing a format, but it could with the RM -rf option on. Did you have this option on when you tried it? If I can figure out what happened, I'll see if I can provide a solution in the next build.
 
Back
Top Bottom