Related
Hello!
today i flashed the new ROM. First I had problems with my ROM Manager but after I updated that everything looked fine. I could install the ROM but when the phone finaly booted I could only unlock my SIM card but after that every application crashed....
I followed the instructions. The only thing I ignored was the kernel...
Copy the downloaded AOSB to your phone.
update recovery, is required for install android kitkat
Boot into your recovery
Back up your ROM
Enter recovery
Make full wipe "included "system"
Select Recommended kernel for first install - > which kernel is recommended/how do I select it??
Install the ROM
install GAPPS package - download it from here
Reboot - the first boot can take up to 2 minutes
Recommended to Reboot again after ROM is up for the first time
2 second to up ! and 1 second to restart or shutdown ! it is AOSB
could this be the reason for every application crash? And how can I fix it?
http://forum.xda-developers.com/showthread.php?t=2642605
bernbrun said:
Hello!
today i flashed the new ROM. First I had problems with my ROM Manager but after I updated that everything looked fine. I could install the ROM but when the phone finaly booted I could only unlock my SIM card but after that every application crashed....
I followed the instructions. The only think I ignored was the kernel...
Copy the downloaded AOSB to your phone.
update recovery, is required for install android kitkat
Boot into your recovery
Back up your ROM
Enter recovery
Make full wipe "included "system"
Select Recommended kernel for first install - > which kernel is recommended/how do I select it??
Install the ROM
install GAPPS package - download it from here
Reboot - the first boot can take up to 2 minutes
Recommended to Reboot again after ROM is up for the first time
2 second to up ! and 1 second to restart or shutdown ! it is AOSB
could this be the reason for every application crash? And how can I fix it?
http://forum.xda-developers.com/showthread.php?t=2642605
Click to expand...
Click to collapse
I think the kernel stuff is here because on others devices there are differents kernels.
On Vision, the recommended one is inside.
If not, the aroma installer would give you a choice.
So what else can cause all apps to crash
Kéno40 said:
I think the kernel stuff is here because on others devices there are differents kernels.
On Vision, the recommended one is inside.
If not, the aroma installer would give you a choice.
Click to expand...
Click to collapse
There is no aroma installer. I can just install the ROM without any choise. So what else can cause the phone to crash?
I can only enter the PIN, then pull down the status bar and "confirm" that all applications are closed or couldn't be started. :crying:
bernbrun said:
There is no aroma installer. I can just install the ROM without any choise. So what else can cause the phone to crash?
I can only enter the PIN, then pull down the status bar and "confirm" that all applications are closed or couldn't be started. :crying:
Click to expand...
Click to collapse
my installation was smooth I used 4EXT
1st backup system did :good:
2nd format and system date cache
3rd boot and tested all for a while ok
4th installed GAPPS form here CM11 http://wiki.cyanogenmod.org/w/Google_Apps small package :good:
5th boot and everything ok
So it's maybe the SD card?
Frogkiller said:
my installation was smooth I used 4EXT
Click to expand...
Click to collapse
My SD card is formatted is FAT32...so change this to 4EXT should help me?
No keep sdcard fat32, 4ext is the name of a recovery and Frogkiller was suggesting to use this one.
What I would do is check md5sum of ROM and gapps to insure you don't have a bad download.
Be sure you have a compatible recovery (latest cwm, 4ext or twrp)
Wipe everything again
(Probably even fastboot wipe or use a superwipe script)
Flash ROM
Flash gapps
Reboot
(And stay away from ROM manager)
If this still doesn't work give some more info on phone, write down everything from bootloader screen, version of recovery, etc
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hi. I have an issue with 3G/Wi-Fi connections. After some time of Wi-Fi or 3G turned on connection to the Internet is not avaliable. It is showing me on status bar that Wi-Fi/3G is running correctly but whenever I'd like to open some web pages there's an info about not being able to connect to the Internet or when I'd like to download an app from Play Store it is simply not downloading. The only thing which helps is rebooting my HTC. It is annoying and I'd like to ask if there's anything I can do about it. The same was happening when I was using CyanKat 1.0.
EDIT: After a few hours of not rebooting device (the only possibility of making internet connection to work correctly) I see that the Wi-Fi doesn't even want to turn on. There's an info about Turning the WiFi on and nothing happens at all.
Solution!
Frogkiller said:
my installation was smooth I used 4EXT
1st backup system did :good:
2nd format and system date cache
3rd boot and tested all for a while ok
4th installed GAPPS form here CM11
small package :good:
5th boot and everything ok
Click to expand...
Click to collapse
This made the difference! Thanks for all your help. There was something wrong with the suggested gapps. Started without installing them and here we go!
osiol3k said:
Hi. I have an issue with 3G/Wi-Fi connections. After some time of Wi-Fi or 3G turned on connection to the Internet is not avaliable. It is showing me on status bar that Wi-Fi/3G is running correctly but whenever I'd like to open some web pages there's an info about not being able to connect to the Internet or when I'd like to download an app from Play Store it is simply not downloading. The only thing which helps is rebooting my HTC. It is annoying and I'd like to ask if there's anything I can do about it. The same was happening when I was using CyanKat 1.0.
EDIT: After a few hours of not rebooting device (the only possibility of making internet connection to work correctly) I see that the Wi-Fi doesn't even want to turn on. There's an info about Turning the WiFi on and nothing happens at all.
Click to expand...
Click to collapse
This is a kernel problem. But for turn on WiFi reboot your phone then you can do it
Sent from my Nexus 7 using Tapatalk
Can you tell me which kernel should I use? I've already updated recovery to newest 4EXT recovery.
EDIT: Flashing no matter what kernel ends with dead device. It tries to turn on but it doesn't happen. I obviously do something wrong but I can't figure out what it is on my own. Can I ask for some little advice?
http://forum.xda-developers.com/showthread.php?t=2290892
http://forum.xda-developers.com/showthread.php?t=2253023
That's what I've been trying to flash via recovery. Making full wipe, installing kernel then rom and it simply doesn't work.
bernbrun said:
Hello!
today i flashed the new ROM. First I had problems with my ROM Manager but after I updated that everything looked fine. I could install the ROM but when the phone finaly booted I could only unlock my SIM card but after that every application crashed....
I followed the instructions. The only thing I ignored was the kernel...
Copy the downloaded AOSB to your phone.
update recovery, is required for install android kitkat
Boot into your recovery
Back up your ROM
Enter recovery
Make full wipe "included "system"
Select Recommended kernel for first install - > which kernel is recommended/how do I select it??
Install the ROM
install GAPPS package - download it from here
Reboot - the first boot can take up to 2 minutes
Recommended to Reboot again after ROM is up for the first time
2 second to up ! and 1 second to restart or shutdown ! it is AOSB
could this be the reason for every application crash? And how can I fix it?
http://forum.xda-developers.com/showthread.php?t=2642605
Click to expand...
Click to collapse
Don't use gapps from this link. Use the modular Package from PAGapps
I recommend the MICRO MODULAR PACKAGE
osiol3k said:
Hi. I have an issue with 3G/Wi-Fi connections. After some time of Wi-Fi or 3G turned on connection to the Internet is not avaliable. It is showing me on status bar that Wi-Fi/3G is running correctly but whenever I'd like to open some web pages there's an info about not being able to connect to the Internet or when I'd like to download an app from Play Store it is simply not downloading. The only thing which helps is rebooting my HTC. It is annoying and I'd like to ask if there's anything I can do about it. The same was happening when I was using CyanKat 1.0.
Click to expand...
Click to collapse
I don't have an answer to your problem but just for the record I haven't had any problems with wi-fi. Back and forth between work and home, I was at a convention yesterday and turned off wifi to try and conserve battery, got home and turned it back on, then upgraded to 1.3.0.
So that being said it may just be you, sorry. I don't remember ever changing the kernel but it's been about 3 years since I installed CyanogenMod, and then about 18 months ago I tried a bunch of other ROMs (to great disappointment before switching back to CM7) so who knows what I actually did at the time.
I hope you figure out what causes the issue and manage to fix it, I have been extremely happy with this AOSB ROM, it's pretty amazing.
Ok, I recently installed Llama so it would automatically change stuff when I go between work and home. This includes turning the wifi off when I get to work (so I don't keep getting the "there is an open wifi" message for the wifi I can't connect to). When I get home it's supposed to turn the wifi back on: it did not. Manually trying to turn it back on it just sits at the screen saying "Turning on wifi" (or whatever the exact words are).
So yeah, there does appear to be a bug with the wifi. I'll check my logcat later, see if I can locate a problem but I doubt I have the tools to figure it out. In the meantime I guess I just don't turn wifi off.
Has anyone else had a problem with the Google "navigation" app? Tried using it for the first time this weekend. In the basic map I had no problem, it knew exactly where I was and the direction I was facing, but when I actually started navigating and it brought up the new app it was very inaccurate and showed me facing north always.
I'm just going to downgrade (as soon as I figure out how... any tips?) but wanted to see if anyone else was having this issue or just me.
Thanks.
osiol3k, and anyone else having the wifi issue, I think I fixed it.
I deleted the "/data/misc/wifi" directory in a adb root shell and rebooted my phone. It has now been several hours, I've turned wifi on and off, connected to different networks, turned wifi tethering on and off, turned it off for several minutes before turning it back on again, a few other things, nothing seems to break it.
It wiped out all my previously saved locations and wifi passwords, obviously, but that's easy enough to fix.
Hope this helps!
I used this asob 1.2.9 for a day and I found it very slow to use, is there a way to speed things up? thanks.
[Q&A] [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Q&A for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
RaiBinger said:
Hi again!
In 211014 ROM trouble with video in YouTub. If set pause then after play again video not work. Tell me please in last build ROM nightly update this issue resolved?
Click to expand...
Click to collapse
I have the same problem. at the same time when it occurs in other players turns off hardware decoding.
@crpalmer "As far as I am concerned, installing Xposed is the exact opposite of a clean install. Xposed can cause all kinds of problems (it just randomly changes how internals of the system work!).
If you have problems with a clean install (without Xposed), please provide logs.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->."
I have factory reset, data wipe cache and delvik wipe and then just flashed Nightly from 24.10.2014 and gapps. Cannot even get through the set up before the screen flickers and the device reboots.
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
joeb690 said:
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
Click to expand...
Click to collapse
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
joeb690 said:
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
Click to expand...
Click to collapse
There isn't any crash in the last_kmsg. Are the logs pulled after a crash?
Yes. Will provide another log today.
Unfortunately cannot provide another log as it the device will not work long enough to email the log, will flash stock ROM and see what happens. Maybe it a physical problem.
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
joeb690 said:
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
Click to expand...
Click to collapse
Are you sure you flashed the right Odin images? Did you factory reset?
One thing to try would be to flash the CM recovery (twrp would also be fine if it supports last_kmsg and I forget if it does) and let it sit and see if it reboots. If so, then grab the last_kmsg via adb. If you want to flash CM again, you can try to use adb to get a last_kmsg via adb since it just has to boot long enough for adb to access it.
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
dft601 said:
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
Click to expand...
Click to collapse
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
crpalmer said:
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
Click to expand...
Click to collapse
Hmm, sorry, do not know which version I had last before 200141109, I already deleted from my device.. at least 200141107....
No, I have no problem with the density. It fixes also problems for me (e.g. Swiftkey, Navigon,....) Till now I added this manually.
Mike
Autorotate and Contact view
Hi
I'VE installed the latest version and untill now everything is fine for me,
But whenn I open my contacts the autorotate function stops to work and I have to turn my tab by 180°
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
poleq16 said:
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
Click to expand...
Click to collapse
I posted a status update in the sm-t320 thread. The snapdragons are in much better shape than the exynos...
joeb690 said:
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Click to expand...
Click to collapse
So I sent my Tab in for repair and all went well, they never mentioned KNOX but this was a private company contracted by Samsung here in Germany to do repairs. Not sure of all the details but its was a hardware failure.
Unfortunately my Tab was "lost" by the courier firm contracted to return my device. In the process of making a claim and will probably receive a new device.
random touchscreen knockout
Hi there,
Just curious: do some more people have random loss of the touchscreen functionality for some seconds or even until a reboot is performed?
Hardware buttons are always fine, though.
I found one post related to this, but no clear answer.
Wiped data and cache but did not install latest nightly yet.
Is that a "known issue something" for build 20141112?
Maybe I should mention that I'm noob level: ultra...
CWMR (Recovery) flash file for ODIN
CWMR (Recovery): (use latest version)
Download: http://download.crpalmer.org/downloads/picassowifi/
* Unzip the .ZIP file and then flash the .tar.md5 that it contains using Odin
Click to expand...
Click to collapse
crpalmer could you pleas upload your flash file again? it's the best way for me because I hate to use the free alternative to ODIN...
EDIT: SORRY SHOULD BE FOR USING WITH SM-T520 DEVICE - DID USE WRONG THREAD!!!
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.
Does this have the Wifi fix in it? or has Google not published that yet?
Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm
Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?
ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3
Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.
Great work, thanks. Flashed about an hour ago, flawless so far!
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?
Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.
ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?
kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.
Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.
Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.
Thread update 15.04.2022, fixed some links, removed others, added RR 5.8.8 and did some formatting.
So since there were many users who had questions for roms,root,firmware and stuff like that which was already available but only in small posts,I finally decided to make a big official thread for the HTC Desire 310 and 320. Why 1 thread for 2 phones? Well,they are practically the same phone but desire 320 is running on stock kitkat and has flash.
Port guys and developers: @MaRtYy01 aka Martin Dimitrov @HTC Desire 310 aka 69techur aka Alija Huskic (Team N3GG3)
@Swoopae (deserves to be here lel) and users in 4PDA Desire 310 and 320 threads
New facebook group (tnx Swoopae) click
1.ROOTFlashable SuperSU zip: in firmware flashing video
<Moderator Edit>: Files removed due to 15 different antivirus services detecting the APKs as Trojans.
2.RECOVERIES
Spoiler: For firmware 4.2.2 only
Recommended-CWM 5(you dont need anything else,everything on 4.2.2 can be flashed with it): click
CWM 6 click
TWRP click
Stock recovery(if something messes up with other recovery and you get into bootloop flash it with sp flash tools) click
OTA - for android 4.2.2 click
Steps:
1.Put the OTA (named as update.zip) and the CWM on your SDCard
2.Reboot to Recovery (Volume UP + Power)
3.Select "apply update from sdcard"
4.Choose our update.zip (OTA)
5.It will return an error(if it doesnt then you should flash the stock rom with sp flash tools)(as our device is already updated) and it will let you choose two options. SELECT REBOOT SYSTEM NOW
6.After the phone is fully booted up, proceed to install the recovery as you wish!!!RENAME THE RECOVERY TO RECOVERY.IMG OR YOU WILL END IN BOOTLOOP!!!(You can use Rashr or MobileUncle MTK Tools or whatever you want)
7.After install, reboot to recovery
4.4.2+These don't work if you are with the jellybean firmware(kernel 3.4.5), only for desire 320 firmware. Required to flash roms with version higher than 4.2.2
- Philz Touch click in this archive you have all stuff required for the rooting and installing the recovery on the d320 kitkat rom. Password is amogus
- Philz Touch mirror link without any other stuff coming with it: click mirror
- Flash the OTA click mirror with the stock recovery and reboot, go to mobile uncle tools and flash the recovery (new recovery.img)
btw OTA for android 4.4.2 is different from the jellybean one
3.ROMS
Spoiler: 4.2.2
These roms are usually bugless or with minor bugs that dont interrupt the work. All ported from 4PDA users
XPERIA C click (sometimes gives errors while installing apps)
Lenovo(vibe ui) click
MIUI 5 click (one of the best 4.2.2 roms)
Lollifox click
Moonmod click
CyanogenMod 10.1 click (google play doesnt work)
4.4.2/4.4.4
WARNING:YOU NEED THE DESIRE 320 FIRMWARE TO FLASH ROMS WITH NEWER VERSION THAN 4.2.2
[07.11.2016]MIUI 8 click (bugless) [ported by @Swoopae]
Spoiler: 5.1.1
[01.11.2016] AICP 10 click
gapps(for AICP only) click [ported by @MilkyPL]
[26.8.2016]CyanogenMod 12.1 click bugfixed version by @Swoopae
Flyme OS 4.5 link in kk firmware flashing video (google play doesnt work,I will try to fix it soon;gapps built in) [ported by me]
Spoiler: 6.0.1
Not 100% of the roms are well tested, so have a working rom as backup in case the rom you try doesnt work properly, also report back if you experience this.
IMPORTANT-If you own desire 320 flash this patch right after the rom or you will face wifi issue-click
Its made for marshmallow roms,so work for lollipop and kitkat isnt guaranteed. Tbh it doesn't always work on marshmallow too lmao
For mounting the sdcard as internal storage,here is @Swoopae 's patch click
It's made for cm13 but will probably work on other marshmallow roms too.
[14.11.2016]Mokee 3 click (bugless,vpn also works,just 2g switch bugged) [ported by @Swoopae]
[01.11.2016]AICP 11 click (gotta be almost bugless as all new mm based roms) [ported by @MilkyPL ]
[12.10.2016]TemastekPLUS click (improved and tweaked temastek cm13,bugless,vpn also should work) [ported by @Swoopae]
[02.10.2016]SwoopaeOS r01 click (based on slim6,fixed lag and minor bugs plus a sexy theme) [yes its by @Swoopae]
[04.9.2016]Paranoid Android 6.0.3(aospa) click (vpn and audio from headphones doesnt work) [ported by @Swoopae]
[17.8.2016]CyanogenMod 13 click ( very stable, gps, google play work,just fm radio doesnt work) [ported by @Swoopae]
[15.8.2016]Slim Marshmallow click (everything except fm radio works) [ported by @Swoopae]
7.1.2|27.09.2017| Resurrection Remix N 5.8.4 by Swoopae: click
(should work well,needs some testing)
|15.04.2022| Resurrection Remix N 5.8.8 by me: post download
Steps:
1.Make sure the rom is on the sdcard
2.If you wish you can make a backup of your current rom
3.Wipe cache,data,system;dont mount anything/wipe for a new rom on philz recovery
4.Select update from sdcard/zip from sdcard/whatever is it from sdcard
5.Choose the rom zip and flash it
6.Flash gapps if the rom requires it(pico gapps are strongly recommended)
7.Reboot,first boot takes 3-8 minutes depending on the rom
GAPPS: http://opengapps.org/
Choose arm - whatever android version rom you are flashing - pico are recommended,if you have problems with gapps try with pico,flashing after rom and after 1 boot and then report if still doesnt work
4.Firmwares
- Have any problems with the gps? Try this: click and this: click
- Desire 310 stock roms:
single sim: click mirror mirror 2
dual sim: click mirror
- Desire 320 stock rom(works for both d310 single and dualsim): click ; When installed on desire 310 bugs of that firmware are little while line on top of the screen and auto rotation(screen flickering too but doesn't happen on 5.0+ roms)
- SP Flash tools: click
- Driver: click
- Fix for driver signature error on windows 8/8.1: click
- Stuff for fixing imei(including toolhero): click mirror
- If you don't want to flash the desire 320 firmware and just want to unbrick this tutorial will be more helpful(also works if you have desire 320 and want to unbrick): click
HTC Desire 310 aka 69techur reported that Lenovo A328 firmware also works without flickering on and white line,but volume buttons,camera,rotation and a lot of other things dont work.
- Instructions for flashing D320 firmware on D310:
1.Backup imei with toolhero on 4.2.2
2.Install the driver on the pc,if it cant install them because they arent signed-disable signature verification(test mode) or try on other pc
3.Run the sp flash tool with compatiblity mode windows 7(only if you are on newer os) and set everything on it like in the video, connect the phone to the pc without battery and holding volume down;da dl with cheksum,high speed,no battery in the options,select firmware upgrade and start to flash
4.Root with the pc software,make sure you have enabled usb debugging in developer settings
5.Flash the OTA with the stock recovery and reboot, go to mobile uncle tools and flash the recovery(new recovery.img)
5.Now you have recovery.Wipe system,data and cache and flash the rom you wanna flash(the 4.2.2 roms dont work anymore) after that flash gapps if the rom requires it and reboot.
KERNEL BUGS:Screen flickering(kitkat roms only),screen rotation,little white line on the top of the screen
5.YOUTUBE
Kitkat firmware,recovery and roms installation: click
CyanogenMod 13: click
How to fix imei: click
CyanogenMod 12.1: click
CyanogenMod 10.1: click
MIUI 5: click
Galaxy S5 mod: click
The HTC Desire 320 rom: click
AICP 6.0.1: click
CyanPOP 5.1.1: click
CleanKat 4.4.4: click
Wanna port a rom on your own? Here is a video guide for android 5 and 6: click
and written tutorial: click
Credits:
-The users of 4PDA for all 4.2.2 roms and all recoveries, cm12.1, guides, etc.
-Me for translating the guides, youtube videos and ported roms
-HTC Desire 310 aka 69techur for helping me test stuff, his porting tutorial, ported roms and youtube videos
-Swoopae and Tomi Sudi for ported roms
-other guys that I havent mentioned
If you have questions, reports about bugs, requests or something feel free to ask.
Don't forget to hit thanks
Nice thread
#Proud_To_Be_Team_N33G3!
Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?
Immortel.CZ said:
Many thanks for this! Good job. Cant wait for completed post
EDIT: How about GAPPS? And in which step we should install it?
Click to expand...
Click to collapse
in 5.x.x roms flash rom, boot, then flash
in 6.0.1 roms flash rom and then flash gapps
Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes
Immortel.CZ said:
Still not sure about few things so please add what missing or correct me:
Highlighted stuff is what Im not sure.
Want to use CWM5 and Broken OS. Already got root. Stock recovery downloaded too (to be sure).
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options. Continue to 8.
b) It will not return an error and you should flash the stock rom with sp flash tools (How?)
8. Select reboot system now.
9. After the phone is fully booted up, proceed to install recovery as you wish. What? How?
10. After install, reboot to recovery.
11. ??? What next?
12. How to install BrokenOSD310.zip?
13. Flash gapps. How and which one (platform ?, android - 6.0. probably?, variant?)
14. Thats all?
I know that lot of ppl could do it but I need to be sure, to not make any mistakes
Click to expand...
Click to collapse
Broken os is for the 4.4.2 firmware (kernel 3.4.67),not the stock 4.2.2(kernel 3.4.5) .You need to flash the d320 firmware first,get philz recovery on it then flash the rom and the gapps.
And here my explanation:
7b) I will add that later in the firmware section
9 ''(You can use Rashr or MobileUncle MTK Tools or whatever you want)'' Rashr is in the google play
11.-14. Well,I guess I will have to add instructions how to flash roms
BTW The kitkat firmware installation+installation of recovery and roms video is complete gotta upload today
Edit:video uploaded https://www.youtube.com/watch?v=QRpw5sQA0rs
and thread finished
Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
Last two bugs above (GPS and data) still occuring but not every time. Looks like switch is bugged.
EDIT: Did full wipe, format SD, reflashed G5 mod and now works without those bugs. Probably my fault flash. Yay!
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too
Immortel.CZ said:
Sooo...
Today, I´ve managed to install Galaxy S5 rom on gf cell phone. It was super easy.
If I remember correctly, this was my step-by-step:
1. Download CWM5. Unpack that file (contains OTA_v1_u.zip and recovery.img).
2. Rename OTA_v1_u.zip to update.zip.
3. Upload update.zip and recovery.img to SD. Upload Galaxy_S5_HTC_Desire_310_Dual_sim.zip on SD too.
4. Reboot to Recovery (VUP + Pow).
5. Select "apply update from sdcard".
6. Choose update.zip.
7. a) Will return an error and it will let you choose from two options.
8. Select reboot system now.
9. recovery.img (from CWM5) flashed from Rashr.
10. Boot to recovery, flash Galaxy_S5_HTC_Desire_310_Dual_sim.zip
11. Restart.
12. Boot to recovery, full wipe and factory reset.
13. Restart.
14. Boot to recovery, flash gapps for 4.2.2. (from other source).
15. Restart.
Now, there was a few things:
- Keyboard was not installed at all, so I´ve copied [censored] keyboard apk to SD and installed it.
- Dialer not showing dialing number (this is probalby because this rom is for S5 which have bigger display). Solved with 3rd party dialer.
- Same thing with date on unlocking screen. Not solved, ignoring for now. Can be probably solved with 3rd party screen locker. Will test it later.
- There is very annoying pop-up about back cover. Did fast look through google and it is solved by xposed, but will not install it until someone from you confirms it will not brick this phone
- When tap on those six dots in round shape (on desktop) to acces all icons of apps, and then tapping any upper icon (upper meaning first and second line from to), sometimes instead of running the app it will roll down status/notification? bar. Not a critical bug but can be annyoing.
- ADDED: Well, it looks like we cant turn data on, when both sims are present. Yes, we have sim which we want to use for data in slot 1 but still, we cant turn data on (no sign of 3G above cell signal). But I remember, it works when there is just one sim. Major problem.
- Another problem, GPS. It is working but it is still ON. We cant turn it off, not even in settings. Major problem. Will try it later without second SIM.
- CONFIRMED: It is problem with second SIM. When we using just one sim in slot 1, there is no problem, data works, GPS works as it should. So if you could look at it, please (if solution exists).
So far so good.
Maybe we will try CM13 but now gf will test it for a few days.
THANKS guys, she is happy with her phone now. And you know, when gf is happy, you are happy too
Click to expand...
Click to collapse
I would recommend you broken os over cm13,I havent updated it from a month(since I currently dont have the phone to test it) and broken os is super stable and almost bugless.
BTW if you have the 512mb ram version,I highly recommend the s6 mod or cleankat(69techur still hasnt uploaded it tho,lazy bastard XD).Kitkat uses less ram and its faster.I actually think that cleankat must be the fastest rom after all.
For the s5 mod:
-Keyboard works by default,just swipe the status bar and choose aoso keyboard
-Weird,dialer worked fine for me.And its not for s5 after all,the dialer looks like jellybean touchwiz,not kitkat,probably ported from s4/s5 chinese clone.
-The unlock screen looks like that because of the navigation bar,if you remove it(find qemu.hw.mainkeys=0 in the build.prop and change it to qemu.hw.mainkeys=1) and add pie controls instead,it will be fine.
-The pop up about the back cover aoso appears in the original s5,but this isnt real touchwiz rom so I suggest you not to touch it/backup the rom and try to remove it.
-Idk,probably sh1tty touchscreen,I think I faced the same issue when I was with the rom
-I dont know about solution of the last problems,the russians have ported the rom not me,checked the forum and they havent even reported these issues XD
BTW,if you have problem with random reboots put the fingerorint unlock.Its not real fingerprint of course,you just have to swipe down on the finger icon.The russians reported that this fixed the random reboots.
Anyway,thanks for the bugs report
Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.
Reading this comments makes me feel like my IQ decreasing
Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!
Immortel.CZ said:
Hey MaRtYy01 again!
Thanks for reply.
1) Dunno if it is 512 or 1025Mb ramm version. Now antutu states info about lenovo cell phone and there is 1024Mb, so not sure if I can trust that information. Is there any app which would provide exact info about ramm, without flashing 310 stock rom? Maybe it is really 1024. It is called HTC Desire 310 v1 white and that should have 1024Mb ramm.
2) I would VERY like to try those roms (Broken Os or S6 mod/CleanKat if memory is just 512Mb) BUT I lack of ability to make it without full step-by-step walkthrough. So if you would be so kind and type it by more describing way (videos dont work for me, my hearing english is low) so I can be 100% I know what I will be doing? Pretty please. For example, this is really idiot proof and it worked for me BrokenOs have some bugs as you stated so S6 mod would be much prefered. Or walkthrough for both, that would be amazing.
3) Keyboard could by my fault. I did not do full wipe after installation of rom, just after reboot. But it really wasnt there. In setup, I wanted to enter wifi password and all I can was voice input
4) Could provide screenshot, if you want. But that can be bypassed by another dialer, so it is okay
5) Pie controls is that round thing you press and few apps will show? We turned it off right away Too annoying.
6) So hw problem?
7) Hmm, okay. Maybe another rom will be solution.
8) No random reboots but thanks for advice! Will remember it.
No problem dude.
Click to expand...
Click to collapse
Just to start from something,6),thats most likely software fault.And indeed I think the tutorials are fine,since you managed to flash s5 mod you are smart enough and for the videos-they are more to see how it happens,if i wanted I could put a song in the background instead of talking,my english sounds like **** tho(sometimes even I dont know what Im saying XD).So if you look at the instructions carefully,then follow what Im doing in the video you will be fine.Just if you dont know,you need to flash the desire 320 stock rom before s6 mod,broken os or other roms with version newer than 4.2.2 which might seem a bit hard for you(its actually easy tho,try to flash roms on htc one x and you will see what is hard ).The desire 320 rom also has a few issues like the rotation and white line.And dont get me wrong,Id choose broken os every day over s6 mod since its wayy better,s6 mod isnt bugless too.Also,your ram seems to be 1gb which is fine.
If you want the fastest solution-flash miui 5,its the stablest and the awesomest rom so far,ive been using it for a month and really loved it.You dont need to flash the desire 320 rom for it.
In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot
Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?
Aconcerneduser said:
Hello!I rooted my htc with kingroot. I uninstalled a bunch of apps and have like 1,2gb free memory in my phone. However when i try to install a game (has like 0.9 gb) it still installs in my phone memory and when it tries to update itself it goes beyond the 1,2gb memory. It also appears that i can't move it to SD. Is there anyway to change the installation folder?
Click to expand...
Click to collapse
Hey Aconcerneduser.
If you have stock room then no, you cant install/move apps to SD. I´ve tried lot of things (like App2SD, Link2SD) and nothing works.
Try flash Galaxy S5 Mod, it is not hard and then you can move apps to SD!
I can make you noob proof walkthrough (how I flashed it), it takes you 15 minutes tops and it works.
EDIT: Updated my bug report about S5 mod!
Immortel.CZ said:
In first post, there is nothing about flashing via SP Flash Tools, so it is really neded?
Now we have CWM5 and Galaxy S5 Mod
and we want BrokenOS
Is this good way to do it?
1) Flash stock recovery with Rashr.
2) Go to recovery and flash 320 rom.
3) Flash OTA_v01_u-1.zip (from PhilzTouch - PT), reboot and do build.prop thing
4) Flash new_recovery.img (PT) with Rashr
5) Copy BrokenOs on SD
6) Go to recovery
7) Wipce cache, data, system
8) Choose BrokenOs zip from SD and flash it
9) Flash gapps
10) Reboot
Click to expand...
Click to collapse
'' 2) Go to recovery and flash 320 rom.'' XDXDXDXDXDXDXDXDXDXDXDXDXDXDXD
Lollll no.You need to flash it with sp flash tools;before that backup imei with toolhero
After that root it with the pc root program,flash the ota with STOCK recovery,do the ''build.prop thing'' and then flash recovery with mobile mtk tools.And new_recovery.img IS philz touch.
The rest is right.
Also,watch my last video for the kitkat firmware.recovery.You dont need to understand what I say,just look what Im doing.
Immortel.CZ said:
Why? Because English is not my first language?
Because I'm not that experienced in flashing as both of you are?
Well sorry that you feeling that way!
Click to expand...
Click to collapse
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-
HTC Desire 310 said:
1st. English isnt my first language too and Im speaking it fluid
2nd You have a step by step tutorial here and dont post fake bug reports -_-
Click to expand...
Click to collapse
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.
MaRtYy01 said:
He is speaking it fine tho
And they arent fake,just the crappy tries of the russians to port roms correctly-full with bugs.
Click to expand...
Click to collapse
Mine MLG ports are bugless
And that's your problem, HTC DESIRE 310. Not everyone is like you, not everyone have everything like you. And lol you are not speaking fluidly English.
If you don't want contribute this conversation, please step aside.
Thanks MaRtYy01 for advices. Few hours back I've refreshed my bug reports. Data and gps problems are gone, probably faulty flash or cause of not wiping.
And thanks for correcting me, as you can see I'm still little bit confused Will look it up tomorrow, now is bed time.
Yesterday, my Samsung Grand Duo i9082 (GI9082, GT-i9082_CU) @ CM 10.1 decided to keep freezing on chinese logo screen. Booting into Odin still possible, but no matter what recoveries I tried to flash, nothing changes. For example, flashing philz_touch_5.15.0-i9082.tar.md5 via Odin software tells me it was a success, then reboots my device and I'm back at Odin mode - no clockworkmode in sight, nothing changed!
I used to install Odin and then CM 10.1, since those work with the chinese version of the Grand Duo which wasn't updated to 4.2.2. But sadly the download link (http://forum.xda-developers.com/showthread.php?t=2231953) expired, and while the source code is available on this link I have no clue on how to create a rom from it. Couldn't find any current ROMs that work with Odin and 4.1.2, hence I tried to install CMW and several others as recoveries instead.
Out of ideas and it's a shame because it seems to have a fine connection to the PC @ Odin recovery, but for some reason no recovery file I tried had any effect.
edit: That feeling, when after a whole day of trying and not having any success you finally got a step forward ........... damn. Found this thread: http://forum.xda-developers.com/showthread.php?t=2315529 and http://www.droidviews.com/best-custom-roms-for-samsung-galaxy-grand-duos-gt-i9082/, flashed CMW 6.3.0.2 with Odin and apparently you have to press volume up + home + power in order to enter CMW. God damn Let's see if this will lead to final success...
edit 2: All I need now is any ROM for 9082 v4.1.2. Hmm.
edit 3: Found the xperia mod whose older version works with 4.1.2: http://forum.xda-developers.com/showthread.php?t=2304492. Trying it tomorrow. This is intense.
All the best mate.
Looking at your situation, I would have suggsted you to upgrade to 4.2.2, but then it seems you have found a solution.
BTW, I love CM10.
vdbhb59 said:
All the best mate.
Looking at your situation, I would have suggsted you to upgrade to 4.2.2, but then it seems you have found a solution.
BTW, I love CM10.
Click to expand...
Click to collapse
Don't think I can upgrade to 4.1.2, wouldn't know how. But I don't care anymore because I got a working phone again )))))
I found out that the original installation files including the 10.1 rom were still on the sd card. Simply reinstalled it.
But really odd, for the phone suddenly freezing for no apparent reason ...
edit: I just looked at the settings, and it's version 4.2.2. That's interesting, I could have sworn I had trouble updating it back then and gave up at some point back then. Hmm. That means I could install the latest CM even, I guess .... but then again, never change a running system, ay?
Lastedit: Trying to update to CM 14 did not work, it ended in a simple boot-loop. I'm back on good ol' 10.1 now
Quick-howto for future me: 1)keep volume-up, home + power pressed to enter Clockworkmod 2) wipe cache/reset to factory 3) install cm 10.1 4) install gapps 5) done.
misterioes said:
Don't think I can upgrade to 4.1.2, wouldn't know how. But I don't care anymore because I got a working phone again )))))
I found out that the original installation files including the 10.1 rom were still on the sd card. Simply reinstalled it.
But really odd, for the phone suddenly freezing for no apparent reason ...
edit: I just looked at the settings, and it's version 4.2.2. That's interesting, I could have sworn I had trouble updating it back then and gave up at some point back then. Hmm. That means I could install the latest CM even, I guess .... but then again, never change a running system, ay?
Lastedit: Trying to update to CM 14 did not work, it ended in a simple boot-loop. I'm back on good ol' 10.1 now
Quick-howto for future me: 1)keep volume-up, home + power pressed to enter Clockworkmod 2) wipe cache/reset to factory 3) install cm 10.1 4) install gapps 5) done.
Click to expand...
Click to collapse
If you are on 4.2.2 then try CM11 and CM12.1 (Jan build).
Same pattern.
Edit: CM11: http://forum.xda-developers.com/showthread.php?t=2563557
CM12.1 (Only the ROM File link): http://forum.xda-developers.com/gal...cm-12-1-pawitp-jan-april-build-files-t3450122