I cannot flash ANYTHING. I mean, Nada, zip, zero.
The stock Rom gives me a assert failed error, twrp says that all the zip files are bad, even though I downloaded them with my phones browser.
I'm stuck, and I don't know what to do
Sent from my SGHI927 using Tapatalk
Related
I'm really not a noob to flashing ROMs, in fact, I got pretty good at it with my Evo before I upgraded to the Galaxy 2.
So I got the phone rooted using Odin, now I need to install Clockworkmod recovery so I can flash some custom ROM's. Everytime I install clockworkmod using Odin, when my phone reboots, I can't get service, and the buttons on the bottom aren't working. The search button now turns into the menu key.
So how can I get this working right? Do I need clockworkmod to be able to install custom ROM's? Is there another way to install clockworkmod aside from using Odin? Because Odin just isn't working.
Any help is appreciated.
Why dont you get it off the market?
Sent from my SPH-D710 using XDA App
I'm using ROM Manager now.
Now I keep getting:
"E: failed to verify whole-file signature"
and: "E:signature verification failed"
This comes up every time I try to use ROM Manager to backup/flash a new ROM.
What method of root did you use?
The one in this thread; from the video:
http://forum.xda-developers.com/showthread.php?t=1265429
saj1jr said:
I'm using ROM Manager now.
Now I keep getting:
"E: failed to verify whole-file signature"
and: "E:signature verification failed"
This comes up every time I try to use ROM Manager to backup/flash a new ROM.
Click to expand...
Click to collapse
my phone is the same way, using the app, or booting into CWM it wont let me back up. I just flash the rom anyway... whatever. Not the best method, but ive installed plenty of roms and never had a problem. It would be nice to find out why though.
yeah, the problem is it isn't flashing. It just gives me that error which eventually forces me to reboot.
rom manager doesnt support this phone yet u have to odin eb30 with clockworkmod 4.0 which supports back up and restore .
So, I'm pretty sure I bricked my phone. Any help turning this around would help greatly. Here's how I got here. Plan was to Flash CyanogenMod 10. I rooted with no problems. Installed clockwork Mod on my phone. Created a backup of the stock Rom through ClockWork. Then backed up data to my removable SD card. I moved the CM-10 zip to the phone. Launched into recovery. Ran zip and it completed. On first boot got stuck on the CyanogenMod splash screen. After toying around with it (I believe clearing data in recovery). I finally got it to boot and went to install the Google apps zip the same way. That's when the real trouble started, now I can only get it to show the Samsung boot screen and then a blank screen.
I have attempted several How-to unbrick threads. However, the same thing happens to each one. I'll get them to work through Odin, but the phone will restart and go back to the same screen.
Thank you in advance for any help!
Just factory reset/wipe cache and dalvik and flash cm10 again, if I understand correctly you did not follow those steps when you flashed first time and those steps are necessary to be stable.
Sent from my SGH-I747 using Tapatalk 2
Krazex2005 said:
Just factory reset/wipe cache and dalvik and flash cm10 again, if I understand correctly you did not follow those steps when you flashed first time and those steps are necessary to be stable.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Did all that and attempted to run the CM zip in recovery can up with an error and stopped installation. Error is right after Installing update it say,
"asset failed: get prop("ro.product.device") == "d2att"
E: Error in /sdcard/CyanogenMod 10/cm-10-20121012-NIGHTLY-d2att.zip
(Status 7)
Installation aborted."
I've been trying to move a new copy the CyanogenMod to the phone but I can't because it won't connect to the computer now. I can get it to download mode but don't know what to use. I attempted to use a stock file but the phone just reboots into black screen.
Thank you.
If you can get to download mode just use Odin to flash your stock rom
Sent from my SGH-I747 using xda app-developers app
What recovery are you using?
Sent from my SGH-I747 using xda premium
Soup7892 said:
Did all that and attempted to run the CM zip in recovery can up with an error and stopped installation. Error is right after Installing update it say,
"asset failed: get prop("ro.product.device") == "d2att"
E: Error in /sdcard/CyanogenMod 10/cm-10-20121012-NIGHTLY-d2att.zip
(Status 7)
Installation aborted."
I've been trying to move a new copy the CyanogenMod to the phone but I can't because it won't connect to the computer now. I can get it to download mode but don't know what to use. I attempted to use a stock file but the phone just reboots into black screen.
Thank you.
Click to expand...
Click to collapse
When I first tried flashing CM9/10 on my phone I got the same error. Weird thing is I didn't do anything special to fix it... I just went through a couple Touchwiz roms then a couple weeks later I tried a couple different AOSP ROM's and all of a sudden CM10 works now :s
Try a factory reset through recovery and see if you can flash any other ROMs or something.
did u try restoring your backup that you made?
Sent from my PC36100 using xda app-developers app
Have you tried using kies? I was able to repair a bootloop with kies. I was able to get into download mode and then had kies to what i believe was referred to as initiating the firmware. solved.
Hi,
I tried to downgrade my Telus SGS3 to 4.1.1 but Odin failed at 75% and now my device is bricked. I can get to download mode easily. I tried Kies, but could never connect to the device even though I have all drivers installed correctly. I tried to reflash 4.2.2 but also failed the same way. I then tried to flash Cyanogen using CWM. I first tried to flash CWM using heimdall but also failed (error claiming interface failed). I then converted the recovery.img to .tar.md5 (7zip to tar and md5sum to md5) and flashed using Odin which went fine and was able to boot into CWM. I put both the ROM and gapps on the SDCARD and flashed from CWM but I got an error stating that (cwm failed to verify whole-file signature). I even tried to flash using adb sideload which seamed to finish 100% but when rebooting it returned the same signature error.
Please any advice. What bothers me is that I have done this many times before and never went into any issue. If I could at least make Kies connect to recover the damn thing.
PS: my GS3 is SGH-i747M and I downloaded the ROMs from sammobile and update-samsung
Thanks
SOLVED ...
I do not get it! I used a Samsung Galaxy Nexus cable and "voila" it worked from the first time!
goldfinsh said:
Hi,
I tried to downgrade my Telus SGS3 to 4.1.1 but Odin failed at 75% and now my device is bricked. I can get to download mode easily. I tried Kies, but could never connect to the device even though I have all drivers installed correctly. I tried to reflash 4.2.2 but also failed the same way. I then tried to flash Cyanogen using CWM. I first tried to flash CWM using heimdall but also failed (error claiming interface failed). I then converted the recovery.img to .tar.md5 (7zip to tar and md5sum to md5) and flashed using Odin which went fine and was able to boot into CWM. I put both the ROM and gapps on the SDCARD and flashed from CWM but I got an error stating that (cwm failed to verify whole-file signature). I even tried to flash using adb sideload which seamed to finish 100% but when rebooting it returned the same signature error.
Please any advice. What bothers me is that I have done this many times before and never went into any issue. If I could at least make Kies connect to recover the damn thing.
PS: my GS3 is SGH-i747M and I downloaded the ROMs from sammobile and update-samsung
Thanks
Click to expand...
Click to collapse
BTW, when I flashed CWM, the menu I got is:
reboot system now
apply update from ADB
apply update from sd card
wife data/factory setting
wipe cache partition
and there is no "Install zip from sd card"!!!
:crying::crying::crying: Please help...
I just flash back to stock rom N7100ZSDME1
When it finish, reboot, S-Note keep force close, the phone is completely unusable, the S-Note force close comes up every second.
I already did full wipe (data, cache, dalvik), even format the internal SD card, but still no luck to fix.
Grateful if someone could help.
Turn out see some error message after flash stock rom, when the phone reboot after flash complate, it enter 3e recovery, then apply a sec_csc.zip update. But it fail:
E:signature verification failed
I tried extract the sec_csc.zip file then use CWM recovery to install, but SNote still keep force close after installed.
So now I can't get back to stock rom :crying::crying::crying:
Still looking for solution...
Thank you.
Use tar file and flash using odin on pc
Sent from my GT-N5100 using Tapatalk 2
Thanks for your reply.
Which tar file should I flash?
I already use the tar file download from samfirmware to flash using odin on PC.
It result 3e recovery cannot apply the sec_csc.zip then SNote keep force close after reboot.
Sent from my GT-N7100 using xda app-developers app
Flashing over CWM will help
I think Flashing the S-Note app over CWM will help to restore it.
Hey everyone,
My nexus 7 is bricked. I have tried everything now. I am trying to just unlock the bootloader now. I get this screen. It just gets stuck here. I have tried different cables, different usb ports, different computers. but maybe i should try another computer with different drivers? Not sure what to do...
wolverineclaws said:
Hey everyone,
My nexus 7 is bricked. I have tried everything now. I am trying to just unlock the bootloader now. I get this screen. It just gets stuck here. I have tried different cables, different usb ports, different computers. but maybe i should try another computer with different drivers? Not sure what to do...
Click to expand...
Click to collapse
Oh, in TWRP it says I have no OS installed and it says I have 0 mb. it just boots to google logo and does nothing.
Try this method, http://forum.xda-developers.com/showthread.php?t=2389107
Sent from my Nexus 7 2013 using Tapatalk
wolverineclaws said:
Oh, in TWRP it says I have no OS installed and it says I have 0 mb. it just boots to google logo and does nothing.
Click to expand...
Click to collapse
Can you use fastboot to flash the stock recovery? If you can, do it, and run a factory reset and cache wipe.
Aerowinder said:
Can you use fastboot to flash the stock recovery? If you can, do it, and run a factory reset and cache wipe.
Click to expand...
Click to collapse
The boot loader is locked and doesn't want to unlock. It just hangs at 'erasing userdata'.
Sent from my Nexus 5 using XDA Premium 4 mobile app
wolverineclaws said:
The boot loader is locked and doesn't want to unlock. It just hangs at 'erasing userdata'.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you still boot into TWRP after all you've tried? You could get a zip of stock recovery, flash it with TWRP, and factory reset that way. If you can't find a zip, I can make one for you.
Aerowinder said:
Can you still boot into TWRP after all you've tried? You could get a zip of stock recovery, flash it with TWRP, and factory reset that way. If you can't find a zip, I can make one for you.
Click to expand...
Click to collapse
I can still bit to twrp recovery. I couldn't find a zip recovery. I have the stock image unzipped. Can you tell me how, or possibly make it for me? Is it as simple as just zipping the recovery.img file?
Sent from my Nexus 5 using XDA Premium 4 mobile app
wolverineclaws said:
I can still bit to twrp recovery. I couldn't find a zip recovery. I have the stock image unzipped. Can you tell me how, or possibly make it for me? Is it as simple as just zipping the recovery.img file?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, but you need a little scripting also. This should work for you: https://db.tt/CVJoj5wY
Flash in TWRP, then use TWRP to reboot recovery.
Aerowinder said:
Yes, but you need a little scripting also. This should work for you: https://db.tt/CVJoj5wY
Flash in TWRP, then use TWRP to reboot recovery.
Click to expand...
Click to collapse
Thanks for all your help Aerowinder. Unfortunitely this is what it says. Well, it says successful with this in the log
Updating partition details
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
E: Unable to mount ' /cache'
E: Unable to set emmc bootloader message.
E: Unable to mount ' /cache'
installing ....
checking for MD5 file...
skipping MD5 check...
Flashing Stock K)T49H Recovery...
Updating partition details...
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
Then I reboot it back into recovery and it goes back to TWRP recovery...
wolverineclaws said:
Thanks for all your help Aerowinder. Unfortunitely this is what it says. Well, it says successful with this in the log
Updating partition details
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
E: Unable to mount ' /cache'
E: Unable to set emmc bootloader message.
E: Unable to mount ' /cache'
installing ....
checking for MD5 file...
skipping MD5 check...
Flashing Stock K)T49H Recovery...
Updating partition details...
E: Unable to mount ' /system'
E: Unable to mount ' /cache'
Then I reboot it back into recovery and it goes back to TWRP recovery...
Click to expand...
Click to collapse
I'll be 100% honest with you, the first thing I did with both my N5 and N7 was unlock the bootloader. But, can you use fastboot to flash a stock factory image zip (link in my signature)?
If not, will it allow fastboot erase cache?
What version of TWRP are you using, and why is your bootloader locked with TWRP installed? Did you relock it?
Aerowinder said:
I'll be 100% honest with you, the first thing I did with both my N5 and N7 was unlock the bootloader. But, can you use fastboot to flash a stock factory image zip (link in my signature)?
If not, will it allow fastboot erase cache?
What version of TWRP are you using, and why is your bootloader locked with TWRP installed? Did you relock it?
Click to expand...
Click to collapse
I'm using TWRP 2.6.3.1.
I can kind of flash the stock image back. I don't think it really works though. I checked the driver under device manager. It says it is for a nexus 4.. I downloaded and installed the google driver from their site. Is there a different one I should be using?
I did relock the bootloader. I thought I had flashed back the google stock image just fine, but apparantly not. What happened was randomly yesterday the tablet was stuck at the google boot screen. I went in to recovery and it said there was no OS installed. So I figured the best thing to do was the return it to stock. It is weird because it just hangs at certain commands. Like fastboot oem unlock or fastboot format etc.... Could it be a driver thing? The tablet responds to other commands though. :/
wolverineclaws said:
I'm using TWRP 2.6.3.1.
I can kind of flash the stock image back. I don't think it really works though. I checked the driver under device manager. It says it is for a nexus 4.. I downloaded and installed the google driver from their site. Is there a different one I should be using?
I did relock the bootloader. I thought I had flashed back the google stock image just fine, but apparantly not. What happened was randomly yesterday the tablet was stuck at the google boot screen. I went in to recovery and it said there was no OS installed. So I figured the best thing to do was the return it to stock. It is weird because it just hangs at certain commands. Like fastboot oem unlock or fastboot format etc.... Could it be a driver thing? The tablet responds to other commands though. :/
Click to expand...
Click to collapse
You can try to uninstall the drivers (also tick the box in the dialog that pops up). Scan for new hardware, and keep deleting drivers until you can't anymore. Then grab the latest ones from my signature, if you didn't have them already. Mine shows up as Android Bootloader Interface. Also, make sure you're using USB 2.0 ports.
Aerowinder said:
You can try to uninstall the drivers (also tick the box in the dialog that pops up). Scan for new hardware, and keep deleting drivers until you can't anymore. Then grab the latest ones from my signature, if you didn't have them already. Mine shows up as Android Bootloader Interface. Also, make sure you're using USB 2.0 ports.
Click to expand...
Click to collapse
yeah, I tried that. I feel like I have tried everything... I'm sure if I didn't relock the bootloader things would be different. Well, I'm going to see if JTag could be able to repair it. for 50 bucks it would be worth it. Thanks for all your help though!