[Q] Root Z2 on 5.1.1 546 - Xperia Z2 Q&A, Help & Troubleshooting

Hello
I have been reading through the threads here but can't seem to find a rooting method for Z2 on 5.1.1 546. Bootloader is unlocked. If this has been discussed somewhere already please kindly point me to the relevant page. Thank you

If you already are on 5.1.1, unrooted, you'll have to either flash a kernel with recovery and then flash superSU(since you bootloader is unlocked) or you'll have to downgrade to 4.4.2, root and install recovery and then make a rootable 5.1.1 zip file and flash it.
Flashable zipfile can be found here: http://forum.xda-developers.com/xperia-z2/general/ftf-cutomized-23-1-0-726-cda-1281-9809-t3082166.

Skanin said:
If you already are on 5.1.1, unrooted, you'll have to either flash a kernel with recovery and then flash superSU(since you bootloader is unlocked) or you'll have to downgrade to 4.4.2, root and install recovery and then make a rootable 5.1.1 zip file and flash it.
Flashable zipfile can be found here: http://forum.xda-developers.com/xperia-z2/general/ftf-cutomized-23-1-0-726-cda-1281-9809-t3082166.
Click to expand...
Click to collapse
Thanks. I will try that. I was hoping I wouldn't need to downgrade though. :good:

Skanin said:
If you already are on 5.1.1, unrooted, you'll have to either flash a kernel with recovery and then flash superSU(since you bootloader is unlocked) or you'll have to downgrade to 4.4.2, root and install recovery and then make a rootable 5.1.1 zip file and flash it.
Flashable zipfile can be found here: http://forum.xda-developers.com/xperia-z2/general/ftf-cutomized-23-1-0-726-cda-1281-9809-t3082166.
Click to expand...
Click to collapse
Hey, sorry to be a bother. My problem is I also can't get into recovery. I have used samsung all my life this is my first non-samsung device so it's vexing me a little. I used fastboot to flash twrp, cwm, philz but each time I can't get into recovery. sometimes I get purple led but it doesn't progress from there. got any ideas?

arsenicas said:
Hey, sorry to be a bother. My problem is I also can't get into recovery. I have used samsung all my life this is my first non-samsung device so it's vexing me a little. I used fastboot to flash twrp, cwm, philz but each time I can't get into recovery. sometimes I get purple led but it doesn't progress from there. got any ideas?
Click to expand...
Click to collapse
You press the volume button down when the purple light shows, right?
Norwegian
Du trykker på volum knappen nedover et par ganger når lyset lyser lilla, ikke sant?

Same for me here. Flashed 5.1 via flashtool and unlocked the bootloader then. But none of the recoverys boot. And no purple light either.
Worked this Morning, when i was on 5.0

