Hi,
I'm trying to root my xperia m4 aqua E2303 which is running android 5.0, and managed to:
-unlock bootloader (then reboot)
-install ( I think ) TWRP (then reboot)
I then flashed the boot.img from this tutorial which I now understand is for 6.0 and not 5.0.
when I rebooted, the phone went into the boot animation (the blue waves thing) and got stuck there for 2 hours until I unplugged it for it to run out of battery and shut down.
when it is in such state, I can see it connected to the PC with
Code:
adb devices
although it is not authorised.
I am also able to enter fastboot but I have no idea what to do from here.
when in fastboot,
Code:
fastboot devices
tells me it is correctly connected and I am able to send commands such as
Code:
fastboot reboot
I have tried to enter TWRP by pressing volume down, but maybe i'm doing it wrong, because I haven't succeeded.
please help.
thanks.
fastboot reboot recovery
You Flash MM Kernel in LP And Finally bootloop. Flash LP Kernel with Flashtools.
Related
Hello,
I'm trying to install TWRP on my m4 aqua. I already unlocked the bootloader and rooted it. Now im trying to install TWRP without success. With a command prompt, my devices won't be detected. And with a install.bat file nothing happens on my phone. The normal adb and fastboot drivers were successfully installed but i can't install the flashtool drivers to start the fastboot mode. Also with the Volume - button the phone boots normaly. So im now trying it with this TWRP app from the teamw.in (can't post the link) website with the modell xperia m but im not sure if it works. Can someone help me ?
XThorodinx said:
Hello,
I'm trying to install TWRP on my m4 aqua. I already unlocked the bootloader and rooted it. Now im trying to install TWRP without success. With a command prompt, my devices won't be detected. And with a install.bat file nothing happens on my phone. The normal adb and fastboot drivers were successfully installed but i can't install the flashtool drivers to start the fastboot mode. Also with the Volume - button the phone boots normaly. So im now trying it with this TWRP app from the teamw.in (can't post the link) website with the modell xperia m but im not sure if it works. Can someone help me ?
Click to expand...
Click to collapse
Lollipop or Marshmallow? Why can't you intall the drivers from flashtool? It boots normally probably because of missing the drivers. And to enter fastboot, you need to hold Volume UP and then connect the USB. If your BL is unlocked, then you can easily flash the TWRP through fastboot mode. In Command p. Fastboot flash recovery "recovery name".img usually it's recovery.img . But without the correct drivers, your phone will not be recognized properly.
ekin_strops said:
Lollipop or Marshmallow? Why can't you intall the drivers from flashtool? It boots normally probably because of missing the drivers. And to enter fastboot, you need to hold Volume UP and then connect the USB. If your BL is unlocked, then you can easily flash the TWRP through fastboot mode. In Command p. Fastboot flash recovery "recovery name".img usually it's recovery.img . But without the correct drivers, your phone will not be recognized properly.
Click to expand...
Click to collapse
I'm using Lollipop 5.0 on my phone. When i'm trying to install the drivers i always get that error: installation failed. Ahhh Thanks its Volume UP. But after this the led lights blue and then comes the charge indicator. Is it normal ?
I now installed TWRP with a bat file. But with Volume UP and usb cable I don't come in the Menu. And with Volume UP and Power the phone just vibrate a few times.
My OPX is running marshmallow 6.0.1 oxygenos 3.1.3 for the past 1 week or a bit more after the OTA update.
I had unlocked the bootloader 2.5 - 3 weeks ago when it had lolipop but I didn't install twrp. It is still unlocked after the update obviously (i have properly checked the oem unlock by the fastboot command fastboot devices oem and advanced reboot). I downloaded the latest twrp version for the OPX: twrp-3.0.2-0-onyx.img (link: https://dl.twrp.me/onyx/) from the official site. I renamed the file to "twrp" In fastboot mode, I used the command: fastboot flash recovery twrp.img. It flashed successfully, as the 2 "OKAY"s appeared. After flashing was over, I used the recovery boot command: fastboot boot twrp.img which FAILED and gave an error- remote: dtp not found. Then I switched off the device using the power button and the tried the recovery mode combination i.e power button + volume down. Although the phone started, it didn't boot into the recovery and got stuck at the "oneplus powered by android" screen. I tried the combination again after which it switched off and returned to and got stuck at that same screen. Frustrated, I rebooted into the OS using the fastboot reboot command and booted into the recovery using advance reboot. To my dismay, I still had the stock recovery. The only difference in the recovery was that it wanted me to choose a language and then it started, just like when i had first booted into the recovery after buying the phone many months ago. I have tried this whole thing 2 times but with no luck! The twrp recovery flashes but fails to boot by any means, be it that fastboot command, the recovery mode combination after flashing successfully (and enter the boot command which fails) where it gets stuck on "oneplus powered by android screen" and rebooting into OS and booting into recovery using advance boot where the OS has already replaced twrp with the stock recovery.
PLS HELP!!
This is the guide I followed- https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
And also, I used this video for reference- https://www.youtube.com/watch?v=RwYmyXyJeww
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
I tried doing this root and safetynet procedure https://forum.xda-developers.com/m4-aqua/general/systemless-root-safetynet-t3725341
in my xperia m4 aqua e2306, but I can not get into recovery mode, I already tried to get into adb and it does not boot or simply reboot in normal mode, I tried to push volume (-) and power button, but it also does not work, and finally I used recovery reboot (and other apps) and nothing worked
This is for sony m4 aqua marshmallow 6.01 (SINGLE SIM)
You must have your bootloader unlocked before attempting this and usb debugging and oem lock both switched on.
For the boot.img and recovery.img you'll need for root CLICK HERE
Download then put the .img's inside your adb fastboot's home folder
Right click on an empty space inside adb fastboot and select open terminal here
On the command line input this command - adb devices -press return(you should see devicies serial #)If no reply from your phone check cables and s1 driver's.
If you are having S1 driver problem's download and install THIS it will install the driver's for you this will work for all phone's.
Once all is good.
On command input - adb reboot bootloader -press return
Once you are in bootloader mode your led on mobile should turn blue
Then input - fastboot flash recovery M4_tulip_recovery.img - return (should take around 5 sec's to flash)
You now have twrp to access switch off phone wait till it vibrates or 10 sec's hold down vol then press power on when sony logo appear's let go of vol down and click a couple of times twrp will start in around 5 sec's.
Switch phone on and put phone back into bootloader mode with -adb reboot bootloader -
Wait for blue led ---
Then input - fastboot flash boot M4_tulip_su_boot.img -takes under 10 sec's
Restart phone with - fastboot reboot - or switch on manually.
If all went well once restarted your phone should now have the supersu app installed and phone rooted with twrp recovery.
It may be worth mentioning that the command line is case sensitive so if any problem's just copy and paste the command's written above straight to the command line.
If you try to install supersu with a zip from twrp on the sony m4 you will probability run into trouble i have had nothing but bootloop's trying that way.
You can flash the .img in any order.
I was trying to flash TWRP in Gionee P5W. The steps I followed were:
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot flash recovery recovery.img (had prepared TWRP img file already)
4. fastboot reboot recovery
I later found out that the last command should had been fastboot boot recovery.img.
Now my phone is stuck in bootloop. I tried going into recovery (vol-up + power) but I only gat the gionee logo and then the boot loop. What is the condition with my phone and is there something that can be done?