Hello,
I have a P3113 that I have previously rooted under 4.0.4, flashed with the french 4.1.1 via mobile odin, and now am trying to flash CWM on it so I can install CM10. I've since factory reset it, so I was hoping to be able to flash straight from CWM (as the CM instructions say), but it appears I don't have CWM anymore and instead have "Android system recovery <3e>". I've tried copying cwm zip files over to the SD card and then updating from those within system recovery, but it always says "E:signature verification failed."
What should I try next?
Thanks in advance!
Related
I have got an Olipad (clone of Malata zpad T2 or not?)with Tap UI 1.2.4222 and my problem is that everytime I try to istall a rom (1.2 branch) I always am unable to perform system.img download , I get always the error message "Nverror 0x12002" (bad data). All commads issued before dowloading system.img are successfully. I tried again and again but always the same error.
I have also a rom that should return me to original stock so eventually I modified its .cfg for istalling Clockwork 3.0.2.8 instead of original recovery and NOT install system.img, this worked fine and now I can enter the clockwork recovery. Then I wrote a .bat for downloading only system.img but still the same error . I tried not only the stock rom but a lot of rom for 1.2, same result. The only rom that successufully download the system is the one in the "format tool" of XDA, unfortunatenly this rom seems to be of 1.1. branch because I get "magic values mismatch"
Is it possible my internal rom is someway damaged? if not anyone know what is the problem?
thanks
Ok, none has idea.
maybe the usb cable?
Have you repartitioned using cwm?
Yes I have repartitioned by mean of cwm and wiped all. Now the situation is that, after a lot of failed tentatives, I eventually succeded in flashing the stock rom, then I backed it up by cwm. After that I tried again to flash the same stock rom in the same way I did before and again I got Nverror0x120002 (also with other roms), but this time I had the back up and used cwm to restore the system. So I suppose may the usb cable (is made by nokia) that has some problems, it worked only one time.
Phone is a Samsung S5830L.
Rooting via AceGingerRoot.zip.... OK
Installing CWM 4.x.x.x.zip via factory recovery........ NO
Installing CWM 5.x.x.x.zip via factory recovery........ NO
Installing CWM via Odin....... NO
Installing CWM via ADP....... Need more info....
Installing custom roms (ICS) via factory recovery...... NO
Restoring default ubranded S5830LUBKPJ_S5830LUNEKP5 via Odin.... YES
As you can see, Im stuck... no way I can install CWM...
In all cases, CWM installs succesfully, but when I try to boot to CWM, it stays frozen, and never loads.
Any suggestions?
Read like 10 threads already.. everyone seems to show off that CWM is simple to install.
Another detail. I think my phone is carrier locked, since its still fairly new.
I followed the steps from this thread:
http://forum.xda-developers.com/showthread.php?t=1952038
I successfully unlocked my phone and installed TWRP recovery, but that's as far as I can get. I tried to flash the latest CM10 nightly but hit an error when I run the zip, saying that the MD5 file is not found. I also tried to separately flash the boot.img from the CM10 zip, but it didn't help.
I've cleared my cache and factory wiped (through recovery), but I'm still stuck in the boot loop and can't get to the OS. Please help!!
I think the problem might be that I never actually rooted the phone, despite having unlocked it. Is there a way to root my phone via recovery, since I can't actually boot into it?
I tried to install RebelMod, but i hit an error saying "Unable to mount /data" -- I'm assuming that's because it's unrooted?
you want to root a stock ROM?
flash superuser downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
update: i managed to flash RebelMod successfully (according to TWRC) by running the zip file, but I'm still stuck in the boot loop even after doing a Factory Reset thru TWRC.
am I missing something?
wait a sec -- I got it working after I flashed the boot.img with fastboot.
Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?
Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking
Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk
Confirmed also an old recovery for me as well. Thank you very much!
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..
In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps