Related
So I'l start off by saying I found this forum, from a freind who said that you guys on this forum could help me with the problem I'm having.
So I have a normal Samsung S Plus. It was rooted. And It was already overclocked, but the preformance was still bad. So someone recomended me to update my Samsung version or install a custom ROM. I talked to a guy who also had the same phone as me and told me about this ROM. I read up alot about how to install them and everything, so I did it. I installed the ClockworkMod Recovery(the touch version) I put the rom on my phone and followed a tutorial on how to install it. It went all good and it said that the rom was installed succsesfully. So to finish the proccess I had to reboot my phone, so I did. The reboot took abit longer than normal and it was expected, but the phone went back to the recovery main menu, I rebooted again hopeing it would resolve it self, but it didn't. I rebooted the phone like 10 times but it kept going to the main recovery menu. So I read up on alot of things on how to fix it and contacted alot other to try and help me, none of the things helped, it always went back to the main recovery menu.
I actully called my phone company and they gave me a number of a phone service, so I brougth the phone to them, I waited for about 2 days for them to get back to me. So when they did, they said that my phone was broken? They didn't say how or why they just said that I broke the phone somehow by trying to install a new version of Android and they said that the reapir would cost me 220 Euros. If you're from Europe you would see that that is a complete rip off. Offcourse I didn't pay them, I just got my phone back in the same state that it was when I gave it to them
So to shorten this topic, I'm looking for a solution to fix my phone myself, without having to pay loads of money, that I dont have.
Basicly my phone is stuck on the ClockwordMod Recovery main menu screen. I can't do anything outside of that. I can edit stuff with the options the mod gives me.And I can put stuff on my SD card if I take the card out of my phone and into my laptop.
If anyone on this forum can help me, please comment bellow. I would be really greatfull to anyone that can give me some tips on how to fix this.
Thanks for reading.
Does download mode work?
Skickat från min GT-I9000 via Tapatalk 2
mreminemfan4ewver said:
So I'l start off by saying I found this forum, from a freind who said that you guys on this forum could help me with the problem I'm having.
So I have a normal Samsung S Plus. It was rooted. And It was already overclocked, but the preformance was still bad. So someone recomended me to update my Samsung version or install a custom ROM. I talked to a guy who also had the same phone as me and told me about this ROM. I read up alot about how to install them and everything, so I did it. I installed the ClockworkMod Recovery(the touch version) I put the rom on my phone and followed a tutorial on how to install it. It went all good and it said that the rom was installed succsesfully. So to finish the proccess I had to reboot my phone, so I did. The reboot took abit longer than normal and it was expected, but the phone went back to the recovery main menu, I rebooted again hopeing it would resolve it self, but it didn't. I rebooted the phone like 10 times but it kept going to the main recovery menu. So I read up on alot of things on how to fix it and contacted alot other to try and help me, none of the things helped, it always went back to the main recovery menu.
I actully called my phone company and they gave me a number of a phone service, so I brougth the phone to them, I waited for about 2 days for them to get back to me. So when they did, they said that my phone was broken? They didn't say how or why they just said that I broke the phone somehow by trying to install a new version of Android and they said that the reapir would cost me 220 Euros. If you're from Europe you would see that that is a complete rip off. Offcourse I didn't pay them, I just got my phone back in the same state that it was when I gave it to them
So to shorten this topic, I'm looking for a solution to fix my phone myself, without having to pay loads of money, that I dont have.
Basicly my phone is stuck on the ClockwordMod Recovery main menu screen. I can't do anything outside of that. I can edit stuff with the options the mod gives me.And I can put stuff on my SD card if I take the card out of my phone and into my laptop.
If anyone on this forum can help me, please comment bellow. I would be really greatfull to anyone that can give me some tips on how to fix this.
Thanks for reading.
Click to expand...
Click to collapse
You have a bootloop into Recovery. Don't worry, it's not a "serious" problem, I had that too, first time I flashed CM. Fortunately, [email protected] has a great and easy solution for this (it worked for me and for many others).
You don't need to pay anything just flash this and bootloop into recovery will never happen again: link.
Hope it helps!
educk said:
You have a bootloop into Recovery. Don't worry, it's not a "serious" problem, I had that too, first time I flashed CM. Fortunately, [email protected] has a great and easy solution for this (it worked for me and for many others).
You don't need to pay anything just flash this and bootloop into recovery will never happen again: link.
Hope it helps!
Click to expand...
Click to collapse
This migth actully solve my problem, but I'm running into a problem.
Odin wont recognize my phone. It doesn't say added in the program. Any tips on how to fix that?
mreminemfan4ewver said:
This migth actully solve my problem, but I'm running into a problem.
Odin wont recognize my phone. It doesn't say added in the program. Any tips on how to fix that?
Click to expand...
Click to collapse
Download Odin Multidownloader 4.43. Open it up in your computer.
Boot into download mode by powering off the phone, than with the phone off, hold down Volume Down + Home + Power until you get into Download Mode. Now plug in your USB cable.(connect your phone), if you have Windows 7, wait for installing the Odin driver, (it installs automatically) and then you should see ADDED !!! in Odin.
Than follow the instructions from point 3:
3. Select OPS - AriesVE.ops (UnZip from AriesVE.zip)
4. Select BOOT - Boot_loader.tar
5. Flash it and bootloop into recovery never gona happen.
You can download all files from here: (All credits go to [email protected], original post: Fix for recovery bootloop problem)
thanks you sooooo much, this finnally fixed it. You saved me from spending a ton of money for a fix. I can't thank you enough
mreminemfan4ewver said:
thanks you sooooo much, this finnally fixed it. You saved me from spending a ton of money for a fix. I can't thank you enough
Click to expand...
Click to collapse
Good! I glad I helped!
Yesterday I went to a party, nothing wrong with the xperia t. When I got home I let it recharge. I think it still worked at that moment. Pretty sure it did. Went to sleep. Woke up. My phone battery was empty lol. Still in the recharger. Did some stuff, let it recharge some more. Got it to boot up again. Now touch screen doesn't work anymore . Tried wiping cache, factory reset. Still not working.
I have cm-10.1.3-RC2-mint installed. I think I might have to update it. This could be the problem.
Any more tips for if it doesn't work? never had this problem before. I hope it is a software thingy.
I updated the firmware but still doesn't work. I think im gonna re-install the stock firmware, and flash a stock kernel which will unroot my mobile. Any tips? please? I can't use my phone at all atm. It just stays at the cyanogenmod install screen..
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
gregbradley said:
Reflash the touch firmware
read this
http://forum.xda-developers.com/showthread.php?t=2220290&highlight=touch+screen+not+working
especially post 11
Click to expand...
Click to collapse
I would like to try that thing with adb, but as I have already reinstalled cyanogenmod, developer options/debugging is turned off. I can't use ADB. Unless you know another way.
So this is totally getting out of hand.. (and I don't know if that is also a english expression lol).
I tried reflashing a stock firmware. Worked, but touchscreen still doesn't work. Then I noticed, that I now don't have cwm anymore... how the f?
SO I probably forgot to exclude the kernel. So now I tried reflashing a kernel with cwm, but flashtool doesn't recognize the kernel files... I don't know what is going on..
Ah already found the problem. Got cwm back phewww..
So here is what needs to be done. I want to try gregbradleys adb shell fix but my usb debugging is off and this means that I can't use adb, as I don't have touchscreen.
So, is there any way, any way at all, to enable usb debugging without touching the screen? Maybe a kernel with that settings automaticly set?
Im getting a bit angry at my phone now.. I didn't even do anything to break it in the first place. Just tried recharging it, and that killed the touchscreen? lol. Help will be appreciated. Im out of ideas.
Get a usbotg cable and attach a usb mouse
Then use that to turn debugging on
When you flash a stock firmware you lose recovery.
Sent from my C6903 using xda premium
thanks, I'll get one tomorrow. I hope it will help. You've helped me before so im pretty confident that you fix my problem again haha. You are a boss.
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
gwodus said:
A non responsive touch screen happened to me too after I flashed a wrong firmware. I flashed back the version that was on before, but it didn't help. Only after I flashed this (pretty old) version Xperia T - 7.0.A.1.303 Generic DE with Flashtool, the touch screen started to working again. I am not sure, maybe any ftf would work. But I know that I had success with this one.
You should try gregbradleys method first though. Funny, that your touch screen stopped working, without you modifying anything. Hopefully it's not a hardware problem.
Click to expand...
Click to collapse
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
quinten96 said:
hmmm, I tried this and it worked. problem solved. I did however not have wrong firmware installed, but it was an rc2 version of cm. So it can be unstable and stuff, but this was kind of a big problem.
Click to expand...
Click to collapse
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Sorry to bump
gwodus said:
Hey, glad your phone is ok again. I remember when that happened to me. I just had the phone for a couple weeks. Shat my pants, thinking I wrecked it. It worked out at the end, though. Feels good to recover a bricked phone, doesn't it.
Click to expand...
Click to collapse
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
jmm288 said:
I am having this exact problem! I'm sorry to awake this sleeping thread, but I have a locked bootloader and I tried a Sony PC Companion reset and it still has the problem. Is there anything else I can do?
Click to expand...
Click to collapse
I have the same problem... I changed touch panel, flex cable and update with pc-companion but it doesn't work
Hey XDA guys,
I've got an I8190N
I've got a pretty big problems and I need the help of your big brains.
Well a long time ago (17th September 2013) I posted a thread about a problem with my phone, when I booted up, it had this screen:
*Image should either be here or in the attached thumbnails*
So about 3 weeks ago from today I was trying to install a new CM11 ROM update from Maclaw but after I put the zip on my sd card and booted into TWRP recovery (2.6.3.0, just in case it needs mentioning), the phone shut off in the middle of the installation, I thought it was just the usual bugs I get whilst flashing ROMs so I tried to turn it on and it wouldn't turn on.
After a couple of attempts I finally realised that it's able to go into download mode only, I think that means it's soft-bricked right?
So I kept trying to re-install the stock ROM (unroot, unbrick etc) through odin but it kept failing.
I sent the phone to repairs and they wouldn't repair it (because it's rooted obviously, I thought maybe they wouldn't know but of course they did).
I obviously can't get a replacement and start over again because the warranty is void now that I've rooted it
So now they've sent it back and it's currently a paper weight that can go into download mode and refuses to install stock ROMs through Odin.
What do I do? I really need help guys (I don't need to worry about backups because I always backup)
Please answer soon, otherwise I'll be without a phone and my phone company will keep charging me for my contract eventhough I'm not using the phone.
Thanks in advance for any help given
LordwinOfficial said:
Hey XDA guys,
I've got an I8190N
I've got a pretty big problems and I need the help of your big brains.
Well a long time ago (17th September 2013) I posted a thread about a problem with my phone, when I booted up, it had this screen:
*Image should either be here or in the attached thumbnails*
So about 3 weeks ago from today I was trying to install a new CM11 ROM update from Maclaw but after I put the zip on my sd card and booted into TWRP recovery (2.6.3.0, just in case it needs mentioning), the phone shut off in the middle of the installation, I thought it was just the usual bugs I get whilst flashing ROMs so I tried to turn it on and it wouldn't turn on.
After a couple of attempts I finally realised that it's able to go into download mode only, I think that means it's soft-bricked right?
So I kept trying to re-install the stock ROM (unroot, unbrick etc) through odin but it kept failing.
I sent the phone to repairs and they wouldn't repair it (because it's rooted obviously, I thought maybe they wouldn't know but of course they did).
I obviously can't get a replacement and start over again because the warranty is void now that I've rooted it
So now they've sent it back and it's currently a paper weight that can go into download mode and refuses to install stock ROMs through Odin.
What do I do? I really need help guys (I don't need to worry about backups because I always backup)
Please answer soon, otherwise I'll be without a phone and my phone company will keep charging me for my contract eventhough I'm not using the phone.
Thanks in advance for any help given
Click to expand...
Click to collapse
I believe that kies has emergency firmware that you can use to revive your phone? Try that. What does it say when it fails in odin?
hello,
so you can still go into download modus?
try the latest recovery (2.7 if i'm correct...) and flash with odin.
then try to boot into recovery and reflash the latest mclaw (or any other) non stock firmware.
think about it that you have to unzip the odin firmware package you download from maclaws site ( i forgot it and got messing around 2hours ago.... also staring at the erro in odin and thinking W*F is happening :cyclops: but then i realized i need to unzip the package...
realy good luck.....
Hi
Odin flash pit file
It just says the big black FAIL in the red background where it's supposed to be PASS in the green background
Could you guys give me download links to the PIT files, TWRP and the firmwares so I could get the right ones please?
Thanks
LOOK HERE
(i8190_goldenxx.zip) is the pitfile for I8190 only and i8190N_goldenxx.zip for I8190N version
BUT: these are NO flashable files - extract them and choose xxx.pit in Odin.
MJ
Could you give me a link to the pit file please
Do you have a link to the firmware I should use because tys0n gave me one before which was the service firmware (like 1.29gb) but it wouldn't work for this problem
LordwinOfficial said:
Do you have a link to the firmware I should use because tys0n gave me one before which was the service firmware (like 1.29gb) but it wouldn't work for this problem
Click to expand...
Click to collapse
come on boy, it´s really easy to find it, but ok, it´s friday and weekend comes ...
Firmware
Look at the attached files in that post
to flash a pre-rooted, deodexed and zipaligned ROM try this one
MJ
LordwinOfficial said:
Hey XDA guys,
I've got an I8190N
I've got a pretty big problems and I need the help of your big brains.
Well a long time ago (17th September 2013) I posted a thread about a problem with my phone, when I booted up, it had this screen:
*Image should either be here or in the attached thumbnails*
So about 3 weeks ago from today I was trying to install a new CM11 ROM update from Maclaw but after I put the zip on my sd card and booted into TWRP recovery (2.6.3.0, just in case it needs mentioning), the phone shut off in the middle of the installation, I thought it was just the usual bugs I get whilst flashing ROMs so I tried to turn it on and it wouldn't turn on.
After a couple of attempts I finally realised that it's able to go into download mode only, I think that means it's soft-bricked right?
So I kept trying to re-install the stock ROM (unroot, unbrick etc) through odin but it kept failing.
I sent the phone to repairs and they wouldn't repair it (because it's rooted obviously, I thought maybe they wouldn't know but of course they did).
I obviously can't get a replacement and start over again because the warranty is void now that I've rooted it
So now they've sent it back and it's currently a paper weight that can go into download mode and refuses to install stock ROMs through Odin.
What do I do? I really need help guys (I don't need to worry about backups because I always backup)
Please answer soon, otherwise I'll be without a phone and my phone company will keep charging me for my contract eventhough I'm not using the phone.
Thanks in advance for any help given
Click to expand...
Click to collapse
You can go to recovery mode then by using three button combo
if its no working flash it from here using odin
Sorry, it's just not my day, phone breaks, gf breaks up with me because I didn't reply to her because my phone broke lol just ain't able to fix my phone myself like usual, I got a USB jig on the side just in case I need it if that'll be of any help? & Thanks for the links, appreciate the help
Fixed
Thanks guys, the phones fixed
Really appreciate all the help
Hey what's up all. I was listening to music in the car today and my G4 just turned off for no reason. Seems like it is completely hard bricked. I can only get the LG logo and Download Mode. No recovery or even a boot loop. Any options on recovering my data thru ADB or something similar? Can I re-flash the rom over ADB?
I'm really in a tough spot with this, never even heard of a random hard brick happening with this phone or any Android phone. Apparently it is a known issue, I haven't flashed anything in months. I was running stock rooted. Thanks for the help!
you can send it to data recovery lab, ask them to fix it for you. But it may cost you money.
Fix here http://forum.xda-developers.com/tmobile-g4/help/how-to-recover-data-boot-loop-defect-t3297766
- Sorry mods for the second thread, but since it's a solution that worked for me, I figured it deserved its own thread.
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