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.
Related
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.
I've been doing research on this for a while, and I decided to sign up and ask about this question. Majority of the topics here dealing with bricking either have solved it because of access to fastboot, or some users have given up and either retired their devices or sent them in to ASUS.
Long story short, I installed Clockwork Recovery Mod and Cyanogen mod with no issues. After a couple of weeks, I decided I wanted to go back to stock. I did some research and found a topic which said I needed TWRP in order to flash back the stock ROM. I installed TWRP, but some things seemed to have gone awry with that install and I no longer have access to the fastboot menu and the tablet keeps booting straight into recovery.
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2). So far, I think I can get it back on track if I could somehow install a new recovery, or start my device from scratch somehow.
Also whenever I transfer to device memory, if I reboot the tablet, everything gets erased and the log is littered with errors about not being able to find and mount /data. From what I've read, it should be solved with a simple format of the file system. However, all of my attempts to use the recovery's built in wiping/formatting tools have ended with no success. If I put in a microSD, that gets wiped as well so in order to load a ROM, I have to push it using adb.
I thought I had fully bricked it, but it seems that since it's accessible through adb, it's still somewhat fixable. I know about backing up everything with nvflash, now, I guess I just didn't do enough research before getting into this. Any ideas, feedback, is appreciated, so far I'm learning a lot about android devices from this experience.
lino4 said:
I can load new roms by pushing them with adb, but when I try to reload the stock mod it just reboots and nothing gets installed. I tried to sideload a rom, but my version of TWRP doesn't have that feature (I have 2.2).
Click to expand...
Click to collapse
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
_that said:
Where did you dig out this ancient TWRP version? It is not compatible with the current bootloaders and cannot access the internal storage at all - that's why all your installation attempts are failing.
Read this thread, it deals with a similar problem: http://forum.xda-developers.com/showthread.php?t=2291974
Click to expand...
Click to collapse
Yeah I found that thread not too long ago, I pushed the bootloader and was able to load the stock rom and get everything going.
I just went through the update to ne5 getting wifi calling and such, then rerooted since I lost it.
Everything was working fine, so I put in philz recovery since I lost that after the update also. I think it booted once after that, then now it is stuck on the spark screen when it boots.
Any way to go into Odin and change it, or reflash a stock rom of it? open to ideas since my new phone is pretty useless now, lol
Cowboyup65 said:
I just went through the update to ne5 getting wifi calling and such, then rerooted since I lost it.
Everything was working fine, so I put in philz recovery since I lost that after the update also. I think it booted once after that, then now it is stuck on the spark screen when it boots.
Any way to go into Odin and change it, or reflash a stock rom of it? open to ideas since my new phone is pretty useless now, lol
Click to expand...
Click to collapse
Ok, I fixed it through my engineering problem solving.
Since I could not boot the phone past the spark screen and I had only zip files to load on the phone, I had to pull my sd card, load it into my laptop, transfer a couple of file of stock roms http://cnexus.co/downloads/getdownload.php?file=SM-G900P/NE5/NE5_ROOTED_ODEXED.zip
this one being the one I used.
Then I was able to boot into Philz recovery, flash the zip file and get my phone back.
Of course the last couple weeks of tweaks and changes were gone and all the bloatware came back in a hurry, but I deleted it as expected.
Just updating this in case someone else runs into the same problem in the future.
Bummer Odin doesn't push .zip files, would have made it a little easier, but through mistakes and failure we learn and tonight I learned a few things about my phone, cool!.
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
CrimsonKatsuro said:
Here's a basic rundown of what happened. I completely rooted my Galaxy S III i535 on 4.4.2, and i installed SafeStrap (A Version of TWRP) since the Verizon S3 has a locked bootloader.
So here's what I tried to do. Using SafeStrap, I backed up my stock rom. And i selected another ROM slot. Using this, i tried experimenting by installing a ROM for another Carrier (They say not to do this, but i have in the past with success, so i thought it mightve worked)
(KEEP IN MIND, THE STOCK OS WAS STILL INSTALLED AND I EVEN HAD A BACKUP)
So, it didnt work and stopped halfway. I rebooted the phone, and Hard bricked.
Doesnt boot up, does not turn on, will not boot recovery or download, or any sign of some boot at all.
And, i get the qhsusb_dload sign on my pc.
Can anyone point me in the right direction, or at least tell me the cause of this problem? Thanks.
Click to expand...
Click to collapse
The solution may be a debrick image. They are designed to boot the phone from an external sdcard and from there reinstall the stock rom/firmware. I haven't searched yet, but check the general and development threads, possibly the stickied summary thread.
Check this thread
Yo, I've been trying to fix the damned phone for ages now. I accidentally wiped it by being a dumb idiot. Now I'm trying to fix the situtaton. So, I've tried installing a stock firmware and just flashing it with Odin. After trying this with like three different Firmwares, and sequential failures, I moved on to trying to flash it with a custom rom using adb, as the s6 doesn't have a removable sd. So I tried this, It said it worked. I used an installer and everything. But after I reboot, it still says there's no os and I cant find the zip anywhere on my phone to install. I'm not sure what to do. I'm a noob with this hence why my phone is in this state. Help MUCH obliged, S6 edge Sprint
http://forum.xda-developers.com/showthread.php?t=3219484