Database Develop

Startup Failed but not Verizon Model

I have the Moto E5 Play, the XT1921-5 model from Boost. I was given it by a friend who asked if I could save it. Apparently, he must have flashed a wrong kernel or rom and it will only go to a screen telling me Startup Failed and to hook it up to the Software Repair Assistant to fix it. Well, The Software Repair Assistant is for the Verizon models. This is the Boost version. Tried flashing stock firmware but won't let me do it. If you notice on the fastboot screen it reads the correct model but the eMMC and DRAM say SAMSUNG. Also, the baseband version it says does not exist. Does anyone have any clue as to what this dude did or if it is even possible to repair? It's a brand new phone just can't install an OS. Any ideas would be appreciated

The device is booting into what is called [circa AOSP @ https://developer.android.com/docs] a Yellow-Boot mode. Unfortunately, without the device's bootloader unlocked,a yellow boot bricks a device. That's my guess.... I would go ahead and try the software repair assistant (even though it's for vzw devices) & just see if you can salvage it at all..... I know I had a vzw great play and after rooting it with the Magisk 13.3 tethered exploit, I came to this screen after flashing a modified boot.img w/ a locked bootloader, and I had to use the software repair assistant to salvage it. If that doesn't fix it, maybe try to sideload the stock firmware through recovery..?

Phone bricked, won't turn on. Help please!

Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.

Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)

Samsung: worst ever for a power user!

Today I got up real pissed with Samsung for being so restrictive around ROM flashing, rooting, flashing custom firmware or even stock firmware, so wanted to create this post to help anybody considering to get a Samsung phone to stay away from it.
This post is not intended to recommend any specific brand or model of android phone, but to recommend the exact opposite, which brand and model NOT TO EVEN THINK of purchasing.
This post relates to Samsung Galaxy S9 G9600 model which is Snapdragon architecture, but since Samsung is coming up with a bunch of "security features" I tend to think this may be the case for other models as well. I browsed all around XDA and other sources for guides on how to root and install custom roms, and it turns out Samsung manages to have limitations for EVERY step of the way.
Getting a few facts straight
Reference post: https://forum.xda-developers.com/ga.../rom-lineageos-17-1-s9-s9-snapdragon-t4093301
Ok, so there is a solid thread about a custom firmware and looks like several users got hands on it, but they might have been able to get passed though all Samsung security crap before it came out or before it got so tightened up. I'll list below every limitation I found:
OEM Unlock
There is a step where we need to tick OEM Unlock from the phone developer settings, it turns out Samsung has put a 7-day timer for this option to even appear listed to enable. If you do factory reset of the phone, the 7-day timer restarts. There are a few posts around on how to get passed this timer, but to me they were all crap, none of them worked. STRIKE ONE!
Bootloader unlock
After 7-days, we get the OEM Unlock option to appear, at this point you may think: Hurray!! .... WRONG! Now next step is to unlock the bootloader using an utility called CROM Services... And as you may have already guessed, did not work! I'm able to install the apk, but on launch it complains about wrong android version. (Tried with Android 8 and 10) STRIKE TWO!
There are some posts and guides claiming to be able to unlock bootloader by using fastboot utility, I can't reach to understand how, since fastboot commands rely on the bootloader to be previously unlocked (?). I least that is my understanding, correct me if wrong. Needless to say fastboot did not work for me. ADB lists my device but fastboot doesn't. There are a few troubleshoot guides around to try selecting proper USB driver from windows device manager, tried all that, tried a couple of ADB installations, fastboot didn't work.
Knox and RMM state
After some lookup in the web, Samsung incorporates some security features trying to prevent device theft and such things. For us power users this is in reality just a whole load of crap preventing us to get all the juice out of our phones.
Reference: https://www.goandroid.co.in/unlock-bootloader-of-galaxy-s9-plus-snapdragon/84688/
TWRP Recovery
Next step would be to flash a custom recovery such as TWRP with Odin or adb/fastboot, but since we are not able to unlock the bootloader in previous step, this is not doable at all. STRIKE THREE! OUT!
Fastboot utility doesn't recognize the device in download mode, so we can't send any commands to the phone.
Odin complains it is only able to flash signed stock roms, so since TWRP is not, we cannot flash it.
Rooting
Needless to say that if we don't have TWRP, we cannot flash the corresponding packages to root. Although this step may not be needed to install custom firmware, rooting has not been possible.
Stock ROM Flashing
Ok, so let's stay out of custom firmware - let's play around with stock firmwares. At this point, since flashing stock firmwares is kind of allowed by Samsung I was able to try out a couple from android 8 to 10 with Odin
Stock ROM Source: https://www.sammobile.com/samsung/galaxy-s9/firmware/#SM-G9600
But watch out! Once you get to install a specific build version, you cannot go back or downgrade to ROMS with previous Android build version. So now that I got Android 10 cannot go back to 8 or 9, this is probably because locked bootloader and unable to unlock. Here, Odin complains with FAIL! (AUTH) message.
STRIKE FOUR! EVEN OUTTER!
SIM Unlock
Ok, let's stay out of Samsung S9 G9600 model, let's crash it to the wall and throw it away to the garbage! Ok no, let's have it carrier unlocked and sell. Unlockbase is a well known and trusted sim unlock provider, I purchased a license to unlock by USB cable, but... GUESS WHAT! G9600 is not supported for unlocking operator network with this software... what a surprise!! I was able to apply for a refund and got my money back, so no worries here.
Note that flashing carrier free ROM does not unlock sim to use with any network operator.
I'll be trying to unlocking by code soon, as this is based on IMEI number, I may think this is independent to the phone model and edition, so I hope I have more luck with this option.
Conclusion
G9600 is a really crappy phone to mess around with. I may have ran low on luck with this specific Samsung Galaxy model since I got it as a gift, which is the latinamerican crappy edition. I wonder if other S9 editions and other Samsung models run with better luck than mine on this scenery... But as a lesson to myself, I will stay away of any Samsung smartphone in the foreseeable future.

