Database Info

Problems rooting Samsung Galaxy GT-B5510

Hi guys,
I ask for your help after having tried everything was in my possibilities.
I recently bought a Galaxy GT-B1150 and I wanted to root it. I tried everything :
1. Superoneclick
2.Z4root
3.Unlock Root
4.Sgtool
5.to put a .zip folder in the SD and to enter in recovery
It was useless. I have all the possible drivers on my windows 7, although 1,2,3 and 4 didn't work.
1 freezes at #7;
2 just doesn't do anything
4 "smart card error 0x89"
5 I feel idiot, but I seriously can't do the recovery mode. I push power+home+volume up but the best result I achieve is a reboot.
It's been 3 days since I started trying, now I just don't know hat to do.
Thanks for any help!

U've written the model no. incorrectly..got me confused.
Anyway i'll see what i can find.
It's seems like the usual update.zip rooting works. http://forum.xda-developers.com/showthread.php?t=1431696
U should be able to boot into recovery.

The model is GT-B5510, sorry.
I swear I tried thousands times to boot into recovery, I just can't!
I even watched a video and a picture of the procedure, but it doesn't work. It's so simple that it seems impossible to me to be so dumb. It's three keys pressed simultaneously: that's what I do. I don't really know what to think.

Tell me what exactly happens when u try to enter recovery mode.
What do u see on the screen?

When the phone is off and I press the 3 keys, the phone turns on and the screen view with "samsung galaxy GT-B5510" written on, appears. If I hold them, after few seconds, the "galaxy GT..." text disappear and the phone just reboots. If I release them, the phone starts normally.

Weird.
Try various other key combination if ur bored, there should be one for download mode but it's not useful in this scenario.
I came across a very similar case the other day but on a different phone, he resolved it by rooting with superoneclick(beware of the various versions) .
Maybe googling on the superoneclick error might get u somewhere.
Maybe..maybe the new phones shipped with 2.3.6 have the recovery mode disabled/blocked(seems unlikely) but i've not been able to confirm this.
---------- Post added at 05:17 PM ---------- Previous post was at 05:14 PM ----------
Also, is ur phone Y Pro or Y TXT?
Which country are u frm?

I uploaded the video to show you better.

It's been 3 days since I started trying. I googled everything I could, I tried to resolve every problem with each method.
The only way left is the recovery, so I will try different combinations.
It's Y PRO.
I'm from Italy.
Tried soe combinations...useless. Is there something else I can do?

Well it can be frustrating at times...try holding down the keys like forever, even after it reboots..maybe next time it'll boot into recovery instead of android.
Have u come across any alternate firmwares, either stock or custom that u could flash?
U have no problem entering download mode right?

Well, I'm not very into Android, it's the first time I use it. That means I didn't understand a word of your second sentence.
Ah, I don't even know how to enter in download mode.
Thank you for helping me, really!

Firmwares are the files which u can flash on ur phone which gives u a fully working operating system.
Flashing = Installing
Stock firmware/rom = factory samsung firmwares
custom firmware/rom = 'custom' like cyanogenmod
I don't think there are any custom roms for y pro as of now on xda.
Seems download mode for pro is voldown+home+power
Use this site http://www.sammobile.com/firmware/?page=3 , u'll find all the firmware and guides on how to flash them.
U can also find it here http://www.tsar3000.com/Joomla/inde...0-b5512-galaxyypro&catid=57:how-to&Itemid=104
But i usually use sammobile.com
U can check ur current firmware version in the About Phone or by typing in some code like *1234# (i don't remember exactly)
Take your time, don't rush into it. U'll lose all ur data when u flash firmwares.
U don't have any necessity to change firmwares at this moment, but the more u know the better it is.
I'm still wondering why u can't get into recovery.

My firmware is GINGERBREAD 2.3.6
I have Kies, so my phone is fully updated: why should I download the firmware?
The download mode doesn't seem to start too.
This whole thing is crazy!!!
Besides, my phone's memory is getting full, so I really need to move everything to the SD (the apps are already there)!

C'mon download mode has to work..else it's almost useless.
Even when updating with kies the phone goes into download mode during the process.
I was just thinking if u could flash to a previous firmware version maybe u could get into recovery..just a thought.
2.3.6 is the android version, u should also see something like B5510ITVLB1 or B5510ITVLF1
As for memory, rooting is the best way to move all the apps to sd...but there are some applications on market which can move certain apps, not all to sd without root.
There is a galaxy y forum here http://forum.xda-developers.com/forumdisplay.php?f=1469 maybe the folks there can help u more.

My firmware version is B5510XXKK2.
Installing a previous firmware should be my last chance, since it deletes everything. :'(
I'll try on that forum too.

same problem here
Hello,
I know this is a old threat but I have the same problem and I am from the Netherlands..
I've bought this phone with a screenlock password and the previous owner don't not know him anymore
I cannot enter recovery and downloade mode..
I tried evrything i could think of. The Phone is simlocked. Don't know if that is the problem?

