Related
I flashed Taboonay 2.1 to my Icona Tab A500 last night. Everything was great. I retrieved all my usual apps and previously purchased apps back down from the market, network was working fine. Turned on tab this morning and it is unable to connect to wifi. Keeps trying several times and then says the attempt has been disabled. It sees the Motorola Surfboard but can't connect. I thought I would try to re-flash since the .zip was still on my external SD. I attempted to boot into CWM but it won't come up. It just says loading image and never goes into CWM, that's it. So, I have no ability to connect by Wifi and am unable to download Acer Recovery Installer in order to re-install CWM. Apparently the CWM image is corrupt. The CWM ROM Manager Premium is still on my desktop but it can't do any sort of recovery because if I bring it up and choose "_install .zip from SDCard" it reboots into recovery mode and can't load the recovery image either. Does anyone have any ideas? Taboonay 2.1 is Android 3.2 it has the xda ad hoc wifi patch in it (which has never been quite right) in my opinion. So I found a copy of the 3.1 wpa_supplicant file and installed it into the /system/bin folder using root explorer to set the permission correctly after renaming the one installed by Taboonay to wpa_supplicant.old and re-enabled Wifi. Still it would not connect. The only difference I could see was that it no longer could see ad hoc wifi networks but still would not connect to my infrastructure wifi although it could see it. This particular wpa_supplicant file that I went back to came from Acer 3.1 stock ROM and worked perfectly under 3.1. I'm basically out of business at this point with no network and no way to flash a new ROM or restore a backup. Does anyone have any idea what to do next. Has anyone else had wifi issues with Taboonay 2.1? I did see an update 2.1b for Taboonay 2.1, but I can't get into CWM to apply it. I might as well be totally bricked. I can connect to the tablet and have full access to the 2 SD cards via Windows and a USB cable, but I can't download Acer's Installation Recovery from the market from a Windows browser. I'm sure its not the router because 3 Windows 7 SP2 Computers can connect to it and so can my wireless HP printer. Everything seems to be a Catch 22. Help! Anyone had trouble with Wifi on Taboonay? Does anyone have any ideas or how to get out of this situation? Any suggestion would be appreciated.
Hey gradyzero sorry to see the trouble buddy but the tabooney 2.1b update is made for wifi updates issues and SU perm, im currently running tabooney 2.1b and full with new market and i have no issues. As far as the recovery have you tried new THORS 1.5 cwm can you try using adb to push recovery.img to the tablet, or maybe using terminal emulator theres a new 1.5 cwm update you can try doing that. just extract recovery img to internal sd and go into thors website "google it" and follow every step except for #3
good luck buddy if not hit me up side PM ill see what i can do atleast to try to get recovery back
I don't think I had restored the terminal program back yet let me check. The apk is something I haven't tried. Thanks for the suggestion. I have thor's 1.5 update on my SD card but not quite sure what use it can be until I can get the ability to connect to boot up in recovery. I'll go to his web site and read the instructions there again, overlooking step 3. I have read them once before but didn't have this problem so I just grabbed the download and planned to update it after the Taboonay flash. Figured it would just have to be redone after the flash anyway. Thank for you idea. I should be able get an .apk onto the SD from Windows and should be able to install it. Again, thanks much buddy. I'll post back to this thread what the outcome is.
Restoration of boot image doesn't resolve the problem.
Okay Crashpsycho I download an Acer Install Recovery apk and CWM Launcher 1.0.0.0 apk. Both appeared to install correctly. Acer Install Recovery came up and I was able to choose to install CWM 1.3.4 image. However, when I reboot into recovery I still stop at "Booting recovery kernel image". So reinstalleing the CWM 1.3.4 image that the Acer Install Recovery show as an option didn't fix anything. Any ideas about why recovery might stop when loading the kernel image? When it says "the Kernel Image" is it talking about the base Linux kernel? I seem to recall reading somewhere that Taboonay replaced the Linux kernel with its own version. Is that true? I thought maybe the recovery image was corrupt but assuming the Acer Install Recovery really did reinstall the recovery CWM 1.3.4 image as it said, then something else is wrong. I did manage to get a terminal program installed so I'll try your second suggestion to force the CWM 1.5 image using adb. If Taboonay really did replace the stock Linux kernel, I have no idea how to recover from that. I'm not quit sure exactly where a recovery image goes and so I suspect that adb will ask for the destination. Maybe I'm wrong but do you know? Does adb know automatically where to install a recovery image? If the Linux kernel has to be replaced then I could get bricked if Tabtoonay won't boot up because a different Linux kernel is installed. What is your thinking about all of this? This is getting heavy. Thanks again for your help. Anyone else that has any fresh ideas is encouraged to jump in here and post to this thread. I'll post back here with the results once I try to force the CWM 1.5 image.
Installing other kernel solved issues for me, using thor kernel 3.5
installing 1.5 use terminal emu, extract the recovery.img from zip folder and place on root of sd go to thors website tegraowners and follow all steps except #3 and that will force 1.5 to tablet. have you tried installing stock recovery image using the acer recovery app
So Sector51 are you telling me you had the same issue. Where booting into recovery locked at loading kernel image? I'll try your suggestion. If it doesn't require you to be able to boot into recovery which I can't. Thanks for the tip.
Crashpsycho, I just completed the terminal method you suggested and followed all the instructions except #3 wihch was a mount, if I remember correctly. I extracted the image file from Thor's 1.5 put it on my external SD by copying it from Windows and then went through Thor's instructions step by step. Recovery boot still hangs at loading kernel image. Thor actually says to install itsmagic into /data/local directory both in his adb push and in his terminal emu methodology. There is no copy of itsmagic in his distribution and I can't find such a file on my tablet. BTW, I also tried the adb push from Windows but the recovery image is pushed to the SDCard so I assume he intents for me to then boot into recovery and to install it. So that's not going to work unless I have itsmagic. The Windows adb method also pushes itsmagic out to the /data/local folder but I can't complete that part and I think it is critical to both methods. Any idea where I get this file? Google search returns nothing except that one entry has been removed due to copyright issues. I think that it is the key to installing from the SDcard. I remember seeing that file on my rooted 3.1 but apparently Taboonay removed it. Can you enlighten me on itsmagic? What is it? Where do I get it? I have currently installed the Stock USA 1.31.06_COM_GEN1 recovery in Acer Recovery but reboot into recovery still hangs at loading kernel image.
This is another side issue but do you know if it would be possible to install the Taboonay 2.1b manually. Is it an update zip or a ROM flash? I'm beginning to think that if I could get back my Wifi back I would just forget the recovery reboot as a last resort. I'm going to investigate what is involved in the kernel update suggested by Sector51. But basically I'm not doing anything else until I can fully complete thor's 1.5 update. Man, I've spent 3 entire days trying to resolve this. I'm going bonkers. It certainly gives me a bad taste for Taboonay that probably isn't deserved because I don't see other post about this particular issue. So please educated me on itsmagic and we'll go from there. Thanks dude for all you help.
I found a copy of itsmagic here on xda. Downloaded it and completly went through the terminal emu process exactly as posted on Thoor's Website for 1.5. Everything seemed to work this time including the execution of itsmagic which spit out a nasty message to Acer something about Its Magic. Acer why did you say the bootloader is locked when it isn't? So this tells me that everything should now be good. I rebooted into recovery and this time it acted a bit different. It still said loading boot kernel but then in about 30 seconds rebooted back to Taboonay automatically. So I'm stumped. Does anyone have and new ideas? BTW, the 1.5 recovery image has a date of 29 Feb 2008. Is that right?
Finally suceeded with 1.5 Recovery, Thanks
This message is specifically addressed to Crashpsycho and Sector51. After four attempts I was finally successful at getting Thor's 1.5 recovery booted. I immediately backed up the current version of Taboonay 2.1 and then applied the 2.1b update. Everything in term of recovery is now good. One problem, the update did not fix the the WiFi problem as I am still unable to connect via WiFi. But that's a totally different issue, which I can deal with. Meantime thank to both of you for generously taking you time to help me resolve this recovery boot problem. I would still like to know what I did wrong during the original ROM flash to Taboonay 2.1 to destroy itsmagic. As well as what I did wrong in my first 4 attempts at repairing the recovery. However, I won't dwell on that as I need to proceed on with working on the WiFi issue. Thanks a million to both of you for all your help and suggestions. You are both what makes xda a truly wonderful and unique place for lovers of mobile devices. I am a programer and web developer and I hope I can contribute eventually to the growing Android mania. I personally think it will eventually dominate the table and phone market, if it already hasn't done so retail wise. I'll return to lurker stats for a while and learn more about the SDK while I try to resolve the WiFi issue. One side note, I recently flashed my HTC HD2 phone from Window mobile 6.5 to Widows mobile 7.5. That involved the flashing of 3 ROMs and then upgrading the OS. It runs beautifully and was much more complicated than what should have been a relatively simple task of upgrading to Taboonay 2.1. I'm sure I missed some small detail that caused the problem with the Icona Tab. You guys helped me greatly and I hope to be able to return the favor at some point. So I consider this issue closed and the moderator should feel free to consider it resolve. xda is power to the people.
Final Note: The adb push from Windows was the last attempt and was apparently the one that successfully fixed everything. As a certified Unix Engineer and somewhat of a Linux expert I opted to use the terminal emulator technique since I knew the commands and what they were doing, but typing in a long stream of commands is always more prone to user error. My advice to anyone else with this problem is to install the Windows Android SDK and use adb push to update as it appears the most recent version takes care of most all the permission issues and is almost fool proof. Again thanks to you guys. The Problem is resolved. Mister Moderator consider this thread closed and resolved.
great job man atleast you got the recovery to work. i cant say much for the wifi issue or what happen to recovery i would say if anything the issue must have came from the wifi ad hoc patch/change but im not fully technically skilled to say that it really was but great job hope you get it back up and going
I am enbrased to admit this but I feel it only fair since so many people attempted to help me. I've search around and apparenty no one has run into this here yet, but it needs to be posted for future reference. Most all of my boot recovery issues took place while the tablet was docked in the Acer A500 docking station. When I have trouble in recovery mode, with the image loading message just hanging up, 100% of the time removing the tablet from the docking station resoves the problem. Just thought I should pass this on. I know it is stupid that I didn't realize this before now. If you are docked, don't boot into recovery' not even with1.5 installed. I have no idea why this is true, but it is. If you have the Acer docking station DO NOT BOOT IN TO RECOVERY WHILE DOCKED!
Open up Rom Manager and click "Fix Permissions" let it do its thing then restart. That worked for me.
I've already searched the forums and found no thread with the solution to my problem. People have had a very similar issue, but not exactly mine, so prior solutions I've found seem to not solve it:
I have a Nexus 7 (2012 WiFi).
It is rooted, clockwork mod.
I have a mac (that seems to not want to detect my Nexus 7 anymore).
I got the update for KitKat, like an idiot, I jumped at it, let it update overnight, and now I'm stuck in the 4 circles loading screen. Since I have CWM, I'm stuck in the CWM recovery mode when I try to do a factory reset. The factory reset does nothing, I was hoping to get back into the stock recovery mode, but have no idea how to get there (nor do I think it's possible).
Keep in mind, I'm semi-tech savvy, but when it comes to "flashing blah blah" I have no idea what the hell anyone is talking about if it's not broken down step by step in layman's terms. If you say, "open the terminal, and type exactly this", then I'm golden, but otherwise, I'm just googling tab after tab to figure out what it means.
As stated above, my mac does not want to even acknowledge the existence of my tablet either with ADK or Android File Transfer. Is there maybe a way I can put a zip on an sd and somehow use an SD reader to mini-usb adapter to sideload a fix? Anyone have any other ideas of how I can fix this issue? I'm not enjoying my Nexus 7 as a paper weight.
Thanks.
Phillustrate said:
I've already searched the forums and found no thread with the solution to my problem. People have had a very similar issue, but not exactly mine, so prior solutions I've found seem to not solve it:
I have a Nexus 7 (2012 WiFi).
It is rooted, clockwork mod.
I have a mac (that seems to not want to detect my Nexus 7 anymore).
I got the update for KitKat, like an idiot, I jumped at it, let it update overnight, and now I'm stuck in the 4 circles loading screen. Since I have CWM, I'm stuck in the CWM recovery mode when I try to do a factory reset. The factory reset does nothing, I was hoping to get back into the stock recovery mode, but have no idea how to get there (nor do I think it's possible).
Keep in mind, I'm semi-tech savvy, but when it comes to "flashing blah blah" I have no idea what the hell anyone is talking about if it's not broken down step by step in layman's terms. If you say, "open the terminal, and type exactly this", then I'm golden, but otherwise, I'm just googling tab after tab to figure out what it means.
As stated above, my mac does not want to even acknowledge the existence of my tablet either with ADK or Android File Transfer. Is there maybe a way I can put a zip on an sd and somehow use an SD reader to mini-usb adapter to sideload a fix? Anyone have any other ideas of how I can fix this issue? I'm not enjoying my Nexus 7 as a paper weight.
Thanks.
Click to expand...
Click to collapse
If your recovery is broken you need to boot into the Bootloader (Hold power until you see the Google logo, then press Vol down.) and then use fastboot to flash a good image from there. You can then do a factory reset etc. You could also do a factory reset from fastboot directly, but you'll want to fix your broken recovery at some point.
Or.. Possibly the better method, since your device is in an unknown state.
https://developers.google.com/android/nexus/images
Get the image FOR YOUR EXACT DEVICE. Don't get the LTE version for the WIFI, etc. Then just run the batch file. It will reset everything (including the internal SD card) and reflash the stock OS. This will leave your bootloader unlocked, with a stock ROM, kernel, recovery. You can flash the custom recovery and supersu.zip if you wish to re-root it.
khaytsus said:
If your recovery is broken you need to boot into the Bootloader (Hold power until you see the Google logo, then press Vol down.) and then use fastboot to flash a good image from there. You can then do a factory reset etc. You could also do a factory reset from fastboot directly, but you'll want to fix your broken recovery at some point.
Or.. Possibly the better method, since your device is in an unknown state.
Get the image FOR YOUR EXACT DEVICE. Don't get the LTE version for the WIFI, etc. Then just run the batch file. It will reset everything (including the internal SD card) and reflash the stock OS. This will leave your bootloader unlocked, with a stock ROM, kernel, recovery. You can flash the custom recovery and supersu.zip if you wish to re-root it.
Click to expand...
Click to collapse
Thank you so much for the response. I apologize for my ignorance: My secondary issue is that my computer does not even recognize when I plug in my Nexus 7. It did previously before my tinkering with it, and before the KitKat update, but now it's like I'm plugging in a brick. I did get to the point of downloading the proper factory image, but it does me no good since I can't load it on there. I don't know how to flash the drive when my computer can't even load anything on to it.
Is it possible to load it through a micro-usb to SD reader adapter? I'm thinking I can load the factory image on to the SD card, and then "sideload" the factory image from there.
To add information so I maybe can get help:
I think the reason my mac doesn't detect it is because I can't get the device into MTP mode so that my mac will see it as a storage device.
I would have to be able to get into the Android OS settings to actually be able to change this setting. I can get into bootload mode, and cwm recovery, but nothing else. I just need some way to get this factory image file onto the Nexus 7, but can't figure out how since this connection does nothing.
Fastboot and recovery do not require any settings configured in the OS. They are independent of the OS. You need to update your sdk on your Mac for the device to be seen in terminal
Sent from my Nexus 5
Pirateghost said:
Fastboot and recovery do not require any settings configured in the OS. They are independent of the OS. You need to update your sdk on your Mac for the device to be seen in terminal
Sent from my Nexus 5
Click to expand...
Click to collapse
It is up to date. It is not recognized either in sdk, android file transfer, or just in finder as a device at all.
You should never see it in a file browser of any sort while in recovery or fastboot mode. Use adb in recovery and fastboot commands in fastboot
Sent from my Nexus 5
I fixed it and recovered it back to 4.2.2, but I will take it!!! NOW I'm going to update to KitKat.
Unfortunately, I can't post links right now since I'm such a new member, but to anyone that has this same issue, I used this guide to get me through it:
Google "nexus 7 factory image restore" written by 2DefMouse. You should find it there.
Also, there's a youtube video counterpart, Google/Youtube this: "How to return to Stock / Updating with Factory Images / Unbrick your Nexus 7"
I'm sure this is fairly common and usual, but for some reason I couldn't figure it out, but to any morons like me, I recommend the guides I followed.
As a tip, for mac, when you type terminal commands, always put the ./ before every "fastboot"... so "./fastboot"
Also, in the guide, it says to type "./fastboot-mac"... I left out the "-mac".
Thanks everyone.
Hello guys.
I would like to ask you for help with my bricked Homecare. I apparently cocked up the flashing process and now I don't know, how to proceed.
What I did:
At first I used the Russian (translated) version of supertool designated for Homecare Note 7. But the process wasn't 100 % successful. The bootloader has been unlocked, CWM recovery has been flashed, ROM 4.3 has been flashed. The tablet was able to boot, but it always froze after a few minutes of operation. Most probably there was a wrong boot flashed. No idea.
So, I checked the forums and RootJnky's videos and decided to use CWM to flash a deodex 4.3 stock ROM.
Flash process was successful, but after restart the tablet remains in boot-loop.
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB.
Right now the only status except a boot-loop is the APX mode. Is there still a chance how to unbrick the tablet???
Thanks for any advice.
Jaro
jardam.cz said:
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB...Jaro
Click to expand...
Click to collapse
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
e8hffff said:
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
Click to expand...
Click to collapse
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
hacktrix2006 said:
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
Click to expand...
Click to collapse
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
jardam.cz said:
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
Click to expand...
Click to collapse
The bootanimation.zip is in /lbh partition under media. Should be a easy enough to copy and paste in if not then i will have a look for a way of doing it without flashing all of it again.
Docs on Homecare Fly One rom update
Hi jardam.cz AND hacktrix2006
I see you guys have a working method to update the Homecare Fly One - do you have any documentation on how to root and update the rom for this model? Jardam mentioned a Russian rom, but it caused problems. I really don't want to brick this, as I live and breathe with this tablet every day! But I can't stand the limitations of no root.
Almost all the YouTube videos show EVGA solutions, and lots of people have Homecare Fly One problems - what's the solution please?
They are all the same base nvidia model which is p1640 the lbh partition is wrote when flashing via apx mode which can be risky. However there is a twrp recovery for our device and a stock 4.4.2 image from tom you can use to flash a generic version if the os.
Hello XDA Members,
first I dont know if im in the right place, but if im not, dont hasitate to move this thread.
Story: I tried to root my Pearl Touchlet XA100 tablet (running Android 4.4.2), but i failed. At this point, it was working. Some time later i wanted to know if it has a fastboot mode were i could boot into, so I typed via adb "adb reboot bootloader", the device rebooted but the device is stuck in the kernel splash image (the image that gets displayed before the bootanimation appears). Its even stuck there when i plug in the charger (it has its own charger port, i dont know i it displayed ever this offline charging animation over usb).
While Im thinking about RMA (with luck they swap/repair it) i cant get it out of my head so i was watching the devices source code, where i found under 0709_4.4/android/hardware/qcom the folders "msm8x74" and "msm8960", the folder msm8960 where in my mind they i looked for it, and its the qualcomm S4 Plus cpu.
Now my Idea/question is that i can compile the source code and flash it... But is there any way for me flashing it if i cant do anything with it? While my PC still detect it as "Samsung Android Phone" i cant use adb, and the device has only a "Back" and a "Power" button on the side, pressing both at the same time to boot into recovery (its the only way i imagine to enter a recovery/bootloader on this device aside from adb...bootloader worked "well").
I dont know much about Android source development, but atleast i know how to flash roms/kernels via recovery and Samsung phones via odin, but maybe with a little help with you it will be enough to revive the tab from the dead.
The device has a 1,5GHz dual CPU, usb 2.0 with OTG support, Android 4.4.2, 2 hardwarebuttons ("Back" and "Power"), a seperate charger port, wifi, a 10.1 zoll touchscreen, 4,5gb internal storage (only /system and /data, no emulated internal sd), the microSD slot supports up to 32gb microSD card. Device at pearl (german cheap-things site: http://www.pearl.de/a-PX8838-1000.shtml Link to the source code of the device: (Sorry, actually i cant upload them on github, its official pearl download) http://www.pearl.de/support/product.jsp?pdid=PX8838&catid=1000&nodocs=1
Call my stupid, frankenstein or so but i cant get it out of my head and i want to repair it, first for fun at the challange and 2nd for saving time waiting on the answer of the support.
Hopefully you understand my personal reasons, the post itself and have the knowhow/right tips to help me
How to root Touchlet XA100?
Hi adi2500,
Unfortunately I do not have the answer for your post, I am new to the Android world.
I would like to know though how you rooted the Touchlet XA100. I have the same tablet and I am a bit lost with all these tools I can find on the internet, none of them seem compatible with Touchlet tablets... Information about tTouchlet tablets is very hard to find...
Which tool did you use? Before you tried the fastboot mode, did you say that your tablet was rooted and working?
Thanks in advance for your answer !
Nothing i tried rooted the device. I actually have 2 superuser apks in /system/app, supersu installed and still i cant install the su binary. Actually i got it running again bx fully discharge the battery, but what makes me wondering is the fact that the battery wasnt connected to the mainboard and the devicr still didnt Boot.
Well, my last Option is building CM11 for it, but i dont know if i can run a modded kernel in it and even if i make it bugless, i dont know how to flash it.
One APP Form bluebox (forgott the Name) tells me, the towelroot bug isnt patched and maybe we have to mod towelroot or write our own APP, but actually im happy without root (better having a non root tab than no tablet). Maybe an Android pro could help us, since im at the end with my knowledge.
Hacker kibs at your service
Never heard of that device, but I can help you
Did u tried the kingo android root
The rooting software is only for supported or unsupported android devices
So I request u to try the kingo android root
This requires a computer to do it
Thanks
HK
Thanks for the advice, I will try Kingo Root
Kingo Root worked
Thanks for the advice KIBS2173 , Kingo Root was able to root my Pearl Touchlet XA100 without any issue I just had to install Universal Android USB Driver on my PC because Windows did not manage to find a driver for it via Windows Update.
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
alajoy said:
I started this thread: (https://forum.xda-developers.com/axon-7/help/help-loss-root-twrp-t3781054)
a while back and ended up never solving my issue, eventually giving up and living with an unrooted phone.
Anyhow I've been trying again to get to the bottom of the issue and after another day of fruitless research here I am hoping to bring it back to your attention.
Does anyone around here regularly use a mac to perform adb commands? I'd love to get some help trying to get fastboot working again.
Should I just give up and find a Windows computer to do this?
Thanks for reading
Click to expand...
Click to collapse
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Teet1 said:
That guy was horribly wrong and sorry you had to live with an unrooted phone for so long. But in newer versions of Nougat (i think B32 or B35) they removed fastboot and you could not boot into it. I have a way of being able to install TWRP here without fastboot (assuming you're on an Oreo bootstack, otherwise you can do almost everything in that thread except use a TWRP for Nougat instead). I haven't tried this, but if you have stock recovery, try downgrading to Nougat B19 by using an official SD card update and using apply update from SD card in stock recovery. Haven't found an official SD card update for you but I've only done a little bit of searching.
edit: ive only found B19 Nougat full image , but here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
download A2017U-7.1.1-B19-Full-326200B1901A2017UV1.1.0B19.zip and extract it and put update.zip in your sd card. boot into stock recovery and use apply update from sd card and select it. hopefully it works and it will downgrade
Click to expand...
Click to collapse
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
alajoy said:
Thank you so much for responding.
So I finally went out and bought an sd card yesterday to try this and I am having no luck.
I tried unzipping the file, but it just creates a duplicate zip file so I simply tried installing the whole package.
Wether I try and install via sd card or via sideload/adb I get the same "installation aborted" message.
This is so frustrating. All I want is to root again! I'm trying to get this phone to last me as long as I can before replacing it.
Doing this all on a Mac, fyi. Not sure if that changes things. Since we're not using EDL or Axon7toolkit I assumed it doesn't matter, but there is a lot that I don't know.
Thanks for any help that you're able to provide!
Click to expand...
Click to collapse
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Teet1 said:
If it's saying that error then it's probably not letting you downgrade.
Also this might be slightly more difficult since you're in a Mac. Can you get access to a windows machine at all? This is why I hate macs
Click to expand...
Click to collapse
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
alajoy said:
So what would be the reason that it wouldn't let me downgrade?
I've always used a mac and always managed to find an answer. Sure, toolkits don't work, but using fastboot and adb and doing it that way always has. Now suddenly no fastboot and I'm screwed... I don't really have access to a windows pc.
I just find it hard to believe that it's simply not possible on a mac.
Click to expand...
Click to collapse
Yeah fastboot screen was removed in newer versions. But that's at a software level of the phone. On your computer, the adb and fastboot commands are universal. It's usable on Mac, Linux and windows. The tools used for the phone like miflash or axon7tool are made for windows though and you kinda need those to fix bricked phones. There's a way to force push the twrp image into the recovery partition via adb but I don't know what the name of the recovery partition is
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
AnonVendetta said:
@alajoy: You can give yourself access to a fake Windows on your Mac. It's called a virtual machine. VirtualBox is one free software that can do this. Pretty easy to use, you install a virtualized Windows that you can boot into. Then you can run all Windows-based tools out there. It's also easy to share a USB port with the VM. Then flashing tools can access it. I run Linux as my main OS on a Sager gaming laptop, this is how I flash my A7 and Samsung phones. It just works, and reliably. I do also have a real Windows 10 installed on a partition on the same PC, but that is only for gaming and I never, ever allow it to connect to the Internet.
@Teet1: The literal name of the recovery partition is exactly that, recovery. And that is what most Android devices call it, regardless of manufacturer. It doesn't matter whether it is TWRP or ZTE stock recovery, the name is the same. It can be accessed via the paths:
/dev/block/platform/soc/624000.ufshc/by-name/recovery
/dev/block/bootdevice/by-name/recovery
/dev/block/sde14
On other devices the path may be different (but the 2nd example above will work for most), but the name is usually the same.
Click to expand...
Click to collapse
By name i meant the path, are you sure that's the path for our device? I tried that once and it was not that. Either way he is able to do it
@Teet1: Yeah, I'm sure, but not on all 3 paths. /dev/sde14 may be correct or not, depending on firmware/boot stack that is installed (or the presence of a vendor partition, which might change the paths). But the other 2 should be as I listed.
Just open a root file manager and see for yourself. I use Total Commander, which also shows symbolic links (the one with "bootdevice" in the path is really just a symlink to 624000.ufshc). Getting the recovery path from the example with "bootdevice" in the name should also work on almost any device running Android, and will generally point to the recovery partition. You can see the paths in TWRP too, but TWRP doesn't show symlink (but you should be able to see them if you use the right commands in any terminal, like TWRP's terminal).