Is there a way to remove the "Custom" message with the unlocked lock when booting up the GS3? Reading around, people seemed to indicate this was related to flashing a custom recovery. However, I only flashed a modified stock rom without flashing a custom recovery and I am receiving this screen when booting up.
I saw one person suggest flashing the stock bootloader from AdamOutler's post in the dev forum. I was just weary about flashing a bootloader image since I've never dealt with a phone this locked down before. Can I simply flash the bootloader linked in his post from Odin?
Is there any confirmed way to remove this in case I need to take the phone in for repairs?
I used to have the custom screen but now I don't anymore. I'm on root66 rom, cwm and have the Samsung boot animation instead of Verizon's animation.
The last thing i did was flash the VRLG1 firmware / baseband I don't know ever the thread is since the forums broke up. Might give that a try or our your on that version reflash it. The file should only be about 40mb and you don't lose root.
Sent from my SCH-I535 using Tapatalk 2
jasondhsd said:
I used to have the custom screen but now I don't anymore. I'm on root66 rom, cwm and have the Samsung boot animation instead of Verizon's animation.
The last thing i did was flash the VRLG1 firmware / baseband I don't know ever the thread is since the forums broke up. Might give that a try or our your on that version reflash it. The file should only be about 40mb and you don't lose root.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I actually ended up fixing it a few hours ago by simply reflashing the root66 image and the immediate freezing the SysScope application with titanium backup. The phone still shows as "modified" under the About Phone menu in settings, but it seems to have prevented the custom boot logo from arising. Credit to crabapples for suggesting this in the thread about resetting the flash count.
My phone shows device status: normal under phone status.
Sent from my SCH-I535 using Tapatalk 2
tasteless1 said:
I actually ended up fixing it a few hours ago by simply reflashing the root66 image and the immediate freezing the SysScope application with titanium backup. The phone still shows as "modified" under the About Phone menu in settings, but it seems to have prevented the custom boot logo from arising. Credit to crabapples for suggesting this in the thread about resetting the flash count.
Click to expand...
Click to collapse
I just started getting this today for some reason on root66 ROM. I'm new to Samsung phones....to reflash root66, do I do so using Odin or can I use CWM Recovery?
Sent from my SCH-I535 using xda app-developers app
Related
PLEASE HELP!! I have successfully rooted the device and was doing ok after flashing CWmod recovery 6.0.1 through E-Z recovery app and running Liquid Rom. I managed to be dumb enough to flash CWMod version 5.8.4.9 through Rom manager and when I rebooted my phone it got stuck in boot loop. I am able to get into CWMod 5.8.4.9 but I cannot restore my backup anymore. I can also data wipe and install a new rom, but it all just keeps going into bootloop and I cannot get past the samsung custom unlock screen. It first flashed that, then the android man pops up on the next screen like its loading something and then just keeps looping through the process. I did not use ODIN for any of this process and I dont know how to get myself back tothe point where I can reboot. Any help would be tremendously appreciated, because I'm dead stuck and in a panic. Thanks in advance for any assistance.
Happend to me last night...
I made the same mistake... DO NOT download any recoveries from ROM manager. I found out the hard way... So the problem now is your phone is stuck using the recovery you downloaded. I am not sure of a quick way using that recovery if you can revert back but... My solution got me where I needed to be in order to get going again.
I had to use Odin to root to stock ROM. Yes when you wipe it will destroy your data but not your pictures, downloaded files, and other files you put on there. When I re-rooted with stock all my stuff for CM10, gapps, and the kexec CWM was there.
So use this guide...
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Section 1!!!!! And follow the steps EXACTLY the way it says to.
This is why i have never liked rom manager...
The best solution for us to flash recoveries is ez recovery free from the market. I would use this going forward once you Odin back to stock
Sent from my SCH-I535 using xda premium
Same **** happened to me.
Odin. I lost my pics and internal memory though...
Sent from my SCH-I535 using Tapatalk 2
Alright so I started the process of rooting, unlocking, and flashing the Bean ROM on my VZW GS3. I backed up using Nandroid and Titanium backup, rooted and unlocked the bootloader using EX Unlock yesterday. Then, without flashing a ROM, I rebooted my phone. And then I got drunk. Today, I flashed recovery, booted into recovery mode, deleted the user data (again) and installed then installed the Bean ROM. I figured my bootloader was still unlocked but I guess it wasn't. Now I'm getting the "This System Software not authorized by Verizon Wireless..." message.
Anybody have any clue what to do now?
Restock the Rom via odin flash of stock files from Adams thread
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
You say you made a nandroid yesterday but today you just flashed recovery. I'm confused.
Sent from my SCH-I535 using xda app-developers app
If you use ez unlock I'd say unlock and lock twice. Recovery told me I wasn't unlocked at first.
Sent from my SCH-I535 using xda premium
Hey guys, so I have been trying to work at this and here is where I'm at...
I'm following section 6 of this post [http://forum.xda-developers.com/showthread.php?t=1762709]. Everything works as listed except for when I select the ROM from the three in that post and try and run it through Odin. It always fails. I tried all three ROMs with the same result and since I don't know what exactly is keeping this from working, I can't troubleshoot it in any way. If anyone could help, I would really appreciate it.
Thank you!
Okay so a little while back my phone had a huge freak out and I had to restore everything to stock in order for it to even turn on anymore. Well I was trying to reroot it the other day and when I installed twrp, my phone would show the twrp screen and then boot loop over and over to that screen while I was trying to get into the recovery. Does anyone know why this could be happening or even better. I fix for my problem.
I'd try to re-flash twrp. Then from twrp, wipe everything multiple times and factory reset. But it could be something with the phone is bad and not repairable
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Did you try restoring to stock using Odin and official Samsung update .tar? And also restoring to stock recovery beforehand? Try that, run the Rom for bit and see if it has any hiccups. If so, I'd say hardware issue. If not, try flashing twrp .tar file from sticky thread on how to root.
Sent from my SGH-I727 using xda premium
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
anacree said:
I have Verizons S3. I recently rooted and unlocked the bootloader and have TWRP recovery. I was on 4.1 JB. I made a Nandroid Backup of System and Data. I then flashed the CM10.1 Monthly ROM, and all seemed to be working fine. However, I was having some issues with my app backups and the weird "emulated" directory structure. So I decided to go back to my Nandroid Backup and start over.
I went into TWRP, did a factory reset, cleared System Data, cache/dvalick cache, then I restored the Nandroid Backup (system and data). TWRP said it was successful and asked to reboot. When I did, the Samsung logo flashes, and then the screen stays black. I tried going back into recovery, but it won't let me. I can get to download though.
I think I'm going to have to use Odin to reflash a ROM as I can't get into recovery, right? But I'm also trying to understand what I did wrong. Did I forget a step? Did it have something to do with differences between 4.1 and 4.2? I'm new to this, and have searched the forums but can't find anything that answers my questions specifically. I appreciate the help.
Click to expand...
Click to collapse
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
You're supposed to backup "boot.img" as well. I'm pretty sure boot.img is the kernel which you failed to backup. The phone won't boot into your nandroid because the kernel wasn't restored as well. In TWRP: system, data, and boot are all supposed to be backed up simultaneously if you want to restore the entire nandroid. Odin flash and make sure to do a proper nandroid with all three that I listed.
Click to expand...
Click to collapse
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
anacree said:
Ah, perhaps that "boot" checkbox wasn't check. =P So basically the CM10.1 boot.img is still there, but now the wrong ROM is there so it won't boot? Can I just flash the boot.img with Odin now, or will I need to do a full ROM flash?
Click to expand...
Click to collapse
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
jdub251 said:
Flash nandroid and then try to flash a kernel. Might work Idk. Worth a shot.
sent telepathically
Click to expand...
Click to collapse
Edit. Are you still not able to get into recovery? Sorry missed that in your post.
sent telepathically
jdub251 said:
Are you still not able to get into recovery? Sorry missed that in your post.
Click to expand...
Click to collapse
No, when I do the button combo for recovery, the word "Samsung" flashes, then "Galaxy S3" logo, but after that nothing...just blank screen. I was on stock Verizon s3 before this, so I guess I need to put that kernel back on the phone? Is the kernel the same as the bootloader? Can I use the unlocked bootloader referenced in this post: http://forum.xda-developers.com/showthread.php?t=1974114?
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
anacree said:
So, I tried using Odin to flash back the stock JB 4.1.1 kernel, which should have matched my Nandroid backup, but then I got an unlocked padlock on my splash screen and then the yellow triangle. blah. so i flashed a stock no wipe rom and that got me back into touchwiz, but I cant get into recovery no matter what i do. And I still have the padlock. I think I may need to do a stock full wipe rom?
Click to expand...
Click to collapse
If you flashed a fully stock rom then you need to root, unlock, and install your custom recovery again.
Sent from my SCH-I535 using xda app-developers app
Ok, so I finally got time to try this again after flashing back to (what I thought) was stock Jelly Bean 4.1. I was following the directions here in this thread: http://forum.xda-developers.com/showthread.php?t=2046439
I get the VRALEC bootchain fine, phone reboots and all seems well. I got to flash TWRP 2.4, do a batter pull, and when I try to boot into recovery mode suddenly there is the Samsung splash screen with an unlocked padlock on it. Then the screen goes black and doesn't go into recovery. When I release the buttons, the phone then boots into the OS. I can still get to the download mode, but for some reason I can't get into a custom recovery. Any help on this? Please?
I used this file to wipe my phone back to stock JB: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship.tar.md5
Thanks for the assistance. =)
Redo step three like the directions state.
Edit : In that thread, some folks even suggest waiting 5-10 mins after its successfully flashed before booting into recovery.
Sent from my SCH-I535 using xda app-developers app
Forgot to followup here, but I got it working. I left my phone plugged in after flashing the recovery for like 15 minutes. I also released the power button on trying to boot into recovery once the Samsung logo appeared. I finally got into recovery and was so happy. Thanks for the help!
Running mastamoon's unofficial CM 10.1. =)
anacree said:
Running mastamoon's unofficial CM 10.1. =)
Click to expand...
Click to collapse
Perfect! Glad you've got it all working properly!
Sent from my SCH-I535 using xda app-developers app
Hello All - I am a long time viewer of the forum, Recently I noticed an update available for the GS# to 4.2.2. I downloaded the Rom and began my normal process of using ROM Manager to boot into recovery mode to install the latest file. When the update finished applying I was presented with a brief view of the Samsung boot screen and then remained stuck on the Google Boot Screen.
I downloaded a stock firmware to apply with Odin 3.07 but it fails halfway through the write process.
Can someone please give me a hand or point me in a direction if you experienced the same problem.
Also when I try to load into recovery mode the phone screen remains black.
Thanks for any help!
Nick
What rom did you try to upgrade? Link please? And just to verify, do you have a Verizon GSIII?
Sent from my SCH-I535 using xda app-developers app
Follow up
I tried to download the 4.2.2 file from the following location,rootzwiki - "aokp-d2vzw-jb-mr1-build-4", went through rom manager and now is timing out on the google screen.
I do still have the phone with me currently. Thanks for any help you can provide.
I never use Rom Manager so that's not surprising to me. When you pull the battery then hold power, home, and Up until it vibrates does it boot to recovery? I would suggest flashing through CWM.
Sent from my SCH-I535 using xda app-developers app
Follow up
SlimSnoopOS said:
I never use Rom Manager so that's not surprising to me. When you pull the battery then hold power, home, and Up until it vibrates does it boot to recovery? I would suggest flashing through CWM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
When I pull the battery and do the pwer,home,up it acts like its going to boot into recovery.. has in blue letters boot into recovery but the screen goes blank. Is this supposed to happen.
thashock said:
When I pull the battery and do the pwer,home,up it acts like its going to boot into recovery.. has in blue letters boot into recovery but the screen goes blank. Is this supposed to happen.
Click to expand...
Click to collapse
It may take a few attempts to get it to work since it's fickle sometimes.
Sent from my SCH-I535 using xda app-developers app
Still having some issues
SlimSnoopOS said:
It may take a few attempts to get it to work since it's fickle sometimes.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks SlimSnoop I have tried roughly 15 times and am still not having any luck, are there any other tools you or anyone can suggest??
Yea, as long as you can boot into download mode then I suggest you utilize Odin and flash a stock image. There are two routes that you can go:
1) Odin flash the Verizon OTA VRBLK3 stock tar from DroidStyle's guide in the dev section. With this method, you would be returned to out of the box VRBLK3 and would need to root/unlock then flash roms again. The Odin tars included here are labeled as wiping /sdcard so be mindful of this.
2) Odin flash a rooted VRBLK3 image from mrRobinson thread. His thread contains Odin flashable rooted tars that are exactly the same as the OTA equivalent except they are rooted already. With this method, you would just need to unlock your bootloader using EZ Unlock v1.2 before flashing any custom roms. There's two versions of each rooted image here, one that wipes /sdcard and one that does not. So if you download the one labeled as wiping /sdcard all of your contents will be completely erased.
Sent from my SCH-I535 using xda app-developers app