Related
As I wrote the guide I realized the files, scripts, and images are scattered through multiple threads, which makes finding what you need difficult, even from a main thread (the guide for example). This was compounded even more when I was writing the CM9 Install Guide for the CyanogenMod Wiki and listed the commands themselves, it became huge, intimidating, and looks extremely daunting, I can only imagine what a new flasher must think seeing it! And and so I decided perhaps I can fix this, and with that I present to you...
The A100 Flashing Toolkit!
What is it?
A single zip file that, when unzipped, contains EVERYTHING you need, ADB, fastboot, scripts, CWM recovery image, everything you need to take your stock ICS A100 through rooting, unlocking the bootloader, and flashing CWM recovery (twrp coming soon)!
How is it used?
Its a set of 6 PC scripts, 3 for windows users (.bat) and 3 for linux users (.sh). Run in order from the same folder, and you can just click and run, reboot, click and run, reboot, click and run, install custom rom, done!
You MUST already be on ICS! This is not for HC, if you are on HC update to ICS FIRST!
Instructions
Make sure you are on ICS! Read the bold red letters above! You have been warned! You should already have installed the Acer USB drivers for ADB to work.
Ok, now you're on ICS....right?
Download and unzip the file to whatever folder you can remember, for example c:\acer or ~/acer.
Open your file manager of choice and browse on over to where you unzipped the files, and get ready.
Windows
Right click on A100-root-win.bat and select Run as Adminitrator.
Once that is finished, let your tablet reboot.
Once it's rebooted, right click on A100-unlock-win.bat and select Run as Administrator.
Once this finishes, let the tablet reboot again (the script will tell you what's happening)
Once it's rebooted, right click on A100-recovery-win.bat and select Run as Administrator.
Allow it to finish, it'll reboot a couple times.
Half the time it reboots into recovery, other reboots into system, not sure why it happens.
If it boots into recovery, go ahead and make a full backup, might as well.
If it boots into system, reboot into recovery and make a full backup, might as well.
At this point, you can now wipe and install a custom ROM, see the A100 Guide in General for ROMs and instructions on this.
Linux
Execute A100-root-linux.sh and allow it to run.
Once that is finished, allow tablet to reboot.
Exectute A100-unlock-linux.sh and allow it to run.
Let the tablet reboot
Execute A100-recovery-linux.sh and allow it to run.
It'll either reboot into recovery, or system, it does one or the other for some reason.
If rebooted into recovery, make a full backup.
If rebooted into system, reboot into recovery and make a full backup.
Wipe and install a new custom ROM, see the A100 Guide in General for ROMs and instructions on this.
How to boot into recovery
There's a few ways, 1 way is an app like quick boot, you can use adb by typing adb reboot recovery or you can do it manually.
Power off the tablet.
Press and hold the volume - button, closest to power and lock switch.
Holding volume - press and hold Power.
Hold until the screen says Booting recovery kernel then let go.
You should be in recovery, either CWM, TWRP, or stock, whatever you have installed.
As always I am open to suggestions, advice, or reports! Feel free to post up or PM me with any issues, questions, bugs, or ideas!
Download
A100 Flash Toolkit 1.1 7-16-12
Now featuring the correct bootloader!
Thanks to smokku for pointing this out.
Who do we thank for this package?
ZeroNull: Alot of the scripting is based on his work, and borrows his ADB and fastboot executables.
ptesmoke: Uses his CWM recovery.img file
CyanogenMod Iconia Team: For allowing me the chance to write for the Wiki, and realizing this NEEDED to be done.
Anyone else I'm forgetting, I'm sorry I will add you as soon as I remember (feel free to drop me a note!)
Sounds great, many thanks.
Thanks for all you hard work and patience.
a100 flash program
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Birbey said:
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Click to expand...
Click to collapse
Oh wow OK I'll take a look I must have mixed everything up. My desktop is littered with files from all these projects. I'm sorry about that I should have double checked everything before I uploaded it. If the called files are different then the scripts it must be the old version mixed with new scripts or something. I should have it squared away sometime tonight/tomorrow morning.
Edit: I'm assuming by saying command prompt you use windows, the a100-root-win.bat file looks fine, was this one giving any issues?
I'm checking the second and third now for whatever is going on.
Tapatalked from my Galaxy S II.
Fixed.
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
diegof18 said:
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
Click to expand...
Click to collapse
You have to be FAST when it gets there, it times out in like half a second it seems.
When you run it, have the tab in your hand, fingers on volume - and volume + (volume - is next to the lock switch). As soon as you see the screen change, hit volume - then volume +. It takes a few tries usually. It'll just sit there until you reboot afterwards.
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
elander said:
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
Click to expand...
Click to collapse
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
thanks for the info.
pio_masaki said:
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
elander said:
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
Click to expand...
Click to collapse
I'm not sure, but I don't think resetting these puts them back to 100% if rooted, the root stays since it sits in /system. You'll have to manually remove SU then reset to get rid of the root, I think. Other option is restore through the update.zip method which should wipe /system. You could try a hard reset and see if it removes SU or not, it might.
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
NeO_CooL said:
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
Click to expand...
Click to collapse
Not quite clear on what you're asking, but as far as I know it should work on any version bootloader unless they changed it on some update, which wouldn't surprise me.
What is the whole message, and when is it occuring?
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
NeO_CooL said:
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
Click to expand...
Click to collapse
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Forgot to say i´m using the windows version.
Thanks
pio_masaki said:
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Click to expand...
Click to collapse
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 (not unlockable) bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
smokku said:
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 not unlockable bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
Click to expand...
Click to collapse
It's just labeled a100, it isn't the actual a100 blob. But go ahead and use that link until I get the chance to go back through it, I'm obviously messing it all up somewhere, I may have used the a100 blob and gotten it mixed up with the a200 blob when I was renaming and shifting things around. I'll pull the download for now until I get the chance to get it all sorted out, sorry guys.
Edit OK its back up with the proper boot loader for unlocking. I can't believe I did that. Huge thanks to smokku for pointing that out!
No worries.
And yeah, you have to be quick when it asks to toggle unlock, like half a second quick.
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
my Xperia Play R800i will not turn on anymore after i tried to flash a rom... i dont exactly remember which one it was... i hope its not important
what my phone does is showing the Sony Ericsson logo and just stays there... i had it on the entire day just be sure that i wasnt doing something in the background or anything ...
but i never did it on my phone yet... (maybe better if never did this now i think of it)
but anyway pc companion says "null" and thats all it will say further it cannot detect my phone or do anything with it
i hope flashtool works if anyone is willing to lead me through it.
i dont have warranty anymore.
MausHaxxi said:
my Xperia Play R800i will not turn on anymore after i tried to flash a rom... i dont exactly remember which one it was... i hope its not important
what my phone does is showing the Sony Ericsson logo and just stays there... i had it on the entire day just be sure that i wasnt doing something in the background or anything ...
but i never did it on my phone yet... (maybe better if never did this now i think of it)
but anyway pc companion says "null" and thats all it will say further it cannot detect my phone or do anything with it
i hope flashtool works if anyone is willing to lead me through it.
i dont have warranty anymore.
Click to expand...
Click to collapse
Would you happen to have a custom kernel? Which Sony Ericsson logo is it, the non-moving one or the animated one?
Now, you wouldn't have happened to install a CyanogenMod, Ice Cream Sandwich or Jelly Bean rom, would you? I know you don't remember which rom you installed, just trying to spark a memory. Anyway, if you did so, then all you need to do is flash a compatible kernel. You see, if the Sony Ericsson logo you are seeing is the non-moving one, then you have the stock kernel, the one that's incompatible with the aforementioned roms.
If you don't want to get involved with this kernel business, then I've provided a Flashtool guide, so you can at least get your phone to a working, albeit factory reset, state:
First, install Flashtool.
Go here and find what you think your stock firmware was, download it.
Place the .ftf file in your Flashtool/firmwares directory.
Open Flashtool (as administrator if necessary) and click on the lightning bolt in the Flashtool window. Highlight Flashmode and select OK. A new window shall pop-up.
Select your downloaded firmware. I should read "R800i" in the first box and "4.0.2.A.0.XX" (with the "XX" being the number of the version you downloaded) in the second, the contents of the third box varies, so disregard it. There are many options for what to keep/replace during flashing, but I'd recommend leaving them as they are. Select OK. The window will now close and a new window will pop-up shortly after.
This window will detail the proceeding steps: With your turned-off phone (make sure its battery is intact), hold the back key (the leftmost one) while inserting the usb from your computer to your phone, continue holding the key until the window closes, DO NOT REMOVE THE USB.
The Flashtool window will now begin streaming various lines detailing its progress, all you need to look for is the line detailing a successful flash which with then tell you to disconnect your phone, now you can remove the USB.
Go ahead and close the remaining Flashtool window, your phone should now be back to default, factory reset, everything except your phone's bootloader and SIM unlocked statuses, they should be how you left them before.
thanks!
Toasty Clown said:
Would you happen to have a custom kernel? Which Sony Ericsson logo is it, the non-moving one or the animated one?
Now, you wouldn't have happened to install a CyanogenMod, Ice Cream Sandwich or Jelly Bean rom, would you? I know you don't remember which rom you installed, just trying to spark a memory. Anyway, if you did so, then all you need to do is flash a compatible kernel. You see, if the Sony Ericsson logo you are seeing is the non-moving one, then you have the stock kernel, the one that's incompatible with the aforementioned roms.
If you don't want to get involved with this kernel business, then I've provided a Flashtool guide, so you can at least get your phone to a working, albeit factory reset, state:
First, install Flashtool.
Go here and find what you think your stock firmware was, download it.
Place the .ftf file in your Flashtool/firmwares directory.
Open Flashtool (as administrator if necessary) and click on the lightning bolt in the Flashtool window. Highlight Flashmode and select OK. A new window shall pop-up.
Select your downloaded firmware. I should read "R800i" in the first box and "4.0.2.A.0.XX" (with the "XX" being the number of the version you downloaded) in the second, the contents of the third box varies, so disregard it. There are many options for what to keep/replace during flashing, but I'd recommend leaving them as they are. Select OK. The window will now close and a new window will pop-up shortly after.
This window will detail how the preceding steps: With your turned-off phone (make sure its battery is intact), hold the back key (the leftmost one) while inserting the usb from your computer to your phone, continue holding the key until the window closes, DO NOT REMOVE THE USB.
The Flashtool window will now begin streaming various lines detailing its progress, all you need to look for is the line detailing a successful flash which with then tell you to disconnect your phone, now you can remove the USB.
Go ahead and close the remaining Flashtool window, your phone should now be back to default, factory reset, everything except your phone's bootloader and SIM unlocked statuses, they should be how you left them before.
Click to expand...
Click to collapse
Thanks, i will try this when im home tonight
i will tell you if i got it working again lol (ps. i aint a noob... i never got freezings before... i was just being cautious so i wont break it behond repair LOL)
ALMOST fixed
ok it works again now. but now it asks me to download settings ... which it fails in... my phone tells me that it failed and asks me to retry downloading them.... which eventually will fail again... i got wifi on ofcourse (duh...)
anyway... i dont get it why i am having so much trouble with my phone.... my tablet i can hack without hassle... i just never used flashtool XD
always cmd and such...
anyway im almost there to have it completely fixed
thanks so far
MausHaxxi said:
ok it works again now. but now it asks me to download settings ... which it fails in... my phone tells me that it failed and asks me to retry downloading them.... which eventually will fail again... i got wifi on ofcourse (duh...)
anyway... i dont get it why i am having so much trouble with my phone.... my tablet i can hack without hassle... i just never used flashtool XD
always cmd and such...
anyway im almost there to have it completely fixed
thanks so far
Click to expand...
Click to collapse
Okay, having not used stock in a long time, I've reverted my rom and kernel! Upon doing so, I noticed little wrong. Though I do remember an annoying prompt when I opened the browser, it'd say "Please insert SIM card" and "downloading settings" would pop-up following it.
Aside from that, I can't recreate the problem you're having. Could you go into more detail?
screen photo
Toasty Clown said:
Okay, having not used stock in a long time, I've reverted my rom and kernel! Upon doing so, I noticed little wrong. Though I do remember an annoying prompt when I opened the browser, it'd say "Please insert SIM card" and "downloading settings" would pop-up following it.
Aside from that, I can't recreate the problem you're having. Could you go into more detail?
Click to expand...
Click to collapse
here is the popup that i get all the time.... while i CAN call people and receive calls... my phone refuses to use 3G which i do need...
MausHaxxi said:
here is the popup that i get all the time.... while i CAN call people and receive calls... my phone refuses to use 3G which i do need...
Click to expand...
Click to collapse
Well... That's something I have never seen before...
Searched the Q&A and troubleshooting section, and I'd found a thread detailing such an error upon switching firmware. No offence but perhaps I didn't give you enough detail on which firmware to download, and for that I apologise.
Would you happen to know what branding your phone is, and post what it is and which firmware you installed (you can find said information in that third box I told you to ignore in Flashtool)? AT&T, Verizon, unbranded/no SIM/unlocked? I ask this as you may have installed incompatible firmware.
As an example, my phone was unbranded and came with no SIM, the pre-installed installed firmware (and the only one that I find to be fully compatible) was the R800i 4.0.2.A.0.42 UK Generic. In the context of stock roms, I find that it's best not to stray.
Anyway, you've probably already figured out what to do: find the intended firmware and flash it, using the instructions above. I'd recommend gathering some more outside help, changing the thread's title to reflect the current conundrum should be a good starting point.
will do
Toasty Clown said:
Well... That's something I have never seen before...
Searched the Q&A and troubleshooting section, and I'd found a thread detailing such an error upon switching firmware. No offence but perhaps I didn't give you enough detail on which firmware to download, and for that I apologise.
Would you happen to know what branding your phone is, and post what it is and which firmware you installed (you can find said information in that third box I told you to ignore in Flashtool)? AT&T, Verizon, unbranded/no SIM/unlocked? I ask this as you may have installed incompatible firmware.
As an example, my phone was unbranded and came with no SIM, the pre-installed installed firmware (and the only one that I find to be fully compatible) was the R800i 4.0.2.A.0.42 UK Generic. In the context of stock roms, I find that it's best not to stray.
Anyway, you've probably already figured out what to do: find the intended firmware and flash it, using the instructions above. I'd recommend gathering some more outside help, changing the thread's title to reflect the current conundrum should be a good starting point.
Click to expand...
Click to collapse
if i cant obtain the required info i need i will make a new post regarding this issue...
but thanks to you for getting my phone to a working state
ps. i will post here if i got the 3G back to work or not using the thread you supplied.
fixed
MausHaxxi said:
if i cant obtain the required info i need i will make a new post regarding this issue...
but thanks to you for getting my phone to a working state
ps. i will post here if i got the 3G back to work or not using the thread you supplied.
Click to expand...
Click to collapse
it was simply the APN settings....
how could i know xD never had this error before... anyway it works fine now 3G works smoothly
MausHaxxi said:
it was simply the APN settings....
how could i know xD never had this error before... anyway it works fine now 3G works smoothly
Click to expand...
Click to collapse
Oh, sorry about that. I'd only ever experienced an APN problem when one of the roms I had installed had a broken settings app.
Anyway, it's nice to see that you've fixed your phone yourself, congrats!
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.
Yes, it's me again. Yes, I have written about this already. Yes, still the same problem.
So, as some of you may know, I have a huge problem with flashing TWRP. No matter how hard I try, no matter what my pc OS is, I get this problem every time, when I try to move from official MIUI to any other ROM.
At this time I'm using Ubuntu 18.04 LTS, but it gets to the same point as on Windows. I reboot to bootloader via ADB, my device is on fastboot devices list, and when I enter 'fastboot flash recovery twrp.img' or 'sudo fastboot flash recovery twrp.img' - nothing happenes. Terminal is like frozen, there is no information what's going on (no sending recovery). When I had Windows, I used to reset (to be clear - format) my PC, and then it worked for some time. Theoritically I could do the same with Ubuntu, but hey guys, I think we can all agree that it shouldn't work like that, should it? Right now, the only way for me is to root my phone first, then it would be easy. But guess what! Root requiers TWRP, TWRP requiers root. Annoying LOOP.
I'd be really thankfull if someone answered this thread, even wrong, trying is what counts, right?
Download TWRP app and try flashing using the app. Never tested it. Your best bet run window simulator on PC or go library or use someone's computer. Takes like 1 min to root. I have bricked my phone million times already, piece of cake to bring it back to life.
Asheque said:
Download TWRP app and try flashing using the app. Never tested it. Your best bet run window simulator on PC or go library or use someone's computer. Takes like 1 min to root. I have bricked my phone million times already, piece of cake to bring it back to life.
Click to expand...
Click to collapse
To flash TWRP via app I need root. And I see no way to root my phone. But the windows emulator sounds like a good idea Gonna try that. And I have tried on my brothers computer one day, didnt work
Hilus said:
To flash TWRP via app I need root. And I see no way to root my phone. But the windows emulator sounds like a good idea Gonna try that. And I have tried on my brothers computer one day, didnt work
Click to expand...
Click to collapse
Go on your brothers computer, download TeamViewer. Message me and I can do it for you.
Asheque said:
Go on your brothers computer, download TeamViewer. Message me and I can do it for you.
Click to expand...
Click to collapse
Right now I am making a bootable windows, to see if this works. If it fails I'll text you
Hilus said:
Right now I am making a bootable windows, to see if this works. If it fails I'll text you
Click to expand...
Click to collapse
Sounds good. Very easy once you have it setup. Keep in mind you have to reinstall TWRP and root every time you update MiUi OS. For me the global update is like every Friday so I have to reinstall TWRP and Root every week.
Asheque said:
Sounds good. Very easy once you have it setup. Keep in mind you have to reinstall TWRP and root every time you update MiUi OS. For me the global update is like every Friday so I have to reinstall TWRP and Root every week.
Click to expand...
Click to collapse
After some time, I gave up. Last hope was to try one more time on my brother's PC, and luckly - it worked. Everything ended good for me, but I still don't get it why sometimes my PC decides to go along and work with me and sometimes it just doesn't care. I am aware that flashing official MIUI wipes custom recovery, that's why I usually don't come back to it from any other custom ROM. Anyway, I'm really thankful for your help Asheque, thanks for all advices, and I think one day I will come back exactly to this thread and read them again. Appreciate it!
Hilus said:
After some time, I gave up. Last hope was to try one more time on my brother's PC, and luckly - it worked. Everything ended good for me, but I still don't get it why sometimes my PC decides to go along and work with me and sometimes it just doesn't care. I am aware that flashing official MIUI wipes custom recovery, that's why I usually don't come back to it from any other custom ROM. Anyway, I'm really thankful for your help Asheque, thanks for all advices, and I think one day I will come back exactly to this thread and read them again. Appreciate it!
Click to expand...
Click to collapse
I am glad it worked out Make sure you install Magisk apk and flash Magisk.zip for root access and pass safetynet if you want to use Google Pay. Also, highly recommend you download GBoard Theme module from Magisk. It's the best, makes Google Keyboard freaking awesom.
Asheque said:
I am glad it worked out Make sure you install Magisk apk and flash Magisk.zip for root access and pass safetynet if you want to use Google Pay. Also, highly recommend you download GBoard Theme module from Magisk. It's the best, makes Google Keyboard freaking awesom.
Click to expand...
Click to collapse
Thanks so much, I'm gonna try it out