Develop Bugs

Accidentally Wiped Network. Null IMEI. Uknown Baseband.

Well if you press *#9090#, DO NOT choose option 1 as it will immediately wipe your IMEI and All related network information.
I may have to send my phone out for repair unless anyone knows of a cheap/inexpensive way to fix this problem. I know of a program called Chimera, but it charges €59.90 for the ability.
So currently I have no Network, no IMEI, unknown baseband version and to top it off, my phone reboots after 2 minutes. I've tried Odin'ing back to stock but it didn't work probably because that info I erased is stored elsewhere...
Any ideas?

ZPaul2Fresh8 said:
Well if you press *#9090#, DO NOT choose option 1 as it will immediately wipe your IMEI and All related network information.
I may have to send my phone out for repair unless anyone knows of a cheap/inexpensive way to fix this problem. I know of a program called Chimera, but it charges €59.90 for the ability.
So currently I have no Network, no IMEI, unknown baseband version and to top it off, my phone reboots after 2 minutes. I've tried Odin'ing back to stock but it didn't work probably because that info I erased is stored elsewhere...
Any ideas?
Click to expand...
Click to collapse
nope you'll need to warranty replace i had exactly the same thing happen to me. so to anyone reading this thread pay attention to what @ZPaul2Fresh8 says and be very cautious.

Yup $15 later for overnight shipping and I got a warranty replacement.

What do you do?
ZPaul2Fresh8 You call to service and you said that you would change? They asked you ?

I wiped mine to accidentally and had to send mine to Samsung to be fixed ... they received the phone weds and is know being mailed back to me with a new motherboard ..... they paid for ups 2day air for free both ways ....
This was their finding : Original Problem:
OPERATION SYSTEM ISSUE - PLATFORM / SOFTWARE - OPERATING SYSTEM ISSUE
Problem found:
AUTO POWER OFF W/BATT/TEST CAB - REAR COVER - COSMETICS - KEYPAD / KEYPAD BACKLIGHT INOP
Solution:
REPLACED PBA - REPLACED COSMETIC - REPLACED COMPONENT...

Got phone today
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I did the same thing on my note 2 and bought another device then one day i decided to see if i could fix it. I did alot of digging and fixed it. I wanna say i flashed a stock modem and everything imei and all came back. Its fixable just gotta find the right solution but if warranty fix it then i don't blame you .

today if acted very silly, I read this thread and I dont know for what reason did just what he said I should not do and now I have my note 4 in an infinite loop that doesnt allow to use, I already install the current modem device and still the problem persists. The another problem that I have is that Samsung will hardly support me because I didnt have the bill and I'm in a different country in which the note was sold.

thats happens to my phone, restart every 2 minutes i choose the first option on 9090, cim tryingto flash with odin, but i cant find the right files for this model, can someone help me please to find the rom stock SMN910A????

cybertepache said:
thats happens to my phone, restart every 2 minutes i choose the first option on 9090, cim tryingto flash with odin, but i cant find the right files for this model, can someone help me please to find the rom stock SMN910A????
Click to expand...
Click to collapse
unfortunately flashing with odin wont help the only solution is to send it in for warranty replace.

Note 4
Has anyone found a solution fie wiped imei as a result of messing with *#9090*

sincindy said:
Has anyone found a solution fie wiped imei as a result of messing with *#9090*
Click to expand...
Click to collapse
I know that you are not going to want to hear this but I know someone who can repair it via the Internet. You will need a computer with a USB cable to run to the cell phone.. Email me back if you have any questions [email protected]
---------- Post added at 06:30 AM ---------- Previous post was at 06:29 AM ----------
Aaron. Edwin79m said:
I know that you are not going to want to hear this but I know someone who can repair it via the Internet. You will need a computer with a USB cable to run to the cell phone.. Email me back if you have any questions [email protected]
Click to expand...
Click to collapse
Wow I just noticed how old this topic was lol sorry

[HELP] Please rescue this beautiful phone ( matte black OP3)

Hello everyone,
I'm from Vietnam, & a Op fan since OP1
I want to ask for help from OP3 users and maybe oneplus itself too,
I used a OP3 since last year, but sold it for paid some study fee. It's great phone so i missed itt so much.
Last week I got this phone from a local man, I dont know how he got it, but it's damn beautiful, even it bricked.:crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It suppose to be a prototype/lab-only device with only 4GB of RAM ( picture when it still alive from last owner)
Matte-black back make this phone more and more awesome so i decided to buy it & try to unbrick it
but got no luck, the problem is the device is not be reconigzed by my PC - windows 7 64bit- that should be works fine.
tried every driver from this thread, still no luck :https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
when i hold volume + and stick usb cable
only this for a few second, then no device in device manager
once it appear as QHSUSB_BULK, then disappear
last owner said : he is on stock mashmallow oxygen rom, install this rom without any problems :
https://forum.xda-developers.com/on...device-development/rom-freedomos-1-0-t3409348
but got bootloop when install a nougat-based freedom OS ,( it changed the boot splash )
it will boot a few second then shut down
My current is : only boot a few seconds then shut down,no custom recovery, can enter fastboot but no adb/fastboot with pc, bootloader unlocked.
That's all i can do now, ran out of idea, should it be a hardware issue ? ( ex : bad usb C connectors inside phone itself? )
.
Anyone have ideas ? Please help me, rescue this beautiful phone
Thanks all.

