[Q] Phone Rooted but fail to verify whole-file? :( - Android Software/Hacking General [Developers Only]

Okay, here's the deal...
I've searched everywhere for every possible way to get around this and it still doesn't work.
I'm on a Mac (OS X 10.6). It says my phone is rooted (used z4root), then I downloaded busybox, and ROM Manager and Astro. i did the flash for clockworkmod through ROM manager, said everything was good. I try to go into recovery mode, reinstall packages, then I get the error "failed to verify whole-file" type thing. my recovery mode is 3e, and it's blue but from what i've been reading, it should be green? I'm trying to make it green!
I just got my captivate i896/i897 a couple days ago, so I wont mind if i need to restore it (i accidentally did that today but it still ended up being rooted when I finished). I'm brand new to all of this, the most experience i've had with this is..jailbreaking an iphone 4 lol. Any help would be much appreciated! All I want to do is make my phone faster (overclock it) and set a nice theme on it. This is so confusing and I'm starting to get so frustrated with it, close to the point where i'd throw it against a wall...legit. Please help!!

Related

[Q] Clockwork Recovery problem

First.. I want to say hello and that i've been reading around these forums for quite a while since I got my Droid about a year ago. I haven't posted anything till now.. but that's only because everyone else usually get's the answers typed faster than me. lol
On to the problem... I think I screwed up. I JUST bought this thing today. I got a little too excited about getting this tablet rooted and might have jumped the gun a little. I used the apk that has been around to root. No problems there. I got ROM Manager loaded... and I ended up flashing the newest recovery from there before realizing that everyone else says to use something else.
So... at this point, i'm unable to reboot into recovery at all. It starts up, acts like it's about to, and then just reboots again into the OS instead. Is there a way to fix this and get it on the correct recovery image or have I totally screwed myself over? Maybe through ADB? I can only tolerate this horrid TnT OS for so long. Took me 20 minutes to get it to update without a FC... Browser, weather, calendar, and a bunch of other stuff FC on me when I tried starting.. Fortunately, those issues are less frequent with the update, but still not working keeping.
I need some "stock(CyanogenMod)" Froyo goodness.. lol I can't have my year and a half old phone outclass this tablet for too long. If anyone can offer any help on this, I would greatly appreciate it.
The good news is you are still booting into the OS, so I doubt you've screwed anything up too bad. Most likely Clockwork Mod just never flashed so you are still running with the gimpy stock recovery and it's puking on the update.zip file you have on your internal sd card for some reason.
First suggestion is get a copy of Clockwork Mod 0.8 and try installing it. The instructions here are geared toward installing from an external from an external MicroSD card: http://forum.xda-developers.com/showthread.php?t=865245 I am not certain why they say that's the only way to do it, since I never did it that way.
I just downloaded this: http://www.mediafire.com/?dvleg4oatkfxm7w and stuck the update.zip and recovery folder into my /sdcard directory, then turned my tablet off, then held down Vol+ and turned it back on. Clockwork Mod should install itself and boots into Clockwork Mod, and that was that.
I never used ROM Manager at all on my G Tablet, so I can't speak to doing anything that way, but I would stick with the tried and true methods at least until you have Clockwork Mod running.
If that fails and you really can't get any recovery working, maybe something did get botched and you might need to use nvflash to fix it, but I doubt it.
Once you get Clockwork Mod running properly, just copy over the update.zip for TNT Lite or Vegan ROM, flash, and wipe data, then you should be good to go.
Worked perfectly and entirely from the tablet! I installed CM6.1 and I'm a bit upset at the lack way it looks, but then, its packed for smaller screens, so I understand. Thank you for the quick reply. I'm off to try TnT Lite now.

[Q] Please help! Cyanogen didn't like my Ascend

I need some serious help ...
I rooted with Z4root, and it worked great, and EASY!!!!!
I downloaded and bought the RoM Manager from the Market because after weeks of reading, reading, and reading some more, I just couldn't bring myself to install a RoM myself. The only 2 RoM's that popped up for me was PlayfulGod & Cyanamogen 7.
I first chose Cyan... and it was great except the Market was gone, and a few other things didn't work all of a sudden. Then when I tried to change with RoM Manager it kept saying I needed to get the newer version. Long story short, I was finally able to switch over to PlayfulGod via RoM Manager. It's been a long few days, I don't remember what it was that made me want to go back to Cyan, but I figured I could just download a new Market and all would be fine. So, RoM Manager again ... download Cyan, install, backup. While it was backing up I went to sleep.
When I woke up this morning, my phone was in a looping bootmode! I get the movie thing that Cyan boots up with, then the android guy - then the movie again, android guy, movie android, over and over. I can't even get to the Volume Down, End, Power spot. When I try, I get the Huawei screen and that's all it'll do.
I was too scared to "flash" a RoM myself, and now I am completely lost. Please help me fix my phone ...
~Ky
txheart0711 said:
I need some serious help ...
I rooted with Z4root, and it worked great, and EASY!!!!!
I downloaded and bought the RoM Manager from the Market because after weeks of reading, reading, and reading some more, I just couldn't bring myself to install a RoM myself. The only 2 RoM's that popped up for me was PlayfulGod & Cyanamogen 7.
I first chose Cyan... and it was great except the Market was gone, and a few other things didn't work all of a sudden. Then when I tried to change with RoM Manager it kept saying I needed to get the newer version. Long story short, I was finally able to switch over to PlayfulGod via RoM Manager. It's been a long few days, I don't remember what it was that made me want to go back to Cyan, but I figured I could just download a new Market and all would be fine. So, RoM Manager again ... download Cyan, install, backup. While it was backing up I went to sleep.
When I woke up this morning, my phone was in a looping bootmode! I get the movie thing that Cyan boots up with, then the android guy - then the movie again, android guy, movie android, over and over. I can't even get to the Volume Down, End, Power spot. When I try, I get the Huawei screen and that's all it'll do.
I was too scared to "flash" a RoM myself, and now I am completely lost. Please help me fix my phone ...
~Ky
Click to expand...
Click to collapse
With any cyanogen mod you Have to flash google apps separate. That will solve for market problems. Since you have to flash GAPPS you might as well re download whichever cm7 check the md5 checksum and reflash that. You can find videos on youtube that give you a step by step of the flashing and backup process. Just search around the web.
Can somebody help me I love cyanogen mod and I'm trying to update my ascend to cm7.2 but it failed everytime I try any ideas please
Sent from my M860 using XDA App

[Q] Question concerning Dragonzkiller's Droid x2 CM9 Rom

Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.

[Q] Verizon Galaxy S3- Me Messing up

As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.

Kernel/System Load Issues

Hey guys,
I've used XDA for quite a while now as a resource for rooting and flashing my phones. After some trial and error, I finally got a custom rom and root onto my previous phone, the Samsung Galaxy Light (SGH-T399). However, I booted the T-MOBILE kernel, not MetroPCS, and got locked out. So I bought a Galaxy Core Prime, and after a bit decided to root that as well. But when I did some sort of permission modification and tried to make my extSD writeable, the phone crapped out. It would not load the kernel past the bootloader. I tried flashing everything and anything. It just would not allow it to write or mount properly.
So I went back and tried restoring the T399 until I sorted that out, and the same thing is happening. I even flashed ShabbyPenguins stock rom which never failed me before, to no avail . I was able however to successfully install TWRP again. Someone please help me out, I can't afford another phone at the moment. Im still a novice, but I know enough to know it's more than just a mistake in Odin or a file I didn't upload. I've tried searching for an answer to no avail.
P.S. -I'm 90% sure it's a partition issue of some sort, where the filesystem isn't being communicated with properly.

Categories

Resources