Herukon said:
My firmware version is B5510XXKK2.
Installing a previous firmware should be my last chance, since it deletes everything. :'(
I'll try on that forum too.
Click to expand...
Click to collapse
Press volumen down, then Home, then Power.
In above 5 or 6 seconds you will see the Samsung banner, then release all the keys at the same time.
Almost instantaneously you will see a very different menu, and then finally you have to press (as indicated in the screen) the volume up key.
Now you are in download mode, and you can plug the usb cable to connect the mobile to a computer with Odin and then flash the ROM (for instance).
Cheers.
Javier

Same problem - tried everything - can go into download mode - what next?
Hi, I have the same problem. My phone got blocked because my mother tried the pattern too many times. The phone won't accept my gmail login and password (even though it is correct). I've tried a hard factory reset (volume up, home, off) but it doesn't work. I can get in to download mode by pressing volume down, home and off-button but I have no idea what I need to do next. Any advice anyone?

inndranew
Izzie13 said:
Hi, I have the same problem. My phone got blocked because my mother tried the pattern too many times. The phone won't accept my gmail login and password (even though it is correct). I've tried a hard factory reset (volume up, home, off) but it doesn't work. I can get in to download mode by pressing volume down, home and off-button but I have no idea what I need to do next. Any advice anyone?
Click to expand...
Click to collapse
Hi there.
If you read spanish, you can take some ideas from my site:
https://wiki.legido.com/doku.php?id=android:gt-b5510
Summary:
1. Get a GNU/Linux machine (you can build a Virtual Machine on top of Virtualbox for instance)
2. Get SplitFUS2
https://wiki.legido.com/doku.php?id=android:gt-b5510#splitfus2
3. Download a ROM file:
http://samsung-updates.com/device/?id=GT-B5510
4. Uncompress it and generate the required files:
Example:
./splitfus2 -w -s S6102DXMA2_S6102OLBMA1_S6102DXMA2_HOME.tar.md5
5. Get a Window$ machine
6. Download Odin on this machine:
https://wiki.legido.com/doku.php?id=android:gt-b5510#odin
7. Plug the mobile on download mode to the windows machine through a USB cable
8. Pass the files obtained on step 4 to the Window$ machine
9. Upload new firmware with Odin to the mobile
I hope that this summary helps you.
Javier

[Q] Lenovo S5000 -- reinstall system? Bricked after rooting.

Hi,
I used the Framaroot app (v. 1.9.0) to root my Lenovo S5000 -- the Barahir exploit worked fine, I got root, was able to install Titanium Backup at long last, but then I made a mistake: since I also installed SuperSU and configured it for the "survival mode", I thought it would be probably OK to accept an OTA update. After the update, the tablet sort of starts, but all apps (including the launcher, keyboard etc. etc.) force stop and all I get is an endless sequence of "OK" buttons to click while the system tries to run them over and over again. Is there a way to "unbrick" the tablet? I have googled for help, but it seems this particular vendor does not publish any resources that could be of use in this situation. I'm able to get to a kind of diagnostic mode by pressing Vol Up during boot, but it's in Chinese, and I couldn't locate any option that would give an output resembling a "flash a zip file" option. And of course, I don't even have the zip file. All suggestions welcome (perhaps exept for "you shouldn't have bought a Lenovo" -- the tablet was a gift). Thanks.

gstaniak said:
Hi,
I used the Framaroot app (v. 1.9.0) to root my Lenovo S5000 -- the Barahir exploit worked fine, I got root, was able to install Titanium Backup at long last, but then I made a mistake: since I also installed SuperSU and configured it for the "survival mode", I thought it would be probably OK to accept an OTA update. After the update, the tablet sort of starts, but all apps (including the launcher, keyboard etc. etc.) force stop and all I get is an endless sequence of "OK" buttons to click while the system tries to run them over and over again. Is there a way to "unbrick" the tablet? I have googled for help, but it seems this particular vendor does not publish any resources that could be of use in this situation. I'm able to get to a kind of diagnostic mode by pressing Vol Up during boot, but it's in Chinese, and I couldn't locate any option that would give an output resembling a "flash a zip file" option. And of course, I don't even have the zip file. All suggestions welcome (perhaps exept for "you shouldn't have bought a Lenovo" -- the tablet was a gift). Thanks.
Click to expand...
Click to collapse
well if the chinese version of the recovery is similar looking to stock recovery on another device (compare it) you should try to navigate to factory reset.

According to Google Translate, "factory reset" looks like this: 恢复出厂设置

