Related
Good evening!
I have a nexus 7 with 4.2.2 build and i rooted it at afternoon. Everything was okay, but i wanted to back to stock 4.2.2 without root.
I tried with the both toolkit and manually, but when my instalation process reach the sending 'system' <XXXXXX kb> part the bootloader freeze.
I tried manually with 4.2.2, 4.2.1, 4.1.2 but there is the same problem with all.
If anyone can understand my Professional english, please help... :S
gyroskucko73 said:
Good evening!
I have a nexus 7 with 4.2.2 build and i rooted it at afternoon. Everything was okay, but i wanted to back to stock 4.2.2 without root.
I tried with the both toolkit and manually, but when my instalation process reach the sending 'system' <XXXXXX kb> part the bootloader freeze.
I tried manually with 4.2.2, 4.2.1, 4.1.2 but there is the same problem with all.
If anyone can understand my Professional english, please help... :S
Click to expand...
Click to collapse
Hi, gyroskucko73...
Oh.. don't worry about your English ... it's fine...
------
You're not HARDBRICKED... just SOFTBRICKED.
If you can get your Nexus 7 into BOOTLOADER/FASTBOOT mode (from shutdown, VOL DOWN+POWERBUTTON)... there is ALWAYS a way out.
------
When I flash back to STOCK, I also have endless problems myself, with sending system.img/writing system...
I usually get it sorted eventually, by changing to a different USB port on my laptop. (Not all USB ports are born equally... apparently!).
-------
Make sure you're using the official ASUS USB cable that shipped with your Nexus 7 and change the USB ports you're connected to on your PC... and persist.
Eventually, system.img will go across.
Rgrds,
Ged.
Offer to buy
Hi, if your nexus7 stays bricked please get in touch as I may buy it off you for the screen and digitizer. At least this way we both kind of benefit - I have a cracked screen.
GedBlake said:
Hi, gyroskucko73...
Oh.. don't worry about your English ... it's fine...
------
You're not HARDBRICKED... just SOFTBRICKED.
If you can get your Nexus 7 into BOOTLOADER/FASTBOOT mode (from shutdown, VOL DOWN+POWERBUTTON)... there is ALWAYS a way out.
------
When I flash back to STOCK, I also have endless problems myself, with sending system.img/writing system...
I usually get it sorted eventually, by changing to a different USB port on my laptop. (Not all USB ports are born equally... apparently!).
-------
Make sure you're using the official ASUS USB cable that shipped with your Nexus 7 and change the USB ports you're connected to on your PC... and persist.
Eventually, system.img will go across.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks a lot... I changed the USB port and the everything has gone fine But i never thought that, the usb port is important
Hy Guys,
I have tryed to put the rom from Gionee Elife E7 on my Blu life pure XL. The installation occurs everything okay, but when i try to install the recovery, my phone reboot, and never more turn on again... I only can see the Gionee logo, but then shutdown after that. When i try to connect on the PC, just two drivers are showed to me:
-Gionee HS-USB Diagnostics (COM5)
-Qualcomm MMC Storage USB Device
I can enter in ADB mode, but i have no way to acess the internal storage...
Any help will be grateful...
sampadf said:
Hy Guys,
I have tryed to put the rom from Gionee Elife E7 on my Blu life pure XL. The installation occurs everything okay, but when i try to install the recovery, my phone reboot, and never more turn on again... I only can see the Gionee logo, but then shutdown after that. When i try to connect on the PC, just two drivers are showed to me:
-Gionee HS-USB Diagnostics (COM5)
-Qualcomm MMC Storage USB Device
I can enter in ADB mode, but i have no way to acess the internal storage...
Any help will be grateful...
Click to expand...
Click to collapse
when u installed the rom did the phone start up properly?
This look's bad man.
Try power on your phone then
Plugin into your computer.
Open adb then type adb devices
When your device is listed type adb reboot recovery
If IT doesn't boot in recovery mode then You should try flashing again the rom.
Something should work.
Sent from my E7 using Tapatalk
have you fixed it? perhaps i can help
if you've got fastboot (power + vol -)
you can fastboot (sort of like an adb) flash some system images and get your phone getting recognised by gnqc
you need :
ADB
boot.img from blu rom
system1.img from blu
right click on folder where adb and files are (they need to be on same folder for faster tipying)
write
fastboot flash system system1.img
fastboot boot boot.img
after that unplug phone, you need the drivers for blu, change cable from pc port and reconect to see if now it's recognized as a pure xl and check for the drivers.
It should install 2 com ports (hsusb, nmea) 1 adb, 1 modem and 1 storage
that is what i did to mine, hope it works on yours
dzamora said:
if you've got fastboot (power + vol -)
you can fastboot (sort of like an adb) flash some system images and get your phone getting recognised by gnqc
you need :
ADB
boot.img from blu rom
system1.img from blu
right click on folder where adb and files are (they need to be on same folder for faster tipying)
write
fastboot flash system system1.img
fastboot boot boot.img
after that unplug phone, you need the drivers for blu, change cable from pc port and reconect to see if now it's recognized as a pure xl and check for the drivers.
It should install 2 com ports (hsusb, nmea) 1 adb, 1 modem and 1 storage
that is what i did to mine, hope it works on yours
Click to expand...
Click to collapse
this helped me but now i have another problem phone starts up then reboots sometimes it reboots in the middle of starting up i can get into stock recovery but i have no idea what to do now
jetboss said:
this helped me but now i have another problem phone starts up then reboots sometimes it reboots in the middle of starting up i can get into stock recovery but i have no idea what to do now
Click to expand...
Click to collapse
Ok now, you can use GNQC and flash the rom and that will completely restore your phone
NOw if only i could find the blu rom for a 16gb blu
dzamora said:
Ok now, you can use GNQC and flash the rom and that will completely restore your phone
NOw if only i could find the blu rom for a 16gb blu
Click to expand...
Click to collapse
funny thing is i did that and thats whats causing this boot loop i got into recovery after reset and still nothing
is there anything i can push using adb to solve this ?
jetboss said:
funny thing is i did that and thats whats causing this boot loop i got into recovery after reset and still nothing
is there anything i can push using adb to solve this ?
Click to expand...
Click to collapse
perhaps a stock recovery.img can help
dzamora said:
perhaps a stock recovery.img can help
Click to expand...
Click to collapse
ok well im going to try pushing the elife 7 stock recovery and see what happens
tried that all it says is installation aborted .....
You have to to try this,that is how i have unbricked mine today.
power off your phone.
prepare your gnqc so you only have to press download when needed.
power on your phone then conect fast to PC ,then press download.
If IT doesen't leț You ,pres again and just try to see If IT works in different situations.
is a long shot but this is how i unbricked mine today.
fastboot doesen't work on this device,so You can't push anithing. i don't know hou this people are doing that.
If this metod doesn't work You shold try format system and data via adb . and after that gnqc should work.
Muresan01 said:
You have to to try this,that is how i have unbricked mine today.
power off your phone.
prepare your gnqc so you only have to press download when needed.
power on your phone then conect fast to PC ,then press download.
If IT doesen't leț You ,pres again and just try to see If IT works in different situations.
is a long shot but this is how i unbricked mine today.
fastboot doesen't work on this device,so You can't push anithing. i don't know hou this people are doing that.
If this metod doesn't work You shold try format system and data via adb . and after that gnqc should work.
Click to expand...
Click to collapse
He can't use GNQC because his phone's drivers arent insatlled, gionee blocks com ports, and fastboot does work on this device, you just got to flash it, i've been using it several times
A thing to notice is when you want to acces phone storage when phone is bricked You have to poweroff your phone and keep pressing power and volume+ untill some errors start appear in windows.
then You have acces to phone memory and You can paste anithing for later flash with recovery. You must Be very carefull not to format partition when asked !!!!!!
i have bricked my gionee 32 gb several times and always been albe to restore it so,no need to panic,some method should work for You too ,just have to find the right one.
And also,my phone is a rebrand of gionee from Romania,called Allview x1 xTreme,just like life pure Xl and i haven't encountered any problem with usb drivers, just used the one gionee provided. So this mai Be the case for You, i hope i am not wrong with this one.
Com ports are only closed in android 4.4 kitkat so If he didn't update he should Be able to use gnqc.
also You must observe that phone is recognised differently by windows deppending in wich state your phone is. powered off,recovery,or on bootloop. So that's why o have said that gnqc may work but You have to find that state when he is recognised the way that gnqc wants.
Sorry for long post i Hope those observations will help you.
Sent from my E7 using Tapatalk
I finally got it to work using the phone right now to send this message
jetboss said:
I finally got it to work using the phone right now to send this message
Click to expand...
Click to collapse
Got a couple questions would appreciate if u could help.
1. How did u root the blu xl i have both the 16g and 32g
2. Did u install custom recovery in it?
3. Links to downloads plz ...
Thanks in advance
Sent from my SM-G900H using XDA Free mobile app
noblelinux said:
Got a couple questions would appreciate if u could help.
1. How did u root the blu xl i have both the 16g and 32g
2. Did u install custom recovery in it?
3. Links to downloads plz ...
Thanks in advance
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
I can give you some info on root and recovery, im also hoping for someone to be able to extract the 16blu life pure xl rom since the only one is for 32 gb
for root you can just use Vroot and then after installinh busybox and supersu you may erase it, for the recovery i've got the files just send me a pm and ill mail you the link
dzamora said:
I can give you some info on root and recovery, im also hoping for someone to be able to extract the 16blu life pure xl rom since the only one is for 32 gb
for root you can just use Vroot and then after installinh busybox and supersu you may erase it, for the recovery i've got the files just send me a pm and ill mail you the link
Click to expand...
Click to collapse
I sent u a pm hit me bak and ill help u with the 16gb pure xl
Sent from my SM-G900H using XDA Free mobile app
Came bak to chek if any reply i broke both my screens on the blu life pure xl 16g amd 32 gb im now on galaxy s5 but still im gonna replace the screens and use the phones for something idk most likely android dev practice
I just need info on how to extract the rom from the blu
Thanks in advanced
Sent from my SM-G900H
Where files link to download?
jetboss said:
I finally got it to work using the phone right now to send this message
Click to expand...
Click to collapse
Hi can you tell me how did your phone started back, i am also stuck on reboots , recovery is working fine , any OS/ ROM is giving me reboots all the time..please help
honestly it was a long time ago and i cannot remember what i did except it was a windows xp pc software wouldnt work on 7 and i used stock rom not the one from blu
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Different reactions
Hi,
My device could still boot on fastboot mode, and flashes successfully through it on MiFlash Beta. However, the device remains stuck on Mi logo. I've already tested flashing on EDL mode apparently successfully, with the same results. I've flashed TWRP, but the device don't enter recovery mode. What can I do? Any suggestion will be welcome.
benzersizadam said:
Many thanks for this thread, I stuck on my mi max with no reaction at anything, I read more than 100 threads, I tried testpoint, DFC (deep flash cable), click inside usb terminal to pc, windows 8, 7 10, 32 bits, 64 bits, programms like qfil (qpst), flasher tools for other phones and nothing, before with other apps at first second gives me error "can not read from port COM...", and now at least advance to 5 seconds with same error, I need to know it is neccesary too disconnect, remove two plastic cables down where places the battery
Click to expand...
Click to collapse
Working also with Hydrogen. Thanks.
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
coffee-turtle said:
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
Click to expand...
Click to collapse
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
SubwayChamp said:
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
Click to expand...
Click to collapse
Hi @SubwayChamp Everything I did was in the post and video from above in the first post by benz....
His instructions were perfect along with the youtube video. It's tricky, true, but with patience you can go through the steps and get your device running again. I was so glad that @Qulox gave me this link to this thread.
As you go through the steps, if you get stuck, we can try to give you advice.
This works for Hydrogen as well.
Many thanks
I have two dead mi max. One 128gb helium and one 32gb hydrogen.
128gb helium is completely lifeless. No charging led, no vibrations, no fastboot mode. Though i could bring it up to edl mode showing right qualcomm device in device manager. I tried flashing stock rom as mentioned in this guide which rather went successful without giving any error, even while battery connector was removed.
But mobile is still in same lifeless condition. Other than flashing process going through, it didnt make any difference. Dont know whats wrong. Also i didnt have to use two miflash versions as mentioned in steps as flashing process didnt give any error.
32gb hydrogen, boots up in flashboot mode, shows charging led, mi logo even edl model worked without any issue. It even boots up, but gives error of encryption unsuccessful asking me to reset device. I tried factory reseting it. Tried flashing twrp and wiping, formatting data, changing file system to all formats like fat, f2fs, ext1, ext2, ext3, ext4. Tried flashing crdoid and RR based on orea. Nothing working.
With twrp it keeps bootlooping showing mi logo. And with stock rom, recovery shows up encryption error. Followed procedure mentioned in this guide as well.
Is there anything am i missing or can do? Btw, bootloader is locked for both the devices. I could flash twrp referring another guide which suggested to replace stock recovery in rom files/ folder and flashing it like stock rom through miflash tool.
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
cobben said:
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
Click to expand...
Click to collapse
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Hello,
trying with both Helium & Hydrogen. Still on error like say these logs.
log#1
Code:
[0,02 COM7]:[COM7]:start flash.
[0,02 COM7]:received hello packet
[0,02 COM7]:can not found programmer file.
log#2
Code:
[0,00 COM7]:[COM7]:start flash.
[2,03 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[4,56 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,11 COM7]:try to reset status.
[7,13 COM7]:Switch mode back
[7,13 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,14 COM7]:Riferimento a un oggetto non impostato su un'istanza di oggetto.
Hope anyone can help me. What's my wrong following the guide.
Thanks
harpy.eagle said:
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Click to expand...
Click to collapse
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
rizkhan77 said:
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Click to expand...
Click to collapse
This is the video of Test Point https://youtu.be/SqcVY8IWkZI
benzersizadam said:
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Click to expand...
Click to collapse
hi, could someone share with me the miflash beta? I can download the rest but I cannot download the beta one.
thanks
Wanted to say thank you was able to recover my mi max 64gb unit.
Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.
hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
bro do u find solutions for this
I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!
jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.
Hello ,
Yesterday my phone was at 5% so I wanted tot charge it and it did but only not with the original Leeco charger and cable but with a normal charger micro usb with a mico usb to USB C adapter and it was showing that it was charging . But when I came back 10 minutes or so my phone was stuck in a bootloop and I never had a problem with the phone and I was running a LineageOS 15.1 rom.
My Le Pro 3 X720 is stuck in a loop and I can only get to Fastboot mode.
When i try to go to recovery mode (TWRP) it shows Recovery but after a few seconds it is trying to boot but then it restarts again.
What i tried is to flash a new version of TWRP but after that it is still in a loop and not going to twrp.
I know of the QFIL MODE but I don't want to lose my data.
Can someone please help me ?
Thanks in advance.
thebestgames said:
Hello ,
Yesterday my phone was at 5% so I wanted tot charge it and it did but only not with the original Leeco charger and cable but with a normal charger micro usb with a mico usb to USB C adapter and it was showing that it was charging . But when I came back 10 minutes or so my phone was stuck in a bootloop and I never had a problem with the phone and I was running a LineageOS 15.1 rom.
My Le Pro 3 X720 is stuck in a loop and I can only get to Fastboot mode.
When i try to go to recovery mode (TWRP) it shows Recovery but after a few seconds it is trying to boot but then it restarts again.
What i tried is to flash a new version of TWRP but after that it is still in a loop and not going to twrp.
I know of the QFIL MODE but I don't want to lose my data.
Can someone please help me ?
Thanks in advance.
Click to expand...
Click to collapse
Since you changed TWRP
I hate to be the bearer of bad news. But it sounds like your phone was short circuited and something is fried most likely the motherboard. I would forget the data, its gone.
But I would absolutely try QFIL, just in case its a very unusual corruption issue. Sorry.
If it was the battery, the usb card, or just a brick ; your symptoms would be very different.
I has a similar issue last month, when the chip is fried you can still use qfil, see the phone in adb, flash roms etc. But never be able to access Recovery or the system, However, you can access Fastboot.
Hi tsongming,
Thanks for your answer but I changed the TWRP after it was in a loop I tought then it might go to TWRP but that was not the case.
And I am not hoping that it is short circuited but if this is the only realistic option what happend then I am going to try the qfil methode .
Bootloop
Hi tsongming ,
I have tried al QFIL options but it did not fix the problem.
Do you know something else to try ?
tsongming said:
Since you changed TWRP
I hate to be the bearer of bad news. But it sounds like your phone was short circuited and something is fried most likely the motherboard. I would forget the data, its gone.
But I would absolutely try QFIL, just in case its a very unusual corruption issue. Sorry.
If it was the battery, the usb card, or just a brick ; your symptoms would be very different.
I has a similar issue last month, when the chip is fried you can still use qfil, see the phone in adb, flash roms etc. But never be able to access Recovery or the system, However, you can access Fastboot.
Click to expand...
Click to collapse
thebestgames said:
Hi tsongming ,
I have tried al QFIL options but it did not fix the problem.
Do you know something else to try ?
Click to expand...
Click to collapse
Try QPST
https://forum.xda-developers.com/showpost.php?p=77723528&postcount=2
Hello tsongming,
Where can I find the Programmer *Choose "Prog _Ufs_Firehose_8996_Ddr.Efl" and Load *Xml- Choose All Ramprogxxxx —Choose All Pathxxx files ?
tsongming said:
Try QPST
https://forum.xda-developers.com/showpost.php?p=77723528&postcount=2
Click to expand...
Click to collapse
Bootloop
I found the files they were in the in the extracted le_zl1_qfil_ufs_fix.zip .
tsongming said:
Hello tsongming,
Where can I find the Programmer *Choose "Prog _Ufs_Firehose_8996_Ddr.Efl" and Load *Xml- Choose All Ramprogxxxx —Choose All Pathxxx files ?
Click to expand...
Click to collapse
But QPST didn't work either the phone is still in bootloop.
But thanks for your help
thebestgames said:
But QPST didn't work either the phone is still in bootloop.
But thanks for your help
Click to expand...
Click to collapse
Right everything you need is within the qfil. Although I gave mentioned it already its very important that you have all of the Windows protections disabled. Windows 10 has so much potential, but is severely crippled by its monitoring and assistive programs. If you are using programs such as Qfil, Windows security will delete some of the files and it makes Qfil unsuccessful. So again, make sure that every aspect is disabled.
When you open Flash 1.9 or 2.0 or QPST make sure that they are opened as an Administrator ( Right click)
If QPST and Flash 2.0 are not working try using fastboot.bat. This can be loaded while in EDL mode. You need 5.8.26s which comes with the fastboot.bat file.
All you need to do is place the stock Rom on your desktop, unzip the rom and double click fastboot.bat. ( The file name is either fastboot.bat, flash-all.bat or something similar. I don't remember the exact name) But there will only be one file with the option of flashing all so choose it.
The .bat file It will automatically flash all of the boot images to the phone. Afterwards your device will be fully restored to stock.
Here is the file: https://androidfilehost.com/?fid=673956719939836266
Isn't it possible to make this under Linux? It would be easier while windows has so many Antivir and defender tools. Also the USB driver are creapy under windows. I have often problems to see Samsung and leeco phones under windows. Via Linux they appear without a problem.
Fastboot
QPST , Flash 2.0 and fastboot flash where all successful but the phone is still in bootloop so I think it is a hardware problem.
tsongming said:
Right everything you need is within the qfil. Although I gave mentioned it already its very important that you have all of the Windows protections disabled. Windows 10 has so much potential, but is severely crippled by its monitoring and assistive programs. If you are using programs such as Qfil, Windows security will delete some of the files and it makes Qfil unsuccessful. So again, make sure that every aspect is disabled.
When you open Flash 1.9 or 2.0 or QPST make sure that they are opened as an Administrator ( Right click)
If QPST and Flash 2.0 are not working try using fastboot.bat. This can be loaded while in EDL mode. You need 5.8.26s which comes with the fastboot.bat file.
All you need to do is place the stock Rom on your desktop, unzip the rom and double click fastboot.bat. ( The file name is either fastboot.bat, flash-all.bat or something similar. I don't remember the exact name) But there will only be one file with the option of flashing all so choose it.
The .bat file It will automatically flash all of the boot images to the phone. Afterwards your device will be fully restored to stock.
Here is the file: https://androidfilehost.com/?fid=673956719939836266
Click to expand...
Click to collapse
one of le pro 3 have simillar problem on me its only when cable plugged in device powering on(after 20-25mln) and stuck on logo then goes black..Device can go to fastboot but pc not seeing device ( maybe usb type-c board broken) also device is not going to edl mode( tryed many ways all failed) maybe is there any way to switch edl mode via hardware? device already opened condition. vol+and- with cable without cable didnt worked..
My phone is in the same situation qfil, fastboot, anything has work
its like some write protection on the device if not something died inside...flashing successfull fastboot rom install success but still in bootloop...
eltdesign said:
its like some write protection on the device if not something died inside...flashing successfull fastboot rom install success but still in bootloop...
Click to expand...
Click to collapse
Checkout this possible solution: https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71
Hi,
I have same problem, my phone x720 in bootloop when I try to power on or try to go in recovery mode, I read many tread with different solutions that I tried, but nothing, I can't resolve.
I made with fastboot, with this result
PS C:\Users\Pippo\Downloads\platform-tools> fastboot oem unlock-go
...
OKAY [ 0.013s]
finished. total time: 0.015s
PS C:\Users\Pippo\Downloads\platform-tools> fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.087s]
finished. total time: 0.089s
PS C:\Users\Pippo\Downloads\platform-tools> fastboot flash recovery recovery_twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.025s]
writing 'recovery'...
OKAY [ 0.335s]
finished. total time: 1.365s
PS C:\Users\Pippo\Downloads\platform-tools>
Click to expand...
Click to collapse
And with FlashOne I had this
Writing log to 'C:\Users\Pippo\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Pippo\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Succeed
Finish Download
Click to expand...
Click to collapse
But nothing, I'm in the same situation, can someone help me?
michiamomork said:
Hi,
I have same problem, my phone x720 in bootloop when I try to power on or try to go in recovery mode, I read many tread with different solutions that I tried, but nothing, I can't resolve.
I made with fastboot, with this result
And with FlashOne I had this
But nothing, I'm in the same situation, can someone help me?
Click to expand...
Click to collapse
Yes same problem everytime phone resart and resart, i follow all step, working at 1 time . Can open and i update 1537515040_LE_ZL1_LEX720-CN-FN-WAXCNFN6003009091S-6.0.03 . When i install apk phone turn off and back to problem. I try unbrick still same. Maybe hardware problem
Sounds like your battery is faulty. Had the same bootloop issue on my X727 and a new battery fixed the problem. Got the battery here www.aliexpress.com/item/32892123537.html and received an original LeEco battery with date code in 2016. Battery works fine though, phone charges well and no more bootloops.
Hola, tuve el mismo problemas un bucle infinito de reinicios y ningun foro que tenga una solución, sin embargo al leer que podría ser un problema de hardware, lo abri y encontre un conector ligeramente desmontado,(conector de banda anaranjada, superior derecho, si vez de frente la batería a la par de un código qwerty) lo conecte y listo volvio mi LeEco pro. Lo comparto por si a alguien mas le puede servir, de hecho ya había descartado mi telefono y compre otro, pero siempre queda la idea de buscar una solución.