Database Info

root exploit for the d6603?

Hi guys sorry if this is a dumb question but I've been out of the loop on this.
Has there been a root exploit found for the D6603 Z3's?
I'm using a Xperia Z3 on the Canadian Bell network which is showing the bootloader is locked through the Sony app. I'd like to keep it but if there's nothing yet I might just sell it and get something else.
Thanks in advance.

tinodevoe said:
Hi guys sorry if this is a dumb question but I've been out of the loop on this.
Has there been a root exploit found for the D6603 Z3's?
I'm using a Xperia Z3 on the Canadian Bell network which is showing the bootloader is locked through the Sony app. I'd like to keep it but if there's nothing yet I might just sell it and get something else.
Thanks in advance.
Click to expand...
Click to collapse
Google 'giefroot'
You will need to downgrade to a firmware where the exploit works, but it is easy enough to do and easy enough to run the tool
AFAIK, there is a compatible FTF for your network, find one in the mega collection thread or download one from Xperiafirm

gregbradley said:
Google 'giefroot'
You will need to downgrade to a firmware where the exploit works, but it is easy enough to do and easy enough to run the tool
AFAIK, there is a compatible FTF for your network, find one in the mega collection thread or download one from Xperiafirm
Click to expand...
Click to collapse
Thanks for the info. Does the method still cripple the camera or is there a way to work around this?

tinodevoe said:
Thanks for the info. Does the method still cripple the camera or is there a way to work around this?
Click to expand...
Click to collapse
No, because the method does not involve unlocking the bootloader.
Also, the camera issue when unlocking the bootloader was sorted about a year ago

