Database Users

Lava Pixel v1 no os installed in twrp

Hi,
i tried to flash the marshmallow update and accidently erased all the data using twrp. now my mobile is showing no os in twrp and it is not booting.
1. tried to unlock bootloader using fastboot. failed.
2. tried to flash custom rom . failed because bootloader not unlocked.
now i am having only twrp. can anyone help me in this , its really urgent.
thanks.

Do u have any custom rom for pixel v1?

i cant find any custom rom
hi i searched all over the internet but i cant find any custom rom. Can anyone pls give me the link for any custom rom for lava pixel v1.
Thanks

flash the stock firmware with sp flash tool
s015,s019 are for white model & s103 is for gold model .
http://firmwarefile.com/lava-pixel-v1

flashtool not detecting my mobile
AC DC said:
flash the stock firmware with sp flash tool
s015,s019 are for white model & s103 is for gold model .
http://firmwarefile.com/lava-pixel-v1
Click to expand...
Click to collapse
sp flashtool is not detecting my device and in sp flashtool the download is not starting. but fastboot can detect my device.
Importatn: my device has no OS, and my bootloader is locked.

pmkscorpio said:
sp flashtool is not detecting my device and in sp flashtool the download is not starting. but fastboot can detect my device.
Importatn: my device has no OS, and my bootloader is locked.
Click to expand...
Click to collapse
but if you have twrp you can directly install the zip from sdcard

thread link
AC DC said:
but if you have twrp you can directly install the zip from sdcard ,check this thread
Click to expand...
Click to collapse
where is the thread link?

pmkscorpio said:
where is the thread link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/lav...-to-upgrade-to-marshmallow-bypassing-t3315319

Issue
AC DC said:
http://forum.xda-developers.com/lav...-to-upgrade-to-marshmallow-bypassing-t3315319
Click to expand...
Click to collapse
I used SP tool to flash the firmware (Link given by @AC_DC in another thread).
When I select the option 'firmware upgrade' it says error proinfo: Failed to get PMT info. The it says 'select option to format and download'. After doing that, after the 'download OK' popup, I try to boot up the phone and nothing. It isn't booting up. (white variant of pixel v1)
My phone is literally dead, only the preloader is working. I also tried formatting and then trying it again, but nothing works.
Please direct me to what I should do now. Any help highly appreciated :good:

First search in google unlock bootloader

Hello your problem is solve.....?

This method is legit and works 100%
Hey all
U said that u still have TWRP. So go to recovery, clear data, and in clear system partitions, select everything and clear.
Then follow the following steps -
1) Turn off yr V1 and get it into fastboot mode and connect it to yr PC( make sure u've adb installed. Link - https://androiddatahost.com/bnjkh)
2) download : https://firmwarefile.com/lava-pixel-v1. Place the 'boot' and 'system' files from the downloaded firmware to the folder where u have adb installed.
3) Open CMD( A .exe called 'cmd here' is already present in the file of adb, so run it as administrator)
4) Type -
Code:
fastboot flash boot boot.img
. Give it some time.
5) Type -
Code:
fastboot flash system system.img
. Give it time (It takes 4-5mins, so dont panic)
6) Type -
Code:
fastboot reboot
THIS METHOD WORKED FOR ME MANY TIMES.
If it helped you, click the :good: thanks button

Unlock Bootload , Install TWRP , Root : Redmi Note 3[Snapdragon] 7.2.3

