Related
I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.
you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.
I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.
This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock
I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.
chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?
Hi and thanks for using your time to take a look at my post. I am trying to install cyanogenmod 12.1 on my TF300T.
I went to the Asus website and downloaded the unlock tool v8, installed on tablet, and ran it without any issues. Tablet reboots shows little "this device is unlocked" in top left corner. However when it boots up and I try to run an app like titanium backup pro or supersu app, the app say they cannot get root access....
Has anyone experienced this before?
Am I missing a step?
I have android ver. 4.2.1.
Any info is greatly appreciated.
Unlock unlocks the boot loader allowing you to load custom roms via additional boot loader as per rom instructions, it does not give root access. You will need to search to a process to root the tablet, I used Kingo root, some do not like using this......although I had no problems. Using custom roms and rooting is at your own risk!
So this is the process that ive Followed... I ran the unlock tool, everything completes without issue. Nexissue the command adb reboot bootload to get my tablet into correct mode. Once the tablet is ready I flash a recovery image (TeamWin TWRP) to the device and boot the recovery. From here, it seems that recovery does not permission to mount any of the drives/folders. I look at the log file and see errors sayin unable to find partitions and unable to mount folders/drives. Below is a link to an image of the errors.
I am not sure if this link will get posted correctly to this thread: https:// drive.google.com/file/d/0B-bmj1Mkq-xzMkQyMHVPU0poSjQ/view?usp=sharing
BTW, thanks for your quick reply.
FYI, for the link above, there is a space between the HTTPS:// and the word drive which start the web address. The forum would not allow me to post a link since I am new.
Sorry, I'm no expert. When I installed Kang TWRP for KatKiss Lollipop, I did lots of research before diving in. Carefully followed instructions and all went well. When you flashed TWRP did you then reboot into bootloader?
fastboot reboot-bootloader
I think you will have to give all the steps you took, then perhaps someone will come along with more guidance.
Just to add some clarity to my situation, in hopes that someone can help shine a light:
1) Installed and ran Unlock device app V8 on the Asus webiste. It claims this is compatible with android version 4.2, i have version 4.2.1. Unlock ran then needed to reboot device. Upon reboot I saw the message "This device is unlocked" in the top right of the screen.
2) Once device rebooted, I installed adb/fastboot on my pc and ran it using CMD.
3) Connect tablet to PC using usb cable.
4) Ran the command "adb reboot bootloader" to get the device into required mode.
5) Next I run the command "fastboot devices" to verify the PC can see the tablet.
6) Run the command "fastboot -i 0xb05 flash recovery Recovery.img" to flash over the Recovery image file I have. Flashing goes through without any errors.
7) Once flash completes, I press up volume button to go into recovery.
8) Recovery boots and I am at the screen with the various options to install, backup, restore, wipe, etc.... I have Team win recovery project v2.8.7.0
9) If i try to use the backup option, it shows my internal storage as (0MB). I look at the log file (https:// drive.google.com/file/d/0B-bmj1Mkq-xzMkQyMHVPU0poSjQ/view?usp=sharing) and see that it cant find or mount various drives. If you want to view link, copy url and remove the space between https:// and the word drive.
**** ALSO, if you have a better or proven method, please feel free to suggest.*****
imnotorginal said:
Hi and thanks for using your time to take a look at my post. I am trying to install cyanogenmod 12.1 on my TF300T.
I went to the Asus website and downloaded the unlock tool v8, installed on tablet, and ran it without any issues. Tablet reboots shows little "this device is unlocked" in top left corner. However when it boots up and I try to run an app like titanium backup pro or supersu app, the app say they cannot get root access....
Has anyone experienced this before?
Am I missing a step?
I have android ver. 4.2.1.
Any info is greatly appreciated.
Click to expand...
Click to collapse
This issue has been resolved. It looks like the version of TWRP I was using (2.8.7.0) was not getting access to the file systems to be able to make changes or install.
I downloaded version 2.8.7.2 and everyone went flawlessly after that.
Special thanks to bonzoe for telling me that he was using Kang TWRP which led me to google that and get a new version.
Hi,
as I did not find an English guide for rooting a BQ Aquaris M10 tablet and had some problems when trying to root my tablet, I want to post an guide how to root this tablet.
First of all:
- This guide is just from my experience and is not thoroughly tested. It's on your own if you risk bricking your device.
- If you get stuck in the process, in nearly all cases you can revert to stock with the MTK flash tool (can be found on mibqyyo.com) and the images provided by BQ on their website.
- I could not unlock the bootloader with the 1.X-Images (Lollipop), as the VolumeUp-Button didn't work in fastboot-mode and you need this button to confirm the unlock.
- Booting into recovery from start with VolumeUp and Power-Button. This doesn't work with the 1.X-images, too.
- This guide is not intended for users without experience in unlocking/rooting a device. If you don't know how to use adb, fastboot, recovery and things like that, don't try it!
- You will loose all your data during this process!!
Guide:
Modify boot.img, flash new firmware
SuperSU in systemless mode doesn't work on stock image, as the SuperSU installer can't extract boot.img. You have to repack boot.img.
I tried a SuperSU installer without systemless-mode, but device didn't even boot anymore afterwards.
This guide is derived from a Spanish tutorial on the HTCmania-forum ("Root M10 HD Marshmallow") by yquepongo. Thanks to him!
Get a firmware for your device from the BQ-website (should be Marshmallow, see above) and unzip it to a directory.
Extract the boot-verified.img in the firmware directory with a bootimg-extractor. There are various tools available.
I used bootimg.exe, because this was explained in the mentioned thread and I even used it with wine on Linux and it went well.
Search for cpiolist.txt in your extracted boot-verified.img and delete the first two lines:
mode:mtk
mtk_header_name:ROOTFS
Repack boot-verified.img and put it back in the firmware directory.
Flash the modified firmware with the MTK flash tool according to the tutorial on .mibqyyo.com (Title "Hard Reset for the smartphone range Aquaris and Aquaris E"). In short: Disconnect device, start Tool, load scatter file from firmware directory, choose firmware upgrade, start download, connect the device in power off state, download will start automatically.
This will delete all your data and put the device back to factory rom (hard reset)!!!
If you don't want to flash the complete firmware, you can flash only the boot-verified.img with "Download only" in the flash tool. I didn't try this and don't know if this is working.
Start your device, don't activate any security settings to prevent encryption of data partition.
Unlock bootloader, flash TWRP, install SuperSU
Enable developer settings on device and activate "OEM unlock" in developer settings.
Reboot into fastboot (adb reboot bootloader) and unlock bootloader (fastboot oem-unlock).
This will delete all your data!!! Reboot your system afterwards to make sure everything is still ok.
Do not activate any security settings and make sure your data partition is not encrypted!
The existing TWRP-image can't handle an encrypted data partition, you will end in a boot loop and have to start the whole process again!
Double check, your data partition isn't encrypted. (Settings - Security)
Reboot into fastboot (adb reboot bootloader) and flash the TWRP-image from the TWRP-site (fastboot flash recovery twrpxxx.img)
After reboot TWRP should start.
If you have checked that everything is ok (I would recommend a reboot into normal mode), you can install SuperSU with the standard-installer-zip in TWRP.
If you didn't modify your boot.img, the installer will give a warning that it cannot extract boot.img and you will not find any SuperSU on your system.
If you get stuck in bootloop afterwards you can start anew and try it with another image flashed with MTK flash tool. (Firmware 2.2.0 from December 2016 for freezerhd worked in my case)
Maybe some steps could be shortened, but I haven't tried it.
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: unlokied-new.img
Setting up work folders . . .
Splitting image to "/split_img/" . . .
Android boot magic not found.
Error!. . .
Click to expand...
Click to collapse
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
i opened a separate theme for this : https://forum.xda-developers.com/android/general/root-help-to-root-twrp-recovery-bq-t3536170
dreas74 said:
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
Click to expand...
Click to collapse
Sorry, but I can't help you there, as the M8 seems to be too different to the M10: I didn't have to unlock the boot.img, it was easy to unpack.
hi zrfl,
thanks for your reply. i contacted the developer osmOsis from the android image kitchen.
he will implement the bq specials in his tools.
more in the AIK thread: https://forum.xda-developers.com/showthread.php?t=2073775&page=108
this is the only way to root this device !!
thanks a lot ...
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
ZazOufUmI said:
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
Click to expand...
Click to collapse
Sorry, I have done this a long time ago and don't know what could be wrong:
You have the correct message, so unlock was successfull
You try to reboot in fastboot, so you flashed TWRP correctly in fastboot-mode
And I don't have the device at hand to try it myself. But I do have a few suggestions, what you could try:
Don't try to shorten procedure with unlock and flashing of TWRP at once. I'm not sure, but I think I had problems when I tried this. So do a normal reboot after unlock, before booting again into fastboot and flashing TWRP. (Now you have done this already )
I don't remember the proper boot command after flashing of TWRP. But
Code:
fastboot reboot-bootloader
doesn't make sense: You are already in bootloader.
Is there a boot-option in the bootloader where you could choose recovery?
Otherwise better power off and use the key-combination for booting into recovery: VolumeUp+Power.
I think, you have to repeat the procedure, as recovery seems to be overwritten: Boot into fastboot, flash TWRP, reboot into recovery. And avoid normal booting before first boot into TWRP!
Did you use the newest TWRP 3.1.0 from March 8th? I haven't tried this yet, so there could be the problem. You could try the previous one: 3.0.2 from last year.
Thanks, I succeed with the combo key (power + vol up) directly after the reboot process
Perfect it's working great now !
I did exactly what you wrote but SuperSU won't install because it cannot extract the ramdisk...
Hi @zrfl
Thanks for your posting!
I did as you suggested and successfully unlocked bootloader and installed TWRP 3.1.1. Your hint to modify the boot-verified was extremely helpful, as I wouldn't be able to unlock the bootloader otherwise.
However, I did not manage to install super su. And boy, I tried many different versions od regular/system/systemless supersu, each flashed according to the respective how-to.
I ended up either in a bootloop, or get stuck on the Android logo at boot.
Flashing goes well until this step:
"Decompressing ramdisk
--- Failure, aborting"
I checked ramdisk compression of boot with Carliv image Kitchen and it tells me that it already is set to "gz" and not another compression TWRP can't handle.
Please help me on how to flash SuperSu.
Thanks and best
Tom
There is something wrong: TWRP does not need a modified boot.img.
Maybe newer ROM-versions are different.
Solution for geting root on BQ M10 FHD on stock rom 2.6.2: Start with a fresh system and install magisk beta (not stable), reboot and root is granted!
tanks a lot to @scafroglia93!
Are there any Custom ROM's
For this Tablet like CM/LineageOS AOSP etc?
Googling reveals nothing and Considering all the kernel mods like hardcore and Ubuntu touch I find it hard to believe that nobody has built one of the later.
I've been searching for custom ROMs too. Apparently, there are none available at present. However, I'd highly appreciate lineage rom.
Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.
Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image
To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).
Hi all! Now we can root our Sunny 2 phones!
I'd make a TWRP port for this device (adb enabled) so we can just sideload the Magisk installer.
History:
After some time having a Wiko Sunny 2 phone, I'd search a lot and didn't find any method for rooting this little thing.
Then I had the idea to mod the stock recovery to allow test keys and then flash anything, tried to do that and didn't work.
Another idea came to my mind: port TWRP from another phone with same chipset. Started my search for a SPD7731c device with working TWRP and after some time found some guy who made a TWRP port for his "Selecline S6S4IN3G" device and as it had the same chipset it worked. Just gathered the recovery.img from the stock rom (thanks Wiko for giving it on they web page) and unpacked it with carliv image kitchen, replaced the stock ramdisk with TWRP's one and just modded some things inside it (default.prop and the init.rc files). As the vold.fstab is the same, didn't need to modify it.
After some testing, the only problem remaining is that the touch doesn't work well (it receives touch input all the time, even if not touched) but it's enough to get our Sunny2's rooted via ADB and magisk's zip.
REQUIREMENTS:
A PC (or another phone with OTG support, if you use a phone then you'll also need an adb binary compiled for ARM)
ADB, Fastboot and drivers: https://drive.google.com/open?id=1N38jqQqX87dEKsBIgDb_9MC-k43YUi85
TWRP image: https://drive.google.com/open?id=1DZhL6RckvzQyxGCq2Yy64Cqnpnnm1Ofp
Stock recovery image (in case something goes wrong you can revert to this): https://drive.google.com/open?id=1spaFc1sqqjFdwzt9cYDfSO_KVh1aYuh5
Magisk ZIP (can be latest or this zip): https://drive.google.com/open?id=1-OPU1JycSr8nVyAGfdkhdajn8Uap_0dl
ROOT PROCESS:
1. While on Android, go to Settings>About this device and toch 7 times Build number (this will enable Developer Options)
2. Now go back to Settings and then Developer options>Enable OEM unlock and USB debugging.
3. Connect the device to the PC and install the correct driver (for doing this just open Device Manager and force the install of Android Composite ADB Interface on your unrecognized device (should be called SUNNY2)).
4. Open a CMD/Terminal and type this:
Code:
adb reboot-bootloader
5. Now type
Code:
fastboot flash recovery path/to/twrp-suny2.img
and after that just
Code:
fastboot reboot
.
6. Now the phone will start, just type in CMD/Terminal
Code:
adb reboot recovery
and you will boot into TWRP.
7. Okay, this TWRP has a buggy touch so just use ADB to install the magisk zip:
Code:
adb shell twrp sideload
, then
Code:
adb sideload path/to/magisk.zip
and finally
Code:
adb reboot
.
8. Nice, now Magisk should be installed. Now with root access, happy modding!
Some things to note:
1) In this guide I did everything via ADB, never booted to recovery or fastboot using button combinations. Why? Simple, on my device I didn't find the correct combinations.
2) You can use TWRP also for factory resetting or installing anything, but via ADB only (as the touch doesn't work properly).
3) If you need any help with this device just PM me!
I hope this guide will be useful for anyone.
CREDITS:
This guy for his work on porting TWRP to his device
Magisk team for his work on making root as simple as flashing a ZIP!
AndroidMTK website for hosting the ADB installer which
I just mirrored!
Stuck in boot loop
Hi ! Thanks for the HowTo !
But...
I followed the exact same procedure (except I had to fastboot oem unlock before flashing the twrp image, in addition to unlocking it in dev mode).
After flashing, the device was stuck in a boot loop : "orange state your device has been unlocked and can't be trusted / your device will boot in 5 seconds". Tried all manners of key combos to reboot in recovery (Vol Up + power is supposed to be the right combo) but to no avail.
Fortunately Wiko provides an "upgrade" tool that allows you to factory reset the device (support dot wikomobile dot com /maj/Sunny2Plus_V24.zip, window$ only) but no luck installing twrp.
Any idea why ? Thanks in advance
tofleplof said:
Hi ! Thanks for the HowTo !
But...
I followed the exact same procedure (except I had to fastboot oem unlock before flashing the twrp image, in addition to unlocking it in dev mode).
After flashing, the device was stuck in a boot loop : "orange state your device has been unlocked and can't be trusted / your device will boot in 5 seconds". Tried all manners of key combos to reboot in recovery (Vol Up + power is supposed to be the right combo) but to no avail.
Fortunately Wiko provides an "upgrade" tool that allows you to factory reset the device (support dot wikomobile dot com /maj/Sunny2Plus_V24.zip, window$ only) but no luck installing twrp.
Any idea why ? Thanks in advance
Click to expand...
Click to collapse
Hmm this device is pretty strange, his key combinations never worked for me (because of that I'd need to reboot into system a few times, instead of booting to fastboot with keys).
You can try this:
After flashing stock rom and allowing oem unlock on settings, reboot directly to fastboot. Then use "fastboot boot recovery.img" and tell me what it says. If it says something about bad boot image, it's normal (that happens in my device even if try to load stock boot.img).
Also there's a tool called SPD Research Download Tool, which let's you flash the phone partitions one by one (manually selectable) from the path you want, while phone is in download mode (volume down and connect USB to PC). However, I don't know if that tool's license allows it's free redistribution, so I recommend research for it before downloading anything.
You can get the stock files by running the wiko upgrade tool, going to the folder it extracted his files and then looking for a file called rom.pac (then unpack it, there are guides here on XDA for doing so). You can even edit the boot splash image lol
Sorry for wasting your time
I'm so stupid ! It turns out my device is a different model, the Sunny 2 Plus.
Sorry, and thanks again
Does anyone know if a custom rom exists for the Wiko Sunny 2?
Klab98 said:
Does anyone know if a custom rom exists for the Wiko Sunny 2?
Click to expand...
Click to collapse
Nope, sold the device some days after writing this post so didn't even bother to port anything.
BTW it's a 4-core phone with 512MB RAM, so what would you expect to run there? I thing nothing higher than MM (KK would be nice if it was not so outdated nowadays)
Hi, i have got a problem with my wiko sunny 2 plus.
i flashed twrp via fastboot, it succeed. but after reboot the phone didnt start,
only shows orange state, didn´t connect to pc anymore with same cable. i mean i can hear the win7 sound of connecting device and right after connect sound appear then disconnect sound follows right after. so i cant detect the device with adb anymore. what to do, any idea? P.S. sp flashtool also cant detect device. greets
merci beaucoup j espere sa marche