Trozzul said:
well if the chinese version of the recovery is similar looking to stock recovery on another device (compare it) you should try to navigate to factory reset.
Click to expand...
Click to collapse
Thanks for the advice. The menu looks more like factory hardware diagnostics than a recovery menu. It's rather simple, and I've traversed it a number of times already -- shows some hardware test dumps, a testing suite that beeps the speaker, flashes the screen, gives a camera dump, tries WiFi, Bluetooth, GPS etc. and presents a green/red list of successful/failed items, but not much more. However, while playing with it I discovered that pressing Vol+ and Vol- while booting gives me the choice between a normal boot, "fastboot", and the 3e recovery mode. On "fastboot" the booting process hangs, and in the 3e recovery I executed the factory reset/data wipe and cleared the cache partition, but the situation didn't change. I guess the problem might be the su binary failing to grant access to system processes or something like this. Now that I have the recovery mode available the easiest way to solve the problem would be to flash a new/original system image, but I can't locate any Lenovo system file to use. Thanks anyway.

gstaniak said:
Thanks for the advice. The menu looks more like factory hardware diagnostics than a recovery menu. It's rather simple, and I've traversed it a number of times already -- shows some hardware test dumps, a testing suite that beeps the speaker, flashes the screen, gives a camera dump, tries WiFi, Bluetooth, GPS etc. and presents a green/red list of successful/failed items, but not much more. However, while playing with it I discovered that pressing Vol+ and Vol- while booting gives me the choice between a normal boot, "fastboot", and the 3e recovery mode. On "fastboot" the booting process hangs, and in the 3e recovery I executed the factory reset/data wipe and cleared the cache partition, but the situation didn't change. I guess the problem might be the su binary failing to grant access to system processes or something like this. Now that I have the recovery mode available the easiest way to solve the problem would be to flash a new/original system image, but I can't locate any Lenovo system file to use. Thanks anyway.
Click to expand...
Click to collapse
Just flash the system image of the original firmware via sptools then update one and then update again-New firmware update dated 24th March 2014 installed for me-and run framaroot again, the barahir exploit as usual works just find

Bingley said:
Just flash the system image of the original firmware via sptools then update one and then update again-New firmware update dated 24th March 2014 installed for me-and run framaroot again, the barahir exploit as usual works just find
Click to expand...
Click to collapse
Thanks, I've been trying to do exactly that, but I have problems either running the flashtool (I downloaded it from androidxda.com again now, maybe a newer version will run better), or, even if flashtool runs without problems, with installing drivers. I've found a Russian Lenovo forum page with links to S5000 firmware, can (sometimes) run the flashtool, but I just can't communicate with the tablet.

gstaniak said:
Thanks, I've been trying to do exactly that, but I have problems either running the flashtool (I downloaded it from androidxda.com again now, maybe a newer version will run better), or, even if flashtool runs without problems, with installing drivers. I've found a Russian Lenovo forum page with links to S5000 firmware, can (sometimes) run the flashtool, but I just can't communicate with the tablet.
Click to expand...
Click to collapse
Did you get this working?
Can anyone else get OTG working on the S5000 with an external hard drive? USB sticks work fine, but I can't get my backup driver to work.

Bingley said:
Did you get this working?
Can anyone else get OTG working on the S5000 with an external hard drive? USB sticks work fine, but I can't get my backup driver to work.
Click to expand...
Click to collapse
No luck yet. I just can't make the Windows machines see the tablet. I'm not giving up, but I haven't got much hope either, it seems Lenovo is generally not a good target for tweaking, rooting etc.

gstaniak said:
No luck yet. I just can't make the Windows machines see the tablet. I'm not giving up, but I haven't got much hope either, it seems Lenovo is generally not a good target for tweaking, rooting etc.
Click to expand...
Click to collapse
any news?
I would like to try to install CM but if I can't flash the tablet, I think I will wait....

leurne said:
any news?
I would like to try to install CM but if I can't flash the tablet, I think I will wait....
Click to expand...
Click to collapse
I haven't even had time to try again, been quite busy. I'll certainly post here if I have any news about it.

MATE 7 L-09 bricked and dead

Hello
I have a Mate 7 L-09 and I am in the same situation of Sassan_Payehdar described in the his thread
Hi everyone,
I have a Huawei Mate 7 LT-09 16 gig, and I recently did these works:
1. The installed rom was android 6 B513.
2. I read a post in this forum (that is closed now) and updated it to B553 KingVIP Chinese through restoring nandroid TWRP backup.
3. After install I saw lots of bugs, so I wipe all partitions through advanced wipe in TWRP.
4. Then install marshmallow stock recovery using mobopx tool.
after that nothing works.
The USB drive just show hisuite CD-Rom and device not recognize for ADB Options in windows 7,8,8.1 and 10.
There is no recovery,
There is no option using combinations of the buttons vol+,Vol- and power.
I tried installing stock ROM through .app file and dload folder and still nothing works.
I tried Jtag and after lots of work, fastboot screen appears and reinstalling all versions of different recoveries and looks like the software is installing nowhere in neverland!, there is nothing!
I take my device to a technician and he said there is maybe no way to re-run the device. I really need help.
Apologize for poor English and thanks in advance help.
Click to expand...
Click to collapse
No bootloader, no recovery, no option using combinations of the buttons vol+,Vol- and power, no recognition by ADB on PC only huawei logo.
He tried Jtag to appear fastboot, but I never read anything about Jtag. Where can I find it and how to use it?
Sorry for my English.
Can somebody help me?
Thank you so much!!
Al

