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.
Related
PREPARATION STEP! download sgs kernel flasher from the market (must be rooted I believe) and do a kernel backup as this process changes your kernel.
SPRINT TAB INSTRUCTIONS THAT WORKEDFOR MANY SPRINT TAB OWNERS. IT MAY NOT WORK FOR YOU!
Ok here it is, Thank koushs for this product, cruiserbax for his awesome instructions and Benjamin Dobell for giving up Heimdall flashing utility and install instructions.
I NOR THE ANYONE LIST ABOVE ARE RESPONSIBLE FOR THIS NOT WORKING!!! OR ANY DAMAGE IT MAY DO TO YOUR TAB!!
To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechidna.com.au/products/heimdall/ <--------click on the binaries link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechidna.com.au/products/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab.
when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab.
Source:
http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Yes, I tried this and it works great but be aware that certain kernels seem to mess it up.
Which Kernel Seems To Work The Best?
@ lloydcabraham
Which kernel is the most stable?
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
I'll have to try this soon.
IP IHI II IL said:
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
I believe the build being worked on right now in here is based on a cdma device...
Not off topic at all. THE ONLY HC port is currently being built by spacemoose (reading more than one thread on one website helps) and that wasn't the focus of my question. Please read before you quote/insinuate. Don't wanna be tagged with the troll label...
cdguider said:
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA Premium App
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
cdguider said:
@ lloydcabraham
Which kernel is the most stable?
Click to expand...
Click to collapse
I like Bauxite but you will get a flaky camera (Sometimes won't initialize without reboot) and seems to mess up CWM (Although redoing these steps fixes it) but I do love running @ 1.4 super stable!
cdguider said:
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11780452&postcount=1
3/26/11 #2:...Second... The "dirty" port will be for CDMA devices, but as soon as the CDMA version is released I'll look into getting a GSM version out asap. Shouldn't be hard. Instead of using my own kernel for this one, I'm using a modified version of Boushh's kernel and can probably hack together a suitable kernel for other devices as well. My own kernel for the larger project is still in fluctuation as I have to make changes to suit the build on a regular basis, but when I finalize that kernel I'll release it as an update and it will get a repo of it's own.
Click to expand...
Click to collapse
The quote was for what?
Re-read it one more time...
Really
I still stand by my message.
It's also apparent you didn't go back to page 1 otherwise you would have known I acknowledged spacemoose1 Honeycomb Port.
Despite someone working on Honeycomb port for Sprint / CDMA devices.
Chances are someone else is working on it for GSM, as with damn near anything, GSM devices will most likely get it first,
KEYWORD: most likely, and if you read the previous post - keyword is chances are
Bottom line is who cares who gets it first.
I'm well aware of most developments going on XDA
can u guys just drop it already!
Ok im stuck I followed steps but I am stuck at the samsung screen won't boot into recovery I don't know what I did wrong... I need help I have it stuck! (sigh) uSING hEIMDALL It isn't specific on which box I should use the zimage in which box using heimdall... I used it in the recovery under other made sure the box was checked. It ran through backups 2 times then looked like it was launching into recovery cwr 3.0 but when I picked it up it turned off when I turned on all I get is the samsung logo FOREVER... I have tried using heimdall again and tried to use it under FACTORYFS but same result. Please help. All I have now is a Huge Expensive Paper Weight. HELP
*** Ok after further review *SIGH* I understand I probably should have studied the damn thing better there is an option for zImage there... So how bad did I mess this thing up and is there a way to UnDue what I have Done?
Update-
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Thanks for the link... Will give it a try.
Really don't know what to say about the error message, My tab was messed up with errors like can't mount....., some other stuff, I had to send mine in to get replaced, never would go past the samsung logo. At the time the only thing Sprint users had was the Stock DJ30 With Modem.
Now we have no modem.
EA24 Stock
Ext 4
Honeycomb Port In Progress.
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
Before I tried that I loaded the Honeycomb ROM well it isn't but the Khasmek's AOSP beta 1 and it worked everything working but the real question is what to do now... If I reboot does it load agian? Should I use Rom manager and run a recovery Backup? what would you advise?
****Update
So after getting everything setup I tried to do a boot to recovery through Rom Manager and low and behold back to dreaded SAMSUNG screen with NUTIN happening. Will try your steps next
****Update
After following steps and flashing image with odin... I was able to boot up fine... Downside---> My Verizon tab is now a Sprint Tab ... I need to find the .tar for VZW anyone? ANYONE? *SIGH*
NOTE: This one's a big one if you can't tell! Everyone give a round of applause to simonsimons34 for tracking down the issue. What does this mean? Well, there may not be a need to ever downgrade using the RUU. If you go here (you really can't miss that big, bolded "here"), you will see that he determined the issue is caused by:
a bad battery driver function in the kernel
Click to expand...
Click to collapse
He also took the liberty of building a kernel compatible with 4.2 and putting in a commit for fixing the kernel to work with the newer radio at GitHub. Any ROM builders who see this, please do check it out. As far as everything goes, I haven't personally tested it but I do always encourage people to try it out. Simon has been a great supporter and kernel builder for our device so I have faith that he hath found the Holy Grail. 'Course my thread will have no more existential purpose, BUT it is a great resource so as it is, I will leave it up for the general perusal of the community. Have a great week everybody and I look forward to a new flood of development.
Exciting news y'all! This thread has been stickied! [Hopefully] this will allow continued support and growth of the thread. My personal philosophy is that anything I post shouldn't be locked down to what I know or believe in, so I encourage any reader to put forth their input. What does that mean? It means that if you have a suggestion, by all means inbox me your thoughts. I'm open to continual development of this tutorial through community teamwork. Have a good day everyone!
-------------------------------------------------------------------------------------------------------
Here are some common reasons why your phone will randomly reboot (bootloop). You should only use an RUU (the methods below the "=" signs) if NOTHING ELSE WORKS (because the RUU does a factory wipe of the phone).
Common Problems:
I switched from another ROM and now my phone keeps rebooting...
There are several factors in play here. The commonly accepted fix is backing up your data and doing a full wipe (cache, dalvik cache, system, data) followed by reflashing your ROM.
I upgraded my ROM from blah blah version to blah blah version (ex. 4.0.x to 4.1.x)...
This is because your old Ice Cream Sandwich system stuff may not be compatible with JellyBean (in the case of the example). Wipe system and the caches (dalvik & cache) followed by reflashing your ROM.
I upgraded my ROM (within the same version) and it keeps rebooting...
Every time I upgrade my ROM, I wipe cache. If something funky happens, just wipe system and reflash your ROM.
I flashed a ROM and it won't boot at all...
Either you flashed a ROM for a different device, you flashed a kernel for another device, OR you didn't flash a kernel at all. Make sure everything is for your phone (the HTC One V on Virgin Mobile is the CDMA version known as "PrimoC" whereas the GSM version is the "PrimoU").
=============================
NOTE: This guide is for the One V!
I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.
A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience
The following quote is from CafeKampuchia's thread over here.
NOTE ABOUT THE FOLLOWING PARAGRAPH: jmztaylor's site is now legally able to host the RUUs again so the download link is right here*
In support of jmztaylor and all of his work for this device, I have decided to also include his website in this thread... *here is the download directory for the HTC One (Primo) device RUUs. I'm not sure if this bug effects other Primo devices, so this especially pertains to the PrimoC (HTC One V CDMA). Thanks jmz for the tip!
Solution #1
CafeKampuchia said:
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")
Run this command:
Code:
fastboot oem rebootRUU
Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).
As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:
Solution #2
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Won't work if the ota is already applied from the factory.
cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
You need to downgrade your radios or your guide will be useless no matter what, i followed this post i found on android forums and it worked
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
robaho said:
Won't work if the ota is already applied from the factory.
Click to expand...
Click to collapse
Or if you applied the OTA via the popup window saying, "Blah, blah, blah, new update available."
Thank you so much for this. I will try it when I get home. Ever since I applied that OTA battery update, I haven't been able to successfully run any other ROM that I have tried. Hopefully this will be the solution that I have been looking for.
Just out of curiosity though, I have a Nandroid backup of before I applied the OTA Rom. If I restore that backup, would that do the same thing as you provide here, or would I definitely have to go through this process?
Won't work. The radio partition cannot be backed up/restored unless you have an s-off device.
Why not point to htcruu.com no premium acct necessary or wait times
Sent from my One X using xda premium
Moved to General section.
I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.
mastertr said:
I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.
Click to expand...
Click to collapse
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...
mastertr said:
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...
Click to expand...
Click to collapse
Did you relock the bootloader before or after flashing PK76IMG.zip? This does make a difference. My suggestion is just to go back through and try again following everything to a tee. Doesn't always work the first time.
I went with your first solution this time and followed the directions step-by-step and it was a success. I am now running AOKP 10 without any boot loop. Thanks!
Bump
It worked thank you
thanks man followed your guide and boom everything went just fine.
1st i had 1 minute problem. now i dont have any.
i confirm that anybody having 1 minute problem can solve it with this tutorial:laugh::laugh::laugh::laugh::laugh:
thanks
Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA
BobbaLouie said:
Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA
Click to expand...
Click to collapse
check ur version
settigs->about >software version
Is the Sprint RUU the one that works on Virgin Mobile?
Euler MD said:
Is the Sprint RUU the one that works on Virgin Mobile?
Click to expand...
Click to collapse
Yes
Sent from my One V using xda app-developers app
Thankyou for this guide. Even though I followed the steps, it didn't work. Maybe it was just my luck but I'll try again soon.
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Can you boot in to recovery or bootloader (holding power+vol down)?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
That I can
mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Put the stock odexed rom from my thread in development section in your adb/fastboot directory on your PC.
Enter Recovery, assuming you installed a custom recovery.
If not, do that first, using the links in Flyhalfs threads in our Verizon One Original Dev section.
In Recovery go to Advanced in TWRP I believe and do adb sideload > swipe to sideload.
Then you will need to enter in terminal: adb sideload filename.zip from within the fastboot directory with the stock file in that same directory.
Use the filename of the zip you are sideloading. Once its done pushing, it will flash the rom and then you can reboot.
I had tried straight off after the root to install CWM and it gave the option to do TWRP. I had a blank black screen and then kind of stalled so I forced it into the bootloader screen and just reset. In the present time if I attempt the recovery selection it just stalls again, a black yet obviously backlit screen. My new download of ADB does not look the same as it had when I did the last phone either. I don't know what I've fouled up here.
I'll send it out at this point to make the pain go away and have someone undo it.
mySStery_machine said:
I'll send it out at this point to make the pain go away and have someone undo it.
Click to expand...
Click to collapse
I can try and walk you through getting fastboot or adb set up so that you can try fixing it on your end.
It's also pretty well laid out in guides on Google.
If you really wanted to have it fixed for you, I'm about 12 hours or so south of where you are if you wanted to mail it here and back.
Up to you, hit me up via PM if you decide you wanna mail it.
Otherwise, myself and/or others will gladly help you undo it I'm sure man.
Then you wouldn't have to be without it for a few days.
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
mySStery_machine said:
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
Click to expand...
Click to collapse
Sounds good, I'll shoot you my gmail/Hangout info and we can get you squared away I'm sure.
Yeah, I'm up above there just a little, about 2 and a half hours or so from there.
Sounds good, I'm ready to tackle tonight whenever and for however long it takes.
Ok, have deleted and redownloaded the ADB files, yours as well as the TWRP. I have the recovery and your file chilling out in C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools . What now my new found savior?
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
mySStery_machine said:
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
Click to expand...
Click to collapse
Double check the md5 of the downloaded file.
Also shorten the path to the file, at least the folder names leading up to it, so that it's more direct.
Less chance of error or too deep of a path.
Something Like:
C:\Android\sdk\sdk\platform-tools>adb sideload 1.10.605.15_Deodex_Full.zip
Click to expand...
Click to collapse
You will have to rename a directory and a file or so to get it like that and this may not be the issue, but should certainly eliminate potential for issues.
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
mySStery_machine said:
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
Click to expand...
Click to collapse
Yeah try that, you may need to grab HTC Sync and install it if you haven't if your existing drivers aren't cooperating.
MD5 was corrupt, I finally got it to push.
Used pdaNet for drivers.
mySStery_machine said:
Used pdaNet for drivers.
Click to expand...
Click to collapse
Cool, glad that worked.
If you have any further issues or success, let me know.
Sounds like you should be good to go though.
Downloading another version to see if I can get the info across and get this One cooking again!
So should I do the other .zips below the post with your links for the firmware?
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Probably drivers. Just manually boot into bootloader.. And then flash the factory image.
Sent from my Galaxy Nexus using xda app-developers app
Fastboot reboot-bootloader command will only work if you are already in the bootloader mode anyways...
As @mrgnex said, just do it manually, or use adb commands to boot into bootloader where THEN you use fastboot command.
To manually get into bootloader/fastboot mode; power down, then hold power button and volume up AND down all at same time for few seconds, it'll vibrate and you'll be in the bootloader mode where u can issue the fastboot commands.
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
You don't actually move the factory images onto your phone.
One of the sticky threads here is called "return to stock". That should guide you in the right direction.
Sent from my Galaxy Nexus using xda app-developers app
huzzug said:
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
Click to expand...
Click to collapse
it's great that you're learning to do this Droid life has a good howto, just google "droidlife how to root galaxy nexus"
if worse comes to worse you can use this toolkit that does it for you, it's called wugfresh google "wugfresh nexus toolkit"
If you want to install ROMs you download the zip right on your device (make sure you get a ROM zip file AND a gapps zip file. They are linked in pretty much every OP for ROMs)
Downloading a ROM zip directly from/on device is easiest because then you do not have to transfer the file(s) over to your device in order to "flash"(aka install). Then all you do is go into recovery mode. Then go to install, then choose your ROM zip file. After that installs, then install gapps file the same way, always install gapps zip AFTER the rom zip.
If you use TWRP as your custom recovery you can "queue" your zip installs(choose rom zip and then you can choose to add another zip file and it will flash them both for ya)
And usually it is recommend to do a factory reset from recovery before you reboot into system. (Make sure to not wipe ALL /data...choose factory reset...wiping ALL /data will wipe /sdcard contents as well)
This all might seem foreign and difficult at first, but once you've done it once or twice(or more... you might become what we call a "crack flasher"-one who is constant changing ROM and kernel and setups lol, that's when it gets REALLY fun) so do not get discouraged. Especially if you don't understand the terminology we all use, you will become familiar with it quickly. And remember, Google is your best friend, almost any questions you might have will yield MANY helpful results when you put in a Google search, highly recommend that if using Google for trying to get useful info to put things like "how to install custom recovery "Galaxy Nexus" xda" to get the best info possible )
And do not be afraid to ask us either if you feel lost. It's easier to prevent an issue than to fix it(though fixing a borled Gnex is fairly easy with all the tools available here and elsewhere)
As for going back completely to stock, as mentioned above, to do that you aren't putting any files onto your device itself. You download them to PC(I use my laptop) and install from there using fastboot. When you download the factory img that is for your specific device and unzip it (I believe they still come compressed... If not ignore that part sorry!) You will see inside there is a script called "flash-all.sh" OR if using windows use the "flash-all.exe" that will automate the fastboot commands needed for a full factory stock restore of the device.
I could link you to posts containing useful how-tos and info and such, but right now I'm viewing forum via Tapatalk app on my device and really gonna be lazy and just say look at the "Sticky posts" in General, Q&A, and Development sections, those are most likely what I would link to you here.
After reading through some of those, if you need clarification of steps taken or something, come on back and let us know.
huzzug said:
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Click to expand...
Click to collapse
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
SolGoodGuy said:
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
Click to expand...
Click to collapse
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
ashclepdia said:
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
Click to expand...
Click to collapse
I see an optimus G on swappa for $115. Much better phone.
Actually, I ain't in US guys. And whatever I found was a personal preference as I wanted this model and not any other.
Bumpity bump
huzzug said:
Bumpity bump
Click to expand...
Click to collapse
Bump?
Did you ever try what I said?
You need to download the factory img needed and run the flash all script...
Edit::
HERE go to this thread.
http://forum.xda-developers.com/showthread.php?t=2726518
Follow my advice there, except make sure to grab maguro img for your device. Be sure to grab the correct package for your device (takju yakju, etc...it will tell u in bootloader mode which one u have)
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.