go download twrp from their site
go into fastboot mode
fastboot flash recovery [twrp recovery image name].img
Now you should be able to access recovery by pressing vol up multiple times on boot (if it doesn't work, try vol down, or the power button) , you won't see any purple light as that is related to Androplus kernel I think

Skanin said:
You press the volume button down when the purple light shows, right?
Norwegian
Du trykker på volum knappen nedover et par ganger når lyset lyser lilla, ikke sant?
Click to expand...
Click to collapse
Yes I keep pressing the button. it shows the screen is on because you can see the backlight but nothing on display

ticktock666 said:
go download twrp from their site
go into fastboot mode
fastboot flash recovery [twrp recovery image name].img
Now you should be able to access recovery by pressing vol up multiple times on boot (if it doesn't work, try vol down, or the power button) , you won't see any purple light as that is related to Androplus kernel I think
Click to expand...
Click to collapse
for me twrp is the most unresponsive of all the recoveries I tried. it gets stuck on the Sony start up screen

Just an update on my case, I have had a breakthrough (somewhat) with recovery. I flashed extracted the boot.img from the kernel on this post http://forum.xda-developers.com/xperia-z2/development/kernel-andropluskernel-v10-t2974841 and fastboot flashed it as per instructions on the post. I was then able to boot into twrp but couldn't boot into the system due to bootloop. tried to flash a pre tooted stock zip didn't work either so I had to flash CM12. Since I had always wanted to try cm12 I can do so while I'm still trying to find my way back to stock lol. Root works now though, which way my major issue.

Hi, is there a way to root for locked bl?

JonnyZaggi said:
Same for me here. Flashed 5.1 via flashtool and unlocked the bootloader then. But none of the recoverys boot. And no purple light either.
Worked this Morning, when i was on 5.0
Click to expand...
Click to collapse
U need a custom kernel from 5.0.2 then flash recovery. Turn on ur phone and when u see the led colour press volume down

I had a locked bootloader and 5.1.1 on my Xperia Z2. I downloaded an original firmware 5.0.2, flashed it with FlashTools and then applied root without any problem. Also I installed a recovery, so I can now enter by keeping pressed vol-down from first vibration on start until it vibrates many times.

can you please tell me how did you come back to 5.0.2 because whenever i am flashing 5.0.2 my cell phone stuck in booting screen and restarting

Related

help me please!!.. LG g2 mini D618 stuck in TWRP interface

so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
dibik said:
so.. i have an Lg d618 rooted and running official L 5.0.2
i wanted to flash a custom recovery so i started with patching bootloader using this thread
http://forum.xda-developers.com/g2-mini/development/bootloader-d620-d618-t3127819
then i installed TWRP using this thread
http://forum.xda-developers.com/g2-mini/development/recovery-lg-g2-mini-d618-v10c-t2854493
by flashing the img file with Flashify
the the phone rebooted and i got the TWRP interface
http://img.wonderhowto.com/img/39/2...only-custom-recovery-youll-ever-need.w654.jpg
and when i press reboot i got this
http://img.wonderhowto.com/img/38/1...only-custom-recovery-youll-ever-need.w654.jpg
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I got that android logo like i have no recovery installed
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
i tried this solution http://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/ and it didn't help
Click to expand...
Click to collapse
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
OfficerJimLahey said:
Followed you from the other spot...
It sounds like Flashify plunked recovery on your boot/kernel partition (assuming your recovery you described is still stock - that is - Andy laying down with the front panel open). So, I would suggest to ADB push your official L 5.0.2 boot.img while in TWRP and flash that (to boot), and you should be golden.
Also, from my perspective it's hard for me to say your bootloader is acting up, as I have a different LG device and it's bootloader does not have fastboot. It's front-end is only a shim that makes you factory reset to get into recovery mode (it's only function).
Hope this helps.
Click to expand...
Click to collapse
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
dibik said:
thank you Jim for the reply
well my problem is solved.. i just flashed my device with the Official KDZ file using LG flash tool in "normal flash mode not CSE"
my phone turned on normally and everything (apps, pictures, files, messages.... ) and all my data were still there so i did'nt loose a thing
i just lost the root acces and that won't be a prblm cause i can root it all over again
thanks again Jim ^^
Click to expand...
Click to collapse
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
ShadowBlade_20 said:
Did you still have TWRP installed after flashing the KDZ file normal mode? Is your bootloader still unlocked?
Click to expand...
Click to collapse
no i didn't
i re-unlocked the bootloader and installed TWRP 2.8.7.0 and it worked like a charm and now i'm on CM 13
Having sanw problem. Been stuck here on att lg gflex for 3 months. Can u help me please? [email protected]
Sent from my C6740N using Tapatalk

Z5C won't boot after kernel & recovery flash

Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
MatMew said:
Hi guys,
Just unlocked my bootloader and began the root process.
I followed part of this guide but without backing up my DRM keys. http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
I flashed my kernel and the recovery O.K.
fastboot flash recovery recovery.img
flashboot flash boot boot.img
I've tried two versions of TWRP and two different versions of the kernel AndroPlus.
When performing fastboot reboot after flashing both files my phones LED blinks RED once and then does nothing.
Dramatic and scary. What can I do to fix this? When trying to boot without the cable in my phone just vibrates once and does nothing. Screen doesn't light up at all. I'm so worried.
Click to expand...
Click to collapse
did you try to flash first the boot.img and after the recovery ?
acabreram said:
did you try to flash first the boot.img and after the recovery ?
Click to expand...
Click to collapse
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
MatMew said:
I've tried another kernel and it's booting but hanging at the three dots. (bootscreen) been waiting a few minutes. hopefully it gets to system.
Click to expand...
Click to collapse
Ok yo can try this too
Y tried and working fine root & xposed
It's tus stock kernel but with the habilita to support root
Similar issue for me
I've had almost exactly the same issue today:
- I unlocked boatloader using Sony standard process
- I followed the steps under 'How to Install CM13' within CTXz's guide here
- After flashing the Kernel and THEN the TWRP, I reboot and the phone flashes red LED, then green, then off, then red and then stays on green for a while (screen is blank). My computer registers that there is a new connection by making a sound but doesn't show up any devices that I can see.
- Periodically, I get the device disconnection sound and the green LED goes off, then red comes on, then solid green again until next cycle.
- If I disconnect the cable, the LED goes off. When I try to turn the phone on without cable attached, it buzzes but does nothing - no LEDs. I can't tell whether it is on or not, except that doing hard reset with PWR+Vol.Up gives no reaction.
- When I re-attach cable normally, the red/green LED sequence starts immediately with no need to turn PWR on, which would suggest that the phone is perhaps on.
- I am able to get into bootloader as normal and fastboot registers the device just fine.
- There is no yellow LED
I started with Kernel AndroPlus v24 and TWRP 3.0.0.0.
Failing that, I tried Kernel v20. Then I tried AndroPlus' twrp-2.8.7.0-E5823-32.0.A.6.152.
Have also tried Kernels v20 and v21 with TWRP 3.0.0.0.
I haven't had any fast boot errors - all flashes come back 'OKAY'.
I'd be very grateful for any help? Have I missed something?!
update to my post above:
I used: 'fastboot boot recovery.img' and this fired up the Sony logo with white screen and blue LED. However, after 10 mins of waiting, there was no change in status and I still couldn't get into TWRP with pressing Vol buttons, even after several restarts and unplugging, replugging etc.
Then, I realised the stock ROM on my phone before this whole process was Lollipop 5.1.1 Build 32.0.A.6.200. So, I flashed older versions of the Kernel and TWRP. Now, I can boot into the ROM and use the phone (almost) as normal except, being plugged in, it keeps re-detecting the USB cable. I now also get the Sony boot screen followed by yellow LED.
If I don't touch anything, it boots into the ROM. However, if I press a Vol button while the yellow LED is on during boot, then it just resets.
Thus, I still cannot get into the TWRP interface. Perhaps I need a TWRP version that is specific to my build - the one I have is from AndroPlus website and refers to the previous build (twrp-2.8.7.0-E5823-32.0.A.6.152.img)?
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
robledog said:
okay, further update (to save someone replying!)
I managed to boot into the system using AndroPlus Kernel v05a (I had Lollipop build ###.200), but still couldn't get into any TWRP.
I then followed the general process explained in this thread, albeit had to do a heck of a lot of research to understand the detail that is omitted from that (otherwise very useful and concise) original post. For example:
- how to actually use Flashtool (installing drivers and then getting hold of the right firmware from within the program);
- the difference between Fastboot and Flashmode;
- having to plug in the phone while it is loaded into the system before then flashing the selected firmware with Flashtool and ONLY THEN unplugging, switching off and booting into Flashmode.
- loading up the system after flashing the Kernel and TWRP so that I connect to computer and re-copy the erased SuperSU .zip file back onto storage, and then re-booting into TWRP and how to flash a zip file with TWRP.
Having now got a stock Marshmallow firmware rooted, my next step is to go back to the original guide I was following and try to install Cyanogen!
Thank you to all the people who have posted help guides throughout this site so that I could piece together what I needed to do - even though it has still taken me about 30 hours of my life to learn all this!
Hopefully my experience might help someone else in due course...
Click to expand...
Click to collapse
I had the same problem and solution is as is written here.
I had to flash Stock Firmware Marshmallow via Flashtool. After this I flashed kernel(boot) and recovery without problems and yellow icon will displayed.
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
IGNNE said:
Don't want to warm up this kind of old thread, but I have exactly the same issue (E8523). Would any of you mind to post their (stock) ROM versions which finally worked? I tried almost every combination that came to my mind (Customized CE1 32.2.A.0.224 => v31, several LP versions => more or less 20 to 32...).
Currently after installing the MM I mentioned the stock kernel worked, but when I flash the AndroPlus kernel (fastboot flash boot /path/to/boot.img) it won't boot up, black screen, looks like no dtb found (doesn't even try to load). This is also the message I get when I try to boot this img via fastboot directly.
I am sure I am missing something really stupid (quite new to android devices), but what?
Click to expand...
Click to collapse
Pro tip: hold shift and right click inside folder with recover.IMG or voot.IMG to open command prompt from that folder. Then all you have to do is type fastboot flash boot boot.IMG. I suggest trying to put a custom recovery like twrp on and flashing the xpower ROM from that, it will give you everything in one package.
Edit: fwiw I'm pretty sure custom recoveries have been able to flash .IMG fils for a few years now but I've never actually tried it. Might be worth a shot.
Thanks, but I haven't found cmd.exe on my linux machine yet^^ (I suppose wineconsole is cheating )
I know how to flash *stuff* to my phone, but that *stuff* seems only to work if some specific version of stock rom was installed previously. My best guess is the bootloader changes and supports different dtb formats on every version.
Stock Marshmallow 6.0.1 Customized CE1 32.2.A.0.224 does _not_ work for installing any version of AndroPlus kernel (tried a few...). It fails at boot (does not even load system, probably dtb).
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Thanks for sharing the information in this tread, it really helped me to unbrick my phone!
I started with Lollipop on my brand new Z3C and tried to root using AndroPlusKernel v31 / TWRP 3.0. This resulted in a softbick state, only being able to boot in fastboot mode.
After many hours struggling, an upgrade to stock Marshmallow (E5823_32.2.A.0.224) did the trick. This somehow seems ta make the device ready for the new kernel and recovery (I guess it has to do with the partitions in the filesystem).
Anyway, from stock Marshmallow I could start all over and succeeded to flash a custom bootloader, recovery and now have the ability to flash any desired rom! Thanks again.
To updrade to stock MM I used the instructions in this thread:
[GUIDE][18th Dec][4Noobs] Flashing A FTF File Using Flashtool
To set up TWRP recovery I used the instructions in this thread:
[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [ALPHA]
The stock rom I used for my E5823 is "E5823_32.2.A.0.224_R1C_CIS Generic_1298-5167.ftf" from xperiablog.net
Since I'm a new registered member I can't post external links
Google it and you're set!
IGNNE said:
Just in case someone might run into similar issues: What finally worked was Stock MM 6.0.1 Customized DE 32.2.A.0.224 with AndroPlus v31. It seems to be some older release (?), it says R2C instead of R9C for Customized CE1.
I could not find this information anywhere on the net (maybe its me), so for those with a slow internet connection the above version should work. You don't have to actually boot it, flashing is enough.
Click to expand...
Click to collapse
I'm having the same problem, where did you get that MM stock version from?
And what do you mean by "you don't have to actually boot it"?
Search for XperiaFirm and Flashtool. There is plenty.
You don't have to start your freshly installed Stock Rom version "...". You just have to flash it (write it to your phone) Now you boot your phone in fastboot mode and flash your custom kernel and mod rom of your choice. Seems to be some incompatible whatever between not matching kernel versions and the "stuff" flashing installs (suspect sth like bootloader, but no idea).
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
---------- Post added at 11:05 AM ---------- Previous post was at 10:54 AM ----------
starchild78 said:
I have flased boot.img nd recovery.img on android 7.1.1 z5 compact my phone won't pass the sony logo
any help ?
Click to expand...
Click to collapse
I've just discovered I can boot into twrp
anything I can do to fix this from there ?

Need Help - Stuck

Hey guys, I'm facing an issue right now.
I had a rooted OPX with TWRP and Lolipop. I downloaded the new OOS 3.1.3 from OnePlus site, flashed it. There was an error, fixed it by updating updater-script. Flashed the zip, then just after that flashed SuperSU zip and TWRP image over recovery. I don't know why I did that but that's the order. Then I forgot to wipe Dalvik/Cache and rebooted into recovery...It stuck in OnePlus Logo screen with powered by android written at bottom. Then I tried to boot into System by pressing the power button, it got stuck in the boot animation (The new one in Marshmallow update). It just keeps rotating infinitely (I think). I have waited for about 30 minutes on that screen, no luck.
What should I do? Is there a way that fastboot mode would be recognized by my PC and I can boot into recovery via image? Or any way for factory reset? Data is all backed up, so no issue about that. Just need it to get running asap.
Please reply asap.
Thanks for reading.
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Joshwin Aranha said:
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Click to expand...
Click to collapse
Just as I mentioned, booting into recovery doesn't work. Stuck at the OnePlus Logo Screen if I do that manually.
Though I can boot into fastboot. But after doing that, when I connect the phone to the PC, fastboot devices command returns an empty line.
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Exodusche said:
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Click to expand...
Click to collapse
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
choubeyaakash77 said:
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
Click to expand...
Click to collapse
You have to use the modded SuperSU. You can find it in the many guides posted for oos3.

Z ultra nougat root

Hi dudes. I have question. Is possible to have root on nougat on togari ( z ultra ) ? If IT is, van someone explain me, how to do IT ? Or give some link for tutorial.
I have the same situation with recovery.
Have Nougat AOiSP 7.1.1
Thanks for respond
FranekOz said:
Hi dudes. I have question. Is possible to have root on nougat on togari ( z ultra ) ? If IT is, van someone explain me, how to do IT ? Or give some link for tutorial.
I have the same situation with recovery.
Have Nougat AOiSP 7.1.1
Thanks for respond
Click to expand...
Click to collapse
If you have AOSiP 5.6 Nougat I think you should already have root access with SuperSU, look for it in settings, if not, having a custom rom you should have a recovery, reboot to recovery and flash SuperSU.zip from the following link
https://download.chainfire.eu/696/supersu/
Good luck mate!
Sent from my Xperia+Z+Ultra using Tapatalk
Oh dude, thanks for answering
But there is problem. I havent any option with "root" in name. And after install rom i losted my recovery. After this i installed cm recovery img by flashtool ( twrp image in flashtool bricking my bootloader). So when i flashed.... I have purple led. And okay... But when i going to recovery LED is correctly Orange. And after this phone screen is turning off and after few seconds going to normal system booting. For sure i have C6833. What i can do ? Im doing something wrong ?
Ok, I think you should flash TWRP 3.0.x directly to the new /recovery partition via fastboot:
fastboot erase recovery
fastboot flash recovery recovery.img
Here's a link to the full thread with detailed instructions and links to download the .img file you'll need, this way you'll never loose recovery again
https://forum.xda-developers.com/showthread.php?t=3307043
Then if successful you should be able to boot to your new recovery and flash SuperSU.
If you were to fail to get recovery with that method you might have a different problem, try the above, if it doesn't work I'll help. There's a chance your recovery partition wasn't created correctly....
Sent from my Xperia+Z+Ultra using Tapatalk
Okay ill gry tomorrow. There is starting to be late. And i will informate You. Thanks You realny much
Hi!
After flashing that twrp 3 you linked, I still can not enter to recovery.
Power button, wait for purple, push vol down purple changes to weird lightbrown, than nothing.
before cm was working, than I was put a dual rom there, which wasn't able if I remember correctly to flash that nougat, so i flashed it from fastboot. From there I'm not able to enter recovery.
Also that link says "To use, make sure you have installed the new bootloader by flashing the latest stock Sony ROM at least once."
So it could be a problem? I don't know which one was the last stock Sony ROM it, I was bought it used, and w/o thinking I was put cm on it.
pictogram said:
Hi!
After flashing that twrp 3 you linked, I still can not enter to recovery.
Power button, wait for purple, push vol down purple changes to weird lightbrown, than nothing.
before cm was working, than I was put a dual rom there, which wasn't able if I remember correctly to flash that nougat, so i flashed it from fastboot. From there I'm not able to enter recovery.
Also that link says "To use, make sure you have installed the new bootloader by flashing the latest stock Sony ROM at least once."
So it could be a problem? I don't know which one was the last stock Sony ROM it, I was bought it used, and w/o thinking I was put cm on it.
Click to expand...
Click to collapse
You seeing the led going purple and all colors shows you are on an old stock rom.
Flash the latest firmware with Flashtool: http://www.flashtool.net/downloads.php
And try again.
I need stock 5.1 lp for flash recovery ? Damn....
Ok I did it. No purple light now.
But now I don't know how to enter recovery.
Stock sony 5.1.1 is on. Tried to get in recovery, but just boots.
Flashed twrp 3.0 still don't know how to get in.
I thought to install XZDualRecovery https://forum.xda-developers.com/showthread.php?t=2647492 because it says how to enter into it, but im not sure i can flash it via fastboot.
heeeelp!
edit:
adb reboot recovery just simply restarts back to android... ? O.O
eddit:
never mind, it works now
To enter recovery:
* Switch off the phone
* Hold Vol-Down & Power button simultaneously until the phone vibrates
* Release the power button and keep holding Vol-Down until the Sony logo appears
Sent from my Xperia+Z+Ultra using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:10 PM ----------
FranekOz said:
I need stock 5.1 lp for flash recovery ? Damn....
Click to expand...
Click to collapse
You don't actually need it, if you had latest Sony stock at least once then the new bootloader would have been installed, and new /recovery partition created.
If you read and followed AOSiP installation instructions correctly, you should have been aware that having had lollipop installed in your phone was also needed for any Marshmallow or Nougat Rom to work, since your AOSiP worked that should've been the case.
Did you try flashing TWRP 3.0.x via fastboot?
Sent from my Xperia+Z+Ultra using Tapatalk
9crack said:
To enter recovery:
* Switch off the phone
* Hold Vol-Down & Power button simultaneously until the phone vibrates
* Release the power button and keep holding Vol-Down until the Sony logo appears
Sent from my Xperia+Z+Ultra using Tapatalk
---------- Post added at 06:26 PM ---------- Previous post was at 06:10 PM ----------
You don't actually need it, if you had latest Sony stock at least once then the new bootloader would have been installed, and new /recovery partition created.
If you read and followed AOSiP installation instructions correctly, you should have been aware that having had lollipop installed in your phone was also needed for any Marshmallow or Nougat Rom to work, since your AOSiP worked that should've been the case.
Did you try flashing TWRP 3.0.x via fastboot?
Sent from my Xperia+Z+Ultra using Tapatalk
Click to expand...
Click to collapse
Yeah, now recovery working. But i installed supersu next to get in recovery, witthout checking than my rom working correctly. And now i have issue with AOSiP logo... Its stuck ( i had that before in diffrent roms).or recovery. So i will try to take my system wipe....
You're almost there man, you now have a decent recovery, now as you said just do a full wipe, flash rom, gapps and SuperSU, reboot and see if it's working the way you like, write any findings or whatever at your rom's thread, good luck bro.
Sent from my Xperia+Z+Ultra using Tapatalk
9crack said:
To enter recovery:
* Switch off the phone
* Hold Vol-Down & Power button simultaneously until the phone vibrates
* Release the power button and keep holding Vol-Down until the Sony logo appears
Click to expand...
Click to collapse
If I do that nothing happens.
The purple light come back to me, so i'm waiting for that, and when it appears, i press the vol-up and twrp comes in. Though it freezes out, if i press vol-down when the purple light is comeing, or when i press restart in twrp. Black nothingness in both cases.
I think the purple light at boot come back when I flashed nougat boot, system and userdata. I don't really understand. Firmware is a different thing right? It is not on the partitions.
I probably will put another nougat on it, this: https://forum.xda-developers.com/xp...elopment-cm14-android-7-0-freexperia-t3457377
instead of this one: https://forum.xda-developers.com/xperia-z-ultra/development/android-n-t3452954
I will hope it doesn't freeze inside the os.
edit: ohh its freezeng out there too: https://forum.xda-developers.com/showpost.php?p=68603461&postcount=17
eddit: your method also works i tried it again now. when i was powering off the phone it was freezed out. (but i thought it is off) so had to push that reset button.
Whenever your phone needs a restart, (i.e. something happened and it seems frozen...) you don't have to use the little red reset button, you can get the same result by holding Power button + Vol-up until it vibrates, that'll switch it off just like the reset button, then you can just turn it back on normally to boot to your rom or boot to recovery.

Help hard bricked

Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
The Game 370 said:
Hi Friends i flashed miui firmware by stinx when i was on lineage rom to update the rom without any error.Then after flashed no mi logo no recovery no fastboot tooo Anyone pls tell solution for this to recover my device back
Click to expand...
Click to collapse
Are you able to see led blinking as red when you connect it to PC?
gulshanstrider said:
Are you able to see led blinking as red when you connect it to PC?
Click to expand...
Click to collapse
Yes but pc is not recognising
The Game 370 said:
Yes but pc is not recognising
Click to expand...
Click to collapse
Go to device manager and tell which Port it Is connected on ?
900E or 9008
gulshanstrider said:
Go to device manager and tell which Port it Is connected on ?
900E or 9008
Click to expand...
Click to collapse
Hi its not showing anything sorry if i am wrong
Do you have MiFlash tool ?
gulshanstrider said:
Do you have MiFlash tool ?
Click to expand...
Click to collapse
YES
The Game 370 said:
YES
Click to expand...
Click to collapse
Check if it is getting listed there.
If not try test point method
gulshanstrider said:
Check if it is getting listed there.
If not try test point method
Click to expand...
Click to collapse
No its not showing my device
The Game 370 said:
No its not showing my device
Click to expand...
Click to collapse
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Same with me
Try accessing fastboot, then reunlock your bootloader
Simoom Sadik said:
what is the current state of yr phone?
tell in details.
is it charging?
is mi logo appears when power button is pressed?
did u try pressing "vol down+power button"?
and what exactly did u do before the phone was dead?
any error occured during flashing?
Click to expand...
Click to collapse
No mi logo,no fastboot,no recovewry nd not charging too
Only red light blinking when connected to usb
I was on lineage rom nd tried to update that rom nd flashed miui 7.5.4 firmware by the stinx to get rid of error while flashing newer build of lineage rom
auliamaster74 said:
Same with me
Try accessing fastboot, then reunlock your bootloader
Click to expand...
Click to collapse
I am unable to access fastboot
The Game 370 said:
I am unable to access fastboot
Click to expand...
Click to collapse
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
auliamaster74 said:
try pressing power + vol down untill it boots into fastboot
at first, I thought I can't access fastboot, turns out I could
try it
Click to expand...
Click to collapse
Thanks i tried deep flash cable method but it didnt worked nd tried test point method Finally it worked
Also Fixed,but FW Flash is a problem
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Edmundajw said:
HI,
I just wanted to comment on this, in the hope that some more experienced member, or even TheStrix would see it.
I've had the exact same problem over the last few days, but have been able to fix it each time by reflashing recovery from miFlash in edl mode;
Flashing the firmware from TheStrix (Latest, kenzo) without fail, bricks the Redmi Note 3, only being able to get to FastBoot. I'm able to switch to EDL on the PC with that batch file that's floating about, and flash recovery through miflash. I've been on LineageOS14 for the past few weeks, but my phones been barely usable with lag. Switched to AOSPX the other day by first flashing the FW;
1. Reboot to recovery
2. Backups
3. Wipe everything except for sd
4. Flash FW
5. Flash AOSPEx
6. Flash Gapps
7. Clear Cache
8. Reboot
That was the first time, and brick... as described above, back to recovery- tried missing out GAPPS- same result..
I went through a few different combinaitons, so have gotten quite used to the EDL mode miFlash...
Back through EDL.. flash recovery.. JUST AOSPEx, booted fine. Setup, etc, back to recovery, GAPPS, reboot, setups, etc.All working good- Except no power button
So I once again went back to recovery and flashed just the FW (Fully expecting it might fail)- Sure enough.. BRICK... So just, I've gone back through the miFlash, installed recovery, but then just decided to try rebooting from recovery into my existing AOSPEx- All works fine- Even the power button now- Was that fixed by the FW? And the bigger thing I'm wondering, since everytime I've flashed the FW it's resulted in a brick-does that mean the FW's not working? When I re flash the recovery, am I back to original FW?
Am I now on the new FW?
Only other thing is I don't have root... I'll see if I can find a supersu to flash, I guess.
So tl;dr- I'm all up and working- but flashing the latest FW form TheStrix appears to brick the Note 3 every time. I can only get a rom to install by NOT first flashing the FW. Flashing the FW after a rom still bricks. And I don't know if it is actually flashed with the new fw after re-installing recovery.
Edd.
Click to expand...
Click to collapse
It's because you haven't unlocked officially. TheStrix's firmware contains MM bootloader which relocks your bootloader if you're in LP bootloader(which is your bootloader if you've unlocked unofficially). If you've already unlocked officially then flash the latest MIUI dev ROM(which relocks your bootloader) then unlock again, TheStrix's firmware will now work.
Or you can just unzip the Firmware then remove emmc_appsboot.mbn(MM bootloader) then rezip it again. You'd still get problems flashing the latest LineageOS Roms if you don't update your bootloader though. So my advice is unlock officially.
Try This guide http://en.miui.com/thread-235865-1-1.html and this guide make a deep flash cable and download the latest fastboot rom and follow the first link http://en.miui.com/thread-380827-1-1.html

Categories

Resources