BE2026
The stock oxygen OS has a text message bug that apparently isnt fixed yet, so i thought id try a different rom.
I unlocked the bootloader, worked great.
Then i flashed TWRP and it worked great.
I then proceeded to try and flash DerpFest and when the ADB sideload (ACCORDING TO THE DIRECTIONS) was done, it is suppose to reboot into the new os. but I get nothing.
So Ive tried, a bunch of stuff. I tried using orangefox and it doesnt support SD cards and the sideload option just crashes. So then i try TWRP recovery instead of billies recovery and when i select the image to install in TWRP, and then 'swipe to flash' TWRP instantly resets. and nothing happens.
So then i tried the MSMdownloader tool and it will not recognize the phone at all. all adv and fastboot commands work great.
Can someone help me?
I tried switch A or B, and flashing both,
I tried to go back to stock and i cant even get that to work.
Help meh please, i just bought this phone and now i cant even use it
I also cannot get the MSMdownloader to work. it shows my phone on the list in EDL mode. but com port is empty. device id is empty. all the fields are empty and it just says waiting on device. nothing happens.
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
arda99 said:
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
everyone comes up as it should in the device manager. sad face....
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
SomeRandomGuy said:
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
Click to expand...
Click to collapse
OH wow it did. Thank you, the documentation for that side of MSMd is vague. So after trying like 3 different "qualcomm" drivers I finally got it to work! As in the stock android 10 is loaded and the phone is no longer bricked. However, when I try the same methods again to actually put a custom rom on this phone the same thing is still happening.
No matter what OS i try to flash, no matter what mode or slot, or what recovery 'program' i use like twrp or orange FOX, nothing seems to actually boot into an OS. it just loops into Fastbook.
Can anyone help me? I dont want to use oxygenOS
I had a somewhat similar experience in loading custom ROMs, and simply took to de-bloating the stock image (emphasis on de-google-services, de-OnePlusSpyware, and de-auto-OTA). Still not really happy, compiling AOSP source now to try to swap out some of the system APKs that annoy me for customized ones. If there are only a few things that sour you to OOS, maybe I (or others) can help cure those? Debloat and replace...
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
So the main reason for me not wanting to use Oxygen OS is because when initally setting up the phone, everything works great. for about 2 or 3 days. then for what ever reason i cannot receive text messages. If I factory reset the phone, or put my simcard into another telephone all of them come rushing in.
In the event of me factory reseting my phone, ill get text messages from 3 or 4 days ago.
and it always works. as soon as my friend is texting me and i dont recieve it, i just factory reset then boom its there.
I tried everything, different SMS apps, update this, android 11 that. it always did it to me, like clockwork. like the phone installs an update and breaks text messages. I tried contacting oneplus customer support but that shhit is a joke. they told me they are aware of multiple isolated incidents about this and that the only thing to do left is to send it in. I JUST BOUGHT THIS THINg, im not about to send my device away, right after paying for it. I paid you guys $400 just to NOT have a telephone for 8-16 weeks?
SomeRandomGuy said:
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
Click to expand...
Click to collapse
See thats the thing, Ive never gotten another room, to boot. at all. no splash screen, no bootlogo nothing. it always just goes back to fastboot. it never tries to boot an OS. i follow these billie instructions and nothing happens. its the same result. I have tried all the different versions in this forum. from pixel experience to derpfest. all work great, untill the very last step where they say side load rom/flash and then reboot. your new os should be booting! and it doesnt.
Wow, that's a new one for me. I wish I knew more about the internals (slowly learning) to help troubleshoot. I would GUESS that if you can change phones (e.g. you said you can put the sim in a new phone, and get a backup of messages delivered), that it isn't so much that the phone is dropping them as it is not getting them in the first place.
With no guarantees- this is a SWAG- have you checked your APN settings? Most definitely, these come through as part of a new registration (duh), and consequently can get messed up for $diety knows why later... but at least you may be able to get a known-good set of settings (post reset, post registration) to compare to after terrorists strike and you are no longer getting messages. It should be easy to add a new APN with the "right" settings and manually select it.
If it is something like that, odds are an alternative ROM would just do the same thing; I assume there's some kind of handshake standard for initialization of the carrier network. I'm on TMo and happy to share my settings, if it helps....?
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
arda99 said:
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
Click to expand...
Click to collapse
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
agentruley said:
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
Click to expand...
Click to collapse
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
I had to go through the setup process again. First time the DF just didn't catch. I read ADB sideload can be broken as **** sometimes.
arda99 said:
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
Click to expand...
Click to collapse
Sadly this has nothing to do with my problem. Installing newer/ using older versions do not change the behavior.
The phone breaks as soon as I go back to the "Google Assisnt" -Setting up your phone for the first time- wizard and instead of selecting "Remind me tomorrow" i select next, and then the following screen says "Installing updates" and then the telephone will no longer recieve text messages. Does anyone have any help?
Oneplus customer service is terrible and they told me to buy another device.
This is the last phone i will ever purchase from them
Related
Does anyone know a way to know if an sms has indeed been sent away? some Sms's just don't arrive and there is no notice to confirm the fact that it was sent off.
Lionel,
Pocket PC 2003 solves this. It displays a little message bubble when a message has been successfully sent.
I have seen that in Pocket PC 2002, if I write and send a message and turn off the display before the message leaves my phone, it will never go. But it will give you the error messge when you go back into your SMS's.
Regards
Keith Burke
Dublin, Ireland
many thanks, so I guess I'll have to get pcc 2003!
greetings,
Lionel
And you can cook it up from here
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Go for the 4.00.10
Best of luck
Hi Ranger,
Can I be sure everything will work all right by upgrading to 4.00.10? I read quite some comments about a series of problems and some people going back to previous versions. Isn't it going to bust up my phone settings in Belgium? Someone wrote not to do any upgrades unless your an expert technician.
2. If I do go on with the upgrade can I just use sd-backup and get my stuff back from Sd-card? Isn't that going to restore my old system?
3. I don't know anything about technics. Most of the options on http://cuba.calyx.nl/~jsummers/ROMkitchen/ sound like Chinese to me.
Sorry for all the dumb questions, but I want to make sure I'm not going to run into trouble.
Hi Ranger,
I decided to run the risk anyway. I can probably do a hard reset and backup if I get into deep trouble.
I went to your link, but as I am a complete beginner at this, I got stuck after 'building the rom now'! I asked for the 'Installer.exe' but couldn't find it on my pc. What shoud I do?
greetings,
Lionel
Ok, first off. Back up your XDA ROM to your SD card. I've never done this, but I'm sure once this is done you can copy it to your desk top.
Secondly, yes there is a possability that it will kill your phone. See http://www.xda-developers.com/forum/viewtopic.php?t=1624
But I have never had a problem, once I stick to my golden rule. Close EVERY PROGRAM that you possibly can while doing the upgrade. And son't touch your computer while it is doing it as well. It's a tiny price to pay. If you're using USB it shouldn't take more than 5 minutes. With Serial cable, I heard it can take upto 20 minutes, maybe more.
As far as downloading it, after you've selected the options in the ROM kitchen [whici belongs to Jeff Summers by the way, not me ] make sure that the bar up the top is still green, NOT RED.
Next, down the bottom there are three options. For yourself, choose the EXE file. After a few seconds, might take upto 30 seconds, up the top of the screen will be a button to down load your file. Just save it somewhere on your computer and run it.
Make sure that your phone is in it's cradle which should be conntected to your computer [or connect the phone to the computer with a serial or usb cable]. Also make sure that the power cable is plugged in.
I think some people have advised taking out your SIM card but i never have.
That should be it.
Let me know either way. If it messes up, just pray that it's after 5% or 10%, so I hear. If so we can try the second option.
Regards
Keith Burke
Dublin, Ireland
One last thing. Take a note of your Network provider settings [GPRS etc...] before you upgrade. They will not be in the new 2003 image.
I forgot when I was doing mine and no longer have my GPRS settings
Hi Keith,
I'm trying it out right away. I have the backup on the sd-card, so that should work fine.
Just be careful with your SD card. I have heard a few reports that it sometimes gets erased in the PDA. Can't remember when or where but if you search the forum you might find it.
Good Luck. It's worth it.
if all you need are sms delivery reports, just click on options when in the compose sms screen and then click on delivery reports, unfortunately you have to do this for every sms as there doesnt seem to be a way to switch it on permanently.
ranger said:
And you can cook it up from here
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Go for the 4.00.10
Best of luck
Click to expand...
Click to collapse
Does this have a radio update ?
Regards
René
Hi,
I've been trying to cook about 20 times since the 1. of August. Tried about everything. Tried all the roms, with and without adding software. Turning off my firewall. Trying all the Rom's. No other programs running.
This is what happens every time:
After selecting the items, I choose the 'install.exe' option and choose 'build rom now'. It starts doing 'something'. I have ADSL and after about 10 seconds the blue bar at the bottom is completed. At the top of the window in the yellow background it keeps saying
'Creating rom... Please be patient
copying rom Files
running mkrom
even after waiting for 30 minutes nothing more happens.
What am I doing wrong?
greetings,
Lionel
Radio Upgrade
@rk
No.
There's no Radio Stack Unit (RSU) Upgrade integrated.
As it depends on the location, where you live, be carefull, which you choose.
For me living in (good ol') Europe the RSU 4.21.00 from O2 UK webside is working.
My native language is Greek and naturally I send Greek sms.
The only problem is that XDA sends them using Unicode character set meaning that over 70 character messages will be splitted.
Does anybody know of any solution on this issue?
I have an O2 payg sim card, even though I ask for delivery reports on sms each time I dont get them, reason being the remaining balance comes in as an sms which cancels the process somehow. Has anybody got a solution to this?
regarding the last, on o2, put *0# in the subject line, and the main sms in the body.
neil
ukneil said:
regarding the last, on o2, put *0# in the subject line, and the main sms in the body.
neil
Click to expand...
Click to collapse
Thank you very much, that worked a treat, I was told by somebody to put that *0# before the fone number, no wonder it didnt work, thanks again.
Hello Everyone,
I just got the Samsung Galaxy Nexus last night, and it is awesome. My old Eris will now be used as MP3 player, Games, and Camera. I used one click root to root the phone. Now I would like to install CyanogenMOD 7.2.0-RC0 Gingerbread NIGHTLY for the HTC Eris. I have the full version ready and on the SD card. The instructions say that I need to wipe the phone completely (Factory Reset). I did a factory reset before I even attempted to root it, because I wanted to start from scratch. The problem I ran into was that after the factory reset, I couldn't use the phone until I activated the phone with Verizon (by dialing *228 to program the phone). The Verizon tech support had me activate the phone with one of my other add-on phone numbers to get past this, then reactivate the number used, back to the correct phone. My question, is this going to happen if I flash this ROM to my Eris? I'm no longer going to use the Eris as a phone anymore, so I don't need it activated, I just want a cool multimedia device for music, apps, pictures, and web.
Thanks to Everyone who makes this possible.
You just tap for corners of the screen clock wise starting from top left whenever the setup screen comes up on the first boot
Sent from my Galaxy Nexus using XDA App
Yes, on the CM7 ROMs, the tap the four corners works.
However, if you ever need to reinstall stock, you can get by activation in one of two ways:
This: http://androidforums.com/eris-suppo...help-getting-pass-activation.html#post1991633
Or, easier, have it dial to activate, but immediately disconnect. It will try about three times, so have it dial and then disconnect right away each tome. It will then give up and put you through to the initial setup screen without activation.
Well there is a 'Wifi Script' made by CondemnedSoul that turns the Eris into a wifi phone only; I haven't got much in detail, however, if you check it out it might incite you to use it. Also, from the comments in that thread, it seems that the script is remunerative.
Hope this helped
So let me begin by saying the phone in question is a Kyocera Echo for Sprint. Yes, everyone hates it, yes we already know most believe it was a flop. But, I have one, it's been messed up for months and it's driving me nuts because I can't figure it out. I've been to three sprint stores and have talked to countless reps who have no idea. I thought I might be able to throw this out there and get some ideas from you guys on what you think it may be and possible solutions.
Long story short, on Froyo the phone works fine. If I attempt to upgrade, whether I revert to stock or remain rooted... all attempts of an ota fail with an error code. Usually the phone will still run, occasionally it'll boot loop. Now if I flash any version past Froyo, everything on the phone works fine except messaging. If I attempt to send a text message, it just says sending below it and stays that way like it's doing nothing. If someone sends me a text I never receive it.
I have flashed every variation of recovery and roms, stock or otherwise and it's a no go. It can't be a hardware issue because it works fine in Froyo. I've tried using alternate messaging apps.. handcent, gosms.. same thing, just sending.
I've flashed the hell out of this and am out of ideas. I don't know what goes on behind the scenes of the stock messaging app and how to tell what is causing it to hang. Is the Gingerbread messaging app identical to Froyo? Can I somehow pull the Froyo messaging and put it into a Gingerbread rom? Any thoughts or suggestions would be greatly appreciated.
I have been rooting and installing custom roms for a while. I'm no expert, but now newb either. I recently rooted my S4. It's running on the stock verizon ME7 build.
The problem I have been having is that a few minutes after I reboot it all the sounds stop working. No music, notification or in call sounds. If I restart it goes away for a little while, but soon comes back. I tried factory defaulting it, which worked for a little while, but it recently started doing it again. The only thing I can think of is I installed avast Anti-theft with root access recently. Has anyone else had this problem & do you know of a solution? I can always try factory defaulting it again to see if that helps, but I would like to know if anyone else has any ideas.
Odined back
I tried everything I could thing of, then decided to Odin back to stock. Same problem started almost immediately . There are no system sounds and I can not hear anything when I call. Also it does not pick up sounds from my voice via voice commands & the person on the other end of my calls can not hear me. At this point I wonder if blocking is some how activated. Since Verizon was nice enough to prevent me from making changes to it I can't check.... Upwards on onward. I will keep this updated in-case someone else has this problem.
I have noticed that when I am in recovery, if I try to wipe the cache partition. I get a android on his back with a triangle exclamation point & then it reboots itself... Is this normal. I have never experienced this behavior before.
I installed the blocking mode MOD. It does not seem to be the problem. No sounds after using the phone for a few minutes. I guess its time to send it back. I really enjoyed the phone. But I seems like a received a bad one. Unless anyone has anythoughts.
When your sound stops have you tried to see if it is working with headphones or Bluetooth? If there is no sound using headphones or a Bluetooth device there's probably an issue with the phone itself. If you've done a stock Odin flash and its still doing it, I would have to guess the phone is bad. Send it back. The only problem you might have is if they check the flash count, you may end up paying for a new phone. I've never had to use Triangle Away to reset my flash counter, but I believe it needs to be flashed in a custom recovery (which you don't have).
Sent from my SCH-I545 using Tapatalk 4
phone: Samsung Galaxy s9+
android version: 10 (upgraded from 9, pushed out by tmobile)
one ui version: 2.1 (also pushed out by tmobile)
model #: sm-g965u1
Since the 7/1/2020 update, I get a notification from omadm that a firmware update is not complete. This notification cannot be dismissed, and omadm cannot be disabled. auto retries every 60 minutes.
Also, I get another notification that wakes the phone up every 60 minutes
"Attention android update is successful" I will get this same notification again in 60 minutes.
The phone was never rooted by me. But I did buy it used off of Amazon. Phone was working fine with android 9.
I'd just like to stop the notifications. Except for the notifications, the phone works. I can make and receive calls, texting works and I can browse the web. All of my apps work.
Does anyone know how to stop the notifications?
I've already tried removing my sim card. This doesn't do anything.
I had the same problem with an unlocked used S10+ I purchased on Amazon. I had to send it back for other reasons but I got similar notifications. This seemed to work for some people:
SOLUTION (AT LEAST WITH MY GALAXY NOTE 10 +)
Had the same problem on a Samsung Galaxy S10 and here's the solution that seemed to work:
Go to 'Settings' > 'Software update' and hit 'UICC Unlock'
It loads for a moment, then says SIM Restricted... Hit 'OK'
It takes you back to the 'Settings' > 'Software update screen'. Hit 'Download and install'
It loads for a moment, then says Your software is up to date...
Then open that notification saying the profile didn't update.
It loads for a minute, then says Profile updated... Hit 'OK'
It loads again for another minute and says something similarly. Hit 'OK'
Click to expand...
Click to collapse
https://support.google.com/fi/thread/56884144?hl=en&msgid=66380028
If you find a solution that works let me know b/c I'm still interested in getting an newer galaxy phone.
shady909 said:
I had the same problem with an unlocked used S10+ I purchased on Amazon. I had to send it back for other reasons but I got similar notifications. This seemed to work for some people:
https://support.google.com/fi/thread/56884144?hl=en&msgid=66380028
If you find a solution that works let me know b/c I'm still interested in getting an newer galaxy phone.
Click to expand...
Click to collapse
This did not work.
wiping the cache did not work
resetting the phone did not work.
Every hour, the phone wakes up on it's own and does the failed to update thing.
I'd root the phone, but I found out the phone is basically unrootable
It's crap like this that makes me HATE androids, not that Apple is any better. Apples are basically built for morons.
BTW, I did not see what is posted in the above fix. It makes me think some guy put that on his website just to get clicks for the ads on his page.
I tried flashing, this did not work either. As soon as you accept any update from your carrier you get this error back. In my case initially, flashing the stock firmware seemed to work. I did not see the error. But the first update that T-Mobile sent to me was the time zone update, which I got After flashing the phone with the latest stock firmware from sammobile. As soon as I accepted that update, the error came back.
someone in the T-mobile forums suggested using ADB to remove omadm. This can be done as a standard user, apparently, something I did not know.
linking back to the original forum post on this site:
https://forum.xda-developers.com/showpost.php?p=77194732&postcount=11