Related
First things first...
Credits:
Mast3rpyr0 - Original creator of a simple one click root. Most the code used here is based on his work with some tweeks. [ Link ]
webs05 - For the outstanding help he has provided to those who were having issues using Simple Root!!! Thanks!
toastcfh - For root and nand unlock. [ Link ]
Koush - Recovery image [ Link ]
maejrep - For helping with the code to remove sendkeys!! Thanks alot!!
If I forgot anyone that I should have mention, let me know....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Automatic updates and create update patches with wyBuild.
After hours of trying to figure out a way to make Mast3rpyr0's batch files work correctly, I noticed it had problems sending certain commands. So I decided to use some of his batch file codes, and create a VB.NET application along with batch files. I have unrooted and rooted my personal phone multiple times trying to get this to work. I tested the app 3times!! Each time Unrooting my phone! All three times its has been successful!
What exactly does this do?
Exactly what it say, Root your EVO in 3 Steps.
How do you use it?
Make sure your phone is on USB Debug mode. (MENU > Settings > Applications > Developement > USB debugging = Checked ) Click the buttons starting from Step 1.
Why the large file size?
This includes all the .img and .zip files that are needed to root. (2 PC36IMG.zip @ ~ 170MB = 340mb) and a couple of other smaller files. I decided to add them to make things more simple and avoid having to explain where to get these files.
Youtube Example
sorry for all the video splits...not my fault, blame youtube.
Video quality might be bad, give them a few to process 720p version
Part 1-1 - http://www.youtube.com/watch?v=GAqTEAWxh7U
Part 1-2 - http://www.youtube.com/watch?v=578jDEJ6M_c
Part 2-1 - http://www.youtube.com/watch?v=I-FbYqPOrpg
Part 2-2+3 - http://www.youtube.com/watch?v=qk7lBDpSp-A
AndroidPolice.com Review + Tips
Download:
Megaupload - had to put this up, account suspended due to the amount of downloads =( they want my to go dedicated smh...
Official Page | Full (Download this if you never used this program before)
If you have downloaded this program before, please read this
Note: Its recommended to flash a custom ROM. Reason I say this is because for whatever reason, the eng-image doesnt allow proper SU permission!!
Requires: Dot Net Framework 4 and HTC SYNC
I would try it if I didn't fully root yesterday. But props to you guys for putting that together. Seems like a one step jailbreak. Very nice.
WOW! Great work. This will unlock NAND too? If so you might want to update your thread title....
jiqqaman said:
First things first...
FOLLOW THE DIRECTIONS!! IF IT SAYS DONT MOVE YOUR MOUSE, DONT CLICK ANYTHING, DONT TOUCH YOUR KEYBOARD... THEN DONT!!!!
The reason for this is because for some reason a batch file cant send the command
Code:
adb shell cat sdcard/flash_image > /data/flash_image
The only way I found to get around that was using Sendkeys. I know, send keys is lame, and poor programming, but its the only way that I could get this to work.
Basically, Sendkeys sends keystokes to a targeted window, as if you were typing. You might see your keyboard NumLock, Caps light blink while this is being used, which is perfectly normal. (Enjoy the light show)
Click to expand...
Click to collapse
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
this is amazing. too bad noobs like myself could not wait to root and unlock nand. but the process was well worth it. great job, i hope this save someone a headache
Re: [Program] SimpleRoot .1 ---- 3 Click Root!!
smw6180 said:
That's because the windows shell interpreter parses the redirect as belonging to the Windows system, not the android system. So it's trying to redirect the output to c:/data/flash_image or some such nonsense. Since Windows doesn't do / for it's directory structure, but instead uses \ it gacks trying to find the directory to put it in (which would be wrong even if it worked, since it would be on your hard drive, not the phone). You can change the cat line to this:
Code:
adb shell cp /sdcard/flash_image /data/flash_image
and it should work just as well. Anytime you use a redirect in a batch script like that it's going to try and redirect to Windows. If it wasn't my day off and I wasn't so tired I might figure out a fix for that, but the code I posted above should do the trick well enough. I wasn't sure initially why people wanted to to read the file into another one in the first place, but I did it with cp when I rooted and it worked fine. I suggest testing it, and then possibly changing your program. That way you can get rid of sendkeys and people breaking root by clicking something when it's running
Click to expand...
Click to collapse
Thanks, I'll see how that works later on, and if it works ill just upload a zip file with the updated code. Don't like the whole sendkeys thing,...I'd like to figure out on making it work without batch files... but I no pro code lol
Sent from my HTC EVO using Tapatalk
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
It wont hurt to re-root just run the whole thing. make sure you backup of course
thanks OP great work I'm sure it will get even better and easier once you get rid of key presses
STICKY!!!!
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Damn after I followed the 50 step-by-step and wish I had seen this earlier nice work might try this on my older bros in a few days
Sent from my Sprint HTC EVO 4G. via tapatalk
cmdauria said:
If I am already rooted can I skip right to Unlock Nand? I did root using the toast method.
Click to expand...
Click to collapse
Yes, but you must run on the pushfiles.bat file before you goto step 2.
CYBERxNUKE said:
would you mind just posting a zip with the main files and not the roms?
im running low on space and wouldnt mind saving 300 megs
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N6GV5NNP - no .img or .zip files
make sure you have the first PC36IMG.zip from the first root tutorial and the 2nd PC36IMG.zip from the nand unlock rename it eng-PC36IMG.zip or else you'll break it =(
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
OP theres an updates restore image much better options from armon .02 works for people who have bad sectors ALLOT of us have
but 01 is for those who dont try that first
http://forum.xda-developers.com/showthread.php?t=705026
ken987 said:
Hi,
If I do this method will I be able to load custom Roms following these steps? I found these on another site and I am a noob so this one step thing would be great for me to get my feet wet...but the whole reason I would root is so that I could try another ROM...
Here are the steps I found...earlier it said I needed adb and sdk tools so I'm not sure if below will work if I don't have that installed on my computer.
Choose a ROM you want to try. Download it and save it to your computer (do NOT extract it, leave it as a .zip)
2. Plug the phone in via USB cable and mount the sd card so we can transfer files to it.
3. Copy the ROM .zip file and save it to the root of the sd card (NOT in any folders just on the sd card itself). Once it is done copying, unplug the phone from the usb cable.
4. Turn off the phone, then turn it back on by holding down Volume Down and Power until the white bootloader screen comes up (if it finds the PC36IMG.zip on your sd because you didn’t delete it, just say NO when it asks you if you want to update). Now using the volume buttons select Fastboot, then select Recovery and wait for the phone to boot into recovery mode.
5. Scroll to Wipe Data, select wipe data/factory reset and then select wipe dalvik cache.
6. Now scroll to Apply .zip from sd card and select the ROM .zip file we saved to the sdcard and wait for it to finish flashing. Once it is done, hit reboot and you are all set! Enjoy!
Click to expand...
Click to collapse
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
great job on making this easy guys.... To bad I couldnt wait longer than a week to root.
jiqqaman said:
1. The program includes adb, just download, unzip and run Simple Root.exe
2.Yes you will be able to install custom roms after you have completed the all the steps.
3. Those are not complete steps, but its sorta on the right track... have you done the first part of root?
Click to expand...
Click to collapse
Thanks for the quick reply. No, I am a new EVO owner and this is my first android phone. I was an iPhone user but I have come over to the Android side. No regrets. I have basically a new EVO with the OTA update installed. So my goal would be to run your one click method and then learn how to load roms. I also read that people have some kind of rom loader on their phone that sounded pretty easy so I need to do more searching on the forums here so I can learn.
Ken
This would have saved me 3 hours....
Thanks dude though this seems awesome.
Videos are titled "Hero 4g" btw.
Part 1 worked for me but part 2 doesn't. When I click yes on part 2 I get a screen that says "Unhandled exceptin has occured" and it gives me a option to continue or quit and I click continue and it closes out.
Does this method work if I already have the .6 stock rom on my device?
I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).
wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?
Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.
RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.
Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?
llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.
Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!
Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?
do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.
factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5
sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge
Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!
madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there
today i've tried to update my Honor 6 , but when the download terminates and the phone boot in to recovery, appear an error and it doesn't let me upgrade.
What can i do?
anyone else has found this problem?
P.S.
previously I did root, but now I removed root, restored recovery and relocked the bootloader :crying:
up
Same thing happened to me not rotted. I think I'm going to root any way as I want touchwiz
How I fixed my failing update to B370 (OTA) H60-L04.
I had the exact same problem. I got an error while doing the OTA update, even with a stock recovery.
Special Note: If you have an exFat SD-card you should remove or convert it to ext fs before proceeding. ex-Fat filesystem has been known to cause failure of the .img flashing steps.
Special Note 2: If you do not have B109SP01, ensure that you update to that version first before proceeding. This is since the OTA update.zip is an incremental/partial update and not a "full OS" update. It adds the EMUI3.0 and installs specific .img files, not a full Android.
Disclaimer: This method did NOT delete or remove any data for me, but I can not guarantee it will not change any data.
Ensure that you have a CWM/TWRP backup or any cloud backups of contacts/photos/SMSes and any other data
you need before you continue. Settings such as XPOSED and similar may be altered/modified or disappear, but
this is most likely due to temporary removal of root privilige during this upgrade AND the new updated
EMUI 3.0 rom you will receive.
Here's how I suggest you do:
1. Use the Multi-tool again and unlock your bootloader and root the phone again.
Install the universal ADB driver if you haven't previously.
Honor6 Multi-tool download here...
2. Download the following files:
Huawei Update Extractor
^^^Install this one, download setup version 0.9.8.0.
Official
Honor 6 B109SP01 Upgrade .zip file
^^^Extract this .zip file to a temporary folder.
3. Now comes the special part. First of all you need to run the Huawei Update Extractor.
Use the default "Unknown (worstenbrood)" profile and target/select the unzipped "Update.APP" file that should
be in the B109SP01 folder that you just extracted (In the "Honor6" subfolder).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Like the picture above you will only need to extract the RECOVERY.IMG and SYSTEM.IMG files.
Ctrl-left click to select and then right click and select "Extract selected".
(Note: you will also get two ".img.header" files created, those are not needed)
Extract the files to the folder for the Honor 6 Multi-tool where you have adb.exe/fastboot.exe since we will use those commands.
4. When you have done the above extractions (it can take a while for system since it is 1.35 GB) you need to start your phone in
FASTBOOT mode. Power Off your phone and press Volume Down and connect USB to computer
(while pressing down Volume Down) to enter fastboot mode. (Same as when you are unlocking/rooting the phone from scratch).
5. Now start a command/DOS window, As Administrator to ensure no restrictions. We are now going to enter a few commands with ADB.
Go to the path where you have adb.exe/fastboot.exe for the Honor 6 Multi-tool, using cd command eg.
"cd C:\Users\XXX\Downloads\HONOR_6___6Plus_Multi-Tool\HONOR 6 Multi-Tool". Use dir command to check that you have all
files you need adb.exe/fastboot.exe and RECOVERY.IMG and SYSTEM.IMG.
6. First issue the command:
fastboot devices
This will return an identity to show that you have your phone connected. If it returns empty, please check that your phone is
properly discovered and has the right driver (install from Multi-tool if needed). Redo the command until it is discovered
7. Next, issue the following command:
fastboot flash recovery RECOVERY.img
This will flash the stock RECOVERY.img from B109SP01. It will not take a long time.
8. And finally issue the last command:
fastboot flash system SYSTEM.img
This will flash the stock SYSTEM.img from B109SP01 and IT WILL REMOVE ROOT for the time being.
Ensure that this completes properly, since it is a 1.35 GB file it will take a while. Do not disconnect or disturb this activity.
It can take several steps and a few minutes to complete. Check that you really have a final "ready" and are back in the
command prompt before this is complete. Check the RECOVERY.img result for comparison.
9. When both steps above are completed fully you can now disconnect the phone.
Press the power button a 10-15 seconds to ensure it really shuts down from the FASTBOOT mode.
Then boot up the phone again.
10. This should boot up your phone and you should notice no difference now. Root is however gone so any apps/functions
depending on root will fail. This is actually good for now, this means that above steps have worked.
(XPOSED and other apps using root are not working, certain stock features/looks are "back".)
11. Go to the "System Update" function in the regular settings. Now run the OTA update to B370 as normal or
use the Local Update functions if you want to. Do the reboots and hopefully it will run 100% and not stop with a failure.
Please review and redo steps above if it still fails.
12. After reboot it will do the necessary "Updating applications" as any Android update.
When you boot into the phone the first time things will have changed (like background, some icons etc.) but your
apps and data should remain. You will also go through a small guide, about 3-4 steps (Language/regions settings etc.)
13. Do any necessary updates from Google Play store (if any pending). Also reboot the phone into FASTBOOT mode
and re-run the Honor 6 Multi-tool to root your phone again (if needed) and install CWM/TWRP (if you wish).
14. Voilá, you should now have a B370 EMUI 3.0 phone. Please note that certain apps may have changed or lost certain
locks/functions so I recommend that you reinstall those first. Also check your "default" SMS/Webbrowser/Caller apps etc
that you would like to use if you are not using stock Huawei ones.
I recommend you check out these links for any more detailed instructions per step if needed:
Honor 6 Multi-tool
^^^ Full of small and detailed info regarding the Multi-tool and other useful Honor 6 flashing/rooting/unlocking tips.
Huawei Update Extractor tool
^^^ More info on how to use the Update Extractor Tool. It works for H60-L04 .zip/.APP files also even if it is not mentioned in thread.
Full Restoration to Stock ROM
^^^ Only perform steps 1 to 5. Steps 6-7 will GUARANTEE that you loose your data/restore to factory.
Official Huawei Honor 6 download page
^^^ Contains the proper H60-L04 V100R001C00B109SP01 Upgrade Software file to use for the RECOVERY.img and SYSTEM.IMG
that I used for this guide and for the H60-L04 (international version).
Honor 6 H60-L04 OTA Update.zip B370/EMUI.30
^^^ This is the .zip file that is downloaded for the OTA update that I have used. Note: Location I am in: Sweden.
Can be used for the manual/"dload"-folder Local Update function.
Hope this solves the problems for you.
Thanks very much
sheapchit said:
I had the exact same problem. I got an error while doing the OTA update, even with a stock recovery.
Disclaimer: This method did NOT delete or remove any data for me, but I can not guarantee it will not change any data.
Ensure that you have a CWM/TWRP backup or any cloud backups of contacts/photos/SMSes and any other data
you need before you continue. Settings such as XPOSED and similar may be altered/modified or disappear, but
this is most likely due to temporary removal of root privilige during this upgrade AND the new updated
EMUI 3.0 rom you will receive.
Here's how I suggest you do:
1. Use the Multi-tool again and unlock your bootloader and root the phone again.
Install the universal ADB driver if you haven't previously.
Honor6 Multi-tool download here...
2. Download the following files:
Huawei Update Extractor
^^^Install this one, download setup version 0.9.8.0.
Official
Honor 6 B109SP01 Upgrade .zip file
^^^Extract this .zip file to a temporary folder.
3. Now comes the special part. First of all you need to run the Huawei Update Extractor.
Use the default "Unknown (worstenbrood)" profile and target/select the unzipped "Update.APP" file that should
be in the B109SP01 folder that you just extracted (In the "Honor6" subfolder).
View attachment 3131125
Like the picture above you will only need to extract the RECOVERY.IMG and SYSTEM.IMG files.
Ctrl-left click to select and then right click and select "Extract selected".
(Note: you will also get two ".img.header" files created, those are not needed)
Extract the files to the folder for the Honor 6 Multi-tool where you have adb.exe/fastboot.exe since we will use those commands.
4. When you have done the above extractions (it can take a while for system since it is 1.35 GB) you need to start your phone in
FASTBOOT mode. Power Off your phone and press Volume Down and connect USB to computer
(while pressing down Volume Down) to enter fastboot mode. (Same as when you are unlocking/rooting the phone from scratch).
5. Now start a command/DOS window, As Administrator to ensure no restrictions. We are now going to enter a few commands with ADB.
Go to the path where you have adb.exe/fastboot.exe for the Honor 6 Multi-tool, using cd command eg.
"cd C:\Users\XXX\Downloads\HONOR_6___6Plus_Multi-Tool\HONOR 6 Multi-Tool". Use dir command to check that you have all
files you need adb.exe/fastboot.exe and RECOVERY.IMG and SYSTEM.IMG.
6. First issue the command:
fastboot devices
This will return an identity to show that you have your phone connected. If it returns empty, please check that your phone is
properly discovered and has the right driver (install from Multi-tool if needed). Redo the command until it is discovered
7. Next, issue the following command:
fastboot flash recovery RECOVERY.img
This will flash the stock RECOVERY.img from B109SP01. It will not take a long time.
8. And finally issue the last command:
fastboot flash system SYSTEM.img
This will flash the stock SYSTEM.img from B109SP01 and IT WILL REMOVE ROOT for the time being.
Ensure that this completes properly, since it is a 1.35 GB file it will take a while. Do not disconnect or disturb this activity.
It can take several steps and a few minutes to complete. Check that you really have a final "ready" and are back in the
command prompt before this is complete. Check the RECOVERY.img result for comparison.
9. When both steps above are completed fully you can now disconnect the phone.
Press the power button a 10-15 seconds to ensure it really shuts down from the FASTBOOT mode.
Then boot up the phone again.
10. This should boot up your phone and you should notice no difference now. Root is however gone so any apps/functions
depending on root will fail. This is actually good for now, this means that above steps have worked.
(XPOSED and other apps using root are not working, certain stock features/looks are "back".)
11. Go to the "System Update" function in the regular settings. Now run the OTA update to B370 as normal or
use the Local Update functions if you want to. Do the reboots and hopefully it will run 100% and not stop with a failure.
Please review and redo steps above if it still fails.
12. After reboot it will do the necessary "Updating applications" as any Android update.
When you boot into the phone the first time things will have changed (like background, some icons etc.) but your
apps and data should remain. You will also go through a small guide, about 3-4 steps (Language/regions settings etc.)
13. Do any necessary updates from Google Play store (if any pending). Also reboot the phone into FASTBOOT mode
and re-run the Honor 6 Multi-tool to root your phone again (if needed) and install CWM/TWRP (if you wish).
14. Voilá, you should now have a B370 EMUI 3.0 phone. Please note that certain apps may have changed or lost certain
locks/functions so I recommend that you reinstall those first. Also check your "default" SMS/Webbrowser/Caller apps etc
that you would like to use if you are not using stock Huawei ones.
I recommend you check out these links for any more detailed instructions per step if needed:
Honor 6 Multi-tool
^^^ Full of small and detailed info regarding the Multi-tool and other useful Honor 6 flashing/rooting/unlocking tips.
Huawei Update Extractor tool
^^^ More info on how to use the Update Extractor Tool. It works for H60-L04 .zip/.APP files also even if it is not mentioned in thread.
Full Restoration to Stock ROM
^^^ Only perform steps 1 to 5. Steps 6-7 will GUARANTEE that you loose your data/restore to factory.
Official Huawei Honor 6 download page
^^^ Contains the proper H60-L04 V100R001C00B109SP01 Upgrade Software file to use for the RECOVERY.img and SYSTEM.IMG
that I used for this guide and for the H60-L04 (international version).
Hope this solves the problems for you.
Click to expand...
Click to collapse
THANKS VERY MUCH without you I wouldn't have success
You're welcome!
Recovery.img is loaded in to the phone, but system.img not. the first part of the file is loading very quickly, but the second part don't. I have waited more then 2 hours and nothing.
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (410901 KB)...
OKAY [ 45.068s]
writing 'system'...
OKAY [ 13.131s]
sending sparse 'system' (460475 KB)...
Click to expand...
Click to collapse
My phones rooting is gone. But I still can't update
Sorry to hear that smldmr. The SYSTEM.img really needs to complete. Have you retried from the first step? Skip the RECOVERY.img step and just flash the SYSTEM.img until i succeeds. It should do that in less than 15 minutes in 4-5 sparse sends. If it stops, it may be something with the usb port, some sort of disconnect from your computer. Any other USB devices you have that are causing strange polling or similar. If possible switch to another port, avoid using usb-hubs.
sheapchit said:
You're welcome!
Click to expand...
Click to collapse
sorry sheapchit but i followed the guide step-by-step but i still can't update my phone
my situation is this:
root = none
bootloader status = "relocked"
system = STOCK
recovery = STOCK
phone data (i mean app & media) = the same before the guide
TigerDeveloper, is your bootloader locked after update or was it locked before you started? I had unlocked bootloader while flashing this and also unlocked after...
sheapchit said:
TigerDeveloper, is your bootloader locked after update or was it locked before you started? I had unlocked bootloader while flashing this and also unlocked after...
Click to expand...
Click to collapse
i tried to flash with bootloader locked or "relocked" at the first time
than i tried with unlocked bootloader
TheTigerDeveloper said:
i tried to flash with bootloader locked or "relocked" at the first time
than i tried with unlocked bootloader
Click to expand...
Click to collapse
OK.
Perhaps something I missed in my attempt to upgrade....
Perhaps you should do this:
1. Unlock Bootloader and ensure that you have rooted the phone.
2. Start the phone and download a filebrowser like Root Explorer or similar.
3. Ensure that you can remove the folders HWOUC if they are on the SDCARD (0) or even on external SDCARD1.
4. Also check the root folder that there is no "dload" folder from any manual attempts to update. (Delete if there is.).
These steps are to ensure that you do not have a corrupted/failing update left of the update.zip file that is downloaded
and so that a fresh one can be retrieved using the OTA update function in the Settings.
Double check that you do not have any pending/locked updates from Google Play store. If so, ensure that they are installed.
I do not know if there is a size limit on the SDCARD0 (built in 16GB storage) that has to be met.
Please check that you have adequate space left (2gb+) so that the update.zip can unpack itself properly when installing.
Remove any unneccesary/old/large apps that may cause you to loose this and clear out caches to give yourself space.
Then redo the steps to flash RECOVERY.img and SYSTEM.img and attempt a new update with the OTA function.
This may be something I did as I also experimented first trying to do the manual "dload"-folder update before doing my flashing.
after I tried it without my ext-SD Card (64 GB exFat formated SD Card), the system.img was uploaded successfully Now i have EMUI 3.0.
That's great smldmr. I have a regular ext-fs formated sdcard so I didn't anticipate exFat to be an issue. TigerDev,what is your sdcard?
sheapchit said:
That's great smldmr. I have a regular ext-fs formated sdcard so I didn't anticipate exFat to be an issue. TigerDev,what is your sdcard?
Click to expand...
Click to collapse
i have a 16 GB sdcard exfat
now i just tried to do a factory reset with stock recovery and bootloader relocked, redownloaded update via OTA, but no change
smldmr said:
after I tried it without my ext-SD Card (64 GB exFat formated SD Card), the system.img was uploaded successfully Now i have EMUI 3.0.
Click to expand...
Click to collapse
so you have update your phone without SD?
mmh... i should try it...
sheapchit
can you post here (a file i mean) of your build.prop & local.prop? (i think they are official no?)
so i can push them with adb
thanks
This guide is intended for all those who like me were not able to once update your phone (H60-L04)
here's how I solved it:
1) restore the system (rom, recovery, bootloader)
2) remove the ROOT
3) install the "beta" 3.0
TigerDev, I have the B370 local.prop/build.prop now.
The stock B109SP01 .prop files should become/restore to stock when you flash the SYSTEM.img. Did you test, like smldmr, to do my steps after you have removed your exFat sdcard?
Remove micro-sd card before download OTA and updating.
Hello,
Not sure what to do at this point. I have a Creative ZEN Touch 2, device from 2010. Creative told me the bootloader is locked.
It's running Froyo, rooted.
Little background. Would love to.. maybe "try" to port Clockworkmod on it, or maybe just reflash the original kernel, because mine got corrupted somehow (Even then, not sure how. Boot.img packing doesn't seem to be standard!).
- The device does not have fastboot;
- It contains Android Recovery 3e, which does not allow flashing unsigned ZIP files. Tried to sign the ZIPs, not working I guess.
- /Recovery and /Boot seems to be one single 10MB partition (Doesn't look good);
- I managed to get ADB working, detecting the device correctly. Required tweaking.
- No custom ROMs, recoveries, kernels exists. No softwares either provided by Creative.
I do have the original bootloader files, extracted from an official update. If I could somehow replace these, I could perhaps fix the kernel. I have attached the files from the bootloader if people want to take a look. env.bin have been renamed to env.img, u-boot-no-padding.bin has been renamed to u-boot-no-padding.img and uImage has been renamed to uImage.img.
But what now? How am I suppose to unlock the bootloader completely on my own without any software provided ??
If I wanted to attempt the unlock, taking the risk of a hard brick, what shoud I try, how should these files be opened? In a HEX editor? How do people acheive the unlock first, that's what I would like to know. The point is really to find a flaw in the bootloader, correct? (I suppose I don't have the brain to figure this out. But if the answer is that easy because the device is outdated...)
I've read that sometimes it can be impossible if the manufacturer does not provide a way to do it. Am I correct, wondering that since the device is from 2010 (Originally had Eclair), such technology would be really primitive and could be a breeze to find a flaw on such a outdated device? Easy perhaps for not me, but someone else? Is the year of the device completely unrelated?
I would like to know more about this, how this is done (HEX editing?) and if it's really a dead end (Considering also that the device is from 2010).
EDIT: But does the device has Fastboot, somehow? I mean, how did Creative flashed the device from the factory if I cannot reach anything at the bootloader level?! No Download Mode, no Fastboot, no Emergency Mode (Just Android Recovery 3e. Still had to be flashed from somewhere. Jtag?) ??? How can I confirm Fastboot is not there? adb reboot bootloader just reboot the phone normally even with root access.
Asking this, since my other phone, LG P500 does have Fastboot, but it must be manually enabled with a software (And even now, the ZEN Touch 2 has no software availible to do this).
Thank you very much!
GameX2 said:
Hello,
Not sure what to do at this point. I have a Creative ZEN Touch 2, device from 2010. Creative told me the bootloader is locked.
It's running Froyo, rooted.
Little background. Would love to.. maybe "try" to port Clockworkmod on it, or maybe just reflash the original kernel, because mine got corrupted somehow (Even then, not sure how. Boot.img packing doesn't seem to be standard!).
- The device does not have fastboot;
- It contains Android Recovery 3e, which does not allow flashing unsigned ZIP files. Tried to sign the ZIPs, not working I guess.
- /Recovery and /Boot seems to be one single 10MB partition (Doesn't look good);
- I managed to get ADB working, detecting the device correctly. Required tweaking.
- No custom ROMs, recoveries, kernels exists. No softwares either provided by Creative.
I do have the original bootloader files, extracted from an official update. If I could somehow replace these, I could perhaps fix the kernel. I have attached the files from the bootloader if people want to take a look. env.bin have been renamed to env.img, u-boot-no-padding.bin has been renamed to u-boot-no-padding.img and uImage has been renamed to uImage.img.
But what now? How am I suppose to unlock the bootloader completely on my own without any software provided ??
If I wanted to attempt the unlock, taking the risk of a hard brick, what shoud I try, how should these files be opened? In a HEX editor? How do people acheive the unlock first, that's what I would like to know. The point is really to find a flaw in the bootloader, correct? (I suppose I don't have the brain to figure this out. But if the answer is that easy because the device is outdated...)
I've read that sometimes it can be impossible if the manufacturer does not provide a way to do it. Am I correct, wondering that since the device is from 2010 (Originally had Eclair), such technology would be really primitive and could be a breeze to find a flaw on such a outdated device? Easy perhaps for not me, but someone else? Is the year of the device completely unrelated?
I would like to know more about this, how this is done (HEX editing?) and if it's really a dead end (Considering also that the device is from 2010).
EDIT: But does the device has Fastboot, somehow? I mean, how did Creative flashed the device from the factory if I cannot reach anything at the bootloader level?! No Download Mode, no Fastboot, no Emergency Mode (Just Android Recovery 3e. Still had to be flashed from somewhere. Jtag?) ??? How can I confirm Fastboot is not there? adb reboot bootloader just reboot the phone normally even with root access.
Asking this, since my other phone, LG P500 does have Fastboot, but it must be manually enabled with a software (And even now, the ZEN Touch 2 has no software availible to do this).
Thank you very much!
Click to expand...
Click to collapse
i rooted one of these a while back if it helps here is how i did it..
1. Install "z4root.1.3.0.apk". (i used adb to install "adb install z4root.1.3.0.apk")
2. Open Z4root and click permanent root, it will take a bit to complete, then it will restart your Zen.
You should now be rooted and have access to stuff which may help you further? i did have a custom recovery for it somewhere on my linuxbox i will have a dig around on my hdd an see if i can find it..
thank you
Yes, I'm definitely rooted using Z4root as well.
This is interesting about the custom recovery, I found nothing. Not sure, considering Boot and Recovery seem to be a single partition, this could be dangerous.
Creative told me the bootloader was locked, so even if I flashed that custom recovery, I would get an error I guess?
But still, I have no way to verify if what Creative said was true, if the bootloader really is locked. Could be.
Thanks again for looking
Sent from my SGH-I337M using XDA Free mobile app
Inside 4ndroid said:
i did have a custom recovery for it somewhere on my linuxbox i will have a dig around on my hdd an see if i can find it..
Click to expand...
Click to collapse
Found anything new yet?
You can sign flashable zips with te test keys so you can flash them through stock recovery.
You have to have the software called signapk.jar. Search for it.
root-expert said:
You can sign flashable zips with te test keys so you can flash them through stock recovery.
You have to have the software called signapk.jar. Search for it.
Click to expand...
Click to collapse
Previously I think I used to flash an update.zip with absolutely no signature, so I think it would fail immediately to flash.
Now I do believe I've signed the file with sign-apk.jar, but still not working. Now, the update package open along with a progress bar, but 10 seconds later, it's still rejected, with a new error message stating "Failed to verify whole file signature".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it does check for a signature huh?
Weird because this update.zip was extracted from an official APK firmware update.
It check if the signature of the ZIP match the signature of, huh, the manufacturer, Creative?
Any way I could find out what is the valid signature to make it match properly?
Or would I just have to try again, and re-sign the ZIP with a different software?
EDIT: Here's the untouched update.zip file if you want to take a look.
https://dl.dropboxusercontent.com/u/67605655/update.zip
Or maybe you can try and sign it for me? Have I done something incorrectly?
Thank you
@GameX2 i have attached a signed zip. Try to flash it. This file is from the vendor? If this file is from the cendor then it should have been installed without any problems.
As far as the bootloader is concerned, i don't if it is locked. You have to boot to bootloader mode (if any??). If you want to unlock it and the vendor deosn't provides any tools then, yes, you have to hack it. This is done by reverse enginnering and as you said you have to find an exploit. Or maybe you can flashed an "unlocked" bootloader if the partition isn't signed by the vendor.
But if you don't have fastboot you can f;ash anything. Jtag is solution but it is difficult and you need expensive equipment.
root-expert said:
@GameX2 i have attached a signed zip. Try to flash it. This file is from the vendor? If this file is from the cendor then it should have been installed without any problems.
As far as the bootloader is concerned, i don't if it is locked. You have to boot to bootloader mode (if any??). If you want to unlock it and the vendor deosn't provides any tools then, yes, you have to hack it. This is done by reverse enginnering and as you said you have to find an exploit. Or maybe you can flashed an "unlocked" bootloader if the partition isn't signed by the vendor.
But if you don't have fastboot you can f;ash anything. Jtag is solution but it is difficult and you need expensive equipment.
Click to expand...
Click to collapse
Thank you for that;
I've tried your update.zip, strange as it's still not working. In that case, no progress bar shows up, like last time (It's like if the ZIP wasn't signed at all?):
Code:
-- Install from sdcard --
Finding update package...
Opening update package...
Verifiying update package...
E: signature verification failed
Installation aborted.
For info, when I've tried signing the ZIP myself using different tools such as sign-apk.jar and Sign-Em, I got a sightly different message along with a progress bar, shown in my last message.
That file is from the vendor, sort of, the firmware update is provided as an APK file. I've tried using that APK to upgrade the version, which is on 2.00.23 and there is a final release, 2.00.38, which brings almost nothing new, but being able to upgrade would reflash the original kernel and fix all these issues in fact... But when I try launch the APK, it's just not working, I get "The installer is not intended for your device" (Is that a joke ???)
Like this:
Huh. No clue, I have unrooted the device, nothing. I even decompiled the APK file with APKTools to see which conditions the APK check. Not sure, I'm not a programmor, but I saw a reference of build.prop, so I've restored the original build.prop file from the official firmware, still nothing.
Here's where you can download the 2 official firmwares. So they definitely are from the vendor.
http://support.creative.com/Product...MP3+Players&prodID=20275&prodName=ZEN+Touch+2
Regarding the update.zip file, that's also why I said "sort of", because no update.zip file is provided, it's an APK file. Instead, I've followed the instructions from this thread:
http://www.anythingbutipod.com/forum/showpost.php?p=610226&postcount=36
Allright,
I even didn't believe this couple of months ago when I broke my zen touch, but here is the cure which will get you a plain factory reset from the situation we all got into following these steps:
1) download firmare upgrade (the .apk file) from the official creative page
2) rename it to "firmware.zip"
3) extract from this archive a file from the "assets" folder called "data"
4) rename this "data" file to "update.zip"
5) copy this "update.zip" to your microSD card and put it into your Zen Touch device
6) start (or reboot) your Zen Touch
7) open the main screen and if you're lucky enough, you'll see a "firmware upgrade detected" dialogue. if so, allow the reboot and let your device be upgraded
8) in case you don't get the dialogue above, try to put the microSD card into your Zen Touch while running. and hopefully you'll be given the possibility for a firmware upgrade
9) by this firmware upgrade your device will be completely wiped and reinstalled
Good luck!
Bernard
Click to expand...
Click to collapse
So this is what the content of the official APK file look like when you extract it with 7-Zip:
The instructions above said to rename the 70,6MB file "data" to "update.zip" and place it on the SD card, and "randomly" a notification should appear, mentionning "Firmware upgrade found". No luck, no notification.
But still... That "data" file has the structure of an official update.zip file... I'm almost certainly sure that what the APK file does, it just rename the huge "data" file as "update.zip", and then just reboot into Stock Recovery and flash, huh?
So it's technically a trick, renaming the "data" file as "update.zip", but it still remains from the official firmware, yeah? How weird. I still don't understand that "Signature verification failed", then...
Doesn't make any sense.
As far as the bootloader is concerned, i don't if it is locked. You have to boot to bootloader mode (if any??). If you want to unlock it and the vendor deosn't provides any tools then, yes, you have to hack it. This is done by reverse enginnering and as you said you have to find an exploit. Or maybe you can flashed an "unlocked" bootloader if the partition isn't signed by the vendor.
Click to expand...
Click to collapse
There are no public infos on that bootloader anywhere. I had to e-mail the vendor, Creative, which told me the bootloader was locked (Is that even true? Ha, I guess so, but no way for me to verify the statement).
If only I had Fastboot, I could have tried "fastboot oem-unlock" on day one, but it doesn't appear to have Fastboot at all, or it's not accessible (To my knowledge, it could be hidden, but I really have no idea. Just thinking of my LG P500, which you can't access Fastboot the normal way, unless you soft-brick, or you manually enable it with a special software. Done that, on LG P500).
The commmand adb reboot bootloader doesn't work, neither reboot bootloader, with SU rights from Terminal Emulator. It just reboot the system normally. Also tried "adb reboot-bootloader", no luck. Hey, even "adb reboot recovery" just reboot the system normally, without accessing Recovery 3e.
In fact, I believe it just ignores the other arguments somehow. I can type rubbish like this, in Terminal Emulator:
Code:
$ su
# reboot jriogjrog
...Instead of popping an error, it still reboot normally. Huh.
I also have a USB-jig, but I always thought it was intended for Samsung only, and besides, my Jig is a microUSB, while the ZEN Touch 2 has miniUSB, just doens't fit in the port.
There seems to be nothing, tried every hardware key-combos out there, no way to reach bootloader-level, no Download Mode, no Emergency Mode, no Fastboot... Only hardware key-combo is "Home+Power", which access Recovery Mode, that's all.
This is the partition table. From what I see, I strongly believe /Recovery and /Boot are united as one single partition. Obviously, since it's an entertainment device but not a phone, it has no modem/baseband partition. Pretty simple. Appears to use non-standard NAND partitioning (Wow). With an MS-DOS partition table (GPT was new in 2010, isn't it?), so the Block 3 is just an extended partition.
BUT, from what I see, Block 4 start at 158MB, so there would be 158MB of unused space at the start of the NAND ???? Or that part of the bootloader in any way (158MB for the bootloader, no way?) ? Or maybe Creative are just dumb XD Or this could be some sort of Master-Boot-Record just like on computers like GNU-GRUB, but I've never heard of that on Android, we refer to simply a /Boot partition.. Which I still believe /Boot and /Recovery partitions are combined.
But if you don't have fastboot you can f;ash anything. Jtag is solution but it is difficult and you need expensive equipment.
Click to expand...
Click to collapse
I've heard of JTAG, the process of connecting the motherboard to a JTAG box, and reflashing the bootloader that way - Didn't knew this could be used to flash the whole system. Thought you would flash just the Bootloader and restore the rest with Odin, for instance.
A bit off-topic, but to use JTAG, do you have to have a special bootloader file, or can you flash the bootloader using, for example, the u-boot-no-padding.bin file we have here?
Do the device (especially older devices like this one) requires special connections, or connectors, so if the connectors don't exist, no way to JTAG? Oh well, that's not the main topic anyway, just curious, you really seem to know your stuff.
Thank you very much
[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+2]Moto X Pure[/SIZE]
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me
This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk
Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes
This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.
Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Oops
emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.
emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588
Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/
I flashed SU and it didn't give me root, any suggestions?
mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?
Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.
mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.