Related
Hi,Friends.I can only speak a little English, only with the help of Google Translate.
This ROM is Chinese official public beta MIUI V4 for SAGA.
First of all, state that I am not a developer.
How to flash ROM,please refer to the brush into the way of the other ROM.
------------------------------------------------------------------------
ROM Language:English or Chinese.
------------------------------------------------------------------------
Fully-Functional :
Battery history
Bluetooth & WiFi
Bluetooth Headset / A2DP
Google Apps
GPS
Headset / Headphones
HW Acceleration
Microphone when using apps
Mobile Data
Mobile Data usage logging
Sensors (Proximity, Light, Compass, Rotation)
Touchscreen
USB Mass Storage
USB Tethering
WiFi tethering
Camera
Camcorder
------------------------------------------------------------------------
Please note: WIPE
Must WIPE /data and /cache
Must WIPE /system
------------------------------------------------------------------------
download:http://d-h.st/z3P
downloading.......
Why this Rom is 237.81 Mb and the official one from china is 235 Mb??? http://www.miui.com/development.html (use google translator)
Its downloading so slowly , do you have same problem ?
Sent from my DesireS using xda premium
cript0n said:
Why this Rom is 237.81 Mb and the official one from china is 235 Mb??? http://www.miui.com/development.html (use google translator)
Click to expand...
Click to collapse
the official one has no kernel included. he might have put the kernel inside
45 minutes for me -.- ...but it's really official so I'm excited !!
BTW: Where does kernel 3 come from? Build by them? Official ist not out yet isn't it?
from 20-36kb/s sooooo slowly!! still downloading... and download failed 3 times!
cript0n said:
Why this Rom is 237.81 Mb and the official one from china is 235 Mb??? http://www.miui.com/development.html (use google translator)
Click to expand...
Click to collapse
I added in the official version of the kernel, or can not boot
Wody05 said:
45 minutes for me -.- ...but it's really official so I'm excited !!
BTW: Where does kernel 3 come from? Build by them? Official ist not out yet isn't it?
Click to expand...
Click to collapse
Using the HTC China OTA kernel.
cript0n said:
from 20-36kb/s sooooo slowly!! still downloading... and download failed 3 times!
Click to expand...
Click to collapse
I'm sorry, I do not know why your side of the speed is so slow.
kyeeliu said:
I'm sorry, I do not know why your side of the speed is so slow.
Click to expand...
Click to collapse
Finnaly i got it!! :laugh: Let's taste it!
Thanks
cript0n said:
Finnaly i got it!! :laugh: Let's taste it!
Thanks
Click to expand...
Click to collapse
Rom works perfectly BUT superuser is not working for me!! I tried to install some other mod from recovery (superuser.zip) but still not working..
Also when you install any .APK allways shows FC of this app.. (see attachment)
I did Full wipe and I tried it twice... so.. please solutionn!!!
:good:Thanks! :good:
Tutorial if you DONT have 4.0 / Updated HBOOT
Update your recovery.
Check HBOOT version is 1.7 or below
Boot to recovery.
Flash stock ZIP file which is included in ZIP file.
Tutorial if you DONT have 4.0 / Updated HBOOT
You need S-OFF and HBOOT 7.0. If you have HBOOT 6.8 follow steps 2
- Rename the file PG88IMG_hboot7.0.zip to PG88IMG.zip. Follow Steps (4-7)
- If you have HBOOT 7.0 and S-OFF. Flash this PG88IMG_SAGA_ICS.zip.
- Place on root of SD Card.
- Turn phone off.
- Boot with Vol Down and Power to enter Fastboot (or adb reboot bootloader)
- Press vol key. That will start update of HBOOT. Restart at step 3
- After you have HBOOT 7.0 and HTC 4.0, you must flash a new recovery.
- There is a file for every OS (ends in .bat -> Windows, etc)
- Double check that file for your OS and it'll flash a new recovery.
- Then flash MIUI ZIP via Recovery
g12_v4_tools_20120724.zip
MaesTRo's said:
Update your recovery.
Check HBOOT version is 1.7 or below
Boot to recovery.
Flash stock ZIP file which is included in ZIP file.
Tutorial if you DONT have 4.0 / Updated HBOOT
You need S-OFF and HBOOT 7.0. If you have HBOOT 6.8 follow steps 2
- Rename the file PG88IMG_hboot7.0.zip to PG88IMG.zip. Follow Steps (4-7)
- If you have HBOOT 7.0 and S-OFF. Flash this PG88IMG_SAGA_ICS.zip.
- Place on root of SD Card.
- Turn phone off.
- Boot with Vol Down and Power to enter Fastboot (or adb reboot bootloader)
- Press vol key. That will start update of HBOOT. Restart at step 3
- After you have HBOOT 7.0 and HTC 4.0, you must flash a new recovery.
- There is a file for every OS (ends in .bat -> Windows, etc)
- Double check that file for your OS and it'll flash a new recovery.
- Then flash MIUI ZIP via Recovery
g12_v4_tools_20120724.zip
Click to expand...
Click to collapse
Can you just put the boot.img so that miuiandroid users can use the rom directly
On Miui.com thread a guy posted the boot.img.
But you need to download from here :http://115.com/file/an6ehsht
Last 2012-8-4 21:46 HeavenDemon
official 4.0 with boot.img on: http://115.com/file/an6ehsht
brush into the tool: http://115.com/file/dpgwj99u
I cannot connect to WiFi using the rom. Tried with different kernels. Anybody have the same experience?
I installed the Rom with Tutorial but still have Superuser and same FC installing any apk file problems..
show black screen after flash rom ,what i do
Thanks for posting.
No problems downloading and it runs well, I don't know why others have problems...The only thing I encountered was the WiFi not being able to connect as ADHOC, I flashed another supplicant and it shows the network but will never even try to connect..Also reboot into recovery option? I'm surprised there wasn't one. The default launcher (personal taste) completely sucks, trebuchet? Some good features such as access flashlight from lockscreen (my favorite) and configurable back button to kill delay, excellent!! and a few other small things.
twiice said:
Thanks for posting.
No problems downloading and it runs well, I don't know why others have problems...The only thing I encountered was the WiFi not being able to connect as ADHOC, I flashed another supplicant and it shows the network but will never even try to connect..Also reboot into recovery option? I'm surprised there wasn't one. The default launcher (personal taste) completely sucks, trebuchet? Some good features such as access flashlight from lockscreen (my favorite) and configurable back button to kill delay, excellent!! and a few other small things.
Click to expand...
Click to collapse
I am Chinese, I want to show something I read from miui.com forum for desire s.
1. For wifi cannot connect as adhoc, this is because miui remove this feature from v4, so all the official miui v4 devices do not support this feature at all.
2. The rom is based on HTC China 4.0 OTA, not CM9, so the size is increase strangely.
3. There are some UIs with HTC Sense included, the bug is reported to miui dev team, but no response.
4. Some people have the networklocation apk fc, it's because miui use baidu apk for location, not google.
5. Some people said the rom is extremely un-smooth (maybe I use the wrong word), especially when sliding icons on desktop and open folders.
6. The GPU 2d accelerate is disabled by miui dev team because of the issue from the Qualcomm chip. (But the port version can enable this)
7. After pressing home button to return to desktop, the rom reflection is very very slow.
These bugs are found by miui forum, can any devs fix them? Especially for 3,4,5,6,7:angel:
The reason for this User Thread is so that we can keep the development thread clean. Post in the development thread only if you have something useful to contribute such as a logcat, or any dev-related comments. Post any suggestions, bug reports, questions or comments about the rom in this thread,
What's working and what's not?
Working:
Camera - Yes, this means Camcorder also works! 1080P Video shooting and playback work great.
Bluetooth
WiFi
Audio
SD Card Storage
Battery Meter
And of course Hardware Acceleration!
Not Working:
RIL (Mobile Network) - This means no calls, no SMS, no Data, no anything related to the functions of your SIM Card! T-Mobile WiFi Calling also doesn't work.
Information On Dual Booting Roms
Since we currently have an issue with the network radio on our CM10 roms, most people will not be able to use this rom as a daily driver, and would prefer to stay on a fully functioning GB rom. This dual booting method lets us have the best of both worlds! You can have a buttery smooth and fast CM10 rom for enjoying all of Android Jellybean 4.2.1 goodies and a fully function Gingerbread rom when ever you need to make a call and such. For now, this is the best we can do. It's simple and very fast to switch between roms. What else could you ask for? ;D
Installation Instructions Including Dual Booting
DISCLAIMER
I (WE) AM NOT RESPONSIBLE of any damages to your device related to the use of this ROM or the dualboot toolkit. You do this at your own risk. Even though this has been tested and works well, using NVFLASH may brick your device if done incorrectly.
This ROM comes in two flavours: The dualboot toolkit or the Original flashable ROM
Dualboot ROM Instructions
WARNING! NVFLASH will format EVERYTHING, including internalSD. Make sure you backup your important files on your externalSD card
PART 1 - Resizing system partition
1) Unzip the dualboot toolkit and unzip NVFLASH_Resizer-G2X.zip.
2) Power off your phone and remove the battery. Keep vol. up and vol. down held and plug the phone via USB to a WINDOWS computer.
3) Windows should add an "APX driver". Go to control panel -> Device manager and right click on it -> Update driver -> search in system. Then, browse to the drivers folder inside the NVFLASH package and choose nvidiausb.inf. Approve any error messages (Windows 8 users read my FAQ). Install the Nvidia Fastboot driver.
4) Unplug your phone and hold down vol.up and vol.down. Replug it again and double click on flash.bat inside the NVFLASH folder. KEEP BOTH BUTTONS HELD DOWN DURING THE WHOLE PROCESS!.
5) When NVFLASH is done, unplug the phone and put back the battery. Reboot into recovery with power + vol. down. Plug it back and go to mounts and storage -> mount USB storage. If your PC asks to format the internal SD card, select yes.
PART 2 - Installing ROMS
1) Download the desired "call/SMS" ROM and extract boot.img from it's flashable zip. Rename it to boot1.img. Extract Step3_bootimg.zip from the dualboot toolkit and copy-paste boot1.img into system/boot, replacing the file that is already there. Repack Step3_bootimg.zip.
2) Copy-paste your desired ROM into the 0dualboot folder and send it to your device SDcard with everything it contains (your device should already be in the "mount USB storage" menu).
3) From the recovery, flash Step1_enabler.zip. When the screen goes black, hold power + vol. down to get back into recovery.
4) Flash your desired ROM, then Step2_ROM1.zip. Reboot to the OS.
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
And there you go! To switch from one OS to another, just open the systemchanger app and click on "switching"!
Credits to bihariel for the original method. See the original thread here.
Original flashable zip ROM instructions
1) Boot into recovery with power + vol. down
2) Wipe data/cache, then mounts and storage -> format system
3) Flash this ROM
4) Advanced -> Wipe dalvik cache and fix permissions
5) Reboot and enjoy!
Special trick : In settings, go to About phone and click 6 times on Build number. This will pop up the developer and performances options. In performances options, CPU settings, change the governor from INTERACTIVE to SMARTASSV2.
Downloads
ROM with DUALBOOT Toolkit ***BETA***
DOWNLOAD HERE!
Original flashable ZIP (For single boot)
DOWNLOAD HERE!
Credits
See Mazout360s original thread here for the full list!
Thanks to bihariel for the original method for the Optimus 2X which I adapted for the P999. Great job!
Special thanks to Core Memory for helping me start this project[/CENTER][/QUOTE]
*All Information On this User Thread is from Mazout360s Thread in the Dev forums. Credits go to him for the Instructions/Downloads/Etc.
Quick template for now.. I'll update it as soon as I can.
Mazout Kernel on Stock 2.3.4
I flashed Mazout360's GB kernel over kwes' rooted 2.3.4/March 2012 basebannd. Was running pretty smooth, but had some problems
> Bluetooth icon at top of screen did not turn off "connected" status when I turned off my headset (BlueAnt q2.1)
> Had a few freezes. Installed SetCPU to keep max speed at 1015MHz but still some stops. Some out of nowhere, some in the middlle of doing stuff
> Finally started shutting down often. Tried to get a terminal emulator from the Market, but Market started crashing, even after several reboots. Could not get a kmsg to send.
Reinstalled my nandroid. No time at the moment to play more, need my phone reliable for some days to come. Hope lots of people try this kernel out and that I get more time with it. Nice to have new Dev activity for the G2x.
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
grantusmantus said:
Quick question, i was wondering if it matters what zip tool we are using? Can i use 7zip for this, or should i use winzip?
Sent from my Mazout driven Reborn Hellbird.
Click to expand...
Click to collapse
Shouldn't matter, but I always use Winrar.
Micro SD card not detected
I was following along the steps and everything was going well until step 5 in part 1. when i rebooted my phone into recovery and pulged it into the PC nothing happened even though i followed exactly what the steps say, then i continued on and everything was going well until the end, where i found out that i couldn't get the data that I backed up to my Micro SD card because the phone doesn't see it.
Please help, I'm a noob around here.
I appreciate all the great work
did this project die?
reeshmd23 said:
did this project die?
Click to expand...
Click to collapse
No it didn't. My build computer broke and I need to setup a new HDD with my build environment. I'll make a new version as soon as possible.
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
0b095 said:
hello,
I have dualboot now with hellfire2.4.2 and cm10 mazout's. So one is cm 7 and the other one is cm 10, I want to flash kernel but how? If I flash cm7 kernel will it block the cm10 rom or vice-versa?
guys I have just realized that I do not have dualboot after that steps
5) You should have a Systemchanger app. Open it, click on "Switching" and give root permissions. When the screen goes black (again...), hold power + vol. down to get into recovery.
6) Flash ROM2.zip and Step3_Bootimg.zip and reboot in the OS
I had systemchanger app and clicked on switching after that I flashed mazout's rom then when I open app drawer in cm10 rom, I noticed that I do not have systemchanger app anymore nor camera app.?? what should I do? If I do all steps all over again sould it be working ?
Click to expand...
Click to collapse
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Hey. I got everything to work and am dualbooting nicely. My problem is kernel. I flashed a recent CM7 with this and everything went fine. Then I went to install the most recent CM7 kernel from Maz (the OC) and that works until I switch to Rom2 and back. Then the wifi gets an error and wont do anything. The kernel wont stick. Did I miss something?
Also, last night went to bed with my phone charging and when I woke up my phone was burning hot. Had Max OC at 1100.
Thanks! Works great having a taste of 4.2.1 and a phone!
Sent from my LG-P999 using xda app-developers app
Mazout360 said:
If you flash another ROM, you have to flash the corresponding stepX....zip file right after before rebooting, else you won't have the dualboot app.
Since android 4.2.2 just got out, I'll wait until it gets stable and make my upcoming build out of it For now, my phone battery doesn't work very well so I can't really test anything until I get a new one.
Click to expand...
Click to collapse
thank you, I see the problem now, and two question more; do I have to redo PART 1 - Resizing system partition everytime when I install different rom combinations or reinstall same roms and does that Resizing system partition harmful/useless or slows down the phone IF I only use 1 ROM?
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
adamiscool said:
Oh shoots. Somewhere along the line I managed to break the wifi
MAC address comes up as unavailable in jb, just says error whenever I try to turn it on in gb. I'm thinking start the process over?
Sent from my LG-P999
Click to expand...
Click to collapse
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything.
Edit: fyi I use maz's latest kernel 0205OC
Sent from my LG-P999 using xda app-developers app
Freakthis08 said:
You need to flash a kernel. I am having the same problem, but flashing a kernel after switching back to GB fixes everything
Click to expand...
Click to collapse
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
adamiscool said:
So, you mean that after using system switcher app, do power+vol up and flash kernel? Because any time I've tried that it only works on the first instance when i boot into gb. Once i go to jb and back again, the kernel goes back to stock. I'll try again though. Maybe fix permissions too!
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
When you system switch back to GB, reboot back into recovery and flash a kernel. I wouldn't say it goes back to stock because if it did there wouldn't be a wifi error like that. But for some reason JB works fine nothing wrong I have seen yet, though I just noticed I don't have a camera/gallery.
After switching back and forth so much I just flash the kernel and don't do anything else because nothing has seemingly changed if I wipe anything or fix anything.
If Maz has answer for this I would be much appreciated or anyone else for that matter.
Sent from my LG-P999 using xda app-developers app
Edit: figured it out. A new boot1.img does need to get made with the new kernel already installed.
I created a new boot.img per the instructions on the original dual boot for p990 thread with maz kernel. Then I repacked step3_bootimg. Reflashed rom2 and the step3, then voila! So, you have to redo a couple steps if you want to update one rom's kernel.
Pic no longer related.
guys im having some trouble, when i go to the systemchanger app and grant permission instead of the screen going blank it gets stuck on a screen with two lg logos.
i think i havent installed the fastboot drivers correctly. i assumed it gets installed when i run flash.bat, but it may need to be installed seperately. if it needs to be installed how do i do it cause its just a .bin file and i have no idea what to do with it
---------- Post added at 10:20 PM ---------- Previous post was at 10:15 PM ----------
adamiscool said:
I'm considering the dual boot, but want to know if it's possible to go back to single boot if/[hopefully] when radio is fixed. I suppose it'll be a matter of using original nvflash and format to have only one partition?
*edit1* Ok, now I'm getting my toes wet with this. fastboot.bin...what am I doing with this? The instructions say "install NVidia fast boot." Ok, but how? Or, has it already been installed with APX? I'm confused.
*edit2* ok I have dual boot! Wow this is interesting. Been running it through different combinations of reboots through system changer, and it seems when I update gb to the latest mazkrnl it won't stick after switching to jb and back again.
Do I need to use the boot.img from the kernel and repack it into step3?
Sent from my LG-P999
Click to expand...
Click to collapse
hey, i have the same question, did u install the fastboot.bin separately or does it get installed with the flash.bat???
Hi there.
As most of you already know, starting some time ago, CM team has decided to include a script check for firmware/hboot that will allow to flash a CM based ROM only on newer firmware/hboots (2.13.0000, 2.15.0000, 2.15.4444). This is valid for all 3.4 kernel based ROMs (CM 10.2, PACman, PA, Odyssey and so on). This check was introduced because some were reporting problems by flashing such ROMs on lower hboots and it was assumed that you MUST have the latest firmware in order to flash and run them.
This leaves few options for those having lower hboots: either upgrade to latest firmware OR not flashing the ROMs at all.
What if, someone has a lower hboot/firmware and IS able to run those ROMs without issues? The previous assumption that having lower hboot will make the ROM not working/booting is wrong...at least for me and I don't think I'm unique. I'm sure that there are more users having lower hboots that could run the latest ROMs without having to upgrade their firmwares. I'm on 1.06.0000 hboot S-On and I'm happy with it. I didn't had any single ROM flashed on my device that didn't run. I don't like the idea of being forced to upgrade (going through a procedure that for some proved to be difficult or bricked their phones) without needing to
Well there is still hope....
DISCLAIMER
PLEASE BE AWARE THAT I DO NOT RECOMMEND TO TRY THIS IF YOU DON'T KNOW WHAT YOU'RE DOING. EVEN IF FOR SOME USERS THE 3.4 KERNEL BASED ROMS WILL WORK ON LOWER HBOOT/FIRMWARE, CM DIDN'T PUT THAT CHECK THERE FOR NOTHING. I SHOULD NOT BE HELD RESPONSIBLE IF YOU FLASH SUCH ROM AND IT WON'T WORK. ALSO DO NOT REPORT ANY BUGS IN CASE YOU FLASH A ROM THIS WAY
Now, what people maybe thought already (but some don't know how to do it) is that you need to get rid of that script check in order to flash such ROM. Following the steps below anyone can get rid of the check and enjoy the newest ROMs without upgrading their firmware, presuming such a ROM will run on their firmware/device
Prerequisites:
In order to do this properly anyone will need two tools
- PPCGeeks Android Signer application (or similar) - DOWNLOAD
- Notepad ++ (or similar) - DOWNLOAD
Download and install both from links above then you're ready to go...
Steps to change the script & flash ROM:
1. Download the ROM of your choice and save it on your PC
2. Create a folder with a distinctive name (say CM 10.2) and extract the ROMs ZIP there
3. Look for the file "updater-script" located in \META-INF\com\google\android folder where you have previously extracted the ROM
4. Open the file using Notepad++
5. You will usually find the check for firmware at the beginning of the file and it'll look like something like below:
assert(getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000");
That means that, only the users having hboot 2.15.4444, 2.15.0000 and 2.13.0000 will be able to flash that ROM, anyone else will be receiving an error and ROM won't flash
6. Delete those lines with Notepad++ then save the file
7. ZIP the whole ROM again and give the ZIP a name
8. Sign the ZIP with Android Signer then copy the signed ZIP on your phone's sdcard
9. Flash the ROM
This should do it and you'll be able to flash such ROM.
There is an alternative method of extracting the file from the ZIP, deleting the lines then putting it back in the ZIP...this will skip the unzipping and signing steps but depending on how you'll do it it could also give you script errors when flashing (Status 7 or Status 6 errors). Steps to be followed for this "quick" method are:
1. Extract the updater-script from the ZIP and save it on your PC
2. Edit it with Notepad++ like I've described above
3. Open the ZIP with WinRAR and navigate to the place where updater-script is (\META-INF\com\google\android) and delete it from the ZIP
4. Using drag&drop, take the modified updater-script and drop it onto the opened WinRAR window in the location where it should be. There will be a popup windows to confirm adding the file to the ZIP, just press OK.
5. Close the ZIP and flash it
Well many of you might already know and do this one way or another but there might also be some users that don't know how to do it and either ask for help in various ROM Development threads or just quit flashing the ROM
So this is for all those that would like to try the new 3.4 kernel based ROMs and don't know how to do it. It won't guarantee that such ROM WILL WORK on their devices, it just allows flashing it even if they don't meet the firmware requirements. If after flashing, the ROM won't boot or it'll boot loop, there's almost sure need for a firmware upgrade in order to run it.
Thanks rapier. This helps me tons.
I guess the only annoying part about it is that we have to delete those lines each time there's an update/nightly that comes out. But for the time being this will suffice until I have the luxury to upgrade my firmware.
Sent from my HTC One S using xda app-developers app
I too am on Hboot 1.06 and S-on and have never had problems with other ROMs. Being away from the community for several months i'm a bit bewildered by all the risky processes I have to carry out to get my phone to accept the new 3.4 kernel.
So I will give your method a try right away!
Many thanks
RichardW1992 said:
I too am on Hboot 1.06 ...
So I will give your method a try right away!
Click to expand...
Click to collapse
Have you had any success? I am very curious.
Thanks
Patrick
This looks interesting and looks much less complicated than the whole upgrade process.
I'm on HBOOT 1.13 and S-ON; I tried to flash CM 10.2 just for fun but I got the error message (script related).
I read that those who had no problem running the latest Trickdroid and Viper can use this ROM without upgrading their firmware. TD and Viper are the 2 latest ROMS I've been using.
I'm gonna try this this weekend or next week lol - although I prefer the features of Sense ROMS.
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
---------- Post added at 09:54 PM ---------- Previous post was at 09:11 PM ----------
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
This is known about theme'd files, you cannot sign them even with command line. They must be opened with 7zip as not to break the signature and edited that way, then close and flash.
Click to expand...
Click to collapse
I did that, so I guess I dont need to re-sign the file
I'll flash another day, Im really tired
By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
Thanks
salutcemoi said:
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
...
Click to expand...
Click to collapse
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
salutcemoi said:
...
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
I did that, so I guess I dont need to re-sign the file
...
Click to expand...
Click to collapse
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
salutcemoi said:
...By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
...
Click to expand...
Click to collapse
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Rapier said:
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Click to expand...
Click to collapse
thank you !
Much appreciated :good:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
cougzzz said:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Shouldn't be affected by the script change. This change only allows you to flash the ROM, nothing else. You can try a WiFi fix or reflash kernel for this kind of issue. I had CM10.2 running well on my phone and didn't have any problems with WiFi. Same for Odyssey ROM which is also Android 4.3 with same kernel as I know
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
I also had exactly the same issue with CM...could not fix it even after flashing kernels....gave up and went to AOKP ..now Wi-Fi works, still no 4g..but that wasn't working with CM either
Sent from my HTC One S using xda app-developers app
okaiuz said:
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
Click to expand...
Click to collapse
Same here
I'm also hboot 1.13
Sent from my HTC One S using xda app-developers app
I've read it in the forum for either AOKP or CM that lower HBOOT like 1.13 is going to cause bootloops....I was hoping that using this method, in the OP thread, I'd be able to upgrade to newer ROM...but I wasn't able to (bootloops)
Sent from my HTC One S using xda app-developers app
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
el_smurfo said:
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
Click to expand...
Click to collapse
Yup
I rooted my phone and flashed custom roms before the official JB firmware update.
Sent from my HTC One S using xda app-developers app
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??
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.