Related
For some reason my Nexus S will no longer go into recovery mode ... it only restarts the fastboot mode when selected. I'd like to get as fresh a start as I can here, but can't figure out how to get back into recovery mode to get a new image loaded.
I've got the stock-GRH78.zip which seems like the right place to start, but can't figure out how to reload it.
Thanks!
Moved to general
thanks for the move ... hopefully someone will be able to help!
If the bootloader just reloads itself whenever you try to go into recovery, that means that the phone doesn't detect a recovery image. Check the top of your devices as well. In red colors, it should say something about not finding a recovery.
We don't have a true copy of the stock recovery, so you are going to have to use Clockwork Recovery in order to move forward from here. Google has not released the recovery files/rescue .zip so you're going to have to unlock the bootloader/root to fix this. Once you've flashed that on, then you can do a NAND restore of the stock 2.3.1 image linked in the stickied FAQ or in the development section.
EDIT: Just realized AllGamer made a way better step by step guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
unremarked said:
If the bootloader just reloads itself whenever you try to go into recovery, that means that the phone doesn't detect a recovery image. Check the top of your devices as well. In red colors, it should say something about not finding a recovery.
We don't have a true copy of the stock recovery, so you are going to have to use Clockwork Recovery in order to move forward from here. Google has not released the recovery files/rescue .zip so you're going to have to unlock the bootloader/root to fix this. Once you've flashed that on, then you can do a NAND restore of the stock 2.3.1 image linked in the stickied FAQ or in the development section.
EDIT: Just realized AllGamer made a way better step by step guide stickied at the top of this forum: http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
will run through this ... thanks. I don't see any mention of not finding a recovery image. Red just says Fastboot Mode and that my lock state is unlocked.
still struggling along here ... in fastboot mode, I can't connect to my device to run commands so fastboot seems pretty impossible. I can connect when the phone is more fully booted, but you can't run (or I can't anyway) the fastboot commands ...
atmasphere said:
still struggling along here ... in fastboot mode, I can't connect to my device to run commands so fastboot seems pretty impossible. I can connect when the phone is more fully booted, but you can't run (or I can't anyway) the fastboot commands ...
Click to expand...
Click to collapse
You need to install the drivers for fastboot to recognize the phone. Should be detailed in the link I gave you. If not, try the method below. It's what I used. not entirely sure if it will work for you, however.
http://forum.xda-developers.com/showthread.php?t=878786&highlight=pdanet
I'm on a Mac ... No drivers required as I can tell. It worked pre-root.
atmasphere said:
I'm on a Mac ... No drivers required as I can tell. It worked pre-root.
Click to expand...
Click to collapse
Eh, sorry, don't think I can suggest anything else. :/
What worked pre-root? ADB or Fastboot? They're different. Nothing happens when you type in "fastboot devices?" If fastboot doesn't work, I'm pretty sure you're toast. :/
Both commands work but not once I am booted in fastboot mode. Then I lose my connection from the desktop ...
... once rebooted, I am still unable to do anything from fastboot mode. ./adb devices shows nothing listed. added the cable once there, rather than with it connected to switch over. sigh.
atmasphere said:
Both commands work but not once I am booted in fastboot mode. Then I lose my connection from the desktop ...
Click to expand...
Click to collapse
I often don't get a connection on the Mac unless I unplug it from USB and re-plug it in after I've entered fastboot.
Yeah thanks I have tried that multiple times as well as used multiple ports and a USB hub. Maybe rebooting my Mac a few times will do something
unremarked said:
Eh, sorry, don't think I can suggest anything else. :/
What worked pre-root? ADB or Fastboot? They're different. Nothing happens when you type in "fastboot devices?" If fastboot doesn't work, I'm pretty sure you're toast. :/
Click to expand...
Click to collapse
when I do ./fastboot-mac devices I can actually see something ... that's got to be good! adb shows nothing in fastboot mode.
resolved ...
courtesy of my waking up and of course the guidance here, I was able to sort this out by flashing over a recovery image via fastboot. I then used the GRH78 Nandroid backup to get my S back in order. whew!
thanks everyone!
atmasphere said:
when I do ./fastboot-mac devices I can actually see something ... that's got to be good! adb shows nothing in fastboot mode.
Click to expand...
Click to collapse
that is correct, ADB is more for when you are already BOOTed up on the phone
fastboot / fastboot-mac is for when you are in the BOOTloader screen
Just a suggestion, since you have a MAC
it'll be best if you set up a VMware WinXP machine set aside with USB enabled
you'll come across a lot of GUIDEs, HOWTOs and other references written for PC users.
LOL just saying that reminded me of the MAC & PC commercials
AllGamer said:
Just a suggestion, since you have a MAC
it'll be best if you set up a VMware WinXP machine set aside with USB enabled
you'll come across a lot of GUIDEs, HOWTOs and other references written for PC users.
Click to expand...
Click to collapse
Kind of ironic that a linux/unix based phone doesn't have the best support for it on unix based computers like the Mac.
At least fastboot plays nicely with Androids on the Mac. The Galaxy S phones I've had forced me to find an old windows laptop to be able to use Odin.
i just installed pacman rom using clockworkmod recovery something..
fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.
Jack_R1 said:
fastboot flash boot boot.img.
Google the damn thing, instead of spamming threads in all the forums.
Click to expand...
Click to collapse
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!
jigi1993 said:
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!
Click to expand...
Click to collapse
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error
Jack_R1 said:
fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.
Click to expand...
Click to collapse
jigi1993 said:
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error
Click to expand...
Click to collapse
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.
SimonTS said:
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.
Click to expand...
Click to collapse
Sir m damn serious..
i hve been googling in around 4 hrs now..
i did my best but i cant now..
please provide an easy solution..
the boot image error comes in..
i cant extract that file .
Here you go
SimonTS said:
Here you go
Click to expand...
Click to collapse
kk.
So you've installed ADB then?
SimonTS said:
So you've installed ADB then?
Click to expand...
Click to collapse
i downloaded pacman rom.
copied it into root of sd.
wiped data and installed it through clockmod recovery .!
it was installed properly but after reboot it stuck on htc white screen..
:banghead:
teadrinker said:
:banghead:
Click to expand...
Click to collapse
I couldn't agree more - I give up on this guy, if he can't even deal with what I asked then there is no hope for him.
Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege
jugg1es said:
Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege
Click to expand...
Click to collapse
Because we are too nice...
@op cd ( http://en.wikipedia.org/wiki/Cd_(command) ) in the directory where your fastboot and adb in located ( path-to/platform-tools) and fastboot commands should be working.
Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app
Jedioscuro said:
Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby
jugg1es said:
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
Click to expand...
Click to collapse
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?
SimonTS said:
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?
Click to expand...
Click to collapse
Yeah, you're right. But from the disperation of the guy It seemed to me pointless to leave him with a non-functioning phone without any advise. After all this is a forum plenty of people that know how to do practically everything with an android device, but I don't think that everyone have started from a solid programming base or a perfect hardware knowledge.
Regarding me, I have looked into this forum a couple of months BEFORE even try to unlock my phone and flashing something other than the horrible desire's gingerbread stock rom, but I understand the people who wants to try something new, even if they are not so expert.
For the next time, don't worry I'll be mercyless
I'm always ready to help where i can but. It seems like the op followed half a guide then just assumed it would work, i must of read all the guides until my head hurt, and most of my first posts were silly questions already posted. I learnt far more about my phone from searching than i think i could have from my first posts
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby
He would have avoided all the pain if he used the boot img flashing software
Sent from my Desire S using xda premium
I have found an easier to follow way to root the version 5.0 security update, it follows basic logic for rooting with twrp and magisk after the bootloader is unlocked with the boot.img I patched based off of the most recent security update with the help of @tarkus1000
Reboot to the fastboot interface "adb reboot bootloader" or see my youtube video for the keystroke on the unit itself (useful if you break somthing, it happens)
flash the patched boot.img **see link bellow** now you must reboot to system and select the option in settings "allow oem unlocking"
reboot to fastboot using whichever method suits you, just remember this is an old boot-loader so be patient with it as always
1) enter the command "fastboot oem unlock" sometimes it reboots and you know you have success sometimes it says failed... but it is usually unlocked (The more I study this the more I think its a problem with the android 5.1 dalvik heap its interpreter sometimes skips lines of code)
reboot from the fastboot state is required for unlocking so you have to enter the command "fastboot reboot" even if you get the failed command then wait for about 30 seconds for the device to respond if it does not respond reboot using the power button
2) check for the orange state of the bootloader enter command "fastboot getvar all" if you have orange continue to flash the hacked recovery
3)if boot state is green flash the new boot.img again and repeat step 1, remember to be patient and use commands like "fastboot devices"..ect we are working with android lollipop after all
The bootloader is unlocked and you can flash twrp with "fastboot flash recovery (drag and drop .img here)"
Now we enter the hacky recovery by either going to system and "adb reboot recovery" or with fastboot via "fastboot boot (drag and drop .img here)"
Its a little difficult to have the recovery recognize your mouse I had luck with the logitech M100 doing this;
after you hear the device disconnect from your computer (chirp or whatever) plug in the mouse so the device boots up getting input from the mouse
Twrp will tell you it needs a password (will never be able to decrypt your partition no matter what you tell it ) hit cancel and navigate to the backup tile make a backup and include the recovery.img in your nandroid backup
now to root
flash dissable dm-verity/force encrypt (find on xda)
flash magisk (find on xda)
reboot to system. you may have to download magisk manager app to detect magisk and finish the installation
When you have success remember to reboot back to recovery and make a backup before you make any changes to the system or were gonna have to work something out
how to boot into fastboot manually https://youtu.be/766TR5hFEqs
patched v5.0 boot.img [url]https://drive.google.com/open?id=1KDpLxhYBa2Nto9dTaHFOqEKCfs6B1RjV[/URL]
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
awesome!
alecthenice said:
@amg314 pointed out to me that the most direct way to do this is through adb since any failure could be catastrophic... In the past we used a recovery that almost worked for Moverio Bt300s, I will link it bellow for academic purposes; anyways (fastboot under some situations requires something special...I really wanna know, I think I got it once by holding power and volume down as it booted and plugged into the computer, can't be replicated so idk what happened)
So start tutorial here
"adb devices"
"adb reboot-bootloader"
"fastboot devices"
"fastboot OEM unlock"
......
"fastboot reboot"
.......
"adb reboot-bootloader"
"fastboot devices"
"fastboot format user data" (all user data lost)
"Fastboot update /path_to_zip/DM-verity_force..." Drag and drop "payload" into cmd after space in update
"Fastboot update /path_to_magisk (same deal)
" fastboot reboot"
Like magic your rooted. Sometimes you have to download magisk manager from the aurora store in order to use all the features.
For this install you need a working adb environment
the latest Intel drivers
dm-verity dissable.zip
Magisk.zip
I believe this to be the cleanest safest way to achieve root (no zombie recovery.img) even though that recovery may be fine I'm cautious to use it more than I did. Anyways. I recommended this. I'll also advise on installing a google ecosystem without twrp if y'all would like. It would be great to grow this device's community
Now that we are rooted though we can combine our boot.img and stick recovery and make a twrp...I'll probably set that aside for another day since I don't have an immediate need for it (unless some genius makes a ROM)
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Alec!!! You are a GOD in my eyes. I'll give this a go this weekend and report back.
chuck1026 said:
Alec!!! You are a GOD in my eyes. I'll give this a go this weekend and report back.
Click to expand...
Click to collapse
Not to shoot my own post in the foot here but we can install virtual xposed installer and then microg through an included module all without touching our computers. Have fun though guys hahaha I love finding work a-rounds.
https://forum.xda-developers.com/xposed/virtualxposed-xposed-root-unlock-t3760313/page39
^^^^This is pretty much cutting edge android software development so use this as a way to create the right environment on an app by app basis (no root or unlocked boot loader required) kids have been using this to cheat on mobile android games since they dont know how to root. this works for us because we want gapps and there is no hardware command for fastboot mode. be advised my root method still works if you are not intimidated by Epsons' annoying attempt to keep their hardware stock also if you mess up I was informed you are still covered under warranty for "damaged operating system" as if they know its buggy and annoying to work on
google services independent google.map.apk
Use this apk for an easy way to use google maps without google services (less background precessing=more flying) https://drive.google.com/file/d/1GqTrR27gpYXeRl-XtHPbojIwbg89X-9i/view?usp=drivesdk
(No root required)
bricked, thinking about warranty
So I downloaded the nanodroid MicroG installer from the magisk manager (I flashed gapps and google wouldn't whitelist the device ID so I went to microG) and it caused my device to boot loop. It seems my adb key was changed in my device as a result of the install. I don't think this device is worth having root access anymore since i only wanted google services. I do have a usable twrp but the device won't boot to it by default upon boot loop recognition. If I could find a way to tell the device to boot to twrp upon issues (some phones automatically go to recovery upon this situation) I could continue to find ways to make the device more useful. At this point the device responds to adb as (embt3c offline) thoes tricky guys locked me out of fastboot too. Upon boot loop it seems you can get to fastboot only once by repeating the same button inputs you would to get into recovery in the powered off state. Please offer any ideas you may have. Perhaps there is a way we can model the android environment the bt300s operate under with the SDK in order to test our mods? I want to continue but the lack of a button combination to get to recovery just kills me. I hope an engineer of some sort will offer me some guidance on how to proceed. I have seen references of a test plug in order to supply the correct voltage to the chip to trigger fastboot mode but at this point we might as well be hacking with JTAG? I have a small research budget... A spare unit may help development quite a bit. I believe I will use my warranty on this unit so i can continue to enjoy my drone but this is where I stand with this unit. I look forward to insight from the community.
transitioning from script kiddie to developer
So I decided I'm going to learn how to build what we need on this device.
We need
-more test pin info for the hardware fastboot mode (I can build but I'm not good with theory I need help here)
-I'm working on building a virtual moverio bt300. Some guides would be useful. I'm using the android development studio so I can test modules before I brick my device. These babies are too cool for my to resist really. I also downloaded droid explorer in hopes of manually uninstalling the magisk module that bricked my all time favorite waste of time.
-update exactly 24hrs from last time I was able to get into fastboot I was able to get in by holding power and volume down for 10 seconds. I was not able to replicate. Will try again in 24hrs. The device responded to my commands but did not carry them out
recovery mode
We need to find out how to manually put the device into recovery mode. I'm really frustrated this high end "developer" device is so hard to work on. Does anyone know how to do this with code? Idk where to even start my research
Fastboot mode and recovery fix
Hold volume down and power
When green light comes on click volume down while holding power and hold
After first vibration click volume down
Fastboot mode
Repair
My moverio Firmware (FULL ROM) v4.0
Here is a copy of the firmware I am running on my device right now https://drive.google.com/file/d/1xZx6xuubQ-P58LL_-vcuCjPkx-hPTk_v/view?usp=sharing
This is the stock recovery
https://drive.google.com/file/d/1uOofDprPNw4Dqy-euyQwpW3A0LWEZLpy/view?usp=sharing
Stock system
https://drive.google.com/file/d/1f3Xcr4gdKAkG_kiARB3NmEYyjPi41pxA/view?usp=sharing
Twrp prototype (use a mouse that supports linux)
https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
alecthenice said:
Here is a copy of the firmware I am running on my device right now https://drive.google.com/file/d/1xZx6xuubQ-P58LL_-vcuCjPkx-hPTk_v/view?usp=sharing
This is the stock recovery
https://drive.google.com/file/d/1uOofDprPNw4Dqy-euyQwpW3A0LWEZLpy/view?usp=sharing
Stock system
https://drive.google.com/file/d/1f3Xcr4gdKAkG_kiARB3NmEYyjPi41pxA/view?usp=sharing
Twrp prototype (use a mouse that supports linux)
https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Alec, I have to commend you on what you have accomplished with the Bt-300's. Kudos Sir! Keep up the excellent work. :good: We have posted this thread in our facebook group so that all can benefit. If you haven't checked us out, please feel free. You probably have rock star status by now. lol. https://www.facebook.com/groups/269299563510341/
Thanks and Happy New Year!
dvegaman said:
Alec, I have to commend you on what you have accomplished with the Bt-300's. Kudos Sir! Keep up the excellent work. :good: We have posted this thread in our facebook group so that all can benefit. If you haven't checked us out, please feel free. You probably have rock star status by now. lol. https://www.facebook.com/groups/269299563510341/
Thanks and Happy New Year!
Click to expand...
Click to collapse
Thank you for the accolades I am flattered! As for development progress I am trying to figure out what google maps APIs are called upon in the "NLD DJI go 4.22" app developed by the No Limits Drones group. I need this information to know how to patch the system apks and apply the correct form of microG package (basically for google apps and related). On the topic of facebook I have yet to create one but am evaluating cost/benifit on an ongoing basis and will join your community if i do ever make one! I look forward to colaborating on the bt300s now that another creative avenue is unlocked with root access to this cool gadget. Happy new year!
Awesome work!
But I need help, because I am stuck.
I tried different ways with the on and down buttons, but it seems I am doing something wrong.
Everytime the Bt300 boots up normally.
I tried the adb reboot-bootloader, it restarts immediately, but then it`s getting stuck in a
Moverio Boot screen, with the note below "Is now under process"....!?!?! and nothing happens anymore, even after 5minutes it is stuck.
Also it isn`t shown in fastboot devices, just nothing there.
So it seems I can`t get into fastboot by adb command nor manually with the buttons.
ADB Debugging and untrusted sources are enabled, not my first device I try to root, did this on a couple of phones already and are familiar with the process.
But fastboot and the Moverio BT-300 seem to be special.
I tried it now more then 10 times and any hint or advise is greatly appreciated.
My Moverio has the 1.5.0 Firmware installed.
guili2 said:
Awesome work!
But I need help, because I am stuck.
I tried different ways with the on and down buttons, but it seems I am doing something wrong.
Everytime the Bt300 boots up normally.
I tried the adb reboot-bootloader, it restarts immediately, but then it`s getting stuck in a
Moverio Boot screen, with the note below "Is now under process"....!?!?! and nothing happens anymore, even after 5minutes it is stuck.
Also it isn`t shown in fastboot devices, just nothing there.
So it seems I can`t get into fastboot by adb command nor manually with the buttons.
ADB Debugging and untrusted sources are enabled, not my first device I try to root, did this on a couple of phones already and are familiar with the process.
But fastboot and the Moverio BT-300 seem to be special.
I tried it now more then 10 times and any hint or advise is greatly appreciated.
My Moverio has the 1.5.0 Firmware installed.
Click to expand...
Click to collapse
That "moverio is now under processes" screen is your fast boot interface. You should be able to adb pull any .img you need after you pull the boot.img, patch with magisk manager and flash patched_boot.img. Remember the twrp recovery image requires a linux compatable mouse. (You can get "adb su" with twrp recovery if needed) Lemme know if you have any other questions, epson didnt do the cleanest job of with their android implementation most likely for proprietary purposes, we expect better from the parent company Seiko. Have fun.
Yes thanks!
Figured this out in the same second.
I was under the impression that the intel usb/adb driver was already installed, but it wasn`t...
So now I can see it with fastboot devices
Got now the "too many links" message but I follow the guide, this was already explained.
Thanks!
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Ah now, I need your help/advise.
I need this android-help.text file, which need to be included into the DM-verity_force.zip
guili2 said:
Yes thanks!
Figured this out in the same second.
I was under the impression that the intel usb/adb driver was already installed, but it wasn`t...
So now I can see it with fastboot devices
Got now the "too many links" message but I follow the guide, this was already explained.
Thanks!
---------- Post added at 02:30 AM ---------- Previous post was at 02:11 AM ----------
Ah now, I need your help/advise.
I need this android-help.text file, which need to be included into the DM-verity_force.zip
Click to expand...
Click to collapse
Set the path according to this https://stackoverflow.com/questions/5846197/error-could-not-load-android-info-txt
Dont have android-info.txt? Ill track it down for you within the day. I got it from the original bt300 thread somewhere.
Flashing zips through Bt300 hacked recovery has been tested and is the easiest way to accomplish customization at this point. Please use caution to chose the hacked recovery rather than 4.0 stock. Check your work with "fastboot getvar all" as always.
-cheers
An update on how to manually boot to fastboot "incase you have issues"
Hold power and volume down button while device is powered off
You will feel a vibration and see the epson logo. In this same moment release volume down
Quickly press volume down again (hold power the whole time) and you will be brought to the "moverio is now under processes screen"
Here you will be able to flash/boot to the prototype recovery to rescue yourself.
****prototype is safe you just have to use mouse*****
It is possible to root this device classically with twrp and magisk as a flashable zip. Remember the order is DM-verity dissable, then Magisk.
prototype TWRP cannot decrypt the userdata partition so make sure you act accordingly
alecthenice said:
@amg314 pointed out to me that the most direct way to do this is through adb since any failure could be catastrophic... In the past we used a recovery that almost worked for Moverio Bt300s, I will link it bellow for academic purposes; anyways (fastboot under some situations requires something special...I really wanna know, I think I got it once by holding power and volume down as it booted and plugged into the computer, can't be replicated so idk what happened)
So start tutorial here
"adb devices"
"adb reboot-bootloader"
"fastboot devices"
"fastboot OEM unlock"
......
"fastboot reboot"
.......
"adb reboot-bootloader"
"fastboot devices"
"fastboot format user data" (all user data lost)
"Fastboot update /path_to_zip/DM-verity_force..." Drag and drop "payload" into cmd after space in update
"Fastboot update /path_to_magisk (same deal)
" fastboot reboot"
Like magic your rooted. Sometimes you have to download magisk manager from the aurora store in order to use all the features.
For this install you need a working adb environment
the latest Intel drivers
dm-verity dissable.zip
Magisk.zip
I believe this to be the cleanest safest way to achieve root (no zombie recovery.img) even though that recovery may be fine I'm cautious to use it more than I did. Anyways. I recommended this. I'll also advise on installing a google ecosystem without twrp if y'all would like. It would be great to grow this device's community
Now that we are rooted though we can combine our boot.img and stick recovery and make a twrp...I'll probably set that aside for another day since I don't have an immediate need for it (unless some genius makes a ROM)
check out the hacked recovery image (you must use mouse) https://drive.google.com/file/d/1fcLoHw0CTAs7qIYZi2xoaAgImVREHz8O/view?usp=sharing
Click to expand...
Click to collapse
Flashing zips through the prototype recovery is now the easiest way to make your A/R goggles custom. Im glad I initially did it the old school way for the sake of understanding epson file systems. This twrp works traditionally and has all partitions correct!!!
Bootloader unlock problem with v5.0
It has come to my attention that there is a problem with the bootloader unlock command for version 5.0 firmware
to solve this please boot this boot.img
use the command "fastboot boot boot.img"
****note the command "fastboot flash boot boot.img" may cause issues****
after you boot this boot.img
"fastboot oem unlock"
disregard the response. enter this command after to check your unlock status
"fastboot getvar all"
you should be in the orange state and this will be persistent upon the next reboot
DOWNLOADhttps://drive.google.com/file/d/1_2qwuL85SkirnEu7bHLRigBWrJlPnYXj/view?usp=sharing
Correct getvar all response[/B]https://drive.google.com/file/d/0BzLMyqznaCbVVnFXQ2NqNnppXzg4LVQ0ajNmMmU2c2hjTktJ/view?usp=sharing
Does anyone know where the ota updates are stored on this device? I will pull the updated boot.img and patch accordingly so the bootloader unlock is more simple if i can find the ota...OGs in the original hacking forum have fell silent on this, furthermore it seems that the epson file systems team only wants to utilize my input for their own development so I have stopped communications with the contact I had.
I can post a full nandroid backup on here if others would like to revert to software 4.0
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.
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?