Database Info

Trying to root my g-slate

So I got bored with waiting around for someone else to do it, and decided to take a shot at rooting my G-Slate. I figure it's basically the same as the Xoom, so the same sort of process should work....
My initial game plan was this:
Get into Fastboot
Flash a recovery image
Boot the recovery image
Now "adb shell" is a root shell
Copy a "su" binary into /system/bin
Declare victory
That started out pretty well. Powering on and holding down volume-up gets into fastboot. The fastboot binary on my laptop sees the device. Typing "fastboot oem unlock" claims to work. Flashing the Xoom recovery image [1] claims to work.
But... I can't seem to boot to recovery. Running "adb reboot recovery" just reboots normally. Doing "fastboot boot recovery.img" freezes the device. Booting with down-volume gets me to some sort of LG updater state that might as well be freezing the device. Booting with both volume buttons down either 1.) doesn't boot or 2.) brings me to fastboot. That's all the button combinations.
So I guess my question is this: does anyone have any suggestions for how to proceed?
I really don't want to just blind-flash the Xoom boot.img from the unlock thread, because if that doesn't work my device is bricked until someone either makes a working kernel or somehow extracts the current one.
On the up side, my g-slate is *claiming* to have working fastboot that can flash images. It could be totally lying though.
[1] http://forum.xda-developers.com/showthread.php?t=1038870

Tried the same method. No dice. Right now there has been no luck on anyone's part that i know when it comes to rooting. Shoot we havent even been able to get one of the xda mods to create us our own forum for that matter...i had to go out and create my own. I have tried other methods that worked on my nexus one when none other would but alas still no luck.
I imagine since the g-slate is brand new that its not a question of if it can be rooted, but how and when. I'm going to try one more method i know of that worked on the lg optimus tonight. I'll post here if it works.

Soure code seems to be available too
It also appears the source code is available from LG here .lg.com/global/support/opensource/opensource-detail.jsp
I just did a search under mobile phones for the model number 909
Don't know if that will help anyone here.
I have been hunting all over for root access. fastboot says I unlocked the bootloader but nothing seems to want to take.
XDA Mods, please create a G-Slate Section
HA. member since 2006 and my first post just add a www in front of that link

When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command. I have rooted a lot of devices, but never have done anything on an LG device and it is awkward. Vol+ and power gets some form of fastboot. Vol- and power gets download mode, which I am used to from Samsung devices (if we can get an interface like Odin then this becomes a lifesaver and makes the device "virtually" unbrickable). I cannot find any form of recovery. 'Adb reboot recovery' just restarts the device. One interesting this is that pushing both Vol+ and Vol- and power puts the device into what would seem like a bricked device (just use reset button). This same button combination worked on some Samsung devices so something is happening there, but I have not tried enough combos yet to figure it out.
So far as root, well, I have tried z4 (works with nearly all Sammy devices and LG seems to be using a lot of Sammy ideas or at least it looks that way), but to no avail. Gingerbreak apk might work or even the Xoom Root, but the rootboot.img might be different and I have not opened any of that up yet. I did get SU loaded once and in the system, but I could not reproduce it.
I will be working on this some more this weekend (returning the device at some point as it reboots on its own about 5 times a day), and looking into the recovery issue. If anyone has any ideas then please post.
Also, it looks like LG hacked the crap out of the thing to get the SD card to mount and it is weird, so please be aware of that. The SD card mounts every time you plug the device in and there is no way to turn that off. The reason this is important is that some root methods require that the SD card not be mounted, so you will have to unmount the SD card via ADB and with the card being internal I am not too sure it is a good idea, but . . .
I will mark this thread as a favorite and update if I get any where. I know that Cyanogen and Kmobs got G-Slate's recently, so hopefully they can give us a little insight once the device gets to them. I have also contacted LG and @TheLGGirl and asked them to confirm that the bootloader is locked, but have not heard anything back.

Also, the the Acer HC tablet was rooted yesterday using the Gingerbreak root method, and so that is helpful, but it has an SD card (see above).
Sent from my LG-V909 using Tapatalk

I tried the Acer method (GingerBreak) and it does not work. Will look at the logcat in a bit.
Sent from my LG-V909 using Tapatalk

Thanks hourst
I am used to odin (also have a vibrant). Something like that would be a life saver.
Makes sense about the fastboot commands seeming to take.
I was also having reboot issues with mine. I had a handful of reboots each day (about 3 or 4) for the first two days but they have stopped completely now. I have had it for about a week now and have not noticed a reboot since day 2.
I will keep poking around to see if i can come up with anything as well.

Could this help?
Under the impression the G2x root method maybe helpful since they are both LG devices with somewhat similar hardware.
Does anyone know or tried this http://forum.xda-developers.com/showthread.php?t=1056847 to see if it works?
Not sure if I am brave enough yet. But it could be possible the vol up+vol down+power button combo that seems to lock the device is putting it into the mode needed to run the nvflash application.
This really is mostly speculation but could be something to try.

