Trying to install custom ROM - getting error

[rkhanso]

The phone was rooted before....then my daughter wanted to sell the phone and she did a reset to factory default from withing the Android OS. I guess that's a bad thing to do.

After that, it only boots into the CWM recovery. I've tried to install some other ROMs (don't have the original from VM). The ROMs say they are successfully installed, but when I reboot, I still get into recovery mode.

The message at the bottom after booting says:

CWM-based Recovery v5.0.2.7
e:Bad boot message
"recovery "​

Can someone help me out or point me to the right forum post? I've searched, but must be searching on the wrong words because I don't see the solution in the results.

 

[rkhanso]

Wait....I found this thread. Is this the solution?
Break from recovery boot loop!! (Slider too) - Android Area51

 

[rkhanso]

I did run through the instructions at the Android Area 51 website. It worked, the phone does boot to Android now....but in my other attempts to fix it, I did install a different ROM on the phone. Now the WiFi doesn't work. Anyone know of a link to the original VM ROM? Or maybe a ROM that everything works in it?

 

[dark_samus]

http://forums.androidcentral.com/vi...-unrooted-slider-rom.html?highlight=stock+rom

also a safer method for the recovery loop fix http://forums.androidcentral.com/vi...ry-loop-after-factory-resetting-settings.html

 

[rkhanso]

Thanks for that link. I really appreciate it.

I'm now having a problem getting that ROM on the phone...
The phone is NOT activated. My daughter wants to sell the phone and has stopped/cancelled her VM account.
The ROM I installed when trying to fix this problem gives an error when trying to enable WiFi (unless WiFi is disabled because the phone is not activated??)

Anyway, I can't get the ROM Manager app installed on the phone because I can't access the Play Store, nor can I just install the .apk on the sdcard due to the fact that there is no file manager on the phone to manually install an .apk.

I did get the ROM linked above installed on the SD Card. I got an error when trying to install it (using the stock Android recovery - I think the CWM was blown away when I used that recovery loop solution from Android Area 51) so I changed the name of the .zip to update.zip

Now I get an error installing the .zip

-- Install /sdcard
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.​

Can anyone help?

 

[rkhanso]

I installed Java JDK and Android SDK and was going to install the Rom Manager app that way. I get Android SDK to see the phone, but it won't install the .apk - it keeps saying "waiting for device".

Yes, I do have the debugging option checked on the phone.

C:\Users\Roger\Downloads\adt-bundle-windows-x86-20130717\adt-bundle-windows-x86-
20130717\sdk\platform-tools>adb devices
List of devices attached
A10000199B2602 device​

C:\Users\Roger\Downloads\adt-bundle-windows-x86-20130717\adt-bundle-windows-x86-
20130717\sdk\platform-tools>adb install d:\ROM_Manager_5_5_1_7.apk
4531 KB/s (3109041 bytes in 0.670s)
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -
- waiting for device -​

I've searched the web for a solution but can't find it.

I've tried it with the phone connected in both the 'charge only' state and the 'Mass Storage' state and get the same results.

I know the drivers on my PC are working OK because when I connect the phone as Mass Storage, Windows sees it and wants to import pictures.

I am using Windows 7 Ultimate 64-bit on my PC. I installed the 32-bit JDK as per the instructions I was following.

Not sure what else to do.

 

[gollum18]

Try using adb to push it to your sdcard then sideload it from there. Adb install is finnicky on some devices, but you should be able to install it from your sdcard.

Just so you know though you should have installed 64bit java and jdk as the 32bit doesn't match your CPU architecture. That is most likely the cause of the error.

Sent from my SPH-L710 using Tapatalk 2

 

[rkhanso]

when trying to push a ROM, I get this:

C:\Users\Roger\Downloads\adt-bundle-windows-x86-20130717\adt-bundl
20130717\sdk\platform-tools>adb push update.zip /update
failed to copy 'update.zip' to '/update': Read-only file system​

Maybe that's the issue? Read-only file system on the phone?

I tried:

C:\Users\Roger\Downloads\adt-bundle-windows-x86-20130717\adt-bundle-windows-x86-
20130717\sdk\platform-tools>adb shell sysrw
error: closed​