Related
Hey guys...I really need some help here.
I think I've bricked my Continuum. What have been done:
- cwm installed based on this guide http://www.addictivetips.com/mobile/install-clockworkmod-recovery-on-samsung-continuum/, version 2.5.1 (red)
- then rebooted, OS loaded fine
- turned off, download mode, in Odin1.85 all options by default (no re-partition),
EC07 from http://forum.xda-developers.com/showthread.php?t=1224631 - SCH-I400-EC07-FROYO-REL-PRODUCTION.tar.md5
All steps in Odin passed OK, Success indicator and phone turned off.
And now the phone wont even turn on, not even into download mode.
Is there anything I can do about it? I really need some tips here...thanks again.
well, that's my fault.. I flashed mesmerize image )
download mode was working, just w/o that image with android digging shown..
I'm lost? Does dl mode work now?
Sent from my SCH-I400 using xda premium
yes, it does..
actually, as I stated, it was still working after flashing some mesmerize image, but without indication on the screen at all..
so u should be good... flash dl17 stock and go from there.
the target version is EC07; I was flashing it, but is stucked on flashing modem.bin.. so, I aborted it and was still able to load the OS...
now I'm going to try again with EC07 and see weather it goes through modem.bin
Come over to IRC and we'll see if we can't get you fixed up.
http://webchat.freenode.net/
the channel is #samsung-continuum
I'll be there at least 3 more hours.
u need to flash ec07.tar first (modem)
then ec07 stock.zip unluss its the leaked ec07stock.tar wich has radio+kernel+rom all in one.
try this
http://forum.xda-developers.com/showthread.php?t=1248077
The content of the SCH-I400-EC07-FROYO-REL-PRODUCTION.tar.md5
-zimage
-boot.bin
-modem.bin
-recovery.bin
-Sbl.bin
-param.lfs
-cache.rfs
-dbdata.rfs
-factory.rfs
looks like u should be good...
me and txwolf are in irc... come discuss w/ us
ok, now all went OK
<ID:0/058> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I400-EC07-FROYO-REL-PRODUCTION.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/058> Odin v.3 engine (ID:58)..
<ID:0/058> File analysis..
<ID:0/058> SetupConnection..
<ID:0/058> Initialzation..
<ID:0/058> Get PIT for mapping..
<ID:0/058> Firmware update start..
<ID:0/058> param.lfs
<ID:0/058> NAND Write Start!!
<ID:0/058> Sbl.bin
<ID:0/058> boot.bin
<ID:0/058> recovery.bin
<ID:0/058> zImage
<ID:0/058> factoryfs.rfs
<ID:0/058> dbdata.rfs
<ID:0/058> cache.rfs
<ID:0/058> modem.bin
<ID:0/058> RQT_CLOSE !!
<ID:0/058> RES OK !!
<ID:0/058> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/058> Removed!!
Click to expand...
Click to collapse
and? whats ur end result?
I'm on 2.2.2 )
now I want to have it deodex'ed.. in order to play with localization of some applications
As I understand, my further steps would be - install cwm and flash just system from this thread http://forum.xda-developers.com/showthread.php?t=1286000
(the second post from the bottom)
well that ec07 deodexed is not just deodexed, it is but debloated and debinged.
or the ec07clean.zip
pretty much any ec07 besides stock
ahh, ok.. then I'm fine with any ec07
thanks for your support )
bestrafer said:
ahh, ok.. then I'm fine with any ec07
thanks for your support )
Click to expand...
Click to collapse
there is a thanks button (shameless plug)
It seems to me that I'm in need of the same assistance that bestrafer recieved. After messing up my phone to seemingly the point of not return, I did a wipe of the cache, a factory reset and started over. I tried this thread: http://forum.xda-developers.com/showthread.php?t=1248077 and followed the little tutorial made by ciscogee (post 2 - "Cwm red tutorial for ec07 cleanCwm red tutorial for ec07 clean"). It seemed to be successful and all...but upon reboot I'm still only getting to recovery. I then tried doing a restore from backup made before messing up my phone, which also gave me an "installation successful" response. However, upon reboot, I still takes me directly to recovery.
I would love to get the Froyo debloated/debinged version...but I'll be completely satisfied with the stock EC07 and removing that stuff myself. I'm completely new to all of this and am totally lost at this point. Any suggestions or help?
When you say "only getting into recovery' do you mean factors ry recently very, and you get an error saying "update.zip gone"?
Swing into irc.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George
Not so sure how to use the IRC...I've never used it before...but I think that I'm logged into it. username is bsara.
It used to be giving me an "update.zip gone" but I flashed the CWM again and it sees it now. But basically what I mean is that I can't boot into anything other than recovery, CWM, and Download. Hope that makes sense.
I would have you do my magical fix you can find it in general
Sent from my SCH-I400 using xda premium
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Also, redownload the tar file. It could be a bad download.
jd1639 said:
Also, redownload the tar file. It could be a bad download.
Click to expand...
Click to collapse
ok will try that.
here are the messages that I am getting
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
2nd message
ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
xBeerdroiDx said:
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
Click to expand...
Click to collapse
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
If you had mf3 on, no amount of odin is going to help.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
You must have taken the update to MF3. Essentially, you will not be allowed to downgrade firmware back to older versions. The way Samsung is writing the bootloader is there a monotonic counter only going in one direction, up. So if the bootloader has been updated to the latest version by an OTA, you can't revert it back. Currently I believe there is no workaround, but we have some awesome devs on this site so keep your fingers crossed.
jimsond said:
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Click to expand...
Click to collapse
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
jeffreii said:
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
Click to expand...
Click to collapse
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
jimsond said:
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
Click to expand...
Click to collapse
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
jeffreii said:
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
Click to expand...
Click to collapse
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
P.S in kies the current firmware version PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
jd1639 said:
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
Click to expand...
Click to collapse
It look like I have mf3 So I f__k up. The phone is working
jimsond said:
It look like I have mf3 So I f__k up. The phone is working
Click to expand...
Click to collapse
Good to hear the phone is working. I wouldn't mess with it any more.
jeffreii said:
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
Click to expand...
Click to collapse
Thanks for your input I have a hard time saying on paper what was my problem. I like to talk things out and I use the link that you posted and I have root now..
I apologize if my situation is here somewhere. I have read through so many forums and can't find what I need, plus I am sort of new at this. So here goes.
I rooted my Samsung I337 about 8 months ago for the first time. I can't remember exactly how, but I followed a thread here to do it. It worked perfectly! I then flashed the Golden Eye rom to it through TWRP. I have loved it since then. I did a back up of my original rom on my phone from the start. Well, I decided yesterday to unroot it. I followed the directions from a thread here and it seems to have worked except that when I turn it on, the custom screen is first. However, I have no supersu and when I try to get rooting apps it tells me I need to root my phone. So I assume it worked.
Well, I have used it for a day and now remember why I rooted it in the first place. I want to put it back but can't seem to do that. I downloaded Odin, connected my phone, and when I try and download the file to it, it fails. This is what I get.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The only thing I can see is that I am told the COM port should be yellow and mine is blue. Does that make a difference? What could the issue be? Any help would be awesome!
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
traderkat64 said:
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
Click to expand...
Click to collapse
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
DeadlySin9 said:
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
Click to expand...
Click to collapse
Ok, I won't update!! Thanks!!!!
Hi all,
I am new to rooting (first attempted root) and working with Android, so I'm not familiar with all the jargon.
Earlier I attempted to root my Galaxy S5 (G900V) using jrkruise's guide (http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370). Following the guide closely, after running root.bat I used Odin as per the instructions at the end of the root.bat program. Odin gave me the notification that it was successful. So as per the instructions I attempted to turn on my phone, however it was stuck at the Samsung Galaxy S5 screen.
I have tried factory reset/format and clearing data cache to no avail. I have also tried putting a stock ROM back on via Odin and was met with this message.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please let me know if you have any other fixes that may be able to fix this type of problem, thanks.
UPDATE: I was able to solve my problem flashing the following ROM: https://www.androidfilehost.com/?fid=24438995911970571. This could be helpful for anyone with similar problems, so I will leave this thread up for anyone having troubles.
I was following the exact same directions and ended up with the same issue. Did you try the root process again and find out where you (and probably I) messed up while following the directions on your given link? Before rooting I purchased SuperSu Me, but never opened it. You seem to be a little ahead of me, but I'm also in your boat. I hope to find out your result.
jd13 said:
Hi all,
I am new to rooting (first attempted root) and working with Android, so I'm not familiar with all the jargon.
Earlier I attempted to root my Galaxy S5 (G900V) using jrkruise's guide (http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370). Following the guide closely, after running root.bat I used Odin as per the instructions at the end of the root.bat program. Odin gave me the notification that it was successful. So as per the instructions I attempted to turn on my phone, however it was stuck at the Samsung Galaxy S5 screen.
I have tried factory reset/format and clearing data cache to no avail. I have also tried putting a stock ROM back on via Odin and was met with this message.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_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> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please let me know if you have any other fixes that may be able to fix this type of problem, thanks.
UPDATE: I was able to solve my problem flashing the following ROM: https://www.androidfilehost.com/?fid=24438995911970571. This could be helpful for anyone with similar problems, so I will leave this thread up for anyone having troubles.
Click to expand...
Click to collapse
duece29203 said:
I was following the exact same directions and ended up with the same issue. Did you try the root process again and find out where you (and probably I) messed up while following the directions on your given link? Before rooting I purchased SuperSu Me, but never opened it. You seem to be a little ahead of me, but I'm also in your boat. I hope to find out your result.
Click to expand...
Click to collapse
Nope, I'm not entirely sure where I messed up in the first place. I haven't tried the root process again and intend to wait a while before trying again, I don't want to risk bricking/messing up my phone right now. Next time I think I'll be more careful following the instructions configuring the King Root .apk.
Well I went ahead and gave it a 2nd try and had success! Here are some notes that will help you.
1. Do factory reset so nothing is in the way and start up your cell, copy and past over KingRoot, & install it.
2. At this time also copy over Knox_Removal_SU_BB_INIT.D.zip (The actual whole .zip file) to a folder on your device
3. I "Prepared My Phone For Root" at the bottom of the steps and then went to the top and ran root.bat and then root2.bat. I did get hung up on the "Samsung Galaxy S5" screen again, but I looked at the command prompt screen that opens with root.bat and it was prepared for that situation and had directions for me to follow. I followed those directions and was able to boot up. At this point I went to the Play store, signed in, and installed the SuperSU Me paid app and followed the directions.
4. On Step 6 of the directions, it says to flash OK3, but I noticed the BPB1 file (and saw it was newer when the developer added it) and used it instead as it is newer software.
5. Everything else ran smooth, when you're asked to install the Knox Removal .zip, it's on your device, just find the .zip file itself and open/run it.
Hope this information helps and now I'm off to figure out how I can use the hotspot feature, given I have unlimited data. (That was my entire purpose for rooting)
duece29203 said:
Well I went ahead and gave it a 2nd try and had success! Here are some notes that will help you.
1. Do factory reset so nothing is in the way and start up your cell, copy and past over KingRoot, & install it.
2. At this time also copy over Knox_Removal_SU_BB_INIT.D.zip (The actual whole .zip file) to a folder on your device
3. I "Prepared My Phone For Root" at the bottom of the steps and then went to the top and ran root.bat and then root2.bat. I did get hung up on the "Samsung Galaxy S5" screen again, but I looked at the command prompt screen that opens with root.bat and it was prepared for that situation and had directions for me to follow. I followed those directions and was able to boot up. At this point I went to the Play store, signed in, and installed the SuperSU Me paid app and followed the directions.
4. On Step 6 of the directions, it says to flash OK3, but I noticed the BPB1 file (and saw it was newer when the developer added it) and used it instead as it is newer software.
5. Everything else ran smooth, when you're asked to install the Knox Removal .zip, it's on your device, just find the .zip file itself and open/run it.
Hope this information helps and now I'm off to figure out how I can use the hotspot feature, given I have unlimited data. (That was my entire purpose for rooting)
Click to expand...
Click to collapse
Great, thanks a lot! Haven't tried this yet, but I'm hopeful - will update thread after I try this (probably not any time soon, on vacation and don't want to brick my phone and spend vacation trying to fix it)
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Good one bud.... I can't get it last night but I'm glad u did[emoji106]
TwisT3DroiD_N920T
Threads of this nature do not belong in the development section. Please read the sticky titled "Rules for Posting in Development" before posting in there again.
THREAD MOVED
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
PhilPan said:
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
yes, as odin wipes your internal card and firmware..
PhilPan said:
Can this be odined over the rooted ROM, to return to stock... Before returning to store
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
just factory reset.....poof root gone!
galaxyuser88 said:
Here is the the stock T-Mobile newest firmware that was just pushed to everyone's phone that was not rooted.. >>> N930TUVU2API4
FYI::: Do not install this on your phone if you want to keep root<<<< YOU HAVE BEEN WARNED!!!!!
Otherwise Odin this if you want to be on the latest firmware..
Download Zip File -- use your favorite zip program to unpack it, and have fun..
Click to expand...
Click to collapse
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
ted77usa said:
Good one bud.... I can't get it last night but I'm glad u did[emoji106]
TwisT3DroiD_N920T
Click to expand...
Click to collapse
Throwing you in the mix as well. Please see my post above.
-BoneZ- said:
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
Throwing you in the mix as well. Please see my post above.
Click to expand...
Click to collapse
@-BoneZ-
U said that u tried to go back to stock from root? Meaning u have pgc firmware and u CAN'T use this PI4 firmware to go back to stock..... when u do that u stuck with newer Bootloader and u not able to root again.... if u need to go back then flash PGC original firmware.
EDIT:
If u already on PI4 then flash all at once.... BL AP CP CSC....
TwisT3DroiD_N920T
-BoneZ- said:
Tried flashing another stock ROM trying to get back to stock from root. That didn't work. Then I flashed this and am able to boot. But my mobile data icon is just 4G instead of being 4G LTE (or LTE), and I'm missing the WiFi calling button as well.
So, I probably need to flash the radios and everything with this. So, do I flash the AP first from the ZIP, then everything else after, or can I flash them all at once? Not an experienced ODIN user. Only used it a handful of times.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
Throwing you in the mix as well. Please see my post above.
Click to expand...
Click to collapse
Yes you must flash all parts of this to be on stock PI4 ROM. But remember that you will lose root and not get it back.
You sir are a life saver thank you so much i was stupid didnt read thru forums and tried to root on the latest update...this flashed via odin brought my phone back to life
ted77usa said:
@-BoneZ-
U said that u tried to go back to stock from root? Meaning u have pgc firmware and u CAN'T use this PI4 firmware to go back to stock..... when u do that u stuck with newer Bootloader and u not able to root again.... if u need to go back then flash PGC original firmware.
EDIT:
If u already on PI4 then flash all at once.... BL AP CP CSC....
TwisT3DroiD_N920T
Click to expand...
Click to collapse
galaxyuser88 said:
Yes you must flash all parts of this to be on stock PI4 ROM. But remember that you will lose root and not get it back.
Click to expand...
Click to collapse
Thanks, guys. Those were the answers I was looking for.
Hello I want to say thank you for providing the T-Mobile Firmware Package for restoring the Note 7 to its original state after a Rooting atampt botched up. I also had this problem but now restored the phone with the supplied firmware. Thank you.
I do have one problem though. The firmware supplied has the first update with the annoying Safety Recall statement in that hugh box while plug is inserted, pulled out and turned on. I like to know if you can supply the original firmware that the phone came boxed with or if you have some kind of way of getting rid of that stupid annoying big box message that pops up all the time.
And again thank you so much.
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
mikesx4911 said:
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
Click to expand...
Click to collapse
Have you tried this yet?
★[ROM] [STOCK] N930TUVU1APGC | 6.0.1 |… | T-Mobile Samsung Galaxy Note 7
http://forum.xda-developers.com/tmo...om-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
mikesx4911 said:
Ok I feel like a dumb ass,
This has to be the most complicated root, update I have ever seen. I accidently hit update earlier today which reduced my battery life to 60% I tried living with it today and it was driving me absolutely nuts I thought about taking the phone in and getting a damn iphone just because I'm tired of messing around with this phone..... I tried to root using post one however it keeps failing, I tried rooting using post 2 that also failed. I tried going back one firmware version that also didn't work, I tried doing the samsung smart switch recovery it asks for a code I tried the serial of the phone and model number that also didn't work. Can someone please explain either how to get root from the newest firmware or to revert back to a older firmware that dosen't have this stupid battery restriction. The information of my phone is below .
I'm tired of the battery restriction and tired of hitting okay I know my phone will blow up....
Samsung Note 7 Tmobile
SM-N930T
6.0.1
Build Number
MMB29M.N930TUVU2APK1
any help is appreciated as I am pulling out my hair...
Click to expand...
Click to collapse
If you can restore it back to stock. This thread may help. It's helping me.
Need help with Package Disabler 6.3 | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/help-package-disabler-6-3-t3494052
So I just tried to do the instructions from the ROM STOCK below however I get stuck on step 5 when I try to flash the "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRM WARE.tar.md5" it FAILS at
<ID:0/003> 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/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> adspso.bin
<ID:0/003> apdp.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth) <------------------------
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I than did a quick search had someone suggest checking "re-partition" that also failed with the same error. After rebooting the phone it wouldn't boot anymore and was stuck at "an error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software"
So I gave that a go and it tells me that the device is not supported after doing the model and serial number lol.
ConcernedCustomer said:
Have you tried this yet?
★[ROM] [STOCK] N930TUVU1APGC | 6.0.1 |… | T-Mobile Samsung Galaxy Note 7
http://forum.xda-developers.com/tmo...om-n930tuvu1apgc-6-0-1-deodexed-knox-t3461513
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
If you can restore it back to stock. This thread may help. It's helping me.
Need help with Package Disabler 6.3 | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/help-package-disabler-6-3-t3494052
Click to expand...
Click to collapse
mikesx4911 said:
So I just tried to do the instructions from the ROM STOCK below however I get stuck on step 5 when I try to flash the "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRM WARE.tar.md5" it FAILS at
<ID:0/003> 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/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> adspso.bin
<ID:0/003> apdp.mbn
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth) <------------------------
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I than did a quick search had someone suggest checking "re-partition" that also failed with the same error. After rebooting the phone it wouldn't boot anymore and was stuck at "an error has occured while updating the device software. Use the emergency recovery function in the smart switch pc software"
So I gave that a go and it tells me that the device is not supported after doing the model and serial number lol.
Click to expand...
Click to collapse
I was able to stop the 60% update with package disabler, but was also trying to go back to pgc update...getting the same fails as you. 3 Button into recovery and wipe everything then reboot. Should start you fresh to use the phone
Sent from my SM-G935T using XDA-Developers mobile app
ArmyofTracy said:
I was able to stop the 60% update with package disabler, but was also trying to go back to pgc update...getting the same fails as you. 3 Button into recovery and wipe everything then reboot. Should start you fresh to use the phone
Sent from my SM-G935T using XDA-Developers mobile app
Click to expand...
Click to collapse
If only it was that easy. As of now I can't even get into android it fails to boot. I cleared cache and factory reset and still won't boot. I'm sure I will have to flash now for sure from recovery or download mode. I think Samsung is ****n with us somehow to not let us flash.
mikesx4911 said:
If only it was that easy. As of now I can't even get into android it fails to boot. I cleared cache and factory reset and still won't boot. I'm sure I will have to flash now for sure from recovery or download mode. I think Samsung is ****n with us somehow to not let us flash.
Click to expand...
Click to collapse
The same thing happened to me. I re-flashed to the recent firmware I had installed originally (the one with the big ugly safety recall message from September). I flashed everything at once BL, AP, CP and CSC(I used the HOME_CSC_*.tar.md5 named file because I was returning to stock)
This site appears to be an archive for all Android devices. You can find the firmware of your phone using the model going back to launch date.
Download Firmware – Samsung Update
http://updato.com/firmware-archive-select-model
I think you will find this thread useful as well. It contains definitions and explanations on flashing and working with Odin. I just wish there was more information.
Good luck
Galaxy Note 7 All-In-One Information & A… | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/galaxy-note-7-one-information-answers-t3448689
Is there a way too get back to PGC? That was the one before the recall? I've tried flashing it and it fails
Sent from my SM-G935T using XDA-Developers mobile app
ConcernedCustomer said:
The same thing happened to me. I re-flashed to the recent firmware I had installed originally (the one with the big ugly safety recall message from September). I flashed everything at once BL, AP, CP and CSC(I used the HOME_CSC_*.tar.md5 named file because I was returning to stock)
This site appears to be an archive for all Android devices. You can find the firmware of your phone using the model going back to launch date.
Download Firmware – Samsung Update
http://updato.com/firmware-archive-select-model
I think you will find this thread useful as well. It contains definitions and explanations on flashing and working with Odin. I just wish there was more information.
Good luck
Galaxy Note 7 All-In-One Information & A… | Samsung Galaxy Note 7
http://forum.xda-developers.com/note-7/help/galaxy-note-7-one-information-answers-t3448689
Click to expand...
Click to collapse
<ID:0/003> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/003> Odin engine v(ID:3.1205)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Failed again... Tried both CSC files