Database Develop

[Q] D3 question for experts

okay guys. i downloaded the nexus prime theme. went to go flash it. my phone will no longer go into clockwork recovery mode. it just freezes at the boot screen. i even tried to flash it via rom manger but my phone just reboots itself. i cant even go into recovery mode. it just says recovery mode on myphone and it says battery OK connect usb stuff like that. Does anyone have this problem? i am stock deodeodexed and i have bootloader. i even updated the clockwork recovery and i cant get my phone into any type of bootloader anymore. any thoughts or suggestions? is it possible to flash via command promt on my computer? im stuck guys. anything can help!

If you look like 4 threads down I thought someone posted some similar **** and it was solved..
Sent from my DROID3 using XDA App

i mean.. i just looked and i didnt see anything. could you quick reply the thread for me or something? this is really frusterating for me because i have no idea whats going on! haha

Sorry. The thread I thought it was wasn't solved. I thought someone had figured it out but I can't really look atm. I'm at work, lol.
Sent from my DROID3 using XDA App

haha its allright man i just figured it out. it took me a long time. but now whenever i reboot my phone it automatically boots into clockwork recovery. so i just hit reboot again then it works lol. so its not really a problem its just kind of annoying. then again i rarely reboot my phone soo i dont really care

E file signature verification failed?

I am a noob an I am alittle confused with installing roms. I tried to install one and it went through everything and then it stopped and it said in yellow that the E file signature verification has failed now what does this mean. Please help.
Sent from my DROID3 using XDA App

What was the exact name of the rom (or filename)... was it a stock rom (SBF/XML) or was it one of the custom roms?
Also was your phone rooted?

I was trying to install a couple but the one I really have been trying in the liberty 3 2.0.
Sent from my DROID3 using XDA App

Are you using safestrap for your clockworkmodrecovery or are you using regular bootstrap?
And when you're in clockworkmod recovery what exact steps did you do to flash? You should wipe data & cache, then choose install zip from sdcard.
Sent from my XT860

I don't know how to use or get bootstrap and I don't know alot about safe strap yet. I tried different ways I tried using rom manager an downloading the rom from there then it will ask if I want to boot into recover I push ok and the phone just reboots. Nothing happens so I tried rom toolbox an did the same thing. So I tried to boot myself by pushing the power and x an I did as you said I wiped data a cache then I reset and restored my phone went back an installed zip from sd card then it starts to install then it says E file signature verification has failed.
Sent from my DROID3 using XDA App

Ahhhh ok.
It sounds like you are trying to install zips via the stock recovery. That recovery will only install signed/official ones, not custom rom zips.
If you want to install custom roms, try this method (but I recommend browsing through the other threads. There is a lot of useful info out there). This is the safestrap method. Safestrap allows you to have your stock rom (that you are on now) in the "non-safe zone" and with safestrap you can enable the "safe zone" for installing your custom rom.
1) make sure your phone is rooted if it isn't already. There are threads about this... I used DoomLord's root (version 4) for my phone but read up.
2) install safestrap 1.08 (u can find it in the droid 3 development forum). It is an apk file.
3) when you run safestrap 1.08 from your app drawer, superuser will probably ask you if you want to allow it root access, say yes.
4) in the app, hit the first button. It will install safestrap so you can boot into safestrap recovery. When it says its done, restart phone.
5) upon restart, you will be greeted by the safestrap splashscreen. It gives u 10 seconds to hit Menu to take you into safestrap recovery. Otherwise it will just continue with booting.
6) so hit menu. Safestrap ecovery appears. It will indicate that safe mode is not enabled yet. You are in non-safe right now (your stock rom)
7) this step is optional but I'm sure everyone will recommend it (I do also). Navigate your selection with the down/up volume buttons and hit power when you get to "backup". This will back up your non-safe zone and dump it onto your sdcard (internal or external). You can restore it to your non-safe zone (only) if you happen to mess up your non-safe system. The backup will be stored in /safestrap/backup. of whatever card you select.
8) now that that's done, it will take you back to the main menu of safestrap recovery
9) Go to "safe boot menu" and hit Toggle safe zone. Don't do the quick toggle, just do the normal one (the first one)
10) when that is done, you will notice the colour of the text has changed. And at the top it will say safe zone enabled. You can now install your custom rom by going to "install zip from sdcard" from the main menu of safestrap*
*Note that when installing roms, make sure to choose Wipe Data first. It will wipe your data and cache. Then go into mounts and storage and choose "format /system" (thanks Endo). Some people also like to go into the advanced menu and wipe the dalvik cache as well (is this necessary? I do it every time because I had to back on my old htc... maybe someone can comment on this?) It doesn't seem to hurt anything when I do it, so...
So after your wipes, you can go to "install rom from sdcard" . Choose the .zip of the rom (of course) to begin install. When the rom has finished installing, you can go back to the main menu and choose reboot phone. You will be greeted by the safestrap splashscreen again. It will tell you that safe zone is enabled. Wait the 10 seconds to boot normally or you can hit the search button to go immediately.
On first boot of many roms, it may take a little longer than normal to start up. Be patient. If it never boots (and you are looking at the boot animation forever... say more than 5-10 minutes?) Then... somethings wrong, or you may have forgotten to do your wipe procedure, but go to that rom's thread and read all the posts to see if others experienced the same thing... someone could have posted a good suggestion or solution
Oh, if you want to switch back to non-safe mode, restart phone, get into safestrap recovery, go into safe boot menu, and hit toggle. Then restart phone.
If something disastrous occurs, there are Unbrick and Fastboot threads in this forum where you can download a stock rom for your phone and flash to your phone via RSD Lite, which will pretty much restore your phone to stock. (No more safestrap, no more root). Read through those to get more info.
Hope this is helpful. Good luck!
Sent from my XT860

