I have used windroid htc one x+ toolkit to unlock bootloader.
It shows a dialogue saying bootloader is unlocked . But in the phone it still shows a locked screen and also showing as s-off
I have root and i am able to use titanium backup.
I have also tried to flash twrp recovery.. but not able to do so.
Can somebody please point me in the right direction..
tonysimonhere said:
I have used windroid htc one x+ toolkit to unlock bootloader.
It shows a dialogue saying bootloader is unlocked . But in the phone it still shows a locked screen and also showing as s-off
I have root and i am able to use titanium backup.
I have also tried to flash twrp recovery.. but not able to do so.
Can somebody please point me in the right direction..
Click to expand...
Click to collapse
Try manually follow the instructions from htcdev and let us know which part fails........
[email protected] said:
Try manually follow the instructions from htcdev and let us know which part fails........
Click to expand...
Click to collapse
Thank you ..
I was able to flash twrp using Rom toolbox.
now I have twrp but the bootloader still shows as locked.
I tried to install a custom Rom but failed because of my own mistake.. today I will try once more to flash a Rom.
will post it's result..
I think I read somewhere that soff devices can't be unlocked..is this true
tonysimonhere said:
Thank you ..
I was able to flash twrp using Rom toolbox.
now I have twrp but the bootloader still shows as locked.
I tried to install a custom Rom but failed because of my own mistake.. today I will try once more to flash a Rom.
will post it's result..
I think I read somewhere that soff devices can't be unlocked..is this true
Click to expand...
Click to collapse
I dont think so....
Can u try using HTC dev and report back....
NOTE UNLOCKING WILL WIPE ALL UR DATA AND SDCARD STUFF FROM UR PHONE....
SO BACKUP
[email protected] said:
I dont think so....
Can u try using HTC dev and report back....
NOTE UNLOCKING WILL WIPE ALL UR DATA AND SDCARD STUFF FROM UR PHONE....
SO BACKUP
Click to expand...
Click to collapse
Sure I will try it in the evening.
You can definitely Unlock it using the HTCDEV process , I have a done this. Any ways if you are able to flash a ROM then there is no reason to get it Unlocked, more over S-OFF gives you full control over the device but again it also increases the risk of getting your phone bricked so make sure you use it wisely (knowing what you flash) , so I will say why to beg HTC for some thing they have already provided.
One more thing S-OFF device means you dont need to flash boot.img separately so you dont need to use your PC to flash roms no more.
Waiting to know about your progress on flashing the ROM ..
ethanon said:
You can definitely Unlock it using the HTCDEV process , I have a done this. Any ways if you are able to flash a ROM then there is no reason to get it Unlocked, more over S-OFF gives you full control over the device but again it also increases the risk of getting your phone bricked so make sure you use it wisely (knowing what you flash) , so I will say why to beg HTC for some thing they have already provided.
One more thing S-OFF device means you dont need to flash boot.img separately so you dont need to use your PC to flash roms no more.
Waiting to know about your progress on flashing the ROM ..
Click to expand...
Click to collapse
I have now successfully flashed a Rom..initially I tried it without flashing the boot.img and it entered a boot loop.
Then I installed flashify and flashed boot.img that came with the Rom. Then the Rom is working now.
The boot loader is still locked. Has twrp .
tonysimonhere said:
I have now successfully flashed a Rom..initially I tried it without flashing the boot.img and it entered a boot loop.
Then I installed flashify and flashed boot.img that came with the Rom. Then the Rom is working now.
The boot loader is still locked. Has twrp .
Click to expand...
Click to collapse
so you mean to say you failed to install the boot.img from the custom recovery ? well that is weird, one more thing since you were in boot loop how did you manage to install flashiffy !
if you may please include the complete flashing steps , will be helpful for my experiments.
ethanon said:
so you mean to say you failed to install the boot.img from the custom recovery ? well that is weird, one more thing since you were in boot loop how did you manage to install flashiffy !
if you may please include the complete flashing steps , will be helpful for my experiments.
Click to expand...
Click to collapse
Initially I flashed the Rom alone and it went into bootloop and all buttons became unresponsive .so I waited till the battery ran out and the phone switched off. Then I recharged , entered recovery by vol down + power button.. I had the backup there . So I restored back up.. then phone rebooted normally.. and I flashed boot.img by flashify just because I didn't know any other method... Then from recovery I wiped dalvik cache and system .. flashed the new Rom.. reeboot and fine..
Feel free to ask for any more clarification..
Related
hello,
I have got a Desire x after my sister becouse she got a new phone,
at first the desire x was randomly rebooting but ive read on different forums and there was lots of was to stop that ,
so i picked the easyest way to update
so i went to settings, about phone and clicked for the phone to cheak for updates
and it did find the update to jb so i did
and every thing worked fine but i like to play real racing 3 but this device is not compatable so i downloaded the apk from a different source
but i the app opened and than closed
so i toughed that i need to root to install this app so i began
http://forum.xda-developers.com/showthread.php?t=2316662
i read the aboves guide how to do it but i found a tool
http://forum.xda-developers.com/showthread.php?t=1943822
and i used it becouse i found it more easy and i unlocked bootloader flashed twrp 2.6,flashed superuser and cheaked if phone is rooted with root cheaker and it sayed that my device is not fully rooted (or something like this) even busy box was saying that there are no root premission
but so i was trying to redo it manually but when i wanted to do something it sayed [waiting for device]...
and nothing i tryed it on 2 pcs and nothing but i flashed a rom and thoughed that after i will do it i will be able to flash via fastboot the boot.img file but nothing and i think ive bricked my device so i need help to get out of this
the_ziom said:
hello,
I have got a Desire x after my sister becouse she got a new phone,
at first the desire x was randomly rebooting but ive read on different forums and there was lots of was to stop that ,
so i picked the easyest way to update
so i went to settings, about phone and clicked for the phone to cheak for updates
and it did find the update to jb so i did
and every thing worked fine but i like to play real racing 3 but this device is not compatable so i downloaded the apk from a different source
but i the app opened and than closed
so i toughed that i need to root to install this app so i began
http://forum.xda-developers.com/showthread.php?t=2316662
i read the aboves guide how to do it but i found a tool
http://forum.xda-developers.com/showthread.php?t=1943822
and i used it becouse i found it more easy and i unlocked bootloader flashed twrp 2.6,flashed superuser and cheaked if phone is rooted with root cheaker and it sayed that my device is not fully rooted (or something like this) even busy box was saying that there are no root premission
but so i was trying to redo it manually but when i wanted to do something it sayed [waiting for device]...
and nothing i tryed it on 2 pcs and nothing but i flashed a rom and thoughed that after i will do it i will be able to flash via fastboot the boot.img file but nothing and i think ive bricked my device so i need help to get out of this
Click to expand...
Click to collapse
It's not bricked, I think you need to reinstall a recovery. I recommend TWRP 2.5 instead of 2.6 because 2.5 has no bugs. Try to restore your nandroid backup (if you haven't any try one of these: http://forum.xda-developers.com/showthread.php?t=2324815 and choose your cid) and then flash SuperSU: http://download.chainfire.eu/supersu
PS: you can use the tool for installing custom recovery, only choose ''your own recovery'' and click on the recovery image
GtrCraft said:
It's not bricked, I think you need to reinstall a recovery. I recommend TWRP 2.5 instead of 2.6 because 2.5 has no bugs. Try to restore your nandroid backup (if you haven't any try one of these: http://forum.xda-developers.com/showthread.php?t=2324815 and choose your cid) and then flash SuperSU: http://download.chainfire.eu/supersu
PS: you can use the tool for installing custom recovery, only choose ''your own recovery'' and click on the recovery image
Click to expand...
Click to collapse
thank you but i dont have any backup and remeber i flashed a different rom and black screen al the time
the_ziom said:
thank you but i dont have any backup and remeber i flashed a different rom and black screen al the time
Click to expand...
Click to collapse
You can get a nandroid backup from that link, only read everything over there very carefully. And after that flashing superSU
GtrCraft said:
You can get a nandroid backup from that link, only read everything over there very carefully. And after that flashing superSU
Click to expand...
Click to collapse
yes but i cant get cid becouse system does not boot up and fastboot does not see my device bu i will try
the_ziom said:
yes but i cant get cid becouse system does not boot up and fastboot does not see my device bu i will try
Click to expand...
Click to collapse
Reinstall the drivers and you can use the All In One tool to get your cid
GtrCraft said:
Reinstall the drivers and you can use the All In One tool to get your cid
Click to expand...
Click to collapse
yes but i allready tryed reinstalling deivers maybe you could give me a link to specyfic drivers
the_ziom said:
yes but i allready tryed reinstalling deivers maybe you could give me a link to specyfic drivers
Click to expand...
Click to collapse
Use the drivers given in the tool: http://www.hasoon2000.info/getdownload.php?file=HTC Drivers/HTCDriver.exe
GtrCraft said:
It's not bricked, I think you need to reinstall a recovery. I recommend TWRP 2.5 instead of 2.6 because 2.5 has no bugs. Try to restore your nandroid backup (if you haven't any try one of these: http://forum.xda-developers.com/showthread.php?t=2324815 and choose your cid) and then flash SuperSU: http://download.chainfire.eu/supersu
PS: you can use the tool for installing custom recovery, only choose ''your own recovery'' and click on the recovery image
Click to expand...
Click to collapse
Dude if its saying not rooted you were supposed to flash the supersu.zip in twrp and then update it then you would have root privleges you flashed a rom without root the supersu didnt you? And it basically bricked it so hold vol down and power boot into h boot go to recovery it will boot you into twrp check to see if you do have that supersu.zip if you have it flash it and you dont have s-off look in that rom package and find the kernel (boot.img) flash it and wipe your dalvic cache and your cache and it should boot into that rom but if you dont have that supersu.zip you mite have to side load it then flash it
sent from my one x+ if i helped you out hit that thanks button
gothicasshole said:
Dude if its saying not rooted you were supposed to flash the supersu.zip in twrp and then update it then you would have root privleges you flashed a rom without root the supersu didnt you? And it basically bricked it so hold vol down and power boot into h boot go to recovery it will boot you into twrp check to see if you do have that supersu.zip if you have it flash it and you dont have s-off look in that rom package and find the kernel (boot.img) flash it and wipe your dalvic cache and your cache and it should boot into that rom but if you dont have that supersu.zip you mite have to side load it then flash it
sent from my one x+ if i helped you out hit that thanks button
Click to expand...
Click to collapse
but i flashed supersu and flashed the boot.img flashed the rom i want and still blank screen
the_ziom said:
but i flashed supersu and flashed the boot.img flashed the rom i want and still blank screen
Click to expand...
Click to collapse
Just restore the nandroid backup as I told earlier and flash the SuperSU I gave in the link
GtrCraft said:
Just restore the nandroid backup as I told earlier and flash the SuperSU I gave in the link
Click to expand...
Click to collapse
ahumm how to restore it?
sorry but i got no cloue about this phone
ive rooted htc wildfire, sensation
and samsung s2 and s3 but this phone i made a big fail with
the_ziom said:
ahumm how to restore it?
Click to expand...
Click to collapse
Look at the second post in thread with the nandroid backups
GtrCraft said:
Look at the second post in thread with the nandroid backups
Click to expand...
Click to collapse
unfortunetly i restored and still have the black screen promlem
the_ziom said:
unfortunetly i restored and still have the black screen promlem
Click to expand...
Click to collapse
You flashed the boot.img?
GtrCraft said:
You flashed the boot.img?
Click to expand...
Click to collapse
but what boot.img
im very confused
the_ziom said:
but what boot.img
im very confused
Click to expand...
Click to collapse
ok sry the stock boot.img but u forgot that pc does not see my device right?
the_ziom said:
but what boot.img
im very confused
Click to expand...
Click to collapse
Turn your phone into fastboot mode (holding power and volume down when turning on) and plug it into your pc.
Extract the zip file and run ''Install Boot.img.bat'' and reboot
GtrCraft said:
Turn your phone into fastboot mode (holding power and volume down when turning on) and plug it into your pc.
Extract the zip file and run ''Install Boot.img.bat'' and reboot
Click to expand...
Click to collapse
but u forgot that my pc does not see my device right?
the_ziom said:
but u forgot that my pc does not see my device right?
Click to expand...
Click to collapse
Even after reinstalling drivers?
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Filz0r said:
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Click to expand...
Click to collapse
Used the flashing tool.But in every mode of flashing,the bootloader flashing and boot.img flashing is showing some error.But rest all are flashing succesfully.Still in bootloader it is showing baseband not found.And when I boot the device,the bootloader screen comes up,followed by a black screen and the cycle repeats.Any help would be appreciated.
Edit:My moto e 2015 is a LTE RETASIA(Indian) model.In the baseband link you provided,XT1521 RETASIA version's baseband is not available.
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
first.act.line said:
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks I will try that.
gauthamkithu said:
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
vishalgupta.vns said:
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
Click to expand...
Click to collapse
Thanks buddy but unfortunately I have tried that.:crying:
OK guys, thread cleaned.
No more flame from anyone please, no more garbage.
OP please provide as much details as possible. Everyone else, you can ignore the OP if you want, but do not come in here just to flame.
Thanks.
Hi guys,
Before you say again a topic on a non bricked One Plus X, I would like to let you know that I've checked and try almost all of the tutorial I've seen on xda and one plus forum.
I was on CM14.1 with this ROM : https://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-14-onyx-t3452150
Unfortunately, I made the 25-12-2016 update and it totally broke up the phone..
I download the OnePlus X OxygenOS 3.1.4 on the One Plus website. So I flash it on the stock recovery, it tells me "Install success" then I reboot and it stays on the bootlogo.
For information, I can't access the oem unlock menu if needed, but when I ask the oem device info it says unlocked. The phone is detected by the computer sometimes with unknown device and sometimes correctly with the qualcomm drivers..
I have a back up made from TWRP, I can access the device by the fastboot mode, it seems that all the operations written here worked but it doesn't install or even boot on TWRP..
Thanks for your help guys.
Are you using latest TWRP from website think version 3.0.3?
Exodusche said:
Are you using latest TWRP from website think version 3.0.3?
Click to expand...
Click to collapse
I'm not even using TWRP, since I can't boot on it.. But I tried to flash the twrp-3.0.2-2 from blue spark v41, after the installation via Flashboot, it doesn't boot up on the recovery..
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Exodusche said:
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Click to expand...
Click to collapse
Exactly, the phone is stuck on the one plus logo..
defqon_1 said:
Exactly, the phone is stuck on the one plus logo..
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Divyesh49 said:
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Click to expand...
Click to collapse
Didn't work. I tried to lock and then unlock to be sure but not is stay in false for tempered AND unlocked.
So I don't have any idea on how make android back on my phone.
I just have access to Fastboot mode. No recovery, nothing else..
EDIT : phone is not starting anymore. I try to charge it hoping it just a low battery problem..
You should send it to RMA
Trimis de pe al meu Redmi 3S folosind Tapatalk
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Help Pls
defqon_1 said:
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Click to expand...
Click to collapse
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Fix It!
Exodusche said:
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Click to expand...
Click to collapse
Done! finally i can reinstall stock rom and recovery with drivers by usb.
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Done
defqon_1 said:
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Click to expand...
Click to collapse
Don't worry i have restored my OPX 5 days ago. I used the method of this video: https://youtu.be/R4SVSovw4Jo and files from this thread: https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 , if it can help someone.
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
shreyasminocha said:
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
Click to expand...
Click to collapse
What was your last rom? Did u upgrade ur bootloader?
You probably looking at mega unbrick guide
cva_kabil said:
What was your last rom? Did u upgrade ur bootloader?
Click to expand...
Click to collapse
I was running stock OxygenOS(>3.0.0) ROM.
shreyasminocha said:
I was running stock OxygenOS(>3.0.0) ROM.
Click to expand...
Click to collapse
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
That said, should I follow a bricked guide before doing the above?
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
Also, is there any way I can downgrade my bootloader?
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Flash any 2.X.X ROM. One way is to fastboot flash old stock recovery and flash safest way I think. The other is to flash with twrp make sure after flashing the ROM to flash old twrp IMG after. Make sure you boot right back into twrp.
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Assuming you're on OOS3 with TWRP for new bootloader,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Flash twrp for old bootloader via fastboot, use this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img
Done
-Now u hv sucessfully downgraded ur bootloader,flash PA or any supported roms
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
TravaPL said:
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
Click to expand...
Click to collapse
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
iamsandiprathva said:
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
Click to expand...
Click to collapse
Did you managed to sort it out? How?
Mega unbricked guide?
Im the most stupid person alive because
I didn't unlock my bootloader
I installed xzrecovery witch is a app that installs twrp
Then in twrp i wiped every thing
Then I tried to install a rom witch didn't work
Then i trend the phone off when i tried to do so twrp said your device is not rooted do you want to install super su i said yes the phone is now stuck on sony logo
Pliz help
aliamiri70007 said:
Im the most stupid person alive because
I didn't unlock my bootloader
I installed xzrecovery witch is a app that installs twrp
Then in twrp i wiped every thing
Then I tried to install a rom witch didn't work
Then i trend the phone off when i tried to do so twrp said your device is not rooted do you want to install super su i said yes the phone is now stuck on sony logo
Pliz help
Click to expand...
Click to collapse
You wiped everything and now there is no rom installed so its not going past the sony logo. You have two options.
1. Unlock bootloader if you want to run a custom rom.
2. Flash stock rom to go back to stock.
and how to flash stock rom , you need to have the flashtool , put your phone in donwloadmode ( volumne down + plug in the usb cable ) and then flash the stock rom of sony ( you can find the method on how to do it on google ) its simple and then you decide out of 2 options above from last post
Since your bootloader isn't unlocked your can use Sony Companion Software to repair your phone. When you click update there is a repair option. Select repair and hook up the phone in flashmode. Make sure your ZU is atleast 50% charged.
thanks for replying everyone i tried the flashtool stock rom installation and i got boot loop now i tried two different ftf files but they both result in boot loop what am i doing wrong?
aliamiri70007 said:
thanks for replying everyone i tried the flashtool stock rom installation and i got boot loop now i tried two different ftf files but they both result in boot loop what am i doing wrong?
Click to expand...
Click to collapse
can you flash the stock rom again and copy paste the log here in a code quote like this one:
Code:
write here
And what is your model? C6833 etc..
What stock rom did you download?
Which drivers did you use?
And which version of flashtool did you use?
And lastly what settings did you use when flashing the stock rom? All options included so ALL partitions being flashed. And none excluded.
Screenshots is always good help .
for locked bootloader http://support.sonymobile.com/fr/xperia-companion/
for unlocked bootloader https://developer.sonymobile.com/open-devices/flash-tool/
Thanks I didn't check the wipe section wich causes bootloader thanks again to everyone who helped
aliamiri70007 said:
Thanks I didn't check the wipe section wich causes bootloader thanks again to everyone who helped
Click to expand...
Click to collapse
You're welcome