What happens when you enable your phone (after shutdown) with pressing power + volume up?
Also, what happens when you do the same but with power + volume down?
I would say that if it loads the logo you should be able to enter fastboot/recovery.
Focus on this first and what is your experience with using custom roms to give us an idea of what could be overlooked etc.
If you can load to fastboot and/or recovery let us know and we start from there.

Mother_Teresa said:
What happens when you enable your phone (after shutdown) with pressing power + volume up?
Also, what happens when you do the same but with power + volume down?
I would say that if it loads the logo you should be able to enter fastboot/recovery.
Focus on this first and what is your experience with using custom roms to give us an idea of what could be overlooked etc.
If you can load to fastboot and/or recovery let us know and we start from there.
Click to expand...
Click to collapse
Thank you very much for the answer......
Ok...
I can' t swich off the phone. When I press power off button it reboot and after a few seconds appears huawei logo and then nothing more happens.
When I try to press VOL- and power or VOL+ and power or any other combination of buttons it happens the same think written above: the phone reboot and after a few seconds appears huawei logo and stop.
I brought the phone to the huawei customer center and they told me it need to change motherboard to fix it but it is out of production. I brought it to two famous Chinese stores to fix phones here in Milano, but they couldn't do anything (so they said).
I would just like to retrieve the use of the phone. I saved all the data.
Thanks again for the help.
Al

verdiverdi said:
Thank you very much for the answer......
Ok...
I can' t swich off the phone. When I press power off button it reboot and after a few seconds appears huawei logo and then nothing more happens.
When I try to press VOL- and power or VOL+ and power or any other combination of buttons it happens the same think written above: the phone reboot and after a few seconds appears huawei logo and stop.
I brought the phone to the huawei customer center and they told me it need to change motherboard to fix it but it is out of production. I brought it to two famous Chinese stores to fix phones here in Milano, but they couldn't do anything (so they said).
I would just like to retrieve the use of the phone. I saved all the data.
Thanks again for the help.
Al
Click to expand...
Click to collapse
Not being able to to overcome the logo boot is unknown to me. Maybe the phone should still be able to be flashed!
I lack the knowledge, but to help out I share a link to someone having a similar issue. I will share the link at the end of this post.
If you are unable to connect to your phone and/or make it enter fastboot or recovery I have no idea if that means your phone is bricked.
For now, make sure you understand how to flash,boot,reset etc your phone, only to be sure you have tried all approaches.
Let us know if you did not succeed also so others can learn from this thread in the future
similar topic link -> https://forum.xda-developers.com/mate-7/help/mate-7-booting-t3585079

Mother_Teresa said:
Not being able to to overcome the logo boot is unknown to me. Maybe the phone should still be able to be flashed!
I lack the knowledge, but to help out I share a link to someone having a similar issue. I will share the link at the end of this post.
If you are unable to connect to your phone and/or make it enter fastboot or recovery I have no idea if that means your phone is bricked.
For now, make sure you understand how to flash,boot,reset etc your phone, only to be sure you have tried all approaches.
Let us know if you did not succeed also so others can learn from this thread in the future
similar topic link -> https://forum.xda-developers.com/mate-7/help/mate-7-booting-t3585079
Click to expand...
Click to collapse
Ok
that's unbelievable I was be able to access in fastboot&rescue mode....
I connected the device to my pc but ADB doesn't recognized it.
Now how can I do?
Many thanks
Al

I have same problem as u before, i managed to go to fastboot and then i installed a recovery but the probleme, i bring it into a repair store and the dude literally broke my sd card slot so now I'm really upset.
After that i wanted to make a restore to proposed backups in the firmware forum but nothing happend

Foxar26 said:
I have same problem as u before, i managed to go to fastboot and then i installed a recovery but the probleme, i bring it into a repair store and the dude literally broke my sd card slot so now I'm really upset.
After that i wanted to make a restore to proposed backups in the firmware forum but nothing happend
Click to expand...
Click to collapse
Good
now I am in this situation: I was able to install TWRP recovery for Marshmallow 3.0.2-0 Mate 7 by Mobopx v.2.1.
I chose this recovery beecause my last firmware was EMUI 4.0 (Marshmallow).
After I tried to apply this method: http://ministryofsolutions.com/2016...09tl10-bootloop-after-marshmallow-update.html, but it didn't work. After flashing I power on the phone and it try to boot (some times the animation start too for a bit) but then nothing. The phone reboot in recovery mode (this is a change compared to before).
Somebody has some ideas??
Thanks
Al

