Database Info

Purchased a Shield K1 Tablet: Should I Root?

Purchased a Shield K1 Tablet
Which will arrive this week, and there are things I would like to know about it, i.e notably on whether or not I should unlock and root it, despite the potential risk of doing so.
What I plan on using this for is primarily emulation (Snes through PSP and maybe Dolphin, no idea how well that works yet) That being said, are there things I should do to it?
Do as in, things I can root or flash to give myself the best possible experience, to get the most out of this? I've seen a lot of custom ROMs, Cyanogenmod (which I have on my
Nexus 7 2012, along with a dual boot OS). I have been thinking about having the stock Android 5.1.1, alongside Android 4.1.2 for the sake of Wii remote support since Google
foolishly broke that part of Bluetooth (and the part that never will be fixed again). The problem is, I don't know how hard or cumbersome it would be to do such a thing
without bricking the Shield tablet and ending up with a pricey paperweight. What tutorials, guides, etc should I look into before I consider such an undertaking? I want
to be sure I pick the right files and OS image(s) to install so I can do this right, if that makes sense.

I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.

koichirose said:
I just bought it too and was coming from a Nexus 7 2012.
Rooted with the latest CM 12.1 nightly, no issues so far.
Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.
Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
Click to expand...
Click to collapse
Fair enough, and I know that no device is perfect, everything has their own set of issues, so I don't think I'll regret getting a Shield Tablet, that much I know. I was going to get a Samsung Tab E 9.6, but the specs just didn't figure, esp. for someone who wants more power, you know? What about the Android OS ROM you install it with? Should I go with Android 5.1.1 or dual boot it with 4.1.2 instead so I can have Wii remote support? Thanks.

I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS

koichirose said:
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
Click to expand...
Click to collapse
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though :laugh:

the_randomizer85 said:
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though [emoji23]
Click to expand...
Click to collapse
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk

Exile1975 said:
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.
That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
Sent from my SM-G386T1 using Tapatalk
Click to expand...
Click to collapse
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?

http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
the_randomizer85 said:
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is
definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?
Reasons for the tablet:
1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming
2 - Multimedia, movies, YT, music and so on
So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
Click to expand...
Click to collapse

wiQbold said:
http://forum.xda-developers.com/shi...t-root-nvidia-shield-tablet-lollipop-t2972316
INSTALL DRIVER
-enable Developer Options
-enable Debugging Bridge
-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'
-shutdown
-hold Volume down and Powerbutton at same time
if the bootloader showed up
-do a 'fastboot devices' if it shows your device online then
-do 'fastboot oem unlock'
after that you have flash your recovery
go to the directory where the file is and
-do 'fastboot flash recovery your_file_here'
after that you can reboot to bootloader and go to recovery
copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)
and flash it over recovery.
reboot enjoy!
Click to expand...
Click to collapse
So I just follow the guide on the thread, or do I follow the guide you just posted?. The reason I ask is because in the thread's guide, past the parts where it said to install the ADB driver and then the USB drivers for the device, I'm not sure what "debugging bridge" is, unless you meant enable USB debugging, IDK.
- Enable USB developer mode
- Enable USB debugging
- Copy the recovery image and supersu.zip to where the ADB install folder is
- Open the program to open a CMD window to the install location
- Type "adb reboot bootloader"
- Etc
I mean, because the two guides are confusing me more, the forum guide, the thread, how it's worded...now I don't know. Sorry. Is that thread and your guide the same thing, all leading to ultimate unlock and root the device using ADB and the recovery image? And is it not feasible to install Android 4.1.2 as a dual boot OS image so I can test out the Wii Classic Controller since Google broke that part of the Bluetooth code in 4.2+?

there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging

wiQbold said:
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)
http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
and yes. usb-debugging
Click to expand...
Click to collapse
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?

the_randomizer85 said:
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then
the one above?
Click to expand...
Click to collapse
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot

