Develop Bugs

****ed up my P8000

Hello XDA, this is my first post, this comunity is awesome and helped me a lot for a couple of years now.
there always seems to be a solution to everything!
but now i realy ****ed up. i accidentaly checked the wrong thing on the so called "smart phone flash tool"
i klicked firmware upgrade instead of download only.
is there any way so rescue my phone? thank you very much in advance! :crying:
here is a screenshot: (i cant paste link because i am new):crying:

I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!

charliepie said:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
Click to expand...
Click to collapse
there probably is SOME way to fix it, i am sure, but the phone does not even boot into recovery.

Mediatek phones are hard to brick, haha
It is PROBABLY going to give a headache in order to find the needed files, flash the stuff again and etc using the proper way, but PROBABLY your phone will relive again. Try rooting and installing Eragon after a full wipe, if that option is available.

You may look here:
Bricked P8000
This may help.

I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!

abubakar486 said:
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
Click to expand...
Click to collapse
hi, thank you; but my phone does not even boot. it gets recognized by the pc though

New problem
OKAY now i got everything working so far. but there is a new real big problem. it has some kind of imei error so it doesnt let me use data on the way
how can this be fixed? i mean, i have the correct imei s right here whith me.
thank you in advance.

Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?

FIXED
charliepie said:
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
Click to expand...
Click to collapse
Hey! i fixed it. again fith XDAs help
http://forum.xda-developers.com/canvas-a1/general/fix-imei-perfect-fix-android-imei-t2943567
solution 2 worked for me.
Also i have a new problem. when connecting my bluetooth speaker it says...well maybe this belongs to another forum :good:

getting "your device is corrupt and cannot be trusted pixel"

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.

urgent please

hi
i flashed pixel custom rom 8.0.1
and i want to back to stock rom
and after flashing ended
my moto g5 does not open
and i cant access to bootloader
and when i press power button nothing happen only black screen
and when i connect g5 wih pc i hear a sound of connect but still black screen no charging percantage
what is name of this problem and what is the solution please ?????

Man, i have the same problem... i tried several methods until jtag and without success ...
just a miracle!:chorando::chorando::chorando::chorando:

begamal said:
hi
i flashed pixel custom rom 8.0.1
and i want to back to stock rom
and after flashing ended
my moto g5 does not open
and i cant access to bootloader
and when i press power button nothing happen only black screen
and when i connect g5 wih pc i hear a sound of connect but still black screen no charging percantage
what is name of this problem and what is the solution please ?????
Click to expand...
Click to collapse
It's called a hard brick
Current solution is a motherboard replacement
There are no blank flash files currently (and probably never will be) for this device
In future never flash the bootloader part of a firmware or repartition a device unless you know what you are doing

