I've been doing at least 2 years of research trying to figure out even the slightest possibility of rooting Qualcomm chipsets, and I think I might've found it. Does anyone here think it's possible to use QPST and EDL to flash a modified stock rom with SuperSU in the system directory to root a locked bootloader?
What device are you trying to root
vanish0104 said:
What device are you trying to root
Click to expand...
Click to collapse
A42 5G purchased from Verizon.
qwiri said:
A42 5G purchased from Verizon.
Click to expand...
Click to collapse
Samsung Galaxy A42 5G
The Samsung Galaxy A42 5G is a 6.6" phone with a 1080x2400p resolution display. The Qualcomm SM7225 Snapdragon 750 5G chipset is paired with 4/6/8GB of RAM and 128GB of storage. The main camera is 48+8+5+5MP and the selfie camera is 20MP. The battery has a 5000mAh capacity.
forum.xda-developers.com
If the bootloader is unable to be unlocked then you can't root it. It's that simple.
vanish0104 said:
Samsung Galaxy A42 5G
The Samsung Galaxy A42 5G is a 6.6" phone with a 1080x2400p resolution display. The Qualcomm SM7225 Snapdragon 750 5G chipset is paired with 4/6/8GB of RAM and 128GB of storage. The main camera is 48+8+5+5MP and the selfie camera is 20MP. The battery has a 5000mAh capacity.
forum.xda-developers.com
If the bootloader is unable to be unlocked then you can't root it. It's that simple.
Click to expand...
Click to collapse
Not necessarily. I can guarantee it's possible to root it because you can in fact load ROMs without unlocking the bootloader. I'm just curious if you can force the rooted rom into the system without the bootloader rejecting it.
Yeah, sure... if you can crack the EDL protocol instead.
AFAIK (at least on OnePlus) it lets you write to all flash partitions, and I'd assume that also means the ones that hold the crypto signatures used in trusted boot. You certainly could modify certain partitions, sign everything again, and create an image if you knew the format. Not listed in AOSP, though, like building your normal custom ROM.
Disclaimer: I've only ever gotten a custom OS with locked bootloader on Pixel, though (Calyx OS, modified with a few OS code changes and the Magisk stack) but I don't think that's a QC phone to have EDL in the first place.
Now Samsungs are notorious for the e-fuses and whatnot, so it may be they have some asinine defense against it... I stopped dealing with vendors that don't outright support custom ROMs (basically down to OnePlus, Google, and Asus if you can afford one). My life has been much easier for that.
Now of those, Verizon usually has a custom firmware to support their bands, which DOESN'T let you unlock bootloader. Some people have reported on some (OnePlus) phones flashing the international rom via EDL lets you overwrite that... but not sure if it loses the 5G mmWave and sub6 bands or whatever VZW uses that the rest of the world does not have.
Hope that helps...?
qwiri said:
Not necessarily. I can guarantee it's possible to root it because you can in fact load ROMs without unlocking the bootloader. I'm just curious if you can force the rooted rom into the system without the bootloader rejecting it.
Click to expand...
Click to collapse
A locked bootloader means that it will refuse to load unsigned code. It's checking for system integrity and rooting/loading a custom ROM will always trip this check unless the custom ROM has the proper signature and I highly doubt it does.
Verizon phones are known for being locked down. There is nothing you can do.
vanish0104 said:
A locked bootloader means that it will refuse to load unsigned code. It's checking for system integrity and rooting/loading a custom ROM will always trip this check unless the custom ROM has the proper signature and I highly doubt it does.
Verizon phones are known for being locked down. There is nothing you can do.
Click to expand...
Click to collapse
I am definitely aware of that, but if you aren't flashing a *custom* rom and are just using a stock rom with added files, does that still change the integrity?
SomeRandomGuy said:
Yeah, sure... if you can crack the EDL protocol instead.
AFAIK (at least on OnePlus) it lets you write to all flash partitions, and I'd assume that also means the ones that hold the crypto signatures used in trusted boot. You certainly could modify certain partitions, sign everything again, and create an image if you knew the format. Not listed in AOSP, though, like building your normal custom ROM.
Disclaimer: I've only ever gotten a custom OS with locked bootloader on Pixel, though (Calyx OS, modified with a few OS code changes and the Magisk stack) but I don't think that's a QC phone to have EDL in the first place.
Now Samsungs are notorious for the e-fuses and whatnot, so it may be they have some asinine defense against it... I stopped dealing with vendors that don't outright support custom ROMs (basically down to OnePlus, Google, and Asus if you can afford one). My life has been much easier for that.
Now of those, Verizon usually has a custom firmware to support their bands, which DOESN'T let you unlock bootloader. Some people have reported on some (OnePlus) phones flashing the international rom via EDL lets you overwrite that... but not sure if it loses the 5G mmWave and sub6 bands or whatever VZW uses that the rest of the world does not have.
Hope that helps...?
Click to expand...
Click to collapse
Thanks for that. I honestly don't mind losing 5G, it's constantly an unstable connection anyways. I've been considering just buying a Pixel from overseas, but I've been chipping away at this for too long and am probably gonna keep trying.
I'd be ok with manually resigning everything if it meant rootable for QC Verizon chipsets.
qwiri said:
I am definitely aware of that, but if you aren't flashing a *custom* rom and are just using a stock rom with added files, does that still change the integrity?
Click to expand...
Click to collapse
Yes. Changing one *bit* of any file will always change the integrity.
vanish0104 said:
Yes. Changing one *bit* of any file will always change the integrity.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vanish0104 said:
Yes. Changing one *bit* of any file will always change the integrity.
Click to expand...
Click to collapse
As mentioned above:
You certainly could modify certain partitions, sign everything again, and create an image if you knew the format.
Click to expand...
Click to collapse
If I could manage this, would it still be possible? I understand this isn't documented in AOSP.
qwiri said:
I'd be ok with manually resigning everything if it meant rootable for QC Verizon chipsets.
Click to expand...
Click to collapse
Doing it (re-signing) with CalyxOS was quite a challenge the first time (but cool as hell to cut your own OTA deltas after the fact, without needing to unlock or flash user partition!), can't fathom doing it with Samsung esp considering AOSP is just the start, you still have binary blobs for the radio, etc. I never figured out how to get raw partitions out of Fastboot (which wouldn't require root, at least on my phones) to get those blobs with an unsupportive vendor. After that, then make the EDL image, which I assume ALSO has a crypto signature with keys not available to sign with (but, y'know, there are ways around everything).
Like I said, I just gave up and went with supporting a phone vendor that wasn't fighting me... much easier and I still have all my customizations (e.g. root + annoyance free) with the security of a locked bootloader.
I *THINK* (maybe gsmarena.com can validate) that the Pixel 6 is like the iPhone and includes the VZW bands in the unlocked version. Buying the unlocked direct from Google shows "set up with any major carrier later", so I assume that includes VZW too.
PS: the fingerprint sensor on front sucks major, and you don't get the 50MP camera in the API used by the open source cameras... I returned the 6 and went with a 5G... but I don't think that one includes the sub6/mmW bands in the universal version.
qwiri said:
As mentioned above:
If I could manage this, would it still be possible? I understand this isn't documented in AOSP.
Click to expand...
Click to collapse
You would need the keys from Verizon to sign it yourself.
vanish0104 said:
You would need the keys from Verizon to sign it yourself.
Click to expand...
Click to collapse
Alright. Thanks for your help
I'll try out a few methods and bump the thread if it works
vanish0104 said:
You would need the keys from Verizon to sign it yourself.
Click to expand...
Click to collapse
If you had the Verizon keys you could just do the system partition mods, sign, and reflash with fastboot, or even better, a OTA delta image of the su/magisk package.
I think @qwiri 's question is could you use EDL to get a layer lower than the Android trusted boot- which you certainly could, or at least on a OP phone. But... you'd have to be able to do the entire image, signing EVERYTHING as you'd be replacing the keys, too. Totally possible, just hard- but THEN you'd have to reverse engineer EDL mode images, which I assume is signed by someone at QC. That may be possible- sign up as a developer, OEM, whatever, social engineer it. But probably more expensive than just buying a phone that LETS you flash keys without EDL (if you want trusted boot) or just unlock the bootloader to permit custom partitions (if you don't have the wherewithal to get an AOSP build environment and do it from scratch)
Related
I just won an S8+ on eBay only to realise that it was Google blocked... I haven't paid for it yet but I did do a check if it was blacklisted or stolen and it comes up clean...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks like it needs the FRP reset method done. This is my first post on the S8 forum, and starting research on the S8, as I have one arriving next week
I just did an FRP reset on an S7 Edge. It took me several days, all day long, to finally find the method which worked on my phone. There are a lot of videos and posts with various methods... egads.
Once that method was processed, it took about 30 minutes to finally have the FRP gone and the soft reset finalize it.
If the seller on eBay did not advertise it as being Google account locked, you may want to consider a refund. Given the hardware is all ok (?), you might/should be able to un'FRP it. As I just looked at a few google search results, seems similar to the S7 method. I wonder why the seller did not un-F(a)RP it?
Do a Google search for 'S8 FRP Bypass'.
Can I just re flash stock firmware and then custom Rom?
BL4CK-H4T said:
Can I just re flash stock firmware and then custom Rom?
Click to expand...
Click to collapse
Good question. I asked that as well and never got an answer... frustrating, so I am not sure.
My thinking leads to 'why not', as a full re-flash I'd think also writes over the Persistence directory/file, however, if it were that simple I'd a thought I would have come across a post, how-to or video, or post reply to my questions, stating yes, it can be solved in that manner.
So my post research and experimentation experience thinks once the FRP is tripped, the system prevents a simple flashing over of the Persistence partition/file with stock.
---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------
I just posted a response... TWICE, where'd it go.
---------- Post added at 02:23 PM ---------- Previous post was at 02:19 PM ----------
Wow, that message posting lag has been about 10 minutes! I sent you a PM.
Yeah because my bosses S7 I put him a custom Rom Batman Rom and I forgot to tick oem unlock and debugging and it went into FRP LOCK...
I can't remember what we did but we never used combination thingy...
I just remember putting the stock firmware on and it worked
S8 plus
tnap1979 said:
hey guys..
both you, message me, ive done both s7 and s8, recently... very easy
Click to expand...
Click to collapse
How?
Ok so I got this phone frp unlocked remotely, but the imei number on the phone back and box is the same but the phone itself *#06# comes up as dual SIM G955FD...
The phone finds the sim but still says no service I have flashed multiple csc files but still no luck so what's the issue I spent so much time and money in this poop fone
Is it 'supposed' to be a dual SIM phone by OEM model?
If so does it have the original stock firmware on it, or if not what has it been changed to.. ?
My S8+ suddenly stopped working because it says "FRP Locked". So the phone won't even boot.
Any advice?
You can I stall the factory binary to bypass frp. And it's that simple.
TheMadScientist said:
You can I stall the factory binary to bypass frp. And it's that simple.
Click to expand...
Click to collapse
Mad Scientist, so when you (re)install the factory binary, it overwrites the Pervasive, or what ever it is called, partition as well, which holds the FRP breach/info?
I did not think that worked, as it was too obvious and too easy a fix.
Please clarify.
JeffDC said:
Mad Scientist, so when you (re)install the factory binary, it overwrites the Pervasive, or what ever it is called, partition as well, which holds the FRP breach/info?
I did not think that worked, as it was too obvious and too easy a fix.
Please clarify.
Click to expand...
Click to collapse
The s8 factory combo test firmware does yes....
It did on mine when I changed my google password and fac reset Its a snapdragon right.....
Some people also install the eng boot and google frp adb bypass command...
TheMadScientist said:
The s8 factory combo test firmware does yes....
It did on mine when I changed my google password and fac reset Its a snapdragon right.....
Some people also install the eng boot and google frp adb bypass command...
Click to expand...
Click to collapse
OK, Snapdragon only, then. Thanks for that info.
Is there a simple method, like that one, for Exynos?
JeffDC said:
OK, Snapdragon only, then. Thanks for that info.
Is there a simple method, like that one, for Exynos?
Click to expand...
Click to collapse
Ahhh yes. I do not know as I havn't had one to try.
Hi.
I bypass it fith Combination FW.
I forgot password and flash combination then stock rom and all fine.
Here is combination for 955f/fd
https://androidfilehost.com/?fid=745425885120753748
marvin_666 said:
Hi.
I bypass it fith Combination FW.
I forgot password and flash combination then stock rom and all fine.
Here is combination for 955f/fd
https://androidfilehost.com/?fid=745425885120753748
Click to expand...
Click to collapse
Interesting. I would have though there was a software/OS method, but then I thought that Samsung would have made entrance into the Persistence partition like a vault door.
So am I understanding you all, an Exynos phone can be flashed with a combination file(?), and afterwards the OEM ROM, and that deletes the FRP file/Persistence partition? What slot would the combo file be used with in Odin?
I learn something new every day.
The problem is, I forget at least two things I've learned, every day
Thanks.
JeffDC said:
Interesting. I would have though there was a software/OS method, but then I thought that Samsung would have made entrance into the Persistence partition like a vault door.
So am I understanding you all, an Exynos phone can be flashed with a combination file(?), and afterwards the OEM ROM, and that deletes the FRP file/Persistence partition? What slot would the combo file be used with in Odin?
I learn something new every day.
The problem is, I forget at least two things I've learned, every day
Thanks.
Click to expand...
Click to collapse
Yes. You need to flash it as AP and flash Home Csc from your FW. Then you must go to setting and apply usb debugging. Then flash your Fw and you can to log in with other google account.
My advice is ... stop buying stolen phones = stopping phones being stolen.
s327374 said:
My advice is ... stop buying stolen phones = stopping phones being stolen.
Click to expand...
Click to collapse
You can (actually) legally purchase once stolen phones, and they come out legit from a court ordered police property room auction.
s327374 said:
My advice is ... stop buying stolen phones = stopping phones being stolen.
Click to expand...
Click to collapse
Or, if you're like me, you buy broken phones. Phones with shattered screens and non-responsive LCDs, that the previous owners sell trying to recoup some of their money rather than pay to repair it themselves. Often when I replace the screen, I'm faced with FRP lock.
One time, I sold a phone I purchased brand new and owned legally. Sold it on Swappa to a guy in Florida (I'm in Oklahoma). What did my stupid ass do? I forgot to remove my account before resetting it, thus tripping the FRP.
So you CAN actually legally buy a legitimate, not stolen phone, and have FRP on it.
Read the first 3 posts before you proceed.
For Android 10 go here
https://forum.xda-developers.com/galaxy-a20/how-to/android-10-q-guide-a20-t4095589
For a20e go here
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!
Advantages of rooting:
Once you root your device you can install flashable zip files and custom ROMs.
You can backup all your apps and data using Titanium Backup.
You can customize your device according to your needs by deleting unwanted system apps and using Deathly Adiutor to modify the kernel.
View attachment 4802662
Disadvantages of Rooting:
Once you root your device, your device warranty will be void.
After rooting yourndevice may become unstable.
You may not be able to upgrade OTA in the future.
This method should root your Samsung Galaxy SM-A205X (all models except SM-A205U and SM-A205DL).
It was developed for the U2 bootloader (June 2019 firmware)
This method does not work for the a20s (A207X)
This method can be used to root other Samsung phones including the a20e( post#77 post#180, post#256)
Quick Root and TWRP for A205xx
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
You'll find it much quicker.
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verify
4. Root instructions and unpatched boot images
https://www.full-repair-firmware.com/search?q=A20
More firmware (some are even prerooted)
https://www.needromarab.com/1/122/SAMSUNG
Samfirm Tool for really fast downloads
https://samfirmtool.com/samfirm-v0-5-0
Useful videos
Instructions
A. Prepare boot image
1. Download magisk manager apk
2. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
https://samfw.com/
3. Use zarchiver to copy AP_20xxxxxxxx.md5 to download directory. It will extract it from the zip.
4. Rename AP_20xxxxxxxx.md5 to AP_20xxxxxxx.tar and extract using zarchiver
5. Copy boot.img.Iz4 to download directory and extract (resulting in boot.img)
6. Use magisk manager to patch boot.img (use top install) result magisk_patched.img
(If using Magisk (Canary) patch, options should be remove dm-verity and not via recovery, but allowing Persist Encrypt.)
7. Rename magisk_patched.img to boot.img
9. Use zarchiver to compress boot.img to boot.tar. If you have a A205xx June firmware (U2 bootloader), you can use my one of you're willing to take a risk. View attachment boot.zip. Just unzip it first.
9a. For a20e users, try this boot.img https://forum.xda-developers.com/showpost.php?p=81649257&postcount=260
10. Copy boot.tar to Windows pc or Windows Virtualbox.
11. On phone developer options in settings unlock OEM and enable usb debugging
(If using Linux
9. Don't compress `boot.img`
10. install heimdall flash with `sudo apt install heimdall-flash`, if you want front-end install it with `sudo apt install heimdall-flash-frontend`)
B. Unlock bootloader
Useful video
12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release vol up to enter unlock screen.
15. Follow the instructions to unlock
(You might need to long press vol up to unlock bootloader)
vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.
C. Flash boot image.
19. Turn phone on in bootloader (download) mode (Hold power and vol+ to enter recovery mode then select bootloader download mode)
20. Connect phone to computer.
21. Use Odin in Windows to add boot.tar to phone. (Select AP). Some people recommend adding the other firmware parts to their slots at the same time.
22. Restart phone
23. select bootloader
24. Select factory reset (this will wipe data)
25. Restart phone
26. install data
26. install magisk manager
27. If green phone is rooted.
View attachment 4802665
28. Of red select install/direct install
29. Advanced tick both.
30. Install root checker and verify root
If Something Goes Wrong
Go here
https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369
If you get a DTBO error after updating Magisk, flash this vbmeta https://drive.google.com/file/d/1-dogButfxKGlx_x2tSROOBDiq90SDlmc/view
(If using Linux
To flash:
20. Detect device with `heimdall detect`
21. Flash the `boot.img` with `heimdall flash --BOOT {location of the boot.img, you can also just drop the file into terminal and terminal should auto-fill it}` ex: `heimdall flash --BOOT '/home/utku/Programlar/ext/boot.img'`
P.S: an easy way to boot into download mode is `adb reboot bootloader`)
If you want to remove the warning messages on the boot screen
try this.
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
The images shown on the A30 thread aren't suitable for the A20 so I have included some better ones here.
View attachment 4803752
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can use this param.tar to make these changes easier.
https://forum.xda-developers.com/showpost.php?p=80169262&postcount=91
You can now move on to install TWRP
This TWRP was originally designed for Android 9 but works perfectly with Android 10 and also has MTP built-in.
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com
Mine
Discussion page.
https://forum.xda-developers.com/t/samsung-galaxy-a20
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
jajk said:
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
Click to expand...
Click to collapse
Another reason to merge. This is a procedure for removing those annoying error messages on startup screens.
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Please, need magisk_patched.img file for SM-A205F.
jajk said:
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Click to expand...
Click to collapse
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
jhjhjhjhjhjh said:
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^THIS ALL DAY. I swapped mine out for the G7 Power and already done rooted, flashed, and wrote a guide while all the 205u users are waiting for the mythical OEM Unlock to magically appear which it ain't gonna. Sammy can kiss my techie ass...we are officially divorced. I won't even go back and buy an old Sammy like I wanted to (was thinking about getting that S7 edge). It's me and Moto for now.
jhjhjhjhjhjh said:
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
Maybe Samsung has an issue with US tariffs.
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
jajk said:
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
Click to expand...
Click to collapse
I used titanium backup first. Now I'll debloat.
physwizz said:
Maybe Samsung has an issue with US tariffs.
Click to expand...
Click to collapse
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Articul8Madness said:
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Click to expand...
Click to collapse
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
physwizz said:
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
Click to expand...
Click to collapse
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Articul8Madness said:
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Click to expand...
Click to collapse
Mine is locked to Vodafone but I can still unlock the bootloader.
physwizz said:
Mine is locked to Vodafone but I can still unlock the bootloader.
Click to expand...
Click to collapse
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
burningcreation said:
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
Click to expand...
Click to collapse
I've downloaded the 2 pics and I modified one to contain my name.
I will try the mods shortly.
First, let me apologize for the rough guide I'm going to deliver I'll clean this up in due time.
1.) Let's get some files downloaded. So here is a guide by @deadman96385 that details Qfil and the actual process of flashing.
2.) Let's incorporate that into my guide
* You'll choose the programmer from my TWRP folder
* You'll choose the rawprogram0.xml from my TWRP folder
3.) Time to flash....just press Download there's nothing else to do.
4.) Boot into recovery...do I need to explain how?
* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.
So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.
good work @Unjustified Dev And @deadman96385
ff7cloudsnobody said:
So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.
Click to expand...
Click to collapse
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Unjustified Dev said:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Click to expand...
Click to collapse
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!
ff7cloudsnobody said:
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!
Click to expand...
Click to collapse
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my G8142 using Tapatalk
Unjustified Dev said:
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.
Click to expand...
Click to collapse
Does going the old "data wipe then flash boot img without encryption" not work anymore? If so then my bad, been a while since I've worked with a phone that is locked down with signed firmware. Was looking into doing that right now.
Edit: And I don't mean via flashboot because first boot should cause it to resign
AT&T
Unjustified Dev said:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
Click to expand...
Click to collapse
Hello!
Thank you for the first ray of light Please, can you answer some questions?
1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?
2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?
3) If all of these works, can root be (some day) obtained with locked bootloader?
I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You
Thanks once again,
WBR - Draco.
Drakosha said:
Hello!
Thank you for the first ray of light Please, can you answer some questions?
1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?
2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?
3) If all of these works, can root be (some day) obtained with locked bootloader?
I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You
Thanks once again,
WBR - Draco.
Click to expand...
Click to collapse
1.) I have the att variant
2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.
3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
Sent from my G8142 using Tapatalk
Great!
Unjustified Dev said:
1.) I have the att variant
2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.
3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Thanks for the answers! Wonderful news, the ability to flash AT&T phone with QFill changes everything. As for the bands, I've seen a lot of articles on how to unlock Qualcomm phones with NV editor, and had success with several Nexus-es & LG's. Let's hope that after (if...) root is obtained, one of the methods works. It will literally breath the new life into this phone & will make it useful everywhere in the world.
WBR, Draco.
Just an FYI, only running this didn't work for me, I changed the img to recovery.img and used the firehose with the stock files, I edited the boot though to remove secure boot.
Root
Unjustified Dev said:
* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.
Click to expand...
Click to collapse
Hello!
Any news on root or, perhaps, some ROM like Lineage?
WBR, Draco.
Any News?
So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?
ehsan96696 said:
So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?
Click to expand...
Click to collapse
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
Sent from my G8142 using Tapatalk
Unjustified Dev said:
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
Thanks, I did get past that error, but now it is stuck at https://imgur.com/YzyzPNP
ehsan96696 said:
Thanks, I did get past that error, but now it is stuck at
Click to expand...
Click to collapse
Use miflash
Sent from my G8142 using Tapatalk
Unjustified Dev said:
Use miflash
Sent from my G8142 using Tapatalk
Click to expand...
Click to collapse
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"
rawprogram0.xml
ehsan96696 said:
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"
Click to expand...
Click to collapse
Here, just use the attached rawprogram0.xml (AT&T B37) with QFil
Drakosha said:
Here, just use the attached rawprogram0.xml (AT&T B37) with QFil
Click to expand...
Click to collapse
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h
ehsan96696 said:
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h
Click to expand...
Click to collapse
Do you have spaces in your username? Put firehose programmer file inside the firmware folder, and put the whole folder in C:\Z999 (without any spaces or long filenames). Run Qfil as admin. And never flash phones from DESKTOP...
I have a several months old s10e, which turned to have no updates (Android 10, UI 2.0, security patch level March 2020(!) although was bought around April 2021). Not even an available "check for updates" button, anywhere. This is some real downer here, with Samsung semi-Android OS. I'm dealing with this issue for several weeks now, when I expected to simply update my device via OTAs.
Also verified with local Samsung service, according to IMEI, should be Android 11.
Anyway, as I found here,
S10e not receiving updates
Hi all, I'm a long time Samsung user (started with an S2, then S4, S7 and now S10e) though this is my first post here. I'm in the UK. A couple of years ago, I bought a Samsung Galaxy S10e from an ebay seller. It all worked fine and the whole family ended up getting S10e's to replace their aging...
eu.community.samsung.com
I've downloaded the correct firmware from Sammobile:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and followed the instructions: https://www.sammobile.com/wp-content/themes/sammobile-6/assets/static/instructions-fw-5file.pdf
During flash on Odin3 v3.14, process get stuck at "recovery.img" while on device's screen, "Secure fail check : (Bootloader)" is writen on red;
with no process bar shown on phone's screen. Next four lines happen when I exit "Download Mode". Tried different USB port, different cable, one prior firmware version (July 2021 release instead of Sep 2021) etc. Many times, same results.
BTW, "Download Mode" model (product name) and "about phone" model number are different: SM-G970N on "Download Mode" upper left corner of the screen (see image above), SM-G970F on "about phone" model number. Could it be that I've downloaded the wrong firmware (one shown under "about" menu)?
Checked "Phone info plus" app, I see that phone model (G970F, Israel) is different than CSC product code (G970N, Vietnam).
I've sent the device to a lab (warranty service). It was returned after over a week, with the exact same status + factory reset. I'm furious.
Do I have a 970F or 970N device?! Which exact firmware should I download\upload?
Any ideas?
Thanks in advance
avner.niv said:
I've sent the device to a lab (warranty service). It was returned after over a week, with the exact same status + factory reset. I'm furious.
Do I have a 970F or 970N device?! Which exact firmware should I download\upload?
Any ideas?
Thanks in advance
Click to expand...
Click to collapse
Your device is N and therefore will only accept N firmware
iBowToAndroid said:
Your device is N and therefore will only accept N firmware
Click to expand...
Click to collapse
Thanks for the super-fast reply!
Can you please tell me which one should I look for on SamMobile.com, i.e. which country should I look for?
And - would it be a problem, trying to install N firmware while the device is (for some reason) defined as an F under device model (about menu)? Why is there such a discrepancy?
avner.niv said:
Thanks for the super-fast reply!
Can you please tell me which one should I look for on SamMobile.com, i.e. which country should I look for?
And - would it be a problem, trying to install N firmware while the device is (for some reason) defined as an F under device model (about menu)? Why is there such a discrepancy?
Click to expand...
Click to collapse
1. Doesn't matter which country you choose
2. No, it won't be a problem. There's a discrepancy because the device was rooted and modified to look like an F model
iBowToAndroid said:
1. Doesn't matter which country you choose
2. No, it won't be a problem. There's a discrepancy because the device was rooted and modified to look like an F model
Click to expand...
Click to collapse
Thanks again, I'll try and hope for the best..
About 2, if the device was rooted to look like an F model, will it change anything else (for an example - carrier related issues due to not looking like F anymore)? Is there a potential risk with "changing it back to N"? Why was it reasonable to modify it to look like an F at the first place?
avner.niv said:
Thanks again, I'll try and hope for the best..
About 2, if the device was rooted to look like an F model, will it change anything else (for an example - carrier related issues due to not looking like F anymore)? Is there a potential risk with "changing it back to N"? Why was it reasonable to modify it to look like an F at the first place?
Click to expand...
Click to collapse
You always take a risk, every time that you purchase a used device. You can't inherently damage the device by re-flashing the official stock firmware. But a used device is never guaranteed to work the way you want it to, and it carries no warranty. So you'll just have to do the flash and then try it and see what happens
I have no idea why it was reasonable. You would have to ask the person that you got it from
iBowToAndroid said:
You always take a risk, every time that you purchase a used device. You can't inherently damage the device by re-flashing the official stock firmware. But a used device is never guaranteed to work the way you want it to, and it carries no warranty. So you'll just have to do the flash and then try it and see what happens
I have no idea why it was reasonable. You would have to ask the person that you got it from
Click to expand...
Click to collapse
Actually, it is not a used device, at least for the best of my knowledge.. I've bought it as a new device, although not from the local official importer. You say that this rooting and model modification means that the device is used?
avner.niv said:
Actually, it is not a used device, at least for the best of my knowledge.. I've bought it as a new device, although not from the local official importer. You say that this rooting and model modification means that the device is used?
Click to expand...
Click to collapse
Samsung (nor any other manufacturer) does not sell rooted and modified devices. So yes, of course it is used. The S10e is more than 2 years old anyways, so it would be almost impossible to find one that is still brand new sealed in the box
iBowToAndroid said:
Samsung (nor any other manufacturer) does not sell rooted and modified devices. So yes, of course it is used. The S10e is more than 2 years old anyways, so it would be almost impossible to find one that is still brand new sealed in the box
Click to expand...
Click to collapse
well. where i live there are operators who still sell them brand new, but only difference, if i bought it 3 jears back for 490, now price are 700, so ridiculous!!
hi
gotta jump on this thread too,
I have the exact same issue, bought the phone brand new from an online store in Israel and can't get updates, can't use the Samsung camera app(had to use a different app for it) and recently the mic stops working suddenly and comes back only if I enter safe mode. If i flash the phone with the n fimware will it work normally?
GGisme said:
hi
gotta jump on this thread too,
I have the exact same issue, bought the phone brand new from an online store in Israel and can't get updates, can't use the Samsung camera app(had to use a different app for it) and recently the mic stops working suddenly and comes back only if I enter safe mode. If i flash the phone with the n fimware will it work normally?
Click to expand...
Click to collapse
If your Baseband Version starts with G970N, then yes, probably
Hi
Thanks for the quick reply
I have flashed(with odin 3.14) the latest firmware according to the baseband version(g970n) and now the same problem persists with a warning message in Korean every time I turn on the phone and also skmobile animation. At least now the phone is capable of updating and is up to date with android 11 and one UI 3.5, and also, the about phone shows the correct model. Any idea how to fix the initial problem? (mic stops working, camera fail on Samsung stock app)
It’s funny how the warranty just expired a few days ago
GGisme said:
Any idea how to fix the initial problem? (mic stops working, camera fail on Samsung stock app)
It’s funny how the warranty just expired a few days ago
Click to expand...
Click to collapse
Sounds like hardware defect
Thanks for your help
just change the date to 2018 or 2019 with november 1
It's been a while even since the last message. I have to inform anyone who wishes to update their firmware to Android 12. You may prefer living with your Pie firmware because the Camera started to add some foggy effect on the captured images for no reason on my device after one of the updates -very likely after an April update at the time. I know because I'm not the only one with this. There are many complaints on this on the Samsung website and no one seems to care.
As far as I can guess, it is related to some effect added to the capured images during or after shooting. It resembles the photoshop effect Convert to HDR, creating some bright areas around edges while the remaining remaining image is foggy. How stupid of Samsung.
May be they just want you to replace a 4 year old phone, asuming you'll again buy a Samsung, even with the imposed circumstances.
Been a Samsung user for years but I'm looking for some other brand for my next phone due to this kind of Factory-Forced replacing necessities. Either your phone gets laggy in a year or two, or your battery inevitably dies and you can not find a single replacement one, roughly on a par with the original. I've tried dozens of different brands including the official service replaced battery. Your phone no longer runs as long as the first day you bought it and you eventually replace your phone.
Still having this crap device in my posession, I wonder if I can revert back to Android 9 Rom from Android 12? Or any ideas on this camera issue? (It happens on any other camera)
Byteman3D said:
I wonder if I can revert back to Android 9 Rom from Android 12?
Click to expand...
Click to collapse
Nope
iBowToAndroid said:
Nope
Click to expand...
Click to collapse
Your statement was so certain that İ'm baffled. I have installed custom roms before too many of my previous devices. Does this device NOT accept custom firmware or any previous version firmware anymore?
no chance with official firmware because the boatloader can not be downgraded
Byteman3D said:
Your statement was so certain that İ'm baffled. I have installed custom roms before too many of my previous devices. Does this device NOT accept custom firmware or any previous version firmware anymore?
Click to expand...
Click to collapse
1. No device will accept any custom firmware without being bootloader unlocked. You never specified which device you have, so I don't know if it can be bootloader unlocked or not
2. Even if it can be bootloader unlocked, I highly doubt that an Android 9 custom ROM will boot on it, since its underlying firmware would be either Android 12 or Android 11
Phone: Redmi Note 11 Pro (IMEI search shows model number 21091116C sticker that came with phone shows model number 21091116SG not sure if this matters)
I have accidently patched and written the wrong boot.img to my phone after poorly attempting to setup Magisk to get google pay working on this phone
Am now stuck with the phone either booting to recovery window or I Can enter fastboot
Device bootloader is locked and i do not have a Xiaomi account linked to phone, trying to flash what i believe is ROM using MiFlash tools but fails since bootloader is locked, attempted to unlock using mediatek unlocker tools and cant manage to get this to work either
Feels like there's nothing i have not tried at this point have 20 chrome tabs open, downloaded so many different ROMs and followed heaps of different methods without any success
Edit: Account had not been linked to phone yet
Apologies if this is not posted in the correct format/section believe its right from the rules
Any help would be really apprechiated
I would think MiFlash should still work on a locked BL from EDL. What specific error do you get on MIFlash?
@orangekid thanks for the reply
Tested with multiple Global and CN roms "error:FAILED (remote: not allowed in locked state)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you in fastboot or EDL?
just reflash the original unpatched boot.img in fastboot.
I have currently the problem that im stuck in poco boot logo, when I flash patched-boot.img. reflashing unpatched boot.img makes it boot again.
orangekid said:
Are you in fastboot or EDL?
Click to expand...
Click to collapse
Fastboot with the orange "FASTBOOT" display
seedlord said:
just reflash the original unpatched boot.img in fastboot.
I have currently the problem that im stuck in poco boot logo, when I flash patched-boot.img. reflashing unpatched boot.img makes it boot again.
Click to expand...
Click to collapse
I tried flashing heaps of different stock ROM boot.img's but must not be able to find the original not sure, believe its a CN phone that had a Global ROM installed when i brought it but could be wrong
Connor.- said:
Fastboot with the orange "FASTBOOT" display
Click to expand...
Click to collapse
Ok you might need to get the phone in EDL mode. If you cannot do it thru fastboot (I think newer phones might not be able to) you might have to remove the back cover and use tweezers to do it thru test point (google or youtube test point EDL for your phone).
Then once in true EDL you can try flashing again with the tool. If you still cannot due to no authorization or locked BL or whatever, you might need to extract the stock image and use a patched firehose file to trick MIFlash tool.
I can try to look but it looks like these guys have a collection as well over here:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
I know this is a lot but my thing is in the future if you are going to modify your phone like kernel patching or anything of the sort you need to unlock your BL first. Just trying to point you in any direction that can resurrect your device.
Believe me I have been in weird situations, such as last year when I somehow flashed a bad file on my OnePlus 9 and the ONLY solution was to literally flash an Indian OnePlus 9 Pro (different device, different region) ROM on my phone from EDL, so my point is there's almost always something you can do unless you want to say screw it and send it in for repair.
I would remove the back of the phone and leave it off, because whatever you're going to do might require test point EDL until you actually get something to flash and boot. At this point I guess it can't really get any worse.
orangekid said:
Ok you might need to get the phone in EDL mode. If you cannot do it thru fastboot (I think newer phones might not be able to) you might have to remove the back cover and use tweezers to do it thru test point (google or youtube test point EDL for your phone).
Then once in true EDL you can try flashing again with the tool. If you still cannot due to no authorization or locked BL or whatever, you might need to extract the stock image and use a patched firehose file to trick MIFlash tool.
I can try to look but it looks like these guys have a collection as well over here:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
I know this is a lot but my thing is in the future if you are going to modify your phone like kernel patching or anything of the sort you need to unlock your BL first. Just trying to point you in any direction that can resurrect your device.
Believe me I have been in weird situations, such as last year when I somehow flashed a bad file on my OnePlus 9 and the ONLY solution was to literally flash an Indian OnePlus 9 Pro (different device, different region) ROM on my phone from EDL, so my point is there's almost always something you can do unless you want to say screw it and send it in for repair.
I would remove the back of the phone and leave it off, because whatever you're going to do might require test point EDL until you actually get something to flash and boot. At this point I guess it can't really get any worse.
Click to expand...
Click to collapse
Thanks for this, i believe its a Mediatek processor not qualcomm unfortunately but EDL pins dont look too hard to access was suprised to see how easy it is to remove the glass back. I'm in talk with the store i purchased it from at the moment so will see how this goes before falling back to pulling the phone apart (only recieved it last Friday )
Realistaclly i am happy with MIUI it works fine for me only intention was to bypass safetynet with magisk so i can use it for contact payments everything else I had already setup just how i like it
Also I would try this maybe?
My experience unbricking a Xiaomi Redmi Note 11 Pro 5G (China) - Hovatek Blog
The Xiaomi Redmi Note 11 Pro (China) is an Android 11 device powered by the MediaTek Dimensity 920 chipset. In
www.hovatek.com
Also you can try this:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Tou should never try to flash anything on a phone with lovked bootloader. Even if you had patched the correct boot.img you would have ended with a brick because your bootloader is locked.
Michael P. said:
Tou should never try to flash anything on a phone with lovked bootloader. Even if you had patched the correct boot.img you would have ended with a brick because your bootloader is locked.
Click to expand...
Click to collapse
well it wasnt locked when i first tried