Related
So I got my Z1 yesterday, was on 4.4.2 stock unrooted. I unlocked the bootloader using Sony's official website and fastboot, then I went on destroying the phone by flashing Philz touch recovery.img through fastboot.
And since then the phone has been bricked, I can only enter Fastboot through the blue led, while Flash mode doesn't show up any LED light and my PC sees the phone when on flashmode as n "S1 device with a parameter error".
I've tried all drivers, none worked, and the flashtool keeps suggesting I should update my drivers when connecting the phone on flash mode:
02/042/2014 22:42:11 - INFO - Device connected in flash mode
02/042/2014 22:42:30 - ERROR - Drivers need to be installed for connected device.
02/042/2014 22:42:30 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Is there any way I can recover from this through fastboot instead of the flashtool? I can still flash system.img and recovery.img through fastboot. I'd really appreciate any help right now.
Abu-7abash said:
So I got my Z1 yesterday, was on 4.4.2 stock unrooted. I unlocked the bootloader using Sony's official website and fastboot, then I went on destroying the phone by flashing Philz touch recovery.img through fastboot.
And since then the phone has been bricked, I can only enter Fastboot through the blue led, while Flash mode doesn't show up any LED light and my PC sees the phone when on flashmode as n "S1 device with a parameter error".
I've tried all drivers, none worked, and the flashtool keeps suggesting I should update my drivers when connecting the phone on flash mode:
Is there any way I can recover from this through fastboot instead of the flashtool? I can still flash system.img and recovery.img through fastboot. I'd really appreciate any help right now.
Click to expand...
Click to collapse
Xperia phones do not have a recovery partition to flash recovery to via fastboot.
If you can enter fastboot, then flash a stock kernel.elf with flashtool (In fastboot mode).
Then you can use flashtool to relock your boot (I imagine you have not even taken a TA backup and you are new to xperia devices, your post suggests so)
then you should be able to use pccompanion to repair, or flashtool to flash a FTF
However, by flashing a recovery image you may have bricked the phone. try what I have said, if it does not work get back in touch. (Do you have access to jtag and setool?)
gregbradley said:
Xperia phones do not have a recovery partition to flash recovery to via fastboot.
If you can enter fastboot, then flash a stock kernel.elf with flashtool (In fastboot mode).
Then you can use flashtool to relock your boot (I imagine you have not even taken a TA backup and you are new to xperia devices, your post suggests so)
then you should be able to use pccompanion to repair, or flashtool to flash a FTF
However, by flashing a recovery image you may have bricked the phone. try what I have said, if it does not work get back in touch. (Do you have access to jtag and setool?)
Click to expand...
Click to collapse
Can you link me to the files you suggested I try? There seems to be a truckload of them laying around the forum.
Also, yes, I am new to xperia phones. Didnt think they were this complicated to flash but I shouldnt have played with fastboot anyway. And no, sadly I dont have a jtag. Never needed one before.
Thanks for the help btw, I greatly appreciate this.
i dont think you have 100% installed the drivers, on windows 7 upwards you need to disable driver signature to allow any unsigned drivers to be installed
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, but how do I extract it from the TFT file?
gregbradley said:
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C6903_14.3.A.0.757_Global 1277-2880.ftf
Is this 4.4.2?
Ok here is an update; after messing with fastboot for so long and a couple of kernel flashes, I managed to boot the phone But now its stuck on the Sony logo.
A sign of hope though lies with the fact that I managed to enter recovery mode and found CWM hanging there. So now Im probably going to try ADB push a rom file to the SD and try to flash it through recovery instead.
@gregbradley
Sounds good. The reason forth hang at the sony logo will be that you have wiped the system partition. Flashing a rom based on the kernel you have will enable the phone to boot
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Sounds good. The reason forth hang at the sony logo will be that you have wiped the system partition. Flashing a rom based on the kernel you have will enable the phone to boot
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Abu-7abash said:
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Click to expand...
Click to collapse
first flash original stock rom, than root your phone and install dualrecovery... and if u relock your bootloader unlock it again... don't try custom rom before this steps
Abu-7abash said:
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Click to expand...
Click to collapse
Yes, as long as the .zip contains a kernel, or id based on the same kernel you have installed now
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Click to expand...
Click to collapse
Yes, if you have an unlocked bootloader
gregbradley said:
Yes, as long as the .zip contains a kernel, or id based on the same kernel you have installed nowYes, if you have an unlocked bootloader
Click to expand...
Click to collapse
Alright thanks, gonna give it a go once im home. And yes, I already unlocked the bootloader through Sony's website and fastboot before this happened.
Vuja1 said:
first flash original stock rom, than root your phone and install dualrecovery... and if u relock your bootloader unlock it again... don't try custom rom before this steps
Click to expand...
Click to collapse
It already has the dual recovery on it but for some reason its stuck in a bootloop.
Abu-7abash said:
It already has the dual recovery on it but for some reason its stuck in a bootloop.
Click to expand...
Click to collapse
do u have any rom on it or u just have bootloop? i u can't access to rom, u need with flashtool to flash stock rom, when u do that u loose your root and lose your dualrecovery... u need to root it again and install dualrecovery
second is
if u can access to rom instal ndr utility and reboot in clockwork mod recovery...
third option si to install via fastboot advanced doomloader kernel which has clockwork mod and has root... after that to flash custom rom but stock version of custom rom
Any of you guys know of a Stock rooted 4.4.4 rom that comes with the stock kernel in a flashable zip? I have looked everywhere for one but I cant find any.
@gregbradley @Vuja1
Abu-7abash said:
Any of you guys know of a Stock rooted 4.4.4 rom that comes with the stock kernel in a flashable zip? I have looked everywhere for one but I cant find any.
@gregbradley @Vuja1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2761614
try this one
Vuja1 said:
http://forum.xda-developers.com/showthread.php?t=2761614
try this one
Click to expand...
Click to collapse
Already did, not really what Im looking for. I want the stock rom but only rooted and in a flashable zip, can't believe there aint any around.
Abu-7abash said:
Already did, not really what Im looking for. I want the stock rom but only rooted and in a flashable zip, can't believe there aint any around.
Click to expand...
Click to collapse
I can think of at least 3 in the development section off the top of my head...
gregbradley said:
I can think of at least 3 in the development section off the top of my head...
Click to expand...
Click to collapse
You can? Link me Greg..link me
So today I embarked on what seemed to be a fruitless journey as I tried to root the Infinix Hot 2 on the latest build (December Security Patch of course) and I observed the following:
1. Flashing TWRP Recovery that was previously made for this device doesn't Flash. SP/Infinix Flash Tool flashes the recovery quite alright but booting to recovery with ADB afterwards gives a "No command" screen.
2. Kingroot (PC & Mobile) can't root this device as of yet :'(
3. I think the bootloader can be unlocked using the Android One Toolkit that was created for 1st Gen Android One devices. Reason being the fact it booted to fastboot and prompted me with the option to accept bootloader unlock or not.
Should you come come successful with flashing recovery or rooting this latest build, please comment your method. Thank you...
Link to Android One Toolkit:
http://forum.xda-developers.com/crossdevice-dev/android-one-general/toolbox-android-one-toolkit-one-click-t3030165
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
sabcpj said:
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
Click to expand...
Click to collapse
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
iAmWiz said:
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
Click to expand...
Click to collapse
yes, you should be. and you need to
Alright then
sabcpj said:
yes, you should be. and you need to
Click to expand...
Click to collapse
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
iAmWiz said:
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
Click to expand...
Click to collapse
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
sabcpj said:
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
Click to expand...
Click to collapse
Alright. If I cannot get a workaround on this, I'll just Flash Infinix 5.1 ROM and wait till M
Try using towel root
https://towelroot.com/
Mysteryagr said:
Try using towel root
https://towelroot.com/
Click to expand...
Click to collapse
Thanks but towelroot didn't work out.
Root achieved... More at
http://forum.xda-developers.com/hot-2/development/root-recovery-xposed-successfully-t3276420
please can you help me sp flashtool stuck at 0 and nothing happens
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Ok now I have the corrupt device message back again.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Droidphilev said:
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Click to expand...
Click to collapse
I need a lot of help installing the drivers.
Sent from my HTC6600LVW using Tapatalk
Like I said I now have the corrupt device message back instead of the 6.0.1 boot logo. I tried flashing the stock img file and the stupid corrupt screen came back. Ok I'm just craps out luck I guess,
Sent from my HTC6600LVW using Tapatalk
Ok I have what says is the latest Google usb drivers which was Aug 2015 downloaded. On my device I'm using I'm gonna transfers the drivers to my pc now, and attempt to install them. I hope this works and fixes my device. I sat in front of my pc yesterday for 7 hrs trying to fix this stupid phone.
Sent from my HTC6600LVW using Tapatalk
the corrupt device message is only there because you have twrp and a stock kernel. flash a custom kernel.
It's fixed, everything is running as it should no boot loops or corrupt screen, now I gotta check to see if recovery is gone. I used wugs to flash stock 6.0.1
Sent from my HTC6600LVW using Tapatalk
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Tower1972 said:
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Click to expand...
Click to collapse
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
flash twrp then when you root, flash a custom kernel as well, that will get rid of the message.
Anybody here?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
Anybody here?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
me. well not here, but in nyc. here in spirit though
simms22 said:
me. well not here, but in nyc. here in spirit though
Click to expand...
Click to collapse
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
simms22 said:
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
Click to expand...
Click to collapse
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
simms22 said:
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
Click to expand...
Click to collapse
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
just download the factory image, then grab the boot.img out of it. link to the 6.0.1 factory image https://dl.google.com/dl/android/aosp/shamu-mmb29k-factory-9a76896b.tgz
simms22 said:
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
Click to expand...
Click to collapse
Ok, with no twrp recover when I boot into boot loader mode and then boot into recovery mode what should I see come up on the screen?
Sent from my HTC6600LVW using Tapatalk
Please help me
Download the latest Superuser Zip and flash it using TWRP Recovery (Unlocked bootloader is required for rooting)
[email protected] said:
Download the latest Superuser Zip and flash it using TWRP Recovery (Unlocked bootloader is required for rooting)
Click to expand...
Click to collapse
Is there any way to flash it via flashtool?
My bootloader is unlocked.
Holydao said:
Is there any way to flash it via flashtool?
My bootloader is unlocked.
Click to expand...
Click to collapse
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
[email protected] said:
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
Click to expand...
Click to collapse
Thank you very much, I''ll try asap.
[email protected] said:
I dont know the other way.
If you already unlocked the bootloader, flash TWRP Recovery using Fast Boot Command and then flash SU Zip using TWRP.
Click to expand...
Click to collapse
Which version of TWRP should I use for Z3+ (E6553) on nougat (32.3.A.0.372_R3D_Customized RU_1295-0592)?
Holydao said:
Which version of TWRP should I use for Z3+ (E6553) on nougat (32.3.A.0.372_R3D_Customized RU_1295-0592)?
Click to expand...
Click to collapse
Check this step by step guide: https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
[email protected] said:
Check this step by step guide: https://forum.xda-developers.com/xperia-z4/general/guide-safe-bootloader-unlock-restore-t3386915
Click to expand...
Click to collapse
I don't know why but I just couldn't make it, I got soft brick everytime and I flashed to "32.3.A.0.372_R3D_Customized RU" for hundred times. I quit trying that.
Now I'm trying to root my E6553 (on 32.2.A.0.224), stiil couldn't make it either. It stucks on SONY logo or endless boot loop. I just want to root it for once, not to flash twrp but to boot on twrp and flash SU. Isn't that what we call "root"? Am I wrong?
My device bootloader is unlocked, on stock MM rom "32.2.A.0.224". I just want to boot it on TWRP and flash SU, that's all. Isn't that enough for rooting? After that I want to use some apps that only works on rooted devices.
Anyway, thank you for your help, I really apreciate that but I still need help more than ever, each post that I followed to root my device ended in a bad way.
I have essential drivers, my bootloader is unlocked. What is wrong with my device? I tried lots of boot.img's, recovery.img and twrp1.img's but nothing changed...
Holydao said:
I don't know why but I just couldn't make it, I got soft brick everytime and I flashed to "32.3.A.0.372_R3D_Customized RU" for hundred times. I quit trying that.
Now I'm trying to root my E6553 (on 32.2.A.0.224), stiil couldn't make it either. It stucks on SONY logo or endless boot loop. I just want to root it for once, not to flash twrp but to boot on twrp and flash SU. Isn't that what we call "root"? Am I wrong?
My device bootloader is unlocked, on stock MM rom "32.2.A.0.224". I just want to boot it on TWRP and flash SU, that's all. Isn't that enough for rooting? After that I want to use some apps that only works on rooted devices.
Anyway, thank you for your help, I really apreciate that but I still need help more than ever, each post that I followed to root my device ended in a bad way.
I have essential drivers, my bootloader is unlocked. What is wrong with my device? I tried lots of boot.img's, recovery.img and twrp1.img's but nothing changed...
Click to expand...
Click to collapse
Sorry bro, forgot to tell you that you also need a patched stock kernel (with DM Variety & Sony RIC disabled and DRM fixed). After that only you can flash SU Zip. Else it will be boot looped. Check guide link for making patched kernel of you choice of version with one little tool. You can also flash custom Kernel like Zach Kernel, Andro Plus Kernel... etc instead of patched stock kernel to avoid bootloop after SU flash.
AND MY XPERIA OPTION TO BE TURNED OFF else also will in boot loop.
Now the steps are as follows:
Flash Stock ROM
Flash patched kernel
Flash TWRP Recovery
Flash SU Zip
That's it
More info Patched Kernel and DM Variety & Sony RIC disabled and DRM fixed: LINK
I did it at last
One of the kernels didn't create a bootloop after I tried aprox. 128 times and after that SU was flashed. Now I have substratum on MM, thanks again
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Holydao said:
I did it at last
One of the kernels didn't create a bootloop after I tried aprox. 128 times and after that SU was flashed. Now I have substratum on MM, thanks again
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
Ohhhhh... Great...
But tried 128 times??? OMG... You have to spend some time on reading all TECH and FAQ posts before attempting the 3rd atleast bro.... :laugh::good:
I spent my whole time after work and slept at 3 am for 4 days, spent aprox 30 hours... I read every discussion about root 5 times on forum. ?
Why is it so hard to find a proper kernel to root?
E6553 cihazımdan Tapatalk kullanılarak gönderildi
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)