ryanw5489 said:
I don't know how to use or get bootstrap and I don't know alot about safe strap yet. I tried different ways I tried using rom manager an downloading the rom from there then it will ask if I want to boot into recover I push ok and the phone just reboots. Nothing happens so I tried rom toolbox an did the same thing. So I tried to boot myself by pushing the power and x an I did as you said I wiped data a cache then I reset and restored my phone went back an installed zip from sd card then it starts to install then it says E file signature verification has failed.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I'm not really sure what you are doing but uninstall any recovery you may have installed and ditch rom manage(you can keep the toolbox) go to www.hash-of-codes.blogspot.com go to downloads and get safestrap. Install it, open it and click install recovery. Reboot your phone, you'll get a screen saying pish menu to enter recovery then once it enters go to safe mode menu(or whatever it exactly says) and enter safe mode. Once safemode is active(it says at the top of the screen)go to mounts and storage and format system then do a data/cache wipe, the install zip from sd
If you're doing what I think you're doing you are new to this and I would suggest reading as much as you can in this forum and by googling the various terms you find so you don't brick your phone
Sent from my DROID3 using xda premium

So do you want me to uninstall clockwork recovery?
Sent from my DROID3 using XDA App

ryanw5489 said:
So do you want me to uninstall clockwork recovery?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Yes. Safestrap will install its own CWR
Sent from my DROID3 using xda premium

So how do I go about uninstalling cmw.
Sent from my DROID3 using XDA App

ryanw5489 said:
So how do I go about uninstalling cmw.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Safestrap will clean that up. Just get rid of any bootstraps and rom manager
Sent from my DROID3 using xda premium

So I have to get rid of rom manager because I paid for it an really don't feel like losing money on it. I don't think I have any bootstrap so I should be good there. I'm sorry that I don't know alot I'm really new an I don't have the most time to even do alot of research so thanks for helping me out greatly appreciated.
Sent from my DROID3 using XDA App

