To start, you will need
Recovery-cmw-hercules.tar (doesn't have to be the latest, you can update it later). This can be found in other recovery threads, as the process remains the same.
Odin3 v1.85 (or any other compatible version)
root.zip found Here
Steps:
1) Make sure Kies is exited, and you have the drivers installed for Odin. If not, check the other threads as this has been covered many times
2) Just select your CWM recovery for PDA once you are in DL mode (which is achieved by holding down VOL Up and VOL Down when the phone is off as you plug in the cable). Select vol up to confirm dl mode.
3) In Odin, leave the default boxes (Auto reboot and F. Reset time), and then select PDA and choose the .tar file we found earlier. Make sure odin sees your phone properly and start this!
4) once you have CWM recovery installed copy the root.zip to your sd card, and boot into CWM recovery. Do a Nand Backup and then install root.zip and enjoy!
5) Delete that crappy bloat!
For those having connection issues in Odin, try the following.
1) Exit Kies
2) Change to a different USB port
3) Reinstall your USB drivers.
I kept getting an error, and the above fixed that.
Thank you!
Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA
Thanks a lot for posting this for everyone. Hopefully this will quell the 50 billion requests that could be handled by using search or google.
TheTechNiq said:
Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
Its should work the same, my official tmo 4.03 ics
was just rooted doing this
so it's the same process?
Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Teo032 said:
so it's the same process?
Click to expand...
Click to collapse
Yes but make sure you download the root.zip file OP posted a link to.
Once you're done with the odin part, having the recovery-cmw-hercules .tar all done.
You should see CWM rom manager in your app, you can click on it but cant really use it. because you don't have superuser permission, That why you need to copy the root.zip file to your sd card. Now get in to CW recovery by turning off the phone.
hold vol. up+down,and hit the power on button, scroll down and install the root zip.
then reboot. now you should have superuser permission and can now uninstall, or freeze all the junk with Titanium backup.
kwilsonjr said:
what do you mean 'leave the default boxes'?!? leave them checked? leave them unchecked? leave them alone? what? I'm assuming you mean leave the boxes alone (default).
Click to expand...
Click to collapse
Don't touch anything but the PDA button, select the .tar file, and click start.
For those worried about using the GB root process with the new ICS ROM, the Kies flashing does not put a new recovery on it. It's the same one that shipped with your phone. Therefor overwriting the the recovery with CWM 5.0.2.6 (via Odin) is the exact same. The root.zip flashed from VWM just installs su, busybox, and the superuser.apk into the OS, this has been done on many ICS roms already.
TL;DR: the process is identical, and confirmed working.
Rooted! T989 with Stock ICS update!
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!
ResidentJack said:
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!
Click to expand...
Click to collapse
Busybox is included in the root.zip in this post?
Worked like a charm thanks!
Damn... Stuck on "Goodbye"
Ok, so I rooted and it worked perfectly, only problem is I'm now getting stuck on "Goodbye" screen when shutting down, or when restarting. I have removed the battery for 2 minutes, wiped cache, wiped dalvik...
Still the same thing...
Anyone have any ideas?
Thanks
kwilsonjr said:
Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OK. Don't know what the heck is going on. Closed and re-opened odin 5 times and tried each time. It finally took on the 5th try. weird.
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/007> Added!!
What did you guys use to remove all the bloatware?
n/m found it.
Blackleopord187 said:
What did you guys use to remove all the bloatware?
Click to expand...
Click to collapse
I freeze it with titanium backup.
I can confirm the reboot hang issue.
ian577416 said:
I can confirm the reboot hang issue.
Click to expand...
Click to collapse
maybe its an isolated incident on some devices? (I used the OP's root method) I just tried restarting and turning off my phone and i get no hangs on the goodbye screen or anything.
No hang issues here. Root method works great.
Bloat removed,,,,,ALL OF IT!!!!!
Related
Just tried to root my phone following some instructions I found on youtube:
http://www.youtube.com/user/mypd1991#p/a/u/1/cFwy0LXOw2c
At first I got "file type invalid" for the .md5 files I downloaded in the info panel in youtube. I finally found one that works, and I keep getting
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried everything I can find from updating my phone drivers to the specific windows 64 bit version, to following the root and recovery/odin stock flashing instructions here http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700.
I've downloaded various versions of Odin, as well as several different .md5 files and still it's failed.
I've tried all of this with the SD card in, and with it out.
When I try to boot my phone up, I keep getting what's been called the "soft brick" screen http://i556.photobucket.com/albums/...80 Shots/My Samsung Vibrant/vibrant_brick.jpg
Sometimes, and I don't know what I do different, it will acutally turn on like I held down the 3 buttons to reboot the phone, but when I select that option, or any other, it goes back to the soft brick screen.
Five hours later, I'm still surprised my phone is in once piece. It's a bit frustrating. Anyone have anything else I can try? Thanks in advance!
Some people have success when trying a different and better quality usb cable. The one that comes with the phone isn't that great.
Sent from my SPH-D700 using XDA App
Tried it on the comp at work, using a different cable. Worked like a charm. Thanks!
allheilkingmatt said:
Tried it on the comp at work, using a different cable. Worked like a charm. Thanks!
Click to expand...
Click to collapse
Great news. Glad you got it fixed.
Sent from my SPH-D700 using XDA App
See my reply to this thread on page 2 for the resolution.
---
So I unlocked and rooted my VZW LTE galaxy nexus a couple months ago, no problems with the process.
I looked into updating from 4.0.2 to 4.0.4 and found this walkthrough for YAKJU IMM76D:
androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2/
Page 1 goes through checking USB debugging, what to back up first, etc. USB debugging was enabled already.
Page 2 (link above) provides the instructions on what to download, how to run it, etc. I followed the steps there. It went through:
---
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> bootloader.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> radio.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---
As it stands, if I put the battery in the phone, the screen will turn on and display an icon of a mobile device, two dots, a warning ! triangle, two dots, and a PC monitor.
Pressing the power button "reboots" back to this screen - it just turns off, then turns back on.
Vol up and power does the same thing - does not go into recovery
vol down and power does the same thing
vol up, vol down, and power does the same thing
pulling/replacing the battery does the same thing
I am able to re-run Odin3 v1.85 with the PDA download option checked, specifying that same .tar. It will still go through 95% of the process and end the same way, with "FAIL!" shown in Odin and an almost-complete blue progress bar on the phone below that other error image described above.
So, I *think* this should be salvageable, but I don't know how or what/where to find the file(s) that I should be using to fix this.
THANK YOU for reading and any advice you have, and let me know if anything needs clarification. Screenshot of Odin results attached (seems to not be working... imgbucket link alternative: imgbucket.info/photo/ggnkdlyyu/Odin3_v1_failed.jpg)
Youre phone has nothing to boot from. That's what that means... (Check my signature) use that, reflash stock 4.0.2, try again... And do a backup, first!!
If you're very unlucky, you buggered up the whole memory unit. That means, loss of EVERYTHING...
Oh, and: Stop being a whimp Be a man. Stand above it. Think: "I can do it!!"...
It may sound harsh, at first. But, if you would know, how many times, that has happend, with a Samsung Phone, to me... And if I would have given up, I wouldn't have gotten me a developers phone
So, be strong, (Use my root helper) And tell that phone, who's boss!
Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.
trevordyck said:
Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.
Click to expand...
Click to collapse
I like your way, of thinking
Like a man!
The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app
El Daddy said:
The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
OH, well that explains everything! Thanks for that clarification... now back to trying to un-bork my handiwork.
Time to try to get into Odin mode.
Sent from my Galaxy Nexus
Time to "stay" in Odin mode... playing with Odin (ignorantly, a bit) is what got me here...
axne1 said:
Time to try to get into Odin mode.
Click to expand...
Click to collapse
Well I haven't made any progress on the phone, but I've done a few things to try familyguy's stuff. I think I have the latest version of that, and the 4.0.2 downloaded via the program, but I get this error message every time I try to flash a stock LTE ROM with it. Do I need to do this with Odin, this program, or something else?
I think you should read this
http://forum.xda-developers.com/showthread.php?t=1600203
Sent from my Galaxy Nexus
Aha! Thank you much for that. Following a few links I think I can fix it just by specifying a suitable firmware, because Odin does actually run the "PDA" flash until the end (progress bar still shows up on my "soft bricked" display and Odin indicates it's copying stuff). So, when I land later tonight I'll download and give this a try:
dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I guess I'm not really asking any useful question here so much as tracking my attempts... hope I get this sorted before work in the AM!
Awesome!!!
Keep us updated!
Sent from my Galaxy Nexus
No luck yet. I can still run the GSM "Phone" flash in Odin until 95% complete when it fails, but all of my attempts at using Google's archived 4.0.2 for CDMA are stopping at about 15%, and I have to R&R battery to restart it. This is as far as I can get:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!! (*sits here indefinitely)
Any pointers on what is required for the various fields to flash a stock setup to this thing using Odin?
It sounds like it's looking for some type of backup like a nandroid
Sent from my Galaxy Nexus
There is a tool on amazon.com that should help it's called a jig or something like that.
Sent from my Galaxy Nexus
AHHHH! FIXED!
Things I learned:
- Odin is a Samsung product and needs special samsung-y .tar files to flash the phone. Regular ROM stuff doesn't work. (pardon the ignorance in terminology)
- "mysid" specifies a VzW compatible build for the GNEX
- If you accidentally flash a GSM tar to your VzW phone using Odin, Odin is the only thing that will get you out of your sitch (of the things I could figure out how to try. I didn't try any command line stuff. That's last ditch for me - takes more time for me to learn, and a busy Monday morning at work wasn't helping me)
- I found the resolution here: http://forum.xda-developers.com/showthread.php?t=1426207&page=5 - a factory Odin pair of files for CDMA/VzW, one for PHONE and one for PDA. Saved. My. Bacon.
- The $10 wifi on Alaska Airlines is slow as junk.
- Starting this whilst abroad is a bad idea. (HAHA!)
Regarding the walkthrough I followed that got me in this mess - nowhere that I saw did the author (or readers) specify that the flash I was about to try was GSM only. Maybe I missed that detail, but if not it would make sense to me that someone reading a tutorial on how to flash their phone probably would have NO IDEA that yukjiwhatever is GSM and mysid was for CDMA. That would have been good to read, like, in the first paragraph of the article. Anyways...
I have a working phone and somewhere unicorns are grazing in a field. I hope this helps some other equally poor sap recover his phone.
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
XXM3G4XX said:
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
Click to expand...
Click to collapse
Make sure you have usb debugging checked in developer options. I had thew same problem as you but once I selected usb debugging it worked..
Phone doesn't turn on
colint3 said:
Make sure you have usb debugging checked in developer options. I had thew same problem as you but once I selected usb debugging it worked..
Click to expand...
Click to collapse
Hi Colint3 thank you for the first person to reply. Much appreciated.
How can I select USB debugging if the phone doesn't come on for me to access the option.
Although if I remember correctly, I already had it on before this incident occurred.
Update 05/02/2014
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMK9_2138564_REV04_user_low_ship.tar.md5 is valid.
<OSM> AP_N7100XXUEMK9_2138564_REV04_user_low_ship.tar.md5 is valid.
<OSM> CP_N7100XXUEMJ9_REV08_CL1423182.tar.md5 is valid.
<OSM> CSC_OXX_N7100OXXEMK4_2174777_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
still nothing. Any further ideas guys?? thanks again.
XXM3G4XX said:
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
Click to expand...
Click to collapse
i guess you have tick marked repartition..you should not do that..
all these roms all request pit files
iprabhsingh said:
i guess you have tick marked repartition..you should not do that..
Click to expand...
Click to collapse
i have followed so many guides its unbelievable. some say to tick, some says dont.
any roms i try to put on always gets stuck around the partition section.
im looking for a good n7100 pit file thats pretty new and is known to work please. would be really helpful. thanks.
XXM3G4XX said:
i have followed so many guides its unbelievable. some say to tick, some says dont.
any roms i try to put on always gets stuck around the partition section.
im looking for a good n7100 pit file thats pretty new and is known to work please. would be really helpful. thanks.
Click to expand...
Click to collapse
just tell me what you really want to do..do you want to install custom rom..or stock rom..was your device rooted before..??
iprabhsingh said:
just tell me what you really want to do..do you want to install custom rom..or stock rom..was your device rooted before..??
Click to expand...
Click to collapse
My device was rooted. I want to get it to work. Doesn't matter with the roms. Any rom that makes it come on is good enough for me.
When I attempt to get it into recovery, all I get is a blank grey screen with white horizontal lines. Download menu doesn't show the device name and all other details are there.
I have tried everything that I've gathered from different threads as well. Keep on getting stuck on pit section.
I've spoken to samsung and sending it for repairs.
I've looked at other threads and from, that I've gathered its half sds and it's a hardware problem which according to the forums will be replaced as the technicians themselves cannot put roms on so they'll change the faulty parts, install a stock rom and send it back.
I could be wrong, so if there are anything else I could try, please advise. Many thanks.
XXM3G4XX said:
My device was rooted. I want to get it to work. Doesn't matter with the roms. Any rom that makes it come on is good enough for me.
When I attempt to get it into recovery, all I get is a blank grey screen with white horizontal lines. Download menu doesn't show the device name and all other details are there.
I have tried everything that I've gathered from different threads as well. Keep on getting stuck on pit section.
I've spoken to samsung and sending it for repairs.
I've looked at other threads and from, that I've gathered its half sds and it's a hardware problem which according to the forums will be replaced as the technicians themselves cannot put roms on so they'll change the faulty parts, install a stock rom and send it back.
I could be wrong, so if there are anything else I could try, please advise. Many thanks.
Click to expand...
Click to collapse
In my opinion if you are not able to find anything from xda or any other site..i think you should go to samsung service center..
or i guess you have bad recovery..just try to flash a new recovery like cwm or philz recovery through odin..May be this might help you.
Update to the issue NOW lol
Hi guys, hope all is well with everyone. I sent the phone to the service centre and got it back unresolved but better than originally. I have new issues which is explained in a new thread. Please advise and help if possible. Many thanks again guys. much respect.
http://forum.xda-developers.com/showthread.php?t=2658220
I have a Samsung S4 Mini on the Verizon network (SCH-i435). I restarted my phone this morning and it took a much longer than usual to boot. My screen showed the Verizon logo for about 5-10 minutes and when the phone finally booted I was greeted with the utility to set up the phone (pick language, setup email, etc. etc.). I was confused because I had done this already a few months ago when I bought the phone. I skipped the steps and I was greeted with the stock home screen (all my custom shortcuts and widgets were gone). All my marketplace apps were still installed, but some of them had been reset (had to reconfigure waze, winamp, etc). My best guess is that there was an OTA update or some security patch that reset everything. Finally I got things running again the way I liked them. I was using my phone and suddenly it went dead. I tried to restart it but nothing showed on the screen. Oddly enough the phone just vibrates over and over again, but the screen remains black. No matter what I do I can't boot it. The only way I could stop it from vibrating was to pull out the battery. Is there any hope to recover this phone? Thanks.
Did you try to enter recovery mode?
Yes, I followed the instructions on the manufacturer site. I held down the home button, up volume, and powered the device on. A small bit of text appeared for a split second, it was so fast I couldn't read it. It disappeared and the screen went black and the same vibrate pattern started up again.
I got a video camera and managed to capture the text that was being displayed. Here is a screenshot...
It looks like...
MMC: mmc_read fail
Movinaand Checksum Confirmation Fail
Any hope of fixing this?
I asked for recovery cause it was easier to reset to factory the phone. If that's not working, i don't know if there's hope for it to enter download mode, for manual flashing with odin.
I'm able to get into download mode. Is there a ROM I can flash with? This S4 Mini is the Verizon phone so it is the SCH-i435, I didn't think there were any custom roms I could use with this phone.
Stock rom.
Try http://www.sammobile.com/firmware and see if your firmware is there.
Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.
RoyaLKurTx3 said:
Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.
Click to expand...
Click to collapse
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?
droid2501 said:
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?
Click to expand...
Click to collapse
I am not sure since this is the first time for me with experience with that phone...
In Odin, make sure Auto Reboot and F. Reset Time check boxes are only two that are selected. DO NOT SELECT ANY OTHER OPTION! Click the AP/PDA button and select that file you downloaded earlier with extension I435VRUBNE1_I435VZWBNE1_VZW.tar.md5 Click the CSC button and select file with CSC in its name. Ignore if there is no such file. Click the PIT button and select the .pit file. Ignore if there is no such file. (You should have this file, do it if you are having that error) Now, once you are ready, hit the START button to begin the flashing process.
If you have any other problems please ask.
RoyaLKurTx3 said:
(You should have this file, do it if you are having that error)
Click to expand...
Click to collapse
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.
droid2501 said:
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.
Click to expand...
Click to collapse
The file should be one of the extracted files in the file you have downloaded from my links. If the file is not there, then most probably Verizon modded the phone to not be able to flash via Odin Mode.
The error during the update may have happened because of low battery, making your phone shut down during the update, which is serious.
You can check yourself if your phone is under warranty (excluding the warranty period)
-Just go to download mode and you will see: KNOX WARRANTY VOID: [if it is 0x0, than it you are still under warranty, but if it says 0x1, you are not.]
Yeah, you should go to the place you have bought the phone from, if none of the above steps worked for you.
Good Luck.
I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?
droid2501 said:
I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?
Click to expand...
Click to collapse
You got the same version of your previous phone?
Yes, that's all they would do for free. They did offer me a Droid Turbo for and extra $100.00 but I really don't like the large phones they're coming out with these days so I declined.
Then you shouldn't get OTA Updates. I don't think that it was needed since the problem you got earlier was because of a faulty firmware from Verizon, which is unlikely or your phone had no battery while your phone was updating.
I have been trying to go back to stock on this device, but that's not happening.
My Odin flash:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2171 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the tablet itself, it says Odin: Invalid ext4 image. What can I do?
Aloupha said:
I have been trying to go back to stock on this device, but that's not happening.
...
On the tablet itself, it says Odin: Invalid ext4 image. What can I do?
Click to expand...
Click to collapse
Redownload stock ROM.
Using single or multiple file ROM?
I recommend the latter.
To be downloaded with samfirm_reborn if not found elsewhere.
bmwdroid said:
Redownload stock ROM.
Using single or multiple file ROM?
I recommend the latter.
To be downloaded with samfirm_reborn if not found elsewhere.
Click to expand...
Click to collapse
I have tried several stock from different sources, and it always fail at the same place. I did try the multiple files once and that failed too.
@Aloupha imo Odin 3.14 is to new for this old stock ROM.
Try 3.09 or even older ones.
Somewhere I've read recommendations regarding Odin versions to stock ROM versions.
bmwdroid said:
@Aloupha imo Odin 3.14 is to new for this old stock ROM.
Try 3.09 or even older ones.
Somewhere I've read recommendations regarding Odin versions to stock ROM versions.
Click to expand...
Click to collapse
Oh I will give that a shot and see. I will google for an old version.
I went as low as Odin 3.04... it keeps failing at the same place: Odin: Invalid ext4 image
Do you have a link for samfirm_reborn?
@Aloupha using ecosia search gave me this:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
And don't forget to check binary or factory mode to get multiple part ROM.
bmwdroid said:
@Aloupha using ecosia search gave me this:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Oh - I did find that link but didn't know I had the right one. I don't know how to use that site.
@Aloupha on the right hand side you see "Releases" below "About".
There is the link to the download site where you find the .zip to be used.
No need to install. Just unpack it and start as admin.
This is the direct link
Ah that makes sense. Not knowing how it work, I was looking to download the firmware directly from the website. That's why I was confused. Thanks for the tip.
Alright, I downloaded the latest firmware from there and tried. I am still getting the same error.
Is there a stock ROM I could flash via TWRP?
Aloupha said:
Ah that makes sense. Not knowing how it work, I was looking to download the firmware directly from the website. That's why I was confused. Thanks for the tip.
Alright, I downloaded the latest firmware from there and tried. I am still getting the same error.
Is there a stock ROM I could flash via TWRP?
Click to expand...
Click to collapse
That will never work as stock ROM includes stock recovery and comes in a different file format.
Perhaps ADB might work but I never tried.
Which Odin right now?
CU in a few hours.
bmwdroid said:
Perhaps ADB might work but I never tried.
Which Odin right now?
Click to expand...
Click to collapse
I have tried Odin 3.04, 06, 07, 09, and 3.14.4, and none worked. I read somewhere that for this to work, I must have the original cable. Since I don't have the original cable, I don't know what to do.
I would give ADB a shot, but I have no clue how to do that.
Aloupha said:
I have tried Odin 3.04, 06, 07, 09, and 3.14.4, and none worked. I read somewhere that for this to work, I must have the original cable. Since I don't have the original cable, I don't know what to do.
I would give ADB a shot, but I have no clue how to do that.
Click to expand...
Click to collapse
Cable doesn't have to be original but of good quality.
Neither do I. I just once checked if tab is recognised and that worked.
Btw does it still work to flash custom ROM?
bmwdroid said:
Cable doesn't have to be original but of good quality.
Neither do I. I just once checked if tab is recognised and that worked.
Btw does it still work to flash custom ROM?
Click to expand...
Click to collapse
I flashed Custom via TWRP if that's what you mean... yes.