Database Develop

[Q] Is Moto G safe to root?

Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yea go ahead. Its totally safe to root. No issues or bugs faced till now. Follow this thread : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
I have rooted and flashed TWRP v 2.8.0.1. I am hoping someone compiles a working CWM recovery for our device.

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.

Okay I will, thanks.
Though what's strange is the version number. I went to the official site of TWRP and the version was 2.8.0.0, but on the root thread, the version is 2.8.0.1.

Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit

marcviado said:
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.
Click to expand...
Click to collapse
Yup current TWRP v2.8 has some issues while flashing KK ROMS and taking too much time to clear cache. The device reboots automatically while taking a TWRP system backup.
We need a CWM recovery ASAP :fingers-crossed:
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
Same here.
Thanks a ton I wanted to rollback to the previous version. I didnt have the latest system backup after the OTA update.

KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
No problems with this one right?

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
v2.7 is relatively bugless as compared to v2.8

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
Nope, works as expected

Okay, I need a little help here. I flashed the old twrp via fastboot but then got the mismatched partition size error. Well I thought what the hell, and I selected recovery from the menu, but the problem is that the phone doesn't go into recovery, just reboots. What should I do?
EDIT: I also tried rebooting via recovery when the phone wasn't connected to the laptop. If i press the power button on any of the options - normal powerup, recovery, factory or barcodes - the phone switches off.
EDIT 2: I tried getting into recovery via adb, but all I get is a 'no command' message when the phone reboots. A quick google search showed me that the no command message means that the phone still has the stock recovery. It seems like twrp isn't flashing. Any ideas!?

[Q&A] [Tutorial] Xperia Z & ZL Bootloader Unlocking/Relocking

Q&A for [Tutorial] Xperia Z & ZL Bootloader Unlocking/Relocking
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

4.4.4 Bootloader Unlock?
I have an Xperia Z C6616 (10.5.1.A.0.283) that I rooted using easy root via flashtool. However, in the service menu, it says I am unable to unlock the bootloader. Is this true? Will I be forced to flash back to 4.3 to unlock it?

japansam23 said:
I have an Xperia Z C6616 (10.5.1.A.0.283) that I rooted using easy root via flashtool. However, in the service menu, it says I am unable to unlock the bootloader. Is this true? Will I be forced to flash back to 4.3 to unlock it?
Click to expand...
Click to collapse
If it says you cannot unlock your bootloader, then you cannot unlock it at all, regardless of which firmware version is installed.
The C6616 bootloader is permanently locked because Bell requested it be that way and there's no way (either officially or unofficially) around it, unfortunately.
Sent from my C6603 using Tapatalk

If it says you cannot unlock your bootloader, then you cannot unlock it at all, regardless of which firmware version is installed.
The C6616 bootloader is permanently locked and there's no way (either officially or unofficially) around it, unfortunately.
Click to expand...
Click to collapse
Well thats incredibly frustrating. Is there any way then to flash new roms or install a recovery? Also, it might not matter, but before I updated to 4.4, it listed my model number as C6606.

Bootloader Issue
Hey guys, ran into a little issue. I flashed my phone with a stock ROM, C6603_10.3.A.0.423_Generic ES.ftf.
Figuring It'd be fine, I then proceeded to attempt to unlock my bootloader. However, this time after flashing this stock ROM, unlocking the bootloader would cause my phone to crash, resulting in having to reflash the stock rom again.
Any ideas?
Cheers.

Please help!
Hello, I need help with unlocking the bootloader for my Sony Xperia Z please. This is the first time I am doing this, so I am a extremely novice on these things. All I want is to flash the sony rom and install android 5 lollipop on my Xperia Z
I have done all the steps mentioned above but when I type the command fastboot.exe -I 0x0fce getvar version it just says waiting for device.
I don't know if my phone is even in fastboot mode. I have turned the developer mode on phone setting with USB debugging set to ON. When I connect my phone to the computer I press power and volume up for around 10 second before plugging in the USB. The phone vibrates 3 times and there is a sound in computer but nothing else happens. When I type the command adb devices, it shows no device attached.
I don't know if this is due to me not installing the drivers but I was tried to install Flashtool-drivers-1.5-20140318.exe file, the installation failed. So I went to advance startup setting and disable driver signing. It then installed. I also downloaded the fastboot package and clicked all the exe files. And my phone has its rooting status: Bootloader unlock allowed: Yes
Please help!

