Develop Bugs

My experience with LG G3's KillSwitch

KillSwitch​
Three different ways that I found to get rid of the KillSwitch
Through deactivating and then reactivating your google account/s.
Using the Hard Brick Recovery method.
Octopus/Octoplusbox.
Explanation​
The one I actually tried was the Hard Brick Recovery Method (WillCracker), but
even after that I was still unable to bypass the KillSwitch. So I went back BoardDiag and decided to flash the System, UserData, and Cache since I still couldn't get into download mode.
After about 5-6 hours it was completed. I try booting up download mode and guess what?! KillSwitch is still there xD. I'm absolutely fustrated now and all I could think of is to flash the rest of the files that the HBRM didn't say anything about.
I started flashing in this order: Modem, Misc, Persist, and RCT. Everything is now flashed and I hope everything worksout.
I turn on the phone, waiting patiently. Bootloop over and over again, but guess what?! I tried download mode one last time before I was going to go ape $h!t. Then to my surprise the download mode screen turned on, I used the LG Flash Tool and I am now killswitch free.
KillSwitch did come back after a few updates, but I was able to enter in a pin code allowing me in the future to turn it off at will
Well thank you all for listening, just wanted to share my experience.
as my first post, I do apologize in advance if this is the wrong area for this.
Keep on keeping on xD

Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!

siredux said:
Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!
Click to expand...
Click to collapse
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963

Solved
JackTraits said:
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963
Click to expand...
Click to collapse
Link u shared shows Test points for G2 .... Correct test Points for G3 are Shown in following video
https://www.youtube.com/watch?v=04AgASAWJu8

[GUIDE] How to correct a wrong shown build number from settings menu

Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
 @BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.​
Be aware, and backup before doing this or everything you're dubious about.
Cheers

nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.

shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.

nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15

sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.

RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:

I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?

BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)

RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.

BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.

RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.

BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?

RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.

BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this

@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited

RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them

RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help

shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)

RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:

shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order

Don't know what to do, am stuck with errors

I'm stuck somehow, I don't know what to do. I tried flashing TWRP, it said failed, and nothing is happening. Guys, someone help

IAmNotANerd said:
I'm stuck somehow, I don't know what to do. I tried flashing TWRP, it said failed, and nothing is happening. Guys, someone help
Click to expand...
Click to collapse
Do you have the latest SDK platform-tools??
What OS version were you on before you started this process?
Do you know how to fastboot a factory image?

Badger50 said:
Do you have the latest SDK platform-tools??
What OS version were you on before you started this process?
Do you know how to fastboot a factory image?
Click to expand...
Click to collapse
Yes, have the latest SDK tools
Was on Android 9
Not actually. I follow some youtube tutorials to do so.

IAmNotANerd said:
Yes, have the latest SDK tools
Was on Android 9
Not actually. I follow some youtube tutorials to do so.
Click to expand...
Click to collapse
Use the factory image that coincides with your current system, September I would assume. Then follow the directions here.
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335

Badger50 said:
Use the factory image that coincides with your current system, September I would assume. Then follow the directions here.
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Click to expand...
Click to collapse
Could you walk me through it? Its kinda greek to me

as of now Im with no TWRP and my system says 'No Command' many times, sometimes just gets stuck on the android loading google logo screen. or sometiems says that 'deivce is corrupted' screen

IAmNotANerd said:
Could you walk me through it? Its kinda greek to me
Click to expand...
Click to collapse
After you download the factory image, extract it.
Place the extracted files in your SDK platform-tools folder.
That will include: Bootloader, Radio, the flash-all.bat file, and the large secondary zip you pulled from the factory image.
Right click the flash-all.bat file with your mouse, and remove the -w toward the end of the script, and leave a single space between the remaining words, then save your edit.
This will not wipe your internal data.
Then, put your phone into bootloader mode manually and connect to your pc.
Open a command prompt on your platform-tools folder and type in...fastboot devices...If you see your phone ID displayed, your good.
Now go back to your platform-tools folder and double click the flash-all.bat file to start the installation process.
Let us know how it goes :good:

Badger50 said:
After you download the factory image, extract it.
Place the extracted files in your SDK platform-tools folder.
That will include: Bootloader, Radio, the flash-all.bat file, and the large secondary zip you pulled from the factory image.
Right click the flash-all.bat file with your mouse, and remove the -w toward the end of the script, and leave a single space between the remaining words, then save your edit.
This will not wipe your internal data.
Then, put your phone into bootloader mode manually and connect to your pc.
Open a command prompt on your platform-tools folder and type in...fastboot devices...If you see your phone ID displayed, your good.
Now go back to your platform-tools folder and double click the flash-all.bat file to start the installation process.
Let us know how it goes :good:
Click to expand...
Click to collapse
This is where I am now. Should I go ahead and factory reset my device? Or is there some error during installation? (Kind of thought as it said some files weee missing as attached in the photo there)

IAmNotANerd said:
This is where I am now.
Click to expand...
Click to collapse
You don't appear to be in bootloader mode. That's recovery. With the phone off, hold the power button and volume down until you see the bootloader screen.