OEM Unlock
The 7-day lock prevents stolen phones from being factory reset, leaving the thief with a phone permanently protected by your account. While a minor inconvenience, it's actually effective and not the worst compared to other manufacturers.
Bootloader Unlock
After OEM Unlocking, flashing TWRP through ODIN is effectively unlocking the bootloader. This is possible on both exynos and snap.
Knox and RMM
While this is an inconvenience, from Samsung's point of view, it's worth it. It makes the phone look more secure in the eyes of potential customers. If you really wish for NFC payments, I'm still able to use GPay with Magisk on a custom ROM.
TWRP Recovery
TWRP is flashed through ODIN, not fastboot. Look up an actual guide before complaining.
Root
Yes you can
Stock ROM Flashing
The one thing I could agree on with you is Samsung disabling OTA updates when OEM unlocking. I don't see the point really, but you're free to flash whatever you want through ODIN. Downgrading shouldn't be an issue. Not sure what's up with that.
Before buying a phone, how about you do some research before crying on forums. As a power user coming from the Oneplus One, I don't regret going for Samsung in the least.

Thanks for your reply, I had dropped all hope after several attempts over last few weeks. Found this option and I was able to get past my blocking issue with TWRP and moved on.
https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751

I have G960F and have to admit I totally disagree with your original post. I've been using custom ROMs on nearly every phone I ever had and don't think S9 (G960F) is bad in terms of unlocking. Just did an OEM unlock, waited a week, flashed TWRP through Odin, booted straight to TWRP and immediately flashed a custom ROM from it (because a boot to the stock ROM would replace TWRP back with the stock recovery IIRC). In the end I got sick of all the problems with Magisk and non-working google pay that I went back to the stock ROM - making S9 the first phone I use with a stock ROM even though it can be flashed. I think it's a great phone for power users.
And as far as SIM unlock goes - Samsung is not to blame, the carrier the phone was made for (and purchased from) is. Phones that Samsung itself sells are unlocked. I wonder why there's still some countries where SIM locking remains legal.

This thread is a prime example of how people end up with bricked devices. So much misinformation in one page LOL

I had the 9650 and most of what I'm doing here is user error. This was one of the best devices I've ever owned. I mention of fast boot and such you obviously just do not know samsung devices. You can't blame samsung on your own ignorance

What if you hard brick your Redmi Note 9 device?

I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.

pepsimaxmjs said:
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
Click to expand...
Click to collapse
Maybe this is kind a ethical question. I don't consider its ok to pay someone to be able to flash your device, specially if you have to send money to some anonymous russian guy and hopping you are not getting scamed. Clearly its not a comfortable method and it shouldn`t be that way.
If I ever need that service I would use it just to record username and password with a keylogger and post it freely, its ridiculous to pay for flashing your phone.

Yes but...
ma259 said:
Maybe this is kind a ethical question. I don't consider its ok to pay someone to be able to flash your device, specially if you have to send money to some anonymous russian guy and hopping you are not getting scamed. Clearly its not a comfortable method and it shouldn`t be that way.
If I ever need that service I would use it just to record username and password with a keylogger and post it freely, its ridiculous to pay for flashing your phone.
Click to expand...
Click to collapse
If you actually hard brick your device (mine shipped from China direct) you have a lot of hassle to get it fixed. If you don't have a service centre nearby, double the hassle and significant costs / risks to ship overseas. Sat at home, someone with the skills and the important EDL keys (i.e. registered repairer with Xiaomi) could fix the device. Mine was an unlocked phone, therefore technically I had removed the warranty. $29 to flash a bricked device and fully recover from my ****-up. OK value for me.

Hello, could you show me how to do it?

