Related
I recently bought this Nexus off eBay and it worked fine.
Owner said it had problems with the SD card, but it seemed to be working, for they said it wouldnt read, when it does.
Anyway, it had cyanogen mod 6.1.1 on it, and I hate the setup...so i changed roms. That was a success, but when i flashed a sense rom thru clockwork(most updated) it said:
E:Error in /sdcard/N1Sensation_v0.4.zip
(Status 0)
Installation aborted.
Now, when i flash any roms, whether it says it installed correctly, it doesnt change anything. Now it's stuck at the 4 color x with the unlock icon. Any advice is good advice!
In my hboot, it says:
*** UNLOCKED ***
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANAL-SYNT0103
RADIO-5.00.00.04
Oct 12 2010, 14:33:16
HBOOT
Etc. Etc. Etc.
Thanks for any help!
Edit: I fixed the issue with why it failed, was my fault, didnt partition the card...but i was flashing a stock rom and it said complete and when i rebooted it stayed at the X and then powered off. Since then has never turned on. I don't know what to do. Nothing will turn it back on. I have a universal charger that charges the battery and it said the battery is full. I need help!
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Dude Random21 said:
Ok lets see here try this plug in the charger then pull the battery place it back in wait a few seconds and repeat until you see the splash screen (the static X). This could get the phone to at least boot.
But just to check did you flash a radio in all that stuff??
Click to expand...
Click to collapse
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
matistight said:
That did not work. I work at a cellphone repair store, but im yet to open it up. But i flashed a sensation rom...
http://forum.xda-developers.com/showthread.php?t=1083035
After then i got stuck on the X
Then i used... well i cant find the link, but it's PureGoogleMod.
From what I saw, there was no radio or kernal being flashed. I just know i flashed a rom, it said completed, then went to the X, rebooted, but never turned on. And ive tried other batteries.
Click to expand...
Click to collapse
Try flashing CM7. Also...before you do...you may want to search for a format.zip from a member named temasek. It'll wipe your phone...clean. Real clean. Then flash CM7. try that.
also....those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
SiNJiN76 said:
Try flashing CM7.
those sense roms sometimes take at least 5 minutes to boot. Sometimes it'll stay on the X screen for 5 minutes or it'll stay on the bootanimation screen for 5 minutes. FYI.
Click to expand...
Click to collapse
I can't flash anything. Phone wont react to anything anymore. Hoping one of my family members can fix it. But if I get it on I will try that.
I am pretty sure i waited long enough, but who knows. I didn't partition my card, which may have been the problem. And also it was S-On....which i thought was odd when it had a custom firmware.
Unlock bootloader. Flash recovery. Boot into recovery. Wipe everything. Flash rom.
Why do you guys keep suggesting software stuff when it's probably a hardware problem he can't get the phone to boot up so he can't do any of that.
Although there is one thing I want you to try before your family take a crack at it to take it apart and what not, it's a long shot but it's your last chance if it's software. Hold down trackball and press power keep holding trackball for another 5-10 seconds (better to long then to short) then connect it to the computer via USB you could see a popup notification saying that it's looking for driver software if you do then it's software and we need to reflash everything and might need to unlock the bootloader. Now if you don't see a popup notification I would still go check in the device manager and check for an unidentified device probably in other (it should be extracted so that you can see it).
If this doesn't work then sorry but I think it's a brick
Because in order to find out if its truly a hardware problem you need to try every software fix first.
Op mentioned nothing of trying fastboot as well. Software fix is free hw is not. That is why we suggest software fixes.
Sent from my Nexus S using XDA App
Let me remind you guys, THE PHONE WONT TURN ON AT ALL REGARDLESS OF WHAT I DO. I can post a YouTube video to show everything. It'd be very random for it to be hardware because it just turned off and will not turn back on. If there is any software like an RUU out there, that would help, if not, ill have to buy a bottom piece and warranty it out. But I'd feel bad because that isn't the right thing to do.
I don't expect you guys to fix it and I and very thankful of your help! But the phone won't turn on at all. So telling me to flash roms doesn't work. Imagine it as flashing a rom with the battery out of your phone. I am wondering if there's an adb way or something to get it to turn on and restore to stock?
With all that said, any help is amazing help and I am very grateful that this isn't a post I have to bump! Thank you so much, when I go on the PC, ill thank the helpful posts
Sent from my (finally) permanent root Sensation 4G
Then it is a brick if it won't turn on at all. The entire getting stuck at the x thing confused me to think it was powering on.
You have me confused sir, I'm not quite sure what good it is your looking for a RUU for. If the phone truly won't turn on/go past the X screen and you have it on a charger with no LED notification, then the phone is bricked. When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom. If you can still get to the bootloader screen then you are not bricked and should retry everything from scratch.
Thread Closed
xsnipuhx said:
When you said you flashed a Sensation rom, I truly hope you just meant a Sense rom.
Click to expand...
Click to collapse
Sensation based, but it was a Sense rom
Confirmed it is bricked.
Sold on eBay for $100
Bought for $77
Semi-Winning.
Thread Closed
First of all I experimented with some custom ROMs. But after a while I wanted to go back to stock and tried to install a RUU I already used succesfull. But during the installation it hung up and I had to cancel it. And now it is impossible to use everything. The phone just show me the black background with the HTC log and four triangles in the corners. I can't use the bootloader, go into recovery or use adb, first of all because my PC doesn't recognize my phone anymore. Already tried to use adb and some tools like the AIO bye anders and the XL Multi tool. I also tried the Forum search for bricked stuff, but nothing worked so far. Any idea how to fix it?
And please excuse my bad english. It was a long day. ^^
In pretty sure that's completely bring, idk how yous brick the sxl, ivebdonebso much stuff to mine and I wonder how mines still perfect, you might wanna look into some articles about jtag!
Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.
Mr. Despair said:
Don't know how, as I said. I did also do a lot of stuff to my phone, custom ROMs, Themes, Kernel etc. Now I just tried to go back to stock, relocked, went into fastboot, everything as prescribed.
And during the installation I've got said that the installation was aborted. The progress bar on the phone didn't react and the software stucked too. Additionaly, my PC is really potent, without any other software problems so far. So, Software forced to close and I had no other joice than to put the battery out of my phone to restart it. And so it happened.
Thanks for the info about jtag. As an Electrician, it is really inviting to buy such a machine. But I think, this time I'll bring it to repair and wait for the results. Let to the experts their job. But thanks for the reply.
Click to expand...
Click to collapse
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app
I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!
ricky310711 said:
I'm not being rude I'm.just stating sxl is very hard to brick if you even try to, I'm not saying its your fault either, a fault USB cable could brick your phone if your half way through an installation if you can't get into bootloader, recovery or pick up your device in adb, I think the only solution is jtag! All the best!
Click to expand...
Click to collapse
before jtag , if the phone is under 2 years , always try to send it in for repair they cant boot up the device , then they cant see if it is unlocked
Very true Anders! Just hope he has warrenty!
anders3408 said:
So if you turn on phone all you have is a black screen? What if you pull out battery and insert it and hold down volume down and power button? Does it go to bootloader or also just black screen? If black screen try adb devices and fastboot devices. And when connected look in control panel what it calls the phone. Perhaps it says qsusb or something?
Sent from my HTC Sensation Z710e using XDA Premium HD app
Click to expand...
Click to collapse
When yo flash RUU the phone goes into kind an own bootloader. The black screen with a silver HTC logo. This is the only thing i get into, but with four triangles, in each corner of the display. It doesn't matter what I do, tried to pull the battery, use the key combo, adb/fastboot etc. When the phone starts, it shows directly the screen described above.
Sent in for repair today and just can wait now. But thanks guys for your replies.
How did it go? Did they fix your problem? Also this happened to me, I discovered that the cause was because installing the ruu relocks the bootloader before it wipes the Rom, and mine failed just before wiping the Rom,I had a custom Rom installed so it would not boot into it because the bootloader was locked so I re-unlocked the bootloader then the phone booted up normally!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Nightstaar said:
Hello,
I'd like to preface this to say I've searched through this and other sites but have not found quite the same problem. I also apologise for the small wall of text. I just want to post everything that seems relevant.
Several weeks ago I unlocked my phone and flashed the latest stable Cyanogenmod. This has all gone fine. I decided today I wanted to try something else and settled on TeamAsylum's 4.4 rom.
Downloaded a whole bunch of stuff and was a little confused as the flashing process seemed a bit different and I didn't fully understand it. I booted into Clockwork Recovery and inadvertently flashed the raw kernel from here, which I downloaded in my searches earlier thinking I needed it. I rebooted the recovery but now I get nothing from the phone. No lights, no display, no vibrations.
I have tried a reset (Power+Volume UP). I have tried using SUS and Flashtool but both get to the same point and stop (hole Volume DOWN and plug USB in). Nothing happens after this. The only thing telling me the phone is alive is when I plug it in, Windows makes the detected sound. If it's plugged in when I hold power+Volume UP it repeats the detection sound as if the phone is trying to boot over and over.
I realise I have ****ed up by flashing the kernal of a different phone. I'm hoping someone can help me or guide me in the right direction.
Thank you.
Click to expand...
Click to collapse
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
RaZieLRaH said:
Try this:
Open flashtool
Hold volume up and insert usb cable( you will enter fastboot )
then select fastboot and flash a good kernel for CM.
let me know it this works
Click to expand...
Click to collapse
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
no clue then sorry can't help
Nightstaar said:
Hi,
I tried what you said. When holding Volume UP and inserting cable, literally nothing happens. I don't even get a sound from Windows detecting it.
Whilst trying this several times though I did notice if I press Power the phone seems to stay on for 30-60 seconds. If I press Power and plug it in, Windows will make a sound. It will then make another sound after 30-60 seconds as if the device has been removed or turned off.
Click to expand...
Click to collapse
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
scifan said:
Just for giggles, check your device manager to see if you have an unknown device... (you may need to install the fastboot drivers...) I've bootlooped my phone a couple of times while putzing with my phone... And can normally get back into flash mode and fast boot mode...
Sent from my Xperia ZL using Tapatalk
Click to expand...
Click to collapse
I did check this. There are no unknown devices. I did install the Xperia Z/fastbot/flashboot drivers from the flashtool folder. When it does make the detection sound Device Manager does 'reset' as if something has connected as well, although I can't find the device.
Most other similar issues have an LED or some type of display and generally are responsive to flashmode.
Note1 boot partition is the XZ's SBL3 (bootloader) partition. So you have effectively flashed a Note1 boot.img to your bootloader. Phone will never boot again once bootloader is hosed. Sorry about your loss
Sent from my C6603 using xda app-developers app
Shoey is right, your Z is toast now, sorry; the only solution here is to replace the MoBo, and that costs a pretty penny.
But why did you download stuff from the n7000 forum? Didn't everything said there sound unfamiliar and therefore suspicious enough for you
to double-check which forum you were in exactly?
I thought as much. I dun goof'd
Thanks for your help.
@chasmodo: Well I started in the N7000 thread and downloaded all the stuff and copied it to my SD card. I then realised I was in the wrong forum and switched to the relevant thread. All the stuff for the N7000 and the Z were both on my SD card, so it was just a stupid mistake really. Everything on both forums sounded a little unfamiliar. As I mentioned I was a bit cofused on the TWRP section. I should done more research before proceeding.
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Nightstaar said:
Do you think there is any use for the phone now? Do you know of anywhere/anyone I can donate it to for spare parts or something?
Click to expand...
Click to collapse
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
chasmodo said:
As I said, you can get it fixed by replacing the MoBo, but I don't know how much that costs in your country. Google a little, contact someone, get the info and then decide what to do.
Click to expand...
Click to collapse
I did have a look around and had trouble finding a main board in particular. I contacted Sony as well and they said it was quite expensive to replace.
I contacted my carrier and it appears getting a new phone is a lot cheaper than anything I've looked into so far.
Thanks for your help.
The next time you decide to flash your phone , make sure your in the correct forum. Lesson learned
Sent from my C6603 using XDA Premium 4 mobile app
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Which carrier is he on? Also, we would need to know if it's a 626, 626s, 626x, 626g, etc... Not sure which model it is from the info posted above. If it's a 626s, the only way to recover is if it's a T-Mobile 626s (no other versions have an RUU to restore it to stock).
Sent from my HP SlateBook 10 x2 PC using Tapatalk
jtrosky said:
Which carrier is he on? Also, we would need to know if it's a 626, 626s, 626x, 626g, etc... Not sure which model it is from the info posted above. If it's a 626s, the only way to recover is if it's a T-Mobile 626s (no other versions have an RUU to restore it to stock).
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
thank you for your response
it's an HTC Desire 626G+ (dual sim) and the carrier is "Telecommunication Company of Iran"
Hmm - I would have him contact his carrier and see if they have an "RUU" available for that phone. An "RUU" is Windows application that will reset the phone back to the way it came from the factory - and can typically restore any phone - unless it has a hardware issue.
Otherwise, let's see if anyone else has any input (I'm not familiar with the 626g myself).
Sorry that I couldn't be more helpful!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
jtrosky said:
Hmm - I would have him contact his carrier and see if they have an "RUU" available for that phone. An "RUU" is Windows application that will reset the phone back to the way it came from the factory - and can typically restore any phone - unless it has a hardware issue.
Otherwise, let's see if anyone else has any input (I'm not familiar with the 626g myself).
Sorry that I couldn't be more helpful!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
i don't think the carrier would help out with this. though it made me think he didn't do anything wrong so do you think that warranty will accept the phone?
The carrier are the ones that need to supply the RUU (either directly or via HTC), which I why I mentioned that he should contact the carrier.
I would agree that it's a warranty issue if he we just trying to install an OTA update and it caused all of this...
Sent from my HP SlateBook 10 x2 PC using Tapatalk
i have same problem with D626ph. I was rooted phone with kingroot after this try to update with ota and result was error and phone boot only to recovery menu
Ahhh - yeah, if you are rooted (and unlocked bootloader), you cannot apply OTA updates. Although, usually, they fail right away and you can just boot right back into the phone normally (without the update, obviously). It's kinda strange that the OTA is bricking the phone like that.
Sent from my HP SlateBook 10 x2 PC using Tapatalk
i wasnt unlock bootloader. phone was trying updating itsef, but failed. cant revive anymore.
i was repair my phone after many hours by flashing with SP FLASH TOOL and with
this file:
https://mega.nz/#!qFgAUQTI
regards!
Cant download the file, post full link.
bossko said:
i wasnt unlock bootloader. phone was trying updating itsef, but failed. cant revive anymore.
i was repair my phone after many hours by flashing with SP FLASH TOOL and with
this file:
https ://mega .nz/#!qFgAUQTI
regards!
Click to expand...
Click to collapse
Your link requires an decryption key.
pl provide key. facing the same problem with htc 626g+. Updated via official OTA. Sad that they rolled it without thoroughly testing it.
Have you guys contacted HTC and/or the carrier? They should resolve this issue for you (via an RUU or some other means)!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
diml0rd said:
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Click to expand...
Click to collapse
Check this out, hope it helps: http://forum.xda-developers.com/desire-626/help/fix-htc-desire-626g-update-command-t3243510
Guys thank you for your replies. I'm kinda new to xda forum. Should i reply one by one and quote people's names or just reply in one comment? Are there any rules?
About the post, it's weird that many people are experiencing the same problem! And where i live phone carriers don't care about phone problems and it's the first time I'm hearing that i should contact my carrier for my bricked device. But things are differently in different countries ?? to @tpr0 i might try your solution when i get my hands on the device againand if no one provides a better suggestion. Because i gave it back to my friend and told him to try the warranty. After a day turned out he has bought the device without a warranty! They sell phones without warranty in iran for a cheaper price. I think it's worth paying 50 more dollars for a 1-2 years warranty. Anyway I'll let you guys know as soon my friend returns his phone (which will be pretty soon I'm guessing. Meanwhile ill wait if anyone has a link for the ROM or a solution.
try this:
https://drive.google.com/file/d/0B-19rlZr42VQVzNzdEV2MkpQQzA/view?usp=sharing
can u tell me the procedure for working with this file ??
diml0rd said:
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Click to expand...
Click to collapse
Im facing the same problem with desire 626 dual sim,after update phone back me to the recovery menu and giving me message update fail.After phone reboot stuck me on recovery menu and thats is. With 2 hours reading forums,the only way was to flash stock rom via Spflash tool..Afterall banned update from phone ! I dont know why is that issues if someone knows tha answer please let tell us ?
If you're using a phone from Iran I think you have bigger things to worry about.
Hello!
Just today I bought myself a second-hand Oneplus 3T that had issues booting into the system. The start of the boot animation would show, but after that the screen just goes black and a white notification light turns on. Confident in my basic skills, I bought it and started trying things.
It boots into recovery and fastboot, all nicely, so first I tried wiping everything with stock recovery and then installing OOS that I downloaded from oneplus. Installed it through the stock recovery ADB Sideload, didn't change a thing. So since the bootloader is locked and cannot be opened, I went on to tryin the Qualcomm 9008 unbrick. Went through with it got a green text in MsmDownloadTool and all, but still nothing. Tried to install that same OOS on this "fixed boot partition" but the only change I noticed that I couldn't even get the start of the boot animation. Just the oneplus logo splash screen and black with white light after that....
If the device is powered down it shows the offline charging screen and a green notification light.
The device is out of warranty, I need the help of you people.... I might try installing twrp and formatting the system partition and installing on that, that is if I can get twrp installed in this kind of a situation.. Thanks!!
EDIT; Tried installing twrp, of course cannot flash it through fastboot but I also tried tricking MsmDownloadTool to install twrp instead of stock to no avail. I got the boot animation starting back but nothing else, also clicking "Install from internal storage" in recovery does absolutely nothing, doesn't bring up a file explorer like I would have expected..
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
thes3usa said:
Have you tried the Qualcomm MSMtoool to completely reinstall OOS? That may work. Don't try to install TWRP through the MSM tool.
This is an usual brick that takes place when someone has tried to relock the bootloader when a ROM/Recovery has been flashed which is not signed by OnePlus. It has been solved many times, so please do a search on XDA and OP Forums before posting a new question.
Click to expand...
Click to collapse
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
MrMatson said:
Man I searched for this kind of brick for a few hours, only found a couple, one on xda and another on oneplus forums, and those didn't get solved. The MSM tool package I'm using does write the system.img so I guess it at least tries to install OOS.... Could you point me in the direction of similar brick situations? This doesn't get fixed by wiping any partitions..
Thanks!
Click to expand...
Click to collapse
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
thes3usa said:
I'm guessing you used this guide (https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) and you did install the drivers correctly yeah?
What error do you get when you MSM tool tries to flash the images? Is it the Sahara error?
Try another computer, or switch USB ports. Also try to download the firmware packages by yourself, and select it from the MSM tool. Also try to let the in-program download flash.
Try going into Fastboot and erase everything, from Internal Storage to the System partition, and then re-try the MSM tool.
Click to expand...
Click to collapse
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
MrMatson said:
Bootloader is locked, nothing can be done through fastboot. I get no errors in MSM, it's just this white light brick when booting to the system. I found a third guy on page 46 of that thread (that's a bit of reading) who had a similar sounding issue. He got it fixed by using a newer MSM version I believe. I am currently downloading the one he said he used. So far I've tried 2 diffrerent MSM packages so far. One other guy in that thread said that the white light should mean a kernel panic... I really hope I can get it working
How can I choose what firmware MSM installs? Or is that even what you mean by "download the firmware packages by yourself, and select ir from the MSM tool"?
I appreciate your help. This really is a frustrating kind of error.
Click to expand...
Click to collapse
As I'm aware, you can select packaged files which you have downloaded. It is basically the same file the MSM tool downloads, but it could be a higher version. (I.E: MSM tool downloads OOS 3.5.6 by default, but you could flash a file which you downloaded yourself, which can be OOS 4.0 or so.)
Correct me if I'm wrong, I've only used the MSM tool once or twice, and I'm speaking from reading about it on other threads.
Don't panic, your phone can get into fastboot and recovery, so you can definitely save it. Its just a little annoying, but it's not like its a Samsung device. I've myself had the white light. It can be easily fixed.
Supporting each other is what a community is for. Helping each other is what we do.
Good luck, and update us on what happens.
Update: Tried versions 3.0.6 and 3.0.8 of MSM in addition to the version 3.0.0 I had before. No luck. I'm starting to feel like I've tried everything there is to try... The device works everywhere else like it should, it just doesn't boot into system. Recovery and fastboot and Qualcomm mode are available, just can't seem to fix this with those... I need some help
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
He said in OP he can't flash TWRP.
krombopulos said:
It could be some sort of hardware damage. Following liquid ingress, my oneplus 3t had the exact same symptoms. The problem in my particular case happened to be with the board with audio jack on it at the bottom, I could use the phone normally (without hardware keys/fingerprint scanner) by disconnecting and blocking the two connectors for those components, until a replacement board arrived. The board cost me £8.50. There could be loads of reasons for this blank screen and white LED though, gluck mate!
Click to expand...
Click to collapse
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
bluuquthug said:
hey bro, im facing the same with you on my 2nd hand 3T. almost all rom i tried cant fix that problem, but i got some fix when i flashed RR Sultanized.
- UBL
- flash latest TWRP or blu_spark TWRP recovery
- wipe everything
- follow carefully with this link to flashing RR Sultanized
- flash gapps (im using aroma gapps, pico is recommend)
- boot system to make sure everything is good
- install wakelock from playstore, choose partial wake lock (without this you will get random reboots or shutdown, but white led is gone on mine)
- restart system
- then magisk to root if you like
so far this is saved my poor 3T, good luck bro
sorry for my bad grammar
Click to expand...
Click to collapse
Yea... I got my bootloader locked so no luck there... Thanks anyway!
MrMatson said:
Yea... I got my bootloader locked so no luck there... Thanks anyway!
Click to expand...
Click to collapse
Yeah You need to UBL first bro, try via fastboot to flash twrp.
Im using msm tool first, then flashing OOS, next UBL
I don't think UBL will help either, as I am stuck on stock reocevoery.
Update: https://forum.xda-developers.com/general/rooting-roms/installing-twrp-locked-bootloader-t3669879 this guy seems to have succeeded in doing what I tried on a Xiaomi phone. I don't know if it's possible to replicate on a oneplus though... No luck so far
MrMatson said:
Yup, cannot flash twrp throguh ususal means... But you saying you had a similar problem, phone wouldn't boot with those parts connected, but did go just fine with them disconncted? If that's the case, I will start trying it with different parts. I really want to get this thing working! Thank you for both of your inputs!
Click to expand...
Click to collapse
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
Oh... As I have stock recovery, the back key can be used to go back, and it seems to work... Well, any hardware modifications will have to wait, as I do not have a T2 driver and there seems to not be a single one in stock in Finland anywhere, gotta wait out on one from china.... But maybe trying some other parts will work The navigation keys also light up briefly when booting, for a second or so. Thanks!
krombopulos said:
That's right, the phone would boot normally and was usable with the two flexes disconnected, I just had to active a software navbar. TWRP would work normally with them connected, I think that's because the hardware keys/fingerprint scanner aren't active in recovery.
Click to expand...
Click to collapse
koax88 said:
my friend op3 also had similar problem, the problem only occur after changing camera module. change back to original faulty modules seems fixed the issue. after he order other camera module and assemble it back, the device worked normally, it seems that any hw dmg will prevent the phone from booting system.
Click to expand...
Click to collapse
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
MrMatson said:
Thanks to you, I have that tingling sensation of trying again! I hope this is not on the motherboard, everything else I can manage.... Just gotta survive the wait for my T2 screwdriver..... This is a nice feeling
Click to expand...
Click to collapse
Just curious, did the seller give you any information about why the device was bricked?
Cause if he was just trying to modifying the software without knowing what he was doing you should have resolved it by now, as MSM-download-tool does not show specific errors I assume it's able to write software correctly to the corresponding partitions but then something prevents it from booting up to android system, unfortunately the chances for any hardware related problem are definitely there, even very likely...
So if you bought the device assuming a software related problem but got a hardware defect it could look just the same from outside, only further possibilities I see is by having a look inside and even then you'll need some luck finding the issues...
Don't know if you have one of these little phone repair shops around but they're helpful sometimes getting advice about hardware, etc. also YouTube is a great resource for tutorials...
Just my 2 Cents, good luck
- hope you succeed in the end!
Sent from my OnePlus 3T using XDA Labs