Kathmandu13 said:
I don't know if my phone is even in fastboot mode. I have turned the developer mode on phone setting with USB debugging set to ON. When I connect my phone to the computer I press power and volume up for around 10 second before plugging in the USB. The phone vibrates 3 times and there is a sound in computer but nothing else happens.
Click to expand...
Click to collapse
You're holding the wrong key combination.
Power your phone OFF first.
When the phone is off, hold volume UP only while connecting your device to your PC. Do not press the power button. The LED should light up blue when done correctly. You can then stop pressing the volume key.
Sent from my C6603

kingvortex said:
You're holding the wrong key combination.
Power your phone OFF first.
When the phone is off, hold volume UP only while connecting your device to your PC. Do not press the power button. The LED should light up blue when done correctly. You can then stop pressing the volume key.
Sent from my C6603
Click to expand...
Click to collapse
Oh Thank you so much! I think I unlocked the bootloader now
So what do I need to do now to install custom ROM?
If I understood correctly, I need to flash the current Sony ROM and install different one? Then again what is root? Is unlocking bootloader rooting? Also is the information on the forum up to date? because according to it the newest firmware is 10.3.1.A.0.244/10.3.1.A.2.67. But my firmware is 10.5.1.A.0.292. Please help, I tried finding these information but can't find them.

