Hello guys! At last, it is here! This tool has some distinct similarities with hasoon2000's tool (which is awesome by the way), but it also has few differences, more will be explained below.
Please note, this tool has certain requirements that you MUST follow!
This will flash a T-Mobile OTA, so if you are on ANY other carrier, you must have SuperCID, or wait for a similar tool that I may release in the future for your specific carrier. As of now, you must have SuperCID in order to run this tool (although you can try without, but results are NOT guaranteed)
As noted in the title, this tool is currently in beta, so use this as your own risk! I have tested this many times myself, but unfortunately, I haven't had enough testers respond to my request, so I am releasing this to the community as I know this would be a valuable tool.
Also, due to some people in this forum, I feel compelled to state this in big, bold, colored text.
This tool is only meant FOR S-Off users, and it does not, in ANY way, give you S-Off! NO, it will NOT work with an unlocked bootloader. To use this tool, you MUST have S-Off, plain and simple.
Click to expand...
Click to collapse
And now an explanation on what this tool does:
I've made a simple tool that will completely update your phone to the latest T-Mobile's OTA (Ice Cream Sandwich version), but without the need of reinstalling your custom recovery and reflashing SuperUser.
This is great for:
- People (especially newbies) with S-OFF that want to update to the latest OTA update, without having to find an Engineering/J-Bear hboot, without having to find a recovery to flash, without having to figure out how to flash superuser package, and without figuring out which fastboot commands to input.
- People without a SDCard, as this tool DOES NOT require a SDCard to flash the OTA!
- People who are stuck in a seemingly endless bootloop, and cannot figure out what to do in order to get the device back into a working state.
The true beauty of this tool is that it is ridiculously simple. All you really need to do is read the instructions, plug in your phone, run the program. In this program, you literally only have to touch your computer twice. The first one to accept the disclaimer, and then the 2nd to ensure that you have plugged in your USB cable.
Then this program will do the rest. It'll automatically detect which state your phone is in and then run the correct commands, check your S-Off state, flash the entire modified OTA*, detect whether the flash succeeded or failed, flash SuperUser and the free 4EXT recovery application, and does some other commands to ensure the phone works upon boot-up. This entire update should take no more than 15 minutes to complete, depending on your phone.
* The modified OTA update consists of 4Ext recovery, J-Bear Hboot (.2222), and a custom splash screen (hope you like it :laugh: )
Click to expand...
Click to collapse
Credits:
-MadMaxx82 for permission to use his awesome recovery and his free 4EXT recovery app
-Hyuh (and the entire unlimited.io team) for their work with S-Off and permission to use the J-Bear Hboot
-Hasoon2000 and Dark Nightmare for some of his suggestions and ideas
-Kgs1992 for some of his help on batch files
-Dark Nightmare, gregma, andy55, and shekki for testing this tool out
-I probably forgot some others, contact me if I did so I can credit you accordingly!
Click to expand...
Click to collapse
Before we go any further about this S-Off tool, you need to understand that there is always a risk of damaging your phone, even though I have personally tested this tool many times.
By downloading this tool, you accept all risks associated with this tool. I am not responsible if this breaks your phone, bricks it, or otherwise render your phone unusable. The standard disclaimer applies to this situation. Although I will try to help you, you are still responsible for whatever happens to your device.
Alright, moving on.
You MUST ensure that you have met the following requirements:
-The HTC Amaze 4G must have S-OFF
-The device must have SuperCID! (If it's a non T-Mobile phone)
-The device must be rooted!
-Battery must be *FULLY* charged
-A Windows computer with ADB/Fastboot drivers installed Files are included - but if it does not work, install these yourselves manually
-You must have an USB *DATA* cable. -- If you can transfer files and send adb/fastboot commands with the USB cable, it will work
-You must have USB Debugging turned on!
-Most importantly, you must have the ABILITY to follow directions
I cannot stress this enough. Make sure your battery is of decent charge. You do not want to have your phone shut down in middle of the process.
Click to expand...
Click to collapse
Instructions:
(READ THROUGH THE INSTRUCTIONS BEFORE DOING ANYTHING!)
Step 0) Ensure that your requirements are met.
Step 1) Make a nandroid backup if you want to restore your phone to the way it was before the tool. After backing up, make sure to make a backup of the nandroid backup, and both of the internal and external SDCards to your computer. I can not guarantee if the tool will wipe your external SDCard (It shouldn't, but it doesn't hurt to be safe)
Step 2) Disable any antivirus applications. This is a precautionary measure. You don't want the antivirus to remove something important in the middle of the update.
Step 3) Download the tool
Step 4) Verify the MD5 checksums to make sure they match. You do not want a corrupted tool.
The MD5 checksum is displayed on the download site, but if you need it, the MD5 checksum is:
f697211a9a49b293c4b99eee80de47d9
Step 5) After verification, use your favorite file extraction utility, put the entire ToolV2 folder (not just the files, but the entire folder) in an accessible location such as the C:\ Drive, Desktop, or whatever is the easiest for you.
Step 6) Open the folder *IMPORTANT* DO NOT change the files, move them, rename them, or anything of that nature. If you do, the tool most likely will not work.
Step 7) Open the RUN-ME.exe file (with an icon like this:
{
"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"
}
) *IMPORTANT* Do not extract the file named 'UltimateUpdater', leave it alone!
Step 8) Ensure that your phone is turned on. It can be in recovery, fastboot, or even in normal mode. It will automatically detect the device state. However, if possible, it is recommended to have your phone be booted into android.
Plug in the data cable. Make sure it is set to charge only (If booted into android). Do not forget to turn on USB Debugging!!!
Step 9) Follow on screen instructions. The process may take a while. Do not touch the phone, touch your computer, close the program, and most importantly, do NOT unplug the USB cable! It should auto-detect your device state, and it will detect your S-OFF state as a precautionary measure. When you get to this point like in the screen shot:
Follow it! Do not do any of those things! Leave it alone for 10 minutes! It will then detect if the update was successful. (If it does not do anything after 10 minutes, or does not detect anything, post on this thread and we'll see what needs to be done)
Click to expand...
Click to collapse
DOWNLOAD LINK
PLEASE READ BEFORE DOWNLOADING!
http://d-h.st/r22
Click to expand...
Click to collapse
Also, if you don't like the splash screen, this is your first step in figuring out how to mod your phone. Remember, DON'T post a question on how to change the splash screen, there ARE posts in the Amaze forums complete with step-by-step instructions on how to install a different splash screen!
It's time you started using the search button, my friend
Also, don't forget to press the THANKS button if this tool helped you!
Congrats! You finally released it! lol
hasoon2000 said:
Congrats! You finally released it! lol
Click to expand...
Click to collapse
Indeed I did! You know, you should test it out too. It's pretty neat if I say so
I gave ideas too , Jk JK, congrats on your release and thanks for the creds. :good:
Dark Nightmare said:
I gave ideas too , Jk JK, congrats on your release and thanks for the creds. :good:
Click to expand...
Click to collapse
Indeed you did! Maybe you'd like to read the credits again
Keylogger_0 said:
Indeed you did! Maybe you'd like to read the credits again
Click to expand...
Click to collapse
Lol I was jk dude, thanks though, appreciate it . Now back on topic, I'll be recommending this as the restoration option for all s-off users.:good:
Edit: Don't mention it bro, you did a good job and this will be a saviour for many.
Dark Nightmare said:
Lol I was jk dude, thanks though, appreciate it . Now back on topic, I'll be recommending this as the restoration option for all s-off users.:good:
Click to expand...
Click to collapse
Thanks!
thank you!!!
As I lost hope this utility actually worked!!! Hassons utility wouldn't read my phone. I flashed nightmare sense 1.6 and my phone wouldn't boot up, then I went to recovery like you're supposed to right? Using twrp and it just crashed and it automatically boot it up to the boot loop. And this helped so much thank you for this.
HTC amaze bootloop
Keylogger_0 said:
Hello guys! At last, it is here! This tool has some distinct similarities with hasoon2000's tool (which is awesome by the way), but it also has few differences, more will be explained below.
Please note, this tool has certain requirements that you MUST follow!
This will flash a T-Mobile OTA, so if you are on ANY other carrier, you must have SuperCID, or wait for a similar tool that I may release in the future for your specific carrier. As of now, you must have SuperCID in order to run this tool (although you can try without, but results are NOT guaranteed)
As noted in the title, this tool is currently in beta, so use this as your own risk! I have tested this many times myself, but unfortunately, I haven't had enough testers respond to my request, so I am releasing this to the community as I know this would be a valuable tool.
And now an explanation on what this tool does:
I've made a simple tool that will completely update your phone to the latest T-Mobile's OTA (Ice Cream Sandwich version), but without the need of reinstalling your custom recovery and reflashing SuperUser.
This is great for:
- People (especially newbies) with S-OFF that want to update to the latest OTA update, without having to find an Engineering/J-Bear hboot, without having to find a recovery to flash, without having to figure out how to flash superuser package, and without figuring out which fastboot commands to input.
- People without a SDCard, as this tool DOES NOT require a SDCard to flash the OTA!
- People who are stuck in a seemingly endless bootloop, and cannot figure out what to do in order to get the device back into a working state.
Before we go any further about this S-Off tool, you need to understand that there is always a risk of damaging your phone, even though I have personally tested this tool many times.
By downloading this tool, you accept all risks associated with this tool. I am not responsible if this breaks your phone, bricks it, or otherwise render your phone unusable. The standard disclaimer applies to this situation. Although I will try to help you, you are still responsible for whatever happens to your device.
Instructions:
(READ THROUGH THE INSTRUCTIONS BEFORE DOING ANYTHING!)
Also, if you don't like the splash screen, this is your first step in figuring out how to mod your phone. Remember, DON'T post a question on how to change the splash screen, there ARE posts in the Amaze forums complete with step-by-step instructions on how to install a different splash screen!
It's time you started using the search button, my friend
Also, don't forget to press the THANKS button if this tool helped you!
Click to expand...
Click to collapse
Hi, i flashed this OTA but my HTC amaze still in a bootloop, could you help me with this?
Are you on tmobile? if not did you SuperCID?
This tool has helped me several times, you should not be in a bootloop if you followed the steps correctly. it installs a completely new everything, recovery included (4ext). you should at least be able to access that from bootloader and restore a backup.
Andy1886 said:
Hi, i flashed this OTA but my HTC amaze still in a bootloop, could you help me with this?
Click to expand...
Click to collapse
What carrier are you on? CID? Can you also PM me your UpdateLog.log file found in the AIO folder of this tool? Don't post it here, PM it to me.
Gonna try it now... Will update u in a while..
This is the error I get while I am on trying to run the exe file...
I am running Win 7 ultimate X86 (32 bit)
vikasraj said:
Gonna try it now... Will update u in a while..
This is the error I get while I am on trying to run the exe file...
I am running Win 7 ultimate X86 (32 bit)
Click to expand...
Click to collapse
Any help regarding the tool from the developer..
Related
WARNING!!!!!Use of the following has been know to cause bricks and/or loss of functions in most of the devices it was attempted on. Because of this, the Thread was permanently closed. However the files will remain to assist in further development. Additionally, there is no promise if any of the links still work. So if you choose to mess with these files, you do so knowing it will probably brick your device.
Moscow Desire, XDA Moderator*******************************************************************************
[Pudding]
WARNINGS: READ ALL OF THIS BEFORE CONTINUING
1. All phones You most likely will lose 4g data connectivity from using this, hopefully a workaround is on the horizon.
2. All phones This has received limited testing, use at your own risk and accept that there may be a risk of hard bricks now or in the future (Unless you get your SBK.)
3. All phones Charge your phone, all the way please.
4. Use at your own risk. Have a backup phone, insurance plan or other means of recovering from a possible brick or loss of functionality. You are using experimental software at your own risk.
Works/Does not work list
Sprint en/us 45.2.5: Warning: Loss of 4g connectivity very likely
Electrify 2.3.5: Danger: Untested, I do not own one and cannot test
Click to expand...
Click to collapse
Updates
8/30/2011 Added stock recovery image for those wishing to use pudding remover.
8/25/2011 Pudding remover added. This restores your stock bootloader. 4G will be restored but your phone will be locked again. This is only the bootloader, so system changes will not be removed (root, recovery, program data, etc). Having the custom recovery still installed with the locked bootloader may cause problems (soft-brick, you will need to use full sbf or re-unlock and flash back the stock recovery). will cause you to soft brick. You will need to reflash the unlocker to recover and either leave it unlocked or restore the stock recovery and use the pudding remover afterwards. Thank you tuxy for being the only one basically willing to test this.
8/16/2011 Just a quick update on the 4g issue, most likely this will go unresolved until your kernel source is released and someone with the appropriate skills in kernel hacking fixes your ATAGS passed by the bootloader. For now you can either be unlocked and use 3g, or locked and use Wimax/4g. Pick your poison, at least neither is a permanent thing.
Click to expand...
Click to collapse
Who does/doesn't need this.
You need this if:
1) You need to flash custom single partitions such as system, osh, boot.img, recovery, or data.
2) Mainly for testing custom kernels, see number one.
3) You have a real ROM with a custom kernel, like CM7 or MIUI, and want to flash it.
You don't need this if:
1) Number one in the last section doesn't make any sense to you or sounds like gibberish.
2) You wanna show your friends how much cooler or better than them you are.
3) You just want to install P-ROMs and Themes.
Click to expand...
Click to collapse
You want pudding for Photon? There is pudding in space too!
Pudding:
http://diamantephoto.com/photon_pudding.rar 1mb bootloader only
Fastboot:
Use this to unlock after flashing pudding sbf (not available), also to flash custom partitions.
Windows: Moto-fastboot for windows thanks to romracer. Direct Download Link
Linux/Mac: Moto-fastboot for linux in several flavors thanks to eval-.
RSD/Drivers/SBF_FLASH:
You may need to reinstall drivers after the unlock.
RSDLite 5.5 Download
http://mophoforum.com/Roms/rsdanddrivers.zip
64bit windows drivers
SBF_FLASH(*nix/Mac)
Pudding remover:
Directions:
1) Make sure you are on the stock Recovery. If not, flash the image I provided below using this command:
Code:
fastboot flash recovery stock_recovery.smg
2) Flash the nopudding4u sbf using RSDLite or sbf_flash.
3) Done
http://www.multiupload.com/A4KCLBTL3K - 3.6mb stock recovery image from CM5
http://diamantephoto.com/photon_nopudding4u.rar - 1mb bootloader only, stock locked bootloader. For those of you who want a quick way to return to 4G.
Howto:
Is your phone fully charged? This should be first thing you check whenever you flash anything.
0) Back up all your apps and anything else you want to keep that is stored in /data, YOU WILL LOSE ALL FILES IN /DATA
1) Flash the pudding sbf file via sbf_flash(*nix/Mac) or RSDLITE(Windows).
2) Get moto-fastboot in your $PATH or at least in the same directory as the command line you open.
3) Open a command line or well, linux users know what to do, in the folder with pudding.
4) Type moto-fastboot oem unlock
5) Look for the UNIQUE ID number and copy it, use copy or your fat fingers might mistype it.
6) Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED
7) Enjoy!
Here is a picture of the steps on a windows command line (yes, I renamed moto-fastboot to just fastboot on my PC.) The blurry bits are where YOUR unique ID shows/is entered.
{
"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"
}
Root:
A moto-fastboot flashable /system image with su already in /system/bin (pre-reooted) This is based of the system in Yay4jugg's thread (NB: you need to be unlocked to flash this .)
Instructions:
0) Make sure your phone is charged.
1) Boot your phone in to fastboot mode, connected to PC.
2) At the prompt/cmdline type moto-fastboot flash system system.img
3) Make sure you have superuser app installed from market.
4) Enjoy!
CWM:
Romracer's official CWM thread for Photon
Calkculin's CWM thread
A video guide on how to root and install CWM for unlocked Bootloaders by qbking77
Kernels:
Hewett Kernel
Shabby's OC kernel
Problems?:
1) Don't panic.
2) Stop panicing.
3). If you get the following error messages, try restarting the flash process from the start:
- The "secure_motorola_flash" interface could not be found the super-file is secure and for re-flash, the phone needs a super-file that is not secure and for reflash. (0x7066)
4) Just try and go through with the unlock process anyhow
5) Try a different USB port, this is most likely because windows will reinstall all the drivers.
6) Try a different version of RSD Lite.
7) Make sure you put your phone in to USB NONE before plugging it back in. If you do not do this your system will not install all the devices correctly. Alternately, try Motorola Phone Portal mode.
8) Last resort PM me with very specific information about your problem and if applicable screen shots from your computer or phone.
Big thanks to Yay4juggs and Edgan.
The attached file below is only for Electrify owners and is untested
MOD EDIT: Attachment Removed
Yea BL unlock and root without dock? I gotta sleep, hope christmas comes in the morning!! I get some cash soon, gonna buy you guys a round! Man you guys are persisting and pushing tonight...
-DJ
Grats to everyone involved. You did amazing work.
Sent from my MB855 using XDA App
My stomach is ready. Thanks for the efforts and the work into this, we are grateful.
Chocolate pudding.
Has anyone tried this?
Sent from my MB855 using XDA App
evonate said:
Has anyone tried this?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I beleive its still being tested isnt it?
Hey you,
My name is Rick, and I am never gonna give you up. All of you have let me down, made me cry, and spent all day telling lies and hurting people. Your heart's been aching but you're too shy to say it. Honestly, have any of you ever gotten this from any other guy? I mean, I guess it's fun knowing the game and playing it, but you all take to a whole new level. Inside we both know what's been going on.
Don't be a stranger to love. You know the rules and so do I. I'm pretty much perfect. I have been nominated for a Grammy, and had a #1 hit. What games do you play, other than "running around deserting people"? And if you ask me how I’m feeling, I also have a banging hot girlfriend (We’ve known each other for SO long). I just wanted to tell you how I was feeling. I gotta make you understand.
Sent from my MB855 using XDA Premium App
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
theres a handful of people that actually knew anything about the photon and motorolas in general. i knew it wouldnt take long....im selling my nexus s as we speak, im that confident we will see awesomeness very soon.
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
I'll leave that up to you I don't own a Photon or Evo.
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
ooxcfhxoo said:
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
Click to expand...
Click to collapse
it is very exciting. i saw this right here and sold my nexus s this is my Photon in the picture btw...
Huge thanks to the2dcour for making this happen!!!!
what are the chances of getting the sbf tonight from someone?
ooxcfhxoo said:
what are the chances of getting the sbf tonight from someone?
Click to expand...
Click to collapse
0% check back tomorrow around noon EST.
I was thinking along the lines of a small (coffee sized) donation?....on say..........Newbury Street
ooxcfhxoo said:
I was thinking along the lines of a small (coffee sized) donation?
Click to expand...
Click to collapse
I _never_ ask for donations so don't feel obligated to, the work I do is a lot less intensive and technical than people imagine. As I've said before 99% credit belongs to moto for making this, 0.5% to the leaks/people who provide the leaks, and I'm happy to take the last 0.5% credit for being the script kiddie that assembles the pudding.
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
ericdabbs said:
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
Click to expand...
Click to collapse
That's precisely the reason that it hasn't been posted yet. There still may be side effects in the future as we are seeing with the atrix. Be warned, the unlock is irreversible and you should be careful. Most people will not need an unlocked bootloader. When you get custom kernels and CM that is another matter. People who dev this stuff can certainly use the unlock wisely. Till there is a reason for you to unlock I wouldn't bother unless you are adventurous and have a spare phone 99% of the reason people need / want unlock is for a custom kernel the other 1% is for using fastboot or non-bootstrap cwm. Hopefully you will have a non-bootstrap CWM soon. I'm rambling so I'll stop talking.
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
I would be using ......fastboot or a non-bootstrap cwm (when one is available).
i understand CWM is possible now and the reason for me unlocking my boot-loader is to get it done before someone puts the brakes on it.
I like to have access to the things i own based on principal. Its the same reason why i refuse to pay twice for the same data stream i already pay for in order to tether.
ooxcfhxoo said:
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
Click to expand...
Click to collapse
Coming tomorrow, I promise.
Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
I would like to add for those that like my toolkit, PLEASE DO NOT POST IT ELSEWHERE WITHOUT MY PERMISSION!
I have seen multiple sites who copy and paste my work to their site! If I do not approve of it, then do not do it! it will discourage me from adding updates since it is being used for their own benefits!
tl;dr.
If you post my work without permission, don't expect updates!
I created an easy to use GUI program for the HTC Amaze and I decided to make one for the HTC One X+. I spent a good over 10+ hours to learn how to script, watch videos on how to do it, working on it during school when I should have been listening lol and all that fun stuff. I am going to fix it and up and add more updates to it. You CAN place requests and I will try to fulfill it!
If this helped you out, Please press the thanks button and if you want, you can always donate!
FEATURES
- Install HTC Drivers
- Enter Bootloader (after it enters into bootloader, press the power button to enter Fastboot) REMOVED. No longer necessary.
- Get Token ID. Register at HTCDev, login to the site and submit the Token ID here. Buttons have been replaced and include links.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
TWRP (International Model) BE SURE TO CHOOSE TWRP FOR THE CORRECT DEVICE!
TWRP (AT&T / Telus Model)
User Provided Recovery
-Flash Kernels provided
User Provided Kernel
- Link to this thread
- Link to PM me if you need a phone unlocked
- Link to the One X+ Development thread
- Boot Into Recovery
- Boot into Bootloader
- Relock Bootloader (must be in fastboot)
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this! (A great motivator for me to continue updating for the One X+!)
Here is a screenshot.
{
"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"
}
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Mods of the forum!
- Devs for making us ROMS!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
DONATIONS
You can show your appreciation by donating to me via PayPal by clicking THIS. It helps me continue going to school and gives me a motivator to update the toolkit for the One X+!
- droidiac13
- Bob Allen (username not given)
- HaJeeEs
Click to expand...
Click to collapse
Downloads
Mod edit: Download links removed
Changes
V1.0 Released! 11-15-2012
- Initial Release
V1.1 Released! 11-19-12
- Added TWRP for int'l/AT&T models. MAKE SURE TO CHOOSE THE RIGHT ONE!!!
- Edited a few scripts to clarify some stuff
v2.0 Released 12-22-2012
- Major Overhaul
- Users can now select their own recovery, kernel and unlock_code.bin. You no longer need to place it in a the data folder. Just browse for it
- Removed a lot of .bat scripts and integrated it in the program
- Updated SuperSU from 0.97 to 0.99
- Updated TWRP to 2.3.3.0 (AT&T/Telus and INTL)
- Added a few links
- Added ADB sideload (for use in TWRP)
This Update took FOREVER to do, but I did it for you guys!!!
v2.1 Released! 12-30-2012
- Updated APK Batch Installer Tool to v1.4.1
- Added 2 more useful looks (1 to my website and 1 to a written step-by-step guide)
- Automated a few commands. No longer need to use the boot into bootloader then use the command to flash a kernel/recovery/unlock_code.bin
- Added some more message boxes for clarity.
v2.2 Released 1-12-13
- Removed all TWRP recoveries and replaced them with Lloir's CWM
- Fixed a bug where when you want to get your token ID, it'll boot into recovery rather than bootloader.
- When you want to relock the bootloader, it'll boot into bootloader and then lock it.
v2.3 Released! 1-23-2013
- Added Check CID feature
- Added a way to flash RUU Zip files
- Added more clarity.
- Fixed some bugs in the code.
- Nice little update
v2.4 Released! 6-2-2013
- Added new features!
- Replaced CWM With TWRP 2.5.0.0
- Updated links and placed links for my Androidfiles/Dev-Host account
- Added new commands
- I don't remember what else. Updating a lot of my toolkits that I forgot what I did!
v3.0 Released! 7-16-2013
- Updated TWRP to 2.6.0.0
- Updated SuperSU to v1.41
- Removed HTC Drivers and replaced it with a link to download. Lightens up the size of download of the toolkit by 14mb!
Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- Kernels
- More recoveries
- Makes Requests!!!
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - Only the fastboot commands, HTC Dev unlock (device specific) and the HTC drivers. Toolkit is made for the specific device.
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.
File has been uploaded! Enjoy!!!!!!
Great stuff man!
.
Cool!
So glad/honored to see/participate how things born with a new device
Amazing!!!:good:
Has anyone tested this on the AT&T version of the One X+?
mike1986. said:
Great stuff man!
Click to expand...
Click to collapse
It's an honor to hear you say that
orb3000 said:
Cool!
So glad/honored to see/participate how things born with a new device
Click to expand...
Click to collapse
I hope I can get one and wait for T-Mobile to get one or until they refarm their network so I can get 4G on it. then I can participate more
koluchca said:
Amazing!!!:good:
Click to expand...
Click to collapse
Enjoy!
Sent From My HTC Amaze 4G via Someone's Room
Thanks for your work!
Yeah...so I tried it on the AT&T version of the One X+. CWM installs OK, but when you reboot into recovery
E:Can't mount /sdcard/
EDIT: Looks like it bricked my phone. Oh well. All in the name of discovery
jimok82 said:
Yeah...so I tried it on the AT&T version of the One X+. CWM installs OK, but when you reboot into recovery
E:Can't mount /sdcard/
Click to expand...
Click to collapse
Post in Mike's thread. He can help more than me.
Sent From My HTC Amaze 4G via Someone's Room
Thank you! Works perfectly, installed CWM and made my first nandroid backup. Now installing the Maximus Rom.
Does this work with Windows ?
Does it install all the drivers for W8
@home said:
Does this work with Windows ?
Does it install all the drivers for W8
Click to expand...
Click to collapse
Doesn't install drivers for win8. I'll look for it later
Sent From My HTC Amaze 4G via Someone's Room
jimok82 said:
Has anyone tested this on the AT&T version of the One X+?
Click to expand...
Click to collapse
This?
Greatly appreciate your time and efforts into this as i'm a total android newb and this is my first android device. Will be sure to make a nice donation to you as soon as i can fully understand how this bad boy works. Just a few questions:
1. Is this compatable for the ATT USA version of the HOX+?
2. I watched your video a few times and maybe it's my computer's speakers but the audio wasn't the best trying to understand everything you were saying as this is all new to me and trying to understand. For Step 3 to get the token ID using the Prompt screen, you said to highlight the info but then what do i press to copy it once highlighted? Sorry but never have used the prompt screen, reminds me of MS-DOS from back in the day.
3. This is basically everything EXCEPT Root is this correct? I would first need to Root my device, do ADB backup and Titanium App Backup for apps/data/etc, then i can use your program to unlock bootloader and install recoveries, is this correct? If so, the CWM recovery you have is it working and compatible for the ATT USA version of this device?
4. For the Extras section of your program, what exactly is the APK/Data Backup? Is this similar to the Titanium App backup that will backup app data or is this different? Do i do this backup before Steps 1-5 to unlock bootloader?
5. For Perm Root, what exactly is the advantage of doing this VS. the regular Root method? I'm guessing this makes Root permanent and after doing this it then cannot be reversed? If so, again what is the advantage of this and if something goes wrong down the road how could i recover my device?
6. What is Mainver Error Fix in the extra section of your program?
Sorry for all the questions but i'm sure once this device gets out i won't be the only android newb around here and i'm sure like me they will all have the same questions. Just want to cover all my bases here before modding my device to not screw anything up and learn the hard way. Like taking a college course trying to understand android, been reading up on this stuff for weeks now once i decided i was going to purchase this device today.
If i've missed any steps please let me know
I greatly appreciate your time and patience with my questions and will keep in touch with you with a respectable donation my man, thank you again!
Is this compatable for the ATT USA version of the HOX+?
Click to expand...
Click to collapse
Not yet. My phone is bricked bad.
deeznuts said:
This?
Greatly appreciate your time and efforts into this as i'm a total android newb and this is my first android device. Will be sure to make a nice donation to you as soon as i can fully understand how this bad boy works. Just a few questions:
1. Is this compatable for the ATT USA version of the HOX+?
2. I watched your video a few times and maybe it's my computer's speakers but the audio wasn't the best trying to understand everything you were saying as this is all new to me and trying to understand. For Step 3 to get the token ID using the Prompt screen, you said to highlight the info but then what do i press to copy it once highlighted? Sorry but never have used the prompt screen, reminds me of MS-DOS from back in the day.
3. This is basically everything EXCEPT Root is this correct? I would first need to Root my device, do ADB backup and Titanium App Backup for apps/data/etc, then i can use your program to unlock bootloader and install recoveries, is this correct? If so, the CWM recovery you have is it working and compatible for the ATT USA version of this device?
4. For the Extras section of your program, what exactly is the APK/Data Backup? Is this similar to the Titanium App backup that will backup app data or is this different? Do i do this backup before Steps 1-5 to unlock bootloader?
5. For Perm Root, what exactly is the advantage of doing this VS. the regular Root method? I'm guessing this makes Root permanent and after doing this it then cannot be reversed? If so, again what is the advantage of this and if something goes wrong down the road how could i recover my device?
6. What is Mainver Error Fix in the extra section of your program?
Sorry for all the questions but i'm sure once this device gets out i won't be the only android newb around here and i'm sure like me they will all have the same questions. Just want to cover all my bases here before modding my device to not screw anything up and learn the hard way. Like taking a college course trying to understand android, been reading up on this stuff for weeks now once i decided i was going to purchase this device today.
If i've missed any steps please let me know
I greatly appreciate your time and patience with my questions and will keep in touch with you with a respectable donation my man, thank you again!
Click to expand...
Click to collapse
1. This version of CWM will not work on the ATT Model.
2. Highlight the Token ID and right click. Right click will copy the text.
3. This is an All-In-One tool to unlock your bootloader, flash a recovery and to root it. However, CWM will not work so you cannot root yet.
4. Pretty much. It's a windows program so you can back up your stuff. You can use it whenever you want.
5. I just call it perm root. Long story of it. It's just root for the phone and root can easily be removed.
6. When you install a new update to the phone and you want to downgrade, it'll change your software number to a generic number so you can install any RUU for your phone as long as the HBOOT (bootloader) wasn't updated.
The video is a little outdated. I updated my scripts in the program so it'll be easier to do. Just wait til a proper version of CWM is released for your phone
jimok82 said:
Not yet. My phone is bricked bad.
Click to expand...
Click to collapse
Not necessarily a bad brick. You just need a stock AT&T recovery/RUU, but that isn't released. Once that is released, this will be easy to fix.
Just asking here...but if things aren't working on AT&T devices, shouldn't there be an AT&T OneX + thread??!! Just to prevent people from having unusable phones....
big thanks to the developer!
This technique will not work if you have applied the OTA update from 18January2012. Go here: http://forum.xda-developers.com/showthread.php?t=2118348
This device is now unlocked to the point of development board status. After you finish this process, you will have the ability to destroy your device so make sure you flash CAREFULLY. Using only the files in this guide, there is no way to brick your device. Stay away from Odin once you've finished this process unless you're flashing back to stock.
TLDR version: Put your device into USB Debug Mode. Run CASUAL Injection 9. Flash the Suck It Verizon Bootloader with Odin3 If CASUAL calls you a Noob, flash the PIT and Bootloader Baseline package with Odin.
Introduction
The instructions have changed DRAMATICALLY since initial release. It's super simple. You are expected to be stock running I605VRALJB version of software. If you have modified your device using another procedure previous to this, undo it. This is where you start.
Prerequisites
any I605VRALJB stock bootloader and a stock ROM or a rooted stock ROM.
Downloads (in the order you need them)
The Pit File This is the stock i605VRALJB Pit file. It works to make your device partitions stock again. Flashing this will prepare your device for unlock.
The Bootloader Baseline package - Odin Package This is a stock I605VRALJB bootloader, params, kernel and recovery. Flashing this will prepare your device for unlock and relock your device in a safe manner. *This will reset your device if you screw up during the process so you can start over.
Odin3 is a tool from Samsung used to flash Odin packages.
CASUAL Suck It Verizon Injection 9 CASUAL stands for Cross-Platform ADB Scripting Universal Android Loader. In this case, it deploys the Suck It Verizon exploit. To use CASUAL you must enable "Settings>Developer Options>USB Debugging" on your device. CASUAL is used as an automation tool so that you don’t have to use ADB, watch for results, upload files, download files, make decisions and enter commands. CASUAL will make those determinations for you. This guide is much shorter because of it. Source code for CASUAL can be found at http://android-casual.googlecode.com. The exploit was designed by Ralekdev, packaged, tested and made safe by AdamOutler. --DON'T MIRROR, this is in development.
Suck It Verizon Bootloader 2- Odin Package provides a bootloader which has been modified to ignore all security checks at the highest level possible. This firmware runs every time you turn on your device. The SBoot's job is to validate Download Mode flashes. It also validates and executes the kernel. This bootloader will not validate, only download and execute. It will also allow you to flash anything you like, including firmware packages which will destroy your device. This bootloader replacement is not only a Bootloader Unlock, this is an IROM Unlock... The lowest level unlock possible. The bootloader was developed by Ralekdev, conceptualized by Rebellos, tested and packaged with a Sprint GN2 TWRP Recovery by AdamOutler.
Instructions
If these instructions dont quite make sense, check out the video below.
Part 1: Install the Baseline
Launch Odin or click the "reset" button at the bottom if it's already open.
Place the sch-i605-16gb.pit into the "PIT" section of Odin.
Place BootloaderBaseline2.tar.md5.gz into the "Bootloader" section of Odin.
Click Start
Part 2: Run the CASUAL Exploit
Put your device into development mode. Settings>Developer Options>USB Debugging
You need Java installed to double-click or run with "java -jar path_to_file.jar" Do you have java?
Click the "Root and Unlock Me Now!" button and accept( or continue) any notifications which may pop up on the phone or CASUAL.
When prompted by the phone, press the Volume Up key then continue to Part 2.
Part3: Install Suck It Verizon Insecure Bootloader+Recovery
Start Odin or click the "reset" button at the bottom if it's already open.
Place SuckItVerizon_Odin_Package2.tar.md5.gz into the "Bootloader" section of Odin
Click Start
You may now flash a custom ROM of your choice to your 100% IROM/Bootloader unlocked device. You are now Rooted and have the ability to install any CWM recovery zip with TWRP.
Video instructions
Troubleshooting Windows
Q. Why is CASUAL calling me a noob?
A. You need to Install the "Bootloader Baseline" with odin. We only support ONE bootloader, that's VRALJB.
Put your device into Odin Mode by powering on with Volume Down and Home pressed.
Put the BootloaderBaseline.tgz from above into the "Bootloader" section of Odin.
Click Start.
Q. Why am I bootlooping or the device won't boot?
A. You flashed the wrong thing at the wrong time. Flash the bootloader baseline in Odin, then repeat the instructions above.
Q.Why isn't CASUAL working correctly
A. Try redownloading the latest CASUAL package. Also make sure you're running the latest version of Java.
Q.Why is Odin is failing to open or use the package?
A. The download was damaged. Redownload it.
Q.Other unexplained problems?
A.Try using the proper drivers.
1. Go to device manger right-click and uninstall on the device.
2. Go to add/remove programs, uninstall any driver packages.
3. Unplug your device
4. Install Samsung Kies http://www.samsung.com/us/kies/
Q. How come CASUAL didn't start the first time?
A. Unplug and replug your device, or click CASUAL again and deal with both windows. This is a known issue. I cannot reproduce it in my development environment, it only happens on production compilations in JAR format and affects only Windows. If you'd like to submit a patch, you can get the source and I can add you as a contributor to http://android-casual.googlecode.com.
Q. Why won't CASUAL connect to the device?
A. If you've already installed the PROPER drivers, try disabling any firewalls. ADB uses a network connection to talk to your device. ADB is a network transparent protocol.
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Troubleshooting Device
Q.Why does CASUAL fail to find a rooted device?
A. Check the SuperSU/Superuser Permissions app to verify that you have not inadvertently denied root access to shell.
Q. Why won't my phone start? why is it saying unauthorized software?
A. You unlocked, flashed something, then relocked. You need to flash back to stock VRALJB then repeat the unlock procedure. Use this guide http://forum.xda-developers.com/showthread.php?t=2040264
Q. I'm STILL having a problem.
A. Did you turn it off and then turn it back on again?
Pictures
Heres some pictures to show the newfound capabilities of your device.
TWRP Recovery
{
"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"
}
CASUAL
Verizon device running AT&T firmware
Verizon device running International Firmware
Download count of 63 from testing- Note, do not flash any i9300 ROMs.
Conclusion
Congratulations, You're Unlocked. Your Galaxy Note 2 has gone from the most secure device on the market, to the least secure device publicly available. Your device will now accept any flash. Be careful and dont flash with Odin again. Stick to CWM zip packages so as to lower your risk.
Reserved for technical details
Thanks everybody involved! quick question, you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Edit* Yes you can odin back to a stock i605 rom only!
Thank you Adam. Really appreciate all your hard work
Sent from my SCH-I605 using Tapatalk 2
Thanks! Will report back downloading now
Sent from my SCH-I605 using xda app-developers app
You Rock!
droidstyle said:
Thanks everybody involved! quick question; you say not to odin flash after using this...does that mean we can not odin back to stock after this modification?
Click to expand...
Click to collapse
Yeah I would like to know that as well.
Can't wait to do thus after school! Can't wait for the roms to start flooding the forums.
Sent from my rooted galaxy note 2... U mad?
Amazing, I am speechless!!! Thanks for all your hard work!
awesome work thanks
Thanks for all your work
FTW
Very cool. Great stuff Adam. Suck it Verizon indeed. :highfive:
Well...2 hours to download the Revision3 file on our crappy work internet (but damned if I'm going to wait until I get home). At least I'll get to watch the successes/failures roll in in the meantime.
Also...you mention to stick to flashable zip packages. If I understand correctly, flashing through recovery will still run the typical recovery checks, but ODIN will not?
Is there any reason I can't use Heimdall?
If we want to relock later, we can just flash a stock bootloader?
I already have my system setup how I like it and would like to not have to overwrite it with Revision. Will CASUAL work anyways as long as I have the dependencies?
Thanks so much Adam and Team!
:good:
awesome!
Thank you everyone involved!
I'm assuming that when running AT&T firmware/international firmware it won't recognize our VZW SIM correct? Awesome work though! Super excited about this.
I just wanna thank all of you for Guinea pigging this (so to speak). I'm gonna wait for droidstyles broke down step by step before i do this. Its probably not as bad as I'm making it out to be but I error to the side of caution.
Has anybody actually done this with no problem yet??
This guy is the f*ckin' man!!!
Thanks to everybody involved! Cant wait, I might just leave work now
Sent from my SCH-I605 using xda app-developers app
Q&A for [ROOT] Root with Locked Bootloader for SGP621 using giefroot
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root with Locked Bootloader for SGP621 using giefroot. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Deleted
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
WiFi isssue after flashing D6603 rom
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
russse said:
I'm at (24).
I requested the link to get an unlock code at developer.sonymobile.com. It's now been over 24 hours and i haven't get an email yet. Tried ist with a differnet email adress too.
How long does it take usally?
Click to expand...
Click to collapse
Normaly it takes not more than a few minutes. You can resend it at any time by requesting it again on sonymobile. If it still does not work you may need to get in touch with developer support on their website.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
kamal3383 said:
Hi,
I liked the idea of flashing D6603 rom on my SGP621 and rooting it..
I like my tablet now even more..
But the WiFi is not working for me now, only LTE/3G..
Also the camera not working, but I don't care because I'm using my mobile phone for taking pictures..
Is there any way to make WiFi working with D6603 rom?
Thanks...
Click to expand...
Click to collapse
No, you cannot. As there are other drivers used. If you want root and WiFi you need to follow the tutorial to the end and in the process unlock your bootloader and return to the SGP621 stock rom.
Hi lowtraxx
Thanks a lot for your great work!
I have the SGP611 version and have successfully followed rurie's guide to root the unit. Now i'm installing the rooted stock, but I'm stuck at your step 30. In step 28 I booted into fastboot and used Flashtool to execute the Z3TC-stock-twrp.img by pressing the button "Select system to Flash" and selecting the img-file, see pic.
I have tried to reboot by pressing "Reboot into fastboot mode (via Fastboot) to press volume down on purple light. However, the light never goes purple. It is blue, then swishes to red for an instance/glimpse. I have tried to hold down "volume down" and to press it many times but nothing works. Can you explain step 30 to 32 in detail, e.g. by using the buttons on the Flashtool - Fastboot toolbox (see pic)?
Thanks
{
"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,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
lowtraxx said:
Hi,
I hope you did not flash the SGP621_23.0.1.A.0.167_CE.ftf onto your device but the one that is for the SGP611, because from your description it sounds like you are in a bootloop. I haven't used Flashtool to flash a kernel before, I am only using the command line. But my best guess would be that you need to click on Select Kernel to flash, select the Z3TC-stock-twrp.img and click on flash. Once that is done, you should reboot the device and wait until the Xperia logo shows up and the LED goes purple. If you now press volume down you get into recovery where you need to flash the RICDefeat.zip file you downloaded. If that does not work, download flashtool binary for windows, open a cmd prompt as Administrator, boot into fastboot mode and execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img' and then continue as outlined above.
Click to expand...
Click to collapse
Thanks for your reply. I have used the SGP611 firmware, so no problem.
I have flashed Z3TC-stock-twrp.img unto the unit using the button Select Kernal, but when I reboot the LED never goes purple - only blue and for a quick glimpe (~1-3 ms) red. If I boot the unit in normal mode (without fastboot mode or flash mode) it gets stuck at the Sony logo and cannot be shut down without pressing the small force-shut-down button next to the SD card. (It booted as SPG611 just fine before I flashed Z3TC-stock-twrp.img unto it - using the button Select Kernal.)
EDIT. Tried to download Z3TC-stock-twrp.img again and flash it using CMD in windows. Now I can access Recovery.
I'm progressing, but only slowly.
I'm at step 32 in the guide but every time I try to load/install RICDefeat it fails. Nothing happens when I try to issue 'adb sideload /path/to/RICDefeat.zip', so I have put the file on my external SD card. But when I press "install" - "external_sd" - "RICDefeat.zip" in the twrp Recovery it fails and an error comes: "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
How can I progress? Why do I have to install RICDefeat?
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
lowtraxx said:
Without RICDefeat you are not able to mount the system partition writeable, so you have no real root. The error is odd though. Have you tried downloading the RICDefeat.zip again, maybe it was corrupted too (like the TWRP img)
Click to expand...
Click to collapse
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
centric dk said:
Yes, I have tried downloading it again by clicking "View Raw". I have copied both to the SDcard, but both fails with same error.
Trying to use ADB Sideload and writing "adb devices" in Windows CMD from the folder C:\Users\USERNAME\AppData\Local\Android\sdk\platfo rm-tools just returns an empty list, and installing from SD fails with "Error executing updater binary in zip '/external_sd/RICDefeat.zip'".
Is it possible to go back some steps and try again - without bricking the device? E.g. to step 26? Is there an other place to down the advanced stock kernel?
Click to expand...
Click to collapse
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
Hi,
you will most likely be notified about OTA updates, but you should not take them, because they will not apply properly and most likely remove root again. Just wait for recovery flashable updates or build your own flashable update once the ftfs for the lollipop versions get available. If you want a clean installation without unlocking the bootloader again, just build a flashable zip of a clean ftf and flash that. If you want to send it in for repairs and the like, you can always flash a clean ftf with flashtool, but if you want to root it afterwards you need to unlock the bootloader again.
centric dk said:
It worked! I now have an rooted Z3 tablet compact with stock rom and locked bootloader. :good:
I solved it by tring to go back to step 26 and try one more time (with the same files,and same method). This time I did get the same errors about LED in twrp, but everything worked just like it was suppose to and explained in this guide. The RICDefeat flash just took 5 seconds.
Thank you for helping me!
Last questions:
Will I be able to receive Other OTA updates, e.g. for Lollipop when Sony is ready?
Can I always go back to step 35 if I want a clean/new installation, or do I have to unlock the bootloader first, going back to step 24?
Click to expand...
Click to collapse
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Amplifiction said:
I'm currently trying to flash RICDefeat from recovery and am getting the exact same error you reported. Do you know what exactly changed that allowed you to flash it successfully? Did you use the RAW version? Where did you put it, internal memory or SD?
Thanks!
Click to expand...
Click to collapse
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
centric dk said:
I did not change anything. The second time just went a lot faster as I had tried it before. I put RICdefeat on the SD card.
I also have a Z3 Compact (phone). That it a lot simpler to root and RICdefeat is not needed in that guide. Maybe you can get inspiration there?
Click to expand...
Click to collapse
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Amplifiction said:
I actually have been following a guide in the Z3C forums but ended up with partial root. RICD should be able to solve it, but gave me an arror. When I read you've been having similar problems, I thought I'd give it a go. Thanks anyway.
Click to expand...
Click to collapse
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
centric dk said:
I followed this guide for Z3C (phone): http://forum.xda-developers.com/showpost.php?p=59627168&postcount=120
Click to expand...
Click to collapse
Try this one;
http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980
All works fine.
Hey,
today I got my Xperia X3CT and I followed this Guide to Root my Tablet: http://forum.xda-developers.com/z3-t...gp621-t3013534
(I rooted my LG G2 so I thought I should be able to Root my Tablet without any problems )
At Point 6 I started my Tablet, but somehow it is Stuck in a Bootloop. I am sure I did everything the way the Guide told me to, but somehow my Tablet is still in a Bootloop. How do I get out of it? I can turn the Device of by pressing the Power Button und the Volume Up Button.
Can someone please help?
EDIT: Got out of the Bootloop by flashing back to SGP621_23.0.1.A.0.167_CE.ftf. That was quite a shocker
I think the Problem was that I was at 23.1.A.0.690. Now that I am at 23.0.1.A.0.167 it should make any problems? Or could there be another Problem? Would be thankful for help
Emildeon said:
I think the Problem was that I was at 23.1.A.0.690.
Click to expand...
Click to collapse
That was the problem , you must follow the manual from kitkat (23.0.1.A.0.167) . I advise to use http://forum.xda-developers.com/z3-...to-rooted-lollipop-locked-bootloader-t3083980 ( No need to open the bootloader ). I made a guide in Spanish
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"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"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?