Badger50 said:
You don't appear to be in bootloader mode. That's recovery. With the phone off, hold the power button and volume down until you see the bootloader screen.
Click to expand...
Click to collapse
I did the steps you said to me in that mode, then this opened, all on its own.

Also now it’s giving me two options only. Try again, and factory reset, can do one only I suppose.

IAmNotANerd said:
I did the steps you said to me in that mode, then this opened, all on its own.
Click to expand...
Click to collapse
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.

Badger50 said:
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Click to expand...
Click to collapse
Yep, repeating procedure and updating you soon.

Badger50 said:
Interesting. The installation appeared to be going fine. Never have seen that outcome before. Run it again and see what happens.
Click to expand...
Click to collapse
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/

IAmNotANerd said:
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
Click to expand...
Click to collapse
Yeah, you may have not done yourself any favors when you incorrectly installed twrp.
I now recommend you use the Dueces script. It has saved a bunch of people in your predicament.
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
IAmNotANerd said:
Same thing again, no change. Is there something I should do regarding TWRP? Even that isn’t installed properly.
And apart from that, this post is also scaring some **** outta me..,
https://www.reddit.com/r/GooglePixel/comments/7rl7gt/my_pixel_2_xl_64gb_bricked_itself_today/
Click to expand...
Click to collapse
You can find it here.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Thanks a ton mate! Job done, back to stock now. I really gotta find a way to get a custom now. The tutorial I followed got me in a weird state.

IAmNotANerd said:
Thanks a ton mate! Job done, back to stock now. I really gotta find a way to get a custom now. The tutorial I followed got me in a weird state.
Click to expand...
Click to collapse
Congrats bruh! Now do some reading before you jump into the fire again :good:

Badger50 said:
Congrats bruh! Now do some reading before you jump into the fire again :good:
Click to expand...
Click to collapse
This needs to be said. Read everything you can before doing anything. Read everything about the problems that you might come across. And, most importantly, read about how to fix things if you aren't successful. I knew nothing, apart from what I'd read, and I've managed seven phones and three tablets, plus my brother's phones and tablets. I have never bricked any device, because I read and follow instructions. The great thing is, you can learn a lot from guides and such, because, if you're paying attention, you get a better understanding of what is going on.
He's right...read everything you can before doing anything you don't know how to do or understand. And, just for good measure, ask before, and not after you get yourself into a bad situation

Just my two cents... Is incredible how people takes risk on a 1000 dollars phone...

Question chinese tencent 120w red magic 6 pro 12gb/256gb eclipse black version with global rom?

anyone here that has successfully flashed this model of the rm 6 pro with a global rom? does that work or will i brick it?

Bet your the first tester to find out

Pachacouti said:
Bet your the first tester to find out
Click to expand...
Click to collapse
no, im too scared im a newb in this and i dont want to brick it. if i brick it i will be lost cause im a newb

And noobs had to start somewhere. So say someone says it works, then what will you do?

Pachacouti said:
And noobs had to start somewhere. So say someone says it works, then what will you do?
Click to expand...
Click to collapse
i would give it a try ^^

But your replying to me. I'd be shredding cables by now lol, but hey, is it possible your fone is a rebranded redmi 6 pro? Plenty of tuts here for that, but I'll try to help/guide you should you need it, tell me, what stock flashing application will you use to flash your stock BACK in case of a mistake?

Pachacouti said:
Pachacouti said:
But your replying to me. I'd be shredding cables by now lol, but hey, is it possible your fone is a rebranded redmi 6 pro? Plenty of tuts here for that, but I'll trry to help/guide you should you need it, tell me, what stock flashing application will you use to flash your stock BACK in case of a mistake?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the problem is that the vendor from china put some crippled stock rom on my phone where they removed the system update service and so i cant do a local update with the phone. my rm 6 telegram group suggested that i install the qcom 9008 usb driver on my pc and boot my phone via adb into qcom 9008 edl mode and use miflash to flash it with a 4.15 unbrick package and if this would work i would have intact system update again and could flash it with a local update with the firmware id like. thanks for the help btw. gotta go out in 5 minutes but be back in a bit. please give me your opinion, i will read it once im back

What you wrote sounds good. Your flashing app is miflash. Download the 4.14 unbrick, and load it into miflash without fone plugged in, power fone OFF, start the miflash, hit download/flash (dont know the actual button to do the damage), then plug turned off fone into usb, miflash should auto find and flash, anything after that, feel free to ask.
Ps you could just jump in the deep end and flash the one you WANT, so that if it fails you'll know if it works or not, and will have tested a rom before flashing your stock back, kinda better than flashing stock first in a way.

