I had not been using Phoenix OS for sometime. My last version was 3.0.2, which was installed to an ext4 partition sometime ago. It got nicely upgraded, only complained that there's no EFI. Works nicely.
Hope some of you guys had installed Phoenix that way.
Related
Hi folks,
First I wanna take a moment to thank the community for all the great work.
with out your hard work and excellent tutorials I would not have been able to do this on my own.
I Originally had JF1.42RC33, and had used MarcusMaximus's AppstoSD application found here. http://forum.xda-developers.com/showthread.php?p=3627492#post3627492
When JF put out his 1.5ADP recently I went ahead and flashed that without wiping. I also updated the Radio immedietly after flashing JF's ROM. Everything was working fine at this point.
Then when johnowa636 posted his Aero port based on the JF build.
Found here:http://forum.xda-developers.com/showthread.php?t=511183
I decided to flash that, because I really like Aero. Everything at this point was good, with the occasional forceclose error coming from com.vending.something (sorry i just don't remember the excact error)
So recently when Ultra Spikey posted his Aero theme for JF1.5
Found here: http://forum.xda-developers.com/showthread.php?t=482799
I decided to Flash once again the Original JF1.5 I had downloaded from JF's blog. and then I flashed the theme created by Ultra Spikey.
Everything seems fine, but it's not. All the apps installed work and function as they should and the Market sees all my installed apps and purchased apps. it sees them as installed and some have updates available.
The problem Im having is when I clik on update, I get a starting download, but it just sits there and never downloads. I've tryed on both 3G and wi-fi and still it is not working. I also tryed to just download an app i didn't have. and also it would not download.
If anyone can help guide me in the right direction so I can learn what is wrong and how to fix it, I would really appreciate it.
I have the SDK installed in windows XP 64bit and also have a drive I installed Debian 5.0 on. I installed Debian so I could partition the SD, but Im a totall newbie to it.
I hope I've provided enough info. If there is anything else I can add please let me know, And thanks for taking the time to read this.
Something similar happened to me today after I (finally) got A2SD working on JF1.5. Apps were downloading fine initially, but then stalled. Got stuck on the same "Starting download..." step just like yours did. I left it there, remembering people having a similar issue a month ago or so, and eventually they downloaded and installed fine.
Is it just the market throttling people who download too many apps within a short time frame?
Off-topic question. Does the Aero v1.3 theme work with Open Home, or is it purely for the stock launcher?
Thanks for the reply ^^
I'll try just waiting and see if the download issue resolves itself.
I do have open home installed. it seems to work just fine with Ultra spikey's theme. i've a atached 2 screenshots.
Problem is fixed.
waiting did not solve the problem I had downloading apps.
Having no other input for ideas on how to go about fixing this I simply wiped, Reformated the ext2 partition ( just to be sure I started with a clean slate ), and reflashed JF1.5.
I then Applied the Aero theme and Finally used the A2SD method found here:
http://forum.xda-developers.com/showthread.php?t=512743
All is working well
I would close this thread, but I do not know how.
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!
DELETED-- If you face the same problem (No sensors working), flash the following file through TWRP. It is attached to the end of the post.
https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2717
Are you on a custom ROM and have flashed a different kernel?
Please provide more details.
--DELETED--
PATAboy said:
Hello everyone, my sensors have been failing since last saturday.
---Info: ---
*Phone: G4 Plus - xt1641 - 32GB Dual Sim
*OS: Lineage OS 14.1 1st May Nightly Update
*Kernel: (I think it was installed when sensors started failling) ElementalX Kernel 1.05 for Lineage OS
(As of now,12 of may, 8 Hours and a half after this was posted) V. 1.06 for Lineage is installed. Still not working
Never had a problem with any of them
***Problem: Sensors not working (Accelerometer , Gyroscope, Light and Proximity Sensors, Headphones Detection)
Cant get readings from Sensor Data Apps
Cause: Theres no apparent cause. Phone never fell to floor nor nothing like that. It happened after playing a game. No overheating while playing.
**Actions taken:
-Re-Flashed Lineage OS many times, with no succes (Wiped everything but sdcard and usb otg)(With and without ElemntalX)
NO SUCCES
-Flashed Stock Rom, with sensors working momentarily. They worked for 30 secs after one day of the Stock Rom install. Didnt work after that. Reflashed Stock, didnt work. (I believe that ElementalX was installed, version 1.04 for Stock Rom)
MOMENTARY SUCCES
-Flashed Lineage,
NO SUCCES
-Tried using ADB to execute:
*Sensor.qcom
* and sensorsevice
From /system/bin/
NO SUCCES
-Erased hmac.key (the only file) from /data/system/sensor_service
NO SUCCES
I grabbed a logcat, but I'll grab one from boot, so Im not uploading this one.
Click to expand...
Click to collapse
Look for SensorHub-N.zip and flash it in TWRP. This should be flashed after flashing ElementalX Kernel.
--DELETED--
--DELETED--
PATAboy said:
Do you know where to get it? I dont seem to find anything
Click to expand...
Click to collapse
You'll find a TWRP flashable sensorhub firmware zip file here: https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2717
By the way, with flashing the stock ROM, have you flashed/updated your device to Nougat at any point, before flashing Lineage OS?
--DELETED--
PATAboy said:
Yes, when I updated from MM to Nougat, i Flashed Nougat stock rom with fastboot to update it. The I used it for a while, till I found Resurrection Remix. No problems. But I wanted to try CyanogenMod. I ended knowing that Lineage was kinda the new Cyanogen, so I installed it. No problems for about a month and a half.
Also, do i need to reflash lineage and the kernel with it, or just reflash kernel and then sensorhub-n.zip??
Click to expand...
Click to collapse
Hmm, then that's odd sensors have failed when you've been running with no issue.
Don't think you have to reflash L-OS or the kernel, flash the sensorhub in TWRP (you may wish to wipe cache/Dalvik) and reboot - the sensorhub firmware should flash into /etc/firmware. You could re-flash the kernel if you wanted to.
--DELETED--
PATAboy said:
Hello everyone, my sensors have been failing since last saturday.
---Info: ---
*Phone: G4 Plus - xt1641 - 32GB Dual Sim
*OS: Lineage OS 14.1 1st May Nightly Update
*Kernel: (I think it was installed when sensors started failling) ElementalX Kernel 1.05 for Lineage OS
(As of now,12 of may, 8 Hours and a half after this was posted) V. 1.06 for Lineage is installed. Still not working
Never had a problem with any of them
***Problem: Sensors not working (Accelerometer , Gyroscope, Light and Proximity Sensors, Headphones Detection)
Cant get readings from Sensor Data Apps
Cause: Theres no apparent cause. Phone never fell to floor nor nothing like that. It happened after playing a game. No overheating while playing.
**Actions taken:
-Re-Flashed Lineage OS many times, with no succes (Wiped everything but sdcard and usb otg)(With and without ElemntalX)
NO SUCCES
-Flashed Stock Rom, with sensors working momentarily. They worked for 30 secs after one day of the Stock Rom install. Didnt work after that. Reflashed Stock, didnt work. (I believe that ElementalX was installed, version 1.04 for Stock Rom)
MOMENTARY SUCCES
-Flashed Lineage,
NO SUCCES
-Tried using ADB to execute:
*Sensor.qcom
* and sensorsevice
From /system/bin/
NO SUCCES
-Erased hmac.key (the only file) from /data/system/sensor_service
NO SUCCES
I grabbed a logcat, but I'll grab one from boot, so Im not uploading this one.
Click to expand...
Click to collapse
Well it is for xt1643 but should work for u too. See the instructions n u will have a customer service rom flash at ur home. It should definitely solve ur problem
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
DgnrtnX said:
Well it is for xt1643 but should work for u too. See the instructions n u will have a customer service rom flash at ur home. It should definitely solve ur problem
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !
I have an international 6T on Verizon. I've been running AOSP ROM's without issue for about 3 weeks. A few days ago due to my own screw up I had to use the MSM tool and start over. I got back on Havoc and ever since I can't get a stable connection except on LTE only mode. But in this mode I can't text or call -- though, data works perfect and stays connected. I've tried all the kernels and various other AOSP based ROM's and it's always the same issue. Short of using the MSM tool again and starting fresh for the 4th time I've tried everything I can think of. I feel like there has to be a solution without using the MSM tool and I'd hate to go through all that and get the same problem again. There must be a solution. Thanks for any help.
I ran the MSM tool again, got everything rooted, and flashed the older version of Havoc I had working, and my radio is still acting stupid. I don't understand. I checked everything while I was on stock and everything worked perfect. This one has me stumped.
imucarmen said:
I ran the MSM tool again, got everything rooted, and flashed the older version of Havoc I had working, and my radio is still acting stupid. I don't understand. I checked everything while I was on stock and everything worked perfect. This one has me stumped.
Click to expand...
Click to collapse
Are you sure that the OOS version you are flashing with MSM tool isn't too new for the older Havoc ROM? i.e do you need to flash an older OOS base? No guarantee that Havoc has been build for the latest OOS base.
bowlandspoon said:
Are you sure that the OOS version you are flashing with MSM tool isn't too new for the older Havoc ROM? i.e do you need to flash an older OOS base? No guarantee that Havoc has been build for the latest OOS base.
Click to expand...
Click to collapse
I'm not sure why this would effect anything. Havoc isn't old since it's based on the latest Pie updates. Also, I had everything working before. It's just for some reason now no matter what I have this radio issue and can't get messages and phone to work.
imucarmen said:
I'm not sure why this would effect anything. Havoc isn't old since it's based on the latest Pie updates. Also, I had everything working before. It's just for some reason now no matter what I have this radio issue and can't get messages and phone to work.
Click to expand...
Click to collapse
I know it's not old just I know from experience customs ROM's aren't always built on the newest base for the device. However in this case it looks like the newest version of Havoc is based on 9.0.12 so it's not that...
Strange that it's happening from a clean flash of OOS. Have you tried just formatting data from TWRP and flashing OOS from recovery rather than MSM tool?
Weirdest thing. But sideloading havoc in twrp fixed the issue. I side loaded havoc and the twrp installer and rebooted system and it booted up with data working along with calling and text.
I rebooted recovery and installed gapps and magisk and all is well. Still don't know what the issue was but glad I got working.