Develop Bugs

SOLVED - "Can't falsh zip file"

I just wanted to throw this out there in the event someone else experiences what I did. I searched the forums and didn't find much out there.
I was trying to flash a new ROM with 3.0 kernal. I went through the routine. Backed up current (reloaded 1.1) ROM. Wiped Factory Rest|Cache|Dalvic Cache and System. When I tried to flash the new ROM I received a message E: cannot open zip file. The KF was stuck/frozen in TWRP so I did a hard shutdown and booted back into recovery. Tried to install the zip again and the same message appeared. Rebooted to recovery again and then mounted USB and put on a few other zip's I had. Each returning the same message that the zip couldn't be opened. I knew I couldn't have had bum downloads of all these ROM's. I restored to my Reloaded 1.1 and rebooted into recovery and this time I wiped everything but System. Installed new ROM without error.
I'm not sure what happened here but it appears that it didn't like when I wiped System. Hope this helps anyone who may find themselves in a similar situation.

Won't boot, can't mount sdcard

Hello,
First of all, I feel like an idiot right now, and I most probably am. I'm using a HTC One X from ROGERS. Here's the whole story:
1) I unlocked the bootloader succesfully
2) I rooted my phone via a superboot script or something like that
Note: At this point the phone was working perfectly and I stayed that way for 3-4 days.
3) I finally found a working CWM recovery image for the One X from Rogers
4) I flashed it and was able to enter CWM Recovery
5) Following the thread on Android Revolution that's around on these forum, I downloaded something called Super Wipe and the ROM itself
6) When trying to "install" Super Wipe from within CWM Recovery, it kept giving me an error with Status 0
7) Got tired trying stuff so I did Wiped data/cache/Delvin (however it is spelled) cache/battery stats/everything I could wipe
8) Tried again, still didn't work
9) This time -and here is where I think I massively screwed up- I decided I'd try the format options, so I formatted cache, data, sdcard and system.
10) At this point I noticed the phone wouldn't boot anymore, I'd just get the "This build is for development purposes blah blah blah" and it would loop on that forever
11) Going back into CWM recovery, I now noticed that the sdcard was unmounted, when I tried remounting it, it would give me an error message saying E:Can't mount \sdcard (or was it "Error mounting \sdcard"? Not so sure anymore)
12) Tried re-locking and re-unlocking the boot loader, didn't work
So now here I am, phone won't boot, will just loop, and I can't mount the (internal?) sdcard anymore, actually I never really noticed if it was mountable, but I assume it was since I recall being able to complete the wipe everything operation in CWM recovery.
Is there anything I can do? I've heard of a few options, namely installing the RUU or something like that and a software called Odin which after searching a bit I believe is only for Samsung devices. The thing with the RUU is that I have a Rogers handset, and I don't think the RUU for that one is available. Also, is there any way I can access the internal sdcard on my PC while the phone is in the bootloader or CWM recovery? Maybe I'd be able to do something that way...
Also, I bought with the 3-years contract from Future Shop 5 days ago, think I can just go back and say "Hey, the phone crapped up" and expect them to change it without inspecting it too much to notice the **Tampered** **Unlocked** tags in my bootloader?

[q] os deleted, odin won't add file, brick

