I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
There is nothing that can set the custom binary to 0.
jc1337 said:
I'm wanting to unroot and return the number of custom flashed roms back to none. I've heard you can do this? I was planning on using this (http://forum.xda-developers.com/showthread.php?t=1342348) to unroot phone and then what would I use to return the custom rom count to none?
Click to expand...
Click to collapse
appdroid said:
There is nothing that can set the custom binary to 0.
Click to expand...
Click to collapse
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
jc1337 said:
I was following the unroot tutorial that I posted a link to in my first post and it just sits there and doesn't do anything after it gets to <ID:0/003> NAND Write Start!!
I watched a youtube video of a guy who was doing a visual step by step of that tutorial and he put his phone into debugging mode and I didn't because I didn't see anything about it in that post. Now my phone won't boot past that yellow exclamation point symbol... did I mess something up?
Click to expand...
Click to collapse
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Pirateghost said:
debugging mode has no bearing whatsoever in download or recovery mode....debugging mode is for the OS only....
Click to expand...
Click to collapse
\
do you have any idea why it might not be working then? I'm using the .tar from that post about unroot i727 and it's not working. What I'm doing is
1. running odin as admin
2. selecting pda (the SGH-I727-UCKJ2-k0nane.tar)
3. while phone is off pressing both volume buttons and then plugging in usb (putting it into download mode)
4. making sure odin sees my phone
5. clicking start
and this is what it does and it won't go any further
<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> boot.img
<ID:0/003> NAND Write Start!!
I've let it sit there for about 30 minutes without it moving any further?
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Pirateghost said:
do you comprehend what root actually is?
why are you trying to 'unroot' your phone?
did you have a custom rom on your phone before this?
Click to expand...
Click to collapse
I'm needing to return the phone to AT&T. Yes, I do comprehend what root is. And yes, I had a custom ROM on it before this.
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Pirateghost said:
sorry, i read this all the time about 'unrooting' your phone because so many people use the terminology incorrectly. this isnt about UNROOTING your phone as much as it is restoring STOCK...big difference. UNROOTING implies that you will be removing the su binary and superuser.apk from your /system, but leaving the rest of the system intact....regardless of what rom you are on.
are you using the samsung cable and not some other cable? i have seen bad cables do this. i have also seen front panel USB hubs do this, and you might have better luck finding another USB port to try
Click to expand...
Click to collapse
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
jc1337 said:
All I am really wanting to do is remove superuser stuff so if at&t checks they won't see it. An I am using the cable that came with the phone but I am using the front panel USB hubs so I guess I'll have to try plugging it into the back. Thank you very much for all of your help!
Click to expand...
Click to collapse
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Pirateghost said:
if you are on a custom rom, when you get that tar to load, you will be loading STOCK rom....not just removing superuser....that file is meant to restore your phone to STOCK, not 'unroot' it. root only applies within the OS. if you load a new OS that doesnt have root access, its not unrooting it, its loading a new rom.
Click to expand...
Click to collapse
I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
jc1337 said:
So, should I just try to find the stock rom online?
Click to expand...
Click to collapse
that k0nane.tar IS the stock rom.....
Pirateghost said:
that k0nane.tar IS the stock rom.....
Click to expand...
Click to collapse
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
jc1337 said:
Yeah, I noticed that I worded that wrong and changed it but I guess you'd already seen it. I'm just trying to get the phone so that I can return it to at&t, how would you do it if you were me?
Click to expand...
Click to collapse
with that exact file.
it will however, probably trip the download counter
Pirateghost said:
with that exact file.
it will however, probably trip the download counter
Click to expand...
Click to collapse
It is, I've gone from YES(4 counts) to YES(15 counts) I honestly have no idea what I'm doing wrong and why it won't go past NAND Write. I've been working on this for the past three hours though and they close in an hour an 15 minutes so I guess I may not make it tonight...
at this point I would be okay with just getting this phone working again.... I have to be up in a few hours and need to get to sleep
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
r3dp0is0n2012 said:
If you are under 30 days than return it to att... all you gotta say is that is getting hot and rebooting or just say you can't go pass the logo screen... if you are under the Samsung 1 year warranty just flast the stock firmware (search on xda on how to do it) and reset it to factory setting. Call Samsung center ask for a replacement or service ticket, send your phone and you'll get a working phone back in about 6 business days...
Hit the thanks button if I helped you with your question!
Thanks.
SkyIce 7.3 Speed
Click to expand...
Click to collapse
I am under 30 days, but I don't think that'll work if I can't get past the screen that says "Firmware upgrade encountered an issue. Please selecdt recovery mode in Kies & try again." and says I have a custom binary download of 16
hcyplr29 said:
You WILL trip the counter using that stock .tar. I recently went back to stock via the same method your using and I did not have root. I had no SU access for TiBu etc. So no signs AT&T would see other than seeing the counter bring tripped if they boot into DL mode to check. I have since rooted again to freeze bloat in TiBu. My question is did you extract the 7zip file properly and actually flashing a .tar file and not the compressed .zip?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah I did. I'm trying to flash the .tar not the whole zip
Related
What do i do?
I didn't brick my phone did I?
I accidently restored an old back up that i thought i created but apparently it was one from Verizon and now i'm stuck, i've tried flashing different roms via Odin with no success
all that comes up when i boot is
-- Bootmode=7 from cmdline...
--Movi_check Start..!!
checksum confirmation need checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
darrenbanks18 said:
What do i do?
I didn't brick my phone did I?
I accidently restored an old back up that i thought i created but apparently it was one from Verizon and now i'm stuck, i've tried flashing different roms via Odin with no success
all that comes up when i boot is
-- Bootmode=7 from cmdline...
--Movi_check Start..!!
checksum confirmation need checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
--movi_checking done!...
# MANUAL MODE #
Click to expand...
Click to collapse
sounds like a soft brick, no worries just odin EE4 stock package with PIT file and 'repartition' box checked in odin
blazing through on my 4G Droid Charge
anoninja118 said:
sounds like a soft brick, no worries just odin EE4 stock package with PIT file and 'repartition' box checked in odin
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
i just tried that... i always fail! i put the PIT file in PIT and the stock bloated EE4 in and... fail.
okay nevermind i got it to pass! thanks so much! i'm at the boot animation now!
darrenbanks18 said:
okay nevermind i got it to pass! thanks so much! i'm at the boot animation now!
Click to expand...
Click to collapse
nice... yeah sometimes it might take a try or two, or you have to use a different USB port, put battery in for the whole thing, etc
I restored and got this exact issue. Continually boots to the Android System Recovery no matter what I do/try.
Where would I get the PIT file?
I think I found a Stock EE4 md5 I can use but I have no clue on the PIT file...
I've spent a while looking around but not sure if I am looking at the correct stuff lol.
Any links would be highly appreciated!
xxJectxx said:
I restored and got this exact issue. Continually boots to the Android System Recovery no matter what I do/try.
Where would I get the PIT file?
I think I found a Stock EE4 md5 I can use but I have no clue on the PIT file...
I've spent a while looking around but not sure if I am looking at the correct stuff lol.
Any links would be highly appreciated!
Click to expand...
Click to collapse
http://db.tt/rJq2x0w and it goes in PIT section of odin and check the 're-partition' box
blazing through on my 4G Droid Charge
Just did the same thing pretty easy fix just get the pit http://www.mediafire.com/?kk62yxpp8b8x918 and the stock file http://www.multiupload.com/LNTF3IKJ21
Make sure the drivers for your phone are installed...that youve connected the phone to the pc before. If you have a newer PC dont use the usb3 slot. Unplug battery from the phone do not connect yet...Open Odin Place the pit in pit section the stock in pda check off repartition. Hold the volume down and plug in the phone to usb. Once odin sees the phone upper left youll see a yellow block replug the battery. (I take my sim card out when I flash dont know if its needed) then click start. After its done unlpug for the boot. Sould be at stock. Replace sim and renable the account.
Just had this problem. Solution worked flawlessly thanks a ton!
zdiddy14 said:
Just had this problem. Solution worked flawlessly thanks a ton!
Click to expand...
Click to collapse
Perfect solution ...glad I click on thread ....I didn't the dummy with the sim card though..gotta stop by VZw...to get a another....
Wow everyone having this issue today =-O
Sent from my SCH-I510 using xda premium
Thank You!!!!!!
Guys , i wanted to thank u for the info in this thread. it helped save my phone.
Hey guys .. im having this issue now , and the solution isnt working for me .. Odin doesnt fail ,it passes , but then just goes back to giving the error in the OP when i boot . Ideas?
are you putting the battery back in before you start to flash? I have seen it pass but still be screwy if not. Also you may want to try to download the files again could be something wrong with the download.
If none of that works, try going to ed2 instead of ee4.
why wouldnt you just do the EP4 full odin instead of any past versions? Odin the EP4 full file and use the PIT file and check repartition in Odin and uncheck the others....when flashing leave your battery in...IE with phone off...hold volume down then plug USB cable to phone
chiahead52 said:
why wouldnt you just do the EP4 full odin instead of any past versions? Odin the EP4 full file and use the PIT file and check repartition in Odin and uncheck the others....when flashing leave your battery in...IE with phone off...hold volume down then plug USB cable to phone
Click to expand...
Click to collapse
Well since he tried ee4 as in the OP and it didnt work I figured instead of messing with new, back was a good start
So, this happened recently, and I fixed it. Link: http://forum.xda-developers.com/showthread.php?t=1735119
Well, outta no where, same basic issue, but with a twist.
This afternoon while I was asleep my GTab rebooted. It came back to the "Samsung Galaxy Tab 7.0 Plus" splash screen and is stuck. I *can* get into download mode, and I can almost get into recovery. When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
Twist:
So, knowing what I did last time, I installed Odin and the Samsung drivers on my POS computer at home, booted into Download Mode, and did the "PDA" option with the correct FW (same as I used last time for the T869 from SamMobile, I saved all the files). It runs through just fine, gets to the end and the Tab reboots. It then goes into recovery and and does a few things (I believe it said it was deleting the cache and a few other processes). Then, lastly, it again says:
"# Manual Mode #
-- Updating Application
... followed by a reboot, and back to hanging on the boot logo.
Any ideas?!? Ironically, I put it on CL today to see if I can sell it for enough to cover a Nexus7. I woke up to an offer, and a bricked Tab. Figures.
Any thoughts/help are greatly appreciated. The sooner the better. lol
Is it possible that I need to flash a good recovery in Odin? If so, what's the procedure. and can someone link me to the one I would need for the US TMobile 4G version of the GT7+?
Also, since flashing the stock FW isn't fixing anything, and it seems like a possible Recovery issue, a friend at work is suggesting I choose the option in Odin to delete the partitions.
Thoughts??? (quickly)
Damn dude, again?
I think there is 3 or 4 threads about this on this forum and same amount on 7.7 forum. None come to a cause our solution, seems like people repeats some procedures and out of nothing it works again.
When it happened to me a let its battery drain fully to the point it won't turn on anymore let it this way for some time. Then fully charged, this is a little harmful to your bat, for the record. Then try to turn on, it will take some time but eventually it could enter on the system.
I think the data partition got corrupted.
Sent from my GT-P6210 using Tapatalk 2
Yup.
So, I tried the option in Odin to re0make the partition, and every time I try it fails with an error of "Can't Open Package" (or something along those lines).
I have reinstalled the FW through Odin no less than 10 times, nogo. The first time I open recovery after flashing, It says it is installing a package, clearing cache, etc, and the last line always says "-- Updating Application". After 10-15 seconds, that goes away and it reboots only to hang on the GT7Plus splash screen again. Then, any time I go into recovery after that first post-Odin instance, if says:
"# Manual Mode #
-- Updating Application
Should I be trying to reinstall Recovery? If so, what do I use (link)? Also, how do I do that in Odin...
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
leodfs said:
I believe that for use remake partition you have to provide the pit file if your stock does not have it.
Anyway I did that also about 3 times, providing the pit and the md5, they flashed ok, but the problem was the same. Did you tried the battery thing? Some guy give a tip to start with the usb plugged.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Where was that tip? Link?
Also, any one have that .pit file I can try with?
http://forum.xda-developers.com/showthread.php?p=28574760
Sent from my MB525 using Tapatalk 2
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
statuzz said:
Hey buddy..
Which fw u using? T869 came shipped with 2 different, search for both of them and try each one...don't use repartition without the correct pit file...
Maybe not here but I google sgh-t869 factory and found a website with both tar
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I'm not sure which file it is that I'm using, I'll have to look at home in a couple of hours. This happened to me a few weeks ago (link in original post), and I flashed this FW with Odin and it recovered, and has been fine since (till now), so I know it's at least a usable FW. I'll try to find the other one today.
I just tried finding the stock pit file for the TMo SGH-T869, but I can't find it. Anyone have a link to it by chance? Also, once I get it, what do I do (options to choose) in Odin to flash it?... and do I do it at the same time as the FW?
Thanks for any help! I was really hoping to sell it in the next day or two to fund the Nexus7, so now I'm really frustrated.
ETA: Also, I let it completely die, to the point it wouldn't boot. Then charged it for a bit and booted. Same issue.
I think that if u find the pit file they should be flash at the same time...fw in pda and pit in phone...(this need to be check to confirm) after flashing.. reboot into factory recovery wipe everything and try to boot
Hopefully u fix that today
Sent from my Galaxy Nexus
When it happened to me, i flashed the pit first and at the same with stock with re partition checked, didnt help. I did everything that I could find and I feel like it only worked again by itself
You can look every single thread of this exact problem, the ones that got it back working can't really say how, they flash everything many times and it suddenly works.
The good things are that flash the stock ones don't increase you flash count, and as long as you can enter download mode you are not really s#%
Sent from my MB525 using Tapatalk 2
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
VisualOddity said:
Thanks for the help...
Anyone have a link to the .pit for this model (T869)?
Also, I had a thought. When I go into Recovery, I get the following and then it reboots again:
# Manual Mode #
-- Updating Application
1. Is it possible that recovery is hosed, and overwriting it with a fresh version will allow me to wipe the device, set to factory and then boot? Maybe this is the issue?
2. Is it even possible to just flash a fresh copy of the recovery over whatever is there (or replace it)?
2.a. If it is possible, what file should I use, and do I do it though Odin? Anyone have a link to what I should use?
Thanks :good:
Click to expand...
Click to collapse
The problem is that there's is not development for t869 so there's not much to look for...just factory images and root method
Sent from my Galaxy Nexus
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
VisualOddity said:
Can anyone link me to the proper pit file? Also, in the linked thread a few posts back, there are a couple of files, will those work for this?
Can someone post the proper pit file for me so I can repartition? I'm doing this on my wife's phone because my internet at home is down till tomorrow...
Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad?
Click to expand...
Click to collapse
i think u should forget about the pit file, couz the firmware have the pit repackage with the tar, im gussing u will only need the pit file in case u want to change the phone partitions, try to get those 2 fw and try them :good:
That's why I'd like the pit file, so I can check the option in Odin to re-partition.
So, I have internet at home now. I have now tried again letting it completely die, then completely charge, same issue. I have also tried 2 different versions of the SGH-T869 firmware.
Any thoughts?
Also, given what I have done so far, I posted this yesterday, any thoughts?
"Lastly, recovery. Since when I go into recovery it says "manual mode" then reboots, can I replace recovery only? Then I can wipe and whatnot in it and maybe that will do the trick. If so, can someone link me to the proper recovery and tell me how to do it in Odin? What happens if I watch the FW flash, then right after it completes the recovery portion, I unplug it? Bad? "
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
chrisrotolo said:
Yes. Unplug is bad. Possibly fatal. you should be able to.find a stock recovery.img in a stock Odin.tar, flash it with heimdall. Recommend factory reset beforeand after doing so.
I dont know about tmobile tabs but international ones look to apply CSC files after displaying that manual mode message. Perhaps something has gone awry with a CSC,etc.
Click to expand...
Click to collapse
Thank You. A few questions:
Would that stock recovery.img have to be model specific. i.e. for the SGH-T869, or could it be from any GT 7 Plus (or is it generic on all devices with HoneyComb)? I *think* from experience it has to be T869 specific, but it's worth asking.
Also, about Heimdall, where do I get that, and how do I use it to flash? I've heard of it, but never used it.
Lastly, about the CSC files. That makes sense seeing as what it's doing, so that *could* be the whole issue. How can I overcome that? Can I download and flash those files somehow? Do you have a link to them?
Thanks for the help everyone. I'm hoping that in doing all this, maybe whatever ends up fixing this will be a guide for everyone else having the issue...
OK, I saw a couple of you guys mention the 7.7 people having this issue, so I went there to research. If I am reading right, it *sounds* like this could be a solid mix of a data system being corrupted, and the stock recovery (Samsung e3?) being bad.
Someone mentioned that you can pull the stock recovery.img from a the firmware, make a .tar with only that, then flash that. Once that's done you can do a full wipe in recovery, flash the full FW, and hopefully be back in business.
I want to try this, and if it works, maybe we will have a proven solution for the people getting this issue. However, not only have I never created a .tar, I have especially never created a flashable .tar, so...
What do I do? Other than pulling the recovery.img from the FW, how do I do this?
Can someone point me in the right direction?
I updated the S3 Bootloader Unlocker and for some stupid reason i decided that i wanted to relock and unlock the bootloader.
I relocked it to find out that it didnt give me the option to unlock again.
Then i proceeded to reboot the phone and low and behold, The verizon screen of death popped up.
The screen im talking about is the one that says:
"System software not autorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Is there a way to reflash the bootloader? Odin perhaps?
I just need a little guidance on getting me in the right path. Thanks all!
If you can boot to download mode still, you can Odin back. That's the great thing about Odin, doesn't matter what state your phone is in as long as you can get to download mode, it'll take care of the rest.
Vol Down + home key + power - do this while booting.
I assume you did what several of us did and used the ez-unlock tool? The update for that app actually is broken temporarily, mmeff said he's gonna fix it later tonight. Here is an old v1.2 I managed to find that works flawlessly.
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
I did a few more searches. I found the soft brick fix page. I just reflashed everything.. But everything is lost......
Im gonna shoot myself.. Had tons of pictures from my daughters first birthday on there.. ALL GONE!!
Didnt think it would flash the internal storage.. FML
Actually it sounds like what he did was re lock his bootloader with a custom kernel on the phone. Because the update broke the unlocking part of the app his bootloader stayed locked and with a custom kernel on the device the subsequent reboot caused it to fail Verizon's signature check.
OP: Use the stock root66 Odin file in the stickies to restore stock.
iSpyder said:
I did a few more searches. I found the soft brick fix page. I just reflashed everything.. But everything is lost......
Im gonna shoot myself.. Had tons of pictures from my daughters first birthday on there.. ALL GONE!!
Didnt think it would flash the internal storage.. FML
Click to expand...
Click to collapse
I'm pretty sure that step 8 in that guide is what erased your internal sd card. That's where it says "Nand Erase All." That's tough that you lost all your pics.
JBO1018 said:
Actually it sounds like what he did was re lock his bootloader with a custom kernel on the phone. Because the update broke the unlocking part of the app his bootloader stayed locked and with a custom kernel on the device the subsequent reboot caused it to fail Verizon's signature check.
OP: Use the stock root66 Odin file in the stickies to restore stock.
Click to expand...
Click to collapse
This is what i did. I have lost all data that was on there. I even lost the CWM backups that were saved the the internal storage. So i couldnt flash back to any of those. Starting from square one.. and it sucks.
Edit:I found an old back up on my desktop. Flashed it and it was going really slow. I downloaded a rom, and flashed that. Then it took me right back to the VERIZON screen saying there was unauthorized software again.. What am i doing wrong? The bootloader app says the boot loader is unlocked.. maybe ill try the APK file from this thread instead of the market.
iSpyder said:
This is what i did. I have lost all data that was on there. I even lost the CWM backups that were saved the the internal storage. So i couldnt flash back to any of those. Starting from square one.. and it sucks.
Edit:I found an old back up on my desktop. Flashed it and it was going really slow. I downloaded a rom, and flashed that. Then it took me right back to the VERIZON screen saying there was unauthorized software again.. What am i doing wrong? The bootloader app says the boot loader is unlocked.. maybe ill try the APK file from this thread instead of the market.
Click to expand...
Click to collapse
Yea, unless EZ Unlock was updated again today you need to use EZ Unlock 1.2 to properly unlock.
SlimSnoopOS said:
Yea, unless EZ Unlock was updated again today you need to use EZ Unlock 1.2 to properly unlock.
Click to expand...
Click to collapse
I think that was the problem. The app updated and is thinking that the boot loader was still unlocked so i couldnt unlock it again even after odin.
I just reflashed stock rooted with odin. downloaded unlock apk and rom manager. making back up of stock rooted. looks like it booted back to home screen! TIME TO ROM IT UP AGAIN!
EDIT:
TechSavvy2 said:
If you can boot to download mode still, you can Odin back. That's the great thing about Odin, doesn't matter what state your phone is in as long as you can get to download mode, it'll take care of the rest.
Vol Down + home key + power - do this while booting.
I assume you did what several of us did and used the ez-unlock tool? The update for that app actually is broken temporarily, mmeff said he's gonna fix it later tonight. Here is an old v1.2 I managed to find that works flawlessly.
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
Click to expand...
Click to collapse
I LOVE YOU FOR PROVIDING THAT APK!!
Thank you
TechSavvy2 said:
If you can boot to download mode still, you can Odin back. That's the great thing about Odin, doesn't matter what state your phone is in as long as you can get to download mode, it'll take care of the rest.
Vol Down + home key + power - do this while booting.
I assume you did what several of us did and used the ez-unlock tool? The update for that app actually is broken temporarily, mmeff said he's gonna fix it later tonight. Here is an old v1.2 I managed to find that works flawlessly.
apk
Click to expand...
Click to collapse
Thank you so much for that apk.
Its been updated to 1.4. I dont know if i want to do even that one until the bugs are taken care of.
Thanks again to everyone that helped me get my phone back up and running.
I got my rom flashed. Apps installed. All is good in this world again. minus the losing pictures and stuff.
I upgraded to 1.4 before seeing this. Do I just uninstall EZunlocker completely and then flash 1.2?
this time back up your pics to the cloud!
im late to this thread but there is a guide in the development section that would of saved you alot of hassle as all your issues are explained there...hmmm I wonder who wrote that?
This was a really useful thread. Learned a lot, prompted me to check my backups and moments after reading the thread, I got an EZ-Lock update pushed to my phone (v. 1.4). Is this the one that addresses the bug?
iSpyder said:
I did a few more searches. I found the soft brick fix page. I just reflashed everything.. But everything is lost......
Im gonna shoot myself.. Had tons of pictures from my daughters first birthday on there.. ALL GONE!!
Didnt think it would flash the internal storage.. FML
Click to expand...
Click to collapse
I suggest you to download dropbox and activate the auto upload of pictures and video ( it should be active by default...) you can pick between upload only over WiFi to save your data plan or both WiFi and mobile.
It saved me and my pics many times..
Sent from my SCH-I535 using xda premium
iSpyder said:
Its been updated to 1.4. I dont know if i want to do even that one until the bugs are taken care of.
Thanks again to everyone that helped me get my phone back up and running.
I got my rom flashed. Apps installed. All is good in this world again. minus the losing pictures and stuff.
Click to expand...
Click to collapse
What the heck is he even updating in the ez unlock app? All it does is copy aboot.
piiman said:
What the heck is he even updating in the ez unlock app? All it does is copy aboot.
Click to expand...
Click to collapse
He has a changelog...
v1.4
hotfix for last issue. Bootloader checking is disabled for the time being, so all you will see is UNKNOWN for the status. Fret not, as unlocking and relocking are still working. Sorry about all this, will rectify ASAP. I recommend using 1.2 from the Rootzwiki linked thread in the description.
v1.3
Use SHA-1 to check bootloader status (much more reliable)
removed sound
Bad hash value....???? Help pls?
Hey guys,
Im new, but I am stuck. I am a victim of this as well. I am trying to use the instructions in the [HOW-TO] Unbrick your soft bricked Galaxy S III thread but Odin says that the VRALF bootchain file has a bad MD5 Hash value. The original link is bad, the file does not download. I was able to download from the mirror and the MD5 for that file does match the download, but for some reason Odin doesnt like it....
Im stuck. Can someone send me a file they have used? I just got this phone today....
Any help would be VERY appreciated.
Firstsage said:
Hey guys,
Im new, but I am stuck. I am a victim of this as well. I am trying to use the instructions in the [HOW-TO] Unbrick your soft bricked Galaxy S III thread but Odin says that the VRALF bootchain file has a bad MD5 Hash value. The original link is bad, the file does not download. I was able to download from the mirror and the MD5 for that file does match the download, but for some reason Odin doesnt like it....
Im stuck. Can someone send me a file they have used? I just got this phone today....
Any help would be VERY appreciated.
Click to expand...
Click to collapse
Whats the error that Odin is giving you?
apacseven said:
Whats the error that Odin is giving you?
Click to expand...
Click to collapse
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2- (2).md5 is invalid.
<OSM> End...
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Boot into recovery and do a factory reset.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I've tried that a few times already. No luck thus far
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
What baseband are you on ?
jlyle said:
What baseband are you on ?
Click to expand...
Click to collapse
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
ImBarone said:
i was on vrbmf1 when i got it back but ive been trying to flash back to the stock to hopefully get out of the "unauthorized software" screen. when i tried to wipe system and data and then restart from the stock recovery menu, i got an error message saying that the directory /system didnt exist, yet ive tried flashing back to stock twice and both processes finished through odin
Click to expand...
Click to collapse
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
jlyle said:
Are you 100% sure you was on MF1 and Verizon did not ship it to you with 4.3.
If you was on MF1 Odin should flash fine and resolve any issues. If you was on 4.3 than you have issues if you ran Odin
Click to expand...
Click to collapse
1000% sure that it was 4.1.2 and MF1 because it was trying to push an OTA update that i kept canceling. should i attempt reflashing through odin again? and if so could you link me to something specifically i should flash and possibly some instructions because ive been without a phone for 2 weeks and wouldnt like to wait til october for another one....
thanks
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
prdog1 said:
If it was fixed or replaced by Samsung they usually update to newest software before returning it. If it was on 4.3 and you tried to unlock it is now bricked beyond our ability to repair at this time.Can't unlock, flash custom recovery or downgrade to 4.1.2 or lower or it will brick. If was on 4.1.2 just need to Odin stock tar.If it hangs then a Factory reset in stock recovery will usually fix it. Need more info on what build you were actually on when started.
Click to expand...
Click to collapse
im completely sure it was NOT 4.3 though. it flashed fine when i ran this http://forum.xda-developers.com/showthread.php?t=2046439 i just forgot to flash the bootloader unlock through recovery so then i tried reflashing stock and now im here. and where could you point me in the direction of a stock tar and some instructions because ive been using the ones on the original thread i linked with no luck
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/?fid=23134718111254196
http://forum.xda-developers.com/showthread.php?t=2332825
prdog1 said:
Remove .tar from zip and flash in Odin. If was on MF! it should fix with no more than a factory reset in stock recovery. Then run Beans casual to reroot and unlock.
http://www.androidfilehost.com/user/settings-dev-files.php?action=show-files&flid=7111#
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
ImBarone said:
the androidfilehost link is giving me this
"Access Denied
Sorry!
It looks like you don't have permission to access that folder. Make sure the url you are trying to access is correct.
http://forum.xda-developers.com/showthread.php?p=48799846
If you feel this is in error, please contact us."
Click to expand...
Click to collapse
Try again with this link.
http://www.androidfilehost.com/?fid=23134718111254196
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
im currently flashing the root66.tar through odin hopefully my problem will be solved afterwards
jlyle said:
Do you get a "PASS" when you run Odin ?. Run the tar from PR and all should be good (Iv ran it many times HA)
Click to expand...
Click to collapse
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
ImBarone said:
ok so i no luck with the root66.tar file im going to try the other one now. should i be checking the nand erase all box?
Click to expand...
Click to collapse
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Your in download mode right ? HA / just checking
ImBarone said:
Would anybody be able to provide any insight on how i could fix my s3 that appears to be stuck on boot? i received my warranty fixed device from samsung today and upon rerooting it, i forgot to unlock the bootloader i then went to the "Verizon has detected unauthorized software" screen. After which, I followed this thread http://forum.xda-developers.com/showthread.php?t=1840030 hoping to get back to stock. But after following these directions, the phone boots to a Samsung custom (Unlocked) screen and then it goes to the galaxy s3 boot screen and remains there, if anybody could provide any assistance, that would be awesome. I'd just hate to get laughed at if i bring it into a verizon store. thanks and happy holidays.
Click to expand...
Click to collapse
Boot into download mode and on the screen where the option to continue or restart phone, choose to restart your phone. This worked for me just this morning, for some reason it bypasses the check.
Sent from my SCH-I535 using XDA Premium 4 mobile app
jlyle said:
Leave everything in odin as is..dont check or uncheck anything
Make sure u put in PDA
Make sure you have a solid connection with cable .. that will cause issues too
Click to expand...
Click to collapse
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Odin will reboot your phone.. are you getting Pass in Odin ??
ImBarone said:
im trying with the stock MF1 file now. left everything checked normally as it always is in odin lets see how this goes. would it be common for a boot to hang on the "Samsung Galaxy s3" screen coming off of odin?
Click to expand...
Click to collapse
Yes. It is common for it to reboot but bootloop. Pull battery and then boot into stock recovery and factory reset. Then it should boot.
Sooooo, I tried by myself to root my s8+ from att and couldnt do it. So i tried oneclickroot.com and payed like a idiot to get it done and they did but now HATE it and would like to go back to factory. I have tried EVERYTHING it seems like and always get errors with odin! either its a FAIL! (Auth) error or something else. What in the world do I need to do to get back to factory!??? SM-G995U and says build # nrd90m.g955usqu2bk5
imadrunkie said:
Sooooo, I tried by myself to root my s8+ from att and couldnt do it. So i tried oneclickroot.com and payed like a idiot to get it done and they did but now HATE it and would like to go back to factory. I have tried EVERYTHING it seems like and always get errors with odin! either its a FAIL! (Auth) error or something else. What in the world do I need to do to get back to factory!??? SM-G995U and says build # nrd90m.g955usqu2bk5
Click to expand...
Click to collapse
do i need to go into supersu and go down to full unroot?
I would think just flashing the OEM firmware with Odin3 would reset phone back to factory would do the trick.
Sent from my SM-G955U using Tapatalk
just reread your post and you did use Odin but was that the regular version or did you try the modified "prince consey" ( probably spelled that wrong)?
RebelShadow said:
I would think just flashing the OEM firmware with Odin3 would reset phone back to factory would do the trick.
Sent from my SM-G955U using Tapatalk
just reread your post and you did use Odin but was that the regular version or did you try the modified "prince consey" ( probably spelled that wrong)?
Click to expand...
Click to collapse
thats what i have been trying but getting errors left and right. always get the FAIL! (auth) error or mismatch error. All im doing is going into download mode and then adding files and then start...and always get errors. Ive tried mutply att factory files and all same thing. tried like 10 versions of odin lol even the mod version prince one
Are u sure you're flashing the correct firmware for your phone?
Go to sammobile and download a fresh firmware for your phone type and try flashing again.
And by the way did they (oneclickroot) or yourself flash any other firmware whether custom or not in the phone after rooting?
Or have you or them updated the bootloader and modem?
gideonlfc said:
Are u sure you're flashing the correct firmware for your phone?
Go to sammobile and download a fresh firmware for your phone type and try flashing again.
And by the way did they (oneclickroot) or yourself flash any other firmware whether custom or not in the phone after rooting?
Or have you or them updated the bootloader and modem?
Click to expand...
Click to collapse
nope just asked and they say no bootloader updated, but i have the option of 19.99 for them to go back to stock smh.. now when looking for a working ATT stock firm do i look for my current baseband version?
So what happened?
I'm sure your bootloader got updated. Have to find firmware with same bootloader. Something that has u2...
Try this : https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033