I did an aosp following the instructions on the Sony aosp site. Everything is kind of ok, the phone works, but from time to time I see these strange things:
1. I do a reboot and when the phone starts again, the carrier is not detected. It shows no carrier in the settings. if I check the phone status, it does not even show the IMEIs.
2. I do another reboot or a power off -> then power on and all seems to be ok again.
3. Only once I did a reboot and the phone did not start. I went into fast mode and then I saw that the active slot was changed from a to b. I switched back to a and it booted normally. Maybe I should explicitly flash the .imgs to both slots explicitly? Anyway, I saw this just once.
Any ideas of what is going on?
Thanks,
M.
do you still have those issues? I plan on building aosp soon
Sorry for the late replay, yes the issues are there. I think we need new releases for the blobs. Currently on the Sony page there are still the ones from Feb 15.
Related
I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Shaolinstyle said:
I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Click to expand...
Click to collapse
Are you able to re-do the Hard spl?
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Shaolinstyle said:
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Click to expand...
Click to collapse
I know this sounds obvious and dont take it the wrong way but are you sure that the rom you are trying to flash as been unzipped properly and is named correctly. Try re-downloading a fresh rom and unzip it and rename it Rhodimg.nbh and put it on the root of your Sd card and try flashing it from the card. Also is the battery charged?
I am certain that the roms that I have been using are unzipped and named properly, there was actually a flahed rom on this phone that was workig fine until it started resetting with the rom on it, I wasn't updating or anything when it started to act up. Plus I use the same roms on a second TP2 which are working fine. I did try now to flash from my SD card, Hard SPL said it installed correctly but when I rebooted phone its doing the restart thing over and over still. Battery has been at 100% or close to for all flashes.
Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.
I believe I've deeply messed up here. I was trying to update to 8.1 while keeping Magisk root and ElementalX, but now I've got various UI problems including the home and app switch buttons not doing anything, the cell signal indicator never shows whether I'm on any data network, and notifications never show up. I also get a pop up right after boot that says my device has an internal problem, when I open up the phone app it says that my device isn't supported but I can still make and receive phone calls, and the USB OTG is not functioning at all. Almost if not everything else is working.
I followed the instructions to the T (I'll post a link to instructions a little later) then installed EX but, I didn't have root. At one point I also forced the phone off when it was presumably setting up final things after the ROM switching reboot. After booting up again, several apps were crashing and the problems above came up, so I followed different instructions specifically for installing EX and Magisk, which only fixed app crashes and Magisk.
I'm thinking where I messed up is that I didn't make a Magisk patched boot image for 8.1 before installing it, but at this point I'm not sure if that's the problem. I don't want to wipe the user data partition, but I'd do it if I have to. I have backups of everything anyways.
I just figured out that I was having the same issue as Cristiano Matos, though my OTG cable seems defective. The type-C connection is not working in one orientation, so I'll just have to use it in the other. This thread can be closed. Sorry for my stupidity
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
furiify said:
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
Click to expand...
Click to collapse
Same problem
i delete /data/system/locksettings.db with twrp file manager to get rid of this problem but i can not lock because all lock types freezes.
Good evening companions, I have a question that is more out of curiosity since it is not a problem of malfunction.
The point is that when I turn on the phone it starts perfectly until the lock screen is shown, there I put the pattern and it already opens the desk. So far so good, but after about 10 seconds the device returns to the lock screen even if I am using it and I have to unlock it again even if I already have the fingerprint reader. It is normal to block again even if you do not want to ??, someone else happens, can be solved ???
My model is the G9600 (snapdragon).
Thanks for any comments, regards!
losoollenos said:
Good evening companions, I have a question that is more out of curiosity since it is not a problem of malfunction.
The point is that when I turn on the phone it starts perfectly until the lock screen is shown, there I put the pattern and it already opens the desk. So far so good, but after about 10 seconds the device returns to the lock screen even if I am using it and I have to unlock it again even if I already have the fingerprint reader. It is normal to block again even if you do not want to ??, someone else happens, can be solved ???
My model is the G9600 (snapdragon).
Thanks for any comments, regards!
Click to expand...
Click to collapse
that does not sound normal at all. go into settings and disable all screen locks, reboot, re-enable the desired locks and let me know if that solves this for you
youdoofus said:
that does not sound normal at all. go into settings and disable all screen locks, reboot, re-enable the desired locks and let me know if that solves this for you
Click to expand...
Click to collapse
Thank you very much for your response, I commented that I have verified that it does so until the rom is installed by odin, that is, without having configured any security. This Sunday I was testing and I put several times trying some options in odin but nothing changed. I also just tried deactivating the pattern and the footprint, restarting and reapplying the locks to make sure, it's the same.
Outside of that I have no complaints, everything is excellent :good:
Today I installed the rom with a June patch and the problem does not (I remembered that there was an update that I thought would be solved), but when updating by September to September, the problem has returned.
Tonight I will try to install the June one again and take it by odin to September but without updating modem or csc .... play a little haha
Well ... the problem is solved or hidden I don't know. I have installed "Bl" by odin but the one in June and the rest of the patch has been in September, I had never done this but it works there without the restart.
What I don't know is what problems this graft can cause even when it can continue like this. I suppose that when I leave rom with bootloader 6 it won't work for me anymore ... or if it will allow me to skip the "bl" when installing by odin .....
Now with the October update I could no longer maintain the bootloader because it has gone to binary 6 and does not allow installing the new rom with the old bootloader. Unfortunately again the problem returned ..... nobody knows how to solve it ???