ryanw5489 said:
So I have to get rid of rom manager because I paid for it an really don't feel like losing money on it. I don't think I have any bootstrap so I should be good there. I'm sorry that I don't know alot I'm really new an I don't have the most time to even do alot of research so thanks for helping me out greatly appreciated.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
If you have your heart set on rom manager, I believe it will work, but I've never used it so I can't help you there. I recommend safestrap because once you're in safemode its pretty hard to screw up your phone in any serious manner. In safemode you'll always be able to access recovery.
In a google search of your issue I found a recommendation of turning off signature verification. I know I've seen an option for this or something really damn similar in clockwork recovery. You can try that if you like but I don't know the effects of it. As always, I'm not responsible if you brick your device
That said, I would also suggest that you look into obtaining rsdlite and the appropriate fastboot package(you may know this as an sbf, although that term isn't totally correct)so if you do brick your device you know how to recover it. There's a sticky in the dev forum about it
Sent from my DROID3 using xda premium

Thank you I understand I wouldn't ever blame anyone for my mistakes so your good. I was thinking about using safestrap anyways just haven't had time to research it much yet. Probably would be best since I don't know much about roms anyways. Now it's not that I have it set with rom manager just seemed easy to use and I like rom toolbox alittle more anyways. I also know that not all roms are comparable with the safestrap so that's another reason why I haven't used it yet.
Now on another topic. I have downloaded safestrap on my computer all I have to do is plug my phone to the computer an put it on mass storage and place it in the sd card or internal memory and unplug it an click on it on my phone.
I really need to start some research cause this stuff is pretty hard.
But thanks for your help again
Sent from my DROID3 using XDA App

I have installed safestrap. Is there anywhere that's best to look up how to use it.
Sent from my DROID3 using XDA App

i have installed safe strap i rebooted my phone and now it is stuck on boot screen now what did i do to my phone and what happen can it be fixed?

Which boot screen? What does it look like? Is it the safestrap boot screen (that says you can hit Menu to get into recovery?)
I replied to this thread with instructions on how to use it. Were they not useful? Did you get stuck somewhere?

LaZiODROID said:
Which boot screen? What does it look like? Is it the safestrap boot screen (that says you can hit Menu to get into recovery?)
I replied to this thread with instructions on how to use it. Were they not useful? Did you get stuck somewhere?
Click to expand...
Click to collapse
I don't know how I missed your huge write up. More detailed than mine.
I figured the same, stock recovery. I'm not sure what steps he's taken before he wrote this thread.
OP if its the boot animation, on first boot it takes a long time. 5 minutes normally but give it 10 to be sure. If its the splash screen you may have issues. Is the safestrap splash coming up, where it says press menu
You may have to use rsdlite or the fast unbrick to restore your phone to stock. If you can write us EVERYTHING you've done in as much detail as possible, and exactly what is happenig now we can come up with a solution.
I think often all the various terms can be confusing to newcomers. I have a feeling perhaps that you still have a bootstrap installed and safestrap.
Sent from my DROID3 using xda premium

ok well first i went to hash of codes and downloaded the safestrap. Then i put the download on my sd card and i went into my files and pushed sd memory. then i went and found the apk and downloaded the safestrap. it installed fine then i pushed install recovery.then after all that i rebooted my phone and now it is stuck on the BIG RED Motorola symbol that says DUAL CORE TECHNOLGY. I even took out battery and tried that did not work. i also tried pushing power and x and restoring phone. still nothing. i must of missed something i just cant figure what that would be! Please help!

ryanw5489 said:
ok well first i went to hash of codes and downloaded the safestrap. Then i put the download on my sd card and i went into my files and pushed sd memory. then i went and found the apk and downloaded the safestrap. it installed fine then i pushed install recovery.then after all that i rebooted my phone and now it is stuck on the BIG RED Motorola symbol that says DUAL CORE TECHNOLGY. I even took out battery and tried that did not work. i also tried pushing power and x and restoring phone. still nothing. i must of missed something i just cant figure what that would be! Please help!
Click to expand...
Click to collapse
No I meant with rom manager and rfom toolox. All the steps you took prior to posting on this thnread
Sent from my DROID3 using xda premium

Cm9 on bootable sd wont work

I've been trying like crazy to make a bootable sd card to run cm9 with no success. the Cyanogen universal bootloader comes up, but when it goes to boot up the ROM it just sits on a black screen for about 15 seconds then reboots. I can't figure out what I'm doing wrong. Any suggestions would be greatly appreciated. Thanks
Sent from my NookColor using xda premium

It would be so much useful if you could also describe us which installation method did you follow.
Produced by NookColor at CM9 4.0.4

I followed verygreens method. Over the last 6 months, I've performed this method a good 30-40 times for cm7. From what I understand, I'm supposed to perform this same method for cm9. I've tried using both image installers just to make sure I was using the correct one
Sent from my NookColor using xda premium

purpleurkle said:
I followed verygreens method. Over the last 6 months, I've performed this method a good 30-40 times for cm7. From what I understand, I'm supposed to perform this same method for cm9. I've tried using both image installers just to make sure I was using the correct one
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
You need to rename the cm zip to begin with update-.
Or are you starting with a fresh SD burned with a new image? You should not get a cyanogen logo if you are. You should just get a loading followed by the penguin and some text. If you do not have the newest image, I think you can get it on leapinlar's tip thread.

I've tried it with the new image and the old one. I'm passed the penguin, it ran the text and shut off. When I turn it back on I get the cyano universal boot, then it goes to a black screen for about 10 or15 seconds then it reboots and will do this over and over again if I don't shut it down.
Sent from my NookColor using xda premium

Will it still boot to emmc when you select that with the boot menu?

Yes it does.
Sent from my NookColor using xda premium

purpleurkle said:
Yes it does.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Ok, that means you are not in a recovery bootloop. And you do not need to repair any partitions on emmc. And given the fact that it boots to cyanoboot bootloader rather than the little penguin means the rom flashed successfully. The only thing I can think of is a corrupted download file for CM. Try re-downloading.

ok, now when i'm in the penguin stage with text, it reaches a point were is says it cant find initial install files. which i assume means it cant find the rom. in know your first thought is going to be that i didnt rename the rom update-, but i did. I am just adding update- to the beginning of the file name right? I'm not supposed to take away the cm- all together am i? it reads update-cm-9.

purpleurkle said:
ok, now when i'm in the penguin stage with text, it reaches a point were is says it cant find initial install files. which i assume means it cant find the rom. in know your first thought is going to be that i didnt rename the rom update-, but i did. I am just adding update- to the beginning of the file name right? I'm not supposed to take away the cm- all together am i? it reads update-cm-9.
Click to expand...
Click to collapse
And it is on the boot partition, right? That name is OK.
Sent from my Nook Color running ParanoidAndroid and Tapatalk

yes it is. i ran it again and it took it, but now its doing the same thing it was before were it goes from cyanoboot to a black sceen for 15 seconds or so then reboots. the thing is i got this rom from a different source this time samiam303. could i be doing something wrong when expanding the partition? im expanding it to around 1g.

purpleurkle said:
yes it is. i ran it again and it took it, but now its doing the same thing it was before were it goes from cyanoboot to a black sceen for 15 seconds or so then reboots. the thing is i got this rom from a different source this time samiam303. could i be doing something wrong when expanding the partition? im expanding it to around 1g.
Click to expand...
Click to collapse
Why are you expanding the boot partition so large? And how are you doing it? And you are doing it before you boot the first time, right? You may be confusing the verygreen script that partitions the rest of the SD. It may be that the other partitions are not created right. Then when you flash, the rom is not installed correctly.
Sent from my Nook Color running ParanoidAndroid and Tapatalk

purpleurkle said:
yes it is. i ran it again and it took it, but now its doing the same thing it was before were it goes from cyanoboot to a black sceen for 15 seconds or so then reboots. the thing is i got this rom from a different source this time samiam303. could i be doing something wrong when expanding the partition? im expanding it to around 1g.
Click to expand...
Click to collapse
Are you expanding the boot partition prior to doing anything else?
It is important that if in windows... when you expand boot partition... do it before any other partition are on it... modifying ext partitions in windows will cause major issues... including moving them.
Also... how long are you waiting... initial boot after running the setup will have a black sceen for several minutes.

I'm expanding to1g because someone told me to do so. I'm expanding after restore to virtual hard drive, but before puting on cm9 file. Could it be because in expanding it to much? I'm using easy partition manger. I don't see a way to expand the partition before restore to virtual hard drive. In response to dizzyden, (like I said in my first post), after the cyanoboot screen it goes to the black screen for about 15 seconds or so then reboots and will continue to do so over and over until I hard power it. I'm aware that I'm coming off as an idiot but up until 6 months ago I'd never ever sat down at a computer. So thankyou for your patience
Sent from my NookColor using xda premium

purpleurkle said:
I'm expanding to1g because someone told me to do so. I'm expanding after restore to virtual hard drive, but before puting on cm9 file. Could it be because in expanding it to much? I'm using easy partition manger. I don't see a way to expand the partition before restore to virtual hard drive. In response to dizzyden, (like I said in my first post), after the cyanoboot screen it goes to the black screen for about 15 seconds or so then reboots and will continue to do so over and over until I hard power it. I'm aware that I'm coming off as an idiot but up until 6 months ago I'd never ever sat down at a computer. So thankyou for your patience
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
You should expand immediately after burning to the card. And 300Mb should be plenty for whatever you want to do. Anything more is just wasting your SD space. It is possible that having it so large did mess it up, but I don't know why it would. Just to be safe, I would boot without the zip on it and come back later after the first boot and it has partitioned the SD and put it on.

purpleurkle said:
I'm expanding to1g because someone told me to do so. I'm expanding after restore to virtual hard drive, but before puting on cm9 file. Could it be because in expanding it to much? I'm using easy partition manger. I don't see a way to expand the partition before restore to virtual hard drive. In response to dizzyden, (like I said in my first post), after the cyanoboot screen it goes to the black screen for about 15 seconds or so then reboots and will continue to do so over and over until I hard power it. I'm aware that I'm coming off as an idiot but up until 6 months ago I'd never ever sat down at a computer. So thankyou for your patience
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
No problem urkle... Personally, I'd install CM7 on the SD and if/when it boots correctly... update it to CM9
Leap... I've only seen the size issue when boot partition is 2GB or larger... and don't ask me why I tried that LOL

OK, so I should burn the installer image, then expand the partition, then boot, then go back and put the cm9 zip on?
Sent from my NookColor using xda premium

purpleurkle said:
OK, so I should burn the installer image, then expand the partition, then boot, then go back and put the cm9 zip on?
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes

Still no change. Im still able to make cm7 burn without a problem, the only thing I'm doing different with the cm9 burn is position expansion.
Sent from my NookColor using xda premium

Hmm, and it does do boot to emmc with the cyanogenmod boot menu? I suspect partition 2 issues on emmc, but it would not boot to emmc if that was messed up.
Edit: Why are you expanding the boot partition at all. To make CM9 fit? If that is the only reason, go get my version that has already been expanded. Your PC may be doing something to the card. You can get my version by visiting my tips thread linked in my signature.

Can't enter Recovery or Boot

Pretty sure I've perm bricked, but figured I would ask anyway. I can not access recovery, or boot at all. Your probably asking how did he do this. Well I went to remove android, right before I did I was asked for format, when I did I'm assuming my android partition was messed up along with recovery. Either way I can't enter usb mode, enter recovery. Any ideas?

No one? That's about what I figured...

techno-update said:
Pretty sure I've perm bricked, but figured I would ask anyway. I can not access recovery, or boot at all. Your probably asking how did he do this. Well I went to remove android, right before I did I was asked for format, when I did I'm assuming my android partition was messed up along with recovery. Either way I can't enter usb mode, enter recovery. Any ideas?
Click to expand...
Click to collapse
Do you mean you can't enter webOS's USB recovery, or CWM's recovery? Have you tried using this guide to use webOS doctor to restore the Touchpad to factory settings?

Archangel013 said:
Do you mean you can't enter webOS's USB recovery, or CWM's recovery? Have you tried using this guide to use webOS doctor to restore the Touchpad to factory settings?
Click to expand...
Click to collapse
Can't enter either... and doctor doesn't register it.
Sent from my DROID3 using Tapatalk 2

techno-update said:
Can't enter either... and doctor doesn't register it.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
I've got nothing, then =/ Sorry. Hopefully someone more knowledgeable will come around and know how to help.

Have you tried holding the power and home button for at least a minute, it is supposed to do a reset .If you cannot turn it on maybe HP can't either if it is still under warranty send it back.
Sorry to state the obvious but I can't think of anything else .

sstar said:
Have you tried holding the power and home button for at least a minute, it is supposed to do a reset .If you cannot turn it on maybe HP can't either if it is still under warranty send it back.
Sorry to state the obvious but I can't think of anything else .
Click to expand...
Click to collapse
Ya already tried that I'm afraid.
Sent from my Xoom using XDA Premium HD app

Moboot fails to boot

So I tried to customize the moboot screen and replaced moboot.background.tga with one I made and now I can't boot into anything. No moboot, no android, no webos. Is there a way to reinstall with acmeinstaller. Someone was talking about using novaterm but I have no clue how to use it. Any advice? Oh and I get this error message: [90] panic (caller 0x500042e1): gfx_surface_blend: unimplemented color space combination (source 0 target 2)
Sent from my Galaxy Nexus using xda premium

Never mind I finally was able to get into USB mode and wiped with webos doctor and now reinstalling :thumbup:
Sent from my Galaxy Nexus using xda premium

syrum84 said:
Never mind I finally was able to get into USB mode and wiped with webos doctor and now reinstalling :thumbup:
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
did the moboot screen show up cuz when resetted mine it wouldnt go into moboot it would go straight to webos

sflecha35 said:
did the moboot screen show up cuz when resetted mine it wouldnt go into moboot it would go straight to webos
Click to expand...
Click to collapse
This happens because the doctor resets the boot partition, removing android and moboot
Sent from my ss_tenderloin using Tapatalk HD