Greetings,
Both my devices are stuck in bootloop but they are facing different issues; details are as followed:
Devices Information:
- Manufacturer: SAMSUNG
- Devices Model: SM-J200GU
- Devices Nickname: j2lte
- Region: XME
- Firmware: J200GUDXS3AQG2
- Baseband: J200GUOLB3APC1
PC info:
WIndows 7 Ultimate SP1 with latest updates
Java 8 Update 144.
______________________________________________________________________________________
I know there are thousands of similar threads, most solutions I found were "enable USB debugging", "use ADB Fastboot", "reinstall drivers" and so on but trust me, I've tried every single options I could; few of them are:
REINSTALLED both Android and Samsung USB drivers (from version 1.3.8.5 to 1.5.6.3), whether you mean both installed together or separately
REINSTALLED Minimal ADB and FASTBOOT (1.3, 1.4, 1.4.2, 1.43)
TRIED using different versions of ODIN. (v1.85, v3.09, v3.10.6, v3.11, v3.12)
_____________________________________________________________________________________
Issue for Device #1: PC UNABLE TO DETECT DEVICE
Screen Options: Stock Recovery, Bootloader, Bootsplash/Bootlogo
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
FRP LOCK: OFF
SECURE DOWNLOAD: ENABLED
I have tried 3 different cables from SAMSUNG OFFICIAL, Lenovo and another off-market (REMAX) respectively on all the 8 USB PORTS that I have, and yes I have reinstalled the USB PORTS and also DISABLED and re-ENABLING it. I am able to boot into stock recovery but it's written "E: UNABLE TO MOUNT /SYSTEM" when I tried to perform HARD RESET. This only happens after I flashed the latest Firmware (J200GUDXS3AQG2).
_____________________________________________________________________________________
Issue for Device #2: PC ABLE TO DETECT DEVICE
Screen Options: Bootlogo/Bootsplash ONLY
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: OFFICIAL
FRP LOCK: ON
SECURE DOWNLOAD: ENABLED
No matter what key combination I pressed, IT ONLY BOOTS INTO BOOTLOADER MODE. Yes, not even a chance to peek at the BOOTSPLASH/BOOTLOGO screen. Stock firmware flashing was SUCCESSFUL but it BOOTS back to the damn same BOOTLOADER page (without all the details), able to flash TWRP (v2.87, v3.0.0, v3.0.2, v3.1.1) SUCCESSFULLY but FRP LOCK is ON.
_____________________________________________________________________________________
I hope the details given are sufficient enough for all you GRANDMASTERS, HACKERS, DEVELOPERS or even PASSER-BYs to provide me with a solution other than what I have done. In summary;
Device #1: PC unable to detect device, HARD RESET successful with ERROR "E: unable to mount /system".
Device #2: Tried flashing TWRP but FRP Lock ON, tried flashing stock firmware SUCCESSFULLY but boot into BOOTLOADER mode again, unable to enter stock recovery page or any other screens EXCEPT FOR THE BOOTLOADER.
_____________________________________________________________________________________
Thank you in advance & have a great day.
No one?
DaRdamnDoG said:
No one?
Click to expand...
Click to collapse
Have you tried using a different windows computer ?
George Malas said:
Have you tried using a different windows computer ?
Click to expand...
Click to collapse
Device #1 has been fixed, apparently another third party USB cable managed to get my PC to detect it in bootloader mode, the rest was easy.
As for Device #2, I was told by mobile shop owner that in recent months many of Samsung devices (especially Galaxy S7 variants and Galaxy Notes) had the same issue as I mentioned and he explains further that it is some sort of the manufacturers' effort or tactic to encourage mobile users to upgrade our devices.
How big of a ****ing asshole is Samsung to do such thing. Really ? They want to kill your ,quote on quote ,old device just so you can buy a new one. Just so I can clear things up in my mind , you mentioned above that you tried flashing TWRP on device #2 but FRP Lock was ON. But FRP Lock has nothing to do with TWRP. FRP Lock is Factory Reset Protection which purpose is to prevent someone from setting up the phone without knowing the credentials of the Google Account previously linked with the device. As long as your bootloader is unlocked , you can hop on TWRP ,flash a custom ROM and your problem should be solved.
Related
Hi everyone. I've had my I9305 for about a year now. When I got it, I rooted the phone. Now, I've been out of the rooting/custom ROM scene since then, and I'm trying my best to figure out how to do what I'm trying to do.
I want to make CyanogenMod my OS. After much researching and googling I've learned that the best way for me to continue is to restore my device to stock condition and start from scratch. This is after trying to boot into Download mode and trying to flash Clockwork Touch 6.0.3.1 .
Note: I've made sure all my connections are good, attached the USB cable to the back of the motherboard (no USB hubs) and tried different USB cords. The phone is fully charged. No SIM card or SD card in the device.
So far I've tried using Heimdall 1.4RC2 to flash CWT. It proceeds very quickly and does not show a blue progress bar on the phone.
I then tried to use ODIN to flash the stock recovery. That one also proceeds very quickly and does not show a green button until I remove the device from the computer.
Now, I can no longer boot the device. I get as far as the first Samsung logo and after half a second it disappears and turns off.
It might be valuable to note that I cannot boot into recovery mode. When I press the button combination I get the blue dialog above the Samsung logo but it disappears in half a second and the device appears to turn off. The reason I say it appears to, is because the screen turns black and the power button no longer turns it on until I remove and replace the battery.
Good news is I can still boot into Download Mode.
I really do not want to continue at this point because I am too afraid of bricking the device.
The phone is not vital, as I've bought an LG G2 to use as my main device and will not be rooting or fooling around with it.
I would more or less like to use this Galaxy S3 as a teaching tool.
I hope I've provided enough information and hope someone can be a guide for me!
Thx to all,
Mike
Hey,
Sounds like you are having a driver issue on your pc.
1. Charge your phone!!
2. Assuming you are using windows, try google for i9300 usb drivers. After installing flash philz recovery via odin and try to reboot to recovery.
Good luck!
Or you could install Samsung Kies to get the USB drivers.
Also, don't forget to turn on USB Debug mode in the developer settings.
A good resource I found when trying to root and install a custom recovery was Android Geeks. They have many tutorials. (disclaimer: I am not affiliated with Android Geeks at all)
I recommend you to root and install a custom recovery using ODIN. I've done precisely this, and I use CWM and have no problem. I've tried many roms and it works like a charm (currently on Temasek's 4.4 ROM).
>>>>>Also, don't forget to turn on USB Debug mode in the developer settings.
NONSENSE please read the faqs and guides first .
>>>>> I use CWM
No longer recommended please read the faqs and guides .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
JJEgan said:
>>>>>Also, don't forget to turn on USB Debug mode in the developer settings.
NONSENSE please read the faqs and guides first .
>>>>> I use CWM
No longer recommended please read the faqs and guides .
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Click to expand...
Click to collapse
This is where I am confused... After reading all of those two posts I'm still unsure about what to do.
I cannot boot into my device and therefore can not install proper drivers or enable USB debugging.
I have went ahead and installed "Samsung Galaxy S3 Unified Toolkit v7.0.0" to try and guide me along this complicated process.
After following the instructions given by the toolkit (to a tee) I am unable to get a serial number at the top of the menu, and therefore cannot continue with that program.
So is the first step in this whole process getting the recovery to work? If so, where should I start since I cannot even boot into it nor talk to my phone properly with my current drivers.
The only thing I have working right now is Download Mode.
The screen shows the following text:
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
I am unable to find the answer to my problem at this point...
If someone needs more information in order to help me don't hesitate to ask.
Thx everyone,
Mike
NOTE: I tried using the recovery.img file included with the above mentioned toolkit with Heimdall and I was able to successfully boot into recovery mode. I did a data cache reset and also a factory reset but I am still unable to boot into the android OS.
NOTE2: I downloaded the stock rom for my device, which I later found out was codenamed d2att or SGH-I747. Mine is actually the Canadian Bell SGH-I747M. Roms for the d2att still work on my phone though. So I flashed the ROM using ODIN after I installed the drivers using the zadig.exe file included with the Heimdall package. The flash worked like a charm. When my phone rebooted it immediately booted into recovery with some errors in red (those of which I can't remember). When I rebooted my device shows the glowing Samsung logo and stays there. It does not load into the OS.
u should search "softbrick" thread I think
thats happen to me in my first experience installing custom roms, in xda dont worry if u're phone softbrick or hardbrick. because there's answer in every problem u have. search search search, dont give up man!
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
You are in the wrong forum this forum is not your phone see sticky top of the page .
Flash nothing from this forum or you will brick your phone .This is I9300/05 forum not SGHI747M
JJEgan said:
ODIN MODE
PRODUCT NAME: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (18 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
You are in the wrong forum this forum is not your phone see sticky top of the page .
Flash nothing from this forum or you will brick your phone .This is I9300/05 forum not SGHI747M
Click to expand...
Click to collapse
My bad, I only found out half way through what phone I actually had. I will post in the right forum.
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli
Hello!
Okay so I recently updated my S9+ to the latest Android Pie version and I've cleaned up all of my stuff, so it's basically new.
When I enter download mode and plug it into my PC (Yes, I have the USB drivers installed as Odin 3.13.1 detects it) and try to flash twrp-3.2.3-0-star2lte.img.tar it leads to FAIL! A message in the phone screen appears after trying to flash: "only official released binaries are allowed to be flashed"
Already have enabled USB debugging and nothing. The only thing that seems weird to me is that I can't see the enable OEM unlock option in the developers tab. Maybe I have to wait the 7 day period as in Oreo 8.0? I doubt it because when I enter download mode, in the top left corner it appears "OEM lock: off"
So all in all, I don't know what to do, I'd like to flash TWRP in order to be able to flash a good Kernel (and maybe magisk root in the near future) which helps my phone to perform better and save as much battery as possible. I'm open to recommendations. If theres another way to flash the kernel (I've already tried ADB and Fastboot but my PC can't detect my phone connected when I do "fastboot devices" it doesn't matter if I'm in download mode or in the home screen, can't be detected either way and already tried to go to Device Manager but "Other devices" tab doesn't appear there.
Thank you so much and I hope you can lend me a hand
Please read the pie thread, this is mentioned many times. There is currently no Twrp image available for pie
Sent from my SM-G965U using Tapatalk
Pie is in a beta phase yet. Also, we are talking about builds coming in the last couple of weeks and to selected regions only. Under these circumstances, how would anyone except proper TWRP? Maybe after the final pie version, next year.
This is a quite common problem for pie beta firmware on S9(+). Try a factory reset or look for OEM Unlock 7 days bypass method on google to restore the OEM Unlock switch.
The OEM Lock status on download mode just seems to be always set to off.
Hello all, Ive been reading on these forums for years and ive always been able to find an answer using the search feature. However, Ive finally found a problem that I cant solve with a simple search. I was given a samsung galaxy j7 crown sm-s767vl that the person tried to remove an frp lock with miracle thunder. Now that I have it, It doesnt boot into android or recovery. The boot screen only says "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software." It will boot into download mode though. Ive tried the recovery function in smart switch, but to no avail. Ive downloaded multiple stock firmwares, combination files, and repair files for it. Ive also tried to flash it with just the stock boot .img and stock recovery.img with odin. no matter what I try to flash with odin I get the same error " Kernel rev check fail. DEVICE:5 BINARY:1 (recovery)". I know im just not getting the right firmware, I had a similar problem with a galaxy S8, but I had it when it would still boot into android so I was able to get the exact firmware needed. this j7 crown doesnt boot into anything but download mode. heres all the info I can get from download mode.
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME : SM-S767VL
CURRENT BINARY: SAMSUNG OFFICIAL
KG STATE: PRENORMAL
FRP LOCK: ON
Secure Download: Enabled
CARRIER_ID: TFN
WARRANTY VOID: 0 (0X0000)
RP SWREV: B:5 K:5 S:5
DID = 0537e6860ac
Any help or guidance you guys give me to finding the right firmware version or fix this problem would be greatly appreciated. I have fixed or rooted many android phones over the years and have bricked a few, but have always been able to recover them with the help of XDA solely. Or even possibly an explanation of what im seeing on the downloading screen that pertains to the right firmware version
thanks
[email protected] said:
Hello all, Ive been reading on these forums for years and ive always been able to find an answer using the search feature. However, Ive finally found a problem that I cant solve with a simple search. I was given a samsung galaxy j7 crown sm-s767vl that the person tried to remove an frp lock with miracle thunder. Now that I have it, It doesnt boot into android or recovery. The boot screen only says "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software." It will boot into download mode though. Ive tried the recovery function in smart switch, but to no avail. Ive downloaded multiple stock firmwares, combination files, and repair files for it. Ive also tried to flash it with just the stock boot .img and stock recovery.img with odin. no matter what I try to flash with odin I get the same error " Kernel rev check fail. DEVICE:5 BINARY:1 (recovery)". I know im just not getting the right firmware, I had a similar problem with a galaxy S8, but I had it when it would still boot into android so I was able to get the exact firmware needed. this j7 crown doesnt boot into anything but download mode. heres all the info I can get from download mode.
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME : SM-S767VL
CURRENT BINARY: SAMSUNG OFFICIAL
KG STATE: PRENORMAL
FRP LOCK: ON
Secure Download: Enabled
CARRIER_ID: TFN
WARRANTY VOID: 0 (0X0000)
RP SWREV: B:5 K:5 S:5
DID = 0537e6860ac
Any help or guidance you guys give me to finding the right firmware version or fix this problem would be greatly appreciated. I have fixed or rooted many android phones over the years and have bricked a few, but have always been able to recover them with the help of XDA solely. Or even possibly an explanation of what im seeing on the downloading screen that pertains to the right firmware version
thanks
Click to expand...
Click to collapse
Search the imei number. You will be give all of the information about the device, including the stock firmware
Signing boot images for Android Verified Boot (AVB) [v8]
Various Android devices support Android Verified Boot (AVB). A part of this is more commonly known as dm-verity, which verifies system (and vendor) partition integrity. AVB can however also verify boot images, and stock firmwares generally...
forum.xda-developers.com
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Didn't work for me, I tried with the AOSP_super.tar, which succeeded, but got a boot loop.
I tried with the AP_AOSP_.., but it fails, I got "Only official released binaries are allowed to be flashed (SUPER)". The same occurs with Havoc tar.
When I tried the AOSP_super.tar again, I got the same message, instead of a boot loop.
Steps:
Unlock bootloader (OEM unlock is also permanently triggered in developer settings)
Power off phone
Download mode (volume up + power on) and connect USB
Load tar file in AP slot (other slots are empty)
Factory reset and clear cache
Flashing back the stock rom still works. Stock rom: A217FXXU5BUB4
Any ideas?
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Is there a way to install Havoc OS prerooted?
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Yeah I think I know why, There's a filesystem problem, the UUID and filesystem has to be the same as the system.img of OneUI
The UUID depends in the device binary that you have (in the firmware)
I'd help you but, all my steps just led to a dead end sadly
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Hi i flash havocos but not reboot in rom reboot in download mode help please
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Can you make a unrooted gsi? If you could please use dot os 5.2 it would mean world for me. The community also i think.
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
EatABRick said:
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
Click to expand...
Click to collapse
It worked, but with older version of OneUI installed. I don't have this phone anymore but maybe i can help