I have the newest philz and some how it can't wipe every time I tell it to wipe it can't do it? I even did another recovery but that one won't install roms this is twrp? Then after when I got a rom to sort of work with twrp recovery I switched thinking that was the problem. After resetting instead that one some how broke adaway and adfree there stuck in a loop and I can't call out that is what happens when I use twrp and I can't flash roms I even checked if the files were broken and they weren't. what recovery works or what is my phone doing with this rom or recovery ?
JinxTheCat said:
I have the newest philz and some how it can't wipe every time I tell it to wipe it can't do it? I even did another recovery but that one won't install roms this is twrp? Then after when I got a rom to sort of work with twrp recovery I switched thinking that was the problem. After resetting instead that one some how broke adaway and adfree there stuck in a loop and I can't call out that is what happens when I use twrp and I can't flash roms I even checked if the files were broken and they weren't. what recovery works or what is my phone doing with this rom or recovery ?
Click to expand...
Click to collapse
You didn't give us nearly enough details to know why you are having problems. Lots of people use TWRP without problems and TWRP can certainly install custom ROMs. To have any idea why you are having difficulties, you'd have to give us a detailed, step by step description of what you did with your phone and the error messages that you received.
.
Ok I'm not sure what details to give you I got my phone on I used a rooting process off the unlocker.com for my phone and it worked but my recover doesn't work no mater witch one I use i have s5 g900f for t mobile I'm not sure if I should just try re-rooting my phone maybe? Also the error I'm getting for installing anything is just abort and it can't install because it can't open? and I know the files are not broken tried downloading from computer and phone and saving to my card and the phone. What else do you need me to provide? I'm using the alliance rom that isn't working right because of what is going on with my phone. I can't go back cuz my backups don't work because my recovery isn't working no matter what I use because it will always not complete the restore in either.
I went to get a error message now and now I just get a blank screen in recovery so it's frozen and I can't bring up anything just the name of any rom I try to flash.
fffft said:
To have any idea why you are having difficulties, you'd have to give us a detailed, step by step description of what you did with your phone and the error messages that you received.
Click to expand...
Click to collapse
JinxTheCat said:
Ok I'm not sure what details to give you
Click to expand...
Click to collapse
Well we can't see your phone. And obviously there is no way to know what is going on if we can see it and you don't describe what you see in detail. For instance you say that you had an error message. But you don't paste the verbatim message here. Don't you think that message might be useful, if not critical.
For effective troubleshooting, you should post a detailed description of what you did, step by step and what was on screen. But I already said that in my last post and you disregarded the suggestion. I'm sure that others will guess at solutions for you. But efficient troubleshooting isn't possible without information.
.
1 If I told you I couldn't post the error message which I did because the recovery screen is blank what do you want me to post? I mean there is nothing on the screen to post there is nothing there because it froze it does not say open or anything there is nothing there unless you want to see a blank background. 2 If you mean what I used to root it would be CF root. Other then that I tried philz and twrp both have the same blank screen when you try to open a zip to install. would you like a black screen for twrp or a or blank purple and pink screen for philz with no text ? I posted that I went for an error message but the screen is blank and I can't make anything happen now. I can't give something when nothing is currently there. I'm just going to flash stock and unroot then root and see if that fixes my problem.
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
I think you got the "cannot receive hello packet", because your bootloader is locked. Using this method https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 to unlock it, then flash twrp, then firmware
The bootloader was unlocked (though it may have been unintentionally re-locked somehow?), and MiFlash works with a locked bootloader, so I don't think that's the issue. Axon7tool also doesn't help, because just like adb it can't find the device.
Now, trying again today, MiFlash is working for some reason. I haven't done anything differently, but I can flash whatever I want with MiFlash now. But it doesn't really make a difference, because the phone is still entirely unresponsive, I can't enter recovery or boot in any way. Any suggestions for what else to try?
Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
bkores said:
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
Click to expand...
Click to collapse
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Aspoehro said:
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Click to expand...
Click to collapse
Ok so TWRP is definitely not the problem. Can you remember exactly when the problem happened, like after SuperSU was flashed since you mentioned using the Flash TWRP and root option?
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Aspoehro said:
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Click to expand...
Click to collapse
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Gnreux said:
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Click to expand...
Click to collapse
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
bkores said:
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Click to expand...
Click to collapse
I can't be sure since I don't know exactly what the problem is or how I caused it. All I really have are guesses at this point.
Aspoehro said:
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
Click to expand...
Click to collapse
I rebricked myself last night (lol), so I had to reflash full package, from the same link you posted, and here are some notes:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Second boot worked (and I now remember that the same thing had happened the first time I bricked my device), but Android asked me for a password even though I had formatted /data
From there, install TWRP via fastboot (and fastboot_unlock prior to that if bootloader is locked, it shouldn't be), format /data using TWRP, reboot, and you should have a working device
Hope it helps!
Gnreux said:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Click to expand...
Click to collapse
I don't even get that much, nothing I do gets any response from the phone at all. No LED when trying to boot (including EDL or recovery), no LED when charging, the only indication that the phone isn't perfectly dead is that it shows up in device manager and MiFlash.
You could try not flashing fastboot_unlock right away and booting first instead... This is the only thing we are doing differently, although I don't see how it could have an impact.
You could also try flashing this EDL package (B13) instead and flash your device specific bootstack afterwards.
Still no luck with anything I try to flash in MiFlash. But I tried reinstalling drivers with Zadig, and axon7tool is working this time. Trying to read gpt works fine, but if I try to read/write boot or recovery, I get "W: bad lba in partition entry 26" and "Cannot find partition boot"/"Cannot find partition recovery". I tried writing TWRP and a couple stock boot/recovery images despite the error, still no change.
Do those error messages give any new information that might be helpful?
Try miflash firmware from offical:
https://www.zteusa.com/axon-7#support
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
lipe123 said:
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
Click to expand...
Click to collapse
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Flapjack said:
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Click to expand...
Click to collapse
Glad it helped someone!
Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.
Vygravlil said:
Hey guys!
At first, this is my first post here so please be lenient if I posted this in the wrong section or whatever. I still need to get used to this forum.
Second, English is not my native language so it could become some gibberish from time to time. I also have to mention that my Android skills are somewhere between newbie and advanced, so please keep that in mind.
But let's get ahead to my problem:
Some days ago, I decided to install Linage OS 14 on my SM-N910F because I don't like the Stock Android 6.0.1 of it.
As you know, a custom ROM requires an unlocked bootloader an that's where my struggle starts.
I simply can't find any tutorial or similar for my phone. The only one I found didn't work (It was with adb fastboot, the process got stuck at "<wating for device>" after the command "fastboot unlock oem" which was described in the tutorial).
I retried it about three or four times before I gave up. It feels like I searched the entire internet, including this forum, but I couldn't find anything useful.
Maybe it's my fault because I didn't look properly, but yeah, know I'm here to ask directly:
Do you guys have any tricks, tipps, ideas or tutorials for me to try?
If it helps you, my phone is already rooted. (chainfire's CF Autoroot)
It'd make me really, really happy and already thank you for your (hopefully) incoming answers.
Click to expand...
Click to collapse
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage
sawdoctor said:
Pretty certain your bootloader isn't locked, you just need to install twrp with odin and then you are good to flash lineage
Click to expand...
Click to collapse
Thank you for your fast reply. I'll try it once again, moreover I'll let you know if it worked.
It's me again. Flashing the ROM worked, my phone now runs under Linage OS 14.1. But now I've got another problem: Gapps. Somehow I can't flash the Gapps package, TWRP always tells me that the file is corrupted. I downloaded both the Pico and the Nano package for ARM Android 7.1* devices. Both don't work. I also tried the Android 7.0.* version, but that didn't work ofcourse. (Error 20: Wrong Android version installed on the device.) Is it my fault because I downloaded the wrong packages or what's the issue?
It'd be awesome if you could help me again.
Vygravlil
EDIT:
Okay, now it works. TWRP was right, the file was corrupted. I figured out that my PC kinda messed up the download of the package. I downloaded it with another computer and now everything works fine.
Guys, I'm at my wits end here. I don't know what to do. And it's driving me crazy.
After saving for 3 months, I got a used Essential Ph-1 from craigslist (for sprint). It came with Android 9, and a February 5, 2019 security patch.
All I want to do is to root the phone. And I have tried everything in my power to get it to work. It just does not. I have unlocked the bootloader, I'm seeing the device in adb and fastboot, but unable to sideload, or flash anything. I've been following different threads on here and youtube looking for directions, but my phone will just not do it.
Can someone please help me? I will send my phone over to you and pay you to have it done. I've tried almost everything to do it, and nothing works. I've even tried to flash android 8 and 7, it still doesn't do it. Someone please help me. I don't know what more i can do. Any guidance is appreciated.
Can someone please help me? I don't know what more to do. Please.
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
goofball2k said:
Can you temporarily boot to twrp?
Are you using fastboot.exe from the essential ph1 driver folder?
Click to expand...
Click to collapse
No. I can't sideload or boot into anything other than the android 9
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
kt-Froggy said:
I also bought my PH-1 on CL, but it was an open market version. I can only outline what I found on this forum, and what worked successfully for me... I assume you are on Windows. First off, make sure you install the drivers provided by Essential, and use adb/fastboot that comes with it (it gets installed and put into the system path when you install the drivers).
I didn't care about TWRP, so the only thing I needed was root. So, after unlocking bootloader (and also unlocking critical, as recommended), I simply followed the steps to install Magisk, which are really straightforward:
https://topjohnwu.github.io/Magisk/install.html
Just use the "Boot Image Patching" section.
That's it. Works perfectly, and I just need to repeat the patching after OTA updates (there is a thread about this procedure specifically).
If fastboot flashing doesn't work for you for some weird reason, I don't have any good ideas about that, sorry! Sounds like you are able to get into the fastboot mode (since you are saying you can see your phone in the device list), so why it wouldn't let you flash is kinda baffling...
Click to expand...
Click to collapse
I tried that too. But it kept saying unable to unpack boot image | installation failed.
I tried it with the stock images from the Essential website, both the OTA and fastboot versions. I'm getting the error for both files.
I would suggest checking out the PH1 Dev telegram group https://t.me/EssentialPH1DEV . not only will you find pre rooted stock boot images along with ones with TWRP as well you will also find help flashing them if you need it. Hope this helps you out.
Thank you everyone for all your help. Special thanks to kt-Froggy. I got it to work. I had to change my usb port from 3 to 2 and i was able to get it to work!