Q&A for [ROM]SLIMPOP [wiko rainbow][micromax a120 c2c]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]SLIMPOP [wiko rainbow][micromax a120 c2c]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Link
And where is the link to download ROM?
my phone is not working pls help me
2 days before when i rebooted my phone it showed me as encryption unsuccesful and stucked at boot logo.but i tried to wipe data...bt it showed me error mount/data error...so i tried to flash using sp flash tools....instead of selecting firmware upgrade and tried format and download....format done but on download it showed me error 5069....pls help me..to solve this ASAP...
I repartioned my device does it causes any defects??
i dont know anything where i have to post this....pls help
Issues with GPS
Hello smokerman,
First thank you for this incredible rom, it's very fast and slick !
I have a brand new wiko rainbow and i tried to flash numerous times your rom (slimpop v2) i noticed no issues except with the GPS and location services in general, i activated the GPS + 3G+wifi network positioning, and nothing seems to work i can't get a position, i tried to use numerous gps fix app, and even your own GPS fixer for the wiko rainbow published on your website in april, and still no luck.
I flashed the wiko in stock kitkat 4.4.2, installed TWRP recovery after rooting it, then used the recovery to flash the slimpop v2 zip + the rootfile do the wiping and all the shebang following your instructions to the letter, but everytime (i tried 5 times) the location service just don't work, i tried all the engineering tools available in the dev section of the phone to try and pinpoint the issue but no luck.
Of course i tested if the GPS and location services were working fine with the stock wiko 4.4.2 rom (gps tools, dev tools, waze) it all work fine !
Do you have any ideas what i could have done wrong ? Im open to do some testings, or report any kind of logs you would need to track that issues.
Thanks,
Cya
EDIT1 : strangely enough after a few tests with differents roms, it seems that all the roms i tried that use the WR kernel have issues with the GPS (even with your fix) the ones that doesn't use it have no problems working. I was thinking maybe that brand new rainbow has a different GPS chip ? i got no clues as to why it's not working
I am using MyPhone Rio, and Wiko v13 as base, followed the instructions on flashing, yet stuck on first boot logo after flash. Hmnn, don't know what to do
ktsarlz said:
I am using MyPhone Rio, and Wiko v13 as base, followed the instructions on flashing, yet stuck on first boot logo after flash. Hmnn, don't know what to do
Click to expand...
Click to collapse
I had this problem when i wasn't using the base V13 from scratch (as in reflashed into the phone) then rooted with kingroot then installed the philz recovery that smokerman supplied, then boot in recovery > wipe for installing new rom (it's an option) > then flash the slimpop v2. before doing that i was stuck all the time in bootloop like you. Maybe try this ?
d4rk80z said:
I had this problem when i wasn't using the base V13 from scratch (as in reflashed into the phone) then rooted with kingroot then installed the philz recovery that smokerman supplied, then boot in recovery > wipe for installing new rom (it's an option) > then flash the slimpop v2. before doing that i was stuck all the time in bootloop like you. Maybe try this ?
Click to expand...
Click to collapse
Hmn, before flashing this, I did flash Wiko v13 thru spft, tried wipe to install new rom as I am using Philz, also tried wipe cache dalvik factory reset, same result. I also tried flashing slim v2 as Wiko v10 still stuck on boot logo. I can use 1.1 and 1.2 perfectly before. I am not sure what I am doing wrong
ktsarlz said:
I am using MyPhone Rio, and Wiko v13 as base, followed the instructions on flashing, yet stuck on first boot logo after flash. Hmnn, don't know what to do
Click to expand...
Click to collapse
ktsarlz said:
Hmn, before flashing this, I did flash Wiko v13 thru spft, tried wipe to install new rom as I am using Philz, also tried wipe cache dalvik factory reset, same result. I also tried flashing slim v2 as Wiko v10 still stuck on boot logo. I can use 1.1 and 1.2 perfectly before. I am not sure what I am doing wrong
Click to expand...
Click to collapse
Have you tried for the initial stock flash to use the wiko official tool V13 KK ? maybe there is something wrong going on with your spft, otherwise no clues ^^
I saw that smokerman posted in the original thread that it should be flashed over a V10 stock, and not a V13, sadly he doesn't seems to look at that Q&A thread and i don't have enough post to ask directly in the original thread...
Anyway since we replace everything kernel + rom, what technical reason is there to have a basic V10 instead of anything (like a V13), since we seems to replace everything anyway. Im curious.
EDIT1 : well still no luck starting with a V10 stock rom then flash the slimpop v2 following the procedure, the gps still giving me no fix at all... ah well too bad, it was looking like an incredible rom, i will use the stock until i find something else to use.
Keep up the good work.
Cheers
d4rk80z said:
I saw that smokerman posted in the original thread that it should be flashed over a V10 stock, and not a V13, sadly he doesn't seems to look at that Q&A thread and i don't have enough post to ask directly in the original thread...
Anyway since we replace everything kernel + rom, what technical reason is there to have a basic V10 instead of anything (like a V13), since we seems to replace everything anyway. Im curious.
EDIT1 : well still no luck starting with a V10 stock rom then flash the slimpop v2 following the procedure, the gps still giving me no fix at all... ah well too bad, it was looking like an incredible rom, i will use the stock until i find something else to use.
Keep up the good work.
Cheers
Click to expand...
Click to collapse
For me, with v10 as base still does not boot Haha
Slimpop is based on KitKat, I suppose??
Related
hi there!
i recently looked for some roms for my 9515 phone
unfourtunantly, i read here: http://forum.xda-developers.com/galaxy-s4/general/galaxy-s4-value-edition-gt-i9515-t3190176
that there are no roms for this device..
so i found another thread- http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-s4-value-edition-i9515-t3031044
which told me to download kernels, modems and other things in order 9505 roms to work.
tried it- but with no sucess.
BTW i tried to use this rom: http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
any help will be appriciated- THANX SO MUCH
ps- sorry for my english..
psII- i know that this is the forum for the 9500 and 9505 only, but i couldnt find any forum for the 9515.
psIII- i can use the phone only through PC- im using MyPhoneExplorer to mirror and control my phone.
Are you flashing a kernel right after flashing the ROM?
audit13 said:
Are you flashing a kernel right after flashing the ROM?
Click to expand...
Click to collapse
yes..
is that a prob?
edit: if i will flash stock, than kernel, and then rom- will it work?
Make sure the phone is running the latest bootloader and modem. Once that has been confirmed, perform a complete system wipe (system, cache, data) before flashing ROM, flash the ROM, and flash the kernel. Don't boot the phone out of recovery until after flashing the kernel.
audit13 said:
Make sure the phone is running the latest bootloader and modem. Once that has been confirmed, perform a complete system wipe (system, cache, data) before flashing ROM, flash the ROM, and flash the kernel. Don't boot the phone out of recovery until after flashing the kernel.
Click to expand...
Click to collapse
thanks so muchhhhh u saved my asss
how do i check my bootloader & modem version?
I suggest flashing a stock ROM from here: http://www.sammobile.com/firmwares/database/GT-I9515/
Once that is done, you can flash TWRP from here: http://forum.xda-developers.com/galaxy-s4/general/galaxy-s4-value-edition-gt-i9515-t3190176
With TWRP, you can create a nandroid backup. If you flash a ROM that doesn't work properly, boot into TWRP and restore your nandroid backup and start over.
Sometimes, you may fine a ROM that will work without further modification. If not, a custom kernel may be required.
What are you talking about? The first link you posted linked to various rom threads for the I9515.
There is unofficial CM13 for the I9515, also known as jflteve.
There also was an unofficial SlimLP..
Unofficial CM13
Unofficial CM12.1
Unofficial SlimLP
As you can see, there are some roms. No need to mess around with patchers. Unless you really want touchwhiz..
GDReaper said:
What are you talking about? The first link you posted linked to various rom threads for the I9515.
There is unofficial CM13 for the I9515, also known as jflteve.
There also was an unofficial SlimLP..
Unofficial CM13
Unofficial CM12.1
Unofficial SlimLP
As you can see, there are some roms. No need to mess around with patchers. Unless you really want touchwhiz..
Click to expand...
Click to collapse
want TW. SO BADLY
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Devc100 said:
first you have to upgrade it to marshmallow using stock rom. Then you can flash cm13 or cm14.1
Click to expand...
Click to collapse
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Ph4nToM_Z3rO said:
Hi guys, its been a few days since I joined here. [Read : I am a noob/newbie in Android related things, and I desperately need help.]
In July (maybe, I forgot), I rooted my ZE550KL, using exactly this method from the website of www-asus-zenfone-com. :cyclops:
Now that, my android seems aged, I wanna shift/upgrade to Marshmallow/Nougat, be it Stock or Custom ROM.
Few days earlier, I unlocked my Bootloader using the Unofficial Bootloader Unlocking Method, as found on this Forum.
I also installed TWRP Recovery, and I tried to flash CM-14.1 [7.1] Nougat-Nightly through TWRP, but, unfortunately, resulted in Status 7 Error. I tried to solve the problem by removing "asserts" section in Update-Binary text file, in the build. But, again, I seemingly worsened the problem; as I got Status 6 error thereby. So, I did factory reset, and I still retain root.
Now, today as I am going through the Official thread of CM 14.1 Nougat, I saw numerous users reporting Bugs of connection issues (something like Wifi to Mobile Data switch problem), which I would like to OBVIOUSLY AVOID, as I want a stable, bug-less build. So, I am thinking to go with the last snapshot build of CM 13.0 Marshmallow.
Here comes the my question : " SHOULD I FLASH CM 13.0 MM -- OR -- STOCK ROM OF MM -- OR -- RESURRECTION REMIX MM ROM?? "
In any of the case, please guide me through the process of doing so.
And, if I have to flash CM 13.0 MM, what would I do if I encounter Status Error 7 again ? :crying:
Click to expand...
Click to collapse
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
aadi50 said:
While flashing CM13 if that error 7 includes "asus.verify trustzone failed..." Then its bcoz of need to update modem files (LP to MM)....
Easy way to overcome it is..... download MM modem ZIP from second post of OFFICIAL CM13 thread (120MB) and flash it using TWRP (If you are using twrp).... THEN you can flash cm13 hopefully without error 7....
If you are using stock recovery then Either u can flash twrp and use above method... OR... Download ASUS ZE550KL firmware zip file from ASUS site (1.6GB) .... Put it in SDCARD... Then boot to stock recovery and use "apply update from sdcard" option... select ZIP... Alongwith firmware Ur Modem files will also update to MM... and now u can flash twrp and then cm13...
sorry.. I know if i am lazy to post direct links...
Try it.. I will help if i can
Click to expand...
Click to collapse
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Ph4nToM_Z3rO said:
Thanks, dude. One question, should I get CM 13.0 or Resurrection Remix ?
Click to expand...
Click to collapse
We have both stable RR and CM13.
CM is simple and clean and less loaded.... RR is most feature rich Custom rom we have alongwith stability...
Rest depends on what type of user, u are... If u like trying differnt ROMs... Start with CM13...
If u just want to have a feature rich longtime setup, U can use RR directly without wasting time... It is based on CM, So it obviously have everything CM has.... :good:
Ph4nToM_Z3rO said:
Please, like I said, guide me through how to do it. Thanks in advance, in case you help. :good:
Click to expand...
Click to collapse
Latest Stock Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-21.40.1220.1877-user.zip
Stock RecoveryRestore it using TWRP)
https://drive.google.com/open?id=0B2BGto29cXq1NjYySjRES21yOTg
Last Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.17.40.1531-user.zip
First Lollipop Software:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550KL/UL-Z00L-WW-1.11.40.299-user.zip
First Do A nandroid backup of your phone. So that if any thing goes wrong, U can recover it.
Then Download both the Stock MM and Recovery file named TWRP.zip.
Extract TWRP.zip.
Then take both the MM software and Xtracted TWRP folder in a memory card.
Then Open TWRP recovery in ur phone and restore the stock recovery.
Then Erase Every Thing including System.
Then Restart The recovery. Now you will see that the recovery has gone back to the stock recovery.
Now flash the stock marshmallow from your memory card.
Then flash TWRP from fastboot and thn u can flash any supported custom Android MM or Android N.
N.B. If it dosent work. Then you have to first install the last lollipop Zenfone 2 Laser(Z00LD) software then install the marshmallow.
Hi there,
just to give a feedback. DUALSIM is not working on both builds. LTE function fails. Made complete new flash, nothing helps...
Same applies to crDroid - build 20170802 - 7.1.2
I would kindly ask for help around here
Thanks,
Light of Magic
after one day....
Hi,
I don´t know why dualsim function stopped working... I tried 2 builds each - Lineageos, Ressurection OS, crDroid ... going back to stock ROM, everthing works fine. I even searched through the net to get a suitable pit file.
Only thing - I wanted to update like https://forum.xda-developers.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283
And I could not find TWRP 3.0.0 as recommended, so I use 3.1.0 - I could not install SkiesROM, since it was maybe to large....
For any help I would be greatful,
Light of Magic
LightofMagic said:
Hi,
I don´t know why dualsim function stopped working... I tried 2 builds each - Lineageos, Ressurection OS, crDroid ... going back to stock ROM, everthing works fine. I even searched through the net to get a suitable pit file.
Only thing - I wanted to update like https://forum.xda-developers.com/galaxy-s5/development/rom-lineage-os-samsung-galaxy-s5-lte-t3534283
And I could not find TWRP 3.0.0 as recommended, so I use 3.1.0 - I could not install SkiesROM, since it was maybe to large....
For any help I would be greatful,
Light of Magic
Click to expand...
Click to collapse
Here u get TWRP 3.0.0.0 for klte as recommended. Extract the zip before use. Use the .tar for Odin flash or the .img for flash through recovery. Tip: download twrp-app from Playstore. You'll find all downloadable content there.
I've read that going back from LOS / AOSP to SkiesROM is not possible without flashing a Stock Rom first. Make sure u have flashed the fitting bootloaders via Odin before u flash the Stock ROM. Suitable are the ROMS from ALEXNDR. They're prerooted and a good base to go further.
Good luck
still
I wounder, does anyone have the same issue? Using the builds in May I did not have this issue.
Thanks to ottili81 for TWRP 3.0.0.0 !!!
Greetings,
Light of Magic
Hi all
Thanks for a great Forum!!
I have a minor issue
Specs: LG G2 D802 32GB - Love that phone! :good:
I have been running it stock for the last 4 years but recently many of my favorite apps does not support kitkat no more, so time to upgrade i thought
I read several post in here and watched a bunch of videos on youtube and gave it a try.
So... First, rooted my phone with IOroot - OK
Installed Autorec and TWRP 2.7.0.0 - OK
upgraded TWRP to 3.2.1.0 - OK
Downloaded Lineage 14.1 D802 and Gapps 7.1 mini - OK
Booted to TWRP and Wiped Dalvik, System, Data and Cache - OK
installed Lineage 14.1 - OK
Wiped Dalvik - OK
Installed Gapps - OK
Wiped Dalvik - OK
Rebooted to System - Not OK :crying:
As far as I can read in here, The problem lies in the boot loader, but herein lies my question. Autorec according to one post in here, downgrades the bootloader to JB but the FAQ Q12, in this thread tells me that Autorec keeps/installs the KK bootloader...
And according to Lineage OS, I need the KK bootloader to run. And alot of posts/threads recommends NOT to use hybrid bootloaders etc...
So, what did I do wrong??? Do I still have the KK bootloader or do I have the JB Bootloader?? If I have the JB and would like to upgrade to KK - how would I go about it in my current situation where Im stuck at LG logo. Or do I have an entirely different problem?
Btw, TWRP works fine and I have all the backups - But Im not interested in reverting back to stock because then Im back with the unsupported phone/apps issue...
Best regards
Dutchmhk
dutchmhk said:
Hi all
Thanks for a great Forum!!
I have a minor issue
Specs: LG G2 D802 32GB - Love that phone! :good:
I have been running it stock for the last 4 years but recently many of my favorite apps does not support kitkat no more, so time to upgrade i thought
I read several post in here and watched a bunch of videos on youtube and gave it a try.
So... First, rooted my phone with IOroot - OK
Installed Autorec and TWRP 2.7.0.0 - OK
upgraded TWRP to 3.2.1.0 - OK
Downloaded Lineage 14.1 D802 and Gapps 7.1 mini - OK
Booted to TWRP and Wiped Dalvik, System, Data and Cache - OK
installed Lineage 14.1 - OK
Wiped Dalvik - OK
Installed Gapps - OK
Wiped Dalvik - OK
Rebooted to System - Not OK :crying:
As far as I can read in here, The problem lies in the boot loader, but herein lies my question. Autorec according to one post in here, downgrades the bootloader to JB but the FAQ Q12, in this thread tells me that Autorec keeps/installs the KK bootloader...
And according to Lineage OS, I need the KK bootloader to run. And alot of posts/threads recommends NOT to use hybrid bootloaders etc...
So, what did I do wrong??? Do I still have the KK bootloader or do I have the JB Bootloader?? If I have the JB and would like to upgrade to KK - how would I go about it in my current situation where Im stuck at LG logo. Or do I have an entirely different problem?
Btw, TWRP works fine and I have all the backups - But Im not interested in reverting back to stock because then Im back with the unsupported phone/apps issue...
Best regards
Dutchmhk
Click to expand...
Click to collapse
I know we've already spoken on another post about this but I'll reply here for thoroughness incase somebody else runs into the same problem. All the above was correct except you missed the bootloader.
flash Daniel Stuarts CAF bootstack. Available here------> https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802
Then flash the Rom.
Then flash Gapps
Then reboot and enjoy.
As a sidenote, it's worth reading the notes on installing. Lineage is a continuation of Cyanogen and as such they are compatible. However, you can't go from cyanogen 13 to lineage 14. To get to lineage 14 you will need either cyanogen 14 or lineage 13. Details can be read here---->https://www.lineageosroms.org/forums/topic/update-lineage-os-13-14-1-on-cyanogenmod-13-14-1-rom/
blueplasticsoulman said:
I know we've already spoken on another post about this but I'll reply here for thoroughness incase somebody else runs into the same problem. All the above was correct except you missed the bootloader.
flash Daniel Stuarts CAF bootstack. Available here------> https://github.com/danielstuart14/hybrid_caf_bootstacks/tree/LG-CAF/d802
Then flash the Rom.
Then flash Gapps
Then reboot and enjoy.
As a sidenote, it's worth reading the notes on installing. Lineage is a continuation of Cyanogen and as such they are compatible. However, you can't go from cyanogen 13 to lineage 14. To get to lineage 14 you will need either cyanogen 14 or lineage 13. Details can be read here---->https://www.lineageosroms.org/forums/topic/update-lineage-os-13-14-1-on-cyanogenmod-13-14-1-rom/
Click to expand...
Click to collapse
Thanks buddy :good:
Gave it a go yesterday and it worked like a charm !!
only thing that bothers me a bit is the knock on knock off code....it´s not like it used to be, but i´ll do some more reading on that subject - and who knows maybe someone found/made a solution for that as well
Btw, Antutu bech = 60871
Dutchmhk
Hello !
Has anyone actually managed to get any custom ROM to work on a Samsung Galaxy A40 SM-A405FN/DS ?
Mine is currently running the current latest stock ROM (SM-A405FN_2_20211030045838_jg43vcqbiw_fac) downloaded with Frija and I managed to install TWRP from here : https://forum.xda-developers.com/t/recovery-a40-teamwinrecoveryproject-3-6-x-unofficial.4364575/
However, ANY custom ROM that I try to install :
https://forum.xda-developers.com/t/a11-r-arm64-a40-lineageos-18-1-unofficial-by-kevios12.4335409/
https://sourceforge.net/projects/eurekaroms/files/Samsung/A40/R/lineage/
GSI
maybe others that I forgot
will either bootloop or end up with a black screen.
Looking at the following threads, I'm starting to wonder if the SM-A405FN/DS is custom-ROM-compatible at all ?
https://forum.xda-developers.com/t/help-my-a405fn-wont-boot-any-custom-rom.4337041/
https://forum.xda-developers.com/t/samsung-a40-black-screen.4354421/
https://forum.xda-developers.com/t/galaxy-a40-infinite-loop-impossible-to-turn-on.4337343/
Im running CrDroid 7.13 without any issues with root and gapps. Many custom roms bootloop because of your newer firmware with Bit/SW REV.
Security Patch Lvl. being 4 and those custom rom were built on the older firmware with probably patch level 3. I had installed DotOS fan edition fully working like a year ago, then I tried some new custom roms, which somehow broke my system so the system couldnt start up even after reflashing original boot image, so I reflashed to the newest firmware which was working, then I tried flashing older one and it wouldnt boot, it just shows black screen with error bit/sw 3 boot 4. So you have to flah roms, whose are built on the newer bit level to boot up, the best is CrDroid and now the newest ALT-F4 version 0.0.3 from this forum: https://forum.xda-developers.com/t/rom-oneui-3-1-a40-alt-f4-v0-0-1-updated-2021-12-18.4373813/
I tried it myself and it is the best for this phone, it is fully debloated and pre-rooted stock rom. I also tried CrDroid 8x, everything works for me, but it fells slow and the ram is almost maxed out. I also recommend upgrading to this TWRP: https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
The unofficial twrps had some bugs for me. I hope this helps and happy flashing!
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
breversa said:
THANK YOU for your comprehensive reply !! I'll give ALT-F4 a try as soon as I can !
Click to expand...
Click to collapse
Good luck!
Well, luck has not been enough: after updating TWRP to the official version, I tried yesterday to install ALT-F4 0.0.3 but got the exact same result: black screen, need to reflash the stock ROM to make it boot (even to recovery !!) again.
Would you have any other idea ?
EDIT:
I actually tried crDroid in the past, to no avail either.