Related
Obviously there are reasons for wrong doing but after soft bricking my vibrant (not really doing anything just started force closing upon a morning reboot and now i'm stuck) I'm wondering why this happens? I've seen a lot of posts saying that from "flashing too many ROMS" but i flashed a boatload of roms on my g1 and as long as I did it correctly it was fine because it should be wiping all data and replacing it with a whole new ROM but yet when I flash the exact zip files that have worked before they all result in a black screen, i'm currently trying to find a solution to get to stock ( i have a mac ) but I mean, I want to go back to bionix fusion but not if I know that after every couple flashes the phone will go black on me and ill have to start all over at stock again. Sorry, I just want more of a specific reason than "flashing too many roms"
joe.kerwin said:
Obviously there are reasons for wrong doing but after soft bricking my vibrant (not really doing anything just started force closing upon a morning reboot and now i'm stuck) I'm wondering why this happens? I've seen a lot of posts saying that from "flashing too many ROMS" but i flashed a boatload of roms on my g1 and as long as I did it correctly it was fine because it should be wiping all data and replacing it with a whole new ROM but yet when I flash the exact zip files that have worked before they all result in a black screen, i'm currently trying to find a solution to get to stock ( i have a mac ) but I mean, I want to go back to bionix fusion but not if I know that after every couple flashes the phone will go black on me and ill have to start all over at stock again. Sorry, I just want more of a specific reason than "flashing too many roms"
Click to expand...
Click to collapse
Step 3: Flash Bionix Fusion
This is the final step of the installation. This presumes you are already rooted and ready to go. If you are not, then you will need to root and install rom manager first.
1. Download the rom of your choice and place the file onto the root of your internal sdcard.
2. Reboot into Clockwork Recovery.
- From Rom Manager app, select 'boot into clockwork recovery'
- From ADB, type 'adb reboot recovery'.
3. From the main clockwork recovery menu, use the 'down' volume control to scroll to 'install zip from sdcard'. Press the power button. this will take you to a second menu screen.
4. From thet second menu screen, scroll to 'choose zip from sdcard' and select with the power button.
5. Scroll to the file name of the rom you downloaded and press the power button. It will ask you to confirm your choice, select 'yes' and the rom will begin to flash. DO NOT TURN OFF YOUR PHONE DURING THIS PROCESS!
6. Once the flash is complete, select 'go back'. Now select 'reboot' from this menu.
7. Allow your phone to reboot completely. The first boot will take a few minutes, please be patient.
8. Once booted into the home screen, please allow your phone to sit for 5-10 minutes to allow all boot procedures to take place. Keep in mind, you've just heavily modified your device, it needs time to adjust to the new changes.
9. Wait roughly 15 minutes after the first initial boot and then restart your phone one time. You may do this by holding the 'power button' and selecting either shut down or reboot.
chichu_9 said:
Step 3: Flash Bionix Fusion
This is the final step of the installation. This presumes you are already rooted and ready to go. If you are not, then you will need to root and install rom manager first.
1. Download the rom of your choice and place the file onto the root of your internal sdcard.
2. Reboot into Clockwork Recovery.
- From Rom Manager app, select 'boot into clockwork recovery'
- From ADB, type 'adb reboot recovery'.
3. From the main clockwork recovery menu, use the 'down' volume control to scroll to 'install zip from sdcard'. Press the power button. this will take you to a second menu screen.
4. From thet second menu screen, scroll to 'choose zip from sdcard' and select with the power button.
5. Scroll to the file name of the rom you downloaded and press the power button. It will ask you to confirm your choice, select 'yes' and the rom will begin to flash. DO NOT TURN OFF YOUR PHONE DURING THIS PROCESS!
6. Once the flash is complete, select 'go back'. Now select 'reboot' from this menu.
7. Allow your phone to reboot completely. The first boot will take a few minutes, please be patient.
8. Once booted into the home screen, please allow your phone to sit for 5-10 minutes to allow all boot procedures to take place. Keep in mind, you've just heavily modified your device, it needs time to adjust to the new changes.
9. Wait roughly 15 minutes after the first initial boot and then restart your phone one time. You may do this by holding the 'power button' and selecting either shut down or reboot.
Click to expand...
Click to collapse
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
joe.kerwin said:
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
Click to expand...
Click to collapse
Well, if you follow the instructions mentioned in the fusion post it should clean wipe your phone and give you a stable phone, give it a try without tweaking the kernel or anything to make sure you are not getting any black screens.
1 question though did you overclock your phone?
I would take 1 step at a time, first get your phone to stabilize. The reason I referenced Fusion is because, Fusion is much more stable than the Stock Samsung JFD.
joe.kerwin said:
Well at least we know you can copy and paste. You obviously didn't read my post correctly.
Click to expand...
Click to collapse
Did you flash anything over Voodoo?
i've never used voodoo and no i wasn't overclocking even though i had an OC capable kernel. My problem was my phone doesn't turn on, and i dont have a PC to use ODIN also I mentioned that no matter what ROM I flash my phone wont turn on, flashing fusion would not fix it. Anyways I went to tmobile and just told them "my phone doesn't work" and this really cool guy just swapped it for me no questions asked even though i'm well beyond that two week grace period.
Bricks don't happen from flashing too many roms. I've been flashing roms constantly for the last couple weeks, and I've yet to brick my phone. Bricks are usually caused by people not carefully following instructions, or by flashing incompatible rom/kernel combinations. If you play it safe and are careful, you won't brick your phone.
joe.kerwin said:
i've never used voodoo and no i wasn't overclocking even though i had an OC capable kernel. My problem was my phone doesn't turn on, and i dont have a PC to use ODIN also I mentioned that no matter what ROM I flash my phone wont turn on, flashing fusion would not fix it. Anyways I went to tmobile and just told them "my phone doesn't work" and this really cool guy just swapped it for me no questions asked even though i'm well beyond that two week grace period.
Click to expand...
Click to collapse
Most probably the oc/uv kernel, some phones cannot handle undervolting.
Sent from my bionix powered Vibrant
My phone is pretty new... I only had it unlocked and rooted.
It just soft bricked on me this morning after listening to music... Not exactly sure why.....
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J
First of all, I'm new to this forums AND I'm new to rooting, so please take it easy with me.
Anyways, so I want to root my Galaxy S9 plus Exynos version, and I heard you should enable OEM unlock in developer options before you do anything, so I did switch it on, it asked me to do a factory reset, so I backed up everything and let it do its thing. Now when I go to developer options the OEM unlock is ofcourse not there, but when I go to download mode it says that OEM lock and FRP lock are off. So does that mean I successfully unlocked the bootloader and now I can flash TWRP?
I believe you have to leave the phone on for 7 days for it to show up.
You can try this too - https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
mjones73 said:
I believe you have to leave the phone on for 7 days for it to show up.
You can try this too - https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
Yeah, maybe i should just wait
LavaSnake54 said:
First of all, I'm new to this forums AND I'm new to rooting, so please take it easy with me.
Anyways, so I want to root my Galaxy S9 plus Exynos version, and I heard you should enable OEM unlock in developer options before you do anything, so I did switch it on, it asked me to do a factory reset, so I backed up everything and let it do its thing. Now when I go to developer options the OEM unlock is ofcourse not there, but when I go to download mode it says that OEM lock and FRP lock are off. So does that mean I successfully unlocked the bootloader and now I can flash TWRP?
Click to expand...
Click to collapse
Well since you new you should have done your research on this process.
If you had you would have known NOT to let it reboot to system once turning OEM unlock on....factory reset is normal as you now know.
What you should have done is flip the swtich and then boot directly to download mode and flash twrp to avoid the reset.
Yes now you must wait 7 days again to do anything.
Reading and research is key here dude, never just blindly do anything...bad things can happen. In this case no biggie though just more waiting
sent from my Exynos S9 plus, Pixel 2 XL or Note FE
force70 said:
What you should have done is flip the swtich and then boot directly to download mode and flash twrp to avoid the reset.
Click to expand...
Click to collapse
Sorry, but with things like this I like to be exact and have no level of presumption or uncertainty.
In saying that, when you say "flip the switch and boot to DL mode" do you mean to flip the switch, and DON'T press agree, or DON'T accept the pop up warning from samsung to restore, but to just ignore and reboot to DL mode?
So literally do what you said and do 2 actions,
1. flip switch
2. restart in DL mode (and exclude pressing any of the pop up notifications from samsung to restore).
Will this work, or do you need to accept samsungs pop up notification to reboot in order to enable OEM unlock ?
jujubeans said:
Sorry, but with things like this I like to be exact and have no level of presumption or uncertainty.
In saying that, when you say "flip the switch and boot to DL mode" do you mean to flip the switch, and DON'T press agree, or DON'T accept the pop up warning from samsung to restore, but to just ignore and reboot to DL mode?
So literally do what you said and do 2 actions,
1. flip switch
2. restart in DL mode (and exclude pressing any of the pop up notifications from samsung to restore).
Will this work, or do you need to accept samsungs pop up notification to reboot in order to enable OEM unlock ?
Click to expand...
Click to collapse
Yes you have to acknowledge the prompt then boot to DL immediately.
The key here is NOT to let the device start the reset process
"Erasing" Loop - Tried Returning to Stock After Converting to US998 from H933
I rooted my phone using LGUP and tried to switch back to stock; hoping to keep root. I flashed all items except "recovery" but then tried to re-flash just the stock recovery, as stated in on one of the posts I found, and now I think I have a paper weight. I made sure to read the instructions a few times before doing things, but guess I missed something, or the instructions I followed aren't for my version or may be outdated?!
I can't get into download mode. The PC doesn't recognize I've even plugged it in. And now it just keeps boot looping showing the Erasing Circle over and over and over.
Anyone here know if I have any hope that once the battery dies, I could plug it in, holding the volume up, and be able to get into download mode? I'm hoping I can... Not a happy camper right now.
I see the thread title now. Let me respond in a few minutes.
---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------
ColtonYYZ said:
I rooted my phone using LGUP and tried to switch back to stock; hoping to keep root. I flashed all items except "recovery" but then tried to re-flash just the stock recovery, as stated in on one of the posts I found, and now I think I have a paper weight. I made sure to read the instructions a few times before doing things, but guess I missed something, or the instructions I followed aren't for my version or may be outdated?!
Click to expand...
Click to collapse
You didn't root your phone with LGUP. You rooted your phone with TWRP and Magisk. You used LGUP to convert to US998 so you would have fastboot flash commands to unlock bootloader and install TWRP, so you could then root with Magisk.
Why don't you ask in thread where you were following the directions? Yes, it is tedious and complicated for the H933 -- but the end result is you WANT TWRP custom recovery and Magisk, but you want to eradicate all traces of US998 firmware.
I still don't have any answer to my question though...
ChazzMatt said:
I see the thread title now. Let me respond in a few minutes.
---------- Post added at 07:40 PM ---------- Previous post was at 07:31 PM ----------
You didn't root your phone with LGUP. You rooted your phone with TWRP and Magisk. You used LGUP to convert to US998 so you would have fastboot flash commands to unlock bootloader and install TWRP, so you could then root with Magisk.
Why don't you ask in thread where you were following the directions? Yes, it is tedious and complicated for the H933 -- but the end result is you WANT TWRP custom recovery and Magisk, but you want to eradicate all traces of US998 firmware.
Click to expand...
Click to collapse
I appreciate you taking the time to reply. You are correct in saying I didn't root with LGUP. I mistyped/misspoke. There are so many threads that I read, I can't find the one I was following. I had 15 tabs opened; I freaked out, and so I created a new thread for my problem. My problem doesn't really involve any particular thread now because it's not even booting up - in order for me to do anything.
I see the LG logo.. then sometimes I see the stupid bootloader warning, then back to LG logo for a few seconds and then it says "Erasing" in bold vibrant colouring.. then it shades out barely visible for 10-15 secs. Turns off, then basically repeats.
I know about all the flashable zips for H933.... but ALL of them say NOT to use them to convert back from US998 to H933.
Here is a thread (step 5) which basically everyone else posts also, that says you flash the kdz - everything except recovery - and twrp should be installed. This is not true. I did this about 6 times and could never boot into recovery afterwards. It would erase the phone and go back into setup mode each and every time.
I couldn't find any article to explain how to get back to stock firmware without using the kdz, which I did, and unselecting recovery. When doing so, twrp was gone - despite me not selecting recovery or even recovery.bak sometimes. So what I did was, use LGUP again with the kdz and uncheck everything except recovery and recovery.bak the 2nd time around and bam... now I am stuck.
ColtonYYZ said:
I appreciate you taking the time to reply. You are correct in saying I didn't root with LGUP. I mistyped/misspoke. There are so many threads that I read, I can't find the one I was following. I had 15 tabs opened; I freaked out, and so I created a new thread for my problem. My problem doesn't really involve any particular thread now because it's not even booting up - in order for me to do anything.
I see the LG logo.. then sometimes I see the stupid bootloader warning, then back to LG logo for a few seconds and then it says "Erasing" in bold vibrant colouring.. then it shades out barely visible for 10-15 secs. Turns off, then basically repeats.
I know about all the flashable zips for H933.... but ALL of them say NOT to use them to convert back from US998 to H933.
Here is a thread (step 5) which basically everyone else posts also, that says you flash the kdz - everything except recovery - and twrp should be installed. This is not true. I did this about 6 times and could never boot into recovery afterwards. It would erase the phone and go back into setup mode each and every time.
I couldn't find any article to explain how to get back to stock firmware without using the kdz, which I did, and unselecting recovery. When doing so, twrp was gone - despite me not selecting recovery or even recovery.bak sometimes. So what I did was, use LGUP again with the kdz and uncheck everything except recovery and recovery.bak the 2nd time around and bam... now I am stuck.
Click to expand...
Click to collapse
Who said you couldn't use H933 after US998? You're fine if you use partition DL.
I have gone from US998 to H933 several times.
I'm currently on my commute to work but let me read your issues and see if we can't get you back to normal.
( I'm pretty active in modding our H933 )
Don't touch recovery.bak; only deselect recovery.
So where are you currently?
And after you pull your phone from PC after not selecting recovery are you pulling your phone and trying to master reset to access recovery or letting LGUP auto boot into twrp? Should happen as soon as H933 attempts to boot.
ColtonYYZ said:
I see the LG logo.. then sometimes I see the stupid bootloader warning, then back to LG logo for a few seconds and then it says "Erasing" in bold vibrant colouring.. then it shades out barely visible for 10-15 secs. Turns off, then basically repeats.
Click to expand...
Click to collapse
Have you tried Master Reset to stop the boot looping? Master Reset is not factory reset.
Master Reset -- using buttons:
1. Unplug phone and turn it OFF.
2. Press and hold the Power and Volume down buttons.
3. When the LG logo appears, quickly release the Power button only -- then immediately press Power button again, while STILL pressing the Volume down button until you see the screen to select Yes to erase and reset everything.
4. Release both buttons so you can make your choices.
With your device powered off, press and hold the Power button and Volume Down buttons simultaneously for a few seconds.
When the LG logo appears, quickly release and then re-hold the Power button while keep holding the Volume Down button.
Let go of the buttons when the onscreen menu appears.
When you see the option to Delete all user data (including LG and carrier apps) and reset all settings message prompt, press the Volume Down button to highlight Yes.
Then press the Power button to reset the device.
Wait until the reset is complete then reboot your device. If it’s able to boot up successfully, proceed with the initial setup.
Click to expand...
Click to collapse
You can even do it if you can not power the device off, but you just have to time it right.
This is the most complete guide of what you were probably trying to do, if trying to go back to stock and keep root:
seadersn said:
@christopherrrg wrote a "little guide" for the peoples, who may ever have thought about going back to h33 original (rooted or not) sw. Give him some thanks pls, he's now a few nerves lost in this procedure i can imagine :good: thanks!
Here it is:
Okay so the steps below are for AFTER using the WTF thread to convert device and unlock bootloader; these steps are for canadian model users who would prefer to go back to stock canadian kdz with working root and twrp intact.
Step 1 - Attach converted US998 (bl unlocked and twrp installed) to LGUP.
Step 2 - PARTITION DL the canadian kdz but do not include recovery.
Step 3 - Let phone boot right from kdz flash and it will automatically boot TWRP.
Step 4 - While in TWRP; 1st factory reset AND AFTER format data then reboot recovery. (If not done TWRP has mount issues with cache and or system.)
Step 5 - After TWRP is rebooted flash no-verity-opt-encrypt-6.0.zip + lg-rctd-disabler-1.0.zip and afterwards flash magisk.
Step 6 - While still in TWRP use the option to power device down.
Step 7 - Attach device to PC while holding vol+ and it will automatically start download mode.
Step 8 - PARTITION DL the canadian kdz again EXCEPT uncheck everything BUT stock recovery; let it flash and reboot.
Step 9 - Should reboot 3 - 4 times.
Step 10 - Once booted to setup; get past then activate USB debugging, also open magisk and click yes as many times as it asks you. (Magisk remains because only RECOVERY is flashed at this point)
Step 11 - Download TWRP and rename to just twrp then place it in the root directory of your internal storage.
Step 11 - Connect device to android debug bridge, and start a shell with 'adb shell' command.
Step 12 - then type 'su' and hit enter in order to gain root privilege. (Will have to click accept on super user on device)
Step 13 - then type 'dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery'
If done correctly you should see flashing (almost like fastboot) however you will not have anything happen to your device graphically SO open magisk and click modules then click reboot to recovery and profit!
You should be on H933 kdz with TWRP and root.
However for some weird reason, cloud is correct as the battery drain is abysmal. My phone used to go from 9am 100% to about 60% by the time I get home at 5pm. Today it's gone down to 22% from 100% at 9am and it's only 2pm. @cloud1250000's brain was mostly picked for this so he deserves any and all credit; I just confirmed and wrote this up for reference.
Enjoy!
Credits to @cloud1250000
Click to expand...
Click to collapse
Also; I realize my guide in seadersn posts need a bit of an update so I will message him today and have him update as a ton of people are using it for reference and that guide has battery issues. (Without doing dd etc)
Try following this guide to the letter.
https://forum.xda-developers.com/lg-v30/how-to/canadian-h933-compatibility-h930-roms-t3897586
Just replace the latest with 20i (h933)
Make sure to read my post inclusive at the end of that thread; feel free to PM me as well if you can't get anything the way you want it.
Unfortunately I can't do anything with the phone when I connect to my PC with the USB cable - except when holding power and both Cole buttons, i can get it to load a page with the imei number etc.
I can also (by holding power and toggling both volumes) get it to recognize on my PC, but it shows up at QSLoader 9008 (or something like that - I'm at work right now so can't type exactly what it shows up as - but know 100% it says 9008).
I installed QPST and will see if I can flash it this way, after I figure out a way to create/find the firehouse. I found a YT video showing how to create the files needed so will give it ago when I get home.
I am grateful of the replies. I'm sure you get many idiots like myself who do stupid crap - so thank you for always still wanting to help. It must be annoying but us idiots are truly grateful!!
ColtonYYZ said:
Unfortunately I can't do anything with the phone when I connect to my PC with the USB cable - except when holding power and both Cole buttons, i can get it to load a page with the imei number etc.
I can also (by holding power and toggling both volumes) get it to recognize on my PC, but it shows up at QSLoader 9008 (or something like that - I'm at work right now so can't type exactly what it shows up as - but know 100% it says 9008).
I installed QPST and will see if I can flash it this way, after I figure out a way to create/find the firehouse. I found a YT video showing how to create the files needed so will give it ago when I get home.
I am grateful of the replies. I'm sure you get many idiots like myself who do stupid crap - so thank you for always still wanting to help. It must be annoying but us idiots are truly grateful!!
Click to expand...
Click to collapse
This sounds like what had happened to me with the RSA after flashing modem.bin. I only got lucky because my TWRP flashed successfully and I was able to restore using seadersn stock method. I've never gone as far as actually putting my device into 9008 brick (yet) so unfortunately I'm not much help there and for that I'm sorry. However there is a gent on ebay who will TeamViewer to your PC and fix it for you. A lot of people report it has a different device firmware but they do report success.
Also don't beat yourself up and call yourself an idiot.
Us humans are curious creatures! While it does suck for your device; it's just a speed bump!
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)
Warning: I am not a super developer, just one more user who wants to help the community
Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.
This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.
Without more to say, let's start.
How to re-lock bootloader:
1. Turn off your device.
2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (- or +) button as best suits you.
LOCK BOOTLOADER:
5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:
Ready! Now you have a device with an OEM lock.
Good luck my friends!!!
chalofito said:
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)
Warning: I am not a super developer, just one more user who wants to help the community
Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.
This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.
Without more to say, let's start.
How to re-lock bootloader:
1. Turn off your device.
2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (- or +) button as best suits you.
LOCK BOOTLOADER:
5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:
Ready! Now you have a device with an OEM lock.
Good luck my friends!!!
Click to expand...
Click to collapse
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.
I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
akkaria said:
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.
I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
Click to expand...
Click to collapse
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
chalofito said:
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
Click to expand...
Click to collapse
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?
This is my current version. I'm in Australia.
View attachment 4767541
akkaria said:
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?
his is my current version. I'm in Australia.
View attachment 4767541
Click to expand...
Click to collapse
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
chalofito said:
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
Click to expand...
Click to collapse
Thanks for your help. Yes, hopefully soon someone will find a method.
akkaria said:
Thanks for your help. Yes, hopefully soon someone will find a method.
Click to expand...
Click to collapse
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?
I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
SakazukiAka said:
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?
I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
Click to expand...
Click to collapse
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.
It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
akkaria said:
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.
It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
Click to expand...
Click to collapse
I see. There is another method, that seems to work, tested by @robbo1947 that he explained here.
robbo1947 said:
Assuming you had the standard Samsung ROM (you hadn't flashed a custom ROM)
Change OEM switch while rooted, exit settings, no need to flash stock firmware.
Power off phone.
Press and hold Bixby and Volume down, whilst holding connect with USB cable to computer. Release buttons when Download screen appears.
Long press the Volume up.
At this stage, the phone will wipe the data and overwrite the Magisk modification then reboot.
You should now have an S10, standard boot screens, stock ROM and no root.
Click to expand...
Click to collapse
I did not check it myselff yet, but it worked for robbo1947. All credits goes to @robbo1947 !! Please let us know if that worked for you or not.
SakazukiAka said:
I see. There is another method, that seems to work, tested by @robbo1947 that he explained here.
I did not check it myselff yet, but it worked for robbo1947. All credits goes to @robbo1947 !! Please let us know if that worked for you or not.
Click to expand...
Click to collapse
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.
Watch this space.
robbo1947 said:
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.
Watch this space.
Click to expand...
Click to collapse
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
I I had root and twrp on my s10 + but I quietly put the last nobrand ASE7 firmware back and I re-locked the bootloader without any difficulty I no longer have any warning messages at startup and in the developer options I have the oem option working like new.
akkaria said:
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though
Click to expand...
Click to collapse
Lebrun213 said:
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
Click to expand...
Click to collapse
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.
During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.
Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.
This is for the Galaxy S10 without TWRP.
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. Then the S10 logo screen will briefly apppear, before it flicks back to the Download screen with the words 'VBMETA: Error verifying vbmeta image etc' at the top, as the image below.
This is all good so far. Leave the phone exactly as it is with this screen showing and make sure the phone is still connected to the computer.
On your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 file parts (BL, AP. CP and CSC) into Odin.
Let Odin finish.
The phone will reboot ready for setup.
The Unlocked bootloader warning screen will be gone.
Scenario 2. Your phone has been rooted but isn't now, and the greyed out OEM switch is ON
Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Scenario 3 Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF
Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.
When rooted, proceed as Scenario 1.
Scenario 4 Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone
Turn off your phone and proceed from the 2nd paragraph of Scenario 1.
If you want proof that I have locked and unlocked time and time again see HERE
:victory:
robbo1947 said:
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.
During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.
Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. The S10 logo screen will briefly apppear, before it flicks back to the Download screen as the image below.
With the phone still connected to your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 parts into Odin.
Let Odin finish. The phone will reboot and the Unlocked bootloader warning screen will be gone.
Scenario 2. Your phone has been rooted but isn't now, and the greyed out OEM switch is ON
Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Scenario 3 Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF
Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.
When rooted, proceed as Scenario 1.
Scenario 4 Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone
Turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Click to expand...
Click to collapse
No dramas, thanks heaps for your reply.
So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
akkaria said:
No dramas, thanks heaps for your reply.
So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
Click to expand...
Click to collapse
Yep, your bootloader is unlocked.
When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.
Then when you get into Download mode you will see that option of LONG press Volume-up.
I've just added video proof to original post.
robbo1947 said:
Yep, your bootloader is unlocked.
When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.
Then when you get into Download mode you will see that option of LONG press Volume-up.
I've just added video proof to original post.
Click to expand...
Click to collapse
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.
Cheers
akkaria said:
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.
Cheers
Click to expand...
Click to collapse
Don't forget the :good:
robbo1947 said:
Don't forget the :good:
Click to expand...
Click to collapse
You sir, are my hero. It all worked perfectly and i no longer get the bootloader warning screen and my bootloader is now relocked!!
For anyone else having this problem, i too can confirm that this method works. The only issue i had was that for some reason, i was stuck on the Samsung flashing boot screen for nearly half an hour. A simple reboot into recovery(hold power and volume down for 7 seconds to shut down and then quickly hold power, vol up and bixby) and wipe factory data then system reboot fixed it.
I can also confirm that after doing this and re locking the bootloader, i now have access to all apps that i was previously having issues with and my google play store recognises my devices as certified.
I now have a fully working and functional device. Thank you again.
if i revert to stock rom after root and samsung status says official and relock bootloader will be able to get otas again???