Success
So i got brave.
vol up+vol down+power Device seems to freeze. Plugged in the usb and got a new hardware pop in windows. Listed it as APX device using the drivers in the file listed in my previous link installed successful and the device was found.
That is a far as I went.

im doing the NVFLASH right now... wish me luck and see how far I can go

Any Luck?
Suzannemscott
How did it go? any results or do you have a large brick?

ok i tried. and no luck , i did manage to brick it tho, but i was able to unbrick it phew, back to square one

Did it seem like anything happened? Also what did you do to unbrick it?

To unbrick it i just press the reset button, in the back, quickly hold down Vol+ and Vol- then it goes to a the Gslate screen with the square and then i hold down the reset again and it reboots, maybe i am doin to much but hey it get my Tab back it works!

Gah! Why does it claim to have fastboot when *any* fastboot command except "fastboot devices" just makes it freeze?
I went ahead and built the kernel that LG released and packed it into the clockwork recovery image for the Xoom. Fastboot boot... freeze.
Computer always says this, but I think it's just making fun of me:
downloading 'boot.img'... OKAY
booting... OKAY
I also tried to build and boot a custom kernel with a fb console enabled just to get some feedback, but all it wants to do in response to "fastboot boot" is freeze.
I'm starting to get discouraged here. My 14 day return period ends on Tuesday and I don't really want to get stuck with an unrootable device.

Chandon, would you be able to send me the kernel you built?

I'm sure someone with more expertise and knowledge will be able to root this thing eventually...but right now it seems to be a lot trickier to root than I initially thought. It's not unrootable...just complicated. Over my head by a lot. I don't think I'm going to return it...but I've now resigned to the fact that I may not ever be able to find a working method to root the damn thing myself.

SmellyTunic -
I've uploaded the two kernels I built [1].
They're both built from the v909 kernel source posted by LG[2], following the instructions posted by adrynalyne[3] for building custom android kernels, but I don't have any way to test them aside from the fact that "fastboot boot" doesn't work either straight, with a ramdisk, or with a rebuilt recovery image using the tools in [4].
[1] http://pandion.ferrus.net/gslate/kernels
[2] http://opensource.lge.com
[3] http://forum.xda-developers.com/showthread.php?t=1039854
[4] http://forum.xda-developers.com/showthread.php?t=915808

hourst2 said:
When the fastboot says Ok it is not telling you that you have unlocked the device. It says ok no matter what you put in. Try unlock and it will say ok as well. If it unlocked the device then it would prompt you on your device with a popup that tells you that you are voiding your warranty and have you hit ok. The device is not unlockable using the 'fastboot oem unlock' command.
Click to expand...
Click to collapse
Not entirely true. You said that if you try simply typing in "fastboot unlock", it tells you "OK" as well, right?
Not for me. That only ended up displaying the whole list of fastboot commands.
I agree with you that "fastboot oem unlock" is not unlocking the device though. But what are the alternatives? Everything I've ever rooted has used "oem unlock". I've never even heard of a different command that can be used to unlock a bootloader. I tried a google search and came up with nada.
Hmm...

wich you the best make happen