wiQbold said:
it is a old thread. It s for kitkat..
I think you go like I said.
be sure. adb drivers are installed
Developer Options
Usb debugging
cmd
'adb devices'
check dialog
'adb reboot-bootloader'
'fastboot devices'
look for output
'fastboot oem unlock`
'fastboot flash recovery /directory/to/your-recovery-file'
'fastboot reboot-bootloader'
go to recovery
flash SuperSU.zip
reboot
Click to expand...
Click to collapse
And I go into recovery mode by holding vol. down and power, right? And in that mode I flash the SuperSu.zip correct? And I did get the recovery.img from nVidia's source, which I assume is the one I use in Command. Okay. Rebooting I assume is well, heh, also by holding down power. I also noticed both of those threads have the OS name Lollipop in the thread title.

Proper OS cleanup of new OnePlu7 Pro

Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.

Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.

brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.

Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:

brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.

I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.

Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:

AT&T Radiant Core (Tinno U304AA) - Modding Discussion

Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.

UPDATE: found a stock system image dump, thank you to @lopestom for directing me to this. This guy's been the MediaTek king for as long as I can remember.
It appears to be a dtbo and system partition dump. It also has the vendor partition and a (partial?) boot image dump. Not sure if things like the full boot and recovery images are stored somewhere in here, I didn't look too deeply into it yet. I have no idea how whoever this is managed to pull these partitions... they either got root access somehow, or they found a proper Download Agent and Auth file to pull it all. Either one of these would be awesome. I reached out to the user to ask them how they did it, we will see what they say if they want to share how they did it.
https://git.rip/dumps/att/u304aa

jasonmerc said:
Picked up an AT&T Radiant Core for cheap at a store around me. I don't intend to use it with AT&T, it was just such a low price that I figured I'd get it and see if I can break into it just for fun. It's an MTK6739 chipset phone, so in theory it should be easy to pull partitions from this thing with something like SPFT (or Miracle Box, if you paid for it) and do a dirty port of TWRP to get root privileges on it. But this is harder than it seems.
I need an auth file to do anything with SPFT. Apparently this has to do with some kind of "secure boot" mechanism that MediaTeks sometimes have now. There's no stock firmware for this device online from what I can find, nor for the generic version of the device, the Tinno U304AA (AT&T just rebranded it). If I had a stock firmware image, maybe I could risk wiping the partitions and reflashing the stock firmware to get rid of the secure boot stuff.
I saw a guide for how to access the bootloader on the Tinno U304AA generic version, but on the AT&T version of the phone there's no option in the boot select menu (Vol. UP + Power) to get to the bootloader to run a fastboot oem unlock. All the AT&T version has is recovery and normal boot. I'm not sure what I can do to maybe reset this to get the other options. Maybe if I had the stock firmware for the generic version of the phone I could overwrite it and get access to those other options.
Either way, just posting this up for anyone else that got one of these and wants to collaborate/contribute. Maybe with enough collective brainpower we can make something happen.
Click to expand...
Click to collapse
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.

sjjtnj said:
OMG! So excited to see this here! My Mom gave my nephew this phone and niece has one. So I've been trying my best to get the thing to at least be a decent phone! I installed a launcher on it, changed the icons and wallpaper and made it look good at least. It will be nice to have someone to talk to about this. The thing has been beyond frustrating! First off though how did you get the computer to recognize it? I can't get Windows or Linux to recognize it and couldn't find any drivers. If you managed that much you got further than I did. I haven't tried with my nieces though. It might just be his phone. She's 13 so it took awhile to pry it from her long enough to find out what kind it was, but I'm willing to try to get it from her once again if the phone can be improved.
Click to expand...
Click to collapse
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.

