Related
[ROM][Stock][ICS]LG P990 v28g Stock ICS flashable zip by harsh & tonyp [DISCONTINUED]
LG P990 Stock ICS flashable zip [DISCONTINUED]
This ROM is discontinued.
If you're looking for a stable ROM I recommend this ROM as an alternative: ParanoidAndroid CM10
It's more up-to-date and smoother than Stock ROMs - but at the same time still rock stable and qualifies as a daily driver.
If you want to continue using a Stock ROM on the GB bootloader I'd recommend to use the updated and actively maintained v30a/b Stock ROM by rugglez.
Some of the work of this ROM went into it - especially the heavily reworked ramdisk.
Using this ROM with the kowalski oldbl kernel does work as well (and fixes the callbug).
I've never intended to support a Stock ROM in the long term - I prefer CM based ROMs by far.
The initial intention of the first version of this ROM was to provide an easy way for people to test the SU660 leaks - back when we didn't even have P990 ICS leaks.
Nowadays that's easy, thanks to tools like the AIO toolbox by spyrosk, but back then it was more complicated for the users - especially with a SU660 ROM as base.
Then harsh & I decided to work on it together and update the initial SU660 base to a P990 v28 one.
A big thanks to harsh with whom I've been working closely together.
What is this?
This is a flashable zip version of the official LG v28g ROM by LG.
It's a Stock LG Android 4.0.4 ROM which uses the default ("old") bootloader and stock ("old") partition layout.
I prefer to stick with the GB layout and old bootloader as pretty much all ROMs, including CM10, are build for that.
If you have used the NVFlash ICS ROM you need to go back to the GB partition layout.
There are two versions. The standard version will fit into the stock GB partition layout.
To make it fit in there we had to remove some apps, including LGEmail, LG Calendar, LGMemo (QuickMemo is still there, don't worry) etc.
If you want to have the full ROM you can use the extended version, but need to increase the /system partition size to 512mb+ beforehand (see here for instructions).
Note that by only changing the partition size the partition layout won't change - so you still can flash other ROMs like CM10.
What's working?
This ROM is considered stable. harsh and I are using it as a daily driver currently!
Full hardware accelleration including:
Working Videocamera
Google Chrome
Videodecoding
etc.
In-call audio
Playstore
LG UI 3.0 & LG 4x lockscreen (THE MOST demanded feature in every dev thread )
Bluetooth
2G/3G
FM Radio
Everything else you can expect from a stable ROM (data, wifi, sms etc.)
What's not working?
slow charging on usb computer connection. Wall charger does work.
Workaround: Power off phone, attach usb cable, boot.
Screenshots (Power + Vol down) are empty. Just use Quickmemo (Vol up + down).
LG Application Manager not fully working and thus not included
The call issue of CM10 ROMs is present for some people.
If you reboot the phone once a day (e.g. at the morning) it usually won't occur during the whole day.
Credits:
Besides harsh thanks (especially for the old versions) to the following people:
(alphabetical order)
Someone missing? PM me asap!
aremcee
bihariel
ergoen
Kostja_V
wkpark
Due to the continuous misunderstanding: This ROM requires you to run the GB (aka the "old") bootloader and partition layout.
If you flashed a ICS ROM (kdz etc.) with NVFlash you need to go back to the old layout and bootloader, for example with this tool:
[TOOL] Full Brick Repair (Clean & Easy)http://forum.xda-developers.com/showthread.php?t=1975274
If you're coming from CM7, CM10, PA, GB (Android 2.3) Stock ROMs etc. this warning does not affect you.
Note:
I fixed the error which required you to use CWM 5.0.2.x for this ROM so you can now use any recovery you want now.
I'd recommend the official CWM 6.0.1.5 Touch or the newest TWRP.
How to install the new CWM:
You can use the ROM Manager to install CWM. But you need ROM Manager premium (or an in-app purchase for ~2$) to be able to flash CWM Touch with it.
You can use this flashable zip to install CWM 6.0.1.5 Touch easily: http://forum.xda-developers.com/showpost.php?p=34263577&postcount=1083
You can use my freshly zipped NVFlash CWM6 touch Recovery flasher (based on Rusty!'s method):
http://goo.im/devs/tonyp/P990-stuff/various/CWM6.0.1.5 touch NVFlash-tonyp.zip
Remove battery, hold both Vol - & Vol +, connect the phone to your notebook and use the "install_cwm6.bat" file (or the matching linux sh install script). APX driver is included.
This will flash CWM without touching any other partition.
Installation (follow carefully!):
Read post 1 and post 2 completely before you're doing anything with your phone!
If it doesn't exist, yet: Create the folder "external_sd" on your internal sdcard.
Reboot once.
Reboot into your recovery.
If you are coming from another ROM than my Stock ICS:
wipe data/factory reset(!)
Install zip from sdcard (flash the ROM)
Reboot (can take a couple minutes)
After fully booting up and going through the setup wizard: Restart your phone once again
Don't touch the RIL! And don't mind the "Unknown baseband" if everything works. This just means you got one of the older basebands which aren't displayed properly anymore. Nothing to worry about.
If automatic time if off you can either flash the v28g baseband (see my stickyied thread) or disable automatic time and use ClockSync.
Download:
standard version (fits into GB's /system partition):
http://goo.im/devs/tonyp/P990-stuff/ICS
extended version ("full" version requires /system of 512+ mb):
http://d-h.st/CVb
Changelog:
Code:
[u]version 3.01[/u]
[LIST]
[*]build.prop lines added to identify it as P990 device in the ROM Manager
[/LIST]
[u]version 3.0[/u]
[LIST]
[*]updated to v28g
[*]CWM Encryption error fixed (you can use any recovery now)
[*]kernel updated. fixes the bluescreen issue and some bugs & memory leaks
[/LIST]
[u]version 2.0[/u]
[LIST]
[*]complete new version based on the v28e leak
[*]no more korean SU660 files, pretty much all bugs are fixed
[*]thanks to harsh who build this version!
[/LIST]
[u]version 0.98[/u]
[LIST]
[*]bsod on screen off fixed (thx arcee!)
[*]huge update to the updater-script
[*]now pre-rooted
[*]Playstore updated
[*]Stock Messaging app replaces LG's one
[*]added Stock LG Browser
[*]added LGAlarm
[*]removed Google TTS
[/LIST]
[u]version 0.81[/u]
[LIST]
[*]typo fix in the updater-script
[/LIST]
[U]version 0.8[/U]
[LIST]
[*]initial release
[*]A mix between the final SU660 v30c ROM and the P990 ICS leak
[*]custom kernel to let it boot with the old bootloader
[/LIST]
Old installation instructions for versions prior to 3.0 (which was way more complex):
Installation (follow carefully!):
Read post 1 and post 2 completely before you're doing anything with your phone!
Create the folder "external_sd" on your internal sdcard.
You need to use ClockWorkMod 5.0.2.x
TWRP & CWM 6.x will result in encryption errors (something to investigate later)
use e.g. RomManager, scroll to the bottom, choose "older recoveries" and install 5.0.2.0
Backup your current ROM
wipe data/factory reset
mounts and storage - format /system
Install zip from sdcard (flash the ROM)
remove the usb cable from the mobile phone!
(if you boot with the phone connected to your PC the PC will either freeze or show you a bluescreen!)
Reboot (can take a couple minutes)
After the setup wizard go to Settings - Connectivity and change the USB connection type to MTP
(now you can attach the phone back to your PC).
Restart your phone
Don't touch the RIL! And don't mind the "Unknown baseband" if everything works. This just means you got an older baseband which aren't displayed properly.
If automatic time if off you can either flash the v28e baseband or disable automatic time and use ClockSync.
Thanks man.
i'll try this and feedback later
thx i'm test:good:
Thanks man. I'll try whether the USSD code is usable or not. This is important for a prepaid user like me.
Sent from my LG-P990 using xda app-developers app
yeah baby
tonyp said:
It's possible that in-call audio is not working! It's too late to call someone to test it.
Click to expand...
Click to collapse
downloading now, will flash and call myself (landline) and report back
I get almost 40kb/s so I think it's gonna be a while
Thank u. Will try
Sent from my LG-P990 using xda app-developers app
flashing...
Damnit, I had it at the USB cable the whole time. I just realized the ROM will bsod when going into deep sleep.
This is a kernel issue due to the GB bootloader.
So this is mainly a "let's check out how ICS works" ROM at the moment
Doesn't deserve an own thread. I can't yet close my own thread, will have to ask a mod about it.
no go then
will check tomorrow for any news
dont worry, you did a amazing job by make it flashable
go get some sleep you deserve it and thanks you again for your hard work :good: :fingers-crossed:
unkown function "uassert"
I wanted to try this anyways(despite the BSOD issue). Installation aborted with (Status 6). Logs show
Code:
line 1 col 89: unknown function "uassert"
1 parse errors
I wiped data and was on CM9 PA rom before. Tried toggling script asserts in recovery but same results.
Let me know if I am missing something? [busybox maybe?]
Edit: Maybe this is a recovery issue, I am on 5.0.2.7, but never had this issue before with any other roms.
Fix: Just use the 0.81 build or modify the update-script as described in the post below.
Aj264 said:
I wanted to try this anyways(despite the BSOD issue). Installation aborted with (Status 6). Logs show
Code:
line 1 col 89: unknown function "uassert"
1 parse errors
I wiped data and was on CM9 PA rom before. Tried toggling script asserts in recovery but same results.
Let me know if I am missing something? [busybox maybe?]
Click to expand...
Click to collapse
This is a simple mistake I made resulting of me being tired.
I did some last minute modifications of the update-script file (to ensure no P999 or SU660 users try and install it) and unfortunately wrote uassert instead of assert.
You can either fix it yourself: Goto META-INF/com/google/android/updater-script and remove the first character (the "u").
Or download v0.81.
goo.im is a great hosting service and offers me remote ssh access via a linux terminal - so I just unzipped the ROM, fixed the line and rezipped it as v0.81. No need to re-upload
Please reply if it works.
v0.81 of this rom is release i didn't even finish to download the first build and another build is uploaded thanks tonyp download speed is 40kbps so it take a while to test it
Tonyp is one of my favourite guy, there is a reason behind and thats he is simply amazing!
Thank u man. Now ppl can flash it w/o worries and fear
Sent from my LG-P990 using Tapatalk 2
grimmyrippy said:
v0.81 of this rom is release i didn't even finish to download the first build and another build is uploaded thanks tonyp download speed is 40kbps so it take a while to test it
Click to expand...
Click to collapse
Oh, goo.im slow again. A couple hours ago I had full speed.
If someone wants to provide a mirror feel free to do so, I'm out now really.
The v0.81 zip is untested, I hope it works the way I did the change remotely. If it doesn't use 0.80 and apply the manual fix I posted in my last post.
Open the updater-script with a texteditor like Notepad++.
Use build 0.81
tonyp said:
This is a simple mistake I made resulting of me being tired.
I did some last minute modifications of the update-script file (to ensure no P999 or SU660 users try and install it) and unfortunately wrote uassert instead of assert.
You can either fix it yourself: Goto META-INF/com/google/android/updater-script and remove the first character (the "u").
Or download v0.81.
goo.im is a great hosting service and offers me remote ssh access via a linux terminal - so I just unzipped the ROM, fixed the line and rezipped it as v0.81. No need to re-upload
Please reply if it works.
Click to expand...
Click to collapse
thanx, i'll modify the update script and try. I also thought it should be assert but refrained on commenting lest you had defined your own macro.
Thank you for your hard work. :good:
Edit: Can confirm that modifying updater-script manually works. Using stock ICS now. Cheers.
Somebody who has installed it, could try running playing song through music player before screen lock?
Does music/song keep playing continuesly after screen locks and after 2-3 mins does the phone wakeup by pressing unlock key or still BSOD?
Definately unplug usb cable before doing this
Sent from my LG-P990 using Tapatalk 2
Hi,
Ive just bought a used Galaxy Note running Stock 2.3.6 (N7000XXLC1 Kernel an N7000XXLB2 baseband) and want to put the latest jellybean rom on.
Ive read through lots of threads about the brick warning and so on, i just want to know how to go from 2.3.6 and have it rooted and cwm on and the latest 4.1 leak or a modified 4.1
Could somebody please tell me the steps to do it as dont want to brick it and this 2.3.6 is rubbish
Matt
Hello!
I've rooted my Note like this:
#1
Get the original software (like N7000XXLRU - the file is 914Mb and it is a *.md5 file. ) and odin (Odin3 v1.87), install it in odin...how?
Open odin and put the file in PDA.
Option in odin leave alone (Auto Reboot & F. Reset Time; are selected)
Put Note in download mode: Volume Down Key + Home Key + Power Key; then Volume up key to continue
Connect the phone to computer
Odin recognize the phone and you will see it on COM port
Click Start
After several minutes the phone will turn on.
Now you have a original sw on your phone, and believe me this sw is GREAT...but if you want more...
#2
Root you phone
Described in this link (http://forum.xda-developers.com/showthread.php?t=1329360)
I used ''1A.Root + safe kernel + advance recovery''
Just read carefully (will write it down)
Visit this thread
http://forum.xda-developers.com/showthread.php?t=1901191
And download kernel in zip format according ROM you are having on device (just look for XXLRU-VDI; PhilZ-cwm6 v3.5 with CWM 6.0.1.8)
Copy downloaded file to Ext SD card to root directory (or any folder you make; I have ''A_ROOT'' for this things)
Reboot into recovery (Volume Up Key + Home Button + Power Key)
Select install(update) zip from ext SD card (Install zip >> Choose zip from sdcard; and click on the *.zip file)
select '[your downloaded kerenel].zip' which you have copied to Ext card above
Reboot device
Now you will have Root + safe kernel
And your phone is rooted now. You can have all the programs that work only when your phone is rooted (Titanium Backup, Root Uninstaller, Root Browser Lite, ...)
#3
Your phone is now ready to install all Android Development ROMs
Read each post ''How to flash'' it is easy
For instance I like stock rom and love 4.1.2, so i have sw from http://forum.xda-developers.com/showthread.php?t=1970626
Example:
Save *.zip on your SD/EXT Card (Ultimate N7000 XXLSA JellyBean 4.1.2 v5)
Restart in CWMR (Volume Up Key + Home Button + Power Key)
Be sure you're on SAFE KERNEL, then you can wipe (jes you are - on PhilZ-cwm6)
Full wipe /data/factory reset /cache and dalvik (dalvik is in advanced option)
Flash the ROM (Install zip >> Choose zip from sdcard; and click on the *.zip file)
Wait some minute until your phone boot!
You are done. That's all.
I've never had any problems with any of the ROMs. You can do the #3 1000 times and nothing will go wrong. Just remember to do a back up in CWM, when you have a rom that works great for you and you like. So if anything happens and you phone is stuck in ''samsung'' sing, you can go in CMW and restore it.
I hope it helps and I didn't forget anything.
Thanks so much for posting. I followed all the instructions and it worked fine. I have however gone and installed a 4.0.4 rom after using 4.1 for a bit and finding it too juddery.
Thanks again
Matt
No problem.
You can wait for the official firmware release and then everything will work 100%.
Since he didnt i hit thanks
Sent from my Amazon Kindle Fire using Tapatalk 2
Have hit thanks now , forgot!
[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?
please fix dead links
dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.
please fix dead links
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.
[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient
[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone
server stilll unreachable.
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
ukppete said:
Hello,
I tried to update my galaxy s via the integrated update screen on cyanogen mod to todays nightly rom update but during the android install animation it got about a third through and then went into quick recovery screen data which i couldnt read and then rebooted but to my existing version...in other words it didnt install properly.
Can anyone guide me through how to get this to update properly?
Thanks
Pete F
Click to expand...
Click to collapse
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
freakymod2120 said:
A few nightlies ago there was a bug in the integrated CM-updater...
Have you tested it with download the zip-file ,put it on your device and flash it via CWM-Recovery ??? That`s my favorite way ...
Click to expand...
Click to collapse
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
ukppete said:
Thanks, I have not done this before so im not sure if it will work if i keep trying downloading the nightly every day...maybe it will work one day? If it doesnt then i will have to flash it i guess. Just wierd that it downloads fine but doesnt install properly.
Pete F
Click to expand...
Click to collapse
SOLVED
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
freakymod2120 said:
It should work ,but i know with some of CM10.2-nightlies there was a bug and pawitp (the dev) makes a warning not to use the inbuilt updater ...but i think with the last nightlies it should work ...my way is flashing over CWM with the zip-file and not "over the air" ...
Is there any error?
You need 2 posts then you can report a bug here http://forum.xda-developers.com/showthread.php?t=2385178 or i would do it for you ...
Click to expand...
Click to collapse
No Prob...
Nice to know i could help ...
Good instruction about flashing ...:good:
ukppete said:
Thanks for your help.
I managed to flash via CWM and now everything is great - and it sorted out my earlier problems which included lack of mobile internet, constant rebooting when turning on and problems with receiving sms texts.
For all those people having similar problem - here are the easy steps to get the new nightly 10.2 rom up and running on your Galaxy S:
1) Download the latest zip file for nightly ROM and latest GAPPS zipp file onto your computer.
2) Connect your mobile to computer and turn on the storage function so that you can see your phone's storage option on my computer.
3) Copy your 2 zip files from above to your phone's storage as zip files without extracting.
4) unplug your phone from the PC, turn off and then go into CWM via volume down/home and power buttons.
5) Select install zip from SD Card and then you should see error message something like 'partition is incorrect/different and you need to wipe data - don't worry about this as you will keep all your apps, ringtones, pictures etc.
6) Install zip from SD card a second time - this should now start the install process. Install the GAPPS file once this is done.
7) Reboot and you should be faced with a Cyanogenmod registration page. Go through the completion process and then your ready to go.
8) check in about phone in your settings to see the latest update in your settings.
I hope this works for you all but as always...this is what worked for me on my Galaxy S and any mod is at your own risk and I wont accept any abuse.
Pete F
Click to expand...
Click to collapse
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
You are amazing.... you did it MASTER.
IEarlyer i also tryed but I gived up.... when I made root I allways lost the encryption the keystore no screenlock etc ... that was unusable.
Another time I was able install working recovery but the system crashed allways. But now its perfect.
The only beauty flaw is the lack of custom roms for a6plus but now I can customize for myself.
Many respect.
Thanks for your kind words
respect and appreciation to you.
You are a true moddfanatic.
Its not about how to keep in use the old phones. Its a passion .
Im the same just lwith mouch less expertion.
Simce You solved this problem I quickly founf the next.
Thr Last 2 -3 ays II spend with a experiment to to open Sansung native callrecder. I tried mouch ways...
all Csc changers
Secret codes
and dparrser mode
wtth activity hacks
with disrcibe files edit
With an apps replacing from customrom.
Wasnnot good .Tomorrow I flash with Odin csc f
So thats what I told ya.
Really I never use this feature !!!!!!
But I can let away I WANT to solve
If a problem prevents you from doing what you imagined, it is unacceptable to us.
caiuse Its about our force in this doddned )mazrix
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
JulioM18 said:
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
Click to expand...
Click to collapse
This: https://github.com/mcmilk/7-Zip-zstd/releases
It is a moded version of 7zip with support for Zstandard. You need this to extract the boot.img from the firmware files.
Hope it helps
It works on Samsung A605GN. I just tested IT. Thanks!
The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
It's been so long since this forum was published, and recently I came across it, purely by chance, since I gave up trying to root my A6+ (A605GN). I tried endless tutorials and invested many hours of my time and rest, and here is my reward.
I am totally grateful for giving you the time to explain these steps in detail, and help the community that has this device (still) and can configure it to their liking.
A big hug and blessings. You have saved my life. <3