silasmvg said:
Man, i have the same problem... i tried several methods until jtag and without success ...
just a miracle!:chorando::chorando::chorando::chorando:[/QUOTWHAT DID YOU DO ?
Click to expand...
Click to collapse

begamal said:
silasmvg said:
Man, i have the same problem... i tried several methods until jtag and without success ...
just a miracle!:chorando::chorando::chorando::chorando:[/QUOTWHAT DID YOU DO ?
Click to expand...
Click to collapse
A few days ago I watched this tutorial from a damn here in Brazil, but he does not know how to explain correctly, or I'm stupid to understand. I tried his method and did not succeed.
People here commented that he succeeded.
But I can not send the links here. I get a flood protection message for new users.
If you want to call me on linkedin or in the email I can send the link of the tutorial that is on youtube that I could not do correctly for not understanding, but maybe you can understand better and could help me.
[email protected]
linkedin: in/silasmvg/
Click to expand...
Click to collapse

silasmvg said:
begamal said:
A few days ago I watched this tutorial from a damn here in Brazil, but he does not know how to explain correctly, or I'm stupid to understand. I tried his method and did not succeed.
People here commented that he succeeded.
But I can not send the links here. I get a flood protection message for new users.
If you want to call me on linkedin or in the email I can send the link of the tutorial that is on youtube that I could not do correctly for not understanding, but maybe you can understand better and could help me.
[email protected]
linkedin: in/silasmvg/
Click to expand...
Click to collapse
check your mail
[email protected]
Click to expand...
Click to collapse

Phone gets bricked no matter what ROM and recovery is flashed, stuck on 3.1.2 OOS

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

Question my mobile network keeps resetting when downloading something after rooting with magisk

i recently flashed magisk on this phone through odin methodm it works. but my mobile network keeps resetting. i havenno idea why. as soon as i download something or do normal tasks it just diesm i haven no idea on what's going on.

UPDATE: this problem still exists after uninstalling magisk. what happened? i am gonna try to flash new firmware and see if something happens

Update: please someone help me. this is getting annoying i don't know what to do. please. i have finally found my perfect non laggy rom! which is stock. but the mobile data glitch is just... i attached the video below. please someone. if you want logs i can give
Your browser is not able to display this video.

Captain_cookie_200 said:
Update: please someone help me. this is getting annoying i don't know what to do. please. i have finally found my perfect non laggy rom! which is stock. but the mobile data glitch is just... i attached the video below. please someone. if you want logs i can give
View attachment 5691215
Click to expand...
Click to collapse
I connected my laptop to the hotspot while taking a class. and my mobile service just disspears as you can see

is someone gonna help me with this? i dont see anyone else having this problem. nor am i getting answers from anywhere. I am just stuck with unoptimised laggy GSI'S? rip me.

Hello mate sorry for the wait, https://forum.xda-developers.com/t/fixed-rooted-a325m-suddenly-no-imei-no-sim.4386753/post-86588571 here the solution, have a good day

i actually followed that tutorial deleting the imei many times but the problem always presisted. like 5-15 times

Same thing happening, also using the same phone. This is insane
Captain_cookie_200 said:
i actually followed that tutorial deleting the imei many times but the problem always presisted. like 5-15 times
Click to expand...
Click to collapse
I also followed the same tutorial, but the issue still persists.

Franzyy said:
Same thing happening, also using the same phone. This is insane
I also followed the same tutorial, but the issue still persists.
Click to expand...
Click to collapse
i would just recommend switching to GSI at this point if you really want the mobile data back. i dont think this is going to be fixed till the next firmware update. GSI fixes this. i am personally using crdroid 8.8 it works the smoothest out of all of them. the battery drain is an issue but i can live with it. i dont think samsung is going to push out a firmware update soon. i bet they dont even know this issue exists in the firmware. this is why i never wanted to go with a midranger from samsung. they dont care about us. well.

Captain_cookie_200 said:
i would just recommend switching to GSI at this point if you really want the mobile data back. i dont think this is going to be fixed till the next firmware update. GSI fixes this. i am personally using crdroid 8.8 it works the smoothest out of all of them. the battery drain is an issue but i can live with it. i dont think samsung is going to push out a firmware update soon. i bet they dont even know this issue exists in the firmware. this is why i never wanted to go with a midranger from samsung. they dont care about us. well.
Click to expand...
Click to collapse
For the battery drain you can try reset battery info with ACC, stratophere x performance or root essentials (deprecate)

Franzyy said:
Same thing happening, also using the same phone. This is insane
I also followed the same tutorial, but the issue still persists.
Click to expand...
Click to collapse
What did you do? it made my imei dead but the tutorial fix it.
Did you put the imei folder in RO and activate offline mode and flash stock?

kilam9900 said:
What did you do? it made my imei dead but the tutorial fix it.
Did you put the imei folder in RO and activate offline mode and flash stock?
Click to expand...
Click to collapse
I fixed it by installing a custom rom.

kilam9900 said:
For the battery drain you can try reset battery info with ACC, stratophere x performance or root essentials (deprecate)
Click to expand...
Click to collapse
can you link me to those and instructions?

Captain_cookie_200 said:
can you link me to those and instructions?
Click to expand...
Click to collapse
of course,
ACC u just have to select the number on the CLI, juste type acc on termux and select the option (if u have unzip error with the module, just unpack and repack)
Stratosphere : The module, just type su -c strpmenu in termux and choose the option for reset battery
Root essentials : The app, just install it and select the option
I think the best and easiest way is Stratosphere
(For all of this, you need to charge your phone at 100%)