Hello, first of all i am sorry for my english.
I beg you to help me.
I wanted to do an update from my Cuoco92 to Lineage ( https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577 ) and i surely made something wrong because the phone was litteraly stuck.
So, i waited 1 hours... and nothing happened. Then, I decided to force the reset. Recovery told me that no rom was installed.
Then, i tried to install several roms from the website (cuoco, linegae, small eui...) but there are some issue :
- google play doesnot want to work at all.
- most of the time, the phone is saying something like "data corrupted. Put in it factory mode" and even when i reset my phone in factory mode, it is still telling me that.
Now, i am giving up because sideload said me "Error 7" each time i try to install something new.
I need your help. I beg you, i can give you with a steam game or something like that but i want to fix that...
Someone want to skype or i dont know?
Thank you!!
in TWRP please go to wipe > format data > yes.
then install any rom.
Heyyo, please upgrade to the latest version of TWRP. 3.2.1-2. it has fixed ADB sideload where as older versions it is broken.
https://twrp.me/leeco/leecolemax2.html
Also, another option is to use ADB push which tbh I always prefer over sideload so that the full zip is on the device.
IE...
adb push NameOfFile.zip /sdcard/
That will copy that zip to the sdcard folder which is the root of the data partition so it can be easily deleted once you are fully booted into the ROM.
For Gapps? I recommend MindTheGapps arm64. It's fully compatible to LineageOS and Oreo ROMs in general where as OpenGapps for Oreo is still of beta quality.
Lastly, I recommend upgrading your device firmware. X820 30s is the latest stable but arguably 466D has a newer timestamp for the modem portion of the firmware so in theory it should have better cellular connectivity.
All links can be found in the LineageOS 15.1 for x2 thread.
Good luck!
Related
I will try to describe problem as much as I can:
1.Unlocked bootloader(unofficial way).
2.Installed TWRP 3.0.M4-0(success).
3.Installed(in such order as stated by some guide) : CM14.1 Firmware(Kate) - 26.11.2016 >>> CM14.1-20161222 Nightly Kenzo >>> Opengapps arm64 7.1 nano with TWRP(success).
4.Reboot, CM 14.1 launches correctly, although it has saved settings and apps from MIUI, making it real mess. Now the problem starts. I assumed by doing factory reset I'll get clean 14.1 - wrong. After that turning on my phone causes it to launch TWRP instead of system.
(Failed)Attempts to fix:
1.Install CM14.1 again.
2.Wipe + install CM14.1 again.
3.Can't get into EDL mode(as stated here http://en.miui.com/thread-290959-1-1.html)
Additional info:
1.Fastboot mode launches, but 'adb devices' doesn't find anything(it was before). Device manager sees phone as well as MiFlash. Not succesful trying to update drivers(system found them up-to-date).
2.I have Kate edition, started installing after reading this http://forum.xda-developers.com/redmi-note-3/how-to/index-custom-roms-t3396628 , last posts states, that sometimes it's necessary to flash non-hlos.bin file to system(not sure if even necessary in my case, as CM14.1 launched before factory cleaning).
3.Only similar thing I found is : http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html , but about different device and CM version.
I'll appreciate any suggestions on how to fix it(either getting into CM14.1 or back to MIUI, preferably the first).
@edit - Solved myself. For anyone encountering such problem, I could install succesfully MIUI back, when I launched my windows in Disable Drivers Signature Mode.
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
h0LLe said:
what exactly have you done at the point "factory cleaning" ? do you mean anything in running android or in TWRP?
Click to expand...
Click to collapse
Factory clean from android settings after running CM14.1 succesfully for the first time. No idea why it caused a problem, but as I wrote in edit, it is solved.
So I got my shiny new device today, and it feels really nice. I worked with the launcher it came with, tried another one, and realized that yep, I gotta root and install a new rom. The notification bar just annoys me too much as I'm used to having quick actions and other things in there.
So, I followed a few guides, and finally worked my way through to having my command line find my device and can successfully reboot it into fastboot mode.
At that point, I realized that I can boot into recoveries without flashing them first (essentially trying them out to see how it works). However, I tried the 4 official version on the twrp site, and one made by a user here (cuoco92). They all successfully boot into the recover using the command "fastboot boot nameOfFileHere.img". At this point, every single recovery failed to respond to touch and volume presses. I can press the power button to turn off the screen, and pressing power to turn the screen back on shows a locked recovery screen, but I can't slide the screen to unlock it.
This is quite concerning to me. I don't want to flash a recovery for good if it's not working properly. I hope this makes sense. Or, is it normal to just flash a recovery and hope for the best? Do recoveries work with just booting to them without being flashed?
I haven't rooted and/or flashed any devices in about 5+ years, the last being a phone from virgin mobile that supported sd cards. When installing new roms, do we store the zips in the root of the phone, or does this get cleared out/deleted when doing the wipe cache/dalvik/etc?
Personally, I just want to make sure I don't rush into this, as there seems to be fragmented results when searching around for twrp not working with touch. I know these things have been asked before plenty of times, and I hope I don't come across as another "ugh, this again" post. I really appreciate any responses!
you never did, then just leave it as it is...its a nice phone eui is not bad... take it easy
Try booting the official TWRP recovery. As far as I remember, some of the versions tweaked by Cuoco92 had issues with the touch panel.
Anyway, EUI is not that bad, as your were told. While I used it, I also used an app called "Notification Toggles", which lets you get Quick Settings like toggles on notification area. It's nice and easy to set up, and the results, although not the same as having the AOSP toggles, is quite nice and convenient.
BTW, which stock ROM did your phone come with?
I have tried 4 different official twrp files (all from the twrp site). My phone is an x820 6gb/64gb and came with EUI version: 5.8.019S (Stable). EUI is nice, very fast and sleek. Maybe I do just need to get used to it, or maybe it's just me itching to try out the different options available since I finally have a phone is not carrier/manufacturer locked down.
Heyyo, hmm that's very odd indeed! I wonder if maybe by temporary booting Cuoco92's TWRP it could have messed up your recovery hmm...
I'd recommend first to flash the stock recovery over your current one and then reboot to fastboot and then flash TWRP. Hopefully this will erase any problem that Cuoco92's recovery could have caused.
This was the guide I followed and it worked flawlessly for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I never actually flashed any of them. I have only ever just tried booting into them using "fastboot boot recovery name.img". I have not used the fastboot flash command for any of the files.
The only thing I can do after booting the recoveries is hold the power button and eventually the phone will boot up normally.
Remember that I just wanted to boot them to make sure they worked before flashing them. I'll be checking out the guide you linked shortly.
Haven't flashed any of them eh? Hmm should work just fine then... Have you tried TWRP 3.0.2-0 ? I know that one was built with Marshmallow sources
As for which ROM to try? I'd recommend OmniROM if you want to try a custom Nougat ROM.
If you want to see why I think so? I made a massive post or two about it here heh
https://forum.xda-developers.com/le-max-2/help/party-rom-best-help-t3691165/
Thank you so much for the guide you linked. I'm making a little bit of progress here.
I found a twrp recover by cuocos92 that is labeled V3 (apparently from what I read in other threads, V3 seems to be good with the 6gb/64gb models). This recovery allows the use of the touchscreen . Remember that I am only using the "fastboot boot" command so no flashing yet.
Now that I am in a working recovery, I kept hitting "keep read only" so that the stock recovery would not be replaced. I set out to make a backup. Well that kept failing with attempts of trying to mount /system and such. Off to more reading, found out that using the Wipe->Swipe to Factory Reset inside twrp fixes this. I did that. I successfully created a backup.
Now to try to flash the SuperSU zip I have, which was previously copied to the root of the phone from my pc. Can't see any zip files on the internal storage. Reboot the phone (forgetting that it takes a long time after the wipe). Copy the backup to my pc. Copy the SuperSU back to root of phone. Restart the process of adb and fastboot -> back into the cuocos92 V3 recovery. Still no zip to be found. Couldn't mount system again...
Did some more reading. I just attempted the Wipe->Format data. I am currently rebooting back into the phone to set it up again. Apparently, a lot of people say this needs to be done if we did not reboot after unlocking the bootloader. Since twrp has been asking for a password each time I entered it, the format data is supposed to solve this.
I'll edit/post again with more steps or results.
I apologize for the second post here, but this seems more than should go into an appended edit:
After doing the Wipe->Format data, it's advised to reboot back into the recovery. Without flashing the twrp cuocos92 recovery, my thoughts are it would just be back into the stock recovery. At least the twrp version works, so I have no problems with flashing it. And then I'll have to Wipe->Format data again, reboot back into recovery, and then I can flash my SuperSU zip. But how can I get my SuperSU zip on the phone?
Doesn't Wipe->Format data remove it? Everytime I reboot my phone after that the SuperSU on the root of the phone is gone. I can't seem to mount to my pc from the recovery either, clicking the usb storage just unchecks itself right away, and clicking the enable MTP doesn't seem to do anything. So, even if I flash the recovery, Wipe-Format data again, reboot back into the recovery, I still don't see a way of getting the SuperSU zip onto the phone anyways.
I know it probably sounds like I'm whining by now about how things aren't as easy as it seems. I'm trying to be descriptive in what I am doing and what's happening.
Hmm by chance are you using Windows 10? At least I've noticed for me it fails to properly mount the correct drivers for ADB and MTP for TWRP. I'd recommend checking device manager.
If I remember correctly here's what mine looked like at first
https://photos.app.goo.gl/wXaqbi3OeH3bKEf62
Select MTP > update driver > browse my computer > let me pick > (standard MTP Device) > MTP USB Device
Sorry I'm not in front of my PC but I'm sure it's something like that to solve it
If that doesn't work? You can always use...
Code:
adb push ROM.zip /sdcard
Which will copy the zip file to the root of your data storage (on the Le Max 2 much like the One Plus 3 they use /Sdcard as a shortcut since we don't have external Sdcard hardware).
As for system read only? Swipe to allow modifications. Can't flash a ROM properly if the system is read only eh? Hence the failed to mount system.
It's really just there as a disclaimer to cover their ass in case people use TWRP improperly and brick their device. Following green man gaming's guide is safe as I've used it plus many other people as you'll see in his replies
I'd also recommend following the guide and flashing TWRP to your recovery. I only did boot recovery image for backup and then booted to EUI and copied that backup to my PC.
Format data is handy to get rid of encryption and also give you full access to your storage capacity because when I didn't before I didn't get 54.43GB of data storage only something like 40GB.
Tbh I haven't used any custom EUI ROMs but if you're fighting with TWRP? I know Cuoco92's eui has a fastboot installable version
Hope this helps
Well thank you so much for the information. I am running windows 10, but never saw mtp under portable devices, only the phone name Le Max 2. That's ok, as I booted (still not flashed) into recovery and this time I swiped to allow modifications. I still couldn't mount /system but I was able to use the adb push command and the SuperSU file appeared inside the /sdcard directory when looking under Install inside twrp. I swiped to flash the zip, then hit reboot system. Looking in the SuperSU app, I noticed that the setting "Install SuperSU into /system" is greyed out. Well, at least I think it worked.
At this point in time, since things appear to be working, I'll be flashing the recovery and installing OmniRom (it was either this or Resurrection Remix). I think if the play store just works on OmniRom like people mention, it'll be worth it.
So, my steps will be to:
adb -> fastboot -> fastboot flash recovery fileName.img
recovery -> wipe -> factory wipe (using factory to get rid of system encryption) -> reboot back into recovery
recovery -> wipe -> dalvik/cache (do i still need to do this after factory wipe?)
adb -> adb push romFileName.zip /sdcard
adb -> adb push gapps.zip /sdcard
recovery -> install -> /sdcard -> romFileName.zip
recover -> install -> /sdcard -> gapps.zip
At any point do I need to flash SuperSU again? I guess I should after flashing the rom/gapps because, afterall, SuperSU is an app.
Once again, thank you so much for all the information that you have already provided!
Heyyo, it's always recommended to do a full wipe when installing a different ROM so you should format data, wipe system, data, dalvik and cache and then install the ROM of choice with Gapps of choice
Wiping system is OK when flashing a ROM as it'll write into system.. plus there's always the risk of instability if system is not wiped if a Gremlin setting is left over from previous ROM
I'd recommend using Magisk v14.3 over SuperSU as SuperSU doesn't have the same functionality as Magisk for passing SafetyNet...
Plus Magisk is full open source software (FOSS) where as SuperSU is closed source so gotta love that open source (this part is more personal preference since Android is built upon open source and people working together).
Plus there's really cool Magisk modules you can do like ART Optimizer and so fourth if you check the XDA forum section for it
Also, you're welcome! We all had our start on XDA at different points and passing on the knowledge I find is just as important as the ROMs we love
Don't use SuperSU. Magisk is the way to go for rooting nowadays. Easy, systemless, updated frequently to pass safetynet. It's a no brainer.
REMOVED PROJECT
XDA:DevDB Information
AOSP for HI6250 Devices, ROM for the Honor 5C
Contributors
Meticulus
Source Code: https://github.com/Meticulus/android_kernel_huawei_hi6250_4.1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2017-12-03
Last Updated 2018-01-18
Hello
I am using this rom on P9 Lite and I can report that pressing the globe icon in Clock application will force close the application.
Also had problem with default Gallery application. I had to install QuickPic, could not reproduce the problem.
If anything will happen again I can send you logcat.
Also I think that Default Camera is taking sometimes blurry photos.
Other bugs are already reported on your webpage.
But aside from that its a best rom on P9 Lite Good Job !
Hi,
I tried to install this ROM on my stock Honor 5C NEM-L51.
Unfortunately I encountered an error when flashing zip via TWRP. TWRP immediately restart after I launch the flash command. Nothing installed and a bricked phone.
And it is the same with every ROM and TWRP found here on xda.
Any idea why this is happening ?
Edit : I managed to install the zip thanks to ADB sideload through TWRP.
Varuu said:
Hi,
I tried to install this ROM on my stock Honor 5C NEM-L51.
Unfortunately I encountered an error when flashing zip via TWRP. TWRP immediately restart after I launch the flash command. Nothing installed and a bricked phone.
And it is the same with every ROM and TWRP found here on xda.
Any idea why this is happening ?
Edit : I managed to install the zip thanks to ADB sideload through TWRP.
Click to expand...
Click to collapse
Strange, I never heard of any problem like this... Maybe hardware sdcard problem?
howpathetic said:
Hello
I am using this rom on P9 Lite and I can report that pressing the globe icon in Clock application will force close the application.
Also had problem with default Gallery application. I had to install QuickPic, could not reproduce the problem.
If anything will happen again I can send you logcat.
Also I think that Default Camera is taking sometimes blurry photos.
Other bugs are already reported on your webpage.
But aside from that its a best rom on P9 Lite Good Job !
Click to expand...
Click to collapse
There is a thread for p9l for this ROM. Suggest to post there.
Gallery is old and not updated by Google anymore. If you find it in Settings->apps and allow permission to camera and storage then it work.:laugh:
Installed this rom yesterday on my Honor 5C NEM-L51 and it works quite well. Super clean, very smooth. First tried to flash the rom with the venus twrp, which didn't work (wrong device), couldn't flash your twrp (this may be because i can't get into recovery while my device is connected via usb, always get into erecovery, but didn't knew it when i tried your twrp, so very possible that your twrp works, i just didn't do it correctly to get into recovery) than used the latest Elite TWRP and it worked with it (of course only when i noticed that i can get into recovery when im not connected via usb). Oh and a gentle note to everyone trying to flash a rom on his honor 5c device, DO A FULL BACKUP, YOU NEED IT, it seems like the honor 5c custom roms only overwrite some files or something, but need all the other emui5x stuff, so you can't just fully wipe your device and reflash the rom and everything works again, you always need to restore your backup first and than flash the rom.
Things i had trouble with while trying to flash this rom:
- The installation guides from johannes dostal is outdated in my opinion, because it says you have to wipe data, which makes the device unbootable (had to restore/resize the data partition, install backup again). I only did a factory reset before installing this aosp rom over the emui 5.x
- The installation guide from HC5DEVSPORTAL's links to some weird ad stuff
- The video installation guide from you is helpful, thanks for that. Maybe better link to that video
Some other Tips/Issues i had:
- When i first tried to flash this rome, i accidentially wiped data, system and so on (ticked everything except sdcard/internal storage i think). After flashing this rom, the device bricked, because the data partition was corrupted.
After some googling i found a solution for this, TWRP is able to format/repair and resize the partition, after this was done i could restore my backup again and try to flash the rom again.
- MTP sometimes didn't work for me in TWRP, this is a bit of a problem if the device doesn't boot anymore, but i could work around this issue by using adb push/pull. So if you have similiar problem, give adb push/pull/shell a try. Saved my ass
As already mentioned, the rom works quite well (ok, only using it since 12h). But there are some things i want to mention:
- The camera isn't working for me, neither the default camera app nor any other camera app. I always get the "No connection to camera possible" error
- The security patch level is from october 5th. Even if this is for android quite recent, it's vulnerable against the krack wifi vulnerabilty. For sure not your fault, don't know how hard it is to merge those security patches, just want to mention it.
Thanks a lot for your work, hated EMUI5.x, loving AOSP
No more development from me.
Hi all,
So yea, i when i went into twrp 3.2.3-1 and i installed magisk 18.0 following happened.
(was following this guide: https://www.gizmochina.com/2019/06/28/install-twrp-root-poco-f1-magisk/ )
Okay first of all, i didnt get root access, even tho i had the magisk itself appear in the apps (along with magisk manager).
SO what i did was try to unninstall it following this guyide: https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242 (idk how to hyperlink)
(mind you im not trying to unroot it, since it failed to do that, without even telling me, found out when i tried some root only apps, and checker)
That didnt work either, matter of fact made matter worse. After doing that now my magisk manager app wont even open, its stuck and after couple of seconds it says App stopped working blabla.
So i the next thing i did is i downloaded Magisk-uninstaller-20191102.zip (idk from who im pissed beyond belief atm) that like did its thing from twrp except 1 line of red code saying something failed idk.
Then i tried: https://magiskroot.net/uninstall-magisk-module-twrp/ installed the zip on the phone, flashed into twrp, tried installing the stated zip, but it says "Invalid zip format! "Error installing zip file '/sdcard/mm-master.zip' (red line)
Like, why dont stuff simply just work? Why wasnt i rooted in the first place, and how do i completley get rid of magisk (ALL OF IT)
I dont know if magisk is installed like deeply in some software or like a regular app (thats why i didnt unninstall it that way) because i dont want its remains somewhere in my system..
Will another factory reset solve this?
Please. Thanks.
Edit: Can i have A PROPER guide on how to root this damn phone?
Edit: Cannot install Paypal (doesnt show up) which means something is definetly still going on.
first of all bro, always mention what Rom you were on? if stock rom then which version/build of MIUI? if custom rom then which one (pixel exp, crdroid, havoc, lineage, carbon, nitrogen, etc etc)
now
twrp3.2.3-1 is way old for Poco, now Twrp3.3.1-x is out , you should try that one!
also if i remember correctly, Magisk18 is for OREO, so I am pretty sure your android version is 9.x
please flash latest recovery and magisk20.1
it will surely work!
a proper guide is already running in discussion forum with MAXX views count! please search
edit: older twrp cannot read newer magisk script, your uninstaller (the link u gave) is the latest! so probably thats why twrp is giving error! , also twrp3.2.3 may not able to flash magisk20 also! it will give your zip file error/corrupt prompt!
YasuHamed said:
first of all bro, always mention what Rom you were on? if stock rom then which version/build of MIUI? if custom rom then which one (pixel exp, crdroid, havoc, lineage, carbon, nitrogen, etc etc)
now
twrp3.2.3-1 is way old for Poco, now Twrp3.3.1-x is out , you should try that one!
also if i remember correctly, Magisk18 is for OREO, so I am pretty sure your android version is 9.x
please flash latest recovery and magisk20.1
it will surely work!
a proper guide is already running in discussion forum with MAXX views count! please search
edit: older twrp cannot read newer magisk script, your uninstaller (the link u gave) is the latest! so probably thats why twrp is giving error! , also twrp3.2.3 may not able to flash magisk20 also! it will give your zip file error/corrupt prompt!
Click to expand...
Click to collapse
Ok so do i flash another twrp, and reinstall magisk then?
Kipce said:
Ok so do i flash another twrp, and reinstall magisk then?
Click to expand...
Click to collapse
flash latest twrp
in twrp then
flash same kernel again (if it was miui11 then extract kernel from zip file)/
flash magisk20.1zip
flash dfe (read more about it)
Hi all,
please find attached the Havoc OS 3.8 custom ROM, Olivelite version, and Magisk 20.4 which you will need for installation also.
I am neither the creator of this ROM or anyhow involved with the team, nor do I take any responsibility for everything which might go wrong during installation.
How I got it to work:
1. Unlock your boot loader (you will find appropriate instructions here in the forum and elsewhere on the web, also on YouTube).
2. Ensure that you have the XiaoMi Flash tool and the latest stock rom available, to be able to recover you phone when you encounter issues.
Both can be found on the Xiaomi website.
3. Get the "minimal ADB and Fastboot" tools. You will find in the web.
4. Get TWRP (you will find out what this is and why you need it here in the forum). Take care that it is a version for your phone model, else worst case it will not work.
5. Put the attached files to an external SD card in your phone.
6. install TWRP. Boot into "Fastboot" mode and install TWRP with command "fastboot flash recovery twrp.img".
7. Boot into recovery mode - if yoiu did everything right, should be TWRP now
7a. Wipe - Format data - confirm with "Yes", then go back to main menu
7b. Wipe - advanced wipe - select all except the last 2 (expecially NOT "external SD" if you put your files on there),
go back to main menu
7c. Install - select location where you've put the "havoc 3.8 update.zip" and select the file, afterwards wipe Cache / Dalvik (TWRP will give you this option after install), DO NOT REBOOT
7d. Install - select location where you've put the "magisk v20.4.zip" and select the file, afterwards wipe Cache / Dalvik and then reboot to system.
Now, hopefully, congratulations and enjoy
If something happens and it will not work at all, search the web first for solutions and, if still does not work and you do not get along with it, do not worry. You can always go back to the Xiaomi original ROM with the XiaoMi Flash Tool. Phone must be in "Fastboot" mode for this. In the flash tool, select your ROM location (ideally in the root of your drive as this tool cannot interpret spaces in paths), then confirm and ensure that you have ticked "Clean all" in the bottom, NOT "clean all and lock" - else you will have to do the unlock procedure again.
Sometimes, you need the "permissiver v5.zip" which you will find on the web. In case the above does not work, you can try to install the Permissiver. I never needed it, and I'm using 2 Redmi Olivelite.
I just tried this and had a success message from TWRP about the Havoc 3.8 flash but the Majisk file had an error from within TWRP first time & then it installed after reboot. But I still go straight into TWRP after rebooting.
Right now I have TWRP on the device & a micro SD card to get files onto the device but no OS on it & no backup as one way or another I want a ROOTed OS & it was the Chinese version when I got the phone so useless to me anyway.
What's the best approach from here to get this thing running again?
Thanks!!! Thanks!!! Thanks!!! after trying to get a GSI rom run on my daugthers olivelite i finally got a new rom working. I don't know why last guides didn'twork for me actually a recently requested a boot.img patch but i managed to patch it myself after dealing with python. Now will try to update it to 3.12 i suppouse it iwll have many improvements. But this worked right out of the box for me. Just followed each step and good to go.
For anyone interested. its de 2Gb/32Gb Global Version. with 12.0.3 latest MIUI updated applied trough fastboot. I used OFOX to test it and it worked fine by now.
If you have guide to update HAVOC please point me in the right direction.
Thanks again
I got off .Havoc precisely because it did not have voLTE support & BT HS 's didn't work. Has anyone had any luck on these 2
I absolutely thank you for this rom, I can now miraculously play Asphalt 9 on high settings at 30ish fps while on miui it struggled on lowest settings, the UI is flawless but I only have one problem I can't send nor receive SMS and the phone sometimes reboots randomly but that cannot make me go back to miui since it's too heavy for my phone.
IS THERE any fix for not being able to receive or send SMS
I have a black screen [FIxed by installing OrangeFox recovery]