[guide] blu life xl (model: #l050u) [root / bootloader unlock / faq]

The BLU LIFE XL phone is an unlocked GSM platform device.
Currently there are absolutely no threads on the internet with information related to this device. I am not responsible for any damage done to your device, you assume sole responsibility for whatever you do to your devices. If you have questions, please reply to this or PM me, I'll be glad to help any of you!
================
Things you should know before you do anything listed in this post:
- Bootloader unlocking WILL ERASE USER DATA!!!!
- Successful root attempts disable OTA updates. (Unroot + Factory Reset MIGHT fix this)
- You must have OEM unlocking & USB debugging enabled in the developer menu.
- Common sense, don't flash anything you find on the internet randomly, you will cause irreparable damage, I learned that the hard way.
- Download & install the ADB Universal drivers & Android SDK tools (links @ bottom)
================
If you'd like to make a backup of your stock ROM, you can use romdump, it's a nifty tool that does exactly what it says, and it works on pretty much any rooted android phone. (yay) DL: http://d-h.st/ErS
- Download & extract to root directory of your sdcard.
- Open Root Browser (Or any file browser that's for rooted devices)
- Navigate to the path where you copied/downloaded romdump
- Move romdump to /data/local/
- Long press romdump and check all 3 rows of boxes above and press"OK"
- Open terminal emulator (or any equivalent terminal emulator app)
- Type "export PATH=/data/local/bin:$PATH"
- Type "su"
- Type "chmod 04755 /data/local/romdump"
- Type "/data/local/romdump"
- Wait until the process finishes, do NOT do anything with your device, set it down and leave it.
================
Rooting The Device:
- Have USB debugging, OEM unlocking & unknown sources enabled.
- Download & install the latest version of KingRoot.
- Swipe up three times, press "try it"
NOTICE: If your device restarts through the process, don't worry, your device isn't broken, but there's a good chance the root attempt failed.
================
Unlocking/Locking The Bootloader (THIS WILL ERASE ALL OF YOUR DATA!):
- Power off the BLU LIFE XL
- Hold down POWER + VOL UP until the phone turns on.
- Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
- Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
- Plug your phone into your computer
- Navigate to your android SDK folder, and find fastboot. (If you don't have the android SDK downloaded, refer below)
- Type fastboot devices and see if your android device is recognized.
- Type "fastboot oem unlock"
- A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
Alternatively, if you wish to re-lock your bootloader, follow these steps above, however type "fastboot oem lock" instead of "fastboot oem unlock"
================
FACTORY MODE & DEVICE TESTING MENUS:
- Power off BLU LIFE XL
- Press POWER & hold VOL DOWN until the phone turns on.
- Release grip of power button, whilst holding VOL DOWN.
================
Downloads:
Android SDK: https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
ADB Universal Drivers: http://www.mediafire.com/download/uo3t409a9vz3kh3/adbdriver_v1.0.zip
KingRoot: https://androidmtk.com/download-kingroot-application
Romdump: http://d-h.st/ErS

My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?

redkvothe said:
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
Click to expand...
Click to collapse
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
By the way, I also replied to your comment on reddit.

TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse

blkkalel said:
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
The ROM I have dumped has personal applications and accounts integrated, I will get around to dumping a clean ROM for you guys soon.
Papa bless
Click to expand...
Click to collapse

BLU Life XL needs all that the mainstream devices have.
Thank you for the info above. It's such a shame this device has such limited info online. I'm not really a Noob, but also not close to a developer. How does one go about creating a custom recovery and a sweet ROM? Do you think you tube might have a how to that is on point or is there a spot here that we as users could request pros to check on it?

BLUE LIFE XL (L050U) has anyone else been successful using this root kit?
@do_root / TheDarknessz0rz, hey just wondering if the BLUE LIFE XL (L050U) you designed this tutorial for had a specific build that is needed to do this without bricking (like markressler/redkvothe whotf-ever did with his device)? In other words what was the build# of the L050U you designed this root process around? Just wondering man so I can get this done without any worries. I shouldn't have any issues using your root process on my BLU LIFE XL (L050u) Build: ALPS.L1.MP6.V2.15.2_6592.WET_P37 Custom Build version: BLU_L050U_V12_GENERIC, right? I've rooted every android device I've owned back to the original Droid1 without ever bricking during the flashing process. Just wondered if there might be a specific reason this other dude bricked his device.
Thanks in advance for even making a root kit for this device. Would appreciate any advice you have here.
-jim :fingers-crossed:
Edit: I'm ready to do this - just wanted to hear your feedback before I give it a rip.

@heatgap, I also have a L050U device. Where you able to unlock bootloader and root your BLU LIFE XL using the procedure desribed above? BTW, Thank you @TheDarknessz0rz
I am new at rooting, etc... Any additional steps you had to do? Or any advice you might give a rookie/noob to be able to get this done?
Many thanks!
Sisafokker

MOSTLY Stock images / Seeking assistance with recovery
Okay, I've dumped all of the raw images.
Most of them are stock, with the exception of system.img and recovery.img
recovery: insecure ADB, which really does no good until I can put together a custom recovery, or at least get a shell.
system: pre-rooted with SuperSU. Also, will NOT reflash recovery to stock on reboot.
Coming from stock, after you've backed up your user data (because it will be wiped), boot into fastboot mode.
Issue a "fastboot oem unlock-go" to unlock the bootloader. (This only has to be done once.) THIS WIPES EVERYTHING!
Then "fastboot flash system system.img" (This takes a while.)
After first boot and setup, download SuperSU from play store, install and update.
I'm working on putting together a working custom recovery, but I'm not an expert at this.

Succeded!!! Rooted device!
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker

This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance

br21763 said:
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
Click to expand...
Click to collapse
I do not have any stock images, the images i have are for my device specifically, i'd have to rid the image of custom files first.

Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again

br21763 said:
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
Click to expand...
Click to collapse
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.

sisafokker said:
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
Click to expand...
Click to collapse
My device always returns status locked when I tell fastboot to dump the variables. I'm not sure why, bootloader unlock process says it's successful, however when it comes time to press VOL_UP to finish the process, none of the hardware keys are recognized, I've even issued fastboot continue from command prompt, yet the bootloader refuses to unlock. I'm going to try once more with "fastboot oem unlock-go" and see what happens from there.

TheDarknessz0rz said:
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
Click to expand...
Click to collapse
Don't mean to sound so clueless but how would I go about doing that? I mean I couldn't find any firmware anywhere, even for other models so could you help me with that part? Also would I be flashing it from the "apply update from sd card" option on the stock recovery?
Thanks a lot

Never mind, I was able to figure out how to flash the system.img file onto my phone. Now it seems to be working perfectly. Thank you very much for all of the help and for uploading the img files, i really appreciate it.
Have a nice day

blu-life-xl Hard brick No problem !!!!!
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site

BLU download site
samgr said:
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
Click to expand...
Click to collapse
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file

hard brick NO! problem
Rickrocks013 said:
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
Click to expand...
Click to collapse
try it it works!!!!!!!!!!!!!!!!!!!:laugh:

I cant unlock bootloader!

I have nexus 5 and its bricked, But I cant unlock the bootloader using fastboot ( I think its because I have no rom ). Is there an another way to unlock the bootloader?

The fastboot oem unblock solution is the only way to unlock the bootloader without root.
If you can't do it then you may have hardware issues.

The phone is recognized when you run the command "fastboot devices"? If not, you'll need to get it recognized before issuing fastboot commands to the phone.

If you have no ROM, and the bootloader is locked, you've gotten yourself into quite the predicament. What error does fastboot oem unlock give you?
Sent from my Nexus 5X using Tapatalk

drsn0w said:
If you have no ROM, and the bootloader is locked, you've gotten yourself into quite the predicament. What error does fastboot oem unlock give you?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I get the devices to oem unlock, but when i try and flash a bootloader.img I get this
Owners-iMac:image-hammerhead-mob31e EmilyHaugen$ ./fastboot flash bootloader /Users/owner/Desktop/android/hammerhead-mob31e/bootloader-hammerhead-hhz20h.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.488s

Strange
Sent from my Nexus 5X using Tapatalk

After unlocking the bootloader, reboot the phone into fastboot and see if the bootloader is still unlocked.
Try relocking the bootloader and then unlock it. If the phone performs a factory wipe in a few seconds, the emmc chip may be damaged.

Primokorn said:
The fastboot oem unblock solution is the only way to unlock the bootloader without root.
If you can't do it then you may have hardware issues.
Click to expand...
Click to collapse
I think that has a root.
My friend rooted it and than remove kingroot (without unroot).
What the way to unlock bootloader with root?
Thenx

matan10 said:
I think that has a root.
My friend rooted it and than remove kingroot (without unroot).
What the way to unlock bootloader with root?
Thenx
Click to expand...
Click to collapse
BootUnlocker app

Primokorn said:
BootUnlocker app
Click to expand...
Click to collapse
But I have no rom. And I cant install rom because my bootloader is locked

matan10 said:
But I have no rom. And I cant install rom because my bootloader is locked
Click to expand...
Click to collapse
I know but you asked. No other solution mate except going to a repair shop.

Hello,
First some background and credits:
There are a few ways to brick a phone. Sometimes it's lack of experience, sometimes it's an accidental thing, sometimes there just isn't an explanation for what went wrong... (share your experience here, if you wish). For me, I owned my OPO for about 4 hours before things went wrong. First thing I did was I rooted it and installed TWRP. After creating a nandroid backup of the stock image I installed my favorite custom ROM and restored all my apps with TiBu. Everything was great and configured just the way I wanted it. I then wiped my old phone (Nexus 4), installed a new ROM and got it all ready for my wife. She was so excited to get rid of her GNex and move up to the N4. But then, for whatever reason, I opened an app on my OPO that I used to manage, download, and install kernels with. It came up with "there is a new kernel update!" and I instinctively clicked on "Install". 10 seconds later my phone was bricked. Nothing came on the screen, no fastboot, no recovery, nothing to boot to, no way to send data to and from it. The second the screen went black and the phone became lifeless I got that wretched feeling in my gut as I realized I just flashed a N4 kernel on my new OPO. Restoring the kernel management app with TiBu made it act like it's still running on my old phone, and in my excitement I didn't take a second to think things through...
I received a bit of consolation when a quick XDA search revealed that I am not the only dumbass to brick his phone this very way. I joined forces with some pretty smart and desperate people and tried different things, all described in the following thread: http://forum.xda-developers.com/oneplus-one/help/wrong-kernel-black-screen-fastboot-adb-t2835696. Unfortunately it took us what seemed like many long weeks to figure it all out. Well, in the end a solution was found and I documented it in the the following post: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136.
This was a few months ago, but I recently noticed many people continue to search for these directions and have problems finding them hidden among many pages and other threads, so I've decided to put this stand alone thread with these, now updated, directions.
Let me get one more thing straight, for the record. I did not find the way to unbrick the OPO. In fact I wasn't even the very first one to do it. It was a collective effort of few people who tried many different approaches and ideas, and I eventually documented these steps for others to follow. Being said, the following people deserve credit as well: @os_man, @rezor92, @Mnt-XDA. If I am forgetting other significant names and efforts, I apologize.
***CAUTION***
The following instructions are for hardware bricked devices ONLY and will not work on soft bricked devices. To determine whether your device is soft or hard bricked, click the button below:
Hardware brick
A hardware bricked OPO has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition. The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OPO should be detected as QHSUSB_BULK USB. You might have a bricked OPO as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition.
Software brick
Please do not attempt to use these directions if your phone is soft bricked. A software bricked OPO is one that might be stuck in a bootloop, but has a working bootloader, recovery partition, fastboot, or adb. If you press the power button and images appear on the screen and you are able to enter fastboot mode (Power + VolUP) or recovery (Power + VolDOWN) then your device is soft bricked. This thread does not encompass soft brick recovery, the instructions below do not apply and will not work on these phones. Consult other threads for help on soft bricked devices.
If based on the above explanation of differences between soft and hard bricks you determined your device is hard bricked, here's what you will need to do...
1:
Download Color.zip from https://goo.gl/iDby26
After downloading, unzip the archive on your computer.
2:
Next, you need proper Windows drivers. There are architectural differences between Windows XP and Windows 7/8, so follow the directions below that pertain to you. One quick note about the drivers: the installation and process is very simple and straightforward on Windows XP (I also tested successfully on Windows 2003), but proves to be quite a challenge when running on Windows 7 or 8. Over and over people report issues when attempting the unbrick procedure on Windows 7/8, some have more luck than others. Being said, if you have access to a Windows XP computer, I highly recommend that you use that. If you have no choice but to use a Windows 7 or 8 computer and have problems, please share them here and read others' experiences.
So first, by now you probably tried a few different things to fix your phone and you've already installed some drivers, including Qualcomm USB drivers for 9006 and 9008. My best advice is to uninstall the drivers you tried so far and use the ones listed below. Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted. Then:
2a:
Windows XP users:
You are in luck, driver installation is straightforward. Go to the extracted Color.zip folder and find Driver.iso. Extract Driver.iso. Inside the extracted folder find Setup.exe. Run Setup.exe to install the drivers. The installer is Chinese, but all you need to do is click through the prompts.
2b:
Windows 7 and Windows 8:
These operating systems block unsigned driver installations by default. Follow these steps (thanks @nag4pl for testing these):
Download and extract these Qualcomm 2012 drivers: https://goo.gl/cIKnFZ. Connect your bricked phone and let Windows do its thing.
Now something very essential you need to do here is to execute two commands to allow you to install unsigned drivers for QHUSB_BULK. Click on Start Menu > Type cmd.exe > Right Click and Run as Administrator.
In the CMD window type in the following commands (hit enter after each):
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Code:
bcdedit.exe -set TESTSIGNING ON
After both the commands should run successfully, restart your computer.
You can now proceed to install unsigned drivers from the file you downloaded. Open Device Manager, you should be seeing ugly yellow warning under other devices for QHUSB_BULK. Right click on the name and select Update Driver Software > Browse my Computer for driver software. For driver software location provide the path where you have extracted Qualcomm 2012 drivers you downloaded and make sure 'Include Subfolders' is checked. Proceed through all the installation prompts ignoring any warnings.
3:
Once you have the drivers straightened out, connect your bricked phone to the computer and start it up by holding VolUp + Power to about 10 seconds, and let the computer do its thing. Don't install drivers if they are not installed by itself. Instead launch Msm8974DownloadTool.exe as Administrator (right click on Msm8974DownloadTool.exe and select "Run as administrator") from the extracted Color.zip archive. It will scan all the COM ports and find the phone. That's the one line that looks different in the list. The list is just a list of your com ports and devices. If you unplug the phone and move it to another port, it will show your bricked phone on a different line.
Clicking on "Enum" just rescans the busses. Clicking the big square button in upper right corner scans the phone and reports what's good and what's not. It takes a minute for the scan to finish.
If you don't see your phone in the list of com devices, try unplugging/plugging in your phone a couple times, and rebooting it with VolUP + Power (hold 10 seconds). You will see it in Device Manager as well.
Once you see the phone in the list, click Start. You should see the programs start writing different files to the phone. Each time it writes a file you'll see a progress bar. Once you see this process happening, smile, you know you will be good to go... After all files are written, the com line with your device will turn green. You're good, unplug and reboot your phone. It will boot to ColorOS, the Chinese OS that comes on OPO.
4:
Optional Steps:
Your phone is no longer bricked. You now have a few options to get back to stock. The easiest way is to use a toolkit from http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418, or you can flash an image manually by following directions from: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541. Download the proper image zip and after extracting it, run the following commands in fastboot mode:
Code:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue.
Good luck! Share your experience here and let me know if I can improve this thread.
Please click the Thanks button if you found the above guide useful.
Click to expand...
Click to collapse
I saw this guide but its for one plus one.
Its any way to do this guide for nexus 5?

http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732/page40
This is the link

Can you boot into fastboot mode? If you can, connect the phone, run the fast boot command "fastboot oem unlock".

audit13 said:
Can you boot into fastboot mode? If you can, connect the phone, run the fast boot command "fastboot oem unlock".
Click to expand...
Click to collapse
I ran this command but it still locked. I think because its need to reboot after run the unlock command, but I cant reboot because I have no rom.

After you type "fastboot oem unlock", you should get a prompt on the phone to say "yes".

audit13 said:
After you type "fastboot oem unlock", you should get a prompt on the phone to say "yes".
Click to expand...
Click to collapse
Right. I did it and its looks like its unlocked, but after reboot to bootloader it was back seems locked.

If the bootloader relocks itself on reboot, the Emmc chip is damaged and needs to be replaced.

audit13 said:
If the bootloader relocks itself on reboot, the Emmc chip is damaged and needs to be replaced.
Click to expand...
Click to collapse
How much does a repair for switch emmc chip?
If I buy this chip, can I switch it alone?

It's the memory chip on the motherboard that needs to be replaced. Unless you have specialized soldering equipment, the best solution would be to find a nexus 5 with a smashed screen and working internal components.

OP7 Pro Fastboot Bootloop! [HELP]

This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated

https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.

MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be

MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?

Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.

I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this

Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.

Can't you just switch slots from fastboot or did you mess up both?

trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/

IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)

larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping

From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop

larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!

Now install the zip twrp

Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!

Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.

unlocking bootloader for realme 6i rmx 2040

hi , since there is no "recovery,root, roms..etc" posts for our device rm 6i rmx 2040 or any developer that work for our device i searched google for at least how to unlock bootloader but o result , i found a site explain how to unlock bl for realme 5i so i said lets try this it might work and it did some telegram groups make it if you pay them money to unlock it so i want to share it with you " i believe it might work with any realme device , enough talk here's the method :
1- first you should backup your data bc all your data will be erased once you unlock your bl
2- install ADB & Fastboot Drivers from this thread https://forum.xda-developers.com/showthread.php?t=2588979
3- download "in depth test" apk and install it "search google for the app
4- open the app and press on start applying, then check the box below then choose submit application
5-after finishing it will show you submitted
6- after one or two hours open the app it will show you review successful
7-You can now click “Start the in-depth test” and the device will reboot automatically and you will see the following on your screen : fast boot_unlock_verify ok
8-now connect your phone via usb cable to pc and open cmd and enter these commands :
- Enter the command: adb reboot bootloader
- Press “Enter”on your keyboard
- Enter the command: fastboot flashing unlock
*if this command not work as it happened with me replace fastboot flashing unlock with "adb flashing unlock" and it should work*
- Press “Enter”on your keyboard
9- On your phone press the Volume Up key to select “Unlock” (or press the Volume Down key if you have changed your mind to select “Do not unlock bootloader”).
press volume up and you are done then reboot your phone to system. ] :fingers-crossed:
for more instructions with pics visit https://c.realme.com/in/post-details/1110804709561597952
we can root the device too but i need boot.img so if anyone have it or a link to it please share it here hope this help and in the future i hope someone work on our device and provide the development our device deserve
Screenshot shows that my bootloader is unlocked already

Yo bro, the "in-depth test" apk doesn't work for me. I tried installing the apk but the phone kept prompting "App not installed"
any solutions for this? thanks man
Edit:
Tried it without the "in-depth test" APK, phone showed me:
The serial is not match
fastboot_unlock_verify fail
not much progress here. APK still doesn't work :'(

rooting for rmx2040?

Joesh.lucas said:
Yo bro, the "in-depth test" apk doesn't work for me. I tried installing the apk but the phone kept prompting "App not installed"
any solutions for this? thanks man
Edit:
Tried it without the "in-depth test" APK, phone showed me:
The serial is not match
fastboot_unlock_verify fail
not much progress here. APK still doesn't work :'(
Click to expand...
Click to collapse
For me also when I install it its says app not installed
What I do now

Joesh.lucas said:
Yo bro, the "in-depth test" apk doesn't work for me. I tried installing the apk but the phone kept prompting "App not installed"
any solutions for this? thanks man
Edit:
Tried it without the "in-depth test" APK, phone showed me:
The serial is not match
fastboot_unlock_verify fail
not much progress here. APK still doesn't work :'(
Click to expand...
Click to collapse
It worked fine for me bro maybe the package you downloaded not suitable for your device try another apk from a different site , and if you follow the instructions you'll succeed and I'll try to upload the apk i used
Here apk link
https://mega.nz/file/xshHHC4Q#kJINQ--_bSSBS8CxohNqB9iIHUldz-FpQSJOZb3ehQE

chickentikka007 said:
For me also when I install it its says app not installed
What I do now
Click to expand...
Click to collapse
Try another site to download the apk from , maybe apk you downloaded not suitable, I'll try to upload the apk i used
Here's the link it's installed successfuly
https://mega.nz/file/xshHHC4Q#kJINQ--_bSSBS8CxohNqB9iIHUldz-FpQSJOZb3ehQE

lilsaint05 said:
rooting for rmx2040?
Click to expand...
Click to collapse
We need boot.img to root , it exist in the firmware files , didn't find a proper site so if anyone find firmware for our device it's easy to root then

Kraitos said:
It worked fine for me bro maybe the package you downloaded not suitable for your device try another apk from a different site , and if you follow the instructions you'll succeed and I'll try to upload the apk i used
Here apk link
https://mega.nz/file/xshHHC4Q#kJINQ--_bSSBS8CxohNqB9iIHUldz-FpQSJOZb3ehQE
Click to expand...
Click to collapse
It finally worked bro, here's a screenshot sample.
https://ibb.co/GkvgNyV
Thank you so much! I guess now I'll just have to wait.
You might want to attach the file in the main post though, so other peeps can see it.
Anyway, thank you!
---------- Post added at 05:01 AM ---------- Previous post was at 04:53 AM ----------
Kraitos said:
hi , since there is no "recovery,root, roms..etc" posts for our device rm 6i rmx 2040 or any developer that work for our device i searched google for at least how to unlock bootloader but o result , i found a site explain how to unlock bl for realme 5i so i said lets try this it might work and it did some telegram groups make it if you pay them money to unlock it so i want to share it with you " i believe it might work with any realme device , enough talk here's the method :
1- first you should backup your data bc all your data will be erased once you unlock your bl
2- install ADB & Fastboot Drivers from this thread https://forum.xda-developers.com/showthread.php?t=2588979
3- download "in depth test" apk and install it "search google for the app
4- open the app and press on start applying, then check the box below then choose submit application
5-after finishing it will show you submitted
6- after one or two hours open the app it will show you review successful
7-You can now click “Start the in-depth test” and the device will reboot automatically and you will see the following on your screen : fast boot_unlock_verify ok
8-now connect your phone via usb cable to pc and open cmd and enter these commands :
- Enter the command: adb reboot bootloader
- Press “Enter”on your keyboard
- Enter the command: fastboot flashing unlock
*if this command not work as it happened with me replace fastboot flashing unlock with "adb flashing unlock" and it should work*
- Press “Enter”on your keyboard
9- On your phone press the Volume Up key to select “Unlock” (or press the Volume Down key if you have changed your mind to select “Do not unlock bootloader”).
press volume up and you are done then reboot your phone to system. ] :fingers-crossed:
for more instructions with pics visit https://c.realme.com/in/post-details/1110804709561597952
we can root the device too but i need boot.img so if anyone have it or a link to it please share it here hope this help and in the future i hope someone work on our device and provide the development our device deserve
Screenshot shows that my bootloader is unlocked already
Click to expand...
Click to collapse
Thanks again for providing the apk file.
I don't know much about rooting or anything but, can't we just download the apk for magisk and see if it works or not? or does it still need a custom recovery like Twrp?

Sup bro, I tried it and it was successful this time.
I was able to unlock the bootloader but everything froze on FASTBOOT mode. Here's a sample picture:
https://imgur.com/a/foLdA8C
I don't know why it did, but I kept trying and it eventually unlocked itself.
I did what you said, but in the frozen FASTBOOT mode I just left it there for 30 minutes and manually shutdown the phone (by holding power button).
When the phone was turned on, it showed this under the logo when it booted up:
"Orange State
Your device has been unlocked and can’t be trusted..Your device will boot in 5 seconds"
It didn't reboot though. I waited and eventually I reached the setup portion in the phone. I checked if the bootloader was unlocked in developer mode and to my surprise, it was.
Idk what the "orange state" was for though. Every time I restart the phone, it still shows.
I got bothered and re-locked the phone xD
Now I'm unlocking it again to see if the "Orange state" text will disappear.
as for the boot.img, can't we use the one on the official site? They post update files there, right? Can't we just open those and look if we'll get something from it?
Edit:
I'm so dumb, I could've just typed: "fastboot reboot" and it would've been a lot easier.
It's all good, tried it again and I found out that the "orange state" was normal.
(For those who want to unlock their bootloaders, go read the instructions FROM YOUR PHONE carefully. It was "press Volume down" on mine. I kept pressing volume up and it would do nothin'! And when you're done, go and type "fastboot reboot" on cmd. You don't have to hold the power button if you're gonna manually restart the phone.)
(PS. It still freezes on fastboot mode)

Kraitos said:
We need boot.img to root , it exist in the firmware files , didn't find a proper site so if anyone find firmware for our device it's easy to root then
Click to expand...
Click to collapse
@Kraitos are these what you're looking for?
found this in the ozip file of Rmx2040 Ver. A.27. Everything came from stock.
vbmeta.img:
https://drive.google.com/file/d/1IkI0I19tPcBbOVmco4F7fOwQzxSMNdpi/view?usp=sharing
boot.img:
https://drive.google.com/file/d/1esqocG-BVfw6MqWlCHKVg15q9L3HHJxo/view?usp=sharing

Joesh.lucas said:
It finally worked bro, here's a screenshot sample.
https://ibb.co/GkvgNyV
Thank you so much! I guess now I'll just have to wait.
You might want to attach the file in the main post though, so other peeps can see it.
Anyway, thank you!
---------- Post added at 05:01 AM ---------- Previous post was at 04:53 AM ----------
Thanks again for providing the apk file.
I don't know much about rooting or anything but, can't we just download the apk for magisk and see if it works or not? or does it still need a custom recovery like Twrp?
Click to expand...
Click to collapse
Thanks for your feedback bro , and I will attach apk in attachments
Second I don't have a pc right now but you don't need custom recovery to root , the method is simple , download magisk and install it normally , it will show you magisk not installed in the app so you click on it and choose patch image , then choose the boot.img you provided from internal storage , after finished the patched img will appear in internal storage "in magisk directory I'm not sure" then you take that patched img and flash it via adb "I don't remember the method now but I'll find it if you interested in testing it " then you're rooted

Joesh.lucas said:
Sup bro, I tried it and it was successful this time.
I was able to unlock the bootloader but everything froze on FASTBOOT mode. Here's a sample picture:
https://imgur.com/a/foLdA8C
I don't know why it did, but I kept trying and it eventually unlocked itself.
I did what you said, but in the frozen FASTBOOT mode I just left it there for 30 minutes and manually shutdown the phone (by holding power button).
When the phone was turned on, it showed this under the logo when it booted up:
"Orange State
Your device has been unlocked and can’t be trusted..Your device will boot in 5 seconds"
It didn't reboot though. I waited and eventually I reached the setup portion in the phone. I checked if the bootloader was unlocked in developer mode and to my surprise, it was.
Idk what the "orange state" was for though. Every time I restart the phone, it still shows.
I got bothered and re-locked the phone xD
Now I'm unlocking it again to see if the "Orange state" text will disappear.
as for the boot.img, can't we use the one on the official site? They post update files there, right? Can't we just open those and look if we'll get something from it?
Edit:
I'm so dumb, I could've just typed: "fastboot reboot" and it would've been a lot easier.
It's all good, tried it again and I found out that the "orange state" was normal.
(For those who want to unlock their bootloaders, go read the instructions FROM YOUR PHONE carefully. It was "press Volume down" on mine. I kept pressing volume up and it would do nothin'! And when you're done, go and type "fastboot reboot" on cmd. You don't have to hold the power button if you're gonna manually restart the phone.)
(PS. It still freezes on fastboot mode)
Click to expand...
Click to collapse
I think to exit fastboot you long press on power button

Kraitos said:
I think to exit fastboot you long press on power button
Click to expand...
Click to collapse
Yo dude, i tried rooting it. Had too many bugs though
I made a thread here, look:
https://forum.xda-developers.com/realme-6i/how-to/tried-rooting-rmx2040-t4182639
Next I'll try to root A.27.
I'll downgrade to A.27 (Currently at 31) and get the boot.img there and patch it. I'll leave a reply here if it works (or i'll just update the thread).

Joesh.lucas said:
Yo dude, i tried rooting it. Had too many bugs though
I made a thread here, look:
https://forum.xda-developers.com/realme-6i/how-to/tried-rooting-rmx2040-t4182639
Next I'll try to root A.27.
I'll downgrade to A.27 (Currently at 31) and get the boot.img there and patch it. I'll leave a reply here if it works (or i'll just update the thread).
Click to expand...
Click to collapse
Ok bro good luck with testing make sure to prepare for flashing stock if any sh!t happened:fingers-crossed: and use latest boot.img from latest firmware, I'll follow your thread and anything new let us know

Official tutorial for Android 10 is released at https://c.realme.com/in/post-details/1365229261799157760

Will it work on Android 11? Software version C.14?