Related
After a long wait... It's time! 6.0 love for your US Cellular Samsung Galaxy S3! Get ready!
This variant is backed and based on the CyanogenMod13 (d2vzw) found here. Thanks to them!
Some things to remember BEFORE installing
This is in TESTING Stage. Expect lots of bugs!
I would not put this on a daily driver. Persue as you please.
I am in NO way responsible for you bricking your phone.
I have not tried cellular service on this variant. (Verizon is CDMA and so is US Cellular. I haven't heard any bugs regarding cell service from the forum below, so assuming it works.)
This should only be downloaded by developers, and those who have this as a second phone.
Installing
factory reset
wipe devlik/cache
install ROM
install GAPPS
*If you have issues with GAPPS on first boot, reboot. If it continues, repeat the steps above.
I recommend OpenGapps for this ROM, which can be downloaded below.
DOWNLOADS:
GAPPS: OpenGapps
ROM: CyanogenMod13
md5: eaec4bf8eebfb6fd10c0d747801cb365
XDA:DevDB Information
[ROM] [d2usc] UNOFFICIAL CyaongenMod13, ROM for the Verizon Samsung Galaxy S III
Contributors
samsung_d2usc, Master Cylinder, Stealth111, and any additional contributors that developed the d2vzw variant.
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-12-15
Last Updated 2015-12-15
Got a status 6 error trying to flash on D2usc. Toggled signature verification off and still got status 6 error.
Sent from my SCH-R530U using Tapatalk
I also got a zip signature verification error.
Fix for status 6 error
First of all, thanks for samsung_d2usc.
About the "status 6 error", it is normally something relating to syntax error of the updater script.
Fix:
Locate the "updater-script" and delete all the comments lines (that starts with semicolon ';' ).
Or you can use the attached one.
Just re-zip or updated the zip content (for example: Winrar allow that).
"updater-script" location:
Code:
cm-13.0-20151210-UNOFFICIAL-d2usc.zip\META-INF\com\google\android\updater-script
Nevertheless, there is no radio, neither sound!.
Good luck...
Any way to fix the sound yet?
Odd problem I have a play store I built that I "need" installed at /system as well as two other modded system apps. But when I go install my play store it will get to about a quarter of the install and then tells me no more system space that's a little odd to me as I just came from cm13 all system installs are fine and have 850mb + leftover what can I do to salve this I'm not seeing anything in logs to indicate that its a bug. As well as titanium backup is saying the space is there......
I cannot install this on the USC GS3. It keeps giving me an error when attempting to install. I have TWRP installed. Also, I have tried replacing the updater-script with the one posted above, but it did not work. Hopefully an updated version of the ROM will be available soon!
Any updates on CM13 for the d2usc??
does this actually work or no
I've been wondering if I'd be able to use D2VZW, D2SPR and D2USC roms on my D2CRI --- They were once unified so I'm guessing the formats of the roms didn't change..(?)
I know how to edit updater-scripts so that's not a problem.. I just don't want to risk a brick because 1 or 2 things may have changed down the line after they became "un-unified"
The phone is out of service so any proprietary APN's on the roms or anything really don't matter to me. I just use it as a wifi phone.
Been using this as a daily driver and no real issues. I'm having GPS lock issues, but I think it might be more hardware related since I haven't been able to get a single GPS satellite lock in the past 4 months on my previous ROM. I've had it crash randomly 3 times so far, but as far as a daily driver, totally dealable.
One big issue for me coming from LiquidSmooth(4.4.2) is the extSdCard permission stuff. Android really got annoying with that. There's an exposed module which allows the sdcard access from previous android versions which is nice
Also, anyone know where I can find a modem to flash with this? My baseband is still VRALF2.....
Problema de sonido y me salen una actualización pero a la hora de instalar me dise error 7 que puedo hacer
Yes it works but a pain to get it to
CurbThePain said:
does this actually work or no
Click to expand...
Click to collapse
I just wanted to post my success story with steps...
Download from post 1
Download 7zip command line
Extract files with: 7za x cm-13.0-20151210-UNOFFICIAL-d2usc.zip
Remove all semicolons from the updater-script file found in the directory: META-INF\com\google\android\
I opened it using Notepad++
I added a a directory called h2f and copied all the files I extracted to there
I entered that directory and then compressed the files with 7zip: 7za a h2f.zip
You can call the .zip whatever i.e. cm13-repack-UNOFFICIAL-d2usc.zip
Downloaded Open Gapps
Copied h2f.zip and gapps.zip to external sd card
Booted into Recovery mode (TWRP)
Wiped my device (factory settings)
Installed h2f.zip (it worked!!!)
Wiped Dalvik Cache
Installed gapps.zip
Installed SuperUserv2.78.zip (not required but an old habit)
Opted to install the TWRP app and as a system app
Rebooted
Took almost 8 minutes to "turn on"
Set up phone
Success!!!
Hope this helps any other d2usc users that have *lost* all hope... Together, we can keep this device alive!
~h2f
h2f said:
I just wanted to post my success story with steps...
Download from post 1
Download 7zip command line
Extract files with: 7za x cm-13.0-20151210-UNOFFICIAL-d2usc.zip
Remove all semicolons from the updater-script file found in the directory: META-INF\com\google\android\
I opened it using Notepad++
I added a a directory called h2f and copied all the files I extracted to there
I entered that directory and then compressed the files with 7zip: 7za a h2f.zip
You can call the .zip whatever i.e. cm13-repack-UNOFFICIAL-d2usc.zip
Downloaded Open Gapps
Copied h2f.zip and gapps.zip to external sd card
Booted into Recovery mode (TWRP)
Wiped my device (factory settings)
Installed h2f.zip (it worked!!!)
Wiped Dalvik Cache
Installed gapps.zip
Installed SuperUserv2.78.zip (not required but an old habit)
Opted to install the TWRP app and as a system app
Rebooted
Took almost 8 minutes to "turn on"
Set up phone
Success!!!
Hope this helps any other d2usc users that have *lost* all hope... Together, we can keep this device alive!
~h2f
Click to expand...
Click to collapse
So does this fix sound?
I was able to watch a YouTube video and it had sound. However, I have since changed ROMs to LineageOS 14.1 for my d2usc. Having really bad network drops with it though.
h2f said:
I was able to watch a YouTube video and it had sound. However, I have since changed ROMs to LineageOS 14.1 for my d2usc. Having really bad network drops with it though.
Click to expand...
Click to collapse
Nice, I'll try out the LineageOS 14.1 port you made. I tried changing the updater script of LineageOS 14.1 for d2vzw to flash on a d2usc once, everything worked except sound, data etc.
V0idst4r said:
Nice, I'll try out the LineageOS 14.1 port you made. I tried changing the updater script of LineageOS 14.1 for d2vzw to flash on a d2usc once, everything worked except sound, data etc. Care to elaborate on how you ported it with a working baseband?
Click to expand...
Click to collapse
can you please provide me with the link to lineageos14.1 d2usc ?
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
hicksd8 said:
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
Click to expand...
Click to collapse
You need the recovery from here to flash sagaopt roms IIRC.
jc1993 said:
You need the recovery from here to flash sagaopt roms IIRC.
Click to expand...
Click to collapse
Yes, that is the instructions I have been using and experiencing trouble with. I'll try it again.
Please give information how you solved difficulties. I'll probably try similar things soon. Thank you in advance
tag68 said:
Please give information how you solved difficulties. I'll probably try similar things soon. Thank you in advance
Click to expand...
Click to collapse
Well I tried it again with no success.
Can someone confirm for me that the ONLY difference between Saga and Sagaopt ROMs is the prerequisite partitioning and filesystem types required? ie, convert filesystems and SDcard filesystem to EXT4.
Trying to install CM13 Sagaopt complains something like "unable to execute the binary updater in the zip file". Trying to install CM12.1 Sagaopt gives exactly the same error so I guess the prerequisites are not right.
My phones are standard HTC Desire S and I assume that's okay?
I downloaded the ROMs from the Open Desire site after selecting device Desire S.
So still scratching my head on this one.
here my desire s runs now cm12.1
hicksd8 said:
Hi HTC Desire S Android experts,
Having been a member on here for years, this is my first post.
Let me start by saying that I'm not an Android expert although I've been four decades in Unix (Solaris) and Linux. I've built kernels from scratch but never tried to build an Android kernel. Anyway that hopefully gives you all a clue as to what I understand and what I don't understand.
I thought that I would try to install CM13 on my HTC Desire S but it doesn't want to play!!!
Having already done some serious hacking my starting point now is this.........
I have unlocked the bootloader.
I've installed Revolutionary S-Off, HBOOT 6.98.1002, Mar 10 2011
I've installed TWRP v2.8.7.0
I've tried to install CM13 (Marshmallow) "sagaopt" but it errors. I've tried to follow the repartitioning instructions (which I don't find very clear) to change filesystem to EXT4. After wiping is says that my SDcard should be empty but it isn't; the files are still there so I'm getting something wrong.
(I have managed to install CM12 for Saga (NOT the Sagaopt version) and it boots. I had trouble getting the virtual keyboard to work but eventually it did. I can't seem to get any Gapps zip to install, the install won't complete.)
Anyway, back to the subject of CM13 which is "sagaopt" only, can anyone give me the steps to take, especially with regards to partitioning, wiping, etc? Also, if I succeed with it, what next? Do I need to install Xposed? What Gapps zip file do I install and where can I get a compatible version for CM13 Sagaopt?
Thx in advance,
Hicksd8
Click to expand...
Click to collapse
the sagaopt rom uses the complete internal memory for the system (for a stable rom use latest CM12.1 nightly CM13 has ram and bluetooth issues)
Preparing and updating
(Optional but useful) http://forum.xda-developers.com/showthread.php?t=1679338 for new S-OFF HBOOT
(Optional but useful) http://forum.xda-developers.com/showthread.php?t=1858508 for new RADIO and Firmware (only B the rest is for a better stock 4.0.4 android)
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
@Layer_DE...........thank you for that. Certainly upgrading to TWRP v2.8.7.1 is key.
I flashed recovery file "TWRP-recovery-sagaopt-2.8.7.1.img" and the "error executing binary updater in zip" is gone.
Yes, I'm having some issues with CM13 so will try your suggestion of CM12.1
Many thanks. I'll post back with any further issues.
@Layer_DE.......I've flashed CM12.1 and it boots. Can you tell me which gapps file you flashed please? I'm finding that whatever gapps file I flash I seem to lose the virtual keyboard function. Using just CM12.1 the virtual keyboard works fine. I'd like to get the Play Store functioning correctly and its icon on my home screen. Thanks.
opengapps.org
ARM 5.1 pico
it works fine BUT for the first app you download you need more than a hour and every appinstallation takes very long
I'll give that a go. Thanks.
sent from my HTC smartphone
Hi All,
Just thought I'd give an update on this one........
I flashed TWRP 2.8.7.1 recovery and used it to set all filesystems to type ext4.
Then installed CM12.1 no problem.
Then installed opengapps 5.1 pico as suggested. No problem.
All working fine with that. In fact extremely good. No problem installing/uninstalling apps at all.
Still can't get CM13 (Marshmallow) to work. It will install but on reboot doesn't behave.
- You had me at 'Hello'...
Hi all -
Stumbled across this Thread, only to discover the AMAZING things still being done to these ol’ HTC Battle-Axes.
My interest stems from one of these devices recently being discovered as ’tucked away’ in a draw somewhere for a rainy day, and long forgotten by my Mother.
I don’t have any prior exposure to any form of Android - ( primarily due to my hate of any/everything Google. )
However, I’m now looking to break this arrogance of mine, with this otherwise un-used and forgotten lil’ HTC.
I am particularly impressed that you guys have managed to get this beast to dance - apparently without any major issues on Lollipop/Android v5.1 - via the installation of CyanogenMod 12.1.
Looking at your list of ingredients;
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
...all seems pretty straightforward.
( Well, straightforward enough - for me to be able to hunt around for explanations regarding what each step actually means! )
Being the ultraN00b I am, I’m curious as to how this set of instructions compares to say what the ‘official’ CyanogenMod position is;
wiki.cyanogenmod.org/w/Saga_Info
wiki.cyanogenmod.org/w/Known_Issues_page_for_saga
- Can any of you compare the ‘official’ CyanogenMod position, ( and specifically why they stop short at Gingerbread/Android v2.3.7 - via the installation of CyanogenMod 7.2 ), with what is suggested here?
- Are there any shortcomings that any of you have experienced running Lollipop/Android v5.1 , on this platform?
- How has the installation of Lollipop pulled up regarding stability? Any ‘glitches’ or ‘gremlins’ yet?
Nevertheless, I’m beyond impressed, and now pretty keen and excited to embark on my very first Android-expedition.
Thanks in advance for your responses -
Nunya-Biz
(c;=
Nunya-Biz said:
Hi all -
Stumbled across this Thread, only to discover the AMAZING things still being done to these ol’ HTC Battle-Axes.
My interest stems from one of these devices recently being discovered as ’tucked away’ in a draw somewhere for a rainy day, and long forgotten by my Mother.
I don’t have any prior exposure to any form of Android - ( primarily due to my hate of any/everything Google. )
However, I’m now looking to break this arrogance of mine, with this otherwise un-used and forgotten lil’ HTC.
I am particularly impressed that you guys have managed to get this beast to dance - apparently without any major issues on Lollipop/Android v5.1 - via the installation of CyanogenMod 12.1.
Looking at your list of ingredients;
Installing
1.Flash TWRP 2.8.7.0
2.Format SDcard ext4
3.Flash TWRP 2.8.7.1 sagaopt
4.boot recovery
5.use "adb push your-system-sagaopt.zip /sdcard/"
6.Flash it with TWRP
7.(Optional) download GAPPS pico copy it do "internal storage" and install it with TWRP
...all seems pretty straightforward.
( Well, straightforward enough - for me to be able to hunt around for explanations regarding what each step actually means! )
Being the ultraN00b I am, I’m curious as to how this set of instructions compares to say what the ‘official’ CyanogenMod position is;
wiki.cyanogenmod.org/w/Saga_Info
wiki.cyanogenmod.org/w/Known_Issues_page_for_saga
- Can any of you compare the ‘official’ CyanogenMod position, ( and specifically why they stop short at Gingerbread/Android v2.3.7 - via the installation of CyanogenMod 7.2 ), with what is suggested here?
- Are there any shortcomings that any of you have experienced running Lollipop/Android v5.1 , on this platform?
- How has the installation of Lollipop pulled up regarding stability? Any ‘glitches’ or ‘gremlins’ yet?
Nevertheless, I’m beyond impressed, and now pretty keen and excited to embark on my very first Android-expedition.
Thanks in advance for your responses -
Nunya-Biz
(c;=
Click to expand...
Click to collapse
the CM12.1 is very stable and only has typical android bugs (found no device specific things) and the official cm people hasn't used the kernel 3.0 source of the desire from android 4.0
for istallation:
1. download adb from http://forum.xda-developers.com/showthread.php?t=2317790
1.1 download and install adb driver
1.2 if you use windows 8 or higher use the fastbootfix form https://opendesireproject.org
2.install adb to "C:\Windows" (pro: no path needed)
3.check android version in system settings if it is lower or lower2.3.X (if its not it could be ****ty) than check bootloader version
3.1 turn off fastboot in battery settings
3.2 power don phone
3.3 boot phone with vol down clicked and if its -REVOLUTIONARY- or if its 0.98.x s-off or 2.0X s-off go to 6
if its 0.98 s-on you go to 5
if its 2.02 ask anyone else on my desires with 2.02 s-off newer worked for me but you can try it (go to 4) or only unlock it
http://www.htcdev.com/bootloader select HTC Desire HD and dont upgrade anything (start at step 1 skip preparation) after that go to 8
4.download the oldest rom with you branding from http://androidruu.com/?developer=Saga
4.1 http://forum.xda-developers.com/showpost.php?p=18746686 downlad misc_version
4.2 http://forum.xda-developers.com/showthread.php?t=1312859 download DooMLoRD_v4_ROOT-zergRush-busybox-su.zip and extract zergRush
4.3 go to folder with misc_version and zergRush and open cmd there and type
adb push misc_version /data/local/tmp/
adb push zergRush /data/local/tmp/
adb shell
cd /data/local/tmp/
chmod 777 zergRush
chmod 777 misc_version
./zergRush
./misc_version -s 1.27.405.6
exit
exit
exit
4.4 execute the firmware form step 4
5 download and follow http://rev.alpharev.nl
6 follow http://forum.xda-developers.com/showthread.php?t=1679338 (optional)
7 follow B in http://forum.xda-developers.com/showthread.php?t=1858508 (optional)
8 follow my first tuturial (if you need help post it to the tread)
Hi there,
I managed to succesfully install CM13 on my girlfriends old HTC Desire S, but it's slow as hell and she keeps complaining (after refusing a more modern phone because of the bigger screens and her small hands...).
Now I'm looking for the old CM10.1 which ran fine on my old original Desire, but all the links I find are way outdated and down. Does anyone still have it?
Regards,
Markus
ElFidel said:
Hi there,
I managed to succesfully install CM13 on my girlfriends old HTC Desire S, but it's slow as hell and she keeps complaining (after refusing a more modern phone because of the bigger screens and her small hands...).
Now I'm looking for the old CM10.1 which ran fine on my old original Desire, but all the links I find are way outdated and down. Does anyone still have it?
Regards,
Markus
Click to expand...
Click to collapse
Try CM11 it runns very smooth and is fine (older than 4.4 isnt 100% supported by app developers)
I installed CM13 as well on my Desire S - at first it was really slow. Until I bought a faster SD card as I saw that the internal memory was emulated on the SD card. Therefore I tried it with a U3 speed SD card - now it is workable - I am happy to have cm13 installed
@schneert
What's the size of your SD Card? What do you mean by 'workable'?
@zurpher: I bought a 32Gb SD Card., therefore I have 32GB stated as internal memory. It is workable in that sense that it is fast enough to use it without very much slow issues. It is still not fast but I guess that is because of the RAM of the device.
This ROM has some FCs on third party apps (such as Facebook, some Bank apps, etc.), so I deleted all the ROM files because they are useless at this time. Due te fact I have no more time to spend on this project, a moderator can close this thread!
Thank you!
Very well done! I just have one question: what does the CellBroadcastReceiver package do, and why is it installed if we don't need it?
gvlfm78 said:
Very well done! I just have one question: what does the CellBroadcastReceiver package do, and why is it installed if we don't need it?
Click to expand...
Click to collapse
In many Countries they use it to broadcast anything useful/vital to people life. In Italy it's used by Vodafone to broadcast the Province/CellID in GSM, channel 50, and TIM for the "Arancione" plans (does it exist anymore?) to bill by Province/CellID (I don't remember the channel ID).
The -> real <- thing, in Italy, is the battery drain!
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
Melkor_98 said:
The modified Twrp does not work for me... the original twrp link is offline and the standard 2.8.7.0 is not working on fever, and the working version of twrp that i found online (that is 3.0.something) is not able to install this rom for the error "signal 11" Then i do not know how to install this rom... if someone has advice, or has installed it, let me know.
Click to expand...
Click to collapse
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!
The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).
These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!
If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).
Lastly, have you clicked on the "d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
@Melkor_98 @sun75 When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
gvlfm78 said:
@Melkor_98 @sun75 When I installed RR for the Canvas 5 on my Wiko Fever I first had to install the Canvas 5 TWRP recovery. This was because otherwise I got a signal 11 error as the updater-script was setup for the Canvas 5 (changing it cause some other errors...). With the Canvas 5 TWRP I had the strange black lines flickering at the top of the screen and some other minor bugs. But then, when I had to reinstall it because the IMEIs were not working, I first flashed the stock Canvas 5 LL firmware ROM and then the recovery. This time it worked perfectly as if I had a Canvas 5. So this could possibly be related as the issue appears to be similar.
Click to expand...
Click to collapse
Yes, it can be true, but the problem is Wiko and Canvas have different partition schemes: Wiko has one partition more (Apedata) and different partition sizes and entrypoints vs. Canvas. (refer scatter file...). If you change your phone to Canvas, make sure to FIRST, make a *complete* ROM backup of all 26 partitions to files with SP Flash Tool!
Then you can format all the flash eprom, and restore the Canvas Rom. So you will need the SN Write Tools to restore IMEI/WIFI/BAR Code/BT mac addr using the Canvas mddb database.
Then you have to restore all the Wiko hidden partitions except the system, boot and recovery, but from now on, you have to use the Canvas scatter file, because you changed the partition scheme!
Hidden partitions are important because they contain calibration data, security keys, crts, etc... For sure they are used on Stock Roms, ... I don't know if custom Roms use them...
So, be careful on mixing the correct scatter file being on Canvas or on Wiko type Rom...
sun75 said:
What problems do you have with the modified Twrp? By the way, the Twrp itself was not modified, only the kernel (stock V39 Fever LL) and I deleted the last page asking to install SuperSu everytime... not so useful, because I use to install it separately, or with the Rom with scripts!
The only issue I have with Twrp 2.8.7.0 (vs. 3.x) is that it's continuosly flickering in upper screen, but it's useable for the two/three items it has to do (format/wipe/install).
These problems doesn't appear on Twrp 3.x, but we can not use it, because it expects MarshMallow filesystem paths format and support,... vs we are using Lollipop format. You got signal #11 because the scripts cannot mount and find the /system filesystem were they expects to find in LL format while you are using Twrp 3.x in MM format!
If you'll try to start Twrp 3.x on kernel 3.10.x (LL), if it starts for whatever miracle, you'll get tons of signal #7 errors bacause the /rootfs of the Recovery image is based on MM files and libraries, while Twrp 2.8.7.0 is based on LL files and libraries and does not start on kernels 3.18.x (MM).
Lastly, have you clicked on the "://d-h.st/82jl" link? I clicked on it, now, and I downloaded it with no problems... (the original 2.8.7.0 twrp!)...
Click to expand...
Click to collapse
I thank you for the answer, yes that link after some ads bring me to a page that do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status? ps on the last version of MM for fever (the one that i have) if i flash a different version of twrp that is not the 3.0.something the recovery do not start, the phone remain on the "wiko" screen and stop here...
Melkor_98 said:
I thank you for the answer, yes that link after some ads bring me to a page than do not load... about twrp i should try to bring back to LL the phone with the official tool of wiko and with that situation restart to unlock bootload /flash twrp 2.8.7/ install rom? For exemple i use the tool taken from andoidiani (i can not post link...) that should bring back everything to android 5.1 status?
Click to expand...
Click to collapse
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.
What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!
For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
sun75 said:
No, you shouldn't bring back to LL the phone nor unlock anything! I was on MM, and simply flashed with SP flash tool the boot.img & recovery.img. Once in recovery, I erased all except the microSD, and then, installed the Rom.zip. Done.
What problems do you have with recovery flashing it with SP flash tool? It does not start? Let me know!
For the original TWRP you can see here (Twrp Beta1 for LL): Link! I'm correcting the OP!
Click to expand...
Click to collapse
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7? (the reason of why i was using adb fastboot is becouse fever has not the removable battery and sp flash tool have difficulty do detect him)
Melkor_98 said:
I was using adb Fastboot, to first unlock the bootloader (that with the wiko tool return locked if you recover the phone) after i use the fastboot command to flash the recovery img, with the classic "fastboot flash recovery" Should i use SP flash tool to flash the twrp 2.8.7?
Click to expand...
Click to collapse
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool!
sun75 said:
Yes, you'll bypass the OS, flashing directly the recovery.img to the flash! I never used adb fastboot, etc. commands on Wiko,... and I never unlocked the bootloader! Maybe with other phones it's mandatory, but with the Wiko Fever, you can flash directly on top with SP Flash Tool!
Click to expand...
Click to collapse
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help
Melkor_98 said:
Okay i will try Sp flash tool, could you just explain better how to make the fever detect by the program? becouse i used it for older phones and i always removed they're battery, but with fever i can not do this and connecting it to the usb it will start the charging screen, i need some particular drivers?... anyway thank you a lot for your help
Click to expand...
Click to collapse
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!
Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash! The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
sun75 said:
The first time you use the official Wiko Update (V34 MM or V39 LL, it doesn't matter) it installs the Wiko drivers (unsigned drivers, so if you use Win 8/8.1/10 you have to reboot in "allow unsigned drivers install mode" by using the Windows recovery menu' and by pressing F7 (If I remember)) and unpacks the original Rom, then it asks to install it: do not install it, you don't need it!
Once installed the drivers, use the SP Flash Tool (it uses the same drivers installed by the Wiko Update!) to update the required images of the Flash! The phone must be completely off, attach it to the pc after you have started the download process in SP Flash Tool and it will start by itself!
Click to expand...
Click to collapse
It worked perfectly, thank you for everything
I've got huge battery drain especialy when the phone is used (I think it's correct on sleep mode) and I already set up kernel audiutor to 1040 max CPU speed...
Is it normal ?
Two others minor bugs :
Settings app crash at first boot, need to force stop it and re-launch the app to get it to work (I'm in France if it's matter).
Mobile data on LTE can't connect directly at phone boot, I have to switch to 3G then set it back to LTE and it's good.
Also, I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
pakrett-bm said:
I've got huge battery drain, only 8 hours and I already set up kernel audiutor to 1040 max CPU speed...
Is it normal ?
Also Settings app crash at first boot, need to kill it and re-launch the app to get it to work.
Mobile data on LTE can't connect directly, I have to switch to 3G then set it back to LTE but this is minor.
Click to expand...
Click to collapse
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?
If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!
The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!
For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
sun75 said:
Huge battery drain? Are you using this rom or the 5.8.4_r29 for Canvas?
If you're on this Rom, why you have set kernel audiutor to 1040 max cpu speed? I can achieve a normal day full battery chargeless whith no particular settings!
The Settings app never crashed at first boot to me (anyone else?), but, instead, with SuperSu installed, it asked for Root permissions!
For mobile data: I think it depends on where you live! I adapted /system/etc/firmware and /system/etc/mddb for SE (Southern Europe, Italy, etc.) Region. If you live elsewhere, you have to simply replace or adapt the contents of these two folders with the data you can copy from your Stock Rom (same paths). One more config, there is a "ro.telephony.default_network=10" in build.prop in /system that works for sure in Italy..., maybe in other countries the LTE default network is not 10 but another value...
Click to expand...
Click to collapse
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)
I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
Also why we need superSU ? Can't we use lineage/cm integrated root ?
Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.
Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?
The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.
Another thing, why there is two camera app exactly ?
pakrett-bm said:
I have a Wiko Fever 4G and I use the rom you recommended : "RR-N-v5.8.3-20170527-l5460-Official" installed from stock Wiko Fever lollipop v22. (What's better ? Installing from lollipop or marshmallow, and which version ? I can't find lollipop v39 anymore)
I deleted superSU from the rom to be able to install magisk 14.0 + xposed 87.3 + gravitybox 7.0.0 alpha1 and it works great but maybe it cause the battery drain ?
Also why we need superSU ? Can't we use lineage/cm integrated root ?
Mobile data isn't a problem for me, I use a tasker task that send an intent to gravitybox at system start to switch to 3G then switch back to LTE. I'm in France and LTE default network is also 10 I think, it also work with 9 if I remember correctly.
Do you know if I can sent an intent to the system to do the same thing, I mean without needing of gravitybox ?
The Settings app doesn't crash at first boot but sometimes (often) at system start. Same thing, I use a shell command with tasker to open settings in background at system start then another command to force close it, and it works.
Another thing, why there is two camera app exactly ?
Click to expand...
Click to collapse
It's not a problem what version of LL or MM did you came from...: the problem, maybe is the Region you are for the Baseband. I "statically linked" the SE Baseband (in the Stock MM Rom it is chosen by reading the NVRAM for the suffix _XX and then it loads the right files from /etc/firmware and ../mddb directories). Now, with the custom ROM, all the scripts reading the NVRAM for the suffix are gone, so it loads everytime the _n modem and mddb databases, whatever they are! So I overvritten the generic _n modem and mddb databases with the _SE ones. For your region to work correctly, I suggest you to upgrade to MM Stock, go in Factory Mode Menu and select Version Info -> check your Region Zone! If it's SE, ok, otherwise you have to copy/paste the zone modem/mddb _XX files to _n overwriting it for each group!
I don't know magisk and the other software you mentioned... so I can not help you for the battery drain with them!
For SuperSu... I tried to use /xbin/su but it doesn't work for all apps... Something works, most not! So, because are years I used SuperSu for all, I installed it solving the rooting problems for all apps requesting it!
Idem with Settings: it's requesting SuperSu with Root Permissions from the first start... maybe not installing SuperSu breaked something. You can check it by logging the boot process "adb shell logcat > log.txt" and looking for the cause of the crash! I can not replicate the problem...
For LTE,... in Italy I'm attaching LTE with no problems with two distinct network operators... it switchs automatically from H+ to 4G and viceversa without any interaction from me! I suspect you are on the wrong Baseband Zone... By the way, I got the Baseband from the MM V.34 ROM (the latest!).
Two cameras? Yes... only because every app has some nice features the other app does not have! Feel free to delete the one you don't like/don't use!
Some Bugs...
Hi,
I found some bugs in this Rom and/or port on Wiko Fever. I'll describe them so you can confirm them!
- In these days I'm working in a DataCenter at floor -1. Well, there is no GSM/data available here. The problem is that when coming back on ground or upper floors, the phone correctly reattach itself to H+/LTE data connection, but it never establishes an ip connection to the Internet, with the "x" in the LTE signal fixed as no ip was negotiated. This is true until a reboot is done! Once a reboot is done, the problem is solved: data connection and ip connection to the Internet are established automatically! I think it's the MM baseband that is not fully compatible with this Nougat Rom based on LL...: I'll try to substitute the Baseband with the LL V39 one and test it!
- FM radio module: I fixed it. BUT... : it's complaining about a "Alsasound: no defined handler specified for .... " forever (draining battery) and info on radio stations and RDS is not working (but radio and audio is working ok!). I'll investigate more on this!
- AudioFX mixer: apparently working,... but ... it's making no difference on sound, no matter on settings you select on its panel! So it's useless! I'll investigate to correct it, to change it, or the like. There is something wrong on the mixer config.
- As someone suggested me, I found that flashing TWRP 2.8.x and the Rom from MM results in some screen glitches and flickering on kernel boot, on charge and on TWRP operation. These can be annoying! To solve them, flash the Fever LL V39 Stock Rom before flashing anything else. Then flash the TWRP 2.8.x, and then the Rom. Doing so, you will never experience screen glitches and flickering on boot and TWRP operation. I think the big difference from the two versions (LL and MM) is the bootloader.bin that is different from the two releases.
- I added some MTK Engineer Mode Modules... someone asked me to do so....: some modules are crashing, e.g. the audio interface test suite, maybe for the Alsasound interface.
- I updated the OpenGLES driver library with the Fever V39 one: more stability.
- I updated all the audio/mixer interface to make FM Radio module work. Maybe this breaks AudioFX, maybe not...
- I updated the installer scripts to look for /gapps/gapps.zip and for /supersu/supersu.zip, so you can download them separately (the version you want) and integrate them yourself. Zip the Rom, and flash!
- Settings -> Backup & Restore -> Factory Reset : is NOT working (if you press "restore", it does NOTHING!!). Ok ok...you can hard reset by TWRP... I Know!
I think it's all... for now!
I'll update the Rom .zip once I'll solve the major issues here explained.
I finally saw someone interested in making a rom for wiko fever and here i am. I would like to know if i can install this rom in the wiko fever 16gb/2g ram version. I noyticed by the stock systems version that this is for wiko fever with 3gb ram. Anyways thank you for your goooooooood work!!
Edit: i have an hanuna twrp already installed in my phone, will it work or i have to install the version metion in the rom description??
Hello,
I saved the first version of my tablet from the kill switch by installing a custom rom. And I never used it anymore since this moment.
A few days ago, I think about a new project that I will prefer to try on an other tablet than my main.
Once on the log screen, I discover that I need a password but I don't remind using one.
I try to go to recovery and wipe all, but the OS disappear, so I try to install another one.
I had some difficulties to install successfully the last version of TWRP, but now it's Ok.
I also install the last bootloader and finally succeed to load new rom like Lienage 14.1 for example.
But I can use it as "google services framework has stopped working" if I install Gapp (and Nvidia services if not)
I can not do anything as I have to first configure the rom (wifi, etc.) and can not access to settings..
Any idea on how to solve that ??
A quick update of my problem : I'm still unable to get a functional rom installation.
So I tried to install an optimized version of a stock rom (this one : Optimized stock rom
But, in this case, I'm unable to install it. I get the following error :
mount : failed to mount /AAPstdin: can't skip at /system: Block device required
Someone knows what is the problem and how to solve it ?
Thanks in advance...
Few days ago as expected, official users (who is using CN-EN official ROMs) of Le Pro 3 AI (further mentioned "x7") got an OTA update to the latest release of EUI 6.0.030S.
The miracle that expected was not appeared. It is still based on Android 6.0.1 (Marshmallow).
The ROM is still not localized for other countries, it contains only CN and EN languages.
And there still many bloatware of LeEco services that is very annoyance.
But first of all, the apps inside are now more optimized and as I see, they starting and function faster then previously.
Ok, let's go to the main part - links =)
The Official Site where you can download the ROM based on OTA update scheme is HERE. Also you can download a copy of OTA package from HERE.
But if you want to download faster, you can use my clouds where I'm continuously holding the most of Official ROMs for x7.
---> MEGA (follow into the folder called "original_stock")
---> FEX
Inside my clouds you can find that the ROM filenames contains not only a version but also an appropriate suffix (_OTA or _FASTBOOT). It's used to separate the ROMs by the installation method.
The FASTBOOT prepared ROMs contains an installation scripts (.BAT for Windows and .SH for Linux/Mac) for not only full installation (with clearing of User Storage), but also for update (without clearing of User Storage).
Please be careful, don't even try to install via FASTBOOT without clearing of User Storage, if you currently have functioning non Official multilingual EUI like 5.9.027S (faked as 028S in menu "About phone") or other non official!!! If you'll do this you will get many conflicts in settings and apps.
I expect that the FASTBOOT updating instructions are widely known, but remind them once more:
1) Enable the "Developer options" menu by clicking on "Build number" 7 times in the "About phone"
2) In the "Developer options" menu, turn on "OEM unlocking" and "USB debugging"
3) Connect the phone to the computer with a USB cable
4) Run one of the installation scripts from the folder of the unpacked firmware
5) Immediately upon startup, allow on the phone screen the "USB debugging" permission for your computer, preferably within the checkbox "always trust this device"
6) Wait until the installation process finishes (15-20 mins), calmly referring to the fact that the phone itself will reboot into FASTBOOT mode, and also please ignore the Sparse format error message (it's normal)
7) The phone itself will reboot into a new OS ... the first launch will be very long
Please feel free to ask anything here about the installation process, cloud links etc.
But be ready that I'm not fast answering.
Any other questions including the comparison of EUI versions performance and functionality will be ignored by me.
We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =|
thank you
I should have researched before buying the device kk was already "lost" trying to find a customized rom for him. this part of the text: "We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =| " , clarified me a lot
I istalled it but it does not have google play store?
azizo07 said:
I istalled it but it does not have google play store?
Click to expand...
Click to collapse
ROM does not have Google applications. You need install it. I think this still working in this version: https://forum.xda-developers.com/le-pro3/leeco-le-pro3-a1-model-x651-guides-development--and-mods/automated-installer-gapps-morelocale2-t3752576
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
azizo07 said:
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
Click to expand...
Click to collapse
030S mod is based on APKs of 030S with few modifications... but it also runs the old Boot from version 027S... so it may have some unexpected behavior...
yes, all of these ROMs have no root... but with mods based on Boot of 027S version you can use a temporary root (one time booting into TWRP) for further system modifications and then back to boot with native stock kernel and modified system will run good (expect the problems with apps you may cause by modifications)
hi, how i can install this ROM if I use a non official Rom? I mean, I recived this phone yesterday with a 028s (stable) that is non official, and I want to install this official ROM.
Help please
My cell phone has brick
You have some rom to fix it?
Does the NFC work on this rom? I had 028s before but the NFC was disabled.
Hi im install rom eui 6.0.030s "https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634"]https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634 But me phone have in antutu 50000 . Ealier was 100000. What is wrong i see Stock-thermal.zip but i cant dowload . plise help
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
cyzarine said:
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
Click to expand...
Click to collapse
What you can't see? The scripts?
You need to look at the contains of unpacked ROM zip that have suffix "FASTBOOT" in filename. There must be files with names like "x7_fastboot_tool.bat" and "x7_fastboot_tool_noUser.bat" and also same files with ".sh" extensions for Linux.
For installation to start you need to run one of this scripts. To run from CLI (CMD), not by double-clicking on it.
what's the score in antutu in new rom ? I have 50000....
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
cyzarine said:
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
Click to expand...
Click to collapse
This is an OTA package. But it's buggy, my try to make a direct update from 028S to this 030S with OTA way was failed, and I heart many reviews about same behavior.
So I think the best way to update is to use Fastboot with scripts and executable provided in my package that contains "_FASTBOOT" suffix in filename.
From there you can use script "x7_fastboot_tool_noUser.bat" (or .sh option in Linux) to make update to 030S (only from clean stock 025S, 026S or 028S, not from fake 027S or any mod) without clearing of Userdata Storage.
Or you can use script "x7_fastboot_tool.bat" (or .sh option in Linux) to make a new installation of 030S with clearing of Userdata Storage (from any other previous ROM).
If you can't download by my links provided in topic, please write here and I'll try to solve this.
grzegorzkuc said:
what's the score in antutu in new rom ? I have 50000....
Click to expand...
Click to collapse
My x650 shows 87000 in antutu on 030S. I can't know what is reason you having less.
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
I think that is 027s custom rom better than this 028s. I recommend you to not change anything.
Sent from my LEX657 using Tapatalk
AmanS99 said:
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
Click to expand...
Click to collapse
As an example of this way how to move into stock 028S with flashing first 025S and then just update to 028S (or 030S if you want) I prepared a video half of year ago. HERE
I understand that not all processes there are perfect... for example I used ADB to push ROM instead of MTP that is much faster =)
But if you have experience and you sure in other option of processing the steps explained in this video - enjoy and good luck.
Hope it will help somebody.
P.S.: Now I have some trouble with focus (can't focus larger then 120 cm) in stock Camera on EUI 030S and have a plan to get 028S back just for testing of Camera and focus processing.
P.S.2.: If you will have desire to get back into custom 027S you had earlier, you always can make it. It's available on both forums (XDA & 4pda). But you need to know, that changing of using between clean stock and custom ROMs is always requires you to clean a Userspace too.
Thanks for your reply . But I want to ask is there is risk of getting brick if anything goes wrong.