Any help here would be much appreciated. I have lost mobile signal altogether . Since fist rooting and flashing roms on my galaxy s3, I've never been faced with a problem that i can't fix. there's been some hairy moments but in this case i'm truly stumped. And I hope someone here can help.
I have been switching between Stock, Havoc, Omni, PE and Evolution X since I Got my OP a couple of months ago. I thought i'd try the latest developer preview. Had it running great for a day and decided to root it when i got home from work. If memory serves, I booted twrp, flashed twrp, rebooted recovery, flashed magisk 19.4. I think i had to format data at some point because twrp wouldn't mount storage. when I booted the system, I had no mobile signal.
I've tried rebooting, taking the SIM out and in again, leaving the phone switched off for a while, Flashing stock fastboot rom, Flashing Omni. Ive tried changing the preferred network type, changing the access point names. i've tried entering *#*#4636#*#* into the dialer to enter service mode and had no luck there (see pictures)
{
"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"
}
ok, panic over. I flashed an OTA zip in twrp and i've got mobile signal back! that was tense. Why would the OTA restore Mobile signal and fastboot ROM not?
CollotsSpot said:
ok, panic over. I flashed an OTA zip in twrp and i've got mobile signal back! that was tense. Why would the OTA restore Mobile signal and fastboot ROM not?
Click to expand...
Click to collapse
Bad or wrong image in the ROM.
Related
Hi,
A few months back, I unrooted my NS4G in order update to the official ICS release. Initially, I was content with the official ICS on my phone, however, I've come to miss the fun mods and features that are available with custom ROMs. Now, I can't seem to re-root my phone.
The bootloader is still unlocked so I tried going into recovery like old times but received a blank screen with an image of the android bot face down with its back door open and an exclamation point (pictured below).
Please help. Although I've rooted a few phones, including this one, I still feel like a rookie and may be missing something very simple.
Thanks!!!
{
"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"
}
You need to snag a custom recovery and get the current superuser. After that, you will need to make sure you either edit the script or delete the script in the system so it doesn't overwrit CWM.
Recovery fix: http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
Superuser:http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
CWM
The recovery needs to be pushed while in the bootloader via fastboot
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img
Recovery first, superuser flash 2nd, fix the recovery last once you've fully booted up.
When the faced down android appears , try pressing volume up button once . Helped me one time.
Sent from my Nexus S using xda app-developers app
So how about an update? How are you going with it?
I have had intermittent problems in the past similar to yours, and I was able to solve it - where are you up to?
You should go into a command prompt on your computer then do a fastboot oem lock then unlock. (This will erase all data)
Tell me if this works
Screenshot shows the phone is already unlocked-
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like 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"
}
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
polybius said:
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
Click to expand...
Click to collapse
Your link doesn't work.
I also cannot see any picture of your screen, but I think you mean freaky colours on your screen.
This is due to updated display drivers some time ago on CMs side.
Which means if you use a newer ROM, you also have to use a newer kernel to get the correct colours back.
If you are S-On your kernel won`t be updated by just flashing the firmware, you have to fastboot the kernel afterwards.
Hello, I have a problem, I have and always open bootloader and installed without problems cyanogenmod, carbon AOSP, etc ... Yesterday install AOKP and I have no wifi signal, no mac address appears to me, went back to the 4.2 meter by flastool. 2 version .17 and I started the process again, doing the dalvik cache and format system / format.
Probe with thunder and phantom and kernels either.
I never had this before last as long probe many roms.
Someone tell me would know that there is solution for this? Thanks
{
"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"
}
lokura72 said:
Hello, I have a problem, I have and always open bootloader and installed without problems cyanogenmod, carbon AOSP, etc ... Yesterday install AOKP and I have no wifi signal, no mac address appears to me, went back to the 4.2 meter by flastool. 2 version .17 and I started the process again, doing the dalvik cache and format system / format.
Probe with thunder and phantom and kernels either.
I never had this before last as long probe many roms.
Someone tell me would know that there is solution for this? Thanks
View attachment 2824850
Click to expand...
Click to collapse
By saying 17fw,are you sure you're flashing latest one...or maybe you're flashing the older one that is 4.1.2?
faizalotai said:
By saying 17fw,are you sure you're flashing latest one...or maybe you're flashing the older one that is 4.1.2?
Click to expand...
Click to collapse
No,got the .17 4.2.2, and the truth I'm going crazy trying everything
Ok, solved, you were right but was getting the .17 4.1.2
Hey everyone,
I have this issue with my device hopefully you know something about it: a while ago I rooted it, got Magisk on it all that. The device was just out so updates were still coming strong--or maybe I payed more attention to them than I do now, IDK--the case is that I accepted one of them and it undid the root and updated MIUI to something-something, regardless, since then I'm unable to flash a recovery image.
I thought the partitions got messed up or something and flashed the official system with the official Xiaomi spyware/adware suite "tools" hoping it would rewrite what needed rewriting then I tried flashing the recovery (TWRP) but no luck.
I'm using the XiaomiADBFastbootTools Java applet. It seemingly flashes the thing successfuly then it boots right into the system again, not in recovery. If I use force a recovery reboot through adb or with the buttons (which I've already forgot which were) the recovery the comes up is the official one, not TWRP.
{
"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"
}
Every time finishes "successfully", then the device reboots taking just tiny bit longer then I see the MIUI logo with the sort of paint-spill animation covering it and then I'm back on stupid Mars again (the stock pseudo-interactive wallpaper). Not even my information is lost--not that I'd want to, but at least it'd be something.
Since I removed most bloat the phone became pretty much useless and I wasn't even thorough because there's stuff that just can't be removed. Rooting would allow me to get some utility back out of it. Can it be fixed at all??
If I check for an update it shows there's an update to android 13. I've tried several times to update and it always says there was a problem installing the update. I start the installation and then says it's paused. I resume and it says the installation will continue when the device isn't being used. I again hit resume and it says there was a problem. Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
{
"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"
}
Rooted on build SD2A.220601.003.B1. I've tried on wifi and mobile data with no change. Restarted the phone several times with no change. I'm coming from a Oneplus 7 pro, is there something Pixel related that I don't know about? I haven't tried anything related to Magisk because I've never had to in the past.
Rooted is the issue. Flash back the stock kernel or just flash 13 manually
You're trying to take an OTA while rooted and asking why it doesn't work? If you want to run a rooted phone, you have some learning to do before you brick your phone.
If root is the problem, it's not a big deal. Taking the OTA and then using Magisk to flash to the inactive slot has always been the easiest solution. The Oneplus never cared about root. Pixel 2 XL was my last pixel device I used but I always had a rom installed. So this is new to me.
Be careful...if/when you DO get updated and reboot into 13, make sure u flash the new bootloader to the other partition.