team viewer my friend

Use the unbrick guide and tool

Considering that is factory/lab experimental device, i don't think you should flash a production build made for 6GB ram version. If you hadn't created a nandroid backup of the ROM your device came with, you are pretty much screwed.
Also, why in the world would you spend money on a experimental device when you know there will be no support whatsoever.

abhibnl said:
Considering that is factory/lab experimental device, i don't think you should flash a production build made for 6GB ram version. If you hadn't created a nandroid backup of the ROM your device came with, you are pretty much screwed.
Also, why in the world would you spend money on a experimental device when you know there will be no support whatsoever.
Click to expand...
Click to collapse
Because its freakin matte black... A matte black OP3 is beautiful. He probably paid cheap for it too.

crzykiller said:
Because its freakin matte black... A matte black OP3 is beautiful. He probably paid cheap for it too.
Click to expand...
Click to collapse
Somebody sooooooooo needs to plasti-dip their OP3!

Does it have any recovery at all? Stock OOS recovery? If so, you could try flashing stock OOS 3.x, which should work if it Freedom OS worked on Marshmallow.

Dhairya said:
team viewer my friend
Click to expand...
Click to collapse
thanks you, i will pm' you when i got it back from a local mobile shop. seem they cant do anything w it
thank

Anova's Origin said:
Does it have any recovery at all? Stock OOS recovery? If so, you could try flashing stock OOS 3.x, which should work if it Freedom OS worked on Marshmallow.
Click to expand...
Click to collapse
when i tried to manually enter recovery, it end up with reboot, & without fastboot connection, i cannot flash a twrp :crying: ,

Just flash with MSM DownloadTool and if hardware is ok, phone will boot up.

crzykiller said:
Because its freakin matte black... A matte black OP3 is beautiful. He probably paid cheap for it too.
Click to expand...
Click to collapse
Hmm, if the decision was based on purely aesthetics and looks, i still don't understand why would he attempt to flash the production software on this version. Anyways, i hope a more technically advanced user would be able to help. My knowledge is really limited when it comes to bricked phones.

well my opinion is if it was an experimental model that was released to a very few. then that guy must have been part of the technical crew or software programming crew. so if he messed it up and cant fix it....hmmm i am starting to become worried here

Seem i'm lucky
My friend at local mobilephone store save it!!!
i will take it tomorrow & buy him a beer
He success enter 9008 after a week trying & unbrick it.
Maybe i must make a backup first before get drunk lol

Moto g5 plus id bad key

After trying to return to the original rom the device does not turn on, it always stays on that screen restarting. I've tried several methods and nothing. Can someone help me?
Your device has been unlocked and can't be trusted.
To learn more, visit: motorola.com/unlockbootloader
"ID: Bad Key"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

wagnerwf said:
After trying to return to the original rom the device does not turn on, it always stays on that screen restarting. I've tried several methods and nothing. Can someone help me?
Your device has been unlocked and can't be trusted.
To learn more, visit: motorola.com/unlockbootloader
"ID: Bad Key"
Click to expand...
Click to collapse
Flash Stock Rom And Reloack Bootloader
How to install Stock Rom :- http://ceesty.com/wgKNj2
how to relock bootloader :- http://ceesty.com/wgKMau
How to Remove warning Logo :- https://forum.xda-developers.com/moto-g5s/how-to/remove-unlocked-bootloader-message-moto-t3699273

problem solved, thank you very much.

wagnerwf said:
problem solved, thank you very much.
Click to expand...
Click to collapse
welcome

