[OFFICIAL ][RECOVERY] [20-08-2017] TWRP 3.2.3-0 - TeamWin Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
What's new in 3.2.1-0:
* minui fixes (cryptomilk) * Better android-8.0 compatibility in ROM trees (Dees_Troy) * Fix missing library in android-8.0 (nkk71) * Fix inconsistent SDCard naming (DevUt) * Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
INSTALLATION:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version above
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
To install from SP Flash Tools:
1) Download scatter file attached to this post
2) Load scatter file into SPFT
3) Plug USB cable into device and computer
4) Press download in SPFT
5) Reboot device
To install from offical TWRP App (Requires a rooted device.)
1) Download Official TWRP App from playstore
2) Choose the device (elephone P9000 -- p9000)
3) Install it
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
Other Projects:
Make sure to also check my dualbooting guide here: https://forum.xda-developers.com/elephone-p9000/how-to/guide-dualboot-patcher-t3608213
Thanks to:
(me) Ruben Craveiro
bigbiff
Dees_Troy
Leskal
Deepflex
Tribual
XDA:DevDB Information
[OFFICIAL][LATEST][RECOVERY] TWRP 3.2.1 for Elephone P9000, Tool/Utility for the Elephone P9000
Contributors
Ruben Craveiro
Version Information
Status: Stable
Current Stable Version: 3.2.1
Stable Release Date: 2017-08-10
Device Tree
[url]https://github.com/Ruben7173/android_device_elephone_p9000[/URL]
Created 2017-08-20
Last Updated 2018-06-03
Great work, however, I can't find it in twrp app from playstore. Will this be updated soon?
What's the difference between an installation from twrp-App and flashtools?
TheMRK said:
Great work, however, I can't find it in twrp app from playstore. Will this be updated soon?
What's the difference between an installation from twrp-App and flashtools?
Click to expand...
Click to collapse
currently due to an error i made while uploading our device info i set the file to go over to twrp main page, i have already sent out a fix but needs review once its approved, it should be up and running to work with the app
Ruben Craveiro said:
currently due to an error i made while uploading our device info i set the file to go over to twrp main page, i have already sent out a fix but needs review once its approved, it should be up and running to work with the app
Click to expand...
Click to collapse
That's good news.
But again, what's the difference between an installation of twrp from its app and via flashtools. Is it in the end the same? Or do you recommend one of both methods?
TheMRK said:
That's good news.
But again, what's the difference between an installation of twrp from its app and via flashtools. Is it in the end the same? Or do you recommend one of both methods?
Click to expand...
Click to collapse
If you already have root, i recommend the app, since its an easier to way to download, install/update the recovery, but if you dont have root you need at least once to install it from flash tools, since the app is not an option yet for the moment(its not on devices list, but you can manually install it), you can download the image and flash it through the app (if you have root, that is) if you dont have roog you need to use flash tools
I have P9000 with Nougat on it, version Elephone_P9000_20170418 and I'm trying to install TWRP 3.0.2 with SPFlash Tool, I only check recovery and flash it, but when I start the phone in recovery mod displays only show "no command". Is there any scatter file for this version, and what should I do to flash it through SPFlash Tool?
tonivet said:
I have P9000 with Nougat on it, version Elephone_P9000_20170418 and I'm trying to install TWRP 3.0.2 with SPFlash Tool, I only check recovery and flash it, but when I start the phone in recovery mod displays only show "no command". Is there any scatter file for this version, and what should I do to flash it through SPFlash Tool?
Click to expand...
Click to collapse
Any scatter file from one of our stock roms should do the trick, just put it alongside the downloaded twrp image, and flash it, also twrp 3.0.2 is not official, unlike this one, this one will be able to be updated directly through the twrp app once the issue is fixed.
Ruben Craveiro said:
(...) this one will be able to be updated directly through the twrp app once the issue is fixed.
Click to expand...
Click to collapse
Without root then or is it always required for this app?
TheMRK said:
Without root then or is it always required for this app?
Click to expand...
Click to collapse
the app will always require root, but you can always use magisk with the certification bug fix and magisk hide so that you can have the device certified and still be rooted. (if you dont know what certification is used for, its to allways allow the usage of android pay)
Thanks for your work
The onely thing that doesn't work for me is OTG.
Stylogey said:
Thanks for your work
The onely thing that doesn't work for me is OTG.
Click to expand...
Click to collapse
Thanks for the log but next time use pastebin so you dont make a huge post (and i have copied the log and later on ill see it, so you can edit and delete the log from post so it doesnt fill the thread, thanks)
Good day!
My apologies as I am new to this, but I can't seem to find the link to the scatter file that you mention. Could you help me, please?
Thanks in advance, and sorry for the trouble.
CrimsonWind said:
Good day!
My apologies as I am new to this, but I can't seem to find the link to the scatter file that you mention. Could you help me, please?
Thanks in advance, and sorry for the trouble.
Click to expand...
Click to collapse
its available in any stock rom that is flashable with sp flash tools
You can try to compare your sources with those of Jonny. The TWRP versions which he build worked for me.
Edit: I tried to fix it by myself and after I used another kernel (Darksense kernel) as prebuild kernel it worked.
TheMRK said:
Great work, however, I can't find it in twrp app from playstore. Will this be updated soon?
What's the difference between an installation from twrp-App and flashtools?
Click to expand...
Click to collapse
Its updated, now its available on twrp app
Ruben Craveiro said:
Its updated, now its available on twrp app
Click to expand...
Click to collapse
That's great. I've just checked with my device and can verify it works well. Thanks for your efforts.
Ruben Craveiro said:
Its updated, now its available on twrp app
Click to expand...
Click to collapse
Works just perfectly. Good job with the app part, I had the app for a long time and our Elephone never apeared, now it is just perfect. Thanks
"Download scatter file attached to this post"
Where can I download the scatter file? There is no attachment.
Thank you!
mano2 said:
"Download scatter file attached to this post"
Where can I download the scatter file? There is no attachment.
Thank you!
Click to expand...
Click to collapse
sorry, didnt add it yet, and im away from a computer, just get the scatter file from any stock rom
Ruben Craveiro said:
sorry, didnt add it yet, and im away from a computer, just get the scatter file from any stock rom
Click to expand...
Click to collapse
I didn't quite understand what are scatter files for, now I did some research and downloaded the most up-to-date stock ROM and now everything is fine!
Thank you for your help!
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.76 BETA or newer.
Current rooted FW version: 14.2.A.0.290 .
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.80 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.1.136:
Files:
For C6902: Download C6902_14.2.A.1.136.flashable.zip (Bittorrent: 926MB) and C6902_14.2.A.1.136_Stripped.ftf (21MB)
For C6903: Download C6903_14.2.A.1.136.flashable.zip (Bittorrent: 806MB) and C6903_14.2.A.1.136_Stripped.ftf (21MB)
For C6906: Download C6906_14.2.A.1.136.flashable.zip (Bittorrent: 872MB) and C6906_14.2.A.1.136_Stripped.ftf (21MB)
For C6943: Download C6943_14.2.A.1.136.flashable.zip (Bittorrent: 889MB) and C6943_14.2.A.1.136_Stripped.ftf (21MB)
Save them somewhere you remember;
Put 'C69XX_14.2.A.1.136.flashable.zip' on (the external) SDcard1;
Put 'C69XX_14.2.A.1.136_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Flash 'C69XX_14.2.A.1.136.flashable.zip' in TWRP;
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C69XX_14.2.A.1.136_Stripped.ftf' using flashtool;
Reboot to system.
The first boot will be slow and after some time at the boot animation you will see Android start optimizing the apps on your phone.
Enjoy! :laugh:
Unlocked bootloader?
To be able to use this ROM without any special tweaking, download C6903_14.2.A.1.136_kernel.img and
Code:
fastboot flash boot C6903_14.2.A.1.136_kernel.img
Or use flashtool to flash it.
It is a kernel repack, with only one change. To confirm you are running this kernel, check if the file '/nuts_repack' exists.
DE-ODEX your ROM!
Make sure you have the flashable ROM installed before you do this.
Download C6903_14.2.A.1.136_deodex.zip (Bittorrent: 412MB), save it somewhere you remember;
Put 'C6903_14.2.A.1.136_deodex.zip' on (the external) SDcard1;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6903_14.2.A.1.136_deodex.zip' in recovery, do not reboot but go back to the main menu;
Clear dalvik-cache ONLY;
Reboot to system.
The first boot after flashing this you will see Android optimizing the apps on your phone, this might take a while... but should be just fine
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery;
Update to 14.2.A.0.290;
Then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][C69XX][4.3] Update to 14.2.A.1.136 [Root & XZDR][LB/UB][DE-/ODEX], a ROM for the Sony Xperia Z1
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290
Based On: STOCK
Version Information
Status: Stable
Stable Release Date: 2014-01-31
Created 2014-01-29
Last Updated 2014-02-01
FAQ & Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this guide ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6903_14.1.G.1.534_[NUT].ftf (Bittorrent: 770MB) and flash it using FlashTool. I've also added the FTF to the downloads page on this DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .534 without loss of your IMEI :good:
Thanks to @mharckk and @MohammadAG for the workaround which contributed to the creation of this FTF.
ROM STATUS: STABLE
At this moment, running out of time to sleep before work tomorrow, I have to put this online still with a SEMI-ROOT
Fortunately recovery is working well, so I will be able to release a simple patch once I crack this one :good:
No patch required, it was my sleep deprived stupidity which resulted in a stupid mistake!
Hahaaaa nice work mon ami ^_^
Sent from my GT-I9505 using XDA Premium 4 mobile app
I'm not much of a developer, but there is one thing im good at seeding! :good:
@[NUT] it just have SEMI Root???
Another RIC must to crack??
Thank you @[NUT]. You're awesome
Sent from my C6903 using Tapatalk
Is this normal, in this case to have /system without RW ?
binoslaw said:
Is this normal, in this case to have /system without RW ?
Click to expand...
Click to collapse
For this version, yes... Will try to find a solution tonight...
The rom is fine to use and some root tasks can still be performed, using recovery you are able to install just about everything... Provided it is flashable of course
Yes, I know. BTW great work. I need RW because I would like to uninstall some apps.
Anyway. I'm waiting for Your magic.
Sent from my C6903 using XDA Premium 4 mobile app
binoslaw said:
Yes, I know. BTW great work. I need RW because I would like to uninstall some apps.
Anyway. I'm waiting for Your magic.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can use twrp for that too you know
Boot twrp, mount system, go to advanced and then the file manager. Navigate to system/app and tap all files you want to do something with... :highfive:
Will /system remount work on an Unlocked Bootloader?
mynameisjon said:
Will /system remount work on an Unlocked Bootloader?
Click to expand...
Click to collapse
Only with a patched ramdisk on the stock kernel I'm afraid... I can do that though, it's not that hard
If anyone wants a patched ramdisk-kernel for this ROM, let me know. I won't integrate a recovery though, just the RW patch.
BIG NOTE: it is intended for use on an UNLOCKED BOOTLOADER ONLY then ... just FYI
Because of your question @mynameisjon I reallized that with the guide in post #2, it should be fairly easy to switch between locked and unlocked TA+kernel sets
[NUT] said:
Only with a patched ramdisk on the stock kernel I'm afraid... I can do that though, it's not that hard
If anyone wants a patched ramdisk-kernel for this ROM, let me know. I won't integrate a recovery though, just the RW patch.
BIG NOTE: it is intended for use on an UNLOCKED BOOTLOADER ONLY then ... just FYI
Because of your question @mynameisjon I reallized that with the guide in post #2, it should be fairly easy to switch between locked and unlocked TA+kernel sets
Click to expand...
Click to collapse
Would be awesome if you could provide the ramdisk-kernel. I'm assuming that it's a boot.img and that I'd have to install the dual recovery seperately?
[NUT] said:
Only with a patched ramdisk on the stock kernel I'm afraid... I can do that though, it's not that hard
If anyone wants a patched ramdisk-kernel for this ROM, let me know. I won't integrate a recovery though, just the RW patch.
BIG NOTE: it is intended for use on an UNLOCKED BOOTLOADER ONLY then ... just FYI
Because of your question @mynameisjon I reallized that with the guide in post #2, it should be fairly easy to switch between locked and unlocked TA+kernel sets
Click to expand...
Click to collapse
For Locked booloader you can use the same root method of 259?
mynameisjon said:
Would be awesome if you could provide the ramdisk-kernel. I'm assuming that it's a boot.img and that I'd have to install the dual recovery seperately?
Click to expand...
Click to collapse
Correct. But if you use my ROM package, recovery will already have been integrated.
fer2503 said:
For Locked booloader you can use the same root method of 259?
Click to expand...
Click to collapse
I'm assuming you mean .290? Well... that same method has been applied in this ROM... but to no avail unfortunately, it needs some updating unfortunately.
Yes, you are right, i mean 290. I Hope you Can find a solution
[NUT] said:
Correct. But if you use my ROM package, recovery will already have been integrated.
Click to expand...
Click to collapse
Does an unlocked bootloader still require flashing the stripped package?
mynameisjon said:
Does an unlocked bootloader still require flashing the stripped package?
Click to expand...
Click to collapse
Yes sir, it contains all the bits the flashable zip can not flash. I did not check if the kernel itself changed to be honest, so maybe this ROM will work fine on any .290 kernel... but i still need to test that.
Loads of stuff to do tonight
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTICE: Go here for my newer tool here http://forum.xda-developers.com/showthread.php?p=52973530
ABOUTThis is a very simple CMD UI to install the TWRP (Jellybean and Kitkat) for the P6, as well as to revert back to stock recovery. There is also option to unlock bootloader, but I'm not very sure that it works.
Hope this makes flashing TWRP/Stock recoveries easier!
This is my first time making something for xda. I would be excited to hear any feedback or suggestions.
FEATURES
TWRP Installing for Jellybean, Kitkat B506, and OMNI ROM.
Reverting to stock recovery for Jellybean and Kitkat B506.
Entering into recovery.
Unlocking device (untested)
REQUIREMENTS
Unlocked Bootloader (You can use this tool or install B506)
KITKAT B506 Based ROM
OMNI Based ROM
JELLYBEAN Based ROM
DRIVERS FOR HUAWEI P6-U06 or P6-U00
DOWLOADS
TWRP Installer V1.1.3b
TWRP Installer V1.1.3a
TWRP Installer V1.1.2
TWRP Installer V1.1.0
TWRP Installer V1.0.1
TWRP Installer V1.0.0
INSTRUCTIONSHere are the steps:
1. Download file here. http://goo.gl/6nONyf
2. Extract the rar to desktop.
3. Run "TWRP_Installer.exe". I don't believe you need admin settings.
4. And just follow instructions on the screen from there.
WHAT IF MY PHONE WON'T BOOT?Do not worry! Just follow the instructions below!
However, you will have to enter into fastboot mode manually before you use the tool. This is how:
1. Plug in your phone to a computer.
2. Press down power and volume(-) for 10 seconds, and wait for your device to turn off. Do not let go.
3. After you see Huawei logo for 2 seconds, release the power button.
4. After 5 seconds, release the volume (-) button.
5. This will enter into fastboot mode, and then you can continue to use the tool. From there, you would either:
a) Install Stock Kitkat/Jellybean Recovery, b) TWRP Kitkat/Jellybean
6. Enter recovery mode. If you choose stock recovery, download an UPDATE.APP and install the OS likewise. If you choose TWRP, download a custom rom, and install the OS likewise.
CREDITS @surdu, @TeamWin, @tauio111 .
Here is the OP of TWRP. Make sure you thank surdu for his hard work.
http://forum.xda-developers.com/showthread.php?t=2709353
Here is the OP for bootloader unlock. Make sure to thank tauio111.
http://forum.xda-developers.com/showthread.php?p=50741449
Here is the old work that I had posted. This gave me the thought to make the CMD installer.
http://forum.xda-developers.com/showpost.php?p=49986799&postcount=10
And don't forget to thank me of course:laugh:
If you repost my work, make sure to give credits to me.
SCREENSHOTS
CHANGELOG2014-Apr-07 - V 1.0.0
Initial Release
2014-Apr-09 - V 1.0.1
Added Support For Jellybean
Added Bootloader Unlock
Added Boot.img Restore
2014-Apr-12 - V 1.1.0
Removed issue for external dll dependency
Removed .bat file dependency to avoid accidental executing
Move recovery.img, boot.img, adb.exe, fastboot.exe into another folder, easier to find TWRP_Installer.
2014-Apr-14 - V 1.1.2
Updated to newest surdu's 2.7.0.0 TWRP
Included boot.img OMNI and B506 for TWRP internal storage support
Fixed a bug issue with option 5 and 6
2014-Apr-24 - V 1.1.3a
Fixed an issue with option 1
2014-May-5 - V 1.1.3b
Added support to Windows XP
XDA:DevDB Information
CMD TWRP Installer, Tool/Utility for the Huawei Ascend P6
Contributors
bokchoi2020, surdu, tauio111
Version Information
Status: No Longer Updated
Created 2014-07-04
Last Updated 2014-07-04
thx
Curcio said:
thx
Click to expand...
Click to collapse
No problem! If I have time, next update I may include choice to install Jellybean Twrp and Jellybean stock!
OK, Update released!
To 1.0.1! More details in the OP thread!
My Phone is Stuck!
Please help,
My phone is stuck after i accidentally installed the OMNI boot image from this tool on the stock Kitkat B506. The problem is that "TWRP_Installer_1.0.1.exe" was not working, asking for some missing .dll. Then i just double clicked on "omni_boot_kitkat.bat" and without waiting for my input or confirmation, it went ahead and did something. Now i am stuck on the android logo. I don't have TWRP also. Please help me to bring the system back to normal.
-Majrul
majrul said:
Please help,
My phone is stuck after i accidentally installed the OMNI boot image from this tool on the stock Kitkat B506. The problem is that "TWRP_Installer_1.0.1.exe" was not working, asking for some missing .dll. Then i just double clicked on "omni_boot_kitkat.bat" and without waiting for my input or confirmation, it went ahead and did something. Now i am stuck on the android logo. I don't have TWRP also. Please help me to bring the system back to normal.
-Majrul
Click to expand...
Click to collapse
Click the stock_boot_kitkat.bat to revert to stock boot.img.
Or just do
fastboot flash boot boot.img
I will look into the issue with the dll library being missing.
Sent from my P6-U06 using xda app-developers app
bokchoi2020 said:
Click the stock_boot_kitkat.bat to revert to stock boot.img.
Or just do
fastboot flash boot boot.img
I will look into the issue with the dll library being missing.
Sent from my P6-U06 using xda app-developers app
Click to expand...
Click to collapse
I am unable to, because i am getting this error everytime:
error: device unauthorized. Please check the confirmation dialog on your device.
And there is nothing on the screen except an android logo. I am unable to do anything!
majrul said:
I am unable to, because i am getting this error everytime:
error: device unauthorized. Please check the confirmation dialog on your device.
And there is nothing on the screen except an android logo. I am unable to do anything!
Click to expand...
Click to collapse
Shoot.... but how is that possible?
When you install the omni boot.img, it requires usb debugging enabled, with RSA fingerprint from the computer to be whitelisted.
It installed, so clearly you had the RSA fingerprint whitelisted...
But now when you try to install the stock boot.img now it blacklisted the RSA fingerprint...
Ok, you can give this a shot but I'm not sure if it will work.
1. Get an SD card, put the B506 update on it.
2. Reboot into recovery with power and (+)(-) buttons.
3. Then reinstall the B506 update.
The update should replace the boot.img.
If it still doesn't work, do a factory reset/ partition wipe from the recovery.
I'm sorry for the inconvenience that this may have caused you.
I will look deeply into this issue.
Can u explain more? I don't get it
Sent from my GT-S7562 using xda app-developers app
Thy Boss said:
Can u explain more? I don't get it
Sent from my GT-S7562 using xda app-developers app
Click to expand...
Click to collapse
Basically my exe didn't start on his computer because I didn't compile the program with a static library. I'm going to fix that.
Then he went ahead and tried running one of my scripts, which installed the OMNI kernel. But he was using B506 stock, which then made his device not boot due to different ramdisk config.
I then suggest that he reflash the stock boot.img which I included in another batch file, but then the OMNI kernel asks for permissions for USB debugging.
His phone doesn't boot in the Android UI so he can't access the confirmation box that allows debuging.
He doesn't have TWRP, so he can't flash recovery boot.img that way either.
So now the only solution is to reinstall the ROM via UPDATE.APP.
Sent from my P6-U06 using xda app-developers app
bokchoi2020 said:
Basically my exe didn't start on his computer because I didn't compile the program with a static library. I'm going to fix that.
Then he went ahead and tried running one of my scripts, which installed the OMNI kernel. But he was using B506 stock, which then made his device not boot due to different ramdisk config.
I then suggest that he reflash the stock boot.img which I included in another batch file, but then the OMNI kernel asks for permissions for USB debugging.
His phone doesn't boot in the Android UI so he can't access the confirmation box that allows debuging.
He doesn't have TWRP, so he can't flash recovery boot.img that way either.
So now the only solution is to reinstall the ROM via UPDATE.APP.
Sent from my P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Followed the steps, got the phone working back again, but unfortunately lost all the phone memory data like call logs and sms. I will request you to please modify this program so that it doesn't installs anything without user confirmation.
I was sincerely looking for such a tool. I thank you for your effort, i am sure you will take care of the changes immediately.
majrul said:
Followed the steps, got the phone working back again, but unfortunately lost all the phone memory data like call logs and sms. I will request you to please modify this program so that it doesn't installs anything without user confirmation.
I was sincerely looking for such a tool. I thank you for your effort, i am sure you will take care of the changes immediately.
Click to expand...
Click to collapse
Yes, thanks for your understanding. For next release I will try to integrate the bat files into the exe so no more accidental installation by the end user will occur. Maybe have a confirmation before the install.
majrul said:
Followed the steps, got the phone working back again, but unfortunately lost all the phone memory data like call logs and sms. I will request you to please modify this program so that it doesn't installs anything without user confirmation.
I was sincerely looking for such a tool. I thank you for your effort, i am sure you will take care of the changes immediately.
Click to expand...
Click to collapse
Ok, Update will be soon.
Changes include .exe working without external dll support, and no more bat files.
bokchoi2020 said:
Ok, Update will be soon.
Changes include .exe working without external dll support, and no more bat files.
Click to expand...
Click to collapse
That's great. Really appreciate your efforts. I am waiting to downloading it again..
Ok, I just updated it to 1.10! If there are any issues, please tell me!
Changes include removing the .bat files and making the .exe non-dependant on external .dll libraries.
The images are put into a sources folder to make using the tool more easier for end user.
bokchoi2020 said:
Ok, I just updated it to 1.10! If there are any issues, please tell me!
Changes include removing the .bat files and making the .exe non-dependant on external .dll libraries.
The images are put into a sources folder to make using the tool more easier for end user.
Click to expand...
Click to collapse
Yes twrp.exe work good. Not any error this time.
bokchoi2020 said:
Ok, I just updated it to 1.10! If there are any issues, please tell me!
Changes include removing the .bat files and making the .exe non-dependant on external .dll libraries.
The images are put into a sources folder to make using the tool more easier for end user.
Click to expand...
Click to collapse
Wow. Works perfect! Thanks a lot once again for such a nice tool!
Super travail
Un grand merci pour ce bon boulot , sa marche nickel , continu comme sa : O: O: O
olhamike said:
Un grand merci pour ce bon boulot , sa marche nickel , continu comme sa : O: O: O
Click to expand...
Click to collapse
Pas de probleme!
Desole si mon francais n'est pas bon.
Sent from my P6-U06 using xda app-developers app
Works fine for me and solved my problems.
Absolutely an useful application, thanks alot bro
What is better than the standard CM Recovery:
You can flash another firmware (not the CM)
Normal backup data
You can easily flash the Root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unlock the bootloader as on CM Wiki instructions
Puth the phone in bootloader mode
In the folder with fastboot put crackling-t0x1.img
Enter the following command:
Code:
fastboot -i 0x2970 erase recovery
then Enter
Code:
fastboot -i 0x2970 flash recovery crackling-t0x1.img
Disconnect the device from the USB and remove the battery. Then replace the battery and restart the device in recovery mode to verify the installation. To do this, hold down the "Volume Down" and "Power".
You can download crackling-t0x1.img from here
http://www91.zippyshare.com/v/60lfsDiR/file.html
Credits to 4PDA Members and especially to FindYanot for developing and allowing posting here
IT is NOT my Work
I've been using this for a while, working very good!
Great to make backups and test ROMs.
There is a problem - this recovery can not mount f2fs partitions
RaidonChrome said:
There is a problem - this recovery can not mount f2fs partitions
Click to expand...
Click to collapse
for my information : which system firmware can mount f2fs partitions?
Dior DNA said:
for my information : which system firmware can mount f2fs partitions?
Click to expand...
Click to collapse
Latest Cyanogen Mod 13 has Linux 3.10, so it should be able to mount f2fs just fine
RaidonChrome said:
Latest Cyanogen Mod 13 has Linux 3.10, so it should be able to mount f2fs just fine
Click to expand...
Click to collapse
thanks, then perhaps latest CM recovery will mount f2fs just fine as well.
Dior DNA said:
thanks, then perhaps latest CM recovery will mount f2fs just fine as well.
Click to expand...
Click to collapse
It does not, in fact it is broken even with ext4 currently
PLEASE HELP, something when wrong
RaidonChrome said:
It does not, in fact it is broken even with ext4 currently
Click to expand...
Click to collapse
Is this the reason why i can't install gapp on my wileyfoxswift and an error appear("e: unable to find partition size for '/recovery") every time i use the wipe.
i upgraded from 12.1 to
13.0-20160127-NIGHTLY-crackling and use the same for recovery but did not work so i installed TWRP and this error occurs -see pics
PLEASE HELP
AromaGapp not working in TWRP
TWRP not working in Aroma Gapp need fix (Aroma is best for me since i can customize install & will not replace CM stock files/app)
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
noob2016 said:
TWRP not working in Aroma Gapp need fix (Aroma is best for me since i can customize install & will not replace CM stock files/app)
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
Aroma compatibility with TWRP is listed on the Open G-Apps website.
Unfortunately this is the only TWRP we have available to us.
Tamarinde said:
Aroma compatibility with TWRP is listed on the Open G-Apps website.
Unfortunately this is the only TWRP we have available to us.
Click to expand...
Click to collapse
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Thanks
robin0800 said:
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Click to expand...
Click to collapse
That is great! i hope i can try i try it but sadly i send it back since the phone was just here for the upgrade. Anyway thanks for the reply here and on my other post.
Much appreciated
robin0800 said:
No it is not there is this one https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRPand yes it works with aroma
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!
There is a zip file and recovery. IMG file, any reason why?
image45 said:
There is a zip file and recovery. IMG file, any reason why?
Click to expand...
Click to collapse
The .img file can be flashed by fastboot.
The zip file by any non stock recovery
and yes I do know the image file is contained in the zip but some people may not
robin0800 said:
The .img file can be flashed by fastboot.
The zip file by any non stock recovery
and yes I do know the image file is contained in the zip but some people may not
Click to expand...
Click to collapse
Yes i downloaded the zip file, extracted the recovery.img then flashed by fastboot. I am used to using fastboot commands
So the zip file would function as an update file via a non stock recovery, however once installed would replace the non stock recovery with twrp version!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TeamWin's TWRP Touch Recovery For Lenovo A7000-a
SCREENSHOT ON ATTACHMENT
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. TWRP also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
This TWRP was originally formed to work on Lenovo K3 Note. After Denis work on K3 Note, I wanted to make it that would work on Lenovo A7000-a to. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at https://github.com/omnirom/android_bootable_recovery/
Flashing Instructions :
To install recovery images use Flashify / Rashr / TWRP Manager from Play Store or flash in your current recovery:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
Download :
TWRP : Mod Edit: Link Removed
Remember to do backup of your current recovery before installing.
XDA:DevDB Information
TWRP 3.0.2-8, TWRP for the Lenovo A7000
Contributors
HDHR, sandeep.sethi, Denis_PDA
Version Information
Status: Stable
Created 2016-10-29
Last Updated 2017-02-19
Mod Edit: Thread Closed
Changelog
TWRP 3.0.2-8 :
~Upgraded to TWRP 3.0.2-8 (Base, Security Patch,ETC.)
~Minor fixes
~Added ability to set system.img
=>TWRP -> Install -> Install image -> system.img -> System Image -> Swipe to confirm Flash.
~Optimized OTG FS support FAT32, exFAT, NTFS
~Flashable installation supported
TWRP 3.0.2-6 :
~Updated to TWRP 3.0.2-6 (Security Patch,Base,ETC.)
~Fixed code name error
~Backup and Restore Improvement
~Lot of Improvement
TWRP 3.0.2-5 :
~Initial release
Detailed Changelogs Here :
https://github.com/omnirom/android_bootable_recovery/commits/android-6.0
Reserved
How is it possible ? Flashing a recovery from another recovery ? Doesn't the recovery partition get overwritten?
[Thanks though for the new version]
tanish2k09 said:
How is it possible ? Flashing a recovery from another recovery ? Doesn't the recovery partition get overwritten?
[Thanks though for the new version]
Click to expand...
Click to collapse
Its will overwrite the old one with the new one... You can update via TWRP to
1. Boot to TWRP
2. Select install files
3. Select install image
4. Then select recovery image
5. Select install on recovery
6. Finish and go to reboot option and select reboot to recovery
6. Tadaaa your new Recovery installed
Themes support?
tanish2k09 said:
Themes support?
Click to expand...
Click to collapse
Support :fingers-crossed:
Thanks!
Ceco85 said:
Thanks!
Click to expand...
Click to collapse
Your welcome
What about compatibility of old backup created in 3.0.2-1
CyberDeat said:
What about compatibility of old backup created in 3.0.2-1
Click to expand...
Click to collapse
It I'll not detect backup from old TWRP,you need to backup files on new TWRP and just move your old backup to new folder one
You ported it or built it from source?
tanish2k09 said:
You ported it or built it from source?
Click to expand...
Click to collapse
Build from source on k3 note ported to a7000 :3
How to install on a non-rooted MM A7000-a?
jocph said:
How to install on a non-rooted MM A7000-a?
Click to expand...
Click to collapse
Use SP Flash tools
Thanks for replying. Can you give the steps? Doesn't spflashtool need a scatterfile? Sorry but I'm not very familiar with spflashtool.
Thnx HDHR for the recovery :good:
---------- Post added at 03:37 PM ---------- Previous post was at 03:21 PM ----------
jocph said:
Thanks for replying. Can you give the steps? Doesn't spflashtool need a scatterfile? Sorry but I'm not very familiar with spflashtool.
Click to expand...
Click to collapse
In sp flash tool...for flashing Recovery
1-Install lenovo driver
2-open sp flash tool by administration
3-load scatter file,
4-select recovery only (also select recovery u have downloaded)
5-check in option that dal dal option is tick
6- click on download
7-switch off ur phone...take out battery for 5 sec..reinsert battery and connect ur phone with pc then
It will automatically flash the recovery after u see a download ok popup window disconnect ur phone and u have successfully flash TWRP recovery
Where can I find the scatterfile for this TWRP image? The download only gives the img file. My MM A7000-a is not rooted and does not have custom recovery yet.
i flashed a theme on my old twrp.....the theme got caried on to this one......
i am unable to remove it....plez help.....
there is no folder of twrp in my sd card....
jocph said:
Where can I find the scatterfile for this TWRP image? The download only gives the img file. My MM A7000-a is not rooted and does not have custom recovery yet.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B5os0Tgr4idrbTA1WkxhUHB6TzA/view
Scatter file...there is also a old TWRP dont use it....
Hey there!
I don't own this device anymore!
There will be no updates from me anymore.
This is how to Root the BQ Aquaris X2 / X2 PRO without a Custom Recovery like TWRP!
This is more or less a workaround until an official TWRP recovery will be available.
*** WARNING ***
This will work for the following builds:
- 1.3.0 -> 1.7.2
Requirements:
- ADB/Fastboot + Drivers
- Unlocked Bootloader
- Working Brain
How to:
Unlock Bootloader:
Unlocking Method
Our Aquaris X2 PRO is locked and needs to be unlocked before flashing anything.
STEPS:
1. Connect your phone to your PC using ADB.
2. > adb reboot bootloader
3. Your phone will now enter the fastboot mode
4. > fastboot flashing unlock
5. Your phone will be unlocked.
*** Make a backup of all your data as it might get erased during the process***
*** Warning***
After you unlock the device, it will become less secure. Your personal data might be leaked or lost.
Please think twice before flashing your phone and do it at your own risk.
Root / install Magisk:
Step 1:
Download the latest Magisk Manager from this Link:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And install the APK File.
Step 2:
Download the patched boot image for your firmware version (See attached screenshot):
Aquaris X2 PRO
Version 1.3.0_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.3.0.img
Version 1.4.0_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.4.0.img
Version 1.5.0_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.5.0.img
Version 1.6.0_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.6.0.img
Version 1.7.0_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.7.0.img
Version 1.7.1_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.7.1.img
Version 1.7.2_x:
https://tt-services.de/xda/aquarisx2pro/patched_boot_1.7.2.img
---
Aquaris X2 Thanks to tomparr for providing the images!
Version 1.3.0_x:
https://tt-services.de/xda/aquarisx2/patched_boot_1.3.0.img
Version 1.4.0_x:
https://tt-services.de/xda/aquarisx2/patched_boot_1.4.0.img
Version 1.5.0_x:
https://tt-services.de/xda/aquarisx2/patched_boot_1.5.0.img
Version 1.5.0_x:
https://tt-services.de/xda/aquarisx2/patched_boot_1.6.0.img
Version 1.7.0_x:
https://tt-services.de/xda/aquarisx2/patched_boot_1.7.0.img
Version 1.7.1_x:
https://tt-services.de/xda/aquarisx2/patched_boot_1.7.1.img
Step 3:
Use ADB to boot into Bootloader:
> adb reboot bootloader
Now try if the patched Boot Image will work for you:
> fastboot boot <<path to boot image>>
Now the Device should boot with this Image.
Check if the device will boot as expected and take a look at the Magisk Manager APP to check if everything has succeeded.
Sometimes this will not always work as expected. If your device stuck at the Android one screen try to flash the image directly (See next step)
If so you can flash the Boot image with the folowing Steps:
> adb reboot bootloader
> fastboot flash boot <<path to boot image>>
Done! :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
works for me too. thanks.
Works perfect, however when I try to enter into Magisk Hide the app close suddenly. Any advice?
wiran8 said:
Works perfect, however when I try to enter into Magisk Hide the app close suddenly. Any advice?
Click to expand...
Click to collapse
Sorry I havent tested MagiskHide yet.
Same problem here...
I opened a issue on GitHub.
You can view the current status here:
https://github.com/topjohnwu/Magisk/issues/619
How do you create the bootimages?
Micha_Btz said:
How do you create the bootimages?
Click to expand...
Click to collapse
Hi Micha_Btz,
there is a detailed guide how to do that in the official Magisk Thread.
You can view it in this section:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
It works withg Aquaris X2? Without the "pro"
SrWindings said:
It works withg Aquaris X2? Without the "pro"
Click to expand...
Click to collapse
Hi SrWindings,
I've updated the thread and add a boot image for the X2.
Can you can give me feedback if everything works?
I do not own an X2...
TurboToni said:
Hi SrWindings,
I've updated the thread and add a boot image for the X2.
Can you can give me feedback if everything works?
I do not own an X2...
Click to expand...
Click to collapse
I will test it today or tomorrow (CEST Time Zone), and I will give you the feedback. Thank you. I hope it works
TurboToni said:
Hi SrWindings,
I've updated the thread and add a boot image for the X2.
Can you can give me feedback if everything works?
I do not own an X2...
Click to expand...
Click to collapse
Well I tested it now with the "fatboot boot [image path]" and it doesen't work. It gets stuck in the android one logo.
Could you fix it or do you need more information?
SrWindings said:
Well I tested it now with the "fatboot boot [image path]" and it doesen't work. It gets stuck in the android one logo.
Could you fix it or do you need more information?
Click to expand...
Click to collapse
Which rom version are you using? Can you tell me the exact build number?
TurboToni said:
Which rom version are you using? Can you tell me the exact build number?
Click to expand...
Click to collapse
Im using the stock rom (the one coming with the device)
Version: 1.4.0_20180830-1036
Android: 8.1.0
https://imgur.com/a/Xkezv7y
SrWindings said:
Im using the stock rom (the one coming with the device)
Version: 1.4.0_20180830-1036
Android: 8.1.0
https://imgur.com/a/Xkezv7y
Click to expand...
Click to collapse
Sorry, it looks like i am not able to create the image without the hardware
TurboToni said:
Sorry, it looks like i am not able to create the image without the hardware
Click to expand...
Click to collapse
Can you at least tell me how to do it? Please?
SrWindings said:
Can you at least tell me how to do it? Please?
Click to expand...
Click to collapse
There is a detailed guide how to do that in the official Magisk Thread.
You can view it in this section:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
TurboToni said:
There is a detailed guide how to do that in the official Magisk Thread.
You can view it in this section:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thank you, but how can I get my boot image? I searched the entire internet for a method for dumping/backuping my boot image without a custom recovery or root and I don't find any. Help me please!
SrWindings said:
Thank you, but how can I get my boot image? I searched the entire internet for a method for dumping/backuping my boot image without a custom recovery or root and I don't find any. Help me please!
Click to expand...
Click to collapse
You can use the official firmware located here:
https://www.bq.com/de/support/aquaris-x2/support-sheet
Download the 1.4 firmware zip file and extract the boot image manually from there.
hello
i heard of trouble with the X2 (pro)'s camera after rooting in one way or another. anybody here who knows something about that?
qiezer said:
hello
i heard of trouble with the X2 (pro)'s camera after rooting in one way or another. anybody here who knows something about that?
Click to expand...
Click to collapse
Hey there,
I don't have any problems/bugs since rooting the phone.
Can you tell me where those camera problems are mentioned?
TurboToni said:
Hey there,
I don't have any problems/bugs since rooting the phone.
Can you tell me where those camera problems are mentioned?
Click to expand...
Click to collapse
hello TurboToni
thx for your answer. my collegue couldn't tell, where he might have read it. it may have had to do with autofocus but not sure
greetz