gregbradley said:
No, because the method does not involve unlocking the bootloader.
Also, the camera issue when unlocking the bootloader was sorted about a year ago
Click to expand...
Click to collapse
Just searching around and it looks like I need to be on 23.0.A.2.93 firmware for the exploit to work.
on my phone the current firmware is 23.0.1.A.5.77 (according to xperiafirm Bell's latest FW is 23.0.1.A.5.77 / R7B)
Is there one of these that I can use to downgrade my phone?
{
"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"
}

tinodevoe said:
Just searching around and it looks like I need to be on 23.0.A.2.93 firmware for the exploit to work.
on my phone the current firmware is 23.0.1.A.5.77 (according to xperiafirm Bell's latest FW is 23.0.1.A.5.77 / R7B)
Is there one of these that I can use to downgrade my phone?
Click to expand...
Click to collapse
The carrier or region should not matter.
As long as you have a 6603 any 6603 FTF will do the job. Make sure you have a 6603 though and not a 6616. I am not to clear on the device models from across the pond and flashing a 6603 rom on 6616 (AT&T device US) will result in bootloop.
Not a problem to fix, but may not enable you to root.

gregbradley said:
The carrier or region should not matter.
As long as you have a 6603 any 6603 FTF will do the job. Make sure you have a 6603 though and not a 6616. I am not to clear on the device models from across the pond and flashing a 6603 rom on 6616 (AT&T device US) will result in bootloop.
Not a problem to fix, but may not enable you to root.
Click to expand...
Click to collapse
Thanks again.
What does the R7B at the end stand for and does that matter when choosing the rom to flash?
sorry to ask one more thing, can you point me in the direction on what to use to flash the rom to an earlier version?

tinodevoe said:
Thanks again.
What does the R7B at the end stand for and does that matter when choosing the rom to flash?
sorry to ask one more thing, can you point me in the direction on what to use to flash the rom to an earlier version?
Click to expand...
Click to collapse
Its just regional and carrier branding, nothing to worry about.
Use flashtool to flash FlashTool Files

gregbradley said:
Its just regional and carrier branding, nothing to worry about.
Use flashtool to flash FlashTool Files
Click to expand...
Click to collapse
bloody shame, I got this far and now I can't seem to be able to get it to root.
I did the firmware downgrade, went smooth.
Now following the steps here: http://www.gizmobolt.com/2015/01/24...-giefroot-rooting-tool-cve-2014-4322-exploit/
I get this message after the giefroot does its thing. It reboots the phone but I end up with the same message on each pass.

Disable antivirus anf firewall.

Alright I've made some progress!
I managed to get my phone rooted. Checked with root checker and its legit! SuperSU is installed.
Now I'm trying to figure out how to install a recovery but no dice.
I downloaded the Z3-lockeddualrecovery2.8.14-RELEASE.installer from here: http://nut.xperia-files.com/
and when running, after selecting the first option for rooted phones with SuperSU, it there are a million error messages adb server is out of date. killing...
at the end it says it worked but I still can't boot into recovery. The phone even shows up within the command prompt when I type adb devices. But adb reboot and key presses don't boot into recovery, it only reboots back into the OS.
Is there another way to flash a custom rom or at least a rooted rom with 5.0/5.1? Ideally I'd like to run Cyanogen on my phone but not sure if its possible without unlocking the bootloader.
Thanks in advance for any advice and help!

You will have to unlock to install CM.
Try rebooting to recovery via NDRUtils app

Yes you are rooted, but I bet you don' t have busybox installed.

TheTeslaCoil said:
Yes you are rooted, but I bet you don' t have busybox installed.
Click to expand...
Click to collapse
Both the giefroot and Dual Recovery installations install Busybox into the correct folder.
Issues normally arise when people try to manually install busybox

gregbradley said:
Both the giefroot and Dual Recovery installations install Busybox into the correct folder.
Issues normally arise when people try to manually install busybox
Click to expand...
Click to collapse
Not true.
Busybox can be installed via a flashable zip without any problems.
And there were people who didn' t had busybox installed after root, RootCheker said busybox is not.installed. Then they flashed the zip and voila. Perfection at it' s best.

TheTeslaCoil said:
Not true.
Busybox can be installed via a flashable zip without any problems.
And there were people who didn' t had busybox installed after root, RootCheker said busybox is not.installed. Then they flashed the zip and voila. Perfection at it' s best.
Click to expand...
Click to collapse
If you follow the NDR thread int he cross device development forum you will see that [NUT] advises not to install busybox manually but to use the NDR installer or NDR flashable zip (Maybe this is what you are referring to)
As this user is having an issue installing dual recovery I would follow the advice the dev of that tool.

gregbradley said:
If you follow the NDR thread int he cross device development forum you will see that [NUT] advises not to install busybox manually but to use the NDR installer or NDR flashable zip (Maybe this is what you are referring to)
As this user is having an issue installing dual recovery I would follow the advice the dev of that tool.
Click to expand...
Click to collapse
Right, he must follow the OP' advice.
In this particular case, that' s the way to go.

Guys, finally after hours of trying everything yesterday figured out my problem. A bloody POS Monoprice usb cable!!
I tried with another usb cable and sure enough it patched everything ok....
So now I have installed a prerooted/recovery version of sony's 5.0 which seems to work fine.
If CM needs to be unlocked, are there any other versions out there that will work with the locked bootloader besides the official sony roms?

tinodevoe said:
Guys, finally after hours of trying everything yesterday figured out my problem. A bloody POS Monoprice usb cable!!
I tried with another usb cable and sure enough it patched everything ok....
So now I have installed a prerooted/recovery version of sony's 5.0 which seems to work fine.
If CM needs to be unlocked, are there any other versions out there that will work with the locked bootloader besides the official sony roms?
Click to expand...
Click to collapse
No

Huawei MediaPad M3 Lite 10 Custom ROM and Custom Recovery [TWRP]

{
"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"
}
​
This thread is for the MediaPad M3 Lite 10 LTE - Tablet from Huawei.
In my case, I´m looking for a C-ROM and C-Recov (e.a. RR, Mokee, TWRP) for the
Huawei MediaPad M3 Lite 10 LTE (BAH-L09) with Android 7.0 and EMUI 5.1
Since it´s quite new on the market it´s atm hard to find anything bout a C-ROM or even a C-recovery.
discoveries
advises
questions
tipps / tricks
productive discussions
solutions
are much appreciated.
Detailed device Informations:
​
​

Nobody knows any thread about this tablet??

Still searching for a root-solution.
So it's possible to read out the firmware with Infinity Box CM2 but haven't found a working "Non-dongle"-version (Loader).
Some days, there will be a root solution.
It just takes time and will be posted in here.

essayn said:
Still searching for a root-solution.
So it's possible to read out the firmware with Infinity Box CM2 but haven't found a working "Non-dongle"-version (Loader).
Some days, there will be a root solution.
It just takes time and will be posted in here.
Click to expand...
Click to collapse
If you need some help and i can do something, tell me

skymota said:
If you need some help and i can do something, tell me
Click to expand...
Click to collapse
I much appreciate the offer but what could u do if u haven´t the device or do u own it ?
Since my CM2-Infinity-box doesn´t work (usually I work with Miracle Box but it´s not compatible ...well the Tablet has to be rooted to read the firmware..), and literally tried all rooting-apps and progs, this device is really stubborn!

I own this device, thats what i told you

skymota said:
I own this device, thats what i told you
Click to expand...
Click to collapse
Very well. ?
Actually, just the stock-recovery is needed to finally start to compile it. Have u been able to extract the recovery or maybe the whole ROM ? ?

essayn said:
Very well.
Actually, just the stock-recovery is needed to finally start to compile it. Have u been able to extract the recovery or maybe the whole ROM ? ?
Click to expand...
Click to collapse
search and read a lot about this but i cant...

skymota said:
search and read a lot about this but i cant...
Click to expand...
Click to collapse
Well, to bad but I guessed so, since this device is atm not rootable. :/
I tried every single Flash-Box like MB, Infinity, Aladdin, Falcon etc pp.. any Rooting-App (APK & PC- based), almost a dozen flash-tools like ADT, AOS-flasher, Ultimate Backup-tool etc...and several command prompts via ADB&Fastboot.
Really Nothing helped to get a nandroid- or even a dumb ROM. From which I could extract the stock recovery.
Nevermind, I will try alil more with Holo- & Heliumbackup, which surely wont work but who knows, rite ??
I'm patient and as soon as I've found a solution I'll share it here immediately.
As any other user is welcome to do so, too.

I´ve managed to extract the stock-recovery via an OTA-update which came from Firmware Finder from Team MT.
U ´ll find the recovery on G-Drive. The "oldRECOVERY.img" is the extracted stock-recovery from the original BAH-L09C100B018 firmware!
So, since I´ve updated the Tablet, the only "RECOVERY.img"-named file is from the newest firmware which is L09C100B021!
If u wanna update to ...021, via the Firmware Finder-App, u need
The App
Time
Be aside your tablet
and watch this video before u start
May read this thread aswell
​

I bought the BAH-W09 model last week, anyone here unlocked bootloader on the lite 10 yet?

jenkins-1984 said:
I bought the BAH-W09 model last week, anyone here unlocked bootloader on the lite 10 yet?
Click to expand...
Click to collapse
Yup, unlocked the BL from day 1. It´s the same procedure for all HUAWEI devices.
Just go here, login or register, confirm the unlocking agreement and put all device infos into the blank fields.
U´ll immediatley get an unlock code, which u have to enter via fastboot command prompts (recommended):
fastboot devices
fastboot oem unlock-go 1234567890123456 <- (this number is an example, u´ll have to put ur code there instead)
fastboot reboot
From now on an unlocked bootloader message will appear every time u start ur device. Just press power shortly to boot then. (It´s also written in the text aswell)
P.S.
Before u try to unlock: Don´t forget to enable USB-debugging in the Engineertool (tap 7 times on "build" in the settings-menue) and "allow OEM unlocking".

essayn said:
Yup, unlocked the BL from day 1. It´s the same procedure for all HUAWEI devices.
Just go here, login or register, confirm the unlocking agreement and put all device infos into the blank fields.
U´ll immediatley get an unlock code, which u have to enter via fastboot command prompts (recommended):
fastboot devices
fastboot oem unlock-go 1234567890123456<- (this number is an example, u´ll have to put ur code there instead)
fastboot reboot
From now on an unlocked bootloader message will appear every time u start ur device. Just press power shortly to boot then. (It´s also written in the text aswell)
P.S.
Before u try to unlock: Don´t forget to enable USB-debugging in the Engineertool (tap 7 times on "build" in the settings-menue) and "allow OEM unlocking".
Click to expand...
Click to collapse
Ok cheers, I looked on the emui site and was nothing under their tablet menu only phones on the unlock bootloader page, on Nexus you just enable usb-debugging and click the OEM unlock in settings and fastboot flashing unlock in terminal. Sony uses a custom tool and HTC via their website I had a few phones in the past and built roms etc this my first Huawei device apart from my Nexus 6p Huawei help build with Google. I take it this device no official forum atm only the Kirin version.

Ya, HUAWEI has a quite faire unlock policy.
Important: There's an unlock bug sometimes. Be sure to have the Original firmware on ur device. (No updated ROM)
Have fun.

essayn said:
Ya, HUAWEI has a quite faire unlock policy.
Important: There's an unlock bug sometimes. Be sure to have the Original firmware on ur device. (No updated ROM)
Have fun.
Click to expand...
Click to collapse
It's on latest official that came with device, I take it there is no twrp or anything out for this device ATM?

Just check a view posts above. I've described how to get the newest FW.
So if the factory ROM-version is installed, unlock the BL and after then update ur ROM. Jfi.
BTW_
Atm there's no custom recovery available for the M3 Lite Versions. U have to compile it by urself or make a request on Hovatek.com

essayn said:
Just check a view posts above. I've described how to get the newest FW.
So if the factory ROM-version is installed, unlock the BL and after then update ur ROM. Jfi.
BTW_
Atm there's no custom recovery available for the M3 Lite Versions. U have to compile it by urself or make a request on Hovatek.com
Click to expand...
Click to collapse
I'm not bothered about updating the firmware ATM more so custom recovery but will look into it after my holiday.

I have requested official forum for this device and looks to be accepted so hopefully get some development going for this device soon...

There seems to be no way to retrieve the unlock code for Wifi-only tablets from the official Huawei site, as it demands the IMEI which is obviously missing.
I have contacted Huawei support with the product ID and serial number of my M3 Lite 10. One day later I have received the unlock code. I think that having been polite has helped
.

Storage question
Hello,
First of all: sorry, if the question is 'noobish', but as a matter of fact I am noob as far as android is concerned
I just bought this tablet for my son (LTE version), and I was quite surprised to find out that I can't move the installed applications to SD card.
Are there any hints and tips on how to take advantage of the big SD card, so my son's game data would not have to be stored in the internal memory?
The only default option is to change the memory from internal to SD, after the tablet restarts. But I assume it uses then only the SD card, and I am looking for a solution I remember from Samsung phone, where I could choose certain apps to move from internal memory to SD.
Another question, just by the way, is following: when I install an apk file from the SD card, during the installation process every few seconds I get a pop-up saying the application is not responding (although the installation is in progress). Any way to disable those annoying pop-ups?
I'd appreciate any feedback

Mi Note 10 Pro Hard Brick

(First of all sorry for my English, I'm from Mexico)
Hello Friends, this is my first post, however, I have always used this forum as a guide along the phones I have had.
A few days ago I made a Hard Brick to my Mi Note 10 Pro, this while trying to load the Xiaomi EU Rom. I have seen many tutorials where they indicate how to revive it, without success since most are focused on the phone turning on in Fastboot mode, mine does not turn on in any way
I managed to make the phone recognize the PC in EDL mode but when flashing in Mi Tools it asks for a My account, when entering it the software tells me that my account is not authorized to carry out that transaction.
{
"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"
}
​Someone here managed to solve this or know of some method in which you do not need that authorized account and finally retrieve the phone?
I would greatly appreciate your help

dbaesteban said:
(First of all sorry for my English, I'm from Mexico)
Hello Friends, this is my first post, however, I have always used this forum as a guide along the phones I have had.
A few days ago I made a Hard Brick to my Mi Note 10 Pro, this while trying to load the Xiaomi EU Rom. I have seen many tutorials where they indicate how to revive it, without success since most are focused on the phone turning on in Fastboot mode, mine does not turn on in any way
I managed to make the phone recognize the PC in EDL mode but when flashing in Mi Tools it asks for a My account, when entering it the software tells me that my account is not authorized to carry out that transaction.
​Someone here managed to solve this or know of some method in which you do not need that authorized account and finally retrieve the phone?
I would greatly appreciate your help
Click to expand...
Click to collapse
do fastboot mode work?

albo.ma said:
do fastboot mode work?
Click to expand...
Click to collapse
Fastboot is an Android protocol that allows you to modify the filesystem through a USB connection to the smartphone, however, in my case it does not enter that mode, only EDL

i'm sorry but never happened to me... did u tried mi flash to flash something? does mi flash recognize your mi note 10 in edl mode?

albo.ma said:
i'm sorry but never happened to me... did u tried mi flash to flash something? does mi flash recognize your mi note 10 in edl mode?
Click to expand...
Click to collapse
Yes, I already tried Mi Flash, but it seems that you need an authorized account, here is the image of the software:

You could try QFIL (Qualcomm Flash Image Loader). I personally haven't needed to use it but it's designed to work with all Qualcomm Android devices.
Some info links
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
https://androidmtk.com/download-qpst-flash-tool
https://www.google.co.nz/url?sa=t&s...jAEegQIDBAO&usg=AOvVaw2g_XEnwfWA5Aj-IyquRhN2p

did a quick research and found these:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
patched version of mi flash to bypass authorization, but for redmi note 5 - check the thread if it works for other models too
https://in.c.mi.com/thread-1571278-1-1.html
people are requesting authorization there, do not know if they ever succeed but maybe it is worth to try

grandma_p said:
did a quick research and found these:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
patched version of mi flash to bypass authorization, but for redmi note 5 - check the thread if it works for other models too
https://in.c.mi.com/thread-1571278-1-1.html
people are requesting authorization there, do not know if they ever succeed but maybe it is worth to try
Click to expand...
Click to collapse
It seems to work, I have been trying for several hours to find the right .mbl for the MI CC9 Pro without success, I will continue searching and inform you.
Thank you for the support!

It looks like Mi Tools need to bind your computer to your device in order to give you authorization, i think you need to ask for authorization in the Official Xiaomi Support Forums.

tadad1 said:
You could try QFIL (Qualcomm Flash Image Loader). I personally haven't needed to use it but it's designed to work with all Qualcomm Android devices.
Some info links
https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
https://androidmtk.com/download-qpst-flash-tool
https://www.google.co.nz/url?sa=t&s...jAEegQIDBAO&usg=AOvVaw2g_XEnwfWA5Aj-IyquRhN2p
Click to expand...
Click to collapse
Thanks, I'm still looking for the correct files for Mi Note 10 Pro, it seems they are limited

CescVicious said:
It looks like Mi Tools need to bind your computer to your device in order to give you authorization, i think you need to ask for authorization in the Official Xiaomi Support Forums.
Click to expand...
Click to collapse
Thank you !, I already tried and posted to see if they hopefully give me authorization :good:

dbaesteban said:
Thanks, I'm still looking for the correct files for Mi Note 10 Pro, it seems they are limited
Click to expand...
Click to collapse
You need to download a fastboot ROM, I checked and they were all there although in the video there is only one XML file but in the MIUI fastboot ROM there are 5 but I was able to load them into QFIL so I think it would not be a problem.
Have a look here you will find all the tucana ROMs
https://t.me/s/MIUIUpdatesTracker?q=#tucana
The last fastboot ROM was 11.0.9.0. you will need to extract the .tgz file which will give you a .tar file which you need to then extract again to get the files needed.

tadad1 said:
You need to download a fastboot ROM, I checked and they were all there although in the video there is only one XML file but in the MIUI fastboot ROM there are 5 but I was able to load them into QFIL so I think it would not be a problem.
Have a look here you will find all the tucana ROMs
https://t.me/s/MIUIUpdatesTracker?q=#tucana
The last fastboot ROM was 11.0.9.0. you will need to extract the .tgz file which will give you a .tar file which you need to then extract again to get the files needed.
Click to expand...
Click to collapse
Yes, in fact I tried all the xml files and their possible combinations without success.
The file "programmer patch", in this case comes in extension .elf and in the videos that I have seen is extension .mbn, Additional the first xml that is loaded is also called rawprogram.xml in the firmware for my Note 10 there are none file named like that.
I will keep searching and if I find something, I will post it for users who have this problem in the future
this is the error that gives me in all cases

.elf and .mbl are both supported by QFIL so should be fine. I have 6 .XML, rawprogram0.xml to rawprogram5.xml. When I press the load XML button I can click and drag and select them all at once. It then prompts me to load the patch.xml once again patch0.xml to patch5.xml and drag and select all. They should now all appear in the Rawprogram and Patch window. Unfortunately I can't get into EDL mode to try flashing but it looks like you are already in EDL. All the best.

Well, after many days of searching without solution, I decided to take it to the technical service, who flashed it in EDL mode with the UFT box.
The cell phone is walking and without any anomaly.
Thank you all for your valuable help.

dbaesteban said:
Well, after many days of searching without solution, I decided to take it to the technical service, who flashed it in EDL mode with the UFT box.
The cell phone is walking and without any anomaly.
Thank you all for your valuable help.
Click to expand...
Click to collapse
is there any way other than UFT box to unbrick the phone mine have working EDL, fastboot , offical recovery but relock bootloader ..:crying:

I am having the exact issue in attempt to update the rom through fastboot. My tucana is no more responding to charging, pwr + Vol combination, detection to laptop etc. I have tried making my own EDL cable and its working with K20 but not with Tucana. Can you please brief how you managed to get phone into EDL mode?

Question how to downgrade sm-a12/5u from sw_rev3 to sw_rev1

i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?

tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded

wouldnt there be a way through twrp or brom mode?

tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
Nope you can try brom mode but i dont trust if works
If you buy a samsung device depending of the device (like this A12 and the MTK imei bug) is not a good idea to upgrade

tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help

I tryed to downgrade via TWRP flashing baseband and BL
Now my A12 is DEAD and i dont had a box to repair it (after flash i see the security error screen and flashed again the Binary 3 BL once odin tell me passed the phone doesn't booted again)
I just wanted to get the imei working because the firmware on the binary 3 (11 and 12) android system uses all my ram memory trying to get the signal working
F*** *** Samsung and mediatek next time i bought an exynos or qualcomm variant

tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
The last rom that i used on my A12 was pixel experience and worked perfectly on binary 3 android 11 based firmare (A125MUBUS3BVF1) just installed TWRP with nulled vbmeta flashed the image as system (not as super) and wiped the data (not advanced wipe) rebooted and the gsi was booted (only bugs mentionated on the thread and the touch bug)

Allehandro said:
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
Click to expand...
Click to collapse
i can access brom mode if that helps

tekkitheidiot said:
i can access brom mode if that helps
Click to expand...
Click to collapse
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.

Allehandro said:
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Click to expand...
Click to collapse
i downgraded to the earliest binary 3, then used test points. worked perfectly

tekkitheidiot said:
i downgraded to the earliest binary 3, then used test points. worked perfectly
Click to expand...
Click to collapse
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover

Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
its relatively easy tbh. just be careful around the volume buttons, but everything else is okay. there arent too many cables to rip

Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
Its easy to open but be careful with the power/fingerprint sensor flex i think the testpoint is near of the charger flex in the mainboard (i see youtube tutorials to access to Brom mode and preloader)
{
"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"
}

Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.

LAST_krypton said:
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
Click to expand...
Click to collapse
where would i find this scattar firmware?

tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working

MauriJ2001 said:
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
Click to expand...
Click to collapse
ill look through it. thanks

tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
You generate it your self

To unlock bootloader on these the easiest way is to convert it to an a125w xac by flashing the a125w bl files. Unlock bootloader with seccfg. Then flash ap, cp, and csc from a125w with odin and when it boots up it should show as a125w. Also in download mode it shows the same. My imei says unknown but i believe thats caused by unlocking bootloader so if you relock it after converting it should go back to normal. Playing with mtk modem tool to rewrite imei. Tried using xposed imei changer but didnt seem effective.

Untouched Poco F2 Pro (SJKEUXM) Unknown baseband after latest update (13.0.8.0 SJKEUXM)

Hello,
I dunno if this thread is still active but I have the EU variant Poco F2 Pro and this has been untouched since 2020(no I regret not unlocking the bootloader). And just last week, (I think) after receiving the latest patch update, I suddenly lost my baseband. Hence I now have no signal. I have raken my ohone to a technician for consultation and checkup and he was the one who noticed the "unknown baseband", Suffice to say my IMEI is also gone. He told me that rhe only way to solve this is to reflash OS. Unfortunately, my bootloader is still locked because I said this is still untouched (I regret it now).
So I did some research and came across this DFT Pro Tool for mobile maintenance which works on multiple brands and claims it can fix the IMEI/baseband issue even with bootloader locked. PROBLEM IS, you have to buy it for $70 and for something you'll gonna be using just once, that is a huge sum.
Now I have sent Fredback to Poco about this and requested for a rollback update (idk if they reply to such cases) just to see if the current update is the issue. I have also tried redownloading and reflashing the full latest firmware via the update menu but it did not solve anything.
The last thing on my mind is to reflash an older version (maybe 13.0.5.0, 4.0, or 3.0) via recovery but I know xiaomi and Poco implemented an anti rollback feature (which I now think is kinda selfish and stupid of them).
I also have this crazy idea of extracting the baseband zip from a previous version of the rom, renaming it 'update.zip" and flashing but I doubt that it's as simple as that.
Anyone encountered a similar issue?
{
"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"
}

ichigo_kurosaki said:
Hello,
I dunno if this thread is still active but I have the EU variant Poco F2 Pro and this has been untouched since 2020(no I regret not unlocking the bootloader). And just last week, (I think) after receiving the latest patch update, I suddenly lost my baseband. Hence I now have no signal. I have raken my ohone to a technician for consultation and checkup and he was the one who noticed the "unknown baseband", Suffice to say my IMEI is also gone. He told me that rhe only way to solve this is to reflash OS. Unfortunately, my bootloader is still locked because I said this is still untouched (I regret it now).
Click to expand...
Click to collapse
V13.0.8.0.SJKEUXM is a stable beta, and yes Xiaomi is updating with Beta versions on the stable channel and this is nothing new, many like you have found themselves with bricked phones.
At first tried with https://www.xiaomitool.com/V2/ if no result reposted.

Will it work even with locked bootloader? Thanks for the reply anyway.

ichigo_kurosaki said:
Will it work even with locked bootloader? Thanks for the reply anyway.
Click to expand...
Click to collapse
First try to reinstall the same version with the OTA.

NOSS8 said:
First try to reinstall the same version with the OTA.
Click to expand...
Click to collapse
Already did that. Tried the ota and the full rom (download full package).

ichigo_kurosaki said:
Already did that. Tried the ota and the full rom (download full package).
Click to expand...
Click to collapse
So;use https://www.xiaomitool.com/V2/,select bricked device.(Not 100% guaranteed that it will work)

NOSS8 said:
So;use https://www.xiaomitool.com/V2/,select bricked device.(Not 100% guaranteed that it will work)
Click to expand...
Click to collapse
Yes you are right. This method is not guaranteed. I tried to trick the tool into thinking my Poco F2 Pro was bricked. I got as far as to the firmware selwction for my device (there was IMI and IMI-new) but I thinkini represents redmi k30 pro because when i tried to proceed it was searching for china rom (when in fact I have F2 eu variant). Idk what imi new is. Maybe that is my device/global and eu f2. But when i tried to proceed i get this error i was lucky to cime uo upon doing google search.

Try with the same rom or update.
This tool is able to detect the rom.

NOSS8 said:
Try with the same rom or update.
This tool is able to detect the rom.
Click to expand...
Click to collapse
So i gotta use "my device is working" then "i want to mod ot" then select my rom file?

ichigo_kurosaki said:
So i gotta use "my device is working" then "i want to mod ot" then select my rom file?
Click to expand...
Click to collapse
try what is possible.

NOSS8 said:
try what is possible.
Click to expand...
Click to collapse
Almost succeeded. Lol. I went in to Mi Assistant in recovery so just to make the device appear in pcsuite mode. All was qell .a rom was found for my device. Almost done flashing then $hit happens and i was booted back (thankfully) to my current system.

NOSS8 said:
try what is possible.
Click to expand...
Click to collapse
Almost succeeded. Lol. I went in to Mi Assistant in recovery so just to make the device appear in pcsuite mode. All was qell .a rom was found for my device. Almost done flashing then $hit happens and i was booted back (thankfully) to my current

Hi, i have the global version (POCO F2 PRO) in the last month i had this problem. I dont know the reason, never did something whith software , only one day the phone freezen and when i do the reboot los this information. You have good news?? pd: sorry for my english no is my principal lenguage

Hello..
Please any solution yet? I also have Poco f2 pro global with same issue (bootloader is locked).. and currently the phone is not recognised by any pc(only charging) all settings are okay. The phone is not even reading USB otg flash storage again.