Hello, y'all. I don't know that I'll get a reply any time soon, as this thread is over a year old, but I am having the same "ID: bad key" problem on my Moto G5S Plus (XT1806) and I have no idea what to do, being that I have not ever even unlocked the bootloader on a phone, as I am having this problem with a phone I bought from eBay that had this issue when I received it.
The full message that displays on my phone is this: "Your device has been unlocked and can't be trusted. - To learn more, visit: motorola.com/unlockbootloader - ID: bad key - Your device will boot in 5 seconds."
For the record, I'm not really concerned with this message being displayed after I restart the phone, as the message goes away after about 5 seconds and the phone starts up properly and is able to be used (*for the most part, with two issues, which I will describe below this paragraph*), it's that the phone will not see any Android updates and is still stuck on these outdated settings: Android version: 7.1.1 - Current version: NPSS26.116-61-8 - Security patch level: April 1, 2018. And I have tried to search for updates with my T-Mobile SIM card in the phone, and also when connected to my home WiFi, but it will not see a new update available.
* The two issues that I referred to earlier have to do with actually making calls on the phone, with outgoing calls taking like 20-30 seconds to actually start dialing and incoming calls not even ringing through to my phone and sending callers straight to voicemail (the phone shows no notification of someone having tried to call me). Text messaging works properly, and I am able to connect to a strong LTE signal with my T-Mobile SIM card in the phone and I can use apps and websites without any issues. However, outgoing calls take much longer to dial out than they should take, and incoming calls will not work at all.
So, I am hoping that flashing a different ROM on to the phone will fix these calling issues and also allow the phone to update to a more recent Android version. However, as I mentioned, I have not ever even unlocked a bootloader, much less, actually flashed a ROM on a phone, so I have no idea what I'm doing when it comes to things this. Also, for the record, I have tried multiple different APN settings on this phone, I have used my T-Mobile SIM card in another phone without any calling issues, and I have done multiple Factory Resets, but nothing has fixed the calling issues or allowed the phone to see any Android updates.
By the way, if flashing a different ROM might be worth trying on this device, being that I would be a first timer doing something like this, how difficult would this be? And about how long should the process likely take?
If anyone has any helpful advice, information or suggestions that they could offer me that might help to fix this issue with my Moto G5S Plus, I would appreciate any and all help that I could get!

If anyone sees this thread and is willing to offer a reply that might help me try to fix this issue with my Moto G5S Plus, I would really appreciate some help with this!

AzAssassin said:
If anyone sees this thread and is willing to offer a reply that might help me try to fix this issue with my Moto G5S Plus, I would really appreciate some help with this!
Click to expand...
Click to collapse
This message means the boot loader is unlocked. Honestly not a huge deal. If you do not plan on using TWRP or Root at all, search the forums on how to relock your boot loader. Otherwise if you wish to use a different recovery or root looks up the logofix which is easy to do. It will have the moto screen, but will say say bad key in small white letters. More thank likely the previous owner had unlocked the boot loader and then flashed it to factory stock before giving it back. That doesn't relock the boot loader so it gives that warning.

One plus 5t root issue on new phone that son has buggered up!

Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse

tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012

Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse

brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.

Yes - He should be allowed to root it again - He needs practice

fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.

First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good:

HTC One E9 plus - dotview

Hello Dears,
kindly help me as my phone after hard reset stuck on dot view mode automaticly and i can't exit it or even setup my phone like gmail or lang ,
after five seconds after make har resest dot view mode apper and i can't exit it ,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Best Regards ,

Redo the hard reset and try again. Also, I suspect that your screen is frozen (watch for changes in dot view mode, like time and battery percentage). It might also be that your tactile screen isn't working anymore and requires a change.

sharvyngunga said:
Redo the hard reset and try again. Also, I suspect that your screen is frozen (watch for changes in dot view mode, like time and battery percentage). It might also be that your tactile screen isn't working anymore and requires a change.
Click to expand...
Click to collapse
Thanks Dear for your replay ,
but the screen is not freezed as i can check my call history and time and battary status ,
also i made har reset and change all frim as i made new flash but problem still exist ,
Regards

Can you share a video of the boot process?
I'll try my best to help you, but I can't guarantee success.

sharvyngunga said:
Can you share a video of the boot process?
I'll try my best to help you, but I can't guarantee success.
Click to expand...
Click to collapse
Thanks Dear ,
i don't have another phone , but i will try to get new one ,
Thanks

Sorry, this is completely unrelated from the current topic but I reallly need help..I tried to flash a rom on my HTC but thr preloader got corrupted xo my phone go hard bricked. Pluging the phone into a computer just shows a red led and the computer shows nothing in device manager.
I tried uninstalling the MTK Preload VCOM driver and reinstalling it but that still didn't work.
Even pressing volume keys while connecting still gave nothing.
I also tried disconnecting the battery and reconnecting the phone to the computer but still nothing.
If there is anyone, please help me.....
I need to unbrick my phone................... I am begging, please help me.

When my E9 got hard bricked, I sent it to a repair shop. They took a long time, but they brought it back to life.
Now, I had a hard brick issue with a Lenovo P1M Vibe (also a MTK device). I solved it using SP TOOL and the proper files. I don't know why the app suddenly decided to detect my phone after dozens of tries. But, during my research, I found interesting articles:
How to get a PC detect and MTK device after flashing wrong ROM/Firmware (Test Point method)
Download the latest & updated stock rom firmware of popular phones like samsung, tecno, itel, infinix, etc with flashing & upgrade tools & instruction
www.romkingz.net
As for the software part of the solution:
[Guide/Info] [How To] Unbrick your Bricked MTK Devices (Dead Brick)
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc) THIS IS FOR INFORMATION ONLY. Q. How Phone gets Bricked? Ans : Basically, phone get bricked during the installation of Android OS (flashing)...
forum.xda-developers.com
You will need additional files for your phone during this process. You can find them online.