Related
Im trying to unroot my phone and get it back to its stock form but when i try to flash the stock t-mobile t999 rom i either get stuck on "get pit for mapping" or ODIN gets to about 80% done flashing and then disconnects the phone then reconnects it
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> cache.img.ext4
<ID:0/008> NON-HLOS.bin
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!
What is your model phone? Look under battery to be certain.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
What is your model phone? Look under battery to be certain.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
sorry i didnt include that but my phone model is SGH T-999
Try using mobile Odin. There is a free version here on XDA. Just need to search for it
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Try using mobile Odin. There is a free version here on XDA. Just need to search for it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion ill try it out and report what happened
I think I had a similar problem. Try checking flash bootloader and make sure you've got the right files otherwise bye bye. If not I would suggest a different computer with drivers installed.
Sent from my SGH-T999 using Tapatalk 4 Beta
TheLastSidekick said:
I think I had a similar problem. Try checking flash bootloader and make sure you've got the right files otherwise bye bye. If not I would suggest a different computer with drivers installed.
Sent from my SGH-T999 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Do you know what the right files are? I've tried to figure that out before but no one can ever tell me exactly what should be flashed using the bootloader option in odin...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Do you know what the right files are? I've tried to figure that out before but no one can ever tell me exactly what should be flashed using the bootloader option in odin...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
No sorry bro. I do know for a fact that everything I needed for my T999 was in the root66 return to stock firmware thread. I'd try going back to the default firmware this phone shipped with for best luck though.
But to Op and anyone else stuck, if the bootloader won't flash then you've got a serious problem if it's already corrupted. My guess is its the OS and your drivers acting weird. Does it say USB Composite Device in Odin? Just a double check, but make sure the architecture of your OS (x86 or x64) matches the drivers you have installed. I'd recommend uninstalling the drivers then rebooting and reinstalling them once more and rebooting once more and it should work from there.
Sent from my Nexus 7 using Tapatalk 4 Beta
DocHoliday77 said:
Try using mobile Odin. There is a free version here on XDA. Just need to search for it
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
This or try flashing the firmware updates through recovery.
Here's the link to the .zip file to all of you that want to manually update to Samsung Galaxy Note II to 4.3. Please post your "About Device" screenshot after completing the update and thanks.
https://www.dropbox.com/s/pnc6ofvuhlm9z25/USER_L900_SPT_MC2_to_MK4_Update_FWD.zip
Here's mine!!
Sent from my SPH-L900 using xda app-developers app
So this is a leak. And not the official OTA? The official build is PAMK4 and this one is PUBMK4
The rest is Deleted. Phone went nuts in pocket.
PUBMK4 or PAMK4 it's 4.3 Nonetheless! If it's not the official build we'll get it pushed to our phones later on anyways!
Sent from my SPH-L900 using xda app-developers app
Anyone else notice a longer delay when waking up your device after this update?...or is it just me?
Sent from my SPH-L900 using xda app-developers app
The Dropbox link has been disabled because of high traffic on their servers so here's a new link to Mediafire.
http://www.mediafire.com/?yxu7eu47h4dhaht
Enjoy!
Sent from my SPH-L900 using xda app-developers app
patrick_1 said:
Anyone else notice a longer delay when waking up your device after this update?...or is it just me?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I did it is definitely a fraction slower.
patrick_1 said:
Anyone else notice a longer delay when waking up your device after this update?...or is it just me?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I remember on 4.1.2 you needed to disable some s-voice options that created that delay...just a guess
Could it be updated for SM-N9005?
Sent from my Note 3 using Tapatalk
i just tried it.. and unless im missing something it didnt work. told me it couldnt verify esignature or something.. i dont need to be rooted for this do i?
thanks.....
butthe knbox is terrible...
Sent from my SPH-L900 using xda app-developers app
You have to be bone stock for this to work. To avoid any problems just flash a stock rooted or non rooted rom on the forums and then download the update file from your computer and not your phone. Put that update zip on external SD and power down to stock recovery and flash. Even the slightest mod can not allow you to update. I had a stock backup and I kept getting signature errors. I just found a bone stock ROM and flashed that and updated fine.
Sent from my SPH-L900 using XDA Premium 4 mobile app
bonebeatz1234 said:
You have to be bone stock for this to work. To avoid any problems just flash a stock rooted or non rooted rom on the forums and then download the update file from your computer and not your phone. Put that update zip on external SD and power down to stock recovery and flash. Even the slightest mod can not allow you to update. I had a stock backup and I kept getting signature errors. I just found a bone stock ROM and flashed that and updated fine.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you be willing to give a step by step on how to download and put 4.3 on phone, I've been waiting for this update and this is the closest website I have found on how to manually do it, but am terribly ignorant about how to do it.
rongd said:
thanks.....
butthe knbox is terrible...
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
what is knbox?
Stuck on Boot, unable to flash stock ROM
Hello,
I am inexperienced with manually updating the OTA file. My Sprint Note 2 was previously rooted but I removed the root using a stock firmware via ODIN 3.09. I downloaded this zip, unzipped it, and then tried using ODIN. In my inexperience, I used the PHONE (CP) tab and installed the sboot.bin file using ODIN 3.09 and now my phone is stuck on boot. I tried reflashing the ROM with a stock using the PDA (AP) option but I keep getting this error from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L900VPAMC2_L900SPTAMC2_1090526_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
KIES_HOME_L900VPAMC2_L900SPTAMC2_1090526_REV04_user_low_ship.tar.md5 came from SamMobile.
I tried using other versions of ODIN as well (3.07 mainly) but all of them gave me the same error message. My phone would tell me unsupported version.
Can anybody help me unbrick my phone?
If your not advanced wait for a ROM without knox bootloader . Knox is a pain if your a noob . check the forums it should be one up in a day or to
Sent from my SPH-L900 using XDA Premium 4 mobile app
QuantumInteger said:
Hello,
I am inexperienced with manually updating the OTA file. My Sprint Note 2 was previously rooted but I removed the root using a stock firmware via ODIN 3.09. I downloaded this zip, unzipped it, and then tried using ODIN. In my inexperience, I used the PHONE (CP) tab and installed the sboot.bin file using ODIN 3.09 and now my phone is stuck on boot. I tried reflashing the ROM with a stock using the PDA (AP) option but I keep getting this error from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_L900VPAMC2_L900SPTAMC2_1090526_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
KIES_HOME_L900VPAMC2_L900SPTAMC2_1090526_REV04_user_low_ship.tar.md5 came from SamMobile.
I tried using other versions of ODIN as well (3.07 mainly) but all of them gave me the same error message. My phone would tell me unsupported version.
Can anybody help me unbrick my phone?
Click to expand...
Click to collapse
Follow the steps I have in this thread and all will be okay. http://forum.xda-developers.com/showthread.php?p=47766521
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
Follow the steps I have in this thread and all will be okay. http://forum.xda-developers.com/showthread.php?p=47766521
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm a little new to all of these. What did you mean when you said "twrp or cwmr with odin"?
EDIT: Nvm, I figured it out. I download a recovery img for the SPH-L900 from ClockworkMod Rom and converted to tar using a tool created by user cabloomi here on the XDA forum. I loaded it and now i'm waiting for the MC2 file to finish downloading.
jlmancuso said:
Follow the steps I have in this thread and all will be okay. http://forum.xda-developers.com/showthread.php?p=47766521
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, I've ran into some issues. I downloaded the files that I was told to download. I used Caboomi's file to change the .img to .tar and flashed using ODIN. I assume that I'd have to go into Clockworkmod Recovery mode in order to flash the MC2 files. However, I can't get into Clockworkrecovery Mod. I tried holding the volume up, power button, and home button but it just shows me the Galaxy Note II splash screen.
FYI you can update through kies.
Sent from my SPH-L900 using xda app-developers app
HELP
I downloaded the USER_L900_SPT_MC2_to_MK4_Update. But how do you install it? I am a noob and am in need of help. Thanks
:crying: since two days ago, I have the same problem... I tried with ODIN and it said:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is the picture of what ODIN said!
Please help me out if you know what I have to do...
I see i9505 in the image. Isn't that a s4?
http://www.gsmarena.com/samsung_i9505_galaxy_s4-5371.php
audit13 said:
I see i9505 in the image. Isn't that a s4?
http://www.gsmarena.com/samsung_i9505_galaxy_s4-5371.php
Click to expand...
Click to collapse
I747 is the s3
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
Had the same problem. Turned out to be a bad USB cable. Switched cables and it flashed perfectly.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
I747 is the s3
Sent from my SGH-I747 using xda app-developers app
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
Had the same problem. Turned out to be a bad USB cable. Switched cables and it flashed perfectly.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Next to the word Odin in the screenshot, I see i9505.
audit13 said:
Next to the word Odin in the screenshot, I see i9505.
Click to expand...
Click to collapse
Thats just the init file in the folder with the Odin.exe
Chainfire has his autoroot name with his packaged Odin, it can flash anything though.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
Thats just the init file in the folder with the Odin.exe
Chainfire has his autoroot name with his packaged Odin, it can flash anything though.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I see. I was thinking that the incorrect firmware was used for the phone that was connected to Odin.
Thanks for the information.
audit13 said:
I see i9505 in the image. Isn't that a s4?
http://www.gsmarena.com/samsung_i9505_galaxy_s4-5371.php
Click to expand...
Click to collapse
hello, i already change the USB cable... and nothing happened... :crying:
82apl said:
hello, i already change the USB cable... and nothing happened... :crying:
Click to expand...
Click to collapse
It's either a bad download, bad USB cable or incorrect drivers.
Re download the file. Try again.
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
It's either a bad download, bad USB cable or incorrect drivers.
Re download the file. Try again.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
i downloaded 3 times differents firmwares... 4.3, 4.2 and 4.0.2 and nothing.... even i tried in my sister's computer... I'll do it again just to make sure... thank u very much... :angel:
82apl said:
i downloaded 3 times differents firmwares... 4.3, 4.2 and 4.0.2 and nothing.... even i tried in my sister's computer... I'll do it again just to make sure... thank u very much... :angel:
Click to expand...
Click to collapse
Where are you downloading them from?
What were you running before you started having problems.
Are you verifying they are the correct file size?
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
Where are you downloading them from?
What were you running before you started having problems.
Are you verifying they are the correct file size?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I downloaded in http://www.sammobile.com/firmwares/2/
I was running the last version of Cyanogen, but i dont like it, and just wanted to go back.... and then, I got stock... before I put the Cyanogen, I was with SO 4.3
82apl said:
I downloaded in http://www.sammobile.com/firmwares/2/
I was running the last version of Cyanogen, but i dont like it, and just wanted to go back.... and then, I got stock... before I put the Cyanogen, I was with SO 4.3
Click to expand...
Click to collapse
OK if you were on stock 4.3 you can't flash anything but 4.3
Flashing the older firmwares will brick your device.
I'm out of options for you right now...
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
OK if you were on stock 4.3 you can't flash anything but 4.3
Flashing the older firmwares will brick your device.
I'm out of options for you right now...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
i have 4.3, then I put the last version of Cyanogen... is that ok???
82apl said:
i have 4.3, then I put the last version of Cyanogen... is that ok???
Click to expand...
Click to collapse
Yup. Just can't flash a stock firmware lower than 4.3
The lower boot loader in the lower stock versions will brick it
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
Yup. Just can't flash a stock firmware lower than 4.3
The lower boot loader in the lower stock versions will brick it
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
okis... i will try to download again the version 4.3, and trying with ODIN again... thank u so much.:victory:
I'm not certain but I don't think AT&T released 4.3 as a complete flashable ROM for Odin, it was only released as an OTA update.
This might help: http://forum.xda-developers.com/showthread.php?t=2498233
KorGuy123 said:
Yup. Just can't flash a stock firmware lower than 4.3
The lower boot loader in the lower stock versions will brick it
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
i saw that the real side of the file es 623.10 MB and the file that I have is more than 700 MB... so, I dont know...
KorGuy123 said:
Yup. Just can't flash a stock firmware lower than 4.3
The lower boot loader in the lower stock versions will brick it
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did it, and it said again:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
here is the picture!!!!
82apl said:
I did it, and it said again:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
here is the picture!!!!
Click to expand...
Click to collapse
That seems like a small file size...
My 4.3 stock rom (rooted and downloaded from here) is 1.41gig
KorGuy123 said:
That seems like a small file size...
My 4.3 stock rom (rooted and downloaded from here) is 1.41gig
Click to expand...
Click to collapse
the size for my file is: 1.16 gigas see the pic
The question I have is when the s4 is in power off charging mode it now just freezes with the white circle when charging screen stays on and when the cable is removed and the charging battery remains on screen /!? So I have to hold the power for what seems like 6 seconds : this can't be normal but I have tried 2 different recovery roms (CWM,TWRP) clearing everything including boot and loading a bunch of roms: NOTHING HELPS or changes a thing. where does this leave the situation. My wife is going to be mad if I don't put it back to stock I assume..
Just to clarify too I just used Cyanogen's new N1 auto root with 4.4.2 C11. And if I didn't login to Google which automatically downloaded all her apps (huge games) eventually gave me 50 920 errors which I couldn't fix. Now what is this a common side effect for everyone ?
If so how come everyone is modding to this killing the knox status and all seems fairly broken with the latest of kernels and roms ;(
Is this all from Knox? I am also getting a message stating something about SEANDROID warranty bit on kernel disabled. Yellow and red message top left..
Can someone just let me know what another sgh m919 does after root with Knox.. What is expected?
Sent from my SGH-M919 using xda app-developers app.. I an not she but my above average intelligence on the topic have me concluding this is a kernel issue but I have the latest slimkat from April said out had the latest kernel... Anyways everything is the same after cwm and freshest twrp wipe 5x on everything including SD and boot still nothing
Guessing I will need Odin and a go back to JB then OTA update to 4.2.2 only problem is this doesn't do anything but or me back at the stating line..
Any advice welcome please inform or enlighten me any way you can
Sincerely
Sean
What does the yellow message under the red one say in the boot screen?
Sent from my GT-I9505G using XDA Premium 4 mobile app
Kriptik210 said:
What does the yellow message under the red one say in the boot screen?
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
: Kernel is Not SEANDROID Enforcing
Set Warrenty Bit : Kernel
Ohh thank you, thank you, thank you : she gets home in 20 minutes kinda scared : j/king
sincerely
futiless said:
: Kernel is Not SEANDROID Enforcing
Set Warrenty Bit : Kernel
Ohh thank you, thank you, thank you : she gets home in 20 minutes kinda scared : j/king
sincerely
Click to expand...
Click to collapse
refreshing this page like a mad man for some help : just noticed the kernel message changes to recovery only when unplugged and booting recovery of course
I think this means it has been rooted weird : maybe ?
Did you make a backup before you flashed anything?
Sent from my GT-I9505G using XDA Premium 4 mobile app
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
The red and yellow is nothing to worry about. That is what pops up when you flash a custom kernel
Sent from my GT-I9505G using XDA Premium 4 mobile app
Kriptik210 said:
Did you make a backup before you flashed anything?
Sent from my GT-I9505G using XDA Premium 4 mobile app
---------- Post added at 09:40 PM ---------- Previous post was at 09:39 PM ----------
The red and yellow is nothing to worry about. That is what pops up when you flash a custom kernel
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually no I didn't because the N1 Cyanogen root tool for NOOB's automated everything so no actually I did not.
Otherwise yes I would consider that standard protocol
:::::::: Im screwed aren't I
Try taking the battery out for 10 seconds, clear data and cache, and reboot. If you still have problems then you need to Odin your phone back to stock.
Sent from my GT-I9505G using XDA Premium 4 mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:52 PM ----------
What carrier do you have?
Sent from my GT-I9505G using XDA Premium 4 mobile app
Kriptik210 said:
Try taking the battery out for 10 seconds, clear data and cache, and reboot. If you still have problems then you need to Odin your phone back to stock.
Sent from my GT-I9505G using XDA Premium 4 mobile app
---------- Post added at 09:53 PM ---------- Previous post was at 09:52 PM ----------
What carrier do you have?
Sent from my GT-I9505G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK I really appreciate the advice and it makes sense but in your advice what is the best method of returning m919 to stock // rooting it in the first place : I imagine this is all caused by the rooting protocol in that "new Autorooter of Cyanogenmod"
sincerely
Sean
http://forum.xda-developers.com/showthread.php?t=2335109
Use this link but I recommend using your PC, not mobile Odin.
Sent from my GT-I9505G using XDA Premium 4 mobile app
futiless said:
OK I really appreciate the advice and it makes sense but in your advice what is the best method of returning m919 to stock // rooting it in the first place : I imagine this is all caused by the rooting protocol in that "new Autorooter of Cyanogenmod"
sincerely
Sean
Click to expand...
Click to collapse
Grab the stock firmware from Sammobile.com. Then use Odin to flash the tar file.
My S4 is Insane...is yours?
Deviant Development Team Member
The Sickness said:
Grab the stock firmware from Sammobile.com. Then use Odin to flash the tar file.
My S4 is Insane...is yours?
Deviant Development Team Member
Click to expand...
Click to collapse
Assuming I am back at stock following your advice can what is the all around best way to root : as it seems the method in the N1 auto rooting tool caused this ...
I AM NOT A DEV so can someone explain are all rooting methods 1:1 finished product or are there slight variances / etc to be aware of ?
BTW I did the procedure 2 times now ..
thanks for the help guys
Try Saferoot
Sent from my GT-I9505G using XDA Premium 4 mobile app
I assume your T-Mobile. Use CF-AUTO ROOT.
http://forum.xda-developers.com/showthread.php?t=2294005
My S4 is Insane...is yours?
Deviant Development Team Member
ODIN fails to reinstall M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 from jellybean
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ran kies went back to stock after 3 attempts ": used the recommended CF-Root and same problem I do have a backup of my efs.,
BUT same thing stuck at the same screen battery circle : 6 seconds needed to reboot ?
Now what ?
Thanks again for all the help BTW
futiless said:
ODIN fails to reinstall M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 from jellybean
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ran kies went back to stock after 3 attempts ": used the recommended CF-Root and same problem I do have a backup of my efs.,
BUT same thing stuck at the same screen battery circle : 6 seconds needed to reboot ?
Now what ?
Thanks again for all the help BTW
Click to expand...
Click to collapse
Flash while the phone is booted up then flash while in download mode
Sent from my SGH-M919 using XDA Premium 4 mobile app
Whats wrong with this now :
futiless said:
ODIN fails to reinstall M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 from TWRP
SCREEN READS
START [224, 1440]
SW REV. CHECK FAIL :fused 5, Binary 1
ODIN SCREEN
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
ran kies went back to stock after 3 attempts ": used the recommended CF-Root and same problem I do have a backup of my efs.,
BUT same thing stuck at the same screen battery circle : 6 seconds needed to reboot ?
Now what ?
Thanks again for all the help BTW
Click to expand...
Click to collapse
Kriptik210 said:
Flash while the phone is booted up then flash while in download mode
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do you use ODIN outside download mode ?
The situation as it stands is that if I use ROOT_M919UVUAMDL.zip from TWRP I get the power off charging mode back :good: But Loose the ability to boot slimkat SO back and forth to no avail trying this and that ...
I thought this was automated DARN !
Saferoot is avail for
VRUEMJ7, VRUEMK2 and UCUEMK2
So that means it wont work on Kit Kat and I can't get the ODIN to let me back either : Kies seems to be my option but again kit kat..
Hey everyone!
Ok so this is my problem.....
My phone ran out of charge so I was switching batteries. After I switched batteries my phone stopped working.
It boots up to the "Samsung GALAXY Note II" white logo but doesn't boot past that. I tried to boot into recovery mode but it didn't work. I tried to re-flash stock with Odin and Odin says "Pass," but never boots up after that. I tried looking through many other forums but came to no avail. I know that my phone is not hardbricked since I am able to boot it into Download Mode. I have re-flashed stock 5 times and Odin says Pass, but it doesn't seem to be working.
Here is the text when I boot into Download Mode:
"ODIN MODE
PRODUCT NAME: SGH-T889
CUSTOM BINARY DOWNLOAD: YES (8 counts)
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 1
AP SWREV: A2"
Here's the Odin Log:
"<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> tz.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)"
Please Help me out!!!!!
Have you find a wipe of system, data, and cache?
Reply
Coug76 said:
Have you find a wipe of system, data, and cache?
Click to expand...
Click to collapse
Since I am not able to boot into recovery mode I was unable to wipe system, data, and cache.
How about adb?
Coug76 said:
How about adb?
Click to expand...
Click to collapse
adb doesn't work in Download Mode, right?
Grasping at straws now. Does the sticker under the battery show SGH-T889?
Hastily spouted for your befuddlement
Coug76 said:
Grasping at straws now. Does the sticker under the battery show SGH-T889?
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I just looked under the battery to notice that the sticker is missing the Model Number as well as the Serial Number. I believe this is due to the replacing of my phone a few days after I first got it. The audio jack wasn't working so I had to claim insurance on my phone and T-mobile told me that their insurance company would send over another phone. My dad happens to have the same phone as me and I took a look at the sticker behind the battery and it did have the Model Number and Serial Number. The model number under his battery is SGH-T889 and we have the same phone. On the sticker under my battery there it does say "T889" followed by a bar code though.
I have been running cyanogenmod nightlies on my device for about a year and a half now and under device information it always said SGH-T889. Also I used the unified Android Toolkit before and always used SGH-T889 as my device.
veeman961 said:
Hey everyone!
Ok so this is my problem.....
My phone ran out of charge so I was switching batteries. After I switched batteries my phone stopped working.
It boots up to the "Samsung GALAXY Note II" white logo but doesn't boot past that. I tried to boot into recovery mode but it didn't work. I tried to re-flash stock with Odin and Odin says "Pass," but never boots up after that. I tried looking through many other forums but came to no avail. I know that my phone is not hardbricked since I am able to boot it into Download Mode. I have re-flashed stock 5 times and Odin says Pass, but it doesn't seem to be working.
Here is the text when I boot into Download Mode:
"ODIN MODE
PRODUCT NAME: SGH-T889
CUSTOM BINARY DOWNLOAD: YES (8 counts)
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 1
AP SWREV: A2"
Here's the Odin Log:
"<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCMK7_T889TMBCMK7_T889UVUCMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> tz.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)"
Please Help me out!!!!!
Click to expand...
Click to collapse
What version of Android were you in b4 it crashed?
Sent from my GT-N7105 using XDA Premium 4 mobile app
terpin32 said:
What version of Android were you in b4 it crashed?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was running cm11 nightlies so 4.4.4.
Oh and I used to have TWRP installed, if that matters at all.
I did try flashing another recovery but my phone still won't boot into recovery mode.
veeman961 said:
I was running cm11 nightlies so 4.4.4.
Oh and I used to have TWRP installed, if that matters at all.
I did try flashing another recovery but my phone still won't boot into recovery mode.
Click to expand...
Click to collapse
Reflash your bootloader and it should boot
Sent from my GT-N7105 using XDA Premium 4 mobile app
terpin32 said:
Reflash your bootloader and it should boot
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for not knowing, but how do I do that?
veeman961 said:
Sorry for not knowing, but how do I do that?
Click to expand...
Click to collapse
Im on att but i had the same problem but find the rom or whatever version of Android you were on and find out what bootloader you had and look to see if you can find somewhere to download it and flash itin odin like you did b4 but just the bootloader
Sent from my GT-N7105 using XDA Premium 4 mobile app
terpin32 said:
Im on att but i had the same problem but find the rom or whatever version of Android you were on and find out what bootloader you had and look to see if you can find somewhere to download it and flash itin odin like you did b4 but just the bootloader
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I use this: http://forum.xda-developers.com/showthread.php?t=2636552?
Just a quick question: doesn't the bootloader get reflashed every time I flash stock rom?
veeman961 said:
Just a quick question: doesn't the bootloader get reflashed every time I flash stock rom?
Click to expand...
Click to collapse
But you can't get to recovery tho right?
Sent from my GT-N7105 using XDA Premium 4 mobile app
terpin32 said:
But you can't get to recovery tho right?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i can get to recovery. but i thought that when i flash stock rom, the bootloader is also flashed so how will it help if i reflash just the boot loader?
and also i wasn't able to find the bootloader files, can u send me a link or something of where i cud find it?
veeman961 said:
i can get to recovery. but i thought that when i flash stock rom, the bootloader is also flashed so how will it help if i reflash just the boot loader?
and also i wasn't able to find the bootloader files, can u send me a link or something of where i cud find it?
Click to expand...
Click to collapse
You on stock recovery or custom?
Sent from my GT-N7105 using XDA Premium 4 mobile app
terpin32 said:
You on stock recovery or custom?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I used to have twrp recovery installed. After that I have flashed stock with odin so im not really sure what recovery i am on.
veeman961 said:
I used to have touchwiz recovery installed. After that I have flashed stock with odin so im not really sure what recovery i am on.
Click to expand...
Click to collapse
well here flash this in odin in the ap option and then i would do a full wipe but not your external sd card and flash a rom and you should be good to go
http://www.techerrata.com/file/twrp2/t0ltetmo/openrecovery-twrp-2.7.2.0-t0ltetmo.zip
---------- Post added at 01:27 AM ---------- Previous post was at 01:21 AM ----------
After you flash that idk if the phone will boot into the recovery but If it doesn't pull the battery out and manually put it into recovery mode
Sent from my GT-N7105 using XDA Premium 4 mobile app
terpin32 said:
well here flash this in odin in the ap option and then i would do a full wipe but not your external sd card and flash a rom and you should be good to go
http://www.techerrata.com/file/twrp2/t0ltetmo/openrecovery-twrp-2.7.2.0-t0ltetmo.zip
---------- Post added at 01:27 AM ---------- Previous post was at 01:21 AM ----------
After you flash that idk if the phone will boot into the recovery but If it doesn't pull the battery out and manually put it into recovery mode
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I already tried to flash twrp and cwm and philz touch recovery.
Even after flashing them, my phone will not boot into recovery mode.