If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
For removing modules, you have two methods.
For first method, you need to boot in emergency mode, open magisk manager, remove module and reboot.
(It works only with magisk +v21.)
(To boot in emergency mode, keep pressed volume down after boot starts.)
For second method, you need to flash the original stock boot.img, open magisk manager, remove module, reboot and then flash the magisk patched boot.img again.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

CruisaderX said:
he probably used [SPAM] that you can avail 3 months subscription for 19.19 usd, planning to get one when i have the money
Click to expand...
Click to collapse
It doesn't work for redmi note 9, my friend.
I'm sorry.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

pepsimaxmjs said:
I am a long time user of Xiaomi devices, and have rooted every one I have. I recently purchased the Redmi Note 9 for my girlfriend and intended to root and block ads etc. I am quite proficient with rooting processes and the tools needed to make that work.
I could find a working TWRP for the phone, and used ADB and Fastboot to program this. However, it seems the MTK Helio G85 is a bit more tricky than a Qualcomm based device. So I basically failed to get root working. In the end through a late night error I managed to delete the Boot.img of the device leading to the dreaded 'hard brick'. I have read on the Forum others who have the same symptoms - basically boot loop, no access to Recovery or to Fastboot. Bad luck my friends this is a Service Centre repair.
So I took to Googling on the issue and found a Russian who advertised a Service Centre repair service but over TeamViewer. This was advertised at US$29 for a fix. Why could he do it? Well he has the Service Centre auth codes needed to do a full recovery of the phone. So taking pot luck I sent my US$29 and they did exactly what they promised. Accessed my PC remotely worked with me to get the correct files set up, and then loaded up their authorised service build on my PC and re-programmed the bricked device. After a 2 hour re-charge (best to do this reset with no battery power) I performed the 3 button re-set and the phone came back to life. Never left my house, and the phone re-booted with a full build of MIUI.
I am not sure if the mods allow me to provide their details, so I in order to keep my XDA status OK I'll ask you to PM me if you need the details.
Saved my phone, and to be honest was worth the cash for the no hassle repair. I am not in a Service Centre area, and this quick reliable fix was great. Took a risk, but the provider is genuine and authorised repair agent. Their English was great, instructions clear, and all the hard work they do remotely on your PC. I scanned for viruses after the session - was all clean.
If you get in a fix, this is a good reliable and convenient solution.
Click to expand...
Click to collapse
Paid solutions are no longer needed. Redmi Note 9 factory firmware is out, so you can unbrick your phone, even if it's hardbricked, without authorised account.

Communos said:
Paid solutions are no longer needed. Redmi Note 9 factory firmware is out, so you can unbrick your phone, even if it's hardbricked, without authorised account.
Click to expand...
Click to collapse
If you are on MIUI V12.0.5.0 or higher, you can NOT flash without authorised account using flash tool.
You really need the EDL auth if you are on MIUI V12.0.5.0 or higher.

Unbrick Redmi 8

My phone suddenly get stucked into Redmi boot logo, cannot access system recovery but can access fastboot menu.
The problem is I hadn't enabled OEM unlock and developer options before. All the methods that I found so far requires bootloader unlock for that I also don't have MI account . What might be my next move? Thank you.

its hard to say what we can|t do with a still locked bootloader. if going to an authorized service center is out of reach, all we can do is try i guess. id still suggest going there if you can easily access your google account.
there are a few threads that say we can flash a still locked bl, but im not so sure.
Flash stock ROM/Recovery, lock bootloader?
Is there any guide on how I can complete return phone to stock and lock bootloader? Thank you.
forum.xda-developers.com
official stock roms can be hard to find on their site, heres an easier to navigate 1.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
gl

With EDL mode? I'm in a similar situation, a friend's mother forced a shutdown during a firmware update and destroyed the system that way. Of course the bootloader is blocked. I find it extremely stupid of Xiaomi to rely on a working system to give you the chance to unlock the bootoader but I guess that's how you sell some extra phones.
So far I've taken out the rear cover and the plastic that goes on top of the motherboard, unplugged the battery and with an arduino cable and some fiddeling shorted the "boot" pins while connecting the USB cable. Seems to be working given that MiFlash has changed the locked bootloader error for "indice fuera de limites" or in English "index out of limits error". I guess I don't have the right ROM so I'm downloading another one, but I'm struggilng to find the correct original fastboot ROM. The first one I've downloaded from Mi Community, the second one is from xiaomifirmwareupdater, but is gonna take forever to download. And I mean... F-O-R-E-V-E-R

Jaki1122 said:
With EDL mode?
...
Click to expand...
Click to collapse
gl with that, as only authorized people can properly flash from there. while i havent used EDL, there are some trusty people who can help us out (ive seen it in tg groups)
a site did say maybe using another version can help, who knows it might do the trick
https://c.mi.com/thread-2027947-1-0.html
also seems weird how goolag hasnt fixed half flashing from destroying, last time i had that happen was '12