Pachacouti said:
What you wrote sounds good. Your flashing app is miflash. Download the 4.14 unbrick, and load it into miflash without fone plugged in, power fone OFF, start the miflash, hit download/flash (dont know the actual button to do the damage), then plug turned off fone into usb, miflash should auto find and flash, anything after that, feel free to ask.
Ps you could just jump in the deep end and flash the one you WANT, so that if it fails you'll know if it works or not, and will have tested a rom before flashing your stock back, kinda better than flashing stock first in a way.
Click to expand...
Click to collapse
thanks for the suggestions! i want to give this a try as soon as i have some time. buthow do i backup my current stock rom in case the new rom wont work? i only know about rom manager app but that needs a rooted phone and mines isnt rooted. is there a way to backup the stock rom without having a rooted device?

Forget backing that up, your already at the stage where you learn if you back this up now, you MAY also back up the problem and have to do it all again, take my advice, keep it simple.
For your 'backup' - download latest official stock from your fone maker.
You may want to revert back AFTER you test the one you want to test.
So test first while it's 'broken' knowing once you go back to stock, it aint broke, dont fix it.

Pachacouti said:
Forget backing that up, your already at the stage where you learn if you back this up now, you MAY also back up the problem and have to do it all again, take my advice, keep it simple.
For your 'backup' - download latest official stock from your fone maker.
You may want to revert back AFTER you test the one you want to test.
So test first while it's 'broken' knowing once you go back to stock, it aint broke, dont fix it.
Click to expand...
Click to collapse
hey there! thanks for your tips, i appreciate it! ok just to clear things up, with "stock" firmware, you mean the official latest chinese firmware from the chinese nubia page, right?

Yup, if thats what you know is your STOCK, ie, not the one you wanna test, but in your scenario, I'd flash the test before stock, this way you gain experience flashing, and if you mess up, then you flash the stock, and learn not to. (again lol)
To clarify, stock is the firmware the fone maker has on their site.
Follow thir instructions, it's easier than you think, as my auld man told me, when testing, write down every step, so you REMEMBER instead of being unsure because I forgot....

Pachacouti said:
Yup, if thats what you know is your STOCK, ie, not the one you wanna test, but in your scenario, I'd flash the test before stock, this way you gain experience flashing, and if you mess up, then you flash the stock, and learn not to. (again lol)
To clarify, stock is the firmware the fone maker has on their site.
Follow thir instructions, it's easier than you think, as my auld man told me, when testing, write down every step, so you REMEMBER instead of being unsure because I forgot....
Click to expand...
Click to collapse
ok i got it. thanks for the help! i have the stock ready on my computer. unfortunately i cant flash my phone by following the manufacturers steps because my phone vendor flashed my phone with some custom chinese multi language firmware with google already pre installed. and whoever edited this firmware before flashing it on my new phone, removed the system service that is necessary to launch the "system update" options. therefore i have no way of making a local firmware update in my phone. unfortunately the red magic 6 pro also does not have a local update option in the recovery menu. thats why my only option is flashing the phone with my computer. but in the worst case i will have the latest stock rom on my phone in the end and this will have the system update options intact. thanks again for all the help!

Need help unlocking AT&T Calypso (U318AA)

Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.

adrian0883 said:
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
Click to expand...
Click to collapse
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process

i can help you , if your device still soft break
Osamaaj03 said:
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
Click to expand...
Click to collapse

sahelkhan022 said:
i can help you , if your device still soft break
Click to expand...
Click to collapse
it is, I think the problem is with the super image but I'm not 100% sure. so if you can share a full mtk client backup it would be awesome. if not, a super image will do

your device stuck on logo ? or deadboot ?

842.92 MB file on MEGA
mega.nz

sahelkhan022 said:
your device stuck on logo ? or deadboot ?
Click to expand...
Click to collapse
every time I try to turn it on it bootloops to fastboot mode, I suspect that the issue is a super image I found online, flashed not knowing that it was corrupted (which I discovered later), and I foolishly didn't create a backup (why I went and downloaded the corrupted image in the first place) thinking that I will never go back to the stock rom but now after I have used a couple gsi's for a while found out that the og rom performance was much better and decided to go back

sahelkhan022 said:
842.92 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
so this is just a bunch of .bin files that I have to flash using mtk client to said partitions? just making sure

and just to let you know I might not be able to download the file today, the internet is pretty sucky where I'm rn, so I hope you don't have a problem keeping the file up till tomorrow. and just wanted to thank you for the incredible help, I've been trying to fix this phone for the last two weeks which was headache inducing say the least.

you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..

sorry for the late response, but yeah I've flashed all of the files using mtkclient and it didn't work Idk if I have messed things up, I thought reflashing all of the stock firmware would fix everything but it seems that there's still something wrong

sahelkhan022 said:
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
Click to expand...
Click to collapse
I've unlocked the bootloader and disabled boot verification, tried fastboot -w and fastboot format userdata and non of it worked, and I'm really sorry but I can't share my screen because as I've mentioned before my internet is bad and I had to go somewhere else to get the files. can I share anything else with you that might help, I have some recovery log files

IT WORKED!!!!! I don't know what was the problem, I've tried flashing the files again but this time using the terminal instead of the gui AND IT WORKED. THANK YOU THANK YOU THANK YOU

I'm going to upload the files later in case someone else encountered the same problem