jasonmerc said:
Linux should just work, plug in the thing and the "drivers" if you will should be there already. Check the phone's settings for USB Debugging in the Developer Options if there's further trouble.
Don't get me wrong too, this phone is, was, and will always be a piece of junk. There's no getting around a screen this bad and 1GB of RAM. I'm actively trying to find a Download Agent and Auth File combo to get this thing to work with SPFT so I can try to port a custom recovery to get us Magisk root permissions at least. Root will make the phone slightly better, but it will still be junk. Unless we can get kernel source for it as well to mess with things like clock speeds and CPU governors (which LEGALLY we are supposed to be guaranteed, but good luck convincing a Chinese company to give it to you) everything we do, if we CAN do anything, will be like deodorant on a turd. It'll smell a little better, but it's still a turd.
Click to expand...
Click to collapse
Right, I'm considering giving him my current phone when I get a new one. It doesn't seem like I'm going to be able to unlock and root it so I want a phone I can. Mainly for space personally. He's young so he doesn't need it rooted, but I'm thinking if I can root it then I might be able to use it to root my phone. Speaking of rooting I think I found a way to root this phone. It took me a couple days to get the phone since he said he couldn't find it, but I have it now. It just needs to charge, but the battery sucks so it takes forever. I did find out that it does have a decent recovery. I had booted it into recovery and then I was messing around with the keys after the little passed out green guy popped up and suddenly it loaded stock recovery. It had an option to mount the system and flash with adb and everything. The only problem is I kept booting it by messing with keys. So I honestly don't know which ones worked. I kept booting into it last night by messing with them, but now I can't seem to get it to boot into the right recovery now that I'm trying to figure out the right key combination. I will figure it out though (eventually) and let you know what you have to click, but if you get the chance just mess with it and hopefully you'll find it like I did.
Also I was looking up the phones variants and downloaded a couple stock roms that I felt had all the right specs I'm going to try to flash one if I can get it plugged in. I downloaded custom twrp image's for them as well, and even found one twrp that I was able to download in the app. If you used it then you know that it takes you to a download page if you are downloading the wrong twrp.img. So the fact it let me download it in the app meant it tricked twrp into thinking it was that phone. So I'm going to try that stock rom first. Maybe we'll be able to change it to another model. It really needs something flashed, because it's a mess. I thought he messed it up, but after reading what you said maybe it's just the phone. He's young so it doesn't matter as much to him, but I feel bad for my niece. I really need to look into at least getting her another phone. I'm going to work on it later today and see what I can do. First I got to get it to work on the computer, but I may be able to root it without the computer. I'll keep you updated with my progress.

any luck with this?

Yeh, is there a status update?

Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.

sjjtnj said:
Sorry, I got a concussion and haven't been able to do much, but really I'm stuck because I can't get it to connect to the computer at all. Not in Windows or Linux. I think he's messed it up beyond repair at this point. The offline root gave me an error around the mounting of the system, but that can be done if you can get the recovery to show up. It's one of the options. I was trying this method. HERE see if you can get it plugged in and to work. Also, Kingoroot gets to 90% on the apk alone. So the computer app might do the trick. Then you can switch it to su. Really a rooted phone can get a lot done with apps like flashify and flashfire that we can't do right now. If you can get even a temp root let me know and I'll tell you what I found out about the apps to unlock the bootloader, flash TWRP, Flash Magisk, then flash ROMs. If you want to try the variant route I was trying then just do a search on google. Some sound just as bad, but other similar phones seem better. You can pick which one you want to try. The phone I have got to a point that it kept deleting applications and stuff on the phone and has trouble with the sd card. So I don't have the stuff I had saved on it anymore. I'm giving him my current phone when I get a new one. It's too messed up to salvage. I hope you have more luck.
Click to expand...
Click to collapse
I need to unlock my phone U304AA

Ok boys and girls, in case anyone is still wondering here is how to root this sucker.
https://drive.google.com/file/d/1--Ul1ae73zcejNuJ1a7ftq5sTo2VP8Ya/view?usp=drivesdk
Comes with two files. Mtksu amd magisk be sure to use the magisk version included in the zip. Install mtksu then wmagisk, open mtksu and install the top magisk option. Reboot then open magisk hit install when it asks. Now open mtksu scroll to the bottom and hit activate and reboot again. Should be good too go at this point. Oh yeah be sure to click apply at boot in mtksu. Not sure if this had been posted before or not. Now, to find a way to unlock bootloader and install twrp.

Thank you, I tried Mtksu on mine and it didn't work, but it might've been the phone. I don't have one of these anymore, but I hope you all the best of luck. For the bootloader and Twrp try Flashfire or flashify.

MTK bypass method released by some smart dudes out there. I will test if we can use SPFT on this phone now. Stay tuned. This could mean root & recovery in a matter of minutes.
EDIT: It ALMOST works. Technically it bypassed the auth file as advertised. The only thing left now is finding a compatible preloader/scatter file to use.

