Develop Bugs

[Q] Update messed up G-Pad

I had stock installed, rooted and twrp install, I downloaded the update and now it only boots into twrp. So i tried factory reset and restoring a backup I had, still nothing. Just now I pressed advanced wipe everything except SD Card, now I have no OS And no backup to restore.
For some reason twrp doesn't recognise any micro sd card I put in, says it cant mount them.
I can't get adb working whilst in recovery. I just want to go back to stock.
Also holding down vol down and up to get into download mode doesn't work.
Thanks for any advice.

Got it into download mode now somehow (rebooting from twrp instead of cold boot) and downloading the stock firmware from LG mobile support tool.

mike_1983 said:
Got it into download mode now somehow (rebooting from twrp instead of cold boot) and downloading the stock firmware from LG mobile support tool.
Click to expand...
Click to collapse
same problem here.. how did you get to download mode? cannot find a way..

Trunkam said:
same problem here.. how did you get to download mode? cannot find a way..
Click to expand...
Click to collapse
1. Turn off the tablet. (from twrp menu )
2. Push vol+ and vol- same time.
3. Insert usb cable.
4. Release both buttons. Now you should be in download mode.

hi mike_1983, but have you solved with this method?

Palux said:
hi mike_1983, but have you solved with this method?
Click to expand...
Click to collapse
I was in same situation. And i solved installing stock room with LG Mobile Launcher.
Go in download mode, and then follow this method: http://forum.xda-developers.com/showthread.php?t=2471370 is 100% working.

dont update the official rom if you re rooted or you have a custom recovery, they ll brick your tablet. If you have access to recovery you can install a custom rom and there is no need to go back to full stock (unless ofc you want to keep the stock rom in which case you need to flash it using the lg mobile support tool)

I think I did it by holding down vol up and vol down whilst in twrp, then pressing reboot, system (or perhaps pressing reboot system then holding them down). I'm not sure if the usb cable was plugged in or not. I tried holding down vol up and down from powered off, but it seemed to still always go into twrp.
Then you need B2CAppSetup.exe which is LGMobile Support Tool, you can then download the stock rom, it overwrites everything, like recovery and root.

Made the same mistake : said yes when the tablet proposed me to update. Booted in TWRP.
Tried to flash with support tool but it stops at 95% and tells me in german (!) to remove the battery and try again... I've tried many times (without removing the battery obviously), just the same.
And now I can't get out of the download mode. Everytime I plug the USB cable, it goes to download mode.
Any suggestion ?
EDIT :
I even tried this method : http://forum.xda-developers.com/showthread.php?t=2622777
and it stops giving me a decompression error...
Edit 2 : it finally uncomressed corectly but i'm still stucked at 95% when installing : WPARAM_UPGRADE_ERROR
EDIT 3 :
Using the method http://forum.xda-developers.com/showthread.php?t=2622777 and leaving default parameters : Korean language and country it finaly worked with the V50010A_00.kdz firmware.
My lg g pad is finally booting ! (the battery is totally drained)
Thanks to all !

Exoten said:
Made the same mistake : said yes when the tablet proposed me to update. Booted in TWRP.
Tried to flash with support tool but it stops at 95% and tells me in german (!) to remove the battery and try again... (..)
EDIT 3 :
Using the method http://forum.xda-developers.com/showthread.php?t=2622777 and leaving default parameters : Korean language and country it finaly worked with the V50010A_00.kdz firmware.
My lg g pad is finally booting ! (the battery is totally drained)
Thanks to all !
Click to expand...
Click to collapse
Many Tanks to Exoten (and others) :highfive:
Same mistake... Same errors (no standard flash / method available)... Try method from Edit 3 and ... My wife is happy again (this is her tablet)
++ No Wipe data necessary - All data (SD and internal were kept)
+ the OTA upgrade was applied, even if I selected A version of KDZ (and not B version)
- I lost the root
F'bien

Bootloop after update ?

Hey there,
I'm new on xda. I see at least im not alone to have G8, this is great !
Recently, I received an update for RIO-L01C02B140 (G8 double sim and rooted device with TWRP) of 150Mo. I clicked the update button but when my phone restarted it just booted on TWRP and didnt boot on system anymore.
Thankfully, looks like someone here had the same problem and with the answer of another member I could fix my device. (the thread)
But now i see that the update is still undone, so is there a way i can do it safely? I'm afraid if i click it, it goes wrong again. I dont think it's a major update but still it should be cool to be able to make updates...
Thanks for eventual replies

1. downloaded the original Stock Rom from http://forum.xda-developers.com/gx8/how-to/g8-g7-plus-official-roms-europe-t3294362
2. Re ziped the dload folder to a NTFS formated SD card
3. Turn off the phone
4. press Vol up + Vol down + power
5. The phone start´s with flashing
If it is not open bootloader need to open !!!
you must be a stock recovery !!!