Its been inspired by Sudeep Duhoon Thread , Thank him if possible . Except the rooting part everything is preety much same as Sudeep Duhoon did.
I just found out you could 7.2.3 much easily Root the device rather than editing scripts and all of the stuff which i didn't get from his thread.[No offense sir]
Downloads :
1. Minimal Adb Tool
2. MiFlash_2016.03.30.exe
3. Fastboot 7.2.3 Rom
4. Unlocked EMMC or check the attachment.
5. 7.2.3 PATCHED BOOT IMAGE
Unlocking Bootloader :
​1 . Connect your Phone to Computer in USB DEBUG and OEM UNLOCK mode to the computer. [Both of these settings are turned on from developer option.]
2. In ADB check if your device is successfully connected using "adb devices" command .
3. NOW , Reboot the phone into EDL mode using this command "adb reboot edl" .
4. Now make sure you're device is connected in "Qualccomm HS-USB QLoader 9008" , if yes continue .
If the device is connected in "Qualcomm HS-USB Diagnostics 900E" Start it from step 1 again.
5. DOWNLOAD 7.2.3 fastboot Rom . Extract the rom.
Download, Extract unlocked_emmc_appsboot.mbn. Rename it to "emmc_appsboot.mbn" And move it inside the extracted ROM FOLDER.
6. Now Start the MI Flash Tool and Browse to the Location Where you have Extracted the Fastboot ROM
7. Go to Advanced and Select:
Flash Programmer, Raw XML File and Patch XML File
from the Fastboot ROM\Images folder.
8. Close the window and click on refresh , Your device with certain COM# will appear. Just click on Flash.
Wait until its successful .
9. Once it is successful , Hard Boot your phone to fastboot using POWER DOWN + POWER ON buttons on your phone.
10. Now in command prompt type "fastboot oem device-info" , you'll see the DEVICE UNLOCKED : FALSE
11. Now Enter the following command "fastboot oem unlock-go" . Your device must be unlocked , to confirm enter the previous[step 9] command again.
YOUR BOOTLOADER IS UNLOCKED NOW
FLASHING TWRP :
​1. Move the twrp image in minimal adb folder. Rename the twrp image to twrp.img
2. Enter the command "fastboot flash recovery twrp.img"
TWRP HAS BEEN SUCCESSFULLY Installed.
P.S : To boot into twrp : volume up + power on . But it might take 2-3 tries to boot into TWRP . [ I don't yet know why this happens .]
ROOTING :
​1. Move SUPER SU and PATCHED BOOT IMAGE into your mobile.
2. Install Super Su.
3. Install Boot Image, Dont forget to select install image and boot partition while installing.
4. You've SUCCESFULLY ROOTED your device .
P.S : PLEASE TRY IT AT YOUR OWN RISK.

Emmc rar does not get extracted... I think the archive is corrupt... Please check onto that
Sent from my Redmi Note 3 using Tapatalk

kirkirehani93 said:
Emmc rar does not get extracted... I think the archive is corrupt... Please check onto that
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
rar file is just fine , anyway i have uploaded a zip file in the attachment . please check.

reply fast
if i m right... i have to put supersu and boot.img to phone fefore flashing twrp. bcoz after flashing twrp if i reboot to system, phone will not boot and may be bricked...plzzz reply

vivekjha said:
if i m right... i have to put supersu and boot.img to phone fefore flashing twrp. bcoz after flashing twrp if i reboot to system, phone will not boot and may be bricked...plzzz reply
Click to expand...
Click to collapse
No no. It doesn't matter when you put it in. And your after flashing twrp you can directly boot into TWRP and then move the files into mobile.
P.S : While in recovery , you can always copy files in to your mobile.

What if bootloader unlocked officially? Start from "Flashing TWRP" section?

any 1 tried this
any one tried this succesfully plzzz reply

Error during flashing with MiFlash
Got this error during Flashing process:
Status: Not enough storage space is available to process this command.(0x80070008; Max buffer sector is 256)
What should I do? My device does not boot...

anirudh281998 said:
Got this error during Flashing process:
Status: Not enough storage space is available to process this command.(0x80070008; Max buffer sector is 256)
What should I do? My device does not boot...
Click to expand...
Click to collapse
Use Windows 64bit edition.
The flashing process will fail in Windows 32bit edition

will this work in RN3 MTK ???

Will this work on 7.2.5 ?

RedBux said:
will this work in RN3 MTK ???
Click to expand...
Click to collapse
No

Thri11 said:
Use Windows 64bit edition.
The flashing process will fail in Windows 32bit edition
Click to expand...
Click to collapse
Thank you.....i tried it on windows 64 bit and it worked.

I tried unlocking bootload. I got this error "The system cannot find the path specified. (0x80070003: Open Programmer c:...)"
What have I done wrong?
Edit: I deleted the file. Extract it again. Then I unlocked bootloader successfully.

will this void warrenty ?
and to flash miui china roms we need to edit the fastboot everytime ?

When I flash supersu my device won;t boot. Boots fine before though

Hi, I'm on MIUI 7.5.3, can I use 7.2.3 ROM as provided to unlock bootloader or I have to find a 7.5.3 one?

GitGudWolf said:
Hi, I'm on MIUI 7.5.3, can I use 7.2.3 ROM as provided to unlock bootloader or I have to find a 7.5.3 one?
Click to expand...
Click to collapse
I too would like to know the same.
Would this work on 7.5.3 or will I need to do something else

not working sir....
when perform fastboot oem unlock-go, result:
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s

UPDATE
SOLVED : "Enable OEM unlock" must be turn on in dev option.

[GUIDE] Fix bricked ZE550ML/ZE551ML (USB logo) and install Marshmallow

EDIT3 15/08/2018 - Some links broke. I found a better way to get the files: go to this thread (RAW firmware collection) by RealYoti here : https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
All the files are here and they will never expire
In case of problem I still have the files on my computer, maybe one day I will upload them myself on my web server
EDIT2 07/06/2017 - I updated links. + INFO: My ZE550ML phone bricked again, but this time with no USB logo and no vibration at boot. The only tutorial that worked for me is the one from Tech YouTubers channel (click to go to their YouTube channel). Please check their tutorials, in case they made a new one. Try multiple tutorials, for me only an older one worked: this one! (during the video tutorial, I was somehow blocked after flashing img files: black screen. But, I managed to run my own guide again, and this time it worked! The video says to flash ZE551ML xFSTK file on ZE550ML device, and flash ZE550ML xFSTK file on ZE551ML device. It allowed me to boot my device on fastboot but it prevented me to boot Android after flashing the correct ZE550ML img, so I had to flash, normally without reversing files, xFSTK ZE550ML config on my ZE550ML to make it work, then use my guide. good luck You can also try directly my "standard" tutorial below, or trying it after trying the Tech YouTuber's one, hoping finally you'll unbrick your device
EDIT 03/09/2016: Updated RAW links, taken from amtech.vn. and new ZIP files from ASUS.com
Hello, just after solving my problem I wrote a guide of everything I did to unbrick my ZenFone 2 ZE550ML (bricked after installing OTA update for Marshmallow Beta).
This is a "duplicate" of my last post on this thread : http://forum.xda-developers.com/showthread.php?t=3405331
because I want to help people who are trying to unbrick their ZenFone 2 ZE550ML or ZE551ML
Here is a detailed guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with lost bootloader without losing any data or setting, everything like before bricking in my case (except settings of some non-system apps, can't figure out why) :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(WARNING : these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
(The whole guide is a "modified" version of this guide by Summit007s)
Step 1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (the inf file for the driver is Android\android_winusb.inf) (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0)
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots). => phone boots on fastboot
Step 2. Flash a lollipop ROM (or Marshmallow raw image from the raw fw collection but I did not test it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (NEW link to Asus Flash Tool 1.0.0.45),
UPDATE Some links broke so I suggest you to download the raw firmware from this thread: https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966, there are Marshmallow raw firmware so you can skip step 3. I havent tried myself for now.
flash a raw file (go download it from the raw collection) on ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
OR FOR A ZE551ML flash a raw file (NEW link to WW_ZE551ML_2.20.40.184_20160504.raw) on ZenFone 2 ZE551ML using Asus Flash Tool (Model: ZE551ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
don't restart the phone, just plug it back to your computer and reopen ASUS FLASH TOOL (notice serial number change in ASUS FLASH TOOL) and flash again with same settings but the new serial number (different from 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
If it did not work, then you can reboot the phone and try again
Step 3. Flash Marshmallow zip with adb sideload, if you didn't installed it with a raw at step 2
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (NEWEST official link to UL-Z008-WW-4.21.40.191-user.zip for ZE550ML / NEWEST official link to UL-Z00A-WW-4.21.40.223-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.191-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.223-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
If you want more details for each step, just ask in the comments! Don't forget to read the other guides linked in the steps (for example, the one for xFSTK)
Now pray, and your device SHOULD magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data (except, maybe, settings of some non-system apps), exactly like before you bricked it.
It worked for me, but with the right new files it should work perfectly for you...
I hope you'll appreciate this "googling" work

Thank you
Thank you for sharing this information dude.. This is a helpful one.. It will surely be of greater use soon..

Thanks man u saved my zenfone 2 ze550ml. I tried various tutorial and videos but things didnt work as old files for z008 didnt work. You got the right files and steps. Cheers and keep up the good work

Hopefully this puts an end to all new unbricking threads *thumbs up*

password doesnt work for the flash tool anymore?

if u face error in ASUS FLASH TOOL
faced error in ASUS FLASH TOOL.
so i followed this guide after step 1 of this post: http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
then phone rebooted normally with a running OS. then i flashed last official lollipop zip from asus website by copying it to phone root directory. After that i flashed again the latest official Android 6 zip from ASUS same way.
everything working fine now. thanks

quarterbreed said:
password doesnt work for the flash tool anymore?
Click to expand...
Click to collapse
Hello,
I just tried it again and I can confirm that www.asus-zenfone.com is the right password for the archive, as seen on the original website :
http://www.asus-zenfone.com/2015/12/download-asus-flashtool-10014-for-windows.html
Download the RAR on your computer and open it : your archive opener software will ask you for the password only if you want to extract file. You can still see the list of file without password

Currently stuck at the end of step 1. :crying: any recommendations? Uploaded a picture of where xFSTK says as an error.

deathmaker06 said:
Currently stuck at the end of step 1. :crying: any recommendations? Uploaded a picture of where xFSTK says as an error.
Click to expand...
Click to collapse
Hello,
Your phone is still not booting on fastboot? Make sure you set settings in xFSTK Downloaded (GP Flag override, see the pdf) and try again. Good luck

fanfan54 said:
Hello,
Your phone is still not booting on fastboot? Make sure you set settings in xFSTK Downloaded (GP Flag override, see the pdf) and try again. Good luck
Click to expand...
Click to collapse
Nope its still not, and I've already set the GP Flag override stated in the pdf.
Good thing I was planning on upgrading to the V20 soon.

deathmaker06 said:
Nope its still not, and I've already set the GP Flag override stated in the pdf.
Click to expand...
Click to collapse
Try > 0x80000807 < (4x0`s)gp over ride in box ending [CRC]

timbernot said:
Try > 0x80000807 < (4x0`s)gp over ride in box ending [CRC]
Click to expand...
Click to collapse
omfg I love you
That means the PDF could be wrong using five 0's. Might want to add that as an edit to step 1 for anyone else that may experience the samething.

deathmaker06 said:
omfg I love you
That means the PDF could be wrong using five 0's. Might want to add that as an edit to step 1 for anyone else that may experience the samething.
Click to expand...
Click to collapse
Theres vid tutorial in my signature thats shows this and also how to restore serial :good:

THANK YOU !
You can find the solution HERE :
http:// forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
http:// forum.xda-developers.com/zenfone2/general/unbrick-vid-tutorial-restore-serial-t3411064
http:// forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
Click to expand...
Click to collapse
What is worked for me :
1°) Using XFSTK > -- Do not hesitate to use another computer OR Reinstall only XFSTK (Change the Folder too) if you are "ATTEMPTING #20" / "errors encountered during download. aborting" / "firmware download completed. continuing to os" --- i had these msg then i shutdown the phone an plug it to his power for all the night then it worked at first try
Then you are on "Weird Flag" then BOOTLOADER with "123456789ABCD"
2°) Use Asus FlashTool with the RAW File (WIPE : NO)> DO NOT REBOOT THE PHONE After it says "RESULT : OKAY" on the Phone
-Close Asus FlashTools only (do not close the task - VIDEO : https:// bambuser.com/v/6355633)
-Relaunch Asus FlashTools
-UNPLUG the USB Cable then Plug it back directly
-Wait 10 sec -> You will have your serial number on Asus FlashTools
>>> Reuse your RAW File with Wipe Yes then it Works
I even use ADB Sideload to upgrade to MM
Thanks A LOT for bringing back to life my ZENFONE 2
-

Anyone have the RAW image for Marshmallow yet? Kind of old to keep flashing Lollipop first, only to sideload later.

Good Morning. My in AFT takes only 4 minutes until " erase data" and then he already restarts . What I do to show the correct serial . Thank you

Hrllo yesterday i update to android M now i have bricked ZE 550ml. Follow this guide im on fastboot screen and when flash raw file from lolipop because i didnt find marshmalow raw phone boot. But i cant get recovery.there is android with triangle says error. Now trying asus flash tool for about 40mins and on display sometimes say erase data flash rrcovery... But nothing happens. How to get rrvive phone and have recovery back and flash marshmallow again. Please help
Odesláno z mého LG-H815 pomocí Tapatalk

Step 3. Flash Marshmallow zip with adb sideload, if you didn't installed it with a raw at step 2
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (NEW official link to UL-Z008-WW-4.21.40.112-user.zip for ZE550ML / NEW official link to UL-Z00A-WW-4.21.40.134-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
adb devices (null)
Click to expand...
Click to collapse
Not work in my case with this recovery: twrp-3.0.2-0-Z00A.img

Man, i am so ****ing happy.. My phone wasn't available for 2 weeks and this was a very bad experience for me. I fixed it because of you. Thank you so so so much!

Stuck in the first step!
Hello, currently my ASUS Zenfone 2 is bricked because I tried flashing the released Android Marshmallow ROM on TWRP.
After 10 minutes of flashing my device abruptly shut down and now it can't even show anything on the screen when I turn it on (phone still buzzes but not even a dead android icon is shown--just dark unlit screen).
I followed your instructions and I got stuck in step 1 when trying to install the drivers using PowerShell. I was able to install the .inf from the folders "MTP" and "tethering" but the one in "android".
May I have some assistance to the next step gentlemen?
I believe because of this my computer could only detect my phone as the "Moorefield Device" for more than a second.
Thank you,
Tom

Installing twrp with locked bootloader

I found a way to install twrp on my mi max with locked bootloader using EDL mode.
NB! This will reformat the phone so you should take a backup if you got something you want to keep on the phone.
NB! DO THIS ON YOUR OWN RISK!!!
To get into EDL mode I followed thi guide:
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
I turned off the phone and pushed vol+and- and connected the usb to the PC.
Then I installed the qualcom drivers I found here:
http://xiaomitips.com/download/qualcomm-qdloader-usb-drivers/
In device manger update the drivers that has name QHSUSB_BULK when the phone is in EDL-mode with the quallcomm-drivers
The driver should be installed and you can see added in Ports as Qualcomm HS-USB
I downloaded a fastbootimage
http://bigota.d.miui.com/6.6.23/hydrogen_images_6.6.23_20160523.0000.23_6.0_cn_5ab5ac0aba.tgz
I also downladed twrp:
http://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-0-touch-recovery-t3388073
I used 7zip to unpack fastbootimage.
Inside I found the folder with images and a recovery.img file. I renamed twrp file to recovery.img and replaced the one in images.
I then used miflasher and flashed the fastbootimage using clean option.
The flasher I used: can be found here:
http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
On flasher program the device should be recognized as COMXX when the Qualcomm drivers.
If the device id is a hexnumber and not COM10 the flashing in EDL mode will not work.
After flashing I diconnected the phone from pc and rebooted into recovery "power and vol+"
Now I had TWRP and could wipe and install ROMS etc.
I installed the ROM I found here
https://xiaomi.eu/community/threads/6-6-23.32335/
This was a much better ROM than the china-rom

Nice... Did your bootloader get unlocked after you flashed the eu global ROM?

nijel8 said:
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
Click to expand...
Click to collapse
Its still locked, but as you got twrp it really doesn't matter

I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!

Survivor1990 said:
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Click to expand...
Click to collapse
You use the Miflasher when telephone is in EDL-mode. I used http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
I didn't pack the ROM again. I had to browse into the catalog with the flasher which has files like flash.all
I see no reason why a Cyanogenmod for max shouldn't work as long at you flash it with twrp

Okay I did not know about this third Tool. I will try it when I am at home in the evening. Thank you very much!!

My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working

tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)

same for me!

g_BonE said:
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
Click to expand...
Click to collapse
Did the flashing give you the developer version of miui?
I don't know if it has something to say. I had the oem unlock option set in developer section on settings.
Are you sure the phone stayed in EDL mode and not in Fastboot? A black screen with a little mi icon
Or that the recovery.img was really swapped with the twrp?
It worked on 2 phones I tried.

Survivor1990 said:
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
Click to expand...
Click to collapse
Doesn't look like it flash with EDL and qualcom drivers. Does it says device is a com port in the flasher utility?
I found this that might help. I had enabled usb debugging:
Be sure to Enable USB Debugging:-
Go to About phone > tap MIUI version at least 7 times to activate the Developer options. Go to Additional settings > Developer options > USB debugging > Enable it.
Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
USB Data cable from your set.
Battery is charged at least 50%.

Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.

Survivor1990 said:
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Click to expand...
Click to collapse
You need the qualcomm drivers
https://goo.gl/CPa5jd
To install the drivers follow this guide when connected in edl-mode:
http://en.miui.com/thread-235865-1-1.html
Follow point 5 and in point 6 use the drivers you have downloaded

There is no need to flash the entire partition set to install TWRP. It is enough to flash a single "recovery" partition using edited rawprogram0.xml, removing all partitions except "recovery" and either specifying TWRP image file name in "filename=" or renaming TWRP image file to "recovery.img".
patch0.xml must be edited too to remove all "<patch>" tags.
Additionally, flashing a modified "boot" image may be required.

I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!

Survivor1990 said:
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Click to expand...
Click to collapse
Thanks for det update, I added an URL to the flasher on the first post

After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB

alexecus said:
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk

iJohnny said:
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked. I thought the partitioning got corrupted after I flashed using EDL. Glad TWRP was able to provide a quick fix

I got this working on my Helium 64gb Mi Max.
Please note that the instructions above is for the 32gb Hydrogen Mi Max. What I did differently is to get the recovery.img out of a Helium image.

Update B181 to android 6.0

Hello
I have the p8 lite ALE-21FRAC530B181 with android version 5.0.1, and the EMUI is 3.1.1
I want to upgrade it to android 6.0 but when I start the installation, I have an error message right away. I used the file provided here : https://forum.xda-developers.com/p8lite/general/guide-huawei-p8-lite-downgrade-to-5-0-t3381013
and here : https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
So I tried to update to B188 first, but I had the same problem.
I unlocked the bootloader, so maybe the issue come from there. Also it is not simlock
any help will be welcome
Thanks

leo15411 said:
Hello
I have the p8 lite ALE-21FRAC530B181 with android version 5.0.1, and the EMUI is 3.1.1
I want to upgrade it to android 6.0 but when I start the installation, I have an error message right away. I used the file provided here : https://forum.xda-developers.com/p8lite/general/guide-huawei-p8-lite-downgrade-to-5-0-t3381013
and here : https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
So I tried to update to B188 first, but I had the same problem.
I unlocked the bootloader, so maybe the issue come from there. Also it is not simlock
any help will be welcome
Thanks
Click to expand...
Click to collapse
Try converting to Europe location or any other....I can't find any marshmallow update for your region

HaiderHady said:
Try converting to Europe location or any other....I can't find any marshmallow update for your region
Click to expand...
Click to collapse
okey but how can I do that ? And then what do I do?

leo15411 said:
okey but how can I do that ? And then what do I do?
Click to expand...
Click to collapse
Follow steps of converting to dual sim ?
Beware say bye bye to your data on cell phone.....Always good idea to backup

HaiderHady said:
Follow steps of converting to dual sim
Beware say bye bye to your data on cell phone.....Always good idea to backup
Click to expand...
Click to collapse
So according to this tuto https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994.
I have to unbricked the phone before convert into dual sim.
But when I launch minimal ADB and fastboot and enter this lines of code :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
I have the message "waiting for devices" but I have already installed hisuite so I should have all the driver installed. I unlock the bootloader too. When I go in fastboot mod, there is "phone unlock" written.
What can I do ?

leo15411 said:
So according to this tuto https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994.
I have to unbricked the phone before convert into dual sim.
But when I launch minimal ADB and fastboot and enter this lines of code :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
I have the message "waiting for devices" but I have already installed hisuite so I should have all the driver installed. I unlock the bootloader too. When I go in fastboot mod, there is "phone unlock" written.
What can I do ?
Click to expand...
Click to collapse
Your pc is not identifying your device as connected and hisuite doesn't come with fastboot drivers... Check device manager (of Windows Pc if you have)
And find FastBoot.2.0 driver and update it from Windows update

HaiderHady said:
Your pc is not identifying your device as connected and hisuite doesn't come with fastboot drivers... Check device manager (of Windows Pc if you have)
And find FastBoot.2.0 driver and update it from Windows update
Click to expand...
Click to collapse
ok so I have now all the drivers but there is still the message "waiting for device". Do I need to extract the image from a specific update.app ? Or is it just the procedure very long ?
thank you a lot for your help :good:

leo15411 said:
ok so I have now all the drivers but there is still the message "waiting for device". Do I need to extract the image from a specific update.app ? Or is it just the procedure very long ?
thank you a lot for your help :good:
Click to expand...
Click to collapse
You need to extract UpDate.App...four images CUST,SYSTEM,BOOT,RECOVERY and have your device in fastboot mode connected to your pc

HaiderHady said:
You need to extract UpDate.App...four images CUST,SYSTEM,BOOT,RECOVERY and have your device in fastboot mode connected to your pc
Click to expand...
Click to collapse
Yes I know that, and I have already tried.
My questions were: which UPDATE.app I must use for the extracion ? Does it matter ?
And, how long is the unbricking ? 10min, 30min, or several hours ?

leo15411 said:
Yes I know that, and I have already tried.
My questions were: which UPDATE.app I must use for the extracion ? Does it matter ?
And, how long is the unbricking ? 10min, 30min, or several hours ?
Click to expand...
Click to collapse
No it doesn't.....it took my really old pc total of 8 minutes

HaiderHady said:
No it doesn't.....it took my really old pc total of 8 minutes
Click to expand...
Click to collapse
well it is not working, I checked my devices manager and I attach a screenshot (it is in french...) with the detail of the driver. There is an exclamation point close to "android bootloader interface"

leo15411 said:
well it is not working, I checked my devices manager and I attach a screenshot (it is in french...) with the detail of the driver. There is an exclamation point close to "android bootloader interface"
Click to expand...
Click to collapse
Hmmm.....Try to uninstall this driver....(Both of them) connect your device again and you should get a notification of installing Fastboot2.0 driver...Install it...or let windows update install it and then check if it helps
And yes before uninstalling try to Update this android bootloader interfaces driver
Sent from my ALE-L21 using XDA Labs