verdiverdi said:
Good
now I am in this situation: I was able to install TWRP recovery for Marshmallow 3.0.2-0 Mate 7 by Mobopx v.2.1.
I chose this recovery beecause my last firmware was EMUI 4.0 (Marshmallow).
After I tried to apply this method: http://ministryofsolutions.com/2016...09tl10-bootloop-after-marshmallow-update.html, but it didn't work. After flashing I power on the phone and it try to boot (some times the animation start too for a bit) but then nothing. The phone reboot in recovery mode (this is a change compared to before).
Somebody has some ideas??
Thanks
Al
Click to expand...
Click to collapse
Wonderful!!!!!!
I solved my problem!!!!!
I flashed a TWRP backup get from this forum and now my phone is working.
Thank you to everybody...
Al

I'm very happy for u, can u give me which one you choose for the backup

Foxar26 said:
I'm very happy for u, can u give me which one you choose for the backup
Click to expand...
Click to collapse
Go here
https://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
and choose the appropriate TWRP backp. Flash it by TWRP recovery. It were very simple!!!.
Obviously you have have a working TWRP recovery.....
Hi

[GUIDE] Unbrick hard-bricked device

Condition​
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
Requirements​
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
Steps​
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.

The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
{
"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"
}

SolomonMT said:
The bypass utility enabled my phone to COM6 but SP tool doesn't recognize that port for UART.
Any ideas?
Also, I can't do step 8 without the battery being plugged in and holding vol+ only.
View attachment 5731647
Click to expand...
Click to collapse
You seem to have a driver issue. Install libusb and try again. The battery should not be required for any of the steps as long as the usb is plugged in properly.

OK, it got unbricked, Im guessing Ill brick it again once I try installing ArrowOS for the second time, but for now, Ill try and sumarize what Ive done since I had the phone on OFW.
To get the phone hard-bricked:
I unloacked bootloader and installed Orange fox succesfully then I bricked my phone while trying to flash Global MIUI (as the first step to install ArrowOS but notice it is totally unrelated to ArrowOS), there is a detailed explanation of how I did it here
[ROM] A11 ArrowOS [Garden] 29-12-2021 UNOFFICIAL
I'm not responsible for damage made to your device About: ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end...
forum.xda-developers.com
Trying SPFlash Tool to unbrick my device
My xiaomi redmi 9A was bricked at this point, I described it as:
"the phone just vibrates after a while holding the power button and the screen doesnt even turn on, it isnt recognized by the computer, and if I try to boot into recovery the same happens but the screen turns on for a fraction of a second whith the redmi logo then turn off again, It is not recognized by the computer in this state either"
after gaining some experience with it, I think adecuate to say that the phone still vibrated when holding the power button, but at least the screen did not turn on and as I said; "it wasnt recognized", but just to be clear, what I mean by that is that the PC did absolutely nothing when I pluged the phone in, later after some failed attempts at fixing it, this changed, now the computer prompted me a message explicitly saying, "this device is not recognized" if it was actually recognized before or not is above me.
anyway, back to the moment right after hardbricking my phone in the first place:
I tried using SP flashing tool with this video
but the video is old and after some links died not all the files where provided, (it did however provide a functioning method to disable protection)
so what I did was mix and match different files from diferent sources, and try different methods from diferent videos using SPFlash tool, wich was admitedly a bad idea, the main issue with it was that it symply stayed long periods of time on "download da 100%" with no error message prompting, so i could only stop it change the files and try again, sometimes disconecting the phone, bypassing security with (vol+ vol-) and repeating.
but at one point, the phone did nothing (from now on by nothing I mean not even vibration), the vol+ vol- security did not work, then I tried:
power button alone; noting
power vol+; nothing
power vol-; nothing
and when connected to the PC it told me "this device is not recognized" so the device was totally unresponsive, total brick.
at this point I had already halfly gave up, I enjoy the process, but it was just so unsatisfactory to fail again and again that I just didnt want anymore.
It fixed itself (still hard-bricked but responding).
Now how this got fixed, I actually dont know, I thought maybe if I wait for a while it will respond again, so after two hours it was still the same, I thought maybe if I charge it, after a while with it charging, let it discharge for a while (some odd days), fully charge it (another day or so), and all of those did nothing.
Then I just left it on my desk for like another day when I decided to just try to turn it on one final time and it responded (I dont know what happened I dont know what worked I have several charger boxes and cables plus the pc usb ports, maybe one of them was defective, maybe the one I used lastly was just better, I dont know, but something worked) maybe it just needed around 5 days to work again, i think when it worked for the first time it was plugged to an outlet, Im sorry I cant be more helpful)
now the phone just vibrated after any of the regular button combos, but it no longer displayed anything on the screen if I tried to boot into recovery, but, the PC no longer prompted me that the phone was not recognized, so I could try again.
What actually completely un-bricked my phone.
(This first step is a substitute to the OP requiremeents 5 and 6 used on steps 1 8 9 10 11, this didnt work for me on windows 10, maybe it was just me , but it didnt work)
I installed the Python3.9.1, MTK driver and libUSB I left this files attached as "extra installs", and did it according to how its done on this video
The video is in spanish so if you need extra assistance you can ask me about it or search how to install libUSB wich is the only one I think needs special attention on how to install it (also MTK gave me an error but apparently always does, I tried putting adb on the install folder but Im pretty sure this did nothing as it just gave me a different error)
then, you extract what I left on "ByPass OFF", and run broom.bat a cmd will open up telling you its waiting for a device
(from now on you cant unplug your phone, if you do you have to restart from here)
You plug your bricked phone, and press both vol+ and vol- at the same time until the cmd tells you something like this
then you go to SPFlash tool latest version, (I used SP_Flash_Tool_v5.1924_Win but im pretty sure any one will work)
youll need the ROM that OP provided, its this one.
its 4.22 GB so download it with time, its not a quick page to download from even tho I have "good" internet (around half an hour to a full hour)
you extract it (i recomend using winrar)
and put the scatter file youll use, on the extracted ROM folder, in the image folder, you can download the three scatter files that are for 12.5.4.0 RCDMIXM from the page OP provided and try them all, i left down here the one that worked for me anyway but I dont know what will work for you.
after that I launched the SP Flash tool, and selected the "no auth .bin" provide by OP as Download agent.
(it is posible you get this error
fix it and try again)
as Scatter file you go to the extracted ROM\image and selecth the Scatter file you want to use (again, I left the one I used down here, I have no idea if its the same one that comes with the ROM, also its important it is on the right folder in the extracted ROM)
leave auth blank
I did not select UART port, It didnt work for me, auto USB worked better for me.
you change the dropdown menu to Firmware update
and finally start the program by pressing the download button.
this should work and youll get a prompt like this.
after it had finished I had to unplug my phone and plug it on an outlet for it to let me turn it on, I tried like 3 times before with it still pluged to the PC but it didnt work for some reason, I did not try with it just umpluged so who knows) it turned on to logo, and in around 10 minutes, it asked me to set up the phone as first start like when its brand new, (it was however different to how it used to be, so I know I at least installed a different ROM, do with that info what you will)
Whatts next?
I havent checked if I still have the orange fox recovery installed, tho I doubt it. and also how do I install ArrowOS now? can I do it from spflash tool? thatd be great, is there a better Custom ROM?
Thanks
Also thanks to OP: Yuarian that even if it didnt work for me as is, it still ended providing me with most if not all the tools I needed to unbrick it, and Im pretty sure the ones that didnt work failed becasue I had residual trash files from previous attempts that screwed over his.
anyway see you around.

