[newbie] writing rom on SM-J100H, how to? - Samsung Galaxy J1 Questions & Answers

[ROM][SM-J100H][09-06-2021][Stable] CyanogenMod 11 MicroG For Samsung Galaxy ‏J1
Hi to all, I'm newbie with old branded SM-J100H with Android 4.4.4.
I would write rom I found in this forum to upgrade Android version.
I have no way to do this.
I've been searching for several guides on the net, none working.
I can detect device (only this) using adb.
I can't put device in recovery mode (tested several combinations of home-power-volume up bottons, none working).
I also enabled "developer options" menu, but missing "oem unlock", I've read "due to TIM operator branded phone".
Any ideas? Thanks.

for recovery mode boot into download when warning screen pop up press restart and hold recovery combination vol + home power

Related

[Q] Secure Boot Error, No Download Mode, No Fastboot, No Regular Boot.

Hello all!
Just a newbie here, but hopefully I don't break any forum rules.
Now, to the problem at hand. I have an LG D802 that cannot be booted normally, cannot be brought into fastboot or download mode.
When trying to power on, I get greeted with "boot verification error / secure boot error".
This happened after trying to flash the "Cloudy G2 3.0" (lollipop version) ROM onto my phone via TWRP. Everything seemed to be in working order until
I had rebooted the device. I think the problem stemmed from the fact that I didn't read that the ROM was only for a different variant of my phone.
I have had a look at one post ( http://forum.xda-developers.com/showthread.php?t=2582142 ) but found it too hard to actually follow the instructions,
so now, I am here, writing this post.
Please feel free to ask for any additional information!
Thank you in advanced.
bryyyyy said:
Hello all!
Just a newbie here, but hopefully I don't break any forum rules.
Now, to the problem at hand. I have an LG D802 that cannot be booted normally, cannot be brought into fastboot or download mode.
When trying to power on, I get greeted with "boot verification error / secure boot error".
This happened after trying to flash the "Cloudy G2 3.0" (lollipop version) ROM onto my phone via TWRP. Everything seemed to be in working order until
I had rebooted the device. I think the problem stemmed from the fact that I didn't read that the ROM was only for a different variant of my phone.
I have had a look at one post ( http://forum.xda-developers.com/showthread.php?t=2582142 ) but found it too hard to actually follow the instructions,
so now, I am here, writing this post.
Please feel free to ask for any additional information!
Thank you in advanced.
Click to expand...
Click to collapse
Guy, guy, guy..... It's clearly write in the FAQ section of CloudyG2 3.0 that the rom is ONLY for F320' series, but no, you still want to flash it in D802.. Anyway, do you have access to recovery mode? Key combination might be power key + volume down until LG logo appears, then those keys again or power key + volume down until lg logo, then volum down + volume up.
For download, try a simple thing: Press your power key for ~1 / 1min30, just to be sure it's poweroff, and then try volume up + plug USB cable
casual_kikoo said:
Guy, guy, guy..... It's clearly write in the FAQ section of CloudyG2 3.0 that the rom is ONLY for F320' series, but no, you still want to flash it in D802.. Anyway, do you have access to recovery mode? Key combination might be power key + volume down until LG logo appears, then those keys again or power key + volume down until lg logo, then volum down + volume up.
For download, try a simple thing: Press your power key for ~1 / 1min30, just to be sure it's poweroff, and then try volume up + plug USB cable
Click to expand...
Click to collapse
Yes... I know. Was very silly in doing so. I have no access to recovery mode using both of those methods you have stated. When trying to get into the download mode for the phone, I get the same error, it will say, secure boot error etc. then the screen will go black, and a bunch of drives pop up on my computer, from [A] - [K], and windows asks me to reformat all of them.
Update: When plugging device into computer, it says QHSUSB_BULK. Hopefully that helps a bit

teamwin-Loop for Galaxy Tab A 2019 SM-T510

Hello everyone,
Usually, I never write posts but in this case, I don't know what I can do anymore.
Here is what happened:
Because I wanted a running Linux-System on my tablet I tried rooting for the first time ever.
I searched the net and watched youtube videos and thought I was ready.
- I downloaded the twrp-file from there [w*w*w.getdroidtips.com/twrp-recovery-samsung-galaxy/#TWRP_Recovery_For_Samsung_Galaxy_Tab]
- Renamed it to RECOVERY.tar
- Downloaded Odin3_v3.13.1
- Downloaded the newest USB-Drivers for Samsung Devices
- I activated USB-Debugging-Mode and OEM-Mode
- I restarted it using Power + Vol+
- I navigated to the bootmanager and tried to install twrp through Odin
- I got 2 different messages:
1. custom binary blocked by oem​2. Only official released binaries are allowed to be flashed​After searching the net I found a german forum entry with this advice:
- Restarting my tablet I pushed VOL +/- together to get to a screen to activate the Bootloader
- Restarting my tablet using Power + Vol+
- Now it was possible to install twrp through Odin (I selected the .tar-file [inside the .tar-file are to different files: recovery.img and vbmeta.img] for the AP-Option in Odin]
I did then a restart and got this 3 different screens [not allowed to post outside links]
h*ttps://postimg.cc/Vr48R5QK
h*ttps://postimg.cc/CdLYKCkX
h*ttps://postimg.cc/m1DG6RTB
This is now a loop! I can not shut-down my tablet or enter any different mode using different button variations or start into the os.
Also connecting it to the computer doesn't work (no connection).
As mentioned before I am new to rooting and I don't have any coding knowledge, so please bear that in mind!
Thank you in advance for your help
much appreciated
PS: Yes I tried duckduckgo but for some reason, it is very difficult to find something for sm-t510 ...
7Nanashi4 said:
Hello everyone,
Usually, I never write posts but in this case, I don't know what I can do anymore.
Here is what happened:
Because I wanted a running Linux-System on my tablet I tried rooting for the first time ever.
I searched the net and watched youtube videos and thought I was ready.
- I downloaded the twrp-file from there [w*w*w.getdroidtips.com/twrp-recovery-samsung-galaxy/#TWRP_Recovery_For_Samsung_Galaxy_Tab]
- Renamed it to RECOVERY.tar
- Downloaded Odin3_v3.13.1
- Downloaded the newest USB-Drivers for Samsung Devices
- I activated USB-Debugging-Mode and OEM-Mode
- I restarted it using Power + Vol+
- I navigated to the bootmanager and tried to install twrp through Odin
- I got 2 different messages:
1. custom binary blocked by oem
2. Only official released binaries are allowed to be flashed
After searching the net I found a german forum entry with this advice:
- Restarting my tablet I pushed VOL +/- together to get to a screen to activate the Bootloader
- Restarting my tablet using Power + Vol+
- Now it was possible to install twrp through Odin (I selected the .tar-file [inside the .tar-file are to different files: recovery.img and vbmeta.img] for the AP-Option in Odin]
I did then a restart and got this 3 different screens [not allowed to post outside links]
h*ttps://postimg.cc/Vr48R5QK
h*ttps://postimg.cc/CdLYKCkX
h*ttps://postimg.cc/m1DG6RTB
This is now a loop! I can not shut-down my tablet or enter any different mode using different button variations or start into the os.
Also connecting it to the computer doesn't work (no connection).
As mentioned before I am new to rooting and I don't have any coding knowledge, so please bear that in mind!
Thank you in advance for your help
much appreciated
PS: Yes I tried duckduckgo but for some reason, it is very difficult to find something for sm-t510 ...
Click to expand...
Click to collapse
for future reference/advice you should always do research and ask questions ifyou are unsure of anything.
When I say research I mean XDA or other known/reliable sources. The TWRP thread and instructions directly from the person who made the twrp are in this forum.
I suggest you locate the TWRP thread for a fix.
7Nanashi4 said:
Hello everyone,
Usually, I never write posts but in this case, I don't know what I can do anymore.
Here is what happened:
Because I wanted a running Linux-System on my tablet I tried rooting for the first time ever.
I searched the net and watched youtube videos and thought I was ready.
- I downloaded the twrp-file from there [w*w*w.getdroidtips.com/twrp-recovery-samsung-galaxy/#TWRP_Recovery_For_Samsung_Galaxy_Tab]
- Renamed it to RECOVERY.tar
- Downloaded Odin3_v3.13.1
- Downloaded the newest USB-Drivers for Samsung Devices
- I activated USB-Debugging-Mode and OEM-Mode
- I restarted it using Power + Vol+
- I navigated to the bootmanager and tried to install twrp through Odin
- I got 2 different messages:
1. custom binary blocked by oem​2. Only official released binaries are allowed to be flashed​After searching the net I found a german forum entry with this advice:
- Restarting my tablet I pushed VOL +/- together to get to a screen to activate the Bootloader
- Restarting my tablet using Power + Vol+
- Now it was possible to install twrp through Odin (I selected the .tar-file [inside the .tar-file are to different files: recovery.img and vbmeta.img] for the AP-Option in Odin]
I did then a restart and got this 3 different screens [not allowed to post outside links]
h*ttps://postimg.cc/Vr48R5QK
h*ttps://postimg.cc/CdLYKCkX
h*ttps://postimg.cc/m1DG6RTB
This is now a loop! I can not shut-down my tablet or enter any different mode using different button variations or start into the os.
Also connecting it to the computer doesn't work (no connection).
As mentioned before I am new to rooting and I don't have any coding knowledge, so please bear that in mind!
Thank you in advance for your help
much appreciated
Looks like you haven't completed the bootloader unlock. Remember, you've got to enable the OEM Unlocking setting and then reboot with the USB cable inserted holding Vol Up & Vol Down. From the light blue Warning screen, long press Vol Up to unlock bootloader.
PS: Yes I tried duckduckgo but for some reason, it is very difficult to find something for sm-t510 ...
Click to expand...
Click to collapse
Looks like you haven't completed the bootloader unlock. Remember, you've got to enable the OEM Unlocking setting and then reboot with the USB cable inserted holding Vol Up & Vol Down. From the light blue Warning screen, long press Vol Up to unlock bootloader.

How to Unlock Bootloader Galaxy A51

Please make back up data first, because unlock bootloader is formatting data and erase all your file
Unlock Bootloader Galaxy A51:
1. Setting >> About Phone
2. Software Information
3. Tap 7 times on build number, to enable developer options.
4. Tap back 2x.
5. Sroll down, tap developer options.
6. Enable (turn on) OEM Unlocking.
7. Enable (turn on) USB Debugging.
8. Turn off the phone.
9. Press and hold Vol Up + Vol Down, and connect USB Cable to PC / laptop.
10. Entering download mode.
11. Long press vol up
12. Press vol up again to Unlock Bootloader.
13. Factory reset
14. Welcome screen
15. Done.
Credit
@redymedan
Hello, after step 12 I get a green screen with some red letters above that say "error verifying vbmeta..." and now I can not restart the phone, any solution?
SOLVED
Nachopincha said:
Hello, after step 12 I get a green screen with some red letters above that say "error verifying vbmeta..." and now I can not restart the phone, any solution?
SOLVED
Click to expand...
Click to collapse
Just follow step by step in video
When I enter the blue screen before step 11, I just get a message saying "Downloading... do not turn off target" and it never goes away.
On my US model, I only get to step 5. Nothing after that. No OEM Unlock. Not sure who is blocking it; AT&T or Samsung or Qualcomm. So this might work in international models, but does not work on mine.
US model A51 5G
Model Number SM-A516U1
Brian D said:
On my US model, I only get to step 5. Nothing after that. No OEM Unlock. Not sure who is blocking it; AT&T or Samsung or Qualcomm. So this might work in international models, but does not work on mine.
US model A51 5G
Model Number SM-A516U1
Click to expand...
Click to collapse
US Model can't be unlocked
I'm stuck on the boot logo and don't know what to do
mohaibr said:
I'm stuck on the boot logo and don't know what to do
Click to expand...
Click to collapse
I dont know what you are doing to your phone
You can flash via ODIN and Stock ROM SAMSUNG
You can see how to flash via ODIN in Youtube
Nachopincha said:
Hello, after step 12 I get a green screen with some red letters above that say "error verifying vbmeta..." and now I can not restart the phone, any solution?
SOLVED
Click to expand...
Click to collapse
How do you solved it
can you share step by step
hey dude can you Help me
my device is showing imei 00000000 and cannot remember original csc version also bootloader cannot unlocked after pressing long vol + button in download mode it always say unlock bootloader when i did itjust reboot and factory rested and still no oem option grey out
my us model s515dl boots to a screen with green text saying entering fastboot and shows up under fastboot devices..can we work with that?
Good afternoon, can you help? And actually, what is the problem with a friend's child blocked Galaxy A51, tried to apply all the magic failed, since the developer mode is disabled and I can't turn on usb debugging, I've already tried everything to put a custom recovery and still in no way (to remove two files with blocking using Aroma fm) The path through Samsung unlock also disappears, since this beast went into flight mode after rebooting and does not turn anything on. I have already tried the very last option through attiny and otg password reseller, but it has already reached 4 minutes for one password and this method has also disappeared. I also sent it to ADB through the regular recovery, but the commands are very limited, and I didn't find anything useful either
irbis36 said:
Good afternoon, can you help? And actually, what is the problem with a friend's child blocked Galaxy A51, tried to apply all the magic failed, since the developer mode is disabled and I can't turn on usb debugging, I've already tried everything to put a custom recovery and still in no way (to remove two files with blocking using Aroma fm) The path through Samsung unlock also disappears, since this beast went into flight mode after rebooting and does not turn anything on. I have already tried the very last option through attiny and otg password reseller, but it has already reached 4 minutes for one password and this method has also disappeared. I also sent it to ADB through the regular recovery, but the commands are very limited, and I didn't find anything useful either
Click to expand...
Click to collapse
Try to flashing stock firmware
I am stuck on Entering Fastboot...
bootloader not opening please help me solve the problem

100% working Solution for m30s random freezing rebooting stuck at bootlogo.

Hello friends
As many of m30s user reporting random freezing while using and auto reboot on itself or sometime not even turns on by pressing and holding volume down and power key.
I too was mad at this hardware problem
I tried all possible ways like flashing old firmware or using aosp ,lineage os,but nothing was successful
Finally I tried one last method which was randomly tried
But that step unknowingly successful.
I have tested it many times without any previous behaviour.
Please check this link
hopefully it may work for you also.
i there. After (an attempt) to unlock the bootloader of my m30s and installing TWRP Recovery (TWRP_A50_Magisk_Prepatched) i find myself in an orange bootstate. I can't get it into recovery, download or fastboot mode. It seems like a full brick. I can't even power off the device. Only Volume up, Volume down and Power button let's the device reboot but then the same boot problems appear. Is there anything i can do to recover my phone?
Text of first screen when booting up:
"The phone's bootloader is unlocked and it's software integrity can't be verified. Andy data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone". Press power key to continue"
Text of second screen when booting up:
"The phone is not running Samsung's official software. You may have problems with features or security and you won't be able to install software updates"
Any ideas!?
Press and hold volume up and down and Connect to computer with drivers installed.
Flash stock rom using odin tool.

SM-T530 can't enter in Download mode (Recovery mode OK)

Deal All,
My first goal (before rooting, try custom rom etc.) is to update with official rom from Android 4.4.2 to 5.0.2.
Samsung Kies ask me to use SmartSwitch which said "your device can't be upgraded" or something like that.
As said in title, I cannot enter in download mode. Pressing Vol+ Home and Power display the usual warning message, Vol+ to continue / Vol- to cancel.
Pressing the Vol+ just reboot the tab.
Entering Recovery Mode work fine with Vol- Home and Power.
I found some info about an eventual "OEM lock" to turn off. I followed instruction but no way, no "OEM lock" appear in Dev menu...
The tab as been wiped thanks to the recovery mode.
Any idea?
Thanks!
Edit: Resolved, it was a faulty volume button
i had th same thing but on lte version i just went to settings, delevoper options, end unlock bootloader or smthing like that it magically started working
Thanks for your reply. Basically those are instructions I followed without success:
1 - Turn off the phone.
2 - Turn on the phone by holding down the volume up button.
3 - The phone will enter official recovery mode.
4 - Wipe cache partition.
5 - Wipe data/factory reset.
6 - Reboot system.
7 - Log in to your Google account and your Samsung account.
8 - Go to settings and enable developer mode.
9 - Enter developer mode, enable "OEM unlocking" option.
10 - Now you will be able to enter the DOWNLOAD mode
I can't find any settings in dev mode meaning "OEM unlocking" or "unlock bootloader"...
I tried also to communicate with Odin, but the tab is only detected in regular mode, not in recovery mode.
I know it's kind of old device, but I can't be the only one, a solution should exist...
Ok, so it's resolved, and was even more stupid than you may think: my physical volume button was faulty and didn't catch each time when I pressed Vol+ or Vol-. Using a small tool did the trick.

Categories

Resources