Stuck in fastboot. No recovery... no bueno :(

So I had my ze551ml / Z00A rooted, was loving life, all was great. Then I tried getting XPosed access and didn't read up on it prior. Anyways, now my phone is stuck in fastboot, I'm able to flash partitions and all, including recovery partition, yet I cannot enter any mode but the hung ASUS logo, or fastboot. I weas even able to load CM's "upgrade to MM bootloader" package, but still the same thing only with green letters where they once were blue..... Please help, I need my beloved phone back.....

I'm not a pro but if you can access fastboot it is just a soft brick and I'm sure many people can point you on the right thread to recover it.

I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....

joecost85 said:
I've scoured the depths of both XDA and the ASUS forums, and while I've gained much knowledge of how I can possibly fix it, nothing seems to work. I go to select "recovery mode" and it instantly just boots right back in to fastboot.....
Click to expand...
Click to collapse
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?

timbernot said:
What ifwi version does it state you have in bootloader screen
Example :-
0094.0XXX
X=?
Click to expand...
Click to collapse
0094.0183

joecost85 said:
0094.0183
Click to expand...
Click to collapse
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link

timbernot said:
Thanks -- you can install giovix`s modder tool from general section
Set it up , use`return to stock option` --in that option , first select boot , then after- recovery(both will be stock)
You then can either
A- Reboot to stock recovery ,adb Sideload stock M -- Follow on to B-( to back-up stock before flashing)
B- Unlock bootloader again , flash twrp and root (if twrp version in modder is now 3.0.3.M4 you can flash lineageos)
---------------------------------------------------------------(if twrp version in modder is still 3.0.2.1 M - you will have to flash 303M4 in fastboot or in 3021M twrp.
1) You might be able to, fastboot flash 3.0.3.M4 immediately and forget above A&B completely
For 303M4 recovery see lineageOS in original android development section OP for download link
Click to expand...
Click to collapse
So I've yet to try your solution, but I do have an update, I was able to, one by one, flash all the stock files (stock as in the stuff I downloaded from asus site) and was almost able to boot to recovery, but when I got to the red triangle android, I couldn't get it to go further. I've heardf alternate key combos for proceeding from there, and tried them all, but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**

joecost85 said:
So I had my ze551ml / Z00A rooted, was loving life, all was great. Please help I need my beloved phone back.....
Click to expand...
Click to collapse
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
joecost85 said:
So I've yet to try your solution,
but maybe I'm just an idiot...... I'll try the giovix solution when I've got time (patience).
**when I tried flashing the cm upgrade package after that, it went back to square 1, so I gave up for the evening.**
Click to expand...
Click to collapse
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108

timbernot said:
Hello again , when you come here begging for help to get your life back and someone with the decency gives you a hand ,a solution , out of respect its got to be worth a try ?
joken btw , I typed out a solution to a regular problem that if you try , will work, you can then like and I can direct others to and also help those that search.
At xda , this helps immensely to prevent same posts,people posting just to waste time or just to spam
---------- Post added at 09:30 AM ---------- Previous post was at 09:19 AM ----------
The last bit btw wasn't in any of my suggestions
TY
The solution I posted fixes many problems , consider that TWRP is now 303M4 , upgraded .
https://forum.xda-developers.com/ze...-apps-apps-t3554565/post70980108#post70980108
Click to expand...
Click to collapse
Here's the thing. I'm super stubborn, and I think I know everything (cuz I do....) so of course I decided that I could figure something out, so I tried my way first............ didn't pan out.... anyway, I'm finding any time I flash a TWRP file, I have no access to recovery mode. Regardless if I do it manually through fastboot, or CM upgrade/downgrade or even the giovix fix (yes I tried it). My question is this, Where is there a return to stock option? of the giovix DLs I could find, I see a 'magisk root' 'TWRP' 'bootloader unlocker' and 'Xposed' tools, nothing else.... Am I missing something? or am I just skimming over that part?
I do appreciate all the help, seriously. Even if it seems like I'm not taking suggestions very well. It's moreso I don't have access to a computer most of the day, and it's not a huge priority since I went and bought a zfone 3 max a few days ago (decent phone for what it is....crazy battery life)

https://forum.xda-developers.com/zenfone2/general/tool-ze551mlmodder-t3458145
Functions:
1- Check connection status
2- Bootloader Unlocker
3- Flash TWRP 3.0.2-0 M1
4- Full-auto xposed flasher!
5- Full-auto root flasher!
5B- Full-auto root (Magisk+Phh's) compatible with 184!
6- ADB Shell
7- Return back to stock
8- Erase /system, /data and /cache for a clean upgrade
9 (HIDE)- Auto-reboot to bootloader
10- More functions inside!

well then forgive me for not downloading the correct option. I nowhere see this list among anything I downloaded, so maybe specify which is which ('full' or 'auto')....... I'm already downloading both of them again, because I'm not sure which I already had. But yea, one of the 2 only has the 4 options I mentioned.

Its not rocket science

timbernot said:
Its not rocket science
Click to expand...
Click to collapse
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?

joecost85 said:
So i finally see what you've been trying to tell me, and I returned everything back to stock, but I still have the same problem, recovery now loads but system wont boot up. I'll try loading the individual factory IMG files today, via fastboot, or should I use a zip file from Asus via recovery?
Click to expand...
Click to collapse
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )

timbernot said:
In stock recovery - choose update from adb -- adb sideload cmd is >
adb sideload MOFD_SDUPDATE.zip
Put .134 M asus firmware in adb/fastboot folder first rename it to MOFD_SDUPDATE(without zip) before this cmd above and then open up adb and type it in and hit enter.
Just in case you are trying different methods (see if this works )
Click to expand...
Click to collapse
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.

joecost85 said:
I'll try it today. Last I checked it was hanging at the ”! Android” screen. But then again I'm not sure I know the combo to get passed that screen, I know it's either power and + or power and - but my only success I got into by button mashing all three keys rapidly, so, yea, I know, I'm am idiot.
Click to expand...
Click to collapse
EDIT"""" because i got it wrong too , i dont even think about , i just do it
It`s ->
From powered off position
Press Power and Vol +
at two vibes, release power
at boot up screen ,release vol+
in bootloader ,scroll vol up or down to and then select(press power) at recovery selection.
At dead android guy -> press vol + and power for 4 seconds -> release Vol +
You should be in recovery.

i am replying in this post since i have a similar problem, and I am as stubborn as OP. Me posting here is a big step in acknowledging my defeat at last. Hours of digging through the internet didn't solve my problem
I have changed my ifwi and dnx more times than i can remember. (my clean slate is mostly using xFSTK downloader with xFSTK_ZE551ML-sal358-amtech.vn files)
Using the above mentioned method (giovix`s modder tool) to go back to stock i still boot into fastboot, not recovery mode.
trying to unlock bootloader it says on the phone "unlock fail"
Using asus flash tool with raw files i get "gpt command failed"
Using a manual method i get the "gpt command failed" on the "6. fastboot oem partition /tmp/partition.tbl" step
in my opinion as soon as i get some kind of recovery my problems are solved. But have been working four hours on this problem with all possible solutions i could think of, nothing but frustration.
info: current ifwi 0094.0183 (wich should be M)
serial 01234........EF
and using the toolkit on "https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293" i found out my device firmware version is 198 (wich is probably not good in combo with the ifwi)
little update in a certain config (android 5 / ifwi 0094.177 / stock recovery) i can boot up untill the dead android icon, but with whatever key combo can't get past it... (vol up + power) / (vol down + power)
fastboot flash boot recovery.img (yep i am really desperate to get into recovery) doesn't even give me the dead android.
thank you beforehand!

Last paragraph with android 5 ifwi 0094.0177
Is your serial correct ?
Press vol + once is it correct?, if not you will have to xfstk first again and flash raw (twice) with temp bootloader 0094.1069
See my unbrick video for help

First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?

Speybrouck said:
First of all, thank you very much for your reply!
I was not very specific there, the android 5 is not the rom (still wasnt able to flash the rom) its only the files like droidboot, ifwi, dnx, .... that i got form lolipop.
Indeed the serial is still 1234........EF (so not the correct one)
I do understand i have to flash the raw twice to get the correct serial, but flashing raw doesn't work. I get "gpt command failed" every time. (so the point where i have to restart flashtool is not even reached). Also if i try to do it manualy.
I watched your video (thanks it was my first steps into understanding how it all worked) but unfortunatly didn't work for me.
Any other ideas?
Click to expand...
Click to collapse
Did you get this device in this condition ?
If not, what happened so that you lost serial ?
Anyway , i have never tried this because i have ALWAYS succeeded flashing raw (twice) to correct serial BUT it may work for you.( i am not sure you have a device that can have the serial corrected due to whether its been tampered with previous ) which affects recovery and IMEI.
Usually , xFSTK is used to install temp bootloader - Its supposed to be the lowest level form of unbricking procedure and restores temp bootloader so you can fastboot after-- flashing raw in fastboot via AFT(twice) restores serial -- 1st flash approx 3mins is with incorrect serial and temp bootloader.
After a couple of mins, cmds on phone pauses on RESULT=OK on phone.
You close AFT and open AFT again , input raw and set AFT up -- press Vol+ on phone -> once, serial will be corrected and 2nd flash can be started and left until it boots into android 5 by itself.
If GPT trouble , that link may help.
There is other programmes for starting to create serial and restoring .
Usually people who use these , have to dig deep into buildprop stuff which if tampered with can end up with problem such that you have.
Good luck
see if anything here helps
https://forum.xda-developers.com/showpost.php?p=70223946&postcount=8

[RECOVERY][UNOFFICIAL][TWRP] For Sony Xperia T3 D5103 (seagull)

Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone

Cool, although upon booting into recovery the screen isn't operating normally, similar to what happens when flashing the fxp lollipop. Might be because I'm on stock ROM/kernel though.

What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute

EmaMaker said:
What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute
Click to expand...
Click to collapse
Yes, sorry for not being more specific xD, I'm indeed getting the white-grey bands on screen.
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
It's possible it's the lollipop kernel that's to blame, since I've had the same problem with other lollipop builds.

Fixed
Download link fixed with working version

EmaMaker said:
Download link fixed with working version
Click to expand...
Click to collapse
Will try it and report back ?

Tried the updated one, still no luck. It could be just my device though.

Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls

EmaMaker said:
Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls
Click to expand...
Click to collapse
Tried both versions, so it's probably my device.
(However, if it is it's fine, since I do have working twrp.)

Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,

Don't know
goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
One of my two seagulls came back from assistance and I tried to flash TWRP on it without any problems. I don't know if it had an updated bootloader or what, but the firmware was stock

goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
In order to flash recovery, you first need to download and install the Emma flashtool and restore your phone through it. That will add a recovery partition so you can flash twrp. (The Emma flash tool supports only the D5103 model of the T3 as far as I know)

I tink you will have the same as the eagle (m2) device, you need to update your bootloader and then flash recovery...

EmaMaker said:
Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone
Click to expand...
Click to collapse
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers

Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards

EmaMaker said:
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards
Click to expand...
Click to collapse
Oh, thx for your reply, I didn't expect it really after so many days This method doesn't work, unfortunately. But I won't bother fixing the power button, actually Ive just being using my old Xperia for testing purposes only. But thank you anyway :good:
Regards
Sent from my mido using XDA Labs

Boot loop
Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:

sushil lad said:
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
Sorry bro, I don't own this device anymore and I truly don't remember the procedure...
Sent from my SM-T720 using XDA Labs

sushil lad said:
Boot loop
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
same me too

Question [SOLVED] Can't return back to stock ROM.

Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.

NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
Try flashing miui via batch scripts is what I would do...
When you extract firmware there should be flash_all.bat file inside, run it via cmd - just type the name of it with cmd directed at the folder where the firmware is unpacked. ( For this you need adb tools installed properly so that the whole system has access to it , if you don't know how then download platform tools from google , unpack it and copy everything inside platform tools folder then paste into firmware folder , then you should be able to run the scripts inside firmware folder )
It will start regular process that mi flash does but if it fails then I guess you can see where it fails exactly and update here .
Idk...

You know, this would've been much easier to read if you put some effort into your grammar.
What error did you get in Mi Flash? Did you download the correct Fastboot Stock ROM for your specific region?

NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
Click to expand...
Click to collapse
try to download again the firmware, maybe the file you have been trying to flash is corrupted.
Most and foremost, try to be specific what it was you encountered. Feels like I was reading in a wattpad.

How did you do it?

Please share with how you solve it
NTClarity said:
Greetings. First of all , I have to say that I think i messed up many things.I'm going to describe all of my steps and how I ended up stuck with fastboot and .. nothing else. So I started with installing stock rom by twrp . Booted to twrp , cleared cache and data and when I flashed the zip , I got error 1 . So I thought it would be easier to do it with Miflash tool. Next , after installing miflash and the fastboot version of the rom , I flashed it but it seemed that it was taking so long (more than 2000 seconds ) and it was stuck on flashing a specific file. The next and crucial imo move I did was to remove the usb cable from my phone resulting to an error in miflash (obviously). And this is when I realised that when I pressed the power button for a long time , it wouldnt boot to my custom rom . Instead it turned back to fastboot . I tried one more time flashing the stock rom with miflash but got an error after a few minutes. Also , I tried to boot to twrp by pressing volume up + power button , but it turned to fastboot again. So I opened cmd , booted to twrp from there and I thought about flashing twrp from the recovery (flash current twrp)and... guess what . Got an error and couldnt flash twrp. I have been searching for help online over the past 3 hours , but unfortunately I havent found any fixes yet. I would really appreciate any help from here , as I really dont want to lose my device. Thanks in advance.
EDIT: I have solved this issue.
Click to expand...
Click to collapse
Please share with us how you solve it

miku1024 said:
Please share with how you solve it
Please share with us how you solve it
Click to expand...
Click to collapse
Basically , I managed to flash it successfully after many attempts. I was getting different errors every time when I was trying to flash the EU version in my PC , so I thought of switching to my laptop and trying with the GLOBAL version this time. I succeed the 2nd time . I also used a different usb cable. So it was just miflash being miflash... nothing to worry about.