You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
M2006C3LG

SolomonMT said:
You mean your display would still show the fastboot logo?
In my case it's completely irresponsive except it's possible to put it in bROM mode if I hold the vol+ button.
But It always stays in Downloading DA 100% then throws an STATUS_RAM exception even with your help.
I'm thinking my hard brick case is of damaged RAM since nothing seems to work.
Also, In my case, the phone won't get in bROM mode (holding vol+) if I don't keep the battery plugged.
View attachment 5765891
M2006C3LG
Click to expand...
Click to collapse
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
I have the exact same model, but I dont know how common is that model number, maybe ones made in china and other places have the smae model, I have a 32 Gb version with a single SIM but I can tell it was planed at some point to have it be dualSIM it also has 2 IMEIs
This post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
About your phone in particular, I have three questions.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.

Ivan.Adriazola said:
No, the "First brick" the phone only vibrated when holdng the power button and showed nothing on screen, but if I tried to go into recovery (hold power and vol+), it showed REDMI for like a tenth of a second and it turned itself off again. it did nothing when I attempted to go into fastboot (hold power and vol-), I dont know what bROM is but I assume you mean bootloader.
The "second brick" I got after doing something terribly wrong on SPflash, it did nothing no matter what I did, and IIRC, it only vibrated when holding the power button and did nothing else no matter the button combination, it never showed anything on screen.
About your phone in particular, I have four questions.
Its a redmi 9A right? this post [https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/] says its probably an incompatible ROM for your device, but this might mean you need another official ROM I would try the chinnese one but IDK I did not get to that.
Does it even do something at all? does it even vibrate when holding any key combo? did you use the libUSB tool? did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? in general what does it do nd what does it not?
Do you know what bricked it? cuz I doubt its a hardware issue if it got bricked while attempting a flash, and viceversa, I doubt its a software issue if it got bricked on its own.
did something like this ever show up on your SPflash? because it always did on mine when it was working right, did you perhaps use the UART option? I think your issue is still with the computer not recognizing the phone as a phone, now that I think about it I didnt explain how to install the libUSB tool, so maybe that.
View attachment 5767183
I m not an expert but Im more than willing to help and I think it would be very helpful if you described what you did and how, my bet right now is that you failed to use the libUSB driver, Im even willing to hop in a discord call to give you assistance if we somehow shhare time disponibility, I do have a pretty thicc spanish accent tho so youll have to put up with that.
Click to expand...
Click to collapse
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.

