[DEV]Alcatel Pixi 4 (6") PORT CM12.1 / ROOT / TWRP

Search This thread
By:
Advanced…
lucas.lop

lucas.lop

Member
Oct 22, 2010
16
12
Help me!!! I don't know what's happened...

My internal memory is 4GB only!!!!

And I don't know what I do. I do a wipe from TWRP, but, not change...

Any idea?
 
  • Like
Reactions: kasaguz_027
poppm

poppm

Member
Nov 5, 2016
9
5
36
www.gilde-wolfsrain.de
Recovery bootloop (semi brick) [PIXI 4 (6) 8050D]

Hi there,
i followed the instructions from the first post of this thread. Just a little log for overview:

Enable USB-debugging and OEM-unlock-possible in the developer erea of my phone --> OK
Restart via ADB to bootloader mode --> OK
Unlock bootloader with "fastboot oem unlock" and tap on the vol+ key --> OK
Flash "fastboot flash recovery TWRP_3.0.0.2_Kirito9@Mod.By_Kevios12_v2.img" --> OK
Code: 
target reported max download size of 134217728 bytes
sending 'recovery' (13432 KB)...
OKAY [  0.391s]
writing 'recovery'...
OKAY [  0.884s]
finished. total time: 1.276s
Now if i force reboot with vol+ and the power key and select recovery it loops like...
Logo-->Black-->TWRP Logo-->TWRP Errors-->Black-->Again...
It's impossible to input anything

The Log entries are:
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details. . .
Failed to mount '/data' (invalid argument)
. . . done
Unable to mount /storage
Failed to mount '/data' (invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands.
Formating Cache using make_ext4fs. . .
Failed to mount '/data' (invalid argument)
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.

I've found solutions that the crypto problem is about left over files in the userdata partition by some devices.
To solve this problem try "fastboot format userdata" ends with an error message:
D:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 838860800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204800
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.009s
Click to expand...
Click to collapse
Now I've no more ideas what can i do.
please help me (i hope i did'nt forgot anything)

EDIT: Problem SOLVED by Kirito9 via PM.
 
Last edited:
  • Like
Reactions: kasaguz_027
G

geo2689

New member
Nov 9, 2016
3
1
poppm said:
Hi there,
i followed the instructions from the first post of this thread. Just a little log for overview:

Enable USB-debugging and OEM-unlock-possible in the developer erea of my phone --> OK
Restart via ADB to bootloader mode --> OK
Unlock bootloader with "fastboot oem unlock" and tap on the vol+ key --> OK
Flash "fastboot flash recovery TWRP_3.0.0.2_Kirito9@Mod.By_Kevios12_v2.img" --> OK
Code: 
target reported max download size of 134217728 bytes
sending 'recovery' (13432 KB)...
OKAY [  0.391s]
writing 'recovery'...
OKAY [  0.884s]
finished. total time: 1.276s
Now if i force reboot with vol+ and the power key and select recovery it loops like...
Logo-->Black-->TWRP Logo-->TWRP Errors-->Black-->Again...
It's impossible to input anything

The Log entries are:
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details. . .
Failed to mount '/data' (invalid argument)
. . . done
Unable to mount /storage
Failed to mount '/data' (invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands.
Formating Cache using make_ext4fs. . .
Failed to mount '/data' (invalid argument)
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.

I've found solutions that the crypto problem is about left over files in the userdata partition by some devices.
To solve this problem try "fastboot format userdata" ends with an error message:
Now I've no more ideas what can i do.
please help me (i hope i did'nt forgot anything)

EDIT: Problem SOLVED by Kirito9 via PM.
Click to expand...
Click to collapse

Hi! May I know how you solved this problem? I'm currently experiencing the same thing with my phone now. :(
 
  • Like
Reactions: kasaguz_027
kirito9

kirito9

Inactive Recognized Contributor
Oct 30, 2013
3,127
1,367
  • Like
Reactions: josgarr, Boombastical, kasaguz_027 and 2 others
G

geo2689

New member
Nov 9, 2016
3
1
Hi again! Just wanna say Thank you so much for the quick response. I had been searching the whole day on how to solve this problem and it's working now.:good:
 
S

svn.wieg

Member
Nov 7, 2016
15
2
Couldnt open the bootloader....

If I type in cmd

"adb reboot bootloader" I get the error - Error: device (null) bot found

I had installed adb drivers both. At first the new one - and cause it doesnt work I tried the older one.
I had tried to switch the usb ports and tried another usb cable.

adb kill-server -> *server is not running*
adb start-server -> daemon not running. started it now on port 5037
daemon started succesfully -
adb devices -> list of devices attached -> but empty

Fastboot OEM Unlock -> wating for device -> since 50 minutes
What could it be?



Thanks
 
Last edited:
poppm

poppm

Member
Nov 5, 2016
9
5
36
www.gilde-wolfsrain.de
svn.wieg said:
If I type in cmd

"adb reboot bootloader" I get the error - Error: device (null) bot found

I had installed adb drivers both. At first the new one - and cause it doesnt work I tried the older one.
I had tried to switch the usb ports and tried another usb cable.

adb kill-server -> *server is not running*
adb start-server -> daemon not running. started it now on port 5037
daemon started succesfully -
adb devices -> list of devices attached -> but empty

Fastboot OEM Unlock -> wating for device -> since 50 minutes
What could it be?

Thanks
Click to expand...
Click to collapse

Are you sure that your device is started in fastboot-mode?
 
  • Like
Reactions: kasaguz_027
S

svn.wieg

Member
Nov 7, 2016
15
2
I go in the pixi 4 revovery mode with vol+ and power and switch to fastboot an press power for ok.
And then it shows fastboot mode but nothing happens
 
S

svn.wieg

Member
Nov 7, 2016
15
2
Nothing worked. A little bit strange. Is rooted almost 20 phones succesfully, but the pixi 4 doesnt work immediatly.
 
poppm

poppm

Member
Nov 5, 2016
9
5
36
www.gilde-wolfsrain.de
Strange is the right word for this situation. I sounds like a problem with communication between your phone and work station. What OS do your work station have? Windows or linux based?
 
kirito9

kirito9

Inactive Recognized Contributor
Oct 30, 2013
3,127
1,367
svn.wieg said:
Nothing worked. A little bit strange. Is rooted almost 20 phones succesfully, but the pixi 4 doesnt work immediatly.
Click to expand...
Click to collapse

I don't think you have the correct adb drivers installed or they got corrupted somehow. Uninstall and install again, this happened to me as well on Win 10 but not sure what you're running. You can use universal adb installer to get the correct drivers.
 
S

svn.wieg

Member
Nov 7, 2016
15
2
Im on win7.
So where can I find some uncorrupted drivers?
I dl them 4 times on different pages.
I also couldnt make a regular Hard reset or Start the Recovery which is installed.
 
poppm

poppm

Member
Nov 5, 2016
9
5
36
www.gilde-wolfsrain.de
svn.wieg said:
Im on win7.
So where can I find some uncorrupted drivers?
I dl them 4 times on different pages.
I also couldnt make a regular Hard reset or Start the Recovery which is installed.
Click to expand...
Click to collapse

On the alcatel homepage there you can download mobile upgrade S 4.6.0 for installing the correct drivers.
just click support and type software update. then in the left menu select software upgrade and look for mobile upgrade s 4.6.0 or minimu 4.4.7

EDIT: Do windows make a sound when you connect your phone in fastboot-mode?
 
Last edited:
You must log in or register to reply here.

Similar threads

kirito9
Alcatel One Touch Pixi 3 Thread [ROOT][RECOVERY][ROMS]
Replies
3K
Views
1M
parrots_
parrots_
kirito9
Alcatel One Touch Pixi 4 - [GENERAL][ROOT][RECOVERY]
Replies
3K
Views
920K
Msi_laptop
Msi_laptop
Unjustified Dev
[GUIDE] New Root Method for LG Devices
Replies
1K
Views
1M
Azaze666
Azaze666
CatZephyr
Huawei Honor Holly [Hol-U19] || All-in-One || ROOT, Recovery & Devlopment Discussion
Replies
2K
Views
986K
M
mrozilla
C
[GUIDE] How to enter developer mode on 2017 Honda Civic (and now root & install apps)
Replies
3K
Views
892K
mvmnts666
mvmnts666

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 7
    kevios12
    kevios12
    Warning! I doesnt have this Phone anymore since years. You DO this on your own RISK! - DISCOUNTINOUD!

    cyanogenmod-12-1-rom.jpg


    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.

    PHP: 
    #include
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review.

    DISCLAIMER: Rooting your Phone and using a Custom Recovery and ROM's have risks and may result brick your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
    Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
    Make sure that whatever you do, you are doing it at your own responsibility.

    :good::highfive::cool:

    Requirements:

    Bootloader Unlock:

    1. Install Drivers for ADB / Fastboot / Preloader
      Download Fastboot / ADB Files
      Backup your Contacts, etc. Super Backup
      Goto Settings > Info > Tap on Build....
      GoTo Settings > Developer option > USB Debugging & OEM Unlock tick it
      Plugin your Phone to PC , make sure USB-Debugging enabled
      Type in CMD : ,,adb reboot bootloader"
      Phone Reboot, Fastboot driver install runs...wait
      Type in CMD: ,,Fastboot OEM Unlock" - WARNING ALL DATA LOOSE!
      Follow screen on Phone, Phone reboot, recovery Wiping Data, if doesn't work try imeadly.

    Recovery:

    1. Download Recovery from Here
      Reboot to Bootloader / Fastboot
      Plugin the Phone to PC
      If Connected then Type in CMD: ,,fastboot flash recovery yourimagename.img
      Reboot the Phone with Volume - / + and Power Button
      Boot in Bootloader, select Recovery, entering with Power Button
      !!!Backup your System!!!

    Root:

    • [1]Option > Use KingRoot App
      [2]Option > Download SuperSU.zip from Chainfire >Place in SD-Card > Reboot Recovery (adb reboot recovery or manuell) > Install ZIP > Reboot, if Bootloop, Restore System, Try Option 1. if not install SuperSU.apk from PlayStore.

    ROM:
    logo.png

    2empl6h.jpg


    CM12.1 PORT By ME!

    Screenshots:
    • See Attachment.

    INSTRUCTION:

    • When you comming up from another ROM / STOCK do you need first Unlock Bootloader , Flash TWRP (above steps)
    • Download >> Here << CM12.1.ZIP, CAPPS >> HERE << , GAPPS ARM 5.1 LP >> HERE <<
    • Push the Files to SD-Card / Copy to SD-Card
    • Reboot to Recovery
    • Make a Factory Reset / Wipe Data / Cache / Dalvik
    • Goto Install > Choose .ZIP Files & Flash all Files.
    • Reboot into System , please be patient, Android Optimiz Apps.

    What is working:
    • All working, but See Not working, also SIM,WiFi,Bluetooth, Camera,Sound,... working
    Not Working:
    • FM Radio
    • Internal Storage as forever Default, but you can Symlink.
    • report me what is not Work, i look into.


    Contributors:
    @kirito9 Thanks for Port TWRP
    @DarkShadeX Thanks for Testing Recovery
    @kevios12 Modified Recovery ! PORT CM12.1
    @CyanogenMod
    @teamwin - for Recovery

    Thanks to other Users for Help, when i forgot a people , PM!

    Version Information
    Rom OS Version: 5.1.x Lollipop
    Based ON: Cyanogenmod
    Status: Stable
    Kernel Source: Using Kernel from Stock ROM

    Created 2016-09-06
    Last Updated 2016-09-17
    View
    5
    kirito9
    kirito9
    geo2689 said:
    Hi! May I know how you solved this problem? I'm currently experiencing the same thing with my phone now. :(
    Click to expand...
    Click to collapse

    Flash this recovery- https://www.androidfilehost.com/?fid=529152257862677997

    It's CTR 5.7.

    ---------- Post added at 11:05 AM ---------- Previous post was at 11:04 AM ----------


    @kevios12 Update your post with this new recovery, CTR 5.7- https://www.androidfilehost.com/?fid=529152257862677997
    View
    3
    kirito9
    kirito9
    kasaguz_027 said:
    pixi 4 (6) 3G version?
    8050g?
    Click to expand...
    Click to collapse

    If it's 5.1 then yeah.
    View
    2
    kevios12
    kevios12
    this one phone only no other in other thread all pixis in there :D
    View
    2
    lucas.lop
    lucas.lop
    Hi friends! I solve my problem!!!

    The internal memory is encrypted. So, I have wipe the data, in the second option on the TWRP, that option were we type "yes" to confirm. Than I reboot the recovery, and I got it to flash the ROM.

    It might be better to highlight this in the tutorial.

    Bye!
    View

New posts