EDIT: Man I'm stupid!!!!
I forgot to Relock my bootloader before running RUU. Got it figured out now. I'll just leave this here in case anyone is as stupid as me, they'll be able to self-diagnose!
And for those that don't care to search, the command is
Code:
fastboot oem lock
Thank's for looking!
ORIGINAL POST:
Hello all. I noticed a couple days ago that my beautiful new evoLTE had quite a few really bright, irregular pixels. I tried to ignore it, because I've done so much over the last two weeks making it my own, that I really didn't want to take it back for a replacement. You can only really see them on light colored, or white backgrounds with the screen at an angle.
Try as I might, I just can't stop focusing on them. So I decided I would take it back. I purchased it through Best Buy, and I also got their Black Tie service, and being that it is a hardware not software problem, I didn't think it would matter, but I decided to unroot and relock the bootloader just in case anyway.
I had flashed viperROM, so when I went to Software Information to find out which RUU to download, I couldn't find the information I needed. I opted for 1.13.651.1. RUU was unable to verify the ROM image and failed, so I tried 1.12.651.2 instead. No luck. I thought maybe a factory restore first would solve the problem, so I booted into TWRP and did just that. After it finished, I rebooted, but it just hung up on the viperROM boot screen. Waited for 15mins, just in case it needed that much time, but it never did anything but flash red....
So I rebooted into recovery and restored the first nand I made of the stock rom right after rooted and flashing TWRP, before I first flashed viperROM.
Rebooted no problem. SuperUser was back, obviously, so I removed it again, rebooted, and tried to RUU 1.13.651.1. again. This time I could actually check the Software Information screen to verify the version.
The process got a little further this time, actually rebooted my phone and sent the rom to it, but it fails every time it tires to verify the signature. I get an ERROR [155].
This is what the ReadMe says about it:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
So I tried to download RUU again. The MD5 checked out on the original, so I didn't think it would help, but I tried it anyway. The new file's MD5 checked out as well, but it still failed at the exact same part.
Does anyone have any ideas what I might be doing wrong? I have checked that drivers are loading in Device Manager when the phone reboots into bootloader. And I think I have the right drivers, they are the same ones I installed to run the one click root bat. I'm completely stumped. I'm about to try and reroot and unlock the bootloader again at it is, then try to run RUU again to see if that fixes it, but after that, I'm completely out of ideas. Anyone have any suggestions for me??
okay so i must have messed something up. i have a tmobile htc one. rooted just fine. tried to flash over liquidsmooth rom. definitely not liquidsmooth. still stock. and now apps dont start. google play store doesnt start. tried flashing a gapps file that was supposed to fix that. it did not. anyways im just going to unroot and go back to fully stock rom for now and read up more before trying again. the problem is nothing is working when trying to unroot. everytime i try to restore to a backup it just reboots into recovery. same thing if i try to ota update to 1.27.531.11. i also, before this, sent the code to relock the bootloader. that probably has something to do with it. but after sending the code again to unlock it like i did initially. it says failed. i try flashing to recovery.img and it says failed. i need some serious help here. not sure what info i need to give but let me know if theres anything else needed
can anyone help me wipe clean and start over from scratch? please
okay so i got the phone function normally again with bulletproof kernel running. definitely not as good as stock rom. first thing i notice is tearing while scrolling through lists. anyways my play store still isnt working. ive been googling and searching on here for HOURS trying to find a solution. the only things ive found are "enable" it. done. wipe data and cache from app. done. reboot phone. done. reinstall rom. done. still does not work! can anyone help me get my store working again
I got a Note 2 yesterday, bought it used. I turned it on, everything seemed normal. I took it to Verizon, they activated it for me in the store, and while I was there, the lady activating it also accepted an OTA software update. I have no idea what version I was on, or what the OTA was. When I got home, the phone shut down as part of the OTA, and everything appeared normal. The little android with a box screen came up, cycled through the progress bar, etc. However, when it was done, the phone rebooted, and froze on the "Samsung Galaxy Note II" screen. I gave it a while, then battery pulled, tried everything I could think of. Couldn't get into the recovery menu. It would get to Odin, but that was it. Anyways, after a very stressful night working on it, I found the thread here:
http://forum.xda-developers.com/showthread.php?t=2040264
I downloaded the "Alternate Restore Mirror" link, put the phone in download mode, and installed from Odin on my computer. The phone booted up, everything worked beautifully.
Then, tonight at work, I checked for software updates, and was informed that there was an available update. I downloaded and installed it(I think the phone said it was 7MB?), and THE SAME THING HAPPENED. Phone is frozen on the "Samsung Galaxy Note II" screen. I plugged it into my laptop, put it in download mode, and did exactly what I did this morning. Odin says everything was successful, and reboots the phone. But it hangs on the "Samsung Galaxy Note II" screen, no matter what I do. I've tried searching, and followed every guide on how to unbrick it I can find, but no matter what software package I use, it fails on "sboot.bin". The only one that will work and not fail is the "Alternate" in the link above, but when I use that one I still have a bricked phone.
I -really- need advice here, guys. I'm in way over my head.
So, a little more information. If I have a ROM that doesn't have an sboot.bin attached to it, it will write just fine and not show any errors. However, the phone will hang up on the "Samsung Galaxy Note II" screen. If I write a ROM that tries to write sboot.bin, it fails. Every time.
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Jiggabitties said:
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Click to expand...
Click to collapse
I did. When it tries to write either image, it fails on sboot.bin. Every image that includes sboot.bin fails on sboot.bin so far. I -really- don't know what to do.
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
viper31573 said:
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
Click to expand...
Click to collapse
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
skiahmutt said:
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
Click to expand...
Click to collapse
not sure what else to tell you that would help
viper31573 said:
not sure what else to tell you that would help
Click to expand...
Click to collapse
Well, the best place I can think to start is to nail down exactly what's happening, then try to figure out WHY it's happening. Once I know the what and why, the solution should be apparent. While I'm not against someone chiming in with a fix that works but I don't understand, I'm here to learn, and would like to come to a better understanding of the issue.
First: what is sboot.bin?
Second: do I need a specific sboot.bin for a specific ROM?
Third: what can cause sboot.bin to fail?
Fourth: is there a way to push just sboot.bin to the phone through Odin or other software?
Fifth: am I fixating on sboot.bin when it's not my issue?
Sixth: did you really read my whole post and get to this point? Wow, thanks! I appreciate you taking the time to try and help me, folks like you are what make the community so strong!
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
viper31573 said:
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
No worries. Thanks for the effort at least!
Okay, a bit of an update... I unzipped and removed sboot from a couple of the ROMs I have, and they flashed successfully, but the phone still hangs on the "Samsung Galaxy Note II" screen... I feel like I'm on the verge of figuring this out, I -know- it's got something to do with sboot now.
Can I write JUST a bootloader to the phone without writing anything else? If so, how?
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
also try flashing the pit file.
mike7728 said:
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
Click to expand...
Click to collapse
I think it was the 4.3 update. So, what's the knox bootloader, and what ROM can I flash to the phone that'll work with the knox bootloader?
Guess I'll start at the beginning so nothing gets left out. I was rooted on OC1, downloaded FlashFire to update to OF1 . Flashed it, the phone rebooted and got stuck on the black Samsung Custom screen. I've tried to flash tar files of OC1 and everytime I put it or any kind of tar file in the AP slot of Odin, Odin becomes unresponsive and closes. I tried to load up the SD Card with OC1 and OF1 Roms and tried to flash those to see if that would do anything. The phone always says (in recovery at the bottom of the screen)- Manual mode, applling multi-csc...applied the csc-code-vzw. Then says below that, remove failed file '/system/csc_contents'(read-only file system. At the top it says Android system recovery so I'm assuming that's custom, I know its not Safestrap so I guess its FlashFires recovery? Anyway, when I try to flash a ROM it says,E:footer is wrong E:signature varification fail. I'm at a loss as to how to get the phone back, if its possible. I was always told that if the phone powers up, its recoverable, just not sure how. Any advice would be awesome, I've been messing with this thing since early yesterday and I really need my phone back!
....It seems as though I have stock recovery. Is there a way to flash a recovery through Odin?
have you tried using ODIN with I545_Downgrade_tC1.tar from [How-To] Update to I545_OF1 - 5.0.1 and KeepRoot by muniz_ri? ODIN tends to get stuck for a bit while loading the tar, as it is reading a 2gb file. You should probably leave ODIN alone for a few minutes after loading, and if it still has problems, maybe re-download ODIN or use a different comp.
Thanks for the response. I did try that file, actually that was the first one I tried but it didn't work. Actually while I was typing this I downloaded another Odin, put the OC1 neutered tar file and did what you said, left it sitting in AP. After 5 mintues or so it worked!!! I've been messing with this phone going on 3 days now and as I'm typing the phone has rebooted and now is in the setup wizard!! Thanks for the reply!
So I screwed up pretty bad....
I have done so many flash's / reboots over the years that I just went through it too quick and wiped EVERYTHING off the device. I am trying to install the factory rom in TWRP now but it is not working...when it trys to install it is saying no MD5 found..it completes the install and then when it asks for a reboot it is saying no OS found!
I don't know what to do...any advice or a thread anyone knows of that can help me get my phone back to a working order???? I have never made such a stupid mistake before.
Or is there a recovery somewhere I can get that will restore the phone to a usable manner so I can at least flash a fresh rom?
Never mind all! I stumbled on someone else's thread and after their experience I ended up rebooting anyway and it actually booted totally normal...Lesson learned about taking my time and double checking I still have a recovery!