So after hard decision, I tried to root my Axon 7 (A2017) (reason: chinese interface without google services), without first taking care of backup (me idiot). I have followed procedure, installed qualcomm drivers, flashed image and then got stuck at boot, with only flash on the screen and open EDL port. I have no guesses what happened, so maybe if anybody experienced same issue I would be glad if he shares solution with me. Or maybe if is possible for someone to pass me recovery and boot backup (if this is option even).
-A2017-B07-20160808093453290 was installed prior flashing
I'm newbie in this, so please excuse me if anything is not obvious to me what should be. Thank you!
Must also apologise for not finishing title of thread, cannot edit it after posting, sorry guys for making mess..
Related
I have been reading and attempting two flash anything for 2 days. I am new as I have stated in some threads and need baby steps unfortunately like im
sure some others do. I have been able to unlock, root, and get into recovery but after that no dice. I get everything Im suppose to do but... I am not able
to flash anything and I have looked for help in threads and have had some help and success but more importantly all detail is not clear to me all the time. I
am on here because I want the most out of my phone and all the goodies and appreciate the work of everyone. Coming from Windows to Android is
different and I understand will take sometime to gain the knowledge needed but it seems as you/we are supposed to know everything already or if you/we
dont understand what to do then you/we shouldnt be flashing some say. I disagree with that because I started the same way on my HD and eventually
was able to help new ppl to the forum. We all have been there at some point trying to learn and being clueless then finally getting it. For instance I was
looking at a theme thread and there was no instruction from the author am I just suppose to know what to do with the file being that Im not a week into
this and have never dealt with android? Also what to write in some command prompts is not the same for everyone different and thats not always clear.
With that being said this being a new device I would hope that things will be more written out to help and if its not at least be able to get help. This is just
in some cases not all . Again I am thankful for everyones work on here.
Now with the files I have trouble with are pretty much every file I have placed on my sd card not being recognized except Modocas rom until I renamed it
update.zip. Until then in recovery nothing would be recognized and even still the rom failed to install in which I have no clue why and have been seeking an
answer and so have others. If anyone has any suggestions it would be greatly appreciated for me and others and also to give detail on what to do with
what we are given. Thanks to everyone who contributes on here and make the experience that much better.
Every one of the instructions that are on this forums (in the dev area) are explained in detail. You must have some core understanding of basic linux commands and android file system. Those we are not going to teach you here. There are many documents on android itself (search on google) and HTC also has a lot of documentation on flashing.
However with that said, rooting instructions were to the point and should be able to follow without issues. thefallen has written it instructions for windows/dos and I've recapped them for linux/osx. To be honest, commands are the same for adb and fastboot.
Amon_Ra also has a good instructions on how to update his recovery. Pretty much if I should recap, I'd say boot phone in boot loader and fastboot flash recovery new_recovery_image.img
As for the themes and most of the updates, always run a nandroid first and update. What do I mean by that? Nandroid is the backup utility in Amon_Ra's recovery. If you ran it, you can restore to that. Call it a restore point but it's more than that (read on that so you know what it actually does). Why nandroid? So you can restore if you don't like the effects of what you just done. Now you can just update via zip that you download.
I think it's very simple. What do you need explained in detail? Most of the stuff you are requesting is simple knowledge. I am not saying I am holier. I am just saying I am used to the commands. Once you flash it a few time, it'll come to you too. But please do read up on how to restore an image from HTC. Go to HTC Global, and support and pull up google ION.
Read thru the instructions. If you are still confused, feel free to PM me.
If recovery is only recognizing update.zip, are you sure you have Amon_Ra's recovery on there? Have you tried to reflash his recovery image?
Thank you guys. I figured out what I was doing wrong.
Hi All…
This is a NOOB question, so if I'm in the wrong place, please accept my apologies and direct me to the right forum. With that said, here's my question: Through Google Play I put both CWM and TWRP on my Nexus 7 to see which one I liked better. I happen to like TWRP, so I uninstalled CWM. This strikes me a completely weird, but every time I reboot into recovery mode CWM keeps coming up…not TWRP. This is frustrating the crap out of me. On another posting I read that someone else was having this same problem. One of the posted solutions was to erase the recovery partition and then flash TWRP through fastboot. THIS is a bit above my pay grade, but I'd really like to learn how to do this. Would someone mind giving me a quick tutorial or at least send me to the appropriate posting so can read how to do this? I'm a quick learner and I promise I won't take up too much of your time. Thank you to all who bother to chime in.
A recovery is not an app that you can just install and uninstall. You need to flash the recovery image you want, in your case TWRP.
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
Have you tried booting to recovery from bootloader and regaining an ADB connection? This should be all you need.
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Magnum_Enforcer said:
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Click to expand...
Click to collapse
I was updating my Nexus 10 tablet - had gotten to the system partition - when I lost the ADB connection. I've since learned that's a problem with newer Macs (I was connected to Windows through Parallels). Here's a link to a thread about that:
https://code.google.com/p/android/i...Stars Reporter Opened&groupby=&sort=&id=65301
Because of the lost connection, the system partition did not flash and my tablet is bricked. There is no operating system so it can't boot into Android, but it can boot into the Bootloader and Recovery mode. All the other partitions are fine.
I have a custom recovery (TWRP) and an unlocked bootloader, but I'm at a loss to figure out how to flash the system.img file. I can't boot to Android so I can't connect through ADB in Fastboot mode to flash the ordinary way. I am connected through ADB when I'm in Recovery mode, but I can't use the flash command in Recovery mode. Nor can I figure out a way to make TWRP flash the partition by running it as a zip file - mainly because I can't figure out what the update.zip file should consist of. There was an OTA update file on my device when I started the manual update (manual updates fail), but I didn't look at it and didn't save it.
I tried pushing the system.img file to the Nexus 10 using the Linux dd command, but that doesn't work with the system partition, which uses a special format. The details are explained here, but I don't fully understand it:
http://www.modaco.com/forums/topic/327661-how-to-backup-the-systemimg-bootimg-and-recoveryimg/
After spending about 8 hours on this last night, I believe the only way I can fix it is to create an update.zip file that uses a Linux script to flash the system partition, but this is way beyond my skill set and I can't find a model for how to do this anywhere. All tutorials I've found for creating zip files for flashing are for installing apps, not flashing a system partition - which is even more complicated than flashing, say, a boot partition. Nor can I find an update.zip file from someone's cache (sure wish I'd saved mine) to use as a model. I'm looking for someone with this kind of high level knowledge who can give me guidance - or someone who can refer me to someone who has this kind of knowledge.
I solved this problem.
Hi all, i'm new to Android Phones, so i started a few days with this phone. But now i think i've done a big mistake, i tried to erase everything from the phone, in a hope to "restore" to the factory state. Instead, i think i've deleted everything from the phone, and now, it only says "Your device is booting now..." and it doesn't boot. It's unlocked and rooted, i've deleted it from the TWRP menu.
So, is there anything that i can do, to restore it back? The model i think it's the VNS-L31, i'm downloading a firmware from the L21, can it be replaced or something like that? Thankx in advance.
*Edit* I found stock rom for my phone here in the fórum, but it says i need to have stock recovery but i have the TWRP recovery. Is there any way that i can do it, with that recovery?
*Edit 2* In Erecovery, when i try to download it says "Getting package info failed"
First of all... Why don't you have a backup in TWRP? ALWAYS back up your stuff before doing ANYTHING in TWRP.
Second: there is an option for factory reset within the EMUI system itself. Absolutely no need to mess around in TWRP for something like that. Of course you can "factory reset" in TWRP but this can also wipe your system which then requires you to flash something.
To your problem:
Since I luckily was not forced to flash a stock firmware yet, some more information would be nice.
In which format does the firmware come (link to where you downloaded it)? TWRP can handle .zip files. So if it comes as a .zip file, you can try flashing it through TWRP (really depends on what you downloaded!)
If you only need stock recovery, try accessing TWRP with your phone plugged into a PC.
This way it normally fires up the stock eRecovery.
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
iDeadSmack said:
Hi, yeah, i should have done a backup, thank you for the advice. The firmware i used is this one www .stechguide.com/huawei-p9-lite-marshmallow-firmware-b100/ - i found it here, and a user used it to, not sure why, but he says that it worked.
I'm not sure if this is the right way to do it, because i'm new to this. The TWRP boot, but i can't get my phone to get recognized by the huawei software, not sure if it need to. Even with the drivers installed, it only connects if the phone is on the menu.
Click to expand...
Click to collapse
Hmm maybe best way is to send the user that made it work a PM and maybe he can provide you a guide on how to do it.
And maybe he or you can then provide a guide here on how to do it.
This device is rather new and the forum is building up so there is a lot of work to do and a lot of things have to be worked around.
Hope you can fix it, like I said, I cannot really help you properly since I never had the problem and therefore do not really understand what's happening on your device.
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
iDeadSmack said:
hi, thank you for the reply. In fact i have solved the problem few minutes ago, and was thinking on do a quick fix tutorial or something like that. Because it's really fast, just need to do the right way.
I'm really happy for the help i got in this forum, all the threads are really intersting. Going to try help others with the same problem that i had. Thank You
Click to expand...
Click to collapse
Could you help me with this problem i have the same problem on Huawei l-21 ??
Always have a backup of your fresh system on TWRP. Then whatever happen just restore it whenever you think you messed up your device and you should be fine ALWAYS.
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.