Here's what I did and where I'm at please help if you can? **MOVED TO CORRECT FORUM **
Originally I tried to root but it didn't root. In fact my phone started to have issues right after my attempt to root.
PHONE: Tmobile Samsung galaxy S2 SGHT989 loaded w Jelly Bean 4.1.2
WHAT I DID: I followed this guide to root my phone (it didn’t work/root, even though the Recovery message said it rooted)
**I'm sorry for referencing another forum..I just googled a how to**
downloaded extracted: ODIN 1.85
downloaded: TWRP (touch recovery 2.5.0)
downloaded to pc then put on SD card: Superuser – CWM_ROOT_SUPERUSER_3.1.3_BUSYBOX
*THEN I FOLLOWED THE REST OF THE GUIDE ON HOW TO ROOT..very meticulously (the guide shows CWM recovery but I used TWRP recovery).
From TWRP I selected and ran the zipfile for Superuser (the CWM***BUSY BOX file).
I got the message that said that I was rooted.
I rebooted the phone and downloaded the Titanium Backup app because it requires root. I got the message from Titanium Backup app that said I wasn’t rooted.
The guide says that if it’s not rooted then to go back to recovery/TWRP and flash Superuser again. I did and it STILL didn’t work.
I tried reloading the cwm recovery as well (both CLOCKWORD MOD RECOVERY I thought maybe this was the issue “nope” and then back to TWRP because it’s easier to use).
After this it started doing the endless “BOOTLOOP”. I had to take out the battery to stop it.
I tried going into MASTER RESET from boot “volume down, power, home key” it didn’t work..still BOOTLOOP.
So I rebooted into recovery/TWRP to wipe thinking that this might fix it. I wiped out everything including the OS (I got a message when I was about to reboot that said “you don’t have an OS, do you want to proceed reboot?”.
In my attempt to unbrick my phone I tried to go through Kies but it didn't recognize my phone (I checked the model & serial number 4-5 times).
So I downloaded the stock ROM through samsung updates so I could flash the ROM with ODIN. I started made sure auto reboot f.reset time was checked, clicked PDA, browsed to the file, highlighted the file and when I clicked "open" to add the file it doesn't show the path in PDA section as it usually does. So ODIN won't let me flash the stock ROM.
I don't think the file's corrupted because I downloaded the stock ROM from 2 sites multiple times, I tried switching USB ports, switched USB cables, rebooted PC, restarted odin. I can't get it to recognize the file.
I'm at my wits end so if anybody can assist I'd be very grateful.
Thank you for your time and help

raymondhs said:
Here's what I did and where I'm at please help if you can? **MOVED TO CORRECT FORUM **
Originally I tried to root but it didn't root. In fact my phone started to have issues right after my attempt to root.
PHONE: Tmobile Samsung galaxy S2 SGHT989 loaded w Jelly Bean 4.1.2
WHAT I DID: I followed this guide to root my phone (it didn’t work/root, even though the Recovery message said it rooted)
**I'm sorry for referencing another forum..I just googled a how to**
downloaded extracted: ODIN 1.85
downloaded: TWRP (touch recovery 2.5.0)
downloaded to pc then put on SD card: Superuser – CWM_ROOT_SUPERUSER_3.1.3_BUSYBOX
*THEN I FOLLOWED THE REST OF THE GUIDE ON HOW TO ROOT..very meticulously (the guide shows CWM recovery but I used TWRP recovery).
From TWRP I selected and ran the zipfile for Superuser (the CWM***BUSY BOX file).
I got the message that said that I was rooted.
I rebooted the phone and downloaded the Titanium Backup app because it requires root. I got the message from Titanium Backup app that said I wasn’t rooted.
The guide says that if it’s not rooted then to go back to recovery/TWRP and flash Superuser again. I did and it STILL didn’t work.
I tried reloading the cwm recovery as well (both CLOCKWORD MOD RECOVERY I thought maybe this was the issue “nope” and then back to TWRP because it’s easier to use).
After this it started doing the endless “BOOTLOOP”. I had to take out the battery to stop it.
I tried going into MASTER RESET from boot “volume down, power, home key” it didn’t work..still BOOTLOOP.
So I rebooted into recovery/TWRP to wipe thinking that this might fix it. I wiped out everything including the OS (I got a message when I was about to reboot that said “you don’t have an OS, do you want to proceed reboot?”.
In my attempt to unbrick my phone I tried to go through Kies but it didn't recognize my phone (I checked the model & serial number 4-5 times).
So I downloaded the stock ROM through samsung updates so I could flash the ROM with ODIN. I started made sure auto reboot f.reset time was checked, clicked PDA, browsed to the file, highlighted the file and when I clicked "open" to add the file it doesn't show the path in PDA section as it usually does. So ODIN won't let me flash the stock ROM.
I don't think the file's corrupted because I downloaded the stock ROM from 2 sites multiple times, I tried switching USB ports, switched USB cables, rebooted PC, restarted odin. I can't get it to recognize the file.
I'm at my wits end so if anybody can assist I'd be very grateful.
Thank you for your time and help
Click to expand...
Click to collapse
https://www.dropbox.com/s/vxapb57yeuk60ud/T989UVMC6_T989TMBMC6_TMB.zip
try unzipping this file- place .tar file on desktop
when your connected ond open odin, click pda , search desktop and add .tar file -hope this helps

Ok..so that I don't mess this up.
after I download this to desk top should I not open the zip file? Just open up ODIN select PDA then browse to the file location?
I'm screwing something up here...

raymondhs said:
Ok..so that I don't mess this up.
after I download this to desk top should I not open the zip file? Just open up ODIN select PDA then browse to the file location?
I'm screwing something up here...
Click to expand...
Click to collapse
did you get pm

Hallelujah!
UNBRICKED :victory: Up and running...phew!!
Thanks Fasted12! If you were here I would hug ya and make you feel uncomfortable. Stay awesome :good:

Galaxy Note 8 (GT-N5110) PC Connection Problems - Boot Loop - SOLVED by ME

NO ONE?????
ODIN --> Flash Stock Recovery (AP) with NAND Erase All Option Checked (because it seemed to make sense) + Auto Reboot + F. Time Reset --> Reboots to Stock Recovery (did not work before) --> Reboot into Recovery --> Wipe Data/Cache and Dalvik just to be safe (this crashed it before) --> Reboot. THE END
TL/DR: I am currently stuck on recovery/update mode. Any attempt to wipe data or clear dalvik crashes it. any attempt to access data through TWRP crashes it. Flashing stock rom or custom rom does not help. Somethings wrong with /data? It thinks it has root from the CF Auto Root, but does not really? Something wrong with partitions? Should I wipe the nand with ODIN 3.10? Repartition? ugh ... Please help ...
I have searched the forums and found nothing that describes this issue precisely. I have also tried to apply various suggestions to repair, which, for the most part seems to have made it worse. I am hoping that people still look at this forum.
PC - Windows 7
Initially @4.2.2 ---> Touchwiz debloated stock ROM which I rooted. It worked for a couple years, but the device crashed frequently. I do not recall much about the installation, but believe that I used CWM/TWRP at the time. After installing the ROM, I ran triangle away (out of the box, it had 4.1.2, i recall)
I decided to upgrade to the most recent stock ROM (4.4.2). In order to do so, I used an easy installer I found else where on XDA. (http://forum.xda-developers.com/showthread.php?t=2773712 ---ODIN One Click exe). The device was not initially recognized, so I reinstalled the official driver package (said that they already existed, but I installed again anyway). Ran 1-click and it appeared to work.
Initially, the device booted (long startup) and seemed to function. It also preserved all data and programs (presumably did not touch the internal memory - 16 GB) and possibly root /data.
I then tried to root through most recent ODIN with CF auto root. This appeared to work and rebooted (again, showing the updating android apps screen before fully booting).
The only thing that i could find that had changed was the wallpaper (showed on lock screen but not on home screen). I could no longer find the image, so tried to go to /data/data to find it with root explorer equivalent. This is where it started to act weird.
NOTE: I did not clear anything (system cache, etc. at any point)<--a lie (see below)
It showed the root folder fine, but when I clicked on /data it took a while and could not access it. It either rebooted itself or I rebooted, but this time it was stuck in a boot logo loop. I entered download mode and flashed TWRP through ODIN. I set it to not reboot automatically so that the bootloader was not overwritten automatically (thus losing recovery). TWRP came up. The computer recognized it as a Media Device after I mounted USB storage. Just in case, I copied all of the important files from the internal SD Card to my computer. I then tried to go to the file explorer to copy the wall paper and it forced a reboot. At this point it was stuck on a logo screen boot loop again. I was able to enter Download mode and reflash TWRP. This allowed me to enter recovery again, however, now it would only boot directly into recovery (or Download mode if I did the button combo). The interesting thing was that it would reboot two or three times before successfully entering TWRP.
I believe I tried to reflash the stock ROM at this point, which might have worked but made no difference.
I was also having a lot of problems getting Windows to properly recognize the device. I had to reinstall the drivers a couple times. I tried Kies after the problems started and it tried to connect by failed. The diagnose connection did not work either. I was not able to get Kies to connect though I tried several times throughout the attempted repair
I downloaded a stock-rooted 4.4.2 ROM from here and tried to flash it. It failed.
I also tried to flash via Heimdall, but initially could not find any stock ROMs for Heimdall for the Galaxy 8. (The driver utility that is included helped to get the phone recognized by Windows sporadically).
I decided to switch over to CWM touch recovery, which I flashed via ODIN (I was having issues with TWRP again and also could not get windows to recognize the device as a media device when I mounted USB storage). This worked after a couple tries and I was able to enter CWM. I attempted to flash the stock ROM but it failed. Either at that point or when I tried to mount data it returned an error that device did not have root. Again, it would only boot into CWM (on its own) or Download mode (with key combo). At some point around here I cleared the cache and dalvik (error) after it returned an error saying insufficient space when trying to flash ROM.
I dissected the .exe from the autoflash used in the beginning (stock unrooted 4.4.2) and used the contents (system.img, cache.img, hidden.img, tz.img, recovery.img and one other I do not remember) in Heimdall to create a Heimdall package. At this point I figured out I did not need to create the package, but just specify the individual files. I flashed. It appeared to complete System.img successfully and then failed. Tried again with the same result.
Now when I rebooted, it would enter download mode with the Key combo, but otherwise it booted instantly to an error screen to the effect that a firmware installation had failed and to use the repair function in Kies to fix. Kies still did not recognize it.
At this point, I figured I should stop. Currently I can get to the download screen or the error screen. The computer recognizes it but intermittently fails to install driver. Zadig.exe sees it as Gadget Serial. Sometimes Windows just sees it as SAMSUNG_Android, in which case drivers fail. Once or twice I got it to recognize it as Samsung USB Composite Device, but Kies would still not work.
That's all i have for now. If more information is needed, let me know and I will update the post when I get home from work tonight (this is from memory).
Thank you
UPDATE: last night I went home and was able to get it back to the point where I could flash TWRP or CWM recovery. If I try to flash Stock Recovery, it fails. A minor problem is that I cannot turn it off - it just turns it self on again, so the battery keeps running down.

Phone won't boot, can't flash new ROM but can get into recovery

This all started when I opened my Pokémon Go app and got "Failed to extract resources needed by Il2CPP". I tried to go into Settings and clear some App data, but I kept getting "com.xxx has stopped working" no matter what I tapped, so I just shut down the phone and try to restart but... it wouldn't go past the boot page. I went into recovery mode to try and clear Dalvik/cache, but the error said "unable to make cache/recovery". When I tried to reboot the phone from inside TWRP, it would freeze.
So I tried to go into recovery again, wiped dalvic/cache/data and that seemed to succeed. I tried to flash Fulmics via OTG but during installation, it says "set_metadata_recursive: some change failed", or sometimes it wouldn't even get to the Fulmics installation and just say "unable to map OTG file" or something like that. Tried to copy the file from the USB drive to the phone to flash directly from the phone, but that kept failing with "process has ended" and nothing copied over. I can't flash from an external SD card cause the SD slot is broken (when the phone was booted up, the SD card kept mounting and unmounting).
Is there any way to fix this? A setting in TWRP or something I need to change? Another file I can flash to fix these errors? Or do I have to try and go back to stock? Is it even possible to go back to stock at this point?