Hi. I have been trying to find an solution to my problem for 3 days. I have looked all over here and the rest of the internet. I believe what I need is an update zip file that will pass the standard e3 recovery.
I have downloaded several zips already(a couple from here), that say they are the stock samsung firmwares, but everytime I put it on an sd, then try to apply the update with it, in the e3 recovey I get E: signature verification failed.
I got to this point by trying to apply the OTA update. ( ok, you can all throw rotten food at me now). I thought I was safe as I didn't have any custom firmware on there. I had, however gained root access. The update went fine and seemed to work, then it finished and tried to reboot, only to get stuck on the samsung logo for over an hour before I decided it had gone wrong and panicked.
The usual ways of fixing I know about are odin, heimdall, adb. None of these are working. I think it's my computer being too old. Odin doesn't detect, Heimdall sees there is a device there but has problems connecting to it. adb will only see it in the e3 recovery mode and not in odin mode and even then because it doesn't seem to be root anymore it can't really do much.
I am open to suggestions on how to get something to work. My thoughts are that I just need a gingerbread rom that has some samsung siigning on that I can put on an sd and use that in E3 to flash from there. I can then work from there if that works. Feel free to laugh and point and tell me that's not gonna work, but if you know a way that will work I would be very grateful.
Thank you for listening and I hope someone can help.
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks for getting back so soon. I have had kies up on the screen actually. It's been trying to connect for about 3 hours now lol.
I did the troubleshoot thing earlier where it reinstalled drivers. Restarted pc but same. Won't actually connect in either odin mode or recovery.I'm pretty sure it's a pc issue, at least partly anyway, but don't have anything else to try it on.
Is the signed zip idea a definite no go?
Not sure about zip,
Close Kies, open pc odin,
Gp into download mode, connect phone, confirm downloadmode with volume up and try tp flash
Let me know how that goes
Sent from my GT-N7000 using Tapatalk 2
No Odin pc refuses to recognise there is anything attached. I'mgiving up for the night now anyway. thank you for looking in. I'll try again in the morning. I might have to buy a new pc before I can get this thing to work.
Connect the usb to back port, sometimes helps with connection. Use stock usb cable.
please hit thanks if i helped
thanks but I've tried all the basics, but if it would help I'd stick a wire up my nose, so it's all helpful. It could be something simple I just forgot.
PC specs? Is it a Mac maybe? Reboot phone and PC and use another cable. Download latest kies and update it restart PC and then connect the phone.
Sent from my GT-N7000 using Tapatalk 2
Umm, did you wipe after the flash?
1. A data wipe will, in all probability, solve the bootloop after the upgrade from GB to ICS.
2. A data wipe on an ICS kernel CAN result in a hardbrick, as I'm sure you must have noticed, on the forums.
I'd say wipe it. The bricks are not all that common. Just this once. I faced a similar situation, and I KNEW the thing would boot after a wipe, so I just crossed my fingers and did it. All went well.
By they way, what do you mean by e3 recovery? I've been assuming stock.
Sent from my GT-N7000 using xda premium
the PC is a 7-8 year old laptop. Our desktop died a few months ago and we've not really had the spare cash to replace it yet. The desktop was even older and was a real pain. The technical gremlins have really infested my house.
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else. (yes I'm looking dumber with every post). My next thing to try I guess is see if I can borrow my sister in laws PC for a few hours or something. That is if if cannot find a rom that the recovery will accept to put on my sd.
yes -the e3 recovery s the stock one.
Feel for ya.... if you can enter stock recovery then the connection problem most likely lies either with the cable and port or drivers being out of date
Sent from my GT-N7000 using xda premium
almost positive it's my knackered computer that won't let me do anything. Still can't believe that a rom doesn't exist with samsung signing, somewhere in the world. What is the point of having a standard recovery at all if you can't use it to recover stuff?
I need to be borrow or steal the use of someones computer now I think. I'll keep an eye on this thread incase someone knows of a signed zip file, and I will report of any news incase someone else has the same problems and wants to fix it without sending to Samsung so they can keep their data.
kyllerbuzcut said:
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else.
Click to expand...
Click to collapse
I understand the reluctance.
Although, the pictures would survive the wipe, as they would be in /sdcard/DCIM/Camera. A wipe wouldn't affect anything in /sdcard, although, you'd lose your contacts if they aren't backed up. Your best bet would be to borrow someone's computer for a while.
thanks for all the advice.
Finally found a zip that the e3 recovery thinks is signed.
It was the 2.3.6 gingerbread, uk cpw one.
It seems to pass the signing check and then it looks like it's doing domething for a few minutes, then nothing seems to happen afterwards. just stays in recovery. If I do it a few times in a row it will sometimes think for longer, then reboot itself like it has all worked, but then get stuck at the samsung logo again.
Can I ask, what exactly is getting wiped then? Just the main android folders and not the sdcard folder? Is that for definite?
Yes. Just the android partition should get wiped, internal SD should remain intact.
Try taking out the battery for five minutes or so before powering on again. Sometimes after flashing the rom needs a breather to "settle".
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Just an update on my situation. I finally managed to get use of another computer and got it to work properly, so managed to flash the stock ICS rom through odin.
Thanks a lot Samsung for forcing me to put the yellow triangle on my device. At least there are people willing to help with fixing mobile phones' software, even if the manufacturers themselves don't care about you losing all your data. I managed to get everything back. Nothing was lost. If only they allowed you to flash the stock rom from their stock recovery. It's ridiculous that it doesn't.
Anyway there is the triangle away app for that I suppose and now I might try some new roms out to see which I prefer.
Yeah you would have to make a flashable zip. Not sure how to do that.
Good you are back
Sent from my GT-N7000 using Tapatalk 2
Related
I've been searching, and reading, and my eyes hurt. I normally don't like to post threads, but I'm left with no choice. If this topic has been covered, then I guess my searchin' skillz are stating to lack. Here is my delimna:
Rooted, Lagfix, enabled Side-loading, recently installed ClockworkMod, stock firmware. I ran a backup using ROM Manager/ClockworkMod. I was attempting to install the Mobile AP fix for WiFi Hotspotting from designgears. I downloaded the new kernel per instructions (Mobile AP ony). I first tried installing it using ROM Manager's boot option into Clockwork without renaming MobileAP.zip. Still received black screen when I open the Mobile AP settings that the new kernel was trying to fix. So I thought that the flash didn't work, so this time I renamed the kernel file to update.zip and did the standard method of flash using stock recovery mode.
Now the phone boots to the Galaxy S screen, then just a black screen. The bottom row buttons seem to be active, but nothing happens. Holding power....nothing. I have to pull the battery; however, I can boot into stock recovery.
Now here's the delimna. I can boot into recovery, but the update.zip file is NOT the one for ClockworkMod, its the modified kernel. Is there a way that I can browse the files on the phone so I can change the update.zip file? I want to put Clockwork's in place so I can restore using my backup made yesterday....It's not a huge order if I have to flashback to stock and lose everything as I usually do that everynow and again anyways (usually I'm prepared). I won't lose anything important that isn't already backed up except maybe some pictures....
BUT, I can't help but try. It's just me I like to break stuff and fix 'em. I want to try to run that backup I made. I have Odin, and I tried flashing the kernel back to stock (i had one hell of a time finding information on how to use it). As a matter of fact, I found instructions on HOW to use it, but I gave up trying to find useful information on how the program runs (like a user guide, what else can it do, that sort of thing....). I spent hours reading thread after thread........information overload I guess.
I figured someone might point me in the right direction. How can I browse/edit the contents of the phone while in Recovery or Download mode?
You could try letting the phone boot up, yes I know it's only a black screen, then plug in the usb to your PC and see if ADB works.
If so then just adb shell into it and work with command line.
I'm not sure if ADB would work in stock recovery mode but that's worth a shot too.
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
swedishcancerboi said:
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
Click to expand...
Click to collapse
Wasn't sure if that would work or not.
So, if you turn it on and just let it sit as long as a normal boot, then try adb does anything work?
I actually let it sit for ~15 minutes. computer doesn't even register the usb being plugged in. I'm going to give it another go or two, but in about an hour I'm going to have to call it quits and just flash it with Odin. Don't want to give up yet, but I am driving out of town later this afternoon and must have my phone for the trip. Maybe I'll break it again tomorrow and play with it over the weekend!
Let me know if you have any other ideas. I'll let you know when I give up.
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
swedishcancerboi said:
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
Click to expand...
Click to collapse
Hybrid from eugene is pretty fast especially if you add the voodoo kernel to it. Thats what I heard tho. Because when i tried it out it was pretty quick with out a lagfix and without autokiller. Only used it for 20 min tho as i couldn't get Titanium backup to work. I think the titanium problem is a hit or a miss.
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
swedishcancerboi said:
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
Click to expand...
Click to collapse
Well, if your going to do that take an extra 2 minutes and load Eugenes Hybrid R3 while your at it. It's extremely easy to do and in my opinion the fastest thing we can put on these phones right now.
Vibrant ROM? is that safe? I mean, I know they are all Galaxy S, but is the hardware really that identical?
I don't think eugenes captivate hybrid is actually a vibrant rom. I think he just borrowed some of the better parts.
Sent from my SAMSUNG-SGH-I897 using XDA App
Got it! I used the one click stock down loader to get the phone to boot. I then noticed that many of my files were still there, music, zips.....so I thought....maybe my backup is still there.
Instead of using my original root, I decided to try Unleash the Beast.applied it so I could load Rom Manager.i opened Rom manager and it showed my backup!
I tried restoring then without success (no update.zip) and had to flash clockwork (even though it showed it already loaded, guess it needed to be refreshed, makes sense since it is a fresh firmware), selected my restore and it ran like a charm.
I am just surprised. I thought the act of flashing the Rom would wipe everything. Apparently not if you never do the "master clear."
Thankfully I had just installed Rom Manager the day before and had a fresh backup. Looks liked I'm gonna have to start shelling out more beer money to the devs!
Now I can prepare to break it again and again. Let the fun begin!
Sent from my SAMSUNG-SGH-I897 using XDA App
Nice. Yeah, stuff you have stored on your "internal SD" is safe between flashes. Of course apps, contacts, etc get wiped, but that's an easy fix.
"the more you know," eh? Ha!
Sent from my SAMSUNG-SGH-I897 using XDA App
Recently, I had a very long discussion with some helpful users regarding how my market disappeared in the Android Themes section. After never recovering my stock market application, I finally just flashed to the cognition rom that is built for 2.1.
This was a huge risk for me because for some reason my phone is not found in Odin when it is in download mode. I have already tried everything to get it recognized, but nothing was able to get it recognized. If I were to brick my phone, I don't think I could fix it. I soft bricked it during the problem with the Market, but luckily I was able to get the phone working again through recovery.
I am thinking of flashing to the new cognition so that I can get my phone running on a 2.2 based rom and then quit flashing until I get a better phone or figure out my Odin problems.
I just have a few questions. I know a lot of people recommend flashing to stock first (which I can't do), while others don't flash stock. I should be able to just disable Voodoo and hopefully flash successfully to a new rom, correct? Also, what are the chances of a permanent brick? As long as I could get into recovery I could probably get the phone back up again without the use of Odin, right?
yentlequible said:
Recently, I had a very long discussion with some helpful users regarding how my market disappeared in the Android Themes section. After never recovering my stock market application, I finally just flashed to the cognition rom that is built for 2.1.
This was a huge risk for me because for some reason my phone is not found in Odin when it is in download mode. I have already tried everything to get it recognized, but nothing was able to get it recognized. If I were to brick my phone, I don't think I could fix it. I soft bricked it during the problem with the Market, but luckily I was able to get the phone working again through recovery.
I am thinking of flashing to the new cognition so that I can get my phone running on a 2.2 based rom and then quit flashing until I get a better phone or figure out my Odin problems.
I just have a few questions. I know a lot of people recommend flashing to stock first (which I can't do), while others don't flash stock. I should be able to just disable Voodoo and hopefully flash successfully to a new rom, correct? Also, what are the chances of a permanent brick? As long as I could get into recovery I could probably get the phone back up again without the use of Odin, right?
Click to expand...
Click to collapse
<<< this might not be helpful, but I will tell you my situation... >>>
I have tried to Rom my JI6 (unoffical froyo) version of captivate, with Cog v2.3b8, using ROM manager.
But after installation, my screen went blank and the battery started to heat up...
After that I was lazy to fix it myself, so I went to exchange shop, and changed it...
- if your phone bricks (forever) try this : http://forum.xda-developers.com/showthread.php?t=775911
peurocs4 said:
<<< this might not be helpful, but I will tell you my situation... >>>
I have tried to Rom my JI6 (unoffical froyo) version of captivate, with Cog v2.3b8, using ROM manager.
But after installation, my screen went blank and the battery started to heat up...
After that I was lazy to fix it myself, so I went to exchange shop, and changed it...
- if your phone bricks (forever) try this : http://forum.xda-developers.com/showthread.php?t=775911
Click to expand...
Click to collapse
I tried that same method and it still did not show up in odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
yentlequible said:
I tried that same method and it still did not show up in odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Main problem with your Captivate is that you cannot connect to your PC???
Did you tried using different computer, or using different version of Windows/Mac?
<Sorry, if I'm not really helping you...>
peurocs4 said:
Main problem with your Captivate is that you cannot connect to your PC???
Did you tried using different computer, or using different version of Windows/Mac?
<Sorry, if I'm not really helping you...>
Click to expand...
Click to collapse
Back when I was really trying to figure the problem out (about 2 months ago), I was trying everything mentioned. I tried different versions of odin, 3 separate computers, windows xp/vista/7, front and back usb ports, multiple drivers, etc... The weird thing is that the phone is recognized in odin when it is on, which is how I was able to do a master clear on it. It is just when it is in download mode that it does not recognize it.
I eventually just gave up thinking that it was just a problem my phone has. The only thing I have not been able to test is using a different cable. I have been using the original OEM one, but I guess it could be the problem.
When did you bought the device?
if its within a year... you can exchange it... this looks like easy way out.
Sent from My Captivate
삼성 겔렉시에서 보냄
peurocs4 said:
When did you bought the device?
if its within a year... you can exchange it... this looks like easy way out.
Sent from My Captivate
삼성 겔렉시에서 보냄
Click to expand...
Click to collapse
Unfortunately, It was purchased off contract and used from someone who lived near me. It is less than a year old, I just don't have the receipt for it. I would say that I bought it around the beginning of last August. They guy who sold it said he only used it for 2 weeks.
Ok, im just going to risk it... Phone should be flashed within the next 10 minutes or so.
yentlequible said:
Ok, im just going to risk it... Phone should be flashed within the next 10 minutes or so.
Click to expand...
Click to collapse
I had the same prob at first and what i found is that I had to remove the drivers and then let windows 7 reinstall the drivers on its own again after turning debugging on, then used Odin to activate DL mode and let those drivers install as well
zelendel said:
I had the same prob at first and what i found is that I had to remove the drivers and then let windows 7 reinstall the drivers on its own again after turning debugging on, then used Odin to activate DL mode and let those drivers install as well
Click to expand...
Click to collapse
How do you use Odin to activate DL mode? I was unaware that it could do that...
I've tried using both Odin methods, even using sdk tools, through command prompt with adb. Nothing is working. My Captivate gets to the download screen, and that's as far as it gets. I've watched numerous videos about this, and haven't come across this problem before.
I'm not an idiot, i've flashed a few roms before, but i'm using phoenix 6.0 with a basic speedmod kernel, no under/over clocking.
Can someone please help me with this, it's extremely frustrating. Thank you
wow
wow, ok, now I still can't get back to stock with odin, nor can I get back the first boot screen past the AT&T World Phone screen
Are you either able to do download with the Vol Up & Down and insert USB and have ODIN recognize?
More details, how did you get here, what have you tried?
Sent from my Captivate using XDA Premium App
mcord11758 said:
More details, how did you get here, what have you tried?
Sent from my Captivate using XDA Premium App
Click to expand...
Click to collapse
I dont mind helping... easier way is IM tho.... google talk.... i'll IM my gmail....
lovethegame0204 said:
I've tried using both Odin methods, even using sdk tools, through command prompt with adb. Nothing is working. My Captivate gets to the download screen, and that's as far as it gets. I've watched numerous videos about this, and haven't come across this problem before.
I'm not an idiot, i've flashed a few roms before, but i'm using phoenix 6.0 with a basic speedmod kernel, no under/over clocking.
Can someone please help me with this, it's extremely frustrating. Thank you
Click to expand...
Click to collapse
When I first decided to flash to stock using Odin I had all kinds of issues. Everything from nothing happening to it only flashing halfway through. My problem turned out to be the cable. I was using a cheap microUSB cable at work. When I got home, I used the original cable that came with the device and had no issues.
Things you can try;
- Using a different microUSB cable
- Making sure you have the samsung drivers installed. If they are, uninstall and reinstall
- Try different USB ports with the microUSB cable. Some people say they had problems using the front ports while others the back ports. Worth a shot
- Try using a different version of Odin either newer or older
- If you have access to another PC, try flashing from there as well
Hope this helps
i've tried using both odins, the 3 click, and the one click. I've gone in with "AIO Captivate Toolbox" and also through the command prompt with adb.exe. It starts flashing and puts my phone into download mode, where Odin has it recognized, then it gets removed, but it never comes back like its supposed to.
for b naughty my google name is [email protected]
B-Naughty said:
Are you either able to do download with the Vol Up & Down and insert USB and have ODIN recognize?
Click to expand...
Click to collapse
I can get into download mode, but after that, odin stops recognizing my phone, and it never comes back to odin. I just have to unplug and reboot it.
ok guys, a couple people said re install the drivers, and that worked. Thank you very much, you saved me from owning a brick. Apparently it didn't install them properly the first time. Thank you to those that helped, I really appreciate it, truly. This is a great site, and the devs, and other members are awesome
lovethegame0204 said:
ok guys, a couple people said re install the drivers, and that worked. Thank you very much, you saved me from owning a brick. Apparently it didn't install them properly the first time. Thank you to those that helped, I really appreciate it, truly. This is a great site, and the devs, and other members are awesome
Click to expand...
Click to collapse
I too am having huge driver issues... I uninstalled the ones that work perfectly, and installed the ones in the aio tool... now huge driver issues... took me an hour to go to stock and load another rom... fixin to load cyanogen so gotta use the nexus s drivers... hopefully those will work better...
lovethegame0204 said:
I can get into download mode, but after that, odin stops recognizing my phone, and it never comes back to odin. I just have to unplug and reboot it.
Click to expand...
Click to collapse
Make sure Odin is up and running prior to going into download mode.
Will not fully reboot after flash back to stock ROM
Just flashed back to stock Rogers with Odin. Everything went OK untill reboot. It gets stuck at the ROGERS screen, then just shuts off!! and ideas?
I have a refurb I897UCKB2 that I rooted and later lost USB connectivity. It is not drivers, pcs, or cables - I tried multiple and they all work for other Captivates. I have root explorer, titanium backup, etc working. I searched for files >1 and <60 days and found MANY in /system/xbin beyond the 3 that come on stock kb2. Can I safely use root explorer to delete them since it already has root access and is in memory? Will I be able to uninstall super-user after? What is the best process to remove roor traces without flashing via ODIN. I can transfer files wirelessly if that helps. Come on gurus... Who can figure out the best solution...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Open another thread on the exact same thing?
Did you even try the dialer codes I posted in the other thread? If so did it do ANYTHING?
studacris said:
Open another thread on the exact same thing?
Did you even try the dialer codes I posted in the other thread? If so did it do ANYTHING?
Click to expand...
Click to collapse
I will try that and report back. However, once the superuser app is gone I have no way to re-root without USB and I really doubt it will delete all those system files. I normally am willing to give anything a shot but I only have one chance to clean up before sending it back. I created a new thread to clearly show what I am up against and it is NOT a typical problem. There is no "automated" way that I can use (with high confidence) so I think a manual process makes sense in this case. I got no other feedback. I do appreciate your help - I just want to see if there are other options since it could easily wind up unrooted with no way to re-root and lots of trace files left over...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I highly doubt samsung will take the time to go through your returned phones file system to make sure you didn't root. If they did that to your phone they would do that with all of them, that is a waste of man hours thus a waste of money for them.
They will fix the usb, reflash/master clear it, then give it to another person...
studacris said:
I highly doubt samsung will take the time to go through your returned phones file system to make sure you didn't root. If they did that to your phone they would do that with all of them, that is a waste of man hours thus a waste of money for them.
They will fix the usb, reflash/master clear it, then give it to another person...
Click to expand...
Click to collapse
Thanks - my only concern is that they could have automated the check. Run a program that generates a "checksum" of stock files that can't change without root and they would know immediately. You are probably right but what I listed would no be hard at all..
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Disclaimer: I am still an android noob. Most of the information below is speculation based on what little i do know. Please flame accordingly
Some quick browsing came up with this link...
http://androidforums.com/captivate-all-things-root/170237-heres-how-you-unroot-your-captivate.html
The first post has a zip you can download to remove root. If you have the ability to sync files via network (such as dropbox) you can download the file to a PC and transfer it to your SD that way. Just replace the update.zip that you used to root the phone in the first place with the one you download through the link and run it through recovery mode.
(Note: you may be able to download it directly through the phone, haven't tried it so i dont know if it will work that way)
I do not know if this will remove any "trace" of the phone being rooted such as modified or extra files but it might be a good start..
If you want to do a full wipe such as ODIN (w/o cables) i think you can find the stock ROM somewhere that you could flash with CWM and then reflash the 2e recovery to cover up your tracks. Again, i dont know what specific traces, if any, this may leave on your phone as "evidence".
I dont have the specific links for the stock ROM or recovery but some googling should turn something up pretty quickly.
If you have Wifi access, search to the forum for the stock 2.2 cwm flashable. I've got that floating around on my PC somewhere. I used to use that when I would Odin to stock 2.1, the install CWM, then flash stock 2.2 on top. That would get rid of root.
Edit, Heh, just saw the last paragraph in the post above. Yeah, what he said.
I wiped it via factory reset
Thanks but I didn't use ODIN because there would be no way to get KB2. I eventually unrooted and then did a factory reset. The extra files were still there but I am sending it back the way it is.
Forgive me for being a noob here,but there is a app called Z4 root get the apk file install it and select unroot....!
it will uninstall superuser !
Good Evening XDA Note 4 Devs/Users,
The Bad News;
I seem to have gotten myself into a pickle. and, Hopefully.. one that isn't permanent.
So, I was planning on reinstalling Firekat 4.4.4 after being on CM12 (Lolipop) Remix. everything went super till I went to wipe my data/cache. In the process of being yelled at by two people and in the stress of it all I accidentally wiped the system data too. Which, seems to have deleted just about everything.. including the original backup of my device, the two ROMS and the system OS. The phone is also claiming not to be rooted now and TWRP seems to have been deleted too. The only thing I can really do is boot into download mode which ODIN keeps refusing to detect. and, Windows 8.1 keeps thinking the phone is a Banana.
The Good News;
I May have a Backup of the Original Unrooted TMO KitKat stored on my Laptop from ODIN.
I May Be able to push the Unrooted ROM by ADB / ODIN
I can boot into Download mode.
So, knowing my predicament and knowing I screwed up. Any advice or help from here to get the device working again?
Also, I promise not to try and turn the phone into a brick again. :good:
Thank you in Advance! :highfive:
Odin
follow this http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
madmike23 said:
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
Click to expand...
Click to collapse
I came from a phone that if you end up deleting everything like this. You bricked the device completely with it not even turning on. (Older android phone). So, Naturally. I thought I had screwed myself with it. lol
I did fix it though right after I posted the thread. I managed to get one of the rom's to flash through odin. (so, I guess I did not accidentally unroot it). I think I Love Samsung phones now that I can accidentally brick it and then still get myself out of trouble with the help of you all
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
Click to expand...
Click to collapse
I regret to say this is my first Samsung device.. was a Motorola and HTC fanboy before both which I bricked one way or the other..
BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while.
Click to expand...
Click to collapse
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Face_Plant said:
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Click to expand...
Click to collapse
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
BACARDILIMON said:
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
Click to expand...
Click to collapse
I couldn't get into download mode. The phone was completely unresponsive to all button combos and my laptop. I tried a USB jig, an unbrick image flashed on an SD card, yelling at it, and sending it off for JTAG but nothing could bring it back. I was quite sad because I had a lot of good memories with that phone, but my Note 4 fills the void nicely.
Hi
I managed to get in trouble with note 3...I have listed my entire trial & error here, can someone please help me bring this phone back to life.
http://forum.xda-developers.com/gal...ed-samsung-note-3-n9005-t3058408/post59580154