Used a modified Moto E6 Play scatter file to pull images from the device. Tried flashing over stuff and got an error. Long story short my U304AA is now permanently bricked, so I'm tapping out of this project here
I do have recovery and boot images that (supposedly) work if anyone else wants to try and take over Keep in mind these were pulled with a scatter file from a DIFFERENT phone that's of the same chipset, so not everything is guaranteed to work. For example, the preloader was pulled with the specified parameters but I do NOT know if it's functional
Because I'm tapping out, and because nobody else seems to have anything on this, I'm uploading everything I can. Some pulls are too big to upload and some just won't work for some reason, but use whatever you'd like for anything you can. Hope I did something helpful

I have searched in Google Search and the tutorials forum but not found a tutorial
_____________
Sent from my website: https://topsanphamhay.com/kem-chong-nang-danh-cho-da-dau-mun.html - https://topsanphamhay.com/kem-chong-nang-innisfree-perfect-uv-protection-cream-co-tot-khong.html - https://topsanphamhay.com/kem-chong...ifying-face-fluid-dry-touch-co-tot-khong.html using Iphone X

Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
My wife and I just got one, so now I have two of these but I'm not sure I trust AT&T enough to use the "free" phone that they sent.
It would be great if someone can pickup this project, especially since so many phones are now flooding the market.

I just got 3 of these "free" from AT&T. In fact I don't really need them, I just happen to have phones with an IMEI number that AT&T cannot decipher, so they sent me new phones just in case I can't use 4G.
Anyway, I'm trying to use mine as spare Google assistants scattered around the house, but because they run that crappy Android Go, the Go version of Assistant won't listen to me until I long-press the home button. I would also like to use them when I travel as a spare.
These things are essentially throw-away, so I'm OK to risk bricking one of them.
What I really want to do is install a real version of Android on here, has anyone managed to crack this yet?

I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images

kayshinonome said:
I personally have been writing and reading using this tool https://github.com/bkerler/mtkclient, which is much simpler than the others
Its a little rough around the edges, but it certainly works
My final problem is disabling secure boot (I already have a boot.img patched with magisk)
It appears that fastboot is simply not a mode for booting on this model, so I was wondering if anyone knows how to disable AVB by hand with just partition images
Click to expand...
Click to collapse
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader

luridphantom said:
if it's possible to downgrade the firmware to before the october 2019 patch, it might be possible to mtk-su the device: https://www.att.com/device-support/article/wireless/KM1376142/ATT/ATTU304AA
might be another alternative to trying to disable avb on a locked bootloader
Click to expand...
Click to collapse
Not possible to do, already tried before when I didn't brick it

KJ7LNW said:
Well AT&T is giving away lots of Radiant Core devices because of their 3G shutdown: https://www.xda-developers.com/att-3g-shutdown-free-phone/
Click to expand...
Click to collapse
Just got mine from this. I'd like to install something like NixOS mobile, but I've never used an android phone before. Will that be possible on this phone? If so, is there a good guide for newbs like myself?

Accidentally locked bootloader -- System destroyed

Hey there! I'm new around here and I'm not sure if this has been asked before... I found this thread but there are a couple differences between our cases and none of the solutions given in the comments seem to work:
"The system has been destroyed" Poco X3 NFC
So here's the thing -- I've been using this phone for a few months as a replacement for an iPhone. I used to be in the custom ROM scene back in 2015-2016 with an old Huawei I had, so I more or less know how all of this works. Since MIUI is visually horrible (in my opinion) I decided to try my luck at installing PixelExperience (great ROM, btw!). Since I've recovered my previous phone, this one has been sitting in a drawer for a couple months already, so I wanted to restore it to factory settings and sell it.
Aaaaand this is where **** happened. I had this weird intrusive thought of using "fastboot oem lock" before doing anything else just to see what would happen. The result? The phone is now bricked. I can access fastbook but that's about it, trying to boot into the system or recovery just gives me a "The system had been destroyed - Press power button to shutdown".
I know you can fix this by unlocking it again, but every tool I find online is meant for Windows and there are barely any solutions for macOS. I have found two of them: XiaoMiTool V2 (but needs adb to be enabled) and XiaomiADBFastbootTools, which seems to kind of work.
It detects the device when put in fastboot mode, but when clicking on "OEM Unlock" it just says "Token Verify Failed, reboot the device" (screenshot attached).
Trying to unlock it from the Terminal does pretty much the same thing (obviously).
Before you ask - Yes, I have all the required drivers installed as this is the exact same computer that I used to unlock the bootloader and flash OFRP. Everything works normally, it's just that I don't have access to the OEM unlock tokens to do it directly from the Terminal the same way I used to do it with previous phones.
So uhh... What can I do? Is it going to stay this way forever? Are there any solutions for macOS users that don't require having to use BootCamp or VM? I don't mind doing it but I'd rather have it as the very last resort, since it's too much of a hassle to do it. I have Xubuntu installed on my secondary drive, so if there is anything that could work on Linux, I'll take it too.
Thank you all for your help!
Edit 1: By the way! If this gets solved, could anyone be kind enough to guide me through the steps on how to mark it as [SOLVED] and close the thread? I'm really really bad at forums.