yeah
SolomonMT said:
Its a redmi 9A right? A M2006C3LG, so yes.
Does it even do something at all? Without libUSB and MTK drivers it will show up as unrecognizable device.
does it even vibrate when holding any key combo? Not a single vibration, screen or light flick.
did you use the libUSB tool? Yes, I have to.
did you manage to use the bypass tool I provided and got the cmd code I showed in my comment? Yes, it seemingly works and when it doesn't work i usually just need to replug the battery.
in general what does it do nd what does it not? It will try to comm with the computer whenever I hold down vol+. Nothing more.
Do you know what bricked it? First I soft bricked it, then i put it into a bootloop, and then I hardbricked it by misplacing a file in the super partition.
Click to expand...
Click to collapse
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?

Ivan.Adriazola said:
yeah
sorry about asking if it was a redmi 9A when the model was the same, I actually edited the comment but you were too fast XD.
Mmm... that makes me think there is hope for you, about the chip info image, did it ever show up?
do you wanna hop in a discord call so we can work it out together?
Click to expand...
Click to collapse
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.

SolomonMT said:
I'll work early tomorrow but i'll probably have time to dig again this weekend.
I didn't understand the chip info image question however.
Click to expand...
Click to collapse
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.

Ivan.Adriazola said:
On my spflash tool (I used the latest version) when I pressed Download, with the firmware update only option it showed me information about my phone, even the times it was stuck on Download DA, it always first show my phone info and then it started downloading, anyway best of luck
Also, Im not sure but its posible you erased your IMEI, changing them is kind of illegal in some places (not in my country to the best of my knoledge) so you cant discuss it in here, but try to look for the box your phone came with, or even better, if you still have the sticker it had in its back, it has the IMEIs, I dont know how you would put them back on or if you would even need to, and cant even discuss it, but there must be a way and its better if you know them before hand.
Click to expand...
Click to collapse
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.

Something to be noted for ArrowOS is that you cannot install it on a phone running MIUI 12.5, as far as I can tell.
To install ArrowOS you need to install a custom recovery, and there is no custom recovery for MIUI 12.5.
Moreover, Xiaomi prevents you from flashing an older version of the stock ROM, so there is no way to rollback to a version supported by a custom recovery.
Hence, I am stuck running MIUI 12.5 for the foreseeable future.

SolomonMT said:
do you wanna hop in a discord call so we can work it out together? UnaPersona#7278
I have both the sticker with the actual IMEI and the original box.
Click to expand...
Click to collapse
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?

Ivan.Adriazola said:
bro, Im sorry to leave you hanging, my college profesor finally answered and Im going to give my carrer talk to aquire the civil engineer title this wednesday, I had kind of a lot to do, are you still trying?
Click to expand...
Click to collapse
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad. Thanks.

SolomonMT said:
Sorry, I ended up forgetting and rejecting your request since it was sus (?). But yes, i'll continue trying while in possession of the device. Send it again, if you are available. I'll give it a chance next weekend.
Congratulations on the (under?)grad.
Click to expand...
Click to collapse
youre welcome

