Related
I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Jtag
Hey buddy i recent hard bricked mine last month got it back today PM this guy tomy1986.nt only charged 25$ and had it back in 7 days sucker working good now hes in texas only cost me 5.80$ shipped from Phx Az hope that helps Sounds like a defint hard brick!!!
JahJahLoO said:
I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Click to expand...
Click to collapse
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Praise!
tomy1986.nt said:
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Click to expand...
Click to collapse
All praise Tomy for his swift and kind work in helping a poor Samaritan. Thoust good deed shant go unnoticed.
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
-DarkKnight- said:
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
Click to expand...
Click to collapse
Good morning guys
tomy1986.nt said:
Good morning guys
Click to expand...
Click to collapse
How would I prevent my device from getting bricked?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
Do not flash modified Rom. :laugh:
tomy1986.nt said:
Do not flash modified Rom. :laugh:
Click to expand...
Click to collapse
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
-DarkKnight- said:
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
Click to expand...
Click to collapse
Alway flash phone with Stock rom.
tomy1986.nt said:
Alway flash phone with Stock rom.
Click to expand...
Click to collapse
What about custom ROMs like cm10.1 or JediMindTrick?
I'M BATMAN
The note 1 SGH-i717 of Keith_Dallas,TX member has already fixed today give it back only about a hours.
So A new update for HTC sense came out this morning. And now my phone refuses to connect to wifi I already reset it through the soft ware then I did a Hard reset using the power button and still. Won't connect to a wifi help????
Also the device is now never able to mount and make the storage accessible
M1keILL said:
So A new update for HTC sense came out this morning. And now my phone refuses to connect to wifi I already reset it through the soft ware then I did a Hard reset using the power button and still. Won't connect to a wifi help????
Also the device is now never able to mount and make the storage accessible
Click to expand...
Click to collapse
You are not even close to being bricked.
You'll have to give me more information if I'm going to be able to help you. I assume you're rooted. Are you running a custom ROM or stock? Custom recovery? Have you updated your firmware by flashing a file?
When did you first notice you didn't have wifi? Did you do any mods around that same time?
Don't worry dude, we'll get this fixed.
xunholyx said:
You are not even close to being bricked. .
Click to expand...
Click to collapse
Yeah I don't know where these guys get their definition of "bricked" from. Phone still works but no wifi "BRICKED!!!". As far as I'm concerned a device is "bricked" if it's about as useful as a "brick" in other words, it ain't doing sh!t. You can only use it to keep the door from slamming shut, or as a paper weight.
Completely dead = Bricked
Can go into recovery/bootloader = Not even close to anything related to any "brick"
BerndM14 said:
Yeah I don't know where these guys get their definition of "bricked" from. Phone still works but no wifi "BRICKED!!!". As far as I'm concerned a device is "bricked" if it's about as useful as a "brick" in other words, it ain't doing sh!t. You can only use it to keep the door from slamming shut, or as a paper weight.
Completely dead = Bricked
Can go into recovery/bootloader = Not even close to anything related to any "brick"
Click to expand...
Click to collapse
Not rooted nothing custom. I am bone stock sprint htc one m8. It gave me a prompt to update sense then it stopped working
M1keILL said:
Not rooted nothing custom. I am bone stock sprint htc one m8. It gave me a prompt to update sense then it stopped working
Click to expand...
Click to collapse
That is super weird dude. I would call your service provider or HTC. If you call them on a landline, they can probably push a fix directly to your phone. If you don't have a landline, they will guide you through the steps to fix it.
If it is having issues when it is unmodded and because of an OTA, you don't want our advice. You would have to modify your phone and void your warranty.
There may be/probably is a solution that someone here has that will fix it, but your best bet with 100% stock is to go to the source for a fix.
Good luck buddy!
xunholyx said:
That is super weird dude. I would call your service provider or HTC. If you call them on a landline, they can probably push a fix directly to your phone. If you don't have a landline, they will guide you through the steps to fix it.
If it is having issues when it is unmodded and because of an OTA, you don't want our advice. You would have to modify your phone and void your warranty.
Good luck buddy!
Click to expand...
Click to collapse
Alright thanks i'll try tomorrow then
M1keILL said:
Alright thanks i'll try tomorrow then
Click to expand...
Click to collapse
Let me know how things go. You can quote me here (so I get a notification), or send me a PM. I'm interested in hearing about your results and the fix, in case anyone else on this forum comes across these same problems.
xunholyx said:
That is super weird dude.
If it is having issues when it is unmodded and because of an OTA, you don't want our advice. You would have to modify your phone and void your warranty.
!
Click to expand...
Click to collapse
I've seen a couple cases of OTA killing WiFi lately. Most of us are used to seeing broken WiFi as a result of flashing a custom ROM and outdated firmware, so yes its a bit odd to see it after an official OTA.
I agree, that aside from trying a factory reset, the OP shouldn't tinker with a phone that is stock and still on warranty. Just contact your warranty department for a repair/replacement.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
M1keILL said:
I already reset it through the soft ware then I did a Hard reset using the power button and still.
Click to expand...
Click to collapse
"Reset" or even "hard reset" is a bit vague. Did you do a factory reset to delete user data, or just rebooted the phone? Factory reset will sometimes clear up random bugs after an OTA.
Sprint has basically said that they don't know what's wrong with it and I need to send it to them.
M1keILL said:
Sprint has basically said that they don't know what's wrong with it and I need to send it to them.
Click to expand...
Click to collapse
For a stock device (not modded) if you've tried a factory reset, and the issue persists, they I would agree that warranty service is the best solution.
Looking for a little help...... I have a rogers lg g3 and I was told it was on lollipop.. Now my problem is that I can't access the (settings/about phone) without it telling me (unfortunately settings has stopped working) my question is has anyone had this problem and is it possible to fix it? Please anyone
Blackfox123 said:
Looking for a little help...... I have a rogers lg g3 and I was told it was on lollipop.. Now my problem is that I can't access the (settings/about phone) without it telling me (unfortunately settings has stopped working) my question is has anyone had this problem and is it possible to fix it? Please anyone
Click to expand...
Click to collapse
A factory reset usually fixes those sorts of problems.
Keaganvdh said:
A factory reset usually fixes those sorts of problems.
Click to expand...
Click to collapse
That's what I thought as well so I did a factory reset and a hard reset with the same outcome... Everything in the settings can be accessed except the (about phone) so I'm completely lost on what to do
Blackfox123 said:
That's what I thought as well so I did a factory reset and a hard reset with the same outcome... Everything in the settings can be accessed except the (about phone) so I'm completely lost on what to do
Click to expand...
Click to collapse
I think it's best you send it back to where you got it then and let them have a look. Otherwise you could try flashing your original firmware again incase your current one has missing components.
Keaganvdh said:
I think it's best you send it back to where you got it then and let them have a look. Otherwise you could try flashing your original firmware again incase your current one has missing components.
Click to expand...
Click to collapse
Send it it back is definitely not going to happen cause I've tried that lol... But to flash the firmware wouldn't I need USB debugging checked? I hope not cause i can't get to it and is there any tutorials that could give me a step by step instructions?
Blackfox123 said:
Send it it back is definitely not going to happen cause I've tried that lol... But to flash the firmware wouldn't I need USB debugging checked? I hope not cause i can't get to it and is there any tutorials that could give me a step by step instructions?
Click to expand...
Click to collapse
This is the guide I use when flashing my stock ROM. Link
If you live outside the US then use the KDZ method.
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
I request all to first please understand the problem and give me suggestions as this gets slightly bonkers.
Thanks in advance.
So I had my OnePlus3 A3003 repaired for water Damage from a professional non OnePlus service called Yaantra. They basically replaced the Mother Board is what they say.
I have no reason to doubt, the Phone works flawlessly, everything is working nicely, from the camera to the battery performance and charging and SOT, the performance is as expected.
Only it runs on Oxygen OS 3.1.2.
Now I first got an OTA update notification for 4.5.1 and I immediately started downloading and attempted install. It went through the whole cycle of installing smoothly and after the first reboot, it splashed a linux Penguin Logo and then turned off, never turned back on. I manually pressed the power button after a long time but it again showed the Penguin for a few seconds and powered off. I figured that the phone is bricked. (this time my boot loader was Locked)
I had to follow the 2nd Method of the Mega Unbrick guide and got my phone up and running back on 3.1.2
I still get the OTA update but this time i thought I'll download the latest stable build of 5.0.1 and install it via ADB sideload. with the appropriate recovery
The phone got bricked again.
Then I thought of Installing regular TWRP after unlocking bootloader and flashed 5.0.1, No luck. had to unbrick it again.
Then I tried bluspark.
Then I flashed Experience OS with the latest firmware. It went through the entire cycle and installed but this time after it turned off and on again I was greeted to a new error.
it was in red saying "Battery does not match" in English and then in some Asian language. I was able to unbrick from that state as well.
After that I have tried Lineage OS but with same result. I get "Battery does not match"
Then I unbricked the device and i tried #*808# and checked Charger option. it says "itech_3000mah" that doesn't sound original, is it?
Basically no matter what I flash my phone gets bricked.
With Custom ROMs I get the "Battery does not match error"
With Official ROM I get the penguin Logo.
I've tried all sorts of Combination of Recovery and ROMs to no luck.
So far the only thing I haven't tried is flashing another Kernal.
Have to come back to 3.1.2 after unbricking which works flawlessly every time with no problems AT ALL. I wish to upgrade to the latest Official build of OOS (but i am ok with unofficial as well)
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
thes3usa said:
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
Click to expand...
Click to collapse
Thanks for the eyeball
AbhiM7 said:
Thanks for the eyeball
Click to expand...
Click to collapse
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
AbhiM7 said:
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
Click to expand...
Click to collapse
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
SivaMaxwell said:
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
Click to expand...
Click to collapse
I am downloading this msm recovery
https://forum.xda-developers.com/on...k-phone-msmdownloadtool-v3-0-6-t3575801/page2
and try for now.
I'll post my experience soon.
An official technician from OnePlus told me that fake batteries don't work well / won't find with OnePlus at all so there is 99% chance that it's not a mock-up.
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
zelendel said:
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
Click to expand...
Click to collapse
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
AbhiM7 said:
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
Click to expand...
Click to collapse
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
zelendel said:
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
Click to expand...
Click to collapse
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
AbhiM7 said:
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
Click to expand...
Click to collapse
That depends on how good they are but to be honest if it is a really good fake then it may fool even the best. But it cant hurt.
Actually I got stuck in the same situation. I also tried different ROMs but with custom ones I get the Replace Battery error and with official Roms I get the penguin. Is there any way to get rid of the Battery error by modifying the kernel or something?
You've a motherboard of OP3T not OP3
Try oneplus 3t full ota
Cheers