To the best of my knowledge, MIUI tools check online if the device is currently associated with a MI account -- and in case it isn't, nothing else goes...
My guess would be to try to run MiFlash with its last fastboot stock ROM in a Windows VM.
In case that doesn't work, taking it to Xiaomi tech support would be the best bet...

pnin said:
To the best of my knowledge, MIUI tools check online if the device is currently associated with a MI account -- and in case it isn't, nothing else goes...
My guess would be to try to run MiFlash with its last fastboot stock ROM in a Windows VM.
In case that doesn't work, taking it to Xiaomi tech support would be the best bet...
Click to expand...
Click to collapse
Thanks for taking your time to answer! I'll just have to install Windows in an external disk and see how it goes
I'm guessing MiFlash works offline, without checking anything about the phone on their servers, right?

kakuluva said:
I'm guessing MiFlash works offline, without checking anything about the phone on their servers, right?
Click to expand...
Click to collapse
I'm not really sure about that (haven't done it myself), but it has been the general recommendation here when faced with serious trouble so I would expect so. YMMV, though.

Blu bl140dl unlock bootloader and ROOT w/magisk

Unlocked bootloader and acheived root/magisk on b140dl aka blu view 3, i did search for this phone on xda before(1 week ago as my first stop) and could not find, or across across web, after deep hair pulling, disapointments in the dark ( I Im pretty new at this guys), and not trying to present something already found or reinvent the wheel, just trying to perpetuate the freedom to "really OWN your device and perceverence of never giving up and you shall prevail!!!!! Any questions, pm me

rtype77 said:
Unlocked bootloader and acheived root/magisk on b140dl aka blu view 3, i did search for this phone on xda before(1 week ago as my first stop) and could not find, or across across web, after deep hair pulling, disapointments in the dark ( I Im pretty new at this guys), and not trying to present something already found or reinvent the wheel, just trying to perpetuate the freedom to "really OWN your device and perceverence of never giving up and you shall prevail!!!!! Any questions, pm me
Click to expand...
Click to collapse
Im now working on removing orange status warning (only meaning unlocked bootloader with 5 sec. delay)
I did extract my stock image in .bin dump as well as extracting .img partitions from this dump. I tried the few online methods of altering the lk.bin hex and reflash leading to no boot, no lights, no nothing as if a security encryption signature principal must be in place, to put a halt if not matched. Not sure but could sure use some advice, Im kinda new at this.

I've also been trying to figure out how to port a twrp recovery, which i also attempted, flashed, same result-phone black, no boot, so i flashed back original, back to normal,(what a scare on such a dead response!!- holding power button down and nothing) So ive softbricked twice, and recovered twice without a problem.
Specs
Helio p22 mtk chipset (6762)
4.19.127 kernel android 11
I do realize each phone has different specific source and understand this determines if twrp compatible, correct me if im wrong my friends, im just learning and open, one more thing, ive gotten a status of p22 from installed play store app device info, cpu-z. no root permission. mtk _client tool gives me p35 as my processor which is the (6735). Maybe the difference is negligible in the two 2 readings? or the mtk_client is old and rounds the 6762 to 6765, as maybe there differences are small enough to ignore 62-65 differences? Like i mentioned Im very new, and though ive researched a lot, this is tough, but i must say, I love a good game of chess!!!!

. Ive currently got two of these phones and Im starting from scratch tryna do the same thing you are. So at least youre not alone. I figured id kinda follow the guide for the b130dl (since that seems to have so much success even with other variants and devices) idk how much help I will be, seeing as I havent done any development of any kind for about 5 years.... But since I have 2, lmk if there is anything kinda risky you wanna try. (After I catch up of course)