Kathmandu13 said:
Oh Thank you so much! I think I unlocked the bootloader now
So what do I need to do now to install custom ROM?
If I understood correctly, I need to flash the current Sony ROM and install different one? Then again what is root? Is unlocking bootloader rooting? Also is the information on the forum up to date? because according to it the newest firmware is 10.3.1.A.0.244/10.3.1.A.2.67. But my firmware is 10.5.1.A.0.292. Please help, I tried finding these information but can't find them.
Click to expand...
Click to collapse
In my own opinion, you shouldn't even unlock your bootloader without getting better known to the entire device and its ROMS/Kernels and etc.,
Anyway, I tink that you haven't made TA pratition backup even, and if I'm right, then you've erased your DRM keys forever without a way getting them back.
But if you have made TA partition backup, then we can proceed to explain next thing.
To flash a custom ROM, you don't have to flash newer nor older software version.
All you have to do is go to your favourite ROM thread and read the instructions very carefully, otherwise you're risking to brick/soft-brick your device.
But on different ROMs can be different flashing guides, for example, we can take "Validus" ROM:
VALIDUS
Flashing instructions are : (I'm going to quote them)
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Optional- Flash GApps.
8. Reboot and Enjoy Validus!
Click to expand...
Click to collapse
So in overall, that mean at first you've to have CWM (ClockWorkMod Recovery) (but I think that it's not necessary if you would flash boot.img with it either way)
Secondly, you've to put the entire ROM in your SD Card (not in phone memory), you can include gapps as well,
Third, you need to extract the file named "boot.img" from the ROM which you've downloaded (Now i'm talking about VALIDUS and ONLY IF YOU'RE GOING TO INSTALL THIS ROM EXACTLY), but don't remove it from .rar/.zip.
After you've done everything what is written above, you can flash boot.img using the command prompt and fastboot file, which you were using to unlock your bootloader.
The command is this : fastboot flash boot boot.img
Then, write fastboot reboot and as soon as your LED will change color, push the volume up rocker and then you will be in recovery. After that, go to "Apply Update" --> "Choose from files" or sth (don't remember now), --> "Validus.zip/.rar". and optional you can flash gapps either.
And then pus the button to "Reboot now".
That's all - you've newest Validus build.
But the main point is that for example you would take Pabx rom, you'll have to do everything using CMD (fastboot)
PABX's ROM YUGA L
Look at yourself and compare everything.
Validus ROM is customized than Pabx ROM. It has more customatizations either : APPS, Control, Mods, Gesture and etc., and Pabx ROM is pure-stock L (I think).
I hope I anwered to all ur questions, if not - quote me

Thanks!
LaurynasVP said:
In my own opinion, you shouldn't even unlock your bootloader without getting better known to the entire device and its ROMS/Kernels and etc.,
Anyway, I tink that you haven't made TA pratition backup even, and if I'm right, then you've erased your DRM keys forever without a way getting them back.
But if you have made TA partition backup, then we can proceed to explain next thing.
To flash a custom ROM, you don't have to flash newer nor older software version.
All you have to do is go to your favourite ROM thread and read the instructions very carefully, otherwise you're risking to brick/soft-brick your device.
But on different ROMs can be different flashing guides, for example, we can take "Validus" ROM:
VALIDUS
Flashing instructions are : (I'm going to quote them)
So in overall, that mean at first you've to have CWM (ClockWorkMod Recovery) (but I think that it's not necessary if you would flash boot.img with it either way)
Secondly, you've to put the entire ROM in your SD Card (not in phone memory), you can include gapps as well,
Third, you need to extract the file named "boot.img" from the ROM which you've downloaded (Now i'm talking about VALIDUS and ONLY IF YOU'RE GOING TO INSTALL THIS ROM EXACTLY), but don't remove it from .rar/.zip.
After you've done everything what is written above, you can flash boot.img using the command prompt and fastboot file, which you were using to unlock your bootloader.
The command is this : fastboot flash boot boot.img
Then, write fastboot reboot and as soon as your LED will change color, push the volume up rocker and then you will be in recovery. After that, go to "Apply Update" --> "Choose from files" or sth (don't remember now), --> "Validus.zip/.rar". and optional you can flash gapps either.
And then pus the button to "Reboot now".
That's all - you've newest Validus build.
But the main point is that for example you would take Pabx rom, you'll have to do everything using CMD (fastboot)
PABX's ROM YUGA L
Look at yourself and compare everything.
Validus ROM is customized than Pabx ROM. It has more customatizations either : APPS, Control, Mods, Gesture and etc., and Pabx ROM is pure-stock L (I think).
I hope I anwered to all ur questions, if not - quote me
Click to expand...
Click to collapse
Thank you very much for your reply and yes perhaps you are right. I should not mess with my phone's software. My skill and knowledge on this is extremely limited. I think I did unlock my bootloader but I will leave it on that. My phone still runs fine for now. Unless I find some tutorial videos which I can understand, I will stay away from flashing my phone
Thanks again for help.

Kathmandu13 said:
Thank you very much for your reply and yes perhaps you are right. I should not mess with my phone's software. My skill and knowledge on this is extremely limited. I think I did unlock my bootloader but I will leave it on that. My phone still runs fine for now. Unless I find some tutorial videos which I can understand, I will stay away from flashing my phone
Thanks again for help.
Click to expand...
Click to collapse
Well, you shouldn't be afraid of flashing stock 5.0.x, as you're not flashing custom kernels. To flash pabx's rom, you just need to connect your phone via USB to PC, whilst holding Volum +. (Phone need to be turn on). Then blue led will show up and you're ready to write commands via CMD prompt, wich you can open in sdk/platform-tools/ (or simply download ADB and fastboot drivers).
To open them, just with holding RMB click on "open command prompt here", then write this command:
fastboot devices
Click to expand...
Click to collapse
And if it will show you like CXXXXXX (or something like that, if not even first letter is C, it's alright), you're ready to go.
Then download all files needed from Pabx site (ROM and gapps). Extract both in ADB-Fastboot driver's folder (in which are fastboot.exe, adb.exe). It should be these files: userdata.img, system.img, boot.img.
And then you just simple need to flash these IMGs:
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
And then just type
fastboot reboot
Click to expand...
Click to collapse
.
Your phone will reboot and will load ~ 1-3 minutes.
Well, personally I don't encourge you to do that, I'm just suggesting. It's your choice to do that or not. I just have given you all the instructions.
Hope I helped you

Hi,
I have problem unlocking bootloader on my C6603. I successfully rooted it with easyroot, made TA backup, my phone says that unlocking bootloader is allowed but whenever i tried to do this it either fails or goes to bootloop. I was investigating a bit more and found some information saying that phone has to be simlock free with some certificates(???) and s1tool gives me answer that my simlock unlock is tampered. Is it the reason why i can't unlock bootloader? If so, is there any way to unlock it anyway?
Thanks in advance.
Sent from my C6603 using XDA Free mobile app

Unlocking Xperia Z bootloader
Hi guys
I 've got a trouble, i tried to unlock bootloader by flashtool and "classic" method. I've done it step by step like in video tutorial but finally cmd shows me that command.
I've checked it on other computer but it also failed.Installed all components + pc com.
Greetings.

Please someone tell me where is this goddamned "fastboot_with_Android_USB_file.rar" to download? It's almost four hours im searching everywhere to find it,but i can't.

Xperia Z2 stuck! help!!!
Hi guys, yesterday i tried to relock th bootloader of my xperia z2, and it was really easy, but now it doesn´t turn on, it´s stuck in flash mode, does anyone know what can i do to fix this? thanks a lot!

nikin101 said:
Hi guys, yesterday i tried to relock th bootloader of my xperia z2, and it was really easy, but now it doesn´t turn on, it´s stuck in flash mode, does anyone know what can i do to fix this? thanks a lot!
Click to expand...
Click to collapse
Did you relock while on a custom rom or kernel? Try flashing a stock FTF.
Sent from my C6603

kingvortex said:
Did you relock while on a custom rom or kernel? Try flashing a stock FTF.
Sent from my C6603
Click to expand...
Click to collapse
Yes, i think i did that. And how do i do that? And where can i download the stock FTF? Thanks, i'm new in this

nikin101 said:
Yes, i think i did that. And how do i do that? And where can i download the stock FTF? Thanks, i'm new in this
Click to expand...
Click to collapse
How to package and flash stock roms in FTF format
I wrote that guide for the Xperia Z, but the method is identical for the Z2. You will probably have to wipe data if you're coming from a custom rom.
Sent from my C6603

kingvortex said:
How to package and flash stock roms in FTF format
I wrote that guide for the Xperia Z, but the method is identical for the Z2. You will probably have to wipe data if you're coming from a custom rom.
Sent from my C6603
Click to expand...
Click to collapse
I can't find the words to thank you! I will try that today. Thanks a lot.

nikin101 said:
I can't find the words to thank you! I will try that today. Thanks a lot.
Click to expand...
Click to collapse
You're welcome.
Sent from my C6603

Access to recovery

Hello,
I installed the CWM recovery for my Xperia SP and then I changed my rom for Cyanogen mod 11. But now, I haven't acces to the recovery. When my phone boots, it does 3 red lights then boot normally even if I press any button to acces to any recovery. I tried to choose " reboot in recovery" bot it doesn't work too ! In addition, I tried to reinstall the recovery in debug mode but the installer says " access denied "
Can someone help me with this problem please ?
Thanks,

Taltausse said:
Hello,
I installed the CWM recovery for my Xperia SP and then I changed my rom for Cyanogen mod 11. But now, I haven't acces to the recovery. When my phone boots, it does 3 red lights then boot normally even if I press any button to acces to any recovery. I tried to choose " reboot in recovery" bot it doesn't work too ! In addition, I tried to reinstall the recovery in debug mode but the installer says " access denied "
Can someone help me with this problem please ?
Thanks,
Click to expand...
Click to collapse
Losing Recovery Mode for your device usually occurs when there is an error or a small mishap in the installation of the custom rom.
Usually, installation of recoveries is possible but for your case it didn't.
As such I recommend flashing a custom kernel compatible with the rom which in this case is Williams Kernel for CM.

Taltausse said:
Hello,
I installed the CWM recovery for my Xperia SP and then I changed my rom for Cyanogen mod 11. But now, I haven't acces to the recovery. When my phone boots, it does 3 red lights then boot normally even if I press any button to acces to any recovery. I tried to choose " reboot in recovery" bot it doesn't work too ! In addition, I tried to reinstall the recovery in debug mode but the installer says " access denied "
Can someone help me with this problem please ?
Thanks,
Click to expand...
Click to collapse
Please tell me the CM11 ROM you have used. Is your bootloader unlocked? Answering these might as well help you. Regards

My bootloader is locked so I can't flash a custom kernel. And I use this one : http://forum.xda-developers.com/showthread.php?t=2735975
Thanks you for your attention.

Taltausse said:
My bootloader is locked so I can't flash a custom kernel. And I use this one : http://forum.xda-developers.com/showthread.php?t=2735975
Thanks you for your attention.
Click to expand...
Click to collapse
Hello,
Sorry for the late reply.
Since you do not have any other option, I recommend repeating the whole rom flashing process

Taltausse said:
My bootloader is locked so I can't flash a custom kernel. And I use this one : http://forum.xda-developers.com/showthread.php?t=2735975
Thanks you for your attention.
Click to expand...
Click to collapse
There are reports that Williams Kernel v7 works on Locked Bootloader though I did not tested it personally.
You might want to try to flash it.
If else fails, then starting fresh is your only option as mentioned by Furrydaus

But, I haven't access to my recovery, So I should flash again my room but with tool flash that's it ?

TechnoSparks said:
There are reports that Williams Kernel v7 works on Locked Bootloader though I did not tested it personally.
You might want to try to flash it.
If else fails, then starting fresh is your only option as mentioned by Furrydaus
Click to expand...
Click to collapse
Kernels shouldnt be able to work on Locked Bootloaders in the first place lol
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
Taltausse said:
But, I haven't access to my recovery, So I should flash again my room but with tool flash that's it ?
Click to expand...
Click to collapse
Start Afresh, yes.
Utilize Flashtool to return back to Stock Firmware and repeat the process again
Regards,
Furrydaus

Ok thank you very much ! So is it good if I use this one http://forum.xda-developers.com/showthread.php?t=2704009 ?

Taltausse said:
Ok thank you very much ! So is it good if I use this one http://forum.xda-developers.com/showthread.php?t=2704009 ?
Click to expand...
Click to collapse
Use an. Ftf to reflash with Androxyde's Flashtool utility at Flashtool.net

Taltausse said:
Hello,
I installed the CWM recovery for my Xperia SP and then I changed my rom for Cyanogen mod 11. But now, I haven't acces to the recovery. When my phone boots, it does 3 red lights then boot normally even if I press any button to acces to any recovery. I tried to choose " reboot in recovery" bot it doesn't work too ! In addition, I tried to reinstall the recovery in debug mode but the installer says " access denied "
Can someone help me with this problem please ?
Thanks,
Click to expand...
Click to collapse
Why dont you try http://forum.xda-developers.com/showthread.php?t=2649923;)

I'm dumb, it worked ! I just forgot the right of super user for adb !
Thanks everyone, I'm going to be able to flash a new rom, thanks !
edit : After trying to format my phone in order to install a new rom, I waited 1 hours, nothing happened then I reboot it and now me phone refuses to boot.
I'm going to try flashtool I hope It will work to install the base stock rom..
edit 2 : It worked...
Now I just have to root, install recovery and start again.. Thanks every one !

Taltausse said:
Hello,
I installed the CWM recovery for my Xperia SP and then I changed my rom for Cyanogen mod 11. But now, I haven't acces to the recovery. When my phone boots, it does 3 red lights then boot normally even if I press any button to acces to any recovery. I tried to choose " reboot in recovery" bot it doesn't work too ! In addition, I tried to reinstall the recovery in debug mode but the installer says " access denied "
Can someone help me with this problem please ?
Thanks,
Click to expand...
Click to collapse
It is a very silly problem with CM11. Rooting is allowed to apps only by default. I had this problem too. It is easy to solve.
Just go to developer options and make sure rooting access is given to both "Apps and ADB" instead of "Apps only". That should solve your problem of "access denied" while installing recovery.

[TWRP][3.0.2][Unofficial] for Huawei P8 [GRA-L09]

TWRP 3.0.2
Huawei P8 GRA-L09​
Fully working recovery, no encryption support.
"No touch at boot" bug is solved.
Battery percentage.
Compiled with stock B370 kernel
(encryption support is still a WIP)
Since I hope to get it "Official" :angel:, I won't post the customized one here: have a look at @nexolight 's CM13 thread for that one.
No need to say you need an unlocked bootloader.
There's a lot of good guides on how to flash a recovery so I won't repeat here
Download:
https://www.androidfilehost.com/?fid=385035244224399403
MD5: 717f2219fef142a8b4713839186a32f7
Sources:
https://github.com/AD2076/android_device_huawei_grace
Credits:
Team Win for their amazing project
Thank to:
@nexolight (again!) cause she made me start develop in the custom roms universe

anyone could help here?
It was my fault: didn't had the phone for a couple of months and now wanted to update to the latest version of TWRP, ROM and didn't read the threads completely . First time that I'm so stupid.
Bootloader is unlocked, think I have the old bootloader. Had TWRP 2.8.7.0 installed and working. Flashed a 6.0 ROM and ended with bootloop...OK related to the old TWRP. So flashed within 2.8.7 the TWRP 3.0.2 ...
now it is only showing Huawei boot logo....neither fastboot nor TWRP is working anymore with (Vol+ & Power button). It just simply is showing the Huawei logo for some seconds and then restarting.
Any chance to unbrick it?

I'm not expert but if you can't get even into bootloader I think your phone is done.

Hitchi said:
anyone could help here?
It was my fault: didn't had the phone for a couple of months and now wanted to update to the latest version of TWRP, ROM and didn't read the threads completely . First time that I'm so stupid.
Bootloader is unlocked, think I have the old bootloader. Had TWRP 2.8.7.0 installed and working. Flashed a 6.0 ROM and ended with bootloop...OK related to the old TWRP. So flashed within 2.8.7 the TWRP 3.0.2 ...
now it is only showing Huawei boot logo....neither fastboot nor TWRP is working anymore with (Vol+ & Power button). It just simply is showing the Huawei logo for some seconds and then restarting.
Any chance to unbrick it?
Click to expand...
Click to collapse
Try booting with Vol- pressed while connected to PC

Even with Holding VOl- by connecting the PC the phone simply restarts to the Huawei logo and then restarts...

Is there still that bug where I'd have to wait for the screen to go off?
Or what does no touch at boot mean?

No, there isn't. The "notouchatboot" bug is solved..

AD2076 said:
No, there isn't. The "notouchatboot" bug is solved..
Click to expand...
Click to collapse
Great! Nice job

I cannot clean cache. Ext4 formatting takes forever. What am I doing wrong?

potworny said:
I cannot clean cache. Ext4 formatting takes forever. What am I doing wrong?
Click to expand...
Click to collapse
Actually it takes long, very long. Wait with patience

Unfortunately, after some time again, I have no touch at the start ;(
Wysłane z mojego Huawei P8 przy użyciu Tapatalka

motshek said:
Unfortunately, after some time again, I have no touch at the start ;(
Wysłane z mojego Huawei P8 przy użyciu Tapatalka
Click to expand...
Click to collapse
Did you flashed a new kernel? Kept vol+ button pressed while booting into recovery?

Ive loaded only new twrp. a week was ok and now I have to wait until the phone is in sleep recovery and then running touch

motshek said:
Ive loaded only new twrp. a week was ok and now I have to wait until the phone is in sleep recovery and then running touch
Click to expand...
Click to collapse
Sounds strange... I am using it with no issues.
Did you tried flashing twrp again?
Btw I am gonna upload a new build (just removes some unneeded stuff).

Not working for me either. No touch at boot at all but when the screen goes off, I can use it again! Just flashed today.

T1mb3 said:
Not working for me either. No touch at boot at all but when the screen goes off, I can use it again! Just flashed today.
Click to expand...
Click to collapse
Can you give me some more details?
Rom version?
Custom kernel?
Did you had a bugged twrp installed before flashing?
Did you keep Vol + pressed until splash screen at first recovery boot after flashing?
Thank you

AD2076 said:
Can you give me some more details?
Rom version?
Custom kernel?
Did you had a bugged twrp installed before flashing?
Did you keep Vol + pressed until splash screen at first recovery boot after flashing?
Thank you
Click to expand...
Click to collapse
I just updated to b382 with normal OTA. (I flashed the stock recovery as I previously had the older TWRP installed.)
I have never flashed custom kernels on this device.
The earlier TWRP (I quess 2.8, new_twrp) was working normally
Let me know if you need more info!

T1mb3 said:
I just updated to b382 with normal OTA. (I flashed the stock recovery as I previously had the older TWRP installed.)
I have never flashed custom kernels on this device.
The earlier TWRP (I quess 2.8, new_twrp) was working normally
Let me know if you need more info!
Click to expand...
Click to collapse
I have the very same version installed and no touch bug. The recovery is compiled with proper options to avoid it.
I am gonna upload a new build asap. I'll pm you to test it, can I?

Is it possible to use this TWRP to install original Huawei ROMs?

AD2076 said:
I have the very same version installed and no touch bug. The recovery is compiled with proper options to avoid it.
I am gonna upload a new build asap. I'll pm you to test it, can I?
Click to expand...
Click to collapse
Sure!

unlocked working bootloader but unable to flash anything...

houston we have a problem...
5 bucks for any good idea!
I have an old xt1068 (titan) that after an (official) update it becames a small brick... (it was stock, no modded bootloader or whatevere, just stock!)
today I decided to give it a chance but then only thing I reach is the bootloader
whatever thing (official retail firmware) I try to flash it doesn't work...
so I unlocked the bootloader with success to give a try a custom rom but suddenly I get a issue...
I can't install latest twrp (I tried also a couple of older ones), I can only boot trough (latest) twrp but whatever rom I install I get error7
I noticed that when it reboots the content (/sdcard /data and /system) is untouched even if from shell I can remount rw... it seems that I can delete but in reality I don't delete anything
I tried almost everything... if I try to re-stock upon reboot I reach the dead android robot
the device is an xt1068, bootloader 48.87 (30.06.2016), unlocked (status code 3)
any (good) ideas?

O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)

HiR3x said:
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
Click to expand...
Click to collapse
no way... I tried but nothing changes... it seems that partitions are read-only
anyway I'm not able to flash twrp (no error it just doesn't install), I can only boot twrp but again nothing changes, I tried soon after booting twrp to gain root trought supersu/magisk, all works without error but upon reboot partitions aren't touched at all

I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd

I am glad to hear that it helped you to resolve your problem
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video

mandar91 said:
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
Click to expand...
Click to collapse
Already commented a liked.

ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost

How come!
How can it happen. It is Moto G 2?
suiller said:
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
Click to expand...
Click to collapse

ni6hant said:
How can it happen. It is Moto G 2?
Click to expand...
Click to collapse
this is what I see from bootloader...