I managed to flash the rom and revive my phone thanks to this guide. It booted, works perfectly
First unplugged battery. Then.
I used MTKClient on Linux, installed following instructions, https://github.com/bkerler/mtkclient
And ran command
sudo mtk payload
(then left Vol up and Vol down pressed together and plugged usb cable to unlock the SLA Authorization)
The tool runs a generic payload to the CPU, mt6765 in this case, and puts the phone on BROM mode
(This will unlock SLA authorization, allowing the Rom to be flashed)
(A message appears saying " Successfully sent payload " along with Hardware/Port info)
From there immediately used SP Flash Tool-V5-1916
sudo ./flashtool
Used DA_6765_6785_6768_6873_6885_6853.bin as DA
Used MT6765_Android_scatter--V12.5.4.0.RCDMIXM--boundary_false.txt as Scatter file.
And flashed the whole Firmware/Rom 12.5.4.0.RCDMIXM Global with UART Connection Setting.
Thank you for the guide master. God bless you.
(Its important to be patient)
(Bypass utility didn't work for me, i think it works better in Windows or Debian/Ubuntu, but not other distros)

Yuarian said:
Condition​
Phone does not turns on
Phone not detected via USB
Phone handshake/memory hash failed
​Requirements​
Unplug battery
Download MIUI 12.5.4.0.RCDMIXM Fastboot ROM
Download Scatter File for 12.5.4.0.RCDMIXM
Download SP Flash Tool
Download Bypass Utility
Download Bypass Configs
Download No Auth File
​Steps​
Put Bypass Configs into Bypass Utility folder
Put Scatter File in ROM images/ folder
Open SP Flash Tool
Select scatter file within images/
Select No Auth File for DA
Leave Auth file selection blank
In options, select UART.
Ready Bypass Utility python3 main.py; do not run it yet
Connect phone via USB
Press and hold volume - & + buttons
Run python3 main.py; wait for successful execution; release buttons
Immediately start SP Flash tool; retry from 8 if fail
Unplug USB; plug battery; charge device; turn it on and leave for 10 minutes
Done.
Click to expand...
Click to collapse
hi i have a redmi k50 pro whit dimensity 9000 MT6983 can you healpe me? pllleasee

Hi, I was trying these steps with no success, maybe something was missing (this was in Windows). However, I found another way to do it with Linux where you don't need to install drivers as the system comes ready to use.
I detailed what I did to unbrick my Redmi 10A here:
Unbrick or Recover Xiaomi Redmi 10A and other MTK devices
Unbrick Xiaomi Redmi 10A and other MTK devices.
runakay.blogspot.com

New Samsung Update for A51 is Bricking phones

Good evening folks. Over the Past week, for some reason, people who downloaded the new Samsung update for A51 have had their phones bricked. FOR SOME REASON, this seems to only be happening here in South Australia. I haven't seen anywhere reporting on this issue other than local news. I have had three A51 phones come into my IT store, all with the same problem.
here is a link to one article talking about it: https://7news.com.au/technology/sam...ng-priceless-photos-vital-contacts--c-9340963
Upon installing the update, their phone will restart then it will not progress past the SAMSUNG logo. I have been able to get each and every phone into recovery mode however I when I try and reboot the phones into bootloader, they simply say "entering fast boot" and then don't progress any further.
Since I have been unable to boot the phone to bootloader I don't have many solutions in front of me, I can either factory reset the phone which has been proven to work, or I can try some alternative method. Simply put, I refuse to take the simple way out and simply factory reset the phone, I don't want my customers to go through the trouble of losing their photos.
The only real option I see is using ADB to install either a new update or new firmware, however, I have had ALOT of trouble finding the necessary software. I have been able to get ADB to detect the devices with a USB connection, so I tried installing some firmware, I found for my device. I didn't trust that this was the correct software, but it couldn't hurt to see if it worked.
Using a515fxxu5gvk6, I was able to find a website where I could download Firmware https://samfw.com/firmware/SM-A515F/TEL I don't believe this to have the correct software but it was the only option I could find that didn't require money or an account.
upon extracting the zip file and typing ADB sideload <file name> it would start the process of installing the software however, it would only install for a single second and then stop working. I would be greeted with the messages: "footer is wrong", "update package took 0.3s", and "signature failed". I believe this means I have either grabbed the wrong software or I have tried installing the software wrong
I really don't know where to find the correct software, and I don't even know if I will be able to update the phone using ADB since I never was able to enable developer tools.
I have already spent quite a few hours on this, and it's starting to drive me insane. I have gone down so many rabbit holes researching different options only to come back up empty-handed. Im lost and really don't know where to turn.
any help would be literally amazing, if someone could even point me in the right direction that's all I need. even if you tell me there is nothing that can be done and I need to factory reset the phone I can at least go to sleep knowing I god damn tried.

Well, one thing you should know is that Samsung doesn't use fastboot to flash software like many other brands. It's unfortunate to say that a lot of the guides you read online are just copy-paste of guides that do use fastboot. Adb doesn't really flash software without elevated permissions afaik.
You can flash firmware using Odin for Samsung devices. There should be plenty of guides online on how to use it, your main goal right now is figuring out how to boot into download mode for Samsung.
What I would do is try to turn the phone off completely if you've been able to boot to recovery. After that, hold both the volume buttons and while you're holding them, connect your phone to a PC. This should force the phone to boot to download mode. Read the screen as it may ask you to press VOL + to proceed.
After that, you can flash the files
AP_XXXX
BL_XXXX
CP_XXXX
HOME_CSC_XXXX (Use HOME_CSC instead of CSC_ so that the phones don't lose any data)
And after that, you should be able to flash firmware

ShaDisNX255 said:
Well, one thing you should know is that Samsung doesn't use fastboot to flash software like many other brands. It's unfortunate to say that a lot of the guides you read online are just copy-paste of guides that do use fastboot. Adb doesn't really flash software without elevated permissions afaik.
You can flash firmware using Odin for Samsung devices. There should be plenty of guides online on how to use it, your main goal right now is figuring out how to boot into download mode for Samsung.
What I would do is try to turn the phone off completely if you've been able to boot to recovery. After that, hold both the volume buttons and while you're holding them, connect your phone to a PC. This should force the phone to boot to download mode. Read the screen as it may ask you to press VOL + to proceed.
After that, you can flash the files
AP_XXXX
BL_XXXX
CP_XXXX
HOME_CSC_XXXX (Use HOME_CSC instead of CSC_ so that the phones don't lose any data)
And after that, you should be able to flash firmware
Click to expand...
Click to collapse
Thank you so much for your reply. I have spent the past few hours setting up Odin and installing the firmware.
I have run into another problem, I select all the firmware I wish to install then click start. It loads for two seconds then says "PASS!". However the phone is still stuck in a boot loop
I believe this is because I haven't turned in USB debugging, since I can't get into the phone I can't turn it on even if I want to.
Is there another option?

USB debugging isn't needed when flashing through Odin. You're most likely just missing the Samsung dev drivers. Try and installing them: https://developer.samsung.com/android-usb-driver