Bootloop fix after rooting and downgrade

Bootloop fix after rooting and downgrade - Micromax Canvas A1

Many of us tried to root our Android Marshmallow Android one device and ended up in bootloop.Well this happened bcoz rooting android 6.0 requires custom kernel and root toolkits wont work(Check this link for perfect root procedure for ur android one device-http://www.ibtimes.co.uk/how-root-android-one-devices-android-6-0-marshmallow-update-1523222 )
Android 6.0 itself was not stable for atleast Android One users as it gave path to battery drain and wakelock,so many people wanted to downgrade.This post will tell you how to downgrade and fix any bootloop caused on android 6.0 after rooting.
THIS PROCEDURE WAS TESTED ON MMX CANVAS A1,IT MIGHT WORK ON OTHER FIRST GEN ANDROID ONE DEVIES IF YOUR ABLE TO GET STOCK ROM FILES.
Requirements-
Android One device
Fast boot and ADB on PC
SP tool(http://androidmtk.com/smart-phone-flash-tool)
Stock Rom-(Link for AQ502-http://firmwarefile.com/micromax-aq4502 and link for aq501- http://firmwarefile.com/micromax-aq4501)
NOTE- WARRANTY WILL BE VOID ALTHOUGH U CAN REGAIN IT(I'LL DISCUSS IT LATER)[/B]
DATA WILL BE LOST.CREATE BACKUP IF POSSIBLE.YOU CANT DO BACKUP IN BOOTLOOP CASE[/B]
Step 1-Reboot your device in recovery,to do so shut down your device then press volume down/up button and power at same time and hold it for a few seconds.Your device will show several options like fast boot and recovery,select recovery by pressing volume down button.Once in recovery,navigate using volume up and down and power button to select.Select reboot to bootloader and you keep your device aside.
Step 2-Turn your device in which ADB and Fastboot is setup.Plug in your device(which is in bootloader now) via USB cable and type the follwing command
fastboot oem unclock
Your device might ask to confirm it by pressing volume up,do so.After unlocking ur bootloader,shut down ur device by removing battery.
Step 3-Now your bootloader is unlocked.It is compulsory to unlock bootloader or else the SP tool will not work.Now download the required stock rom on ur device.Once downloaded open sp tool flasher and use it to flash the stock rom on ur device(http://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool)- visit this link,to see how to use sp flasher.
Step 4-Once flashed give ur device few mins to boot, first boot might take as long as 10 mins.Dont panic!
Step5-Your device has successfully booted up-cheers!
Step 6(optional)-You can regain warranty by relocking bootloader,by again going in recovery and selecting apply update from bootloader and using fast boot but this time execute this command
fastboot oem lock
confirm this on ur device like you did to unlock it.
Step 7- We are almost done,your device will be most likely in Android 5.1(depending on the ver. of Stock ROM you downloaded),you dont need a custom kernel to root this version.Use toolkit however if u want to root android 6.0 follow the link i shared in introduction.
Enjoy!you have successfully break the bootloop/downgraded from Marshmallow to Lollipop!!Any questions then pls comment below!

Thank you. this post helped me to solve bootloop issue in Spice Android One from Marshmallow update

Related

[Guide]Restore to Stock "Bricked" "Unlocked" LG Optimus G f180,E97x

[Guide]Restore to Stock "Bricked" "Unlocked" LG Optimus G f180,E97x
The problem starts when you unlock F180 Bootloader with "freegee":
Unlock the bootloader:
There are 2 ways:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- enough fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function keys
-Cons:
- To Relock, just you have to flash KDZ
Method 2: Unlock by app
https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en
Advantages:
- Add.
- Can be easily Relock by app.
Cons:
- Right to Recovery through app (on Stock Rom & 975).
- Loss of function fastboot that this very important function.
- When crashes, not able to Recovery by pressing hard.
It is recommended to use the first way. :angel:
on E975, E970, E97.x unlock, select KT or SKT. Because E975 and the S / K has Same bootloader unlock.
i have already faced this situation to unlock bootloader with freegee and stuck with google logo and fastboot mode :crying:
not even KDZ flash working, always result in fastboot or KDZ tool stop working. also tried different KDZ and flashing Tools
Tried "TeenyBin" ,not success :crying: but get twrp working, then flash CM10 as suggested but got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function
-Cons:
- To Relock, you have to flashed KDZ
Click to expand...
Click to collapse
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/showthread.php?t=2388440
:good:
have to follow the procedure because adb in recovery not able to replace the bootloader files
KDZ flash After mako bootloader unlock
step 1:
use TeenyBin http://forum.xda-developers.com/showthread.php?t=2249500
get twrp working, then flash CM10 for you device.
you will got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
step 2:
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
to reflash the bootloader files you have to enter in CM10 or some ROM with SU or busybox;
now the device comes in life in CM10
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
Quote:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kz...1.2_edited.zip
Advantages:
- fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function
-Cons:
- To Relock, you have to flashed KDZ
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/show....php?t=2388440
have to follow the procedure because adb in recovery not able to replace the bootloader files
Click to expand...
Click to collapse
UNLOCk steps:
enable USB debugging
connect as MTP
follow the steps in script

umar_fiaz said:
The problem starts when you unlock F180 Bootloader with "freegee":
Unlock the bootloader:
There are 2 ways:
Method 1: Unlock the bootloader
http://www.mediafire.com/download/kzbp2gicuj22cv5/Tool_Root_Unlock_BL_4.1.2_edited.zip
Advantages:
- enough fastboot functions: Start, Power Off, Recovery mod, Restart Bootloader
- Easy on the function keys
-Cons:
- To Relock, just you have to flash KDZ
Method 2: Unlock by app
https://play.google.com/store/apps/details?id=edu.shell.freegee_free&hl=en
Advantages:
- Add.
- Can be easily Relock by app.
Cons:
- Right to Recovery through app (on Stock Rom & 975).
- Loss of function fastboot that this very important function.
- When crashes, not able to Recovery by pressing hard.
It is recommended to use the first way. :angel:
on E975, E970, E97.x unlock, select KT or SKT. Because E975 and the S / K has Same bootloader unlock.
i have already faced this situation to unlock bootloader with freegee and stuck with google logo and fastboot mode :crying:
not even KDZ flash working, always result in fastboot or KDZ tool stop working. also tried different KDZ and flashing Tools
Tried "TeenyBin" ,not success :crying: but get twrp working, then flash CM10 as suggested but got this
Subsystem Crash!
------------------------------------------------------------
DemiGod Crash Handler : Subsystem Crash! : External_modem (Undefined error)
Press key to choose Dload Mode/Reboot/Fastboot.
1) Volume Up : Dload Mode.
2) Volume Down : Reboot.
3) Power : Fastboot.
------------------------------------------------------------
to solve this have to remove sim card and change baseband in TWRP using ADB
then perform a hardreset.
now the device comes in life again
but you find the device is not properly working may be sim or gprs or wifi or something else.
now have to unlock bootloader again by adb with this method
after that will able to flash the stock KDZ without any problem
put device in D/W mode and flash it with appropriate official KDZ
Guide to flash KDZ
http://forum.xda-developers.com/showthread.php?t=2388440
:good:
have to follow the procedure because adb in recovery not able to replace the bootloader files
Click to expand...
Click to collapse
thx for post my friend i have e975 i use freege and mako unlock .I used the first two months trouble-ROM but i have Subsystem crash error.... (external modem ) and i back to stock kdz but no root +bootloader unlocked i use my rom but I found something new
----------------------------------------------------
This problem can easily be solved, I spent 20+ hours on researching this, it's not an operator problem, but a common problem with both the Optimus G and the Nexus 4.
What causes it? Extreme low power states of the processor, some modems are too sensitive for this kind of deeeeeeep sleep (depending on production batch). These states are called C0 (WiFi) until C3 (complete power collapse).
Disable C2 and C3 and enable C0 and C1 and voila, it will never happen again
How? Buy and install Fauxclock, I don't know how to do it manually nor I couldn't find any other app.
You can thank me, but you should also thank Faust because he brought me this solution. Joying all the custom roms for months without problems
---------------------------------------------
Quote:
Originally Posted by metrixx02 View Post
my friend thx for post but ... i have one question what is this c0,c1,c2,c3c ????? CORES ?
x_justin :
No some power state of the processor, linux terms. Nothing to do with core numbers. As far as I know the only app that can change this is FauxClock from the play store, but it's worth the money. Just disable C2 and C3, it's still good for the battery. Stock roms from LG also have this disabled.
C0 Operational state. CPU fully turned on.
C1 First idle state. Stops CPU main internal clocks via software. Bus interface unit and APIC are kept running at full speed.
C2 Stops CPU main internal clocks via hardware. State where the processor maintains all software-visible states, but may take longer to wake up through interrupts.
C3 Stops all CPU internal clocks. The processor does not need to keep its cache coherent, but maintains other states. Some processors have variations of the C3 state that differ in how long it takes to wake the processor through interrupts.
http://doc.opensuse.org/products/draft/SLES/SLES-tuning_sd_draft/cha.tuning.power.html
PLS ONE USER TEST İT
NOT TESTED BY ME
THX x_justin

alimzia said:
Hey thanks a ton bro! I just had a few questions before using the first method to unlock my phones bootloader.
Is this method safe? Has it been tested enough yet? I dont want to use FreeGee again (soft bricked my phone the first time around using it).
If yes, can you please tell the steps to unlock using the 1st method?
Thnks again!
Click to expand...
Click to collapse
you say that u had used freegee??then did u also get ur bootloader of mako?
how did u switch back to stock rom??help me plz...
i need a kdz link for e975 too

I've tested the first method one time without any problem. I highly recommend to use this method rather in play store

yogivin said:
you say that u had used freegee??then did u also get ur bootloader of mako?
how did u switch back to stock rom??help me plz...
i need a kdz link for e975 too
Click to expand...
Click to collapse
Sorry I forgot to mention that was with the at&t version (had that earlier). After it got softbricked by using FreeGee I used teenybin to revive it. Wasn't able to get back into the official rom though. Instead used teenybin to flash recovery (teenybin also unlocks the bootloader in the process) and from there I used a zip file of the official Rom.
I don't know this, Im not entirely sure, but maybe if you can get a zip file (as you do for roms) you can then flash it via recovery. It wont lock back the bootloader ofcourse. Again, I m not sure about it and you best ask a senior member. It did work for me though, on At&t version.
---------- Post added at 07:52 PM ---------- Previous post was at 07:04 PM ----------
yawako said:
I've tested the first method one time without any problem. I highly recommend to use this method rather in play store
Click to expand...
Click to collapse
Can you please lay down the step by step how to unlock bootloader via this method? I do have some idea but don't want to do something stupid and make matters even worse.
Also, I had already tried using FreeGee before i stumbles upon your post. It did nothing, instead during the unlocking process FreeGee force closed. So does that change anything anyhow? I havent even rebooted my phone since then in fear of a possible hard brick
Highly appreciate your replies people!

yogivin said:
BROTHER..i have a LG E975..i unlocked bootloader and now have a mako bootloader installed..its model version is e960 i.e nexus 4..installed kitkat..now i want 2 get back to stock rom..but my model number is changed from e975 to e960..f i try to restock it with lg flash tool it say check phone model..can u plz help me brother ..would be vry thankful to u
Click to expand...
Click to collapse
Edited: to show flash step by step

umar_fiaz said:
Edited: to show flash step by step
Click to expand...
Click to collapse
Can you also add the step by step procedure to unlock bootloader using the first method? As in wether your phone should be in download mode, charge only mode etc etc.

alimzia said:
Can you also add the step by step procedure to unlock bootloader using the first method? As in wether your phone should be in download mode, charge only mode etc etc.
Click to expand...
Click to collapse
enable usb debugging
connect as MTP
follow the script

Hey
Yesterday I flash CM11 over stock 4.1.2 on my Optimus G (E975) and later decided to go back to stock again.
Everything was done witouht problems using nand back up with CWM
But later I realiced that M5 was out and, once again tried to install it but I couldnt
Dont know what happen but now while device is turning on, or trying to go into recovery or dowload mode screen is BLACk.
Device is working properly, I mean I turn it off/on and no problem. Just cant enter fastboot, recovery or download mode.
I tried a couple method to go back to stock using KDZ but proceess stop and nothing, just keep pressing power buttom and phone reboot (just black screen during the process)
Please, any ideas/suggestions
O no please.
I follow method one, I get succes message and now my wifi refuses to turn on. WTF
Update 2:
Now Im screwed. I tried to install another recover with Rom Manager and now phone refuses to turn on.
Something is detected in the pc while conecting it but I have only a black screen
Please what can I do??

ErnestoD said:
Hey
Yesterday I flash CM11 over stock 4.1.2 on my Optimus G (E975) and later decided to go back to stock again.
Everything was done witouht problems using nand back up with CWM
But later I realiced that M5 was out and, once again tried to install it but I couldnt
Dont know what happen but now while device is turning on, or trying to go into recovery or dowload mode screen is BLACk.
Device is working properly, I mean I turn it off/on and no problem. Just cant enter fastboot, recovery or download mode.
I tried a couple method to go back to stock using KDZ but proceess stop and nothing, just keep pressing power buttom and phone reboot (just black screen during the process)
Please, any ideas/suggestions
O no please.
I follow method one, I get succes message and now my wifi refuses to turn on. WTF
Update 2:
Now Im screwed. I tried to install another recover with Rom Manager and now phone refuses to turn on.
Something is detected in the pc while conecting it but I have only a black screen
Please what can I do??
Click to expand...
Click to collapse
have you tried TeenyBin http://forum.xda-developers.com/showthread.php?t=2249500

Yes but I could solve that problem now.
One thing I learned: I will never install a custom rom on my OG. I had several devices before this one and always with custom roms. But with LG there are so many risks and problems to perform needed actions
Thanks
umar_fiaz said:
have you tried TeenyBin http://forum.xda-developers.com/showthread.php?t=2249500
Click to expand...
Click to collapse

ErnestoD said:
Yes but I could solve that problem now.
One thing I learned: I will never install a custom rom on my OG. I had several devices before this one and always with custom roms. But with LG there are so many risks and problems to perform needed actions
Thanks
Click to expand...
Click to collapse
very true. iv learned the lesson too..it was risky to install stock back
its not a cheap phone after all..moreover stock roms are the best ones. u wont get those features n qlides etc in custom

It appears to be that certain functions are sensitive to low power states.
Without downloading the fauxclock app, I took out the SIM from the phone. This allows the phone to work well enough without crashing due to the modem being initialized in a low power state.
Got into performance and set the minimum clock at 1000MHz (for now).
Phone works again.

Recovery mode only
Hello,
I have F180L, I upgraded it to 4.4.2 kitkat then rooted it with freegee and installed cwm via freegee. then booted into recovery and installed Sling 2.2 kitkat. every thing was working great until I factory reset the phone. Now, the phone is stuck in cwm. It starts and boots into cwm . even if I turn off the phone and plug in the power, the phone boots in cwm. it is not even charging because of the led light which is always on in cwm. I have tried everything but nothing is happening ....
someone plz help me and suggest me something to charge and unbrick my phone

Recovery mode only
w8ing for reply...
someone help me please

solution
farhan.ahmed said:
w8ing for reply...
someone help me please
Click to expand...
Click to collapse
1st try to get in download mode..hope u know how to get into download mode.
there is some key combination
vol up+insert cable

yogivin said:
1st try to get in download mode..hope u know how to get into download mode.
there is some key combination
vol up+insert cable
Click to expand...
Click to collapse
I have installed teenybins now I have fastboot and twrp recovery but when i use install zip from sd card, it gives me error E: Can`t mount /sdcard. when i try adb sideload, it show an error can`t read xxx.zip
I need tot and dll files for F180L to try LGNPST
please help me

farhan.ahmed said:
I have installed teenybins now I have fastboot and twrp recovery but when i use install zip from sd card, it gives me error E: Can`t mount /sdcard. when i try adb sideload, it show an error can`t read xxx.zip
I need tot and dll files for F180L to try LGNPST
please help me
Click to expand...
Click to collapse
i dont think there is any need for teenybins n etc
jus try to get into download mode and thn try this link
http://forum.xda-developers.com/showthread.php?p=53659718#post53659718

Root Firmware 18.1.A.1.21

There is a way to root new firmware 18.1.A.1.21 . Tested by myself on my new Xperia T3 (D5103).
Follow the steps below. Credits to him: ( Taken from this post: http://forum.android.com.pl/f1428/root-dla-xperii-t3-456064/ )
1. Install ADB drivers. Follow the steps from this post (Method 1 better): http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/ IMPORTANT: CHECK THAT YOUR PHONE CONNECTS TO PC VIA ADB BEFORE PROCEED TO THE NEXT STEP.
2. With Flashtool, flash the .21 firmware, if you didn't have already flashed.
3. Turn on the phone. Active USB debugging and Install apps from unknown sources.
4. Turn off phone, and flash .14 kernel with flashtool. Download kernel from here: https://drive.google.com/file/d/0B-GorbT9vz2qSlczRHlPWGdKb1U
5. Turn on phone, and connect it to PC via USB. Doesn't matter if phone get stuck in "Updating apps" screen.
6. Download last version of root toolkit by cubeundcube: http://forum.xda-developers.com/showthread.php?t=2559009. With phone connected to PC, launch install.bat from the toolkit. Follow the steps until the phone reboots.
7. Now turn off the phone, and flash again the kernel from .21 firmware: https://drive.google.com/file/d/0B-GorbT9vz2qQm91VU4wWnZvd28
8. Reboot and now you're on .21 firmware and rooted :good:

Nice one..
Is there no one click method...
Im already on 18.1.A.1.21 firmware

Nice tutorial, the only one I've found!

Do I need to exclude TA in flashtool?
thanks.

as u dont unlock the bootloader there is no reason to do so...
also as for now .. can we even backup the TA partition ??
i've red that after relocking bootloader the drm keys are back ...

Confirmed. This method works very well, even if it is not a one-click method. Thank you.

meilbox said:
as u dont unlock the bootloader there is no reason to do so...
also as for now .. can we even backup the TA partition ??
i've red that after relocking bootloader the drm keys are back ...
Click to expand...
Click to collapse
Thanks, I finally did It
Once your phone is rooted, you can backup TA partition, but you have to do it BEFORE you unlock your bootloader. It won't be possible after unlocking it
If you back up your TA partition, then you can relock your bootloader using that backup, like nothing happened.

help
thejosetree said:
There is a way to root new firmware 18.1.A.1.21 . Tested by myself on my new Xperia T3 (D5103).
Follow the steps below. Credits to him: ( Taken from this post: http://forum.android.com.pl/f1428/root-dla-xperii-t3-456064/ )
1. Install ADB drivers. Follow the steps from this post (Method 1 better): http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/ IMPORTANT: CHECK THAT YOUR PHONE CONNECTS TO PC VIA ADB BEFORE PROCEED TO THE NEXT STEP.
2. With Flashtool, flash the .21 firmware, if you didn't have already flashed.
3. Turn on the phone. Active USB debugging and Install apps from unknown sources.
4. Turn off phone, and flash .14 kernel with flashtool. Download kernel from here: https://drive.google.com/file/d/0B-
GorbT9vz2qSlczRHlPWGdKb1U
5. Turn on phone, and connect it to PC via USB. Doesn't matter if phone get stuck in "Updating apps" screen.
6. Download last version of root toolkit by cubeundcube: http://forum.xda-developers.com/showthread.php?t=2559009. With phone connected to PC, launch install.bat from the toolkit. Follow the steps until the phone reboots.
7. Now turn off the phone, and flash again the kernel from .21 firmware: https://drive.google.com/file/d/0B-GorbT9vz2qQm91VU4wWnZvd28
8. Reboot and now you're on .21 firmware and rooted :good:
Click to expand...
Click to collapse
How to unlock the boot I can not flashing with Him Off, already tried bulking up and I can not , please help BY

Anyone ever try to root using towel root?
https://towelroot.com/ (to download apk, click on logo)
(make sure you have active connection when root with towel root)

no work
no work, Alternatively? thanks !

Can someone help me how you do that?. With screenshots or something. What buttons I click on sony xperia t3?

Can't download kernel via the Google drive. Untrusted connection display in browser. Could any one give me aother link? Or pls update the link.

help
ryanxtx said:
Can't download kernel via the Google drive. Untrusted connection display in browser. Could any one give me aother link? Or pls update the link.
Click to expand...
Click to collapse
could make a video of how to use the button up to flash the t3 think not only help me. thank you

To enter flashmode - on your phone turned OFF - hold volume down (-) then connect USB and youll see green led.
@ryanxtx links are working correctly, ive just checked em. Its probably something with your browser/network.

Thank, @horuxan. I've successfully rooted my T3. I just got today. I can't download last two days ago. The important is adb n fastboot driver for T3. It made me a bit headache but I have done now. Thank. ? ?

help
ryanxtx said:
Thank, @horuxan. I've successfully rooted my T3. I just got today. I can't download last two days ago. The important is adb n fastboot driver for T3. It made me a bit headache but I have done now. Thank. ? ?
Click to expand...
Click to collapse
03/036/2015 14:36:42 - ERROR - Processing of loader.sin finished with errors.
03/036/2015 14:36:42 - INFO - Ending flash session
03/036/2015 14:36:42 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80060011";
;/Anyone know what this is?

help
I could now flash the bat does not end and no routes at all takes more than 25 minutes to root?

help
i am be roteed sorry english, how to unlook botloader on linux ? plis

With adb

6. Download last version of root toolkit by cubeundcube: http://forum.xda-developers.com/show....php?t=2559009. With phone connected to PC, launch install.bat from the toolkit. Follow the steps until the phone reboots.
I manage to flash .14 kernel , but when running root toolkit by cubeundcube , just getting errors please can anyone point to the right package? I tried --- CVE-2014-3153 ---
Thanks

Soft/Hard brick when chainfire rooting

Hi there,
Proud owner of a new Pixel XL. Unlocked version. Tried rooting last night (i've rooted all devices i've owned and am not new to this). Followed the instructions to a "t". The device won't get past the white screen and dots leapfrogging each other. Now when going back to fastboot, device isn't recognised by ADB Fastboot etc...
Please help!!!!

My guide should be able to help you get back to the OS and then install root.
Keep in mind you may lose data if you don't remove the -w from the script mentioned in the guide.
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478

Did you unlock bootloader?
Then immediately try rooting?
That is one cause for bouncing dots.
You should: flash factory image, then boot into device before any flashing. Setup device until you are at the home screen and OS settled. Use a pattern or pin security. That is needed to make recovery work properly. You need to decrypt at recovery boot. No ask for pin? Then power off and boot TWRP again.
Follow directions in TWRP and SuperSU threads to a Capital "T"...
Versions:
Latest "Q" firmware
Boot TWRP RC1 img, then flash zip installer
Use SuperSU 2.79 SR1.
You'll have no bootloop. I found first rooted boot to take just a few minutes.
Just in case: update SDK platform tools if you haven't cos that screws people up for days too.

Thanks mate. But i get to step 9 and nothing happens. My device is no longer recognised

thanks mate, but the problem is that now the device is simply not recognised by my computer. I can't flash anything

I should clarify.
SDK is 100% up to date.
I am trying on both Windows 10 and Mac.
Device drivers worked fine prior to trying to root.
I'm really worried that i might have just bricked a $1.4k(aud) device

I unlocked my bootloader and got a bootloop when I tried to fastboot to root. Would not recognize the device either. I redownloaded SU 3 as suggested in the third post and it worked. Good Luck.
I used the fastboot to root method and did not install TWRP.
http://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140

Thanks, Mike01680. trying now

When i go into sideload i can see the device listed on adb devices!

Okay. Booted into recovery, found my firmware for NMF26O. Downloaded and ADB Sideloaded it can once again boot. thanks for all of your help!!!

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

Develop Bugs

welcome