Yeah right on, im goin at orange status removal once again, I did do a little homework, and beleive the inability to flash any custom partition is due to encryption of partitions by dm verity and or AVB preventing boot even if rooted? Not sure exactly but reading and learning. btw my friend, Im Rob, pleasure to meet. I dont know any coding, though ready to learn, just mods a bit, though im relatively new to that as well, but i try being creative, and was stoked I actually pulled off root on this newer phone, unlocked the bootloader with mtk_client, from git-hub, no problem : https://www.google.com/url?sa=t&rct...er/mtkclient&usg=AOvVaw1EA0UgBcE8bbeVuiVn4L7c
I then read all partitions to my laptop which dumped in .bin form, from there i looked everywhere for a root on this phone. too new, as i found nothing. That made me think if mtk_gui could pull off unlocking the bl, what else can it do? So read its readme a bit and noticed the magisk root using adb and fastboot, with accompaning custom magisk for mtk. Thought i was probably wasting my time as this phones security is newer. Well, it worked, so bootloader down, root accomplished with magisk, now this orange state, which i tried online hex manipulation of lk.bin file and flashed it to original lk.bin partition on phone, no boot. Tried making a custom logo.bin and same flash, no boot. So used my mtk_client tool to flash my backup abov 2 partitions and, booted right up, no problem which led me to investigate this vb meta and AVB which im currently trying to grasp. Oh and yes i figured out how to take a complete flash dump into a .bin file with mtkclient, so I have backup of partitions from this tool by reading partitions section, and also backup by using the read flash option under flash in the tool. It gave me one giant file called user.bin. I researched what bin and img files are and learned we can use 7 zip or any storage compress/decompress software or cd iso software to open bin files, so preceded with 7 zip on user.bin file and was able to extract the partitions in .img format, really cool, so now i have backup in3 styles lol .bin partitions, .img partitions or 1 .bin complete rom dump which when opened with 7 zip gives you the img forms, been fun, but this orange state and security stuff seems a bit tricky to understand, so thats where im at my freind, Let me know you need any help, Good idea about starting with previous phone guide, my thoughts exactly as well when i started gettin my hands dirty lol What a universe in these gadgets, awesome

