Responses to “TWRP x32- ROM”

1. 

   11/05/2016
   

    

   mostachon1963 on 02/26/2017 @ 11:08 am

   no puedo instalarlo ninguna de las dos versiones

    

   Log in to reply.
2. 

   11/05/2016
   

    

   mostachon1963 on 02/26/2017 @ 1:01 pm

   consegui instalar el 32 bit como puedo cambiar a 64 bit

   Log in to reply.
3. 

   02/28/2017
   

    

   jmleal on 02/28/2017 @ 12:44 pm

   I can not download!

   Log in to reply.
4. 

   02/08/2017
   

    

   Fnando73 on 03/11/2017 @ 12:08 am

   thanks

   Log in to reply.
5. 

   03/02/2017
   

    

   jmartingg on 03/12/2017 @ 2:16 pm

   after flash tools, reboot phone by pressing power button and volumen up. select recovery mode, but phone reboot normally. no TWRP.

   I've tried it many times, with USB debugger, block OEm and always boot normal. No TWRP

   Log in to reply.
6. 

   03/17/2017
   

    

   MrPotatohead on 03/30/2017 @ 5:59 am

   I bought an X5 Max Pro recently, fully intending to install a custom recovery and root it (then get rid of all the crapware). I've only ever used Android rooted. But, like some of the guys here, I've had nothing but trouble trying to get TWRP installed. I can flash any full stock ROM using SP Flash Tool without problems (as long as it's 32-bit) so I know SP and the USB drivers are fine. I've unlocked the bootloader via developer options and 'fastboot oem unlock'. I can see it's unlocked with 'fastboot getvars all'. I've tried flashing the recovery both with SP and via 'fastboot flash recovery recovery.img'. It always completes successfully but, as jmartingg described, selecting recovery from the power+up menu simply boots the phone as normal. If I then 'adb reboot recovery' I get the "no command" screen which leads to the standard Alps recovery (after tapping the power button).

   Incidentally, after flashing an earlier 64-bit stock ROM, I ended up with invalid IMEI's then spent a couple of days trying to fix this problem with SN_Writer / SN_Write_Tool and Maui Meta… nothing worked (preloader connects, stuck at kernel connection). It was only after spotting teretzis1's comment about dialling *#4634# that I got a restored nvram and cell access again. Very grateful for that advice… perhaps it should be stickied somewhere?

   I'm not fully sure, but I believe these problem devices that some of us seem to have could be running a kernel that prevents the execution of a custom recovery, even when the bootloader is unlocked. It's got to be something in a partition that's not overwritten by a stock ROM flash, or we'd all be affected. The simplest way to know would be if some kind person with a device that can run TWRP dumped their whole flash and we byte-compare to find the differences. There's a simple mod to 'option.ini' in SP Flash to read back all partitions… just edit the line under '[ReadBack]' to: 'ShowByScatter=true' (where it was 'false') then do a read-back. It's probably best to avoid sharing anything personal, like ROM_3 (nvram) which contains IMEI's, among other things.

   I'm hopeful this is a problem that can be solved with a bit of collaboration. The device seems well built and could be really nice, if it could be properly set free. I like it, but I can't use it as it is (even running NoRoot Firewall).

   Anyone up for helping to fix this?

   Log in to reply.
   • 

     04/22/2016
     

      

     miota85 on 04/01/2017 @ 7:47 pm

     Has been imposible for me to flash the recovery. I have tried with flashtools and fastboot in a lot of ways but I have been able to do it. If somebody find out how to do it, please share how to do it. The point is that apparently you are able to flash it but, I don't konw why, it always come back to the stockrecovery.

     May a work around would be finding out the oem commands in fastboot. I have seen a tutorial to get them, but you have to be root: https://www.xda-developers.com.....tboot-commands/

      
7. 

   08/19/2016
   

    

   pikie on 04/01/2017 @ 4:16 pm

   please post new TWRP 3.1 X32

   Log in to reply.
8. 

   04/02/2017
   

    

   bebr0ke on 04/03/2017 @ 2:01 am

   hi guys,

    

   thanks so far.

   i re-flashed the stock rom and it works.

    

   i downloaded the sp flash tool v5.1.62.000 and this twrp version here.

    

   1. i turned off the phone

   2. started sp flash

   3. loaded the scatter file of the twrp version

   4. chose download only and checked recovery

   5. pressed download

   6. plugged in the phone

   7. waited until sp flash said ok

   8. unplugged phone

   9. started with volume up and power to enter the recovery

   10. chose recovery

    

   and nothing happened
    

   am i missing anything?
   what do i do wrong?

   Log in to reply.
   • 

     04/02/2017
     

      

     bebr0ke on 04/03/2017 @ 3:03 am

     I also used an older rom from november with this twrp

     and i still couldnt run this

      

     please test and install the latest stock rom and try to flash this rom

      

     thank you!
9. 

   03/17/2017
   

    

   MrPotatohead on 04/03/2017 @ 6:36 am

   miota85, you can find the fastboot commands by looking through 'lk.bin' in a stock ROM with a hex editor on your PC (or by doing a read-back of your phone and looking in ROM_6). Command text starts at 0x3C308 with 'getvar'. Not many commands implemented. But I noticed they have included 'flashing' so thought 'fastboot flashing unlock' might help. This is worth a read:

   https://source.android.com/sec.....ified-boot.html

   I tried 'fastboot flashing unlock'. It gave the same warning as 'fastboot oem unlock', erased the user partition as usual. TWRP flashes as normal but still won't run. 'fastboot getvar all' shows bootloader is unlocked.

   bebr0ke – this is exactly what I (and others here) have been doing, with the same result. Frustrating.

   It would be VERY helpful if someone who has TWRP installed and running could share a read-back of their flash. There must be some way to fix this problem.

   Log in to reply.
   • 

     04/22/2016
     

      

     miota85 on 04/03/2017 @ 10:07 pm

     I have been trying too with no success with fastboot flashing unlock and the other similar command that let you flash paritions of the bootloader (I don't remember exactly command right know but appears in the fastboot help).

     I have seen in some foros that when somebody has flashed an incorrect recovery compilation in their terminals they have provoke a bootloop. I am not sure if it is the problem, but that is what is happening here. Therefore, I tend to think that in the last versions of this phone the have made some hardware changes and this compilation of TWRP doesn't work in the new terminals. I have seen with AIDA64 app that my hardware is mt6735 and the platform is mt6737m (see attached pictures). I think that may be we should try recompiling TWRP with the specs of this terminal or compare with the ones this compilation works. But for real, I do not have any real lead for a work around.

     
10. 

    03/17/2017
    

     

    MrPotatohead on 04/04/2017 @ 2:01 am

    I hope there's not different hardware versions of this device. I don't think there can be because a stock ROM will flash the recovery partition, and that runs on devices that will run TWRP as well as ours that won't (yet?). I understand what you mean though. I've seen the boot-loops after flashing recovery then immediately trying to enter it. Only after booting the rest of the system is the recovery reset to the Alps version. It's like TWRP is being stopped from running because it's signed differently from the stock recovery. If it is some software that's stopping it, we need to see it. Only people that are able to run TWRP could help here.

    Could anyone (teretzis1 maybe?) please convey the problems some of us are having to the 4PDA forums? I'm assuming that's where the development work is coming from – apologies if I'm wrong. I wish I could speak Russian, but I don't.

    Log in to reply.