Hi,
if Desire X EMMC is bricked and phone stuck on htc boot logo screen.
so via CWM can we partition our external SD as EMMC and boot the phone.
Regards
Bluffmaster
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
vogonpoetlaureate said:
You need to provide more details. What ROM? What recovery version? What kernel? What do you mean emmc is 'bricked'? Do you have logs? etc.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
I think maybe is a guide not an help thread from his post..
xpirt
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
bluffmaster said:
Hi,
I am a mobile phone technician, i received desire x in dead condition from my customer.
He told me that he used a third party rom due to which phone bricked.
So i resurrect via RIFF J TAG to power up phone, during resurrection when i checked repair kernal + flash recovery + repair htc partition i got below ERROR:
Resurrection is not Completed due to Error: 0x3901 when i click generic customization its completed. check below thread.
http://forum.gsmhosting.com/vbb/f63...ick-repair-htc-partition-1632881/#post9293094
I made generic resurrection then phone boot but stuck logo then i flash with RUU. RUU flashing complete but same condition.
then i unlock bootloader and install flash CWM recovery then i install boot IMG of myONEdx ROM then wipe cache factory data and install myONEdx RC4.0 FX+ rom
when rom complete phone still stuck on boot and can not go further.
then i install boot img of Fulmix ROM v1.0/xpirt rom and again wipe data cahce and install Fulmix ROM v1.0 ROM the my phone boot but restarting so i go to CWM recovery and make external SD partition , When Complete my phone boot sucessfully and running android.
some of times it hang and restart but phone working .
i am confused where is the actually problem.
Regards
Bluffmaster
Click to expand...
Click to collapse
Find the decrypted rom.zip somewhere and extract the boot.img. Flash that. Then flash Desire X 1.18 stock rooted rom to give them root and deodex. Tell your customer they're rooted and that everything should work fine...
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
bluffmaster said:
Dear Stero 8,
Can i use below mention version for root and deodexes?
Desire_X_1_18_SUBB_deodexed
Click to expand...
Click to collapse
Yes!
Dear Stereo 8,
I Just Follow all you instruction , but i got black screen after htc sound ?
any suggestion
Weird... I'm clueless...
Flowed from my HTC branded muffin...
Hi,
Riff box release new DLL, so after resurrection with new dll i flash with stock ruu but phone stuck at boot screen and also not go to recovery.
from old dll it stuck on boot screen but can go to recovery so i can flash CWM but after new dll no recovery ?
What can i do .. confused
Fastboot flash recovery if you can go to fastboot.
Flowed from my HTC branded muffin...
i can boot to fast boot and i install CWM Recovery via fastboot.
but when i go to recovery its stuck at htc logo then restart it
Well, it's probably dead if you can't boot it whatever you flash....
Flowed from my HTC branded muffin...
You are wrong, Riff box restores the EMMC to stock plus if you get successful Resurrection with Riff it should be fine this means the problem is NOT EMMC which leads me to believe the device has a hardware fault but then you say if you install rom to Sd-ext the phone boots although unstable it atleast boots up. Which now leads me to think the device may have a unstable EMMC which means it needs the chip replacing. what you need to do is go to fastboot mode and open up a new CMD window and cd into your fastboot dir and type fastboot oem lock. Then run the Stock RUU and let it reboot into android. if that still dont help then PM me and send me your logs of resurrection from riff box and ill take a look at them see what the errors are thanks
Related
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..
Hello everyone,
recently I bought an HTC One X Plus that was AT&T powered. I wanted to get rid of the restrictions they imposed on the phone, like using the FM Radio, and decided to flash a ROM. In TWRP I did first with success. Then I wanted to flash a custom rom and wiped all data, including the zip file that was pushed to the mobile phone. Consecuence: I was left without an OS on the phone and could not install the custom rom. Now my phone is bricked! Luckily I saved CWM recovery on my PC, and I tried fastboot flash recovery recovery.img. It is being pushed somewhere, but I still don't have access to my mobile phone! Who can help me with this, I am desperate! It seems I made an expensive error!
erkui said:
Hello everyone,
recently I bought an HTC One X Plus that was AT&T powered. I wanted to get rid of the restrictions they imposed on the phone, like using the FM Radio, and decided to flash a ROM. In TWRP I did first with success. Then I wanted to flash a custom rom and wiped all data, including the zip file that was pushed to the mobile phone. Consecuence: I was left without an OS on the phone and could not install the custom rom. Now my phone is bricked! Luckily I saved CWM recovery on my PC, and I tried fastboot flash recovery recovery.img. It is being pushed somewhere, but I still don't have access to my mobile phone! Who can help me with this, I am desperate! It seems I made an expensive error!
Click to expand...
Click to collapse
Lol,
First of all , Why would you flash CWM if you already have TWRP installed ?
If you want to flash a custom ROM just use adb while in recovery to push the rom.zip to your sdcard in order to flash it on your phone.
For example if you want to flash cm11.zip , open a command prompt or a terminal if you're using linux ,then change directory to where the zip file is placed.
for example if your cm11.zip is placed on Desktop , after opening cmd use "cd C:\Users\username\Desktop" then type "adb push cm11.zip /sdcard/" (this will push the ROM zip into your sdcard so you can flash it from recovery.
if you need any more help then feel free to ask ! lol
Please press the thanks button if i helped !
backb0ne5p1d0r said:
Lol,
First of all , Why would you flash CWM if you already have TWRP installed ?
If you want to flash a custom ROM just use adb while in recovery to push the rom.zip to your sdcard in order to flash it on your phone.
For example if you want to flash cm11.zip , open a command prompt or a terminal if you're using linux ,then change directory to where the zip file is placed.
for example if your cm11.zip is placed on Desktop , after opening cmd use "cd C:\Users\username\Desktop" then type "adb push cm11.zip /sdcard/" (this will push the ROM zip into your sdcard so you can flash it from recovery.
if you need any more help then feel free to ask ! lol
Please press the thanks button if i helped !
Click to expand...
Click to collapse
Thanks pal,
problem is only that the ADB gives the message "no device detected", don't forget that the OS on the mobile phone was wiped! But I found the solution, using a tool called WinDroid for HTC One X Plus. With this tool, I flashed CWM to the phone and rebooted in recovery mode. From there, I could mount the SD-card which gave me the option to copy the .zip file to /SDCARD/ using ADB. Also with the tool CWM, I then installed the file, and it worked. I'm on the air now,passed a night without sleep but I learned a lot!! Problem solved!.
Even if you don't have an OS installed ADB should work while in recovery.
Well I'm glad you could solve your problems. I knew about the toolkit but trying the harder way is always better for gaining more knowledge.
Sent from my One X+ using XDA Premium 4 mobile app
Stable ROM for HTC One XL Telus Version
I have HTC One XL / Tellus with 64 GB Internal Storage. I wanted to update it to Jelly Bean through Custom roms like ViperXL + / Elegance.
The phone has HBOOT 1.32.000
Whenever I flash Viper XL+ Tellus on the phone the phone Boots to the Home Screen and then if I unlock then the phone does nothing and just shows the HTC logo on Screen.
I had verified the ROM zip file and had checked its MD5
I got same results with Lower version of Viper XL 1.2.0 / Elegancia 6.2.0 ..
I have flashed ROM 2 to 3 Times with same result.
Is HBOOT1.32.00 not compatible to these ROMs?
What am I doing wrong? Has anyone faced the same problem.
Thanks,
SK
Sujitkundar999 said:
I have HTC One XL / Tellus with 64 GB Internal Storage. I wanted to update it to Jelly Bean through Custom roms like ViperXL + / Elegance.
The phone has HBOOT 1.32.000
Whenever I flash Viper XL+ Tellus on the phone the phone Boots to the Home Screen and then if I unlock then the phone does nothing and just shows the HTC logo on Screen.
I had verified the ROM zip file and had checked its MD5
I got same results with Lower version of Viper XL 1.2.0 / Elegancia 6.2.0 ..
I have flashed ROM 2 to 3 Times with same result.
Is HBOOT1.32.00 not compatible to these ROMs?
What am I doing wrong? Has anyone faced the same problem.
Thanks,
SK
Click to expand...
Click to collapse
you probably forgot to flash the boot.img (the kernel). That's probably why it's not booting
Just reboot into bootloader (fastboot mode) connect it to your computer and use "fastboot flash boot boot.img" then fastboot erase cache then fastboot reboot
This should get it working
Please press the thanks button if I helped
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thanks for reply.
I have already tried that option.:crying:
erkui said:
Thanks pal,
problem is only that the ADB gives the message "no device detected", don't forget that the OS on the mobile phone was wiped! But I found the solution, using a tool called WinDroid for HTC One X Plus. With this tool, I flashed CWM to the phone and rebooted in recovery mode. From there, I could mount the SD-card which gave me the option to copy the .zip file to /SDCARD/ using ADB. Also with the tool CWM, I then installed the file, and it worked. I'm on the air now,passed a night without sleep but I learned a lot!! Problem solved!.
Click to expand...
Click to collapse
If you're able to mount /sdcard/ in recovery. You don't have a One X+.
Sent from my HTC One X+ using Tapatalk
Sujitkundar999 said:
Thanks for reply.
I have already tried that option.:crying:
Click to expand...
Click to collapse
Then flash another kernel. Other than the one that comes with the ROM. Flash a kernel compatible with viperx and it might work.
Cuz when i installed ViperX+ on my phone the kernel that came with the ROM didn't work so i used elite kernel instead. I honestly don't knkw if there's Elite kernel for your phone.. Just flash any other kernel compatible
Sent from my HTC One X+ using XDA Premium 4 mobile app
AndroHero said:
If you're able to mount /sdcard/ in recovery. You don't have a One X+.
Sent from my HTC One X+ using Tapatalk
Click to expand...
Click to collapse
if your trying to flash a 4.2.2 X+ sense 5 rom it is recomended that you be at hboot 1.40 im not 100% sure of the compatibility with 1.32 but any of the custom roms should flash fine without regard to the newest hboot
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.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
s3r3tin said:
Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
Click to expand...
Click to collapse
If you have recovery side load may help.or try full unbrick method rather than mini.
Fap4k said:
If you have recovery side load may help.or try full unbrick method rather than mini.
Click to expand...
Click to collapse
i did try that. didn't help either.
I used this guide and worked for me.....
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
s3r3tin said:
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
Click to expand...
Click to collapse
Same problem here. My device is now in the RMA process and I'm still waiting for their answer if they will repair it on warranty.
They told me that I have voided the warranty because the phone is bricked.
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Oneplus_X_Flasher said:
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Click to expand...
Click to collapse
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Kéno40 said:
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Click to expand...
Click to collapse
my normal "pseudo" was not available, so i take this funny one XD
Bootloader unlocked, OS --> OOS 3.x. Smartphone had boot into OS.
Recovery cant access internal Storage (Stock Recovery & TWRP)
After the stupid idea using the Oneplus original recovery tool the Smartphone cant boot anymore into the OS.
Now the Bootloader ist locked, cant open him anymore. Stock Recovery & TWRP cant access internal Storage.
OOS 2.x doesn't Boot. Android boot animation doesn't show.
So the main problem was, i want to flash CM13 but cant access the internal Storage (unable to mount data, system etc) wipe, formating, erasing was also not possible. even Fastboot had no access.
After using the "mega unbrick Quide" from Oneplus with the MSNdownload tool @ Qualcomm back door the Smartphone is "bricked"....Fastboot, recovery etc all good, but can't boot the OS (OOS2.x) Bootloader is locked, internal Flash still locked :silly::crying:
Fastboot command are OK?
Whatt's the output of "fastboot devices" &
"fastboot oem device-info"
If you have the old OOS 2 recovery on it, fastboot reflash the OOS recovery then try OOS 2.2.3 full rom zip
Old stuff links here : http://forum.xda-developers.com/showpost.php?p=69170103&postcount=45
If still a problem, and you think the BL is already on the new version, try to fastboot reflash TWRP 3.0.2.1 official and then OOS 3.1.4 with it.
To transfer it, use the microSD card.
After Flashing over the Qualcomm back door, the bootloader ist locked. so fastboot says of course, Bootloader ist locked (Fastboot oem device-info) that means, i cant flash anything by sideload or fastboot codes... and when i try it over the Recovery Boot, recovery is not able to mount /Data /System /cache and so on. so i am not able to flash anything XD Neither cm nor stock oxygen in the version OOS2.x / OOS3.x. I try the old bootloader, the new Bootloader and the TWRP 2.8.x, TWRP 3.0.2.0, TWRP 3.0.2.1, TWRP 3.0.2.2 and the Stock Recovery from CM and OnePlus
I've never had this behavior of a mobile phone The Technical Support Team of ONEPLUS even cant help. very strange. Here someone with the same strange problem... http://forum.xda-developers.com/oneplus-x/help/twrp-access-internal-storage-t3513748
The only way to flash anything to the phone is over the Qaulcomm BackDoor. With the new Bootloader & Kernel of OOS3 the boot animation of OOS3 starts and the phone gets hot. but not boot into the OS. And i can't find anywhere the system.img of OOS3. in the Recovery Tool from OnePlus ist the system.img from OOS2 (I have exchanged single items from directory xxx.img)
sorry it is very difficult to explain this complex problem in english XD
IT from Oneplus tried to flash OnePlus_15_A.11_160420 but it still didn't work. Bootlader is locked so TWRP is not an option or is flashing anything trough fastboot. Only Qualcomm Msmdownload tool or qfil. I've tried the old bootlader, new boolader, h2os, ColorOS, Miui ... but the phone just won't boot into any OS. it stays on a black screen with a white led on and that is it.
if the Qualcomm driver mount you a few partition under Windows, you can flash the internal Storage with an clone of a running OPX. I found an guide how to write direct into the Flash with a PC
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
UPDATE: I will get my repaired OPX (or a new one, don't know yet) back tomorrow. They repaired/exchanged it, I had the same problem, black screen and white led. Perhaps my good was to remove the "tampered"-flag from fastboot oem device-info
When I told them I use linux and don't have access to a windows PC they didn't even try the remote-session and told me to send it to them right away.
s3r3tin said:
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
Click to expand...
Click to collapse
i have access to two working Oneplus X but the dead phone did not show the removable drive under Windows so i thing we have to send the dead phone back to OP and hope the can fix oder replace it
You should remove the "tampered"-flag before you send it to them. It's simple:
Use the MSMdownloadtool 2.0 to flash twrp (just swap the recovery.img in the MSM-folder). Then you can start the recovery, but I could not do any swipes (screen didn't react), so I couldn't get past the first screen asking if I wanted to mount system r/o. But adb shell was working.
This I used to use the guide at http://forum.xda-developers.com/oneplus-x/help/guide-unlock-bootloader-oneplus-x-using-t3362640
Use adb push/pull to get the file to your pc.
After dd-ing the modified partition back, I used MSMdownloadtool 2.0 to flash the latest original oneplusX-recovery you can download at their site.
I told the support I never rooted the device and was acting like a complete noob, said I had no idea what android version I was on and it seems they accepted it.
It's definitely a hardware problem. Touch isn't working either. The IT guy checked the oem info himself after the flash and after boot was uncussesful and asked me if the phone was rooted. My warranty is now voided. I have decided to sell my oneplus x for parts.
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