Is there anyway you could post a guide of sorts. Looking to unlock the bootloader and root (aren't we all).
Am relatively new at this. Last phone I rooted before this year was the Epic Touch! Please at least list which downloads are needed. Thanks in advance. *Jaymi*

Thsi a Specs by your phone?
Okay. Let's go to the beginning.
I have a friend who knows how to handle Mediatek phones. He even has a BLU MT6762 with Android 9. He compiled the TWRP himself. Maybe compile one to you.
I'll try to send him a message to know if he can help you.
But the bigger question is about the original firmware (without ROOT/Magisk). Have you tried using the Smart Phone Flash Tool (SPFT) to copy all the firmware? Is there an official stock firmware? So you could use the scatter.txt file to use SPFT.
If you couldn't use SPFT then were you forced to use mtk_client?
To unlock bootloader, can you use this guide?: https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
Update:
Okay. He agreed to help. He asked someone to put the stock recovery.img file attached to the message and information about fastboot:
Code:
fastboot getvar all
and fastbootd:
Code:
fastboot getvar all
Furthermore an experienced user should contact him to test the TWRP files he will compile. So think hard if you can get your phone back to normal if something strange happens. Usually just reinstall the stock file and everything will be simple. One more detail: you should be able to understand that the test needs the phone with the full wipe process and without using magisk at the moment.

rtype77 said:
Yeah right on, im goin at orange status removal once again, I did do a little homework, and beleive the inability to flash any custom partition is due to encryption of partitions by dm verity and or AVB preventing boot even if rooted? Not sure exactly but reading and learning. btw my friend, Im Rob, pleasure to meet. I dont know any coding, though ready to learn, just mods a bit, though im relatively new to that as well, but i try being creative, and was stoked I actually pulled off root on this newer phone, unlocked the bootloader with mtk_client, from git-hub, no problem : https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjlsKWdh7b2AhVXjokEHXJ1DD4QFnoECAsQAQ&url=https://github.com/bkerler/mtkclient&usg=AOvVaw1EA0UgBcE8bbeVuiVn4L7c
I then read all partitions to my laptop which dumped in .bin form, from there i looked everywhere for a root on this phone. too new, as i found nothing. That made me think if mtk_gui could pull off unlocking the bl, what else can it do? So read its readme a bit and noticed the magisk root using adb and fastboot, with accompaning custom magisk for mtk. Thought i was probably wasting my time as this phones security is newer. Well, it worked, so bootloader down, root accomplished with magisk, now this orange state, which i tried online hex manipulation of lk.bin file and flashed it to original lk.bin partition on phone, no boot. Tried making a custom logo.bin and same flash, no boot. So used my mtk_client tool to flash my backup abov 2 partitions and, booted right up, no problem which led me to investigate this vb meta and AVB which im currently trying to grasp. Oh and yes i figured out how to take a complete flash dump into a .bin file with mtkclient, so I have backup of partitions from this tool by reading partitions section, and also backup by using the read flash option under flash in the tool. It gave me one giant file called user.bin. I researched what bin and img files are and learned we can use 7 zip or any storage compress/decompress software or cd iso software to open bin files, so preceded with 7 zip on user.bin file and was able to extract the partitions in .img format, really cool, so now i have backup in3 styles lol .bin partitions, .img partitions or 1 .bin complete rom dump which when opened with 7 zip gives you the img forms, been fun, but this orange state and security stuff seems a bit tricky to understand, so thats where im at my freind, Let me know you need any help, Good idea about starting with previous phone guide, my thoughts exactly as well when i started gettin my hands dirty lol What a universe in these gadgets, awesome
Click to expand...
Click to collapse
I get handshake error with mtk client on my b140dl, on both windows and relived iso. Would love to have mine unlocked.

{
"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"
}
Hey guys, I am a total noob with android but I have this same model hone and I have a custom OS. I'm not sure what it means outside of:
"my crazy ex gf managed to get spyware on my new phone like the day after she got the cops to take my old one (Jan 12th) and has been ruining what's left of my sad existence"
But google isn't giving me any results for this firmware version or really this model phone at all so if it would help people working on modding it and there is a way I could like dump the data from it somewhere?

jayleemcnabb81 said:
Is there anyway you could post a guide of sorts. Looking to unlock the bootloader and root (aren't we all).
Am relatively new at this. Last phone I rooted before this year was the Epic Touch! Please at least list which downloads are needed. Thanks in advance. *Jaymi*
Click to expand...
Click to collapse
Hi Jaymi, sorry for the late 2 month late response, been totally busy and other places, but yes, i think i will make a guide, to the best of my ability as im relatively new at this as well and have never wrote a guide, but shall give it my best! Any questions, just ask, Rob

Can someone show me how to do this? it appears OP has been offline and nobody ever got around to actually SHARING THIS METHOD OF BOOTLOADER UNLOCK... I used to unlock my phones bootloaders all the time around 2014 but the game has changed and now you gotta edit files on notepad and download github sources it seems...
tl:dr: NEED ISNRUCTIONZ pl0X!!

rtype77 said:
Yeah right on, im goin at orange status removal once again, I did do a little homework, and beleive the inability to flash any custom partition is due to encryption of partitions by dm verity and or AVB preventing boot even if rooted? Not sure exactly but reading and learning. btw my friend, Im Rob, pleasure to meet. I dont know any coding, though ready to learn, just mods a bit, though im relatively new to that as well, but i try being creative, and was stoked I actually pulled off root on this newer phone, unlocked the bootloader with mtk_client, from git-hub, no problem : https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjlsKWdh7b2AhVXjokEHXJ1DD4QFnoECAsQAQ&url=https://github.com/bkerler/mtkclient&usg=AOvVaw1EA0UgBcE8bbeVuiVn4L7c
I then read all partitions to my laptop which dumped in .bin form, from there i looked everywhere for a root on this phone. too new, as i found nothing. That made me think if mtk_gui could pull off unlocking the bl, what else can it do? So read its readme a bit and noticed the magisk root using adb and fastboot, with accompaning custom magisk for mtk. Thought i was probably wasting my time as this phones security is newer. Well, it worked, so bootloader down, root accomplished with magisk, now this orange state, which i tried online hex manipulation of lk.bin file and flashed it to original lk.bin partition on phone, no boot. Tried making a custom logo.bin and same flash, no boot. So used my mtk_client tool to flash my backup abov 2 partitions and, booted right up, no problem which led me to investigate this vb meta and AVB which im currently trying to grasp. Oh and yes i figured out how to take a complete flash dump into a .bin file with mtkclient, so I have backup of partitions from this tool by reading partitions section, and also backup by using the read flash option under flash in the tool. It gave me one giant file called user.bin. I researched what bin and img files are and learned we can use 7 zip or any storage compress/decompress software or cd iso software to open bin files, so preceded with 7 zip on user.bin file and was able to extract the partitions in .img format, really cool, so now i have backup in3 styles lol .bin partitions, .img partitions or 1 .bin complete rom dump which when opened with 7 zip gives you the img forms, been fun, but this orange state and security stuff seems a bit tricky to understand, so thats where im at my freind, Let me know you need any help, Good idea about starting with previous phone guide, my thoughts exactly as well when i started gettin my hands dirty lol What a universe in these gadgets, awesome
Click to expand...
Click to collapse
Hey, I have a B140DL and unlocking it's bootloader has become personal. I have achieved root on other handsets and tablets, but this little bastard is something else. I was just inquiring to see if you ever put together a guide. Any advice is greatly appreciated. I will say for a cheap phone, it has been a Mother-Fuxxer!

iamx51 said:
I get handshake error with mtk client on my b140dl, on both windows and relived iso. Would love to have mine unlocked.
Click to expand...
Click to collapse
I kept getting handshake error also. Then I started getting device not configured. Have you made any headway?

One more thing, out of curiosity I ran the command "fastboot flashing lock" and I got a menu that asked Do you wish to LOCK BOOTLOADER? Locking your BOOTLOADER will wipe your device of all DATA! You must then flash your phone with a stock ROM.

Looking into this device myself and having a hard time. I haven't rooted a phone since a droid x2 and back then i did it with some kind of software through an ubuntu terminal. Not sure what's being used now but has anyone been able to do this or can anyone offer any tips or guidance?

oldt7mer said:
Looking into this device myself and having a hard time. I haven't rooted a phone since a droid x2 and back then i did it with some kind of software through an ubuntu terminal. Not sure what's being used now but has anyone been able to do this or can anyone offer any tips or guidance?
Click to expand...
Click to collapse
MTK Client and Python with Chimera exploit can supposedly do it. Look to GitHub. Hope you enjoy a challenge. I have made little problems.

ive been playing with this all day and its safe to say this is impossible with currently released tech on the latest security updates. the only way youre going to be able to do this is if youre able to force the phone into brom mode. doesnt seem possible from where im standing unless that can be done, would have to be done through a hardware mod.

oldt7mer said:
ive been playing with this all day and its safe to say this is impossible with currently released tech on the latest security updates. the only way youre going to be able to do this is if youre able to force the phone into brom mode. doesnt seem possible from where im standing unless that can be done, would have to be done through a hardware mod.
Click to expand...
Click to collapse
in case i wasnt clear, if you are on 2021 security updates with this phone (i.e. havent updated it or just got it and declined updates) you can easily unlock the phone with mtkclient and root with magisk; however if you've installed the 2022 security updates, brom mode is basically disabled making it impossible to unlock the phone.

oldt7mer said:
ive been playing with this all day and its safe to say this is impossible with currently released tech on the latest security updates. the only way youre going to be able to do this is if youre able to force the phone into brom mode. doesnt seem possible from where im standing unless that can be done, would have to be done through a hardware mod.
Click to expand...
Click to collapse
Run the fastboot command "fastboot flashing lock". Do that and tell me what you think. Trust me. Just be sure to read the prompt on your phone.

oldt7mer said:
in case i wasnt clear, if you are on 2021 security updates with this phone (i.e. havent updated it or just got it and declined updates) you can easily unlock the phone with mtkclient and root with magisk; however if you've installed the 2022 security updates, brom mode is basically disabled making it impossible to unlock the phone.
Click to expand...
Click to collapse
MTK Client has been no go. Lib USB error and NO BACK END error.