Database Users

[BUSYBOX]Busybox Installation - Droid Ultra General

Don't Use.

That's awesome! Thanks for this. What about xposed? I guess since this flashes blocks 1, 5, 16 there isn't a way to add it before or after.
Sent from my locked but not stocked XT1080.

chuck864 said:
That's awesome! Thanks for this. What about xposed? I guess since this flashes blocks 1, 5, 16 there isn't a way to add it before or after.
Sent from my locked but not stocked XT1080.
Click to expand...
Click to collapse
If I remember correctly, this includes Xposed.
Sent from my Nexus 6 using Tapatalk

Yeah, you said it originally but it wasn't listed in your last post. Maybe add what all is included at the top of the OP for any new comers.
Sent from my locked but not stocked XT1080.

chuck864 said:
Yeah, you said it originally but it wasn't listed in your last post. Maybe add what all is included at the top of the OP for any new comers.
Sent from my locked but not stocked XT1080.
Click to expand...
Click to collapse
Gotcha, added to OP.
Sent from my Nexus 6 using Tapatalk

after flashed. I can install safestrap then flash custom rom??

Quick question. In the starting of the guide , it says
Warning : It wipes off all data.
Then in step 5, you talk about modified XML which helps you to keep data. So is it safe to assume that data is preserved during flash ?
Edit : NVM, Saw your note in the middle of the post. My Bad.
BTW, thanks OP for providing debloated ROM and Viper4android . Finally the perfect ROM *_*
Tuulaihuu said:
after flashed. I can install safestrap then flash custom rom??
Click to expand...
Click to collapse
I feel sorry for OP and the other users here who have said a countless number of times that this ain't possible as of now due to write protect = 1 :3

I think many people tried to download this, dropbox says:
Error (429)
This account's public links are generating too much traffic and have been temporarily disabled!
can someone upload a copy to for example google-drive?

pizmak said:
I think many people tried to download this, dropbox says:
Error (429)
This account's public links are generating too much traffic and have been temporarily disabled!
can someone upload a copy to for example google-drive?
Click to expand...
Click to collapse
I will, one second.
Edit: Updated.
Sent from my Nexus 6 using Tapatalk

Question
If my phone is already rooted, do I still have to start from scratch?
And, how much time should this take?
I read somewhere it was 16 hours?

hazam1992 said:
If my phone is already rooted, do I still have to start from scratch?
And, how much time should this take?
I read somewhere it was 16 hours?
Click to expand...
Click to collapse
Yes and yes.
Sent from my locked but not stocked XT1080.

thenameisnigel said:
If I remember correctly, this includes Xposed.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just double checking, when i reflash this my phone will automatically have xposed, busybox, & viper4android after following the directions, and where it says get busybox RIGHT HERE there isn't a link, that is the reason i'm just getting my facts straight. my phone is almost at 100% and i wanna do this right. Thank you sooooooo much crash and @thenameisnigel for all of the work put into this.

jblock92 said:
Just double checking, when i reflash this my phone will automatically have xposed, busybox, & viper4android after following the directions, and where it says get busybox RIGHT HERE there isn't a link, that is the reason i'm just getting my facts straight. my phone is almost at 100% and i wanna do this right. Thank you sooooooo much @CrashXXL and @thenameisnigel for all of the work put into this.
Click to expand...
Click to collapse
Link fixed and yes, everything will work after it's reflashed.

thenameisnigel said:
Link fixed and yes, everything will work after it's reflashed.
Click to expand...
Click to collapse
ok and sorry but 2 more things, are the edited xml files included in the (the firmware here) link because i didnt see a link there for it ( i'm still downloading off wifi so i cant check), and other is the busy box comes up on my pc as "busybox-armv7l" and its file type is file, so before i move it i'm to rename it as plain "busybox" and do i have to alter the file extension or leave it as is? sorry I haven't done any of this stuff since rooting the droid bionic so i'm a little rusty
and all of the extra batch files for example Runsys_1-5 will auto run in the process?
---------- Post added at 10:44 PM ---------- Previous post was at 10:15 PM ----------
jblock92 said:
ok and sorry but 2 more things, are the edited xml files included in the (the firmware here) link because i didnt see a link there for it ( i'm still downloading off wifi so i cant check), and other is the busy box comes up on my pc as "busybox-armv7l" and its file type is file, so before i move it i'm to rename it as plain "busybox" and do i have to alter the file extension or leave it as is? sorry I haven't done any of this stuff since rooting the droid bionic so i'm a little rusty
and all of the extra batch files for example Runsys_1-5 will auto run in the process?
Click to expand...
Click to collapse
i guess what i mean is the stuff added through you such as the added batch files and the sys folder gonna automatically do its thing when i reflash?
---------- Post added at 11:35 PM ---------- Previous post was at 10:44 PM ----------
please help my loose cord accidently unplugged during flashing system.img 7/16 in rsd and keep getting fail now
nvm restarting rsd seemed to fix

jblock92 said:
and all of the extra batch files for example Runsys_1-5 will auto run in the process?
i guess what i mean is the stuff added through you such as the added batch files and the sys folder gonna automatically do its thing when i reflash?
Click to expand...
Click to collapse
Yeah, I have looked around and can't find what .bat file to run. The RUN_SYS1,2,3,4,5 look like they would be it but I'm not sure if you run just the first or all of them. I am downloading the files now and will look into it more once it completes. The guide is confusing because it's just a quickly patched version of somberfox's. I will see if I can clean it up once I have all the details.
EDIT: Looks like you have to run every RUN_SYS.bat file in order. They are broke up so you can charge your phone in between each one I believe. YOU DO NOT want your battery to die will doing this.

** UPDATED ** I take no credit or responsibility for this. Please do what ever you want with it.
** YOU NEED ROOT ACCESS FOR THIS. IF YOU DO NOT HAVE IT THEN FOLLOW THE GUIDE HERE
Instructions
This entire method is the work of user @CrashXXL and Busybox/V4A/Debloated/Xposed installation by @thenameisnigel. This is a literal copy and paste of @somberfox 's awesome guide with just busybox instructions (Thank you, you're the best for the guide as I'm terrible at rightups). I am ONLY writing it up like this to make the instructions as plain as possible for anyone to follow. All credit goes to @CrashXXL for this awesome hack. Normal warnings, it isn’t my fault, and it isn’t crashxxl’s fault if your phone gets ****ed up because you messed up the process or didn’t read things through carefully. This is an AT YOUR OWN RISK situation. If you can’t afford to lose your phone, don’t do this.
******* WARNING *******
MAKE SURE YOU HAVE A FACTORY CABLE THAT WILL CHARGE YOUR PHONE WHILE IN FASTBOOT. DO THIS BY BOOTING INTO FASTBOOT WITH YOUR PHONE PLUGGED INTO THE CHARGER AND SEE IF IT SAYS THE BATTERY IS CHARGING. IF YOU CAN NOT CHARGE YOUR PHONE IN FASTBOOT THEN YOU CAN NOT DO THIS METOD.
******* END WARNING *******
WHAT THIS ACHIEVES: This will give your phone Root/Busybox/V4A/Debloated/Xposed but WILL NOT turn off /system write protection.
WARNING: THIS WIPES ALL DATA ON YOUR PHONE. Backup any pictures or files you have stored there that you want to keep. UPDATE: YOU CAN KEEP ALL DATA WITH THE XML FILE LINKED IN THE FILES SECTION, but I would still recommend backing things up. Seriously, it's your data. Back it up.
This method works on the following phones:
-Droid Mini XT1030 SU6-7
-Droid MAXX XT1080m SU6-7
-Droid Ultra XT1080 SU6-7
NEEDED FILES
RSD Lite
Motorola Drivers – (if you don’t have these, or know if you have them, get them)
This firmware, CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml.zip
The Soft_and_Drivers.rar file from here
Download Python27.zip from here.
Edited XML file to maintain data in reflash. Thank you user @chuck864 for providing this!
THE PROCESS (Do yourself a favor, start with a fully charged phone)
1.)Install RSD Lite
2.)Install Motorola Drivers
3.)Open the Soft_and_Drivers.zip and extract the files. Install Python 2.7.9 first, and then install pyserial 2.7. This should create a Python27 folder on your C: drive (or other base computer drive). This will be our working folder. Extract the windows_drivers_QHSUSB_DLOAD.zip to the Python27 folder for safe keeping. You might not need this.
4.)Extract everything in the Python27.zip you downloaded to your desktop and copy the contents of the python27 folder you just extracted to the Python27 folder on your C: drive. Overwrite everything.
5.)Create a folder in Python27 called “444” and extract the CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml.zip to that folder. IF YOU WISH TO SAVE THE DATA ON YOUR PHONE, now extract the Edited XML file you downloaded above and copy it into your 444 folder and replace the old version of the file. This one has been edited to allow you to keep your data during the next step.
5.1) DO NOT FORGET THIS STEP.
On your phone, go to a shell and run
Code:
su
cp -R /system/xbin /data/xbin
THIS IS IMPORTANT.
6.) Power down your phone entirely and boot into FASTBOOT. You do this by holding down the POWER and the VOLUME DOWN button at the same time for ten seconds. When you release them you'll be in FASTBOOT. Now plug your phone into your computer (NOT INTO A USB 3.0 PORT, those are off limits for this whole install), and run RSD Lite. Click the “…” next to the blank space that says “filename” and navigate to the “444” folder you just extracted. Select the XML file and click “ok”. Now click “Start” and wait for the process to run and for your phone to reboot. IF THIS PROCESS FAILS and you get something that says “failed flashing process, unknown fastboot command,” then you need to go into the XML file in your “444” folder and delete the line . Then start STEP 6 over again and it should work this time.
7.)After the reboot, boot your phone into FASTBOOT. This is done by powering down your phone all the way (make sure you are not plugged into your USB cable) and then press and hold the POWER and VOLUME DOWN (at least on the Maxx) button on your phone at the same time. Hold this for about ten seconds and then let go. You’ll be in fastboot.
8.)Run BLBROKE.bat from your Python27 folder. This will run a script that is essentially bricking your phone. Your screen will go black. Leave it alone for a minute or two, and then open up your “Devices and Printers” control panel frame and see if you have something listed called qualcomm hs-usb qdloader 9008. If you do, go to STEP 9. If you do not, try unplugging your phone from your computer, and then plugging it back in. Wait for it to be recognized. If you STILL don’t have qualcomm hs-usb qdloader 9008 listed under Devices and Printers, go to device manager and look for it RIGHT HERE.
It will probably be listed as “Unknown Device”. If this is the case, open up the “Unknown Device” and click “Update Driver” and then “Browse Computer.” Remember the windows_drivers_QHSUSB_DLOAD.zip you extracted in STEP 3? Navigate to that folder and tell it to look for the drivers there. It will find them. Install, and you’re good to go! You may need to unplug your phone and plug it back in, but you might not.
IF YOU CANNOT GET THE DRIVER TO INSTALL, it is probably because you need to allow the running of unsigned drivers. Do a google search for "allow unsigned drivers" and your version of windows. This tutorial is long enough without adding that process to it.
******* FINAL WARNING ********
THIS IS NOT FOR THE FAINT OF HEART OR ANYONE WHO DOESN"T WANT TO THROW THEIR PHONE IN THE TRASH!
SCARED YET??? YOU WILL BE. YOU WILL BE.
YOU CAN SIMPLY RUN RUN_SBL.bat IN YOUR PYTHON27 FOLDER AND YOUR PHONE WILL REBOOT NORMALY.
I HAVE NOT DONE THIS AND AM ONLY REPOSTING THE DIRECTIONS I HAVE READ SO YOU ARE ON YOUR OWN.
THIS IS YOUR LAST CHANCE TO RUN TO SAFTEY AND ENJOY WHAT EVER IS LEFT OF YOUR DAY!
********* END OF FINAL WARNING ********
STILL HERE?
9.)This process will take 10+ hours.
Run RUN_SYS1.bat, This will flash (1-30) parts of system section
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS2.bat,This will flash 30 (31-60) Parts of partition system.
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS3.bat,This will flash 30 (61-90) Parts of partition system.
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS4.bat,This will flash 30 (90-120) Parts of partition system.
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS5.bat,This will flash 30 (121-132) Parts of partition system.
When it’s done, your phone should reboot and start up normally.
After the phone boots, run the following steps to install busybox.
1. Download busybox-armv7l from RIGHT HERE.
2. Use a root file explorer to copy busybox-armv7l to your /data/xbin folder and rename it busybox
3. Open terminal and type busybox --install /data/xbin
4. Reboot your phone.
You should now have root, xposed, busybox, and debloat if all went well.
Go and get a beer for a job well done! :highfive:
FAQ
q. Will sunshine work?
a. No, sunshine will not work after this method.
q. Can I install and use (insert an app name here)?
a. Any root app can be installed and used, BUT if the app takes access to /system to work then you will have to bake-in the app and reflash your phone to get it working. It’s not a simple process.
q. How do I get into FASTBOOT?
a. Well, if you didn't read Step 7 where it tells you how to do this already, here is how this is done (again): Power the device off completely and make sure it's not plugged in. Now hold down the POWER and VOLUME DOWN button for about ten seconds and then let them go. This will get you into fastboot.
q. Hey, none of the changes I made to system/ stuck after I rebooted my phone. What gives?!
a. NO CHANGES TO SYSTEM/ WILL PERSIST AFTER A HARD REBOOT. NONE EXCEPT BUSYBOX UPGRADES.
Also, if you love this Root setup as much as I do, PLEASE consider donating to CrashXXL! He has done great work on this and donations help keep folks like him working on innovations for us.

chuck864 said:
Please do what ever you want with it.
Click to expand...
Click to collapse
Sorry, I'm real lazy and don't not speak windows hardly at all.
Say I have one of those cool chargey factory cords and I wanna use linux to do all this, is there any reason I couldn't just plug the phone in with that cord, use a bash script something like this:
Code:
#!/usr/bin/bash
python qdloadSYS1.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS2.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS3.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS4.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS5.py MPRG8960.bin -ptf _SYS/partitions.txt
and go wash dishes (I am real lazy and ain't not done them in awhile)?
I see some notes on flashing blbroke in betwixt each step is why I ask. Not that I really want to wash dishes er nuthin'. It doesn't fix the bootloader at each step does it? If so, is there some re-write on the qdload that could allow the whole shebang in one step? Given I have one of those factory cords (and a short attention span)?
Again, this hinges on having a factory cord that allows you to disregard the state of the battery.

chuck864 said:
** UPDATED ** I take no credit or responsibility for this. Please do what ever you want with it.
Instructions
This entire method is the work of user @CrashXXL and Busybox/V4A/Debloated/Xposed installation by @thenameisnigel. This is a literal copy and paste of @somberfox 's awesome guide with just busybox instructions (Thank you, you're the best for the guide as I'm terrible at rightups). I am ONLY writing it up like this to make the instructions as plain as possible for anyone to follow. All credit goes to @CrashXXL for this awesome hack. Normal warnings, it isn’t my fault, and it isn’t crashxxl’s fault if your phone gets ****ed up because you messed up the process or didn’t read things through carefully. This is an AT YOUR OWN RISK situation. If you can’t afford to lose your phone, don’t do this.
******* WARNING *******
MAKE SURE YOU HAVE A FACTORY CABLE THAT WILL CHARGE YOUR PHONE WHILE IN FASTBOOT. DO THIS BY BOOTING INTO FASTBOOT WITH YOUR PHONE PLUGGED INTO THE CHARGER AND SEE IF IT SAYS THE BATTERY IS CHARGING. IF YOU CAN NOT CHARGE YOUR PHONE IN FASTBOOT THEN YOU CAN NOT DO THIS METOD.
******* END WARNING *******
WHAT THIS ACHIEVES: This will give your phone Root/Busybox/V4A/Debloated/Xposed but WILL NOT turn off /system write protection.
WARNING: THIS WIPES ALL DATA ON YOUR PHONE. Backup any pictures or files you have stored there that you want to keep. UPDATE: YOU CAN KEEP ALL DATA WITH THE XML FILE LINKED IN THE FILES SECTION, but I would still recommend backing things up. Seriously, it's your data. Back it up.
This method works on the following phones:
- Droid Mini XT1030 SU6-7
- Droid MAXX XT1080m SU6-7
- Droid Ultra XT1080 SU6-7
If you are already rooted using crashxxl's method and are running 6-7 then read below. If not, then skip to "NEEDED FILES".
*********************************************************************************
* Section For people who have already rooted using Crashxxl's method running 6-7.
* Download this file. Here.
* Only do steps 4, 5.1, 9
*********************************************************************************
NEEDED FILES
RSD Lite
Motorola Drivers – (if you don’t have these, or know if you have them, get them)
This firmware, CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml.zip
The Soft_and_Drivers.rar file from here
Download Python27.zip from here.
Edited XML file to maintain data in reflash. Thank you user @chuck864 for providing this!
THE PROCESS (Do yourself a favor, start with a fully charged phone)
1.)Install RSD Lite
2.)Install Motorola Drivers
3.)Open the Soft_and_Drivers.zip and extract the files. Install Python 2.7.9 first, and then install pyserial 2.7. This should create a Python27 folder on your C: drive (or other base computer drive). This will be our working folder. Extract the windows_drivers_QHSUSB_DLOAD.zip to the Python27 folder for safe keeping. You might not need this.
4.)Extract everything in the Python27.zip you downloaded to your desktop and copy the contents of the python27 folder you just extracted to the Python27 folder on your C: drive. Overwrite everything.
5.)Create a folder in Python27 called “444” and extract the CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml.zip to that folder. IF YOU WISH TO SAVE THE DATA ON YOUR PHONE, now extract the Edited XML file you downloaded above and copy it into your 444 folder and replace the old version of the file. This one has been edited to allow you to keep your data during the next step.
5.1) DO NOT FORGET THIS STEP.
On your phone, go to a shell and run
Code:
cp -R /system/xbin /data/xbin
THIS IS IMPORTANT.
6.) Power down your phone entirely and boot into FASTBOOT. You do this by holding down the POWER and the VOLUME DOWN button at the same time for ten seconds. When you release them you'll be in FASTBOOT. Now plug your phone into your computer (NOT INTO A USB 3.0 PORT, those are off limits for this whole install), and run RSD Lite. Click the “…” next to the blank space that says “filename” and navigate to the “444” folder you just extracted. Select the XML file and click “ok”. Now click “Start” and wait for the process to run and for your phone to reboot. IF THIS PROCESS FAILS and you get something that says “failed flashing process, unknown fastboot command,” then you need to go into the XML file in your “444” folder and delete the line . Then start STEP 6 over again and it should work this time.
7.)After the reboot, boot your phone into FASTBOOT. This is done by powering down your phone all the way (make sure you are not plugged into your USB cable) and then press and hold the POWER and VOLUME DOWN (at least on the Maxx) button on your phone at the same time. Hold this for about ten seconds and then let go. You’ll be in fastboot.
8.)Run BLBROKE.bat from your Python27 folder. This will run a script that is essentially bricking your phone. Your screen will go black. Leave it alone for a minute or two, and then open up your “Devices and Printers” control panel frame and see if you have something listed called qualcomm hs-usb qdloader 9008. If you do, go to STEP 9. If you do not, try unplugging your phone from your computer, and then plugging it back in. Wait for it to be recognized. If you STILL don’t have qualcomm hs-usb qdloader 9008 listed under Devices and Printers, go to device manager and look for it RIGHT HERE.
It will probably be listed as “Unknown Device”. If this is the case, open up the “Unknown Device” and click “Update Driver” and then “Browse Computer.” Remember the windows_drivers_QHSUSB_DLOAD.zip you extracted in STEP 3? Navigate to that folder and tell it to look for the drivers there. It will find them. Install, and you’re good to go! You may need to unplug your phone and plug it back in, but you might not.
IF YOU CANNOT GET THE DRIVER TO INSTALL, it is probably because you need to allow the running of unsigned drivers. Do a google search for "allow unsigned drivers" and your version of windows. This tutorial is long enough without adding that process to it.
******* FINAL WARNING ********
THIS IS NOT FOR THE FAINT OF HEART OR ANYONE WHO DOESN"T WANT TO THROW THEIR PHONE IN THE TRASH!
SCARED YET??? YOU WILL BE. YOU WILL BE.
YOU CAN SIMPLY RUN RUN_SBL.bat IN YOUR PYTHON27 FOLDER AND YOUR PHONE WILL REBOOT NORMALY.
I HAVE NOT DONE THIS AND AM ONLY REPOSTING THE DIRECTIONS I HAVE READ SO YOU ARE ON YOUR OWN.
THIS IS YOUR LAST CHANCE TO RUN TO SAFTEY AND ENJOY WHAT EVER IS LEFT OF YOUR DAY!
********* END OF FINAL WARNING ********
STILL HERE?
9.)This process will take 10+ hours.
Run RUN_SYS1.bat, This will flash (1-30) parts of system section
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS2.bat,This will flash 30 (31-60) Parts of partition system.
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS3.bat,This will flash 30 (61-90) Parts of partition system.
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS4.bat,This will flash 30 (90-120) Parts of partition system.
After it completes, the phone will try to start and will hang on the logo, boot into fastboot. Let the battery charge for 15-20 minutes and then run BLBROKE.bat from your Python27 folder again.
Run RUN_SYS5.bat,This will flash 30 (121-132) Parts of partition system.
When it’s done, your phone will reboot and you will have root, busybox, etc.
Go and get a beer for a job well done! :highfive:
FAQ
q. Will sunshine work?
a. No, sunshine will not work after this method.
q. Can I install and use (insert an app name here)?
a. Any root app can be installed and used, BUT if the app takes access to /system to work then you will have to bake-in the app and reflash your phone to get it working. It’s not a simple process.
q. How do I get into FASTBOOT?
a. Well, if you didn't read Step 7 where it tells you how to do this already, here is how this is done (again): Power the device off completely and make sure it's not plugged in. Now hold down the POWER and VOLUME DOWN button for about ten seconds and then let them go. This will get you into fastboot.
q. Hey, none of the changes I made to system/ stuck after I rebooted my phone. What gives?!
a. NO CHANGES TO SYSTEM/ WILL PERSIST AFTER A HARD REBOOT. NONE EXCEPT BUSYBOX UPGRADES.
Also, if you love this Root setup as much as I do, PLEASE consider donating to CrashXXL! He has done great work on this and donations help keep folks like him working on innovations for us.
Click to expand...
Click to collapse
I have been stuck on 7/16 flashing system.img in rsd for 6 hours now is that normal
---------- Post added at 05:11 AM ---------- Previous post was at 04:52 AM ----------
jblock92 said:
I have been stuck on 7/16 flashing system.img in rsd for 6 hours now is that normal
Click to expand...
Click to collapse
will i brick if i unplug reboot and give up?

gilbertiddi0 said:
Sorry, I'm real lazy and don't not speak windows hardly at all.
Say I have one of those cool chargey factory cords and I wanna use linux to do all this, is there any reason I couldn't just plug the phone in with that cord, use a bash script something like this:
Code:
#!/usr/bin/bash
python qdloadSYS1.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS2.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS3.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS4.py MPRG8960.bin -ptf _SYS/partitions.txt
python qdloadSYS5.py MPRG8960.bin -ptf _SYS/partitions.txt
and go wash dishes (I am real lazy and ain't not done them in awhile)?
I see some notes on flashing blbroke in betwixt each step is why I ask. Not that I really want to wash dishes er nuthin'. It doesn't fix the bootloader at each step does it? If so, is there some re-write on the qdload that could allow the whole shebang in one step? Given I have one of those factory cords (and a short attention span)?
Again, this hinges on having a factory cord that allows you to disregard the state of the battery.
Click to expand...
Click to collapse
I'm not sure about Linux, but the reason it is broken into 5 steps is because your battery will not last long enough to do it all at once. You have to run blbroke each time because the script fixes your boot loader so you can boot into fastboot to charge your battery. (It won't charge in qdload mode from my understanding.) All this is from crashxxl's original post on the Russian forums and he knows what he is talking about.
Sent from my locked but not stocked XT1080.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jblock92 said:
I have been stuck on 7/16 flashing system.img in rsd for 6 hours now is that normal
---------- Post added at 05:11 AM ---------- Previous post was at 04:52 AM ----------
will i brick if i unplug reboot and give up?
Click to expand...
Click to collapse
6 hours definitely isn't normal. Can you screenshot the window for us?
Sent from my locked but not stocked XT1080.

chuck864 said:
I'm not sure about Linux, but the reason it is broken into 5 steps is because your battery will not last long enough to do it all at once. You have to run blbroke each time because the script fixes your boot loader so you can boot into fastboot to charge your battery. (It won't charge in qdload mode from my understanding.) All this is from crashxxl's original post on the Russian forums and he knows what he is talking about.
Sent from my locked but not stocked XT1080.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
6 hours definitely isn't normal. Can you screenshot the window for us?
Sent from my locked but not stocked XT1080.
Click to expand...
Click to collapse
it failed, now i cant even get past 2/16 flashing gpt.bin

Related

OUTDATED[Guide] Setting up/using adb/fastboot-unlock, flash custom recovery & root
Below is a great guide to rooting, from several sources, (mostly taken from pingvinen's "An Idiot's Guide to Flashing the Xoom" and a guide by publicanimal. and I hope it helps. You can find the links to all of the files referenced below in the Xoom Heaven thread (thanks StrifeSoldierVII!)[/I]
(New thread in General Section by Jack207407 will have all the updated links for flashing
http://forum.xda-developers.com/showthread.php?t=1443110
One Stop For ROM's, MOD's, and Root Wifi-Only and 3G/4G Models)
"What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and don't try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned.
HERE'S THE USUAL DISCLAIMER--I AM NOT RESPONSIBLE FOR ANY HARM THAT MAY COME TO YOUR DEVICE IF YOU FOLLOW ANY PART OF THIS GUIDE--ANY RISK IS ON THE USER!
I strongly recommend you to read the entire guide before trying. In fact, read it twice to ensure that you have understood everything. If there is weird stuff that you don't understand, don't hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but no one (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
Just a note before we begin: the different Xoom. Models that are able to use this guide are the following:
MZ600 - stingray_cdma - Motorola US 3g Xoom (technically this device is stingray as well, but I will be using stingray_cdma as the two devices have incompatible software)
MZ601 - utms_everest - Motorola EU 3g Xoom
MZ602 - stingray - Motorola US 4g Xoom
MZ604 - wingray - Motorola Wifi Xoom
(thanks solarnz!)
___________
Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity) 2. Install Java SDK and Android SDK tools (for adb and fastboot commands) 3. Unlock the device for flashing (allowing replacement of recovery and boot images) 4. Install a modified recovery image (ClockWorkMod recovery for Android) 5. Root the device (Allow r/w access to the device filesystem) 6. Flash a kernel that supports overclocking etc.
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows PC. Windows 7, Mac and Linux users will probably have to do some steps differently.
1.0 Install the latest Motorola USB drivers
The installation file can be found at: http://developer.motorola.com/docstools/USB_Drivers/
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2.0 Installation of development software
Android SDK and Java SDK need to be installed. You can find the installation kits here.
http://developer.android.com/sdk/index.html In case you can't find fastboot.exe, look for it here (thanks to jerrycycle): http://forum.xda-developers.com/showpost.php?p=19546334&postcount=5
Update: you could also just install the adb fastboot pack here:http://www.android.net/forum/downloads.php?do=file&id=67
http://www.oracle.com/technetwork/java/javase/downloads/index.html
2.1 Install them as any other software, making an Android SDK folder on C/.
2.2 Make sure that all the files you need are in the Platform Tools folder (fastboot, recovery image file and so on). Copy any files in the Tools folder to the Platform Tools folder if necessary. Note: If the Android SDK complains that the Java Dev Kit can't be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
(Warning: Never put any zip files in your Platform Tools folder. Flashing zip files through fastboot will cause very serious problems. Zip files must be flashed from the external micro SD card through CWM recovery on the Xoom...we'll get to that later.)
2.3 Test that ADB and FASTBOOT works. You should open a command window by right clicking in your Platform Tools folder where all of your files are, plug in your Xoom to your computer with your Motorola cable (it may not work with a generic cable) and write 'adb devices'. Your Xoom should now be listed. Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom.
Optional: Those that want to be able to access adb from any where on their computer, here's a tip from scsa20: "For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon ().
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%Sy stemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\ System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
It's long but do you see the android stuff there at the end?"
Update: xda poster Mandelbrot Benoit suggests an alternate adb setup, here: http://forum.xda-developers.com/showpost.php?p=18072572&postcount=50
If your windows computer doesn't see your Xoom, consider this (Originally Posted by AngryBulleteyeTruth):
When the xoom does not show up on PC it may be the problem of.... windows media player!
Xoom uses drivers of WMP to communicate with PC. If someone does not have the newest WMP drivers it will not show up and you can see xoom device in the devices tab on PC having an exclamation mark.
So the solution is to download and install Windows Media Player 11. It has worked for me.
--------
OK. Now that you are set up, it's Showtime! Take a deep breath...
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to secure important data before you start. (It will also void your warranty, so you still have time to go back.)
3.1 Power up and start the Xoom.
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode.
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal. Don't bother to do any setup at this time, just make sure that USB debbuging is checked in settings, and now go on to step 4
4. Install recovery image (CWM) UPDATED 4/19/12
If you haven't done it already, download the recovery image file and save it to your computer in the Platform Tools folder.
(Download the recovery image from this link: http://forum.xda-developers.com/showthread.php?t=1604014 only the img file flashed through fastboot Remember, never try to flash a zip file through fastboot!)
Important: At this time, make sure you have a good (known to be working) microsd card in your sdcard slot in your Xoom. Reboot the Xoom with the sdcard in the slot to make sure it's mounted.
4.1 Boot into flash mode with 'adb reboot bootloader.'
4.2 Install your downloaded recovery image: 'fastboot flash recovery eos-recovery-r6.img' or whatever is the exact name of the recovery img file you are flashing.
4.3 Enter CWM recovery with the procedure below.
4.4 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work (if you see Starting Fastboot Protocol), experiment with the timing (see below).
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for getting this far!
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. Just repeat steps 4.1 through 4.6 if that happens.
UPDATE(12/28/11) Since putting this guide together, Motorola has issued a number of Over-the-Air (OTA) updates that have complicated the process of flashing the Clockawork Mod recovery, so if you have accepted any OTA updates, please read the following, which describes each step (http://forum.xda-developers.com/showthread.php?p=26009191#post26008083) (Thanks to Landorin.)
(If you have root and want to remove these files, remove or rename /system/etc/install-recovery.sh with something like root explorer. You can then flash your custom recovery through fastboot again.)
For those of you that get stuck with some error like 'device not recognized' poster Madjinj gives the following advice:
1) Be sure that you have your adb folder in the root of C drive directly and be sure that you are in adb folder in command prompt program (CMD in Windows machines) i.e by typing "cd c:\XXX" where XXX is the name of adb folder in your machine.
2) Be sure that you type "adb reboot bootloader" in comand prompt to activate adb program. if the problem persists, try typing "fastboot reboot" then after reboot type "adb reboot bootloader" in command prompt program.
3) Use the USB cable that came with your Xoom (some cables are not good in flashing for unknown reason..!!
4) make sure that you activate USB debugging mode.
5.0. Rooting the Xoom
The Universal Xoom Root zip file from solarnz is located here: http://forum.xda-developers.com/showthread.php?t=1242241
5.1 You need to transfer the Universal Xoom Root zip file to a working external micro SD card. You can do this on a computer or cell phone, but the Universal Xoom Root zip file must be located in the root directory of the micro SD card.
5.2 Insert the now prepared SD card in the Xoom.
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option.
5.4 Select 'Install ZIP from sd card.'
5.5 Select 'Choose ZIP.'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install any app requiring root and start it. If the rooting was successful, then the app should request superuser permission and you should be able to grant it without any problems.
6. Flashing a new rom or kernel...(e.g. Tiamat Moray Rom and/or Odachi Kernel). Look in the Xoom Heaven thread or in the Development section of this form for all of these files.
6.1 This step is identical to 5, but swap out the ROOT zip for the ROM or KERNEL zip. For simplicity, you may want to prepare the micro SD card with both zip files at the same time in step 5.1..."
------------------------
This is still one of the best explanations of how to use adb and fastboot to unlock and root the Xoom and install a custom recovery, etc, and doesn't deserve to buries on back pages of this forum. Hopefully, the step-by-step nature of this guide will help those of you that have limited experience with this kind of tinkering.
Oh, and please feel free to correct any errors or omissions. As I said, it came from several sources and needed to somewhat updated.

Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium

fastyan said:
Thank you, just bought my xoom yesterday and was confused on the steps to take!
This has made it as clear as possible for me and will follow your instructions to the letter tonight.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
Good luck! Let us know how you make out and if anything needs to be clarified.

think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples

fastyan said:
think im doing something wrong as unlocked fine but when i go to install the recovery file it keeps coming up cannot load? any ideas where im going wrong?
been at it 3 hours now lol and losing the will to live im sure its gona be something simples
Click to expand...
Click to collapse
Check to make sure that your file download is good, and that you are typing it's name correctly. Better yet, you could rename the file "recovery.img" and that will make it very easy to get it right.

On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium

fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
When you're in the bootloader, you won't be able to access the SD Card or anything of that sort and adb won't work, in stead, when you're in the bootloader, you're switching over to fastboot. I'm sure if you type in fastboot devices you'll see your xoom listed.

Thank you for the reply and that's one thing sorted but any idea why its telling me "cannot load recovery"? I have tried renaming it and downloaded the recovery file 4 times incase that was wrong but still no joy :-(
I have done this all before on my phone and never had a problem so I must be missing something but f$*@ed if I know what?
Thanks again for your help though.
Sent from my Desire HD using xda premium

Just had a thought. Could it be that the XOOM hasn't actually unlocked, would that cause it to not load? Is there any way to check if its unlocked successfully? Although I did try it twice before?
Sent from my MZ604 using xda premium

Once you got it in the bootloader, you gotta make sure you do fastboot oem unlock, press volume down then up, press volume down again then up again, and let it format and reboot.
If it's already unlocked, you'd get a message telling you so (generally).
Then when you go to flash the recovery, make sure that the recovery image is in the folder where fastboot is and type in fastboot flash recovery recovery.img (if I remember the syntax that is, I'm at work and don't feel like scrolling up or going into the root guide to confirm xD ).

fastyan said:
On the sd card?I thought we had to put it into sdk platform tools? I have put it and renamed it onto my sd card but what is the command to flash recovery from sd card?
Also noticed once I have done "adb reboot bootloader" my computer doesn't see the XOOM properly, is in can't see it in my computer but does make a noise when I connect and disconnect is this correct? Debugging is on.
Sent from my MZ604 using xda premium[/QUOTE
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse

okantomi said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote.Oof course the cwm recovery img.. goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
Click to expand...
Click to collapse
With the way I have my system setup, I can run adb and fastboot wherever I am

No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.

scsa20 said:
With the way I have my system setup, I can run adb and fastboot wherever I am
Click to expand...
Click to collapse
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.

fastyan said:
No, sorry, I was trying to respond. when I was tired and distracted.I totally miswrote. Of course the cwm recovery img goes in the platform tools...thank goodness you guys are out there to catch mistakes!
So, I don't know if you had any progress, but not successfully unlocking would surely stop you in your tracks.
No progress yet as im at work but when I get home I will start the process from scratch again and see how I get on and will keep you posted.
Click to expand...
Click to collapse
If, as you follow this guide, you find any explanations that are not clear or if you think of a step to take or something else that might improve the guide, please post it and we can add it in. It's been almost 6 months since I've unlocked and at least a couple of months since I've had to use adb, so I'm sure I've forgotten some things. Those of you whose experience is fresh can give really good advice. That's how this guide was originally written, by pingvinen, right after he had gone through a grueling rooting process.

okantomi said:
Care to share???
That would be helpful to many, I'm sure. We could add it to the guide, along with anything else you can think of.
Click to expand...
Click to collapse
For windows, if you go into System Properties and choose Advanced, then Environment Variables..., you'll be able to edit the Path variable under System variables, just add the path to where adb and fastboot is located (separated with a semi-colon (;)).
Here's what my Path variable looks like:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\android-sdk-windows\tools;C:\android-sdk-windows\platform-tools;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\
Click to expand...
Click to collapse
It's long but hey, see where the android stuff is near the end?

@Okantomi:
We all have learned some things from trial & error (eg.the sk cannot detect java dev kit)
i could only flash recovery after renaming it to recovery(do not forget to add.img in cmd while flashing).also the official motorola name recovery as same.
after downloading sdk and updating to platform tools i have kept a zip in safe location so that i do not need to download again platform tools if i install sdk fresh
initially knowledge was scattered now it is at one place.
right now testing steady hawkin's kernel and new recovery
btw good signature pic.

Ok so another night has gone and still can't get recovery on!! Tried re unlocking the XOOM and every time it comes up with "cannot load recovery.img" I tried installing everything on my laptop and went right from the start and getting exactly the same thing!
Starting to think im never gonna get this sorted now :-( just feels like the XOOM isn't unlocking? Every time I go through the unlocking process it never states that its already unlocked? Is there any way I can check that it is unlocked?
Please help im losing the will to live now lol
Sent from my MZ604 using xda premium

I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?

scsa20 said:
I would say to send it to me and I can take a wack at it but I don't think you want to wait that long to simply root it.
Let me ask you, are you getting any sort of error messages when you do fastboot flash recovery recovery.img? If so, what's that error message?
Click to expand...
Click to collapse
Not getting any error message it just says "cannot load recovery.img"
I have tried with and without the .img and always the same?
Tried going through the whole process again on my laptop incase I had missed something but exactly the same.
When I unlock it I follow the onscreen instructions and at the end it says its complete before it reboots. Then I turn on usb debugging again and reboot bootloader all ok but won't let me load the new recovery?
Normally I would just say it wasn't meant to be and leave as it is but I wont be beaten on this so I'm purposely not installing anything on it till its done. Any ideas apart from bringing it round yours lol ;-)
Sent from my Desire HD using xda premium

The recently posted rooting method for the KFHD has been great for owners to get started on modifying the device to suit their own tastes. However, I've been a little concerned about everybody jumping in without a safety net in place. There are numerous ways that this device can get bricked. Not to put all of you into a panic, but just getting an eventual OTA update from Amazon might put some of these rooted KFHDs in jeopardy. With no custom recovery on the horizon, I think it's important to have some backup/restore plan to get these devices booting again.
Overview
This backup plan involves making raw data clones of all critical storage partitions required to boot the device. These backup archives can then be stored somewhere off the device. In case of some critical failure that prevents the device from booting normally, these archives can be used to get the device booting normally again. The restore procedure requires the use of fastboot to write the backup archives back to their proper partitions. The use of fastboot requires a working bootloader, so the device will need to boot to the bootloader's bootlogo at a minimum. If the device has a broken bootloader, this guide will not be helpful. There's currently no working procedure for repairing a broken bootloader on the 2nd generation Kindle Fire devices.
To be clear, this guide is not a backup/restore plan for your data. This is strictly for backing up the system software while in a bootable state and recovering it if some modification bricks the device. This procedure has been tested on a KFHD with system software version 7.1.1. Although I have not tested it, I'm nearly certain it will work just fine on version 7.1.5. If the KF2 has the same partition layout as the KFHD, there's no reason why it shouldn't work for that device as well. Check the post on KFHD partitions for details.
Warning: Everything below is inherently dangerous and can potentially brick your device if they are not executed properly. I have tested various aspects to the best of my ability, but you assume all responsibility for performing any of these steps.
Backup
Attached is a small shell script written to do the following…
Make a "kindlebackups" directory in /sdcard (if necessary) and make it user read/writeable.
Create gzipped backup archives of partitions 1 through 11. This includes all partitions except /cache and /data.
Make all archive files user read/writeable.
The entire backup (stock) takes up approximately 550 MB, so be sure to have at least that much available in /sdcard. Root privileges are required for the script to run properly. The best time to use this script is after step two of the published rooting procedure. That's after the second reboot of the process when the device boots up in emulation mode and allows root access for the first time. At this point, the system partition is completely stock and has not been exposed to any modifications. Even if you are past this point, the backups will still be useful for any bootable state that allows root privileges.
Download the script, unzip and place it into your current working directory where you still have access to adb, then run the following adb commands to copy the script to the Kindle Fire and prepare it to be executed...
Code:
adb push backup.sh /data/local/backup.sh
adb shell chmod 777 /data/local/backup.sh
If the device is in the process of being rooted and it has just finished rebooting for the second time...
Code:
adb shell /data/local/backup.sh
If the device has already been rooted and the su binary is available on the system...
Code:
adb shell su -c "/data/local/backup.sh"
The entire process should take approximately 5 minutes. Once the script has completed the backup, access the Kindle Fire's storage area from your computer, then copy the contents of the "kindlebackups" folder to it. The "kindlebackups" folder may be deleted after transferring to your computer.
Restore
To begin the restore procedure, the device must be put into fastboot mode. My factory cable did the job for me, so I have not explored the possibility of changing bootmodes. I developed this guide on a borrowed KFHD and I do not intend to risk the device more than necessary. Unless someone comes forward with a procedure to change bootmodes into and out of fastboot mode, I'm going to say that a factory cable is required for the time being. Besides, based on my experience with the original Kindle Fire, a broken system almost always means there is no way to change the bootmode through it. Since this procedure will very likely be used on a device that cannot boot completely or otherwise has a bad system, a factory cable will probably be the only way into fastboot mode. If you plan to root or modify your system software, invest in a factory cable.
Use the factory cable (with the device turned off, plug into the device, then the computer) to get to fastboot mode. If successful, a "fastboot" logo will take the place of the original "kindle fire" logo.
Decompress the gzipped archive to be flashed… Linux users have gunzip, Mac OS X users also have gunzip and a built-in GUI utility, and Windows users can use 7-zip. The archive must be decompressed before flashing. Skipping this step will brick your device.
Flash the image file(s) back to the device. In most cases, the device will just have to get a working system partition flashed back to it, but the others are available if they are needed. To flash the system partition...
Code:
fastboot -i 0x1949 flash system system.img
- Optionally erase the cache and/or userdata partitions if the contents of either interfere with the operation of the system software. The system will rebuild them on reboot…
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
Once the process is complete, long-press the power button (~20 seconds) until it powers down, unplug the factory cable, and power the device back up.
Good luck.

Thanks kinfauns. I appreciate everything you did for the original kindle fire. This should help a lot of people.
Sent from my Kindle Fire

My kindles /system directory is already screwed. Do you have a system.img file I can use?
Sent from my Galaxy Nexus using xda app-developers app

When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.

Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.

Copying kindlebackup folder
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)

Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.

vuhai6 said:
When i boot my kindle fire hd to fastboot (by factory cable) and connect it to pc, pc can't recognize kindle, it don't have driver for it.
Click to expand...
Click to collapse
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
ceebu said:
Thanks for the script - the backup procedure was smooth -
I couldnt find the kindlebackups folder while browsing through my PC and for others like me who wonder how to take these out of your KFHD, here is a simple way - I used a program called Wondershare MObilego (Manage SDcard option under more tools) Backing up was a cakewalk.
I have no affiliation to this tool maker - Just sharing a way that helped a n00b like me. (First rooting experience)
Click to expand...
Click to collapse
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
dreamcryer said:
Thanks for the efforts!
BTW, will a backup from a clean device work for other devices instead of the same one which the backup was created from? Just wondering if people who have already fiddled around their root devices can get a fresh start.
Click to expand...
Click to collapse
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.

Not recognized
My kindle is also not recognized when plugged in

kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)

vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
I know that the vendor id is correct.
Sent from my Kindle Fire

kinfauns said:
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
Click to expand...
Click to collapse
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app

cesdev89 said:
My kindle is also not recognized when plugged in
Click to expand...
Click to collapse
Then you're first going to have problems getting root privileges. You need to get adb working before you attempt any part of rooting or backing up with this procedure.
vuhai6 said:
But pc don't recognize as Kindle, it as Tate-PVT-08 (sorry, i use mac cho screenshot, but windows too)
Click to expand...
Click to collapse
This is the correct "product" reported by the KFHD. This and the product ID (0007) are the only differences between the KFHD and the original when it comes to installing the device drivers on Windows.
ceebu said:
I was only able to see the contents of /sdcard using windows...
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
/data/media and /sdcard are essentially the same thing (see the second post in this thread for an explanation of why this is the case). You should have seen kindlebackups in that directory.

kinfauns said:
You should have seen kindlebackups in that directory.
Click to expand...
Click to collapse
For some reason I didn't see it there, on hindsight I guess I panicked a bit (n00b) and fell back to the solution I already had.. (been using mobilego to manage my sgs2)..
Sent from my GT-I9100 using xda premium

kinfauns said:
I don't know if anybody has packaged the device drivers set up for this device. If nothing else, you can get the device driver installer in the "Kindle Fire Utility" for the original KF and use that. You just have to change the PID from 0006 to 0007 before installing it and should work. Refer to this post if you still have problems...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
for device driver information. Again, written for the original KF, but the process for installing device drivers is the same. Only the PID is slightly different and that should get edited in the INF before installation.
Glad to hear it worked out for you. I am not familiar with that program, but the KFHD should connect automatically to a Windows device as external storage... does it not?
I have not tested this and don't have a way to do so. I have some concerns about it, but I'm sure someone desperate enough will jump in and try it out. I know it's too late for some, but my suggestion is for everybody to make a backup if you can and not rely on someone else to give you archives after the fact. It's better to have your own backups.
Click to expand...
Click to collapse
I'm ready to try

Didn't show at first
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?

Yuretz said:
Could anybody post his clean backup here? Screwed my kindle, want go back to stock. Backup is only way.
Click to expand...
Click to collapse
I got the same situation, could anyone kindly help to provide a backup?

Same here ... just need the system image ... Please

I'd appreciate it if everybody would refrain from making this a "beg for a system image" thread.
strat6 said:
Kindlebackups showed up in root browser right away, but didn't show on PC until I rebooted KF2. So now should
I decompress and put in folder containing ADB?
Click to expand...
Click to collapse
You can put the the images wherever you want, but you'll need to specify the path to the file. For example, if you are using Windows and put the kindlebackups directory on C:, you just need to modify the command to...
Code:
fastboot -i 0x1949 flash system C:\kindlebackups\system.img

Thank you for posting how to do this. It opens a lot of doors with at least a little security.
I made a backup earlier without a problem, then went ahead and made myself a factory cable(easy to do and worked great- old asus usb cable, 1k resistor, soldering iron, shrink tape and voila!). I feel much better about doing any mods to this device now knowing I can just flash my backup.

Ok since there is a new house of moto and some of the instructions have changed I am deleting the old instructions go here http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ and follow Samuri's instructions if you get stuck I will still attempt to help you out I am not going to re write all the instructions again. Trying to piece it together will cause more confusion then help. Please read then re-read his instructions they are all you need after all he created the house of moto. If you cant figure it out pm me or post here and I will try to help the best I can. Here are his instructions for quick reference but you have to got to the above link to download everything.
ALL CREDIT GOES TO SAMURI HL FOR CREATING THIS AWESOME TOOL.
Please do yourself a favor and read, read again, and read one more time before installing and using this tool. If it's set up correctly, it's very easy to use. But if you don't follow directions, it'll either not work or not do what you expect. Failure to read and follow the directions is NOT a defect of the tool!
Mission statement for tool:
This will allow users to have a user friendly framework automation tool for new Motorola devices. Easily customized for any device that allows RSD or fastboot flashing of custom scripts that perform various functions. Most notably is when a user screws something up and the phone no longer boots (so called soft bricking). The KEEP DATA and/or FULL scripts can restore the partitions of the phone to minty factory fresh in the event that your phone doesn't boot.
WARNING: Upgrades from 1.4 are NOT supported. Install CLEAN. You have been warned.
SETUP:
Required Steps
o) You MUST have the latest Motorola USB driver installed: http://lmgtfy.com/?q...rola USB driver
o) Download: HouseOfMoto_2.0.zip
o) Extract the HouseOfMoto folder in the zip to your hard drive. IMPORTANT: Make sure no spaces are in the path. (Windows users should extract it to C:\)
o) Download the support file for your device and extract into your HouseOfMoto directory. (see device support below)
o) Download your FXZ from here: http://sbf.droid-developers.org/ [Site is back, BUT, very limited. It'll take time to repopulate it]
o) Add the FXZ files to your HouseOfMoto\FXZ_xtYYY directory. (see Adding the FXZ below)
Optional Steps
o) If root exists for your device, add the files to the root folder. Make sure run.bat and/or run.sh exists.
CLARIFICATION: When I say "if root exists for your phone" I'm referring to a root exploit that has a run.bat script in order to install root. If that doesn't exist for your phone, or your root exploit does not have a run.bat, this does not apply to you. This is ONLY for adding an option to root your phone to the House of Moto menu as a convenience option. It is NOT a required step.
Linux/Mac Notes:
o) You may need to chmod +x HouseOfMoto.sh
o) You may need to run HouseOfMoto.sh as sudo
Usage:
o) Your phone MUST be in AP Fastboot mode. Try holding volume down and pressing the power button when the phone is off.
o) Run the HouseOfMoto.bat or HouseOfMoto.sh in your HouseOfMoto directory
o) On first run:
Enter your device model (xt926, xt875, etc)
For Windows: Select flash mode: rsd or fastboot
o) Flash mode on Windows can be changed from the main menu
o) Phone model can be changed from the main menu
o) Select the script you wish to flash
o) Follow directions!
Adding the FXZ:
This part confuses a LOT of people so I'm going to use the FXZ for the xt926 as an example of how this should work. Obviously you'll need to use the proper FXZ for your device, but, the concept is generally the same.
This is a point that many get wrong so please follow this carefully...
When you open your VRZ_XT926_9.8.1Q-79-1_CFC.xml.zip file, you will see a directory inside it. You must go INTO the directory inside the zip. There you will see a whole bunch of files. Select them all, and extract them into the FXZ_xt926 folder. All the files must be at the root of the FXZ_xt926 folder, NOT in a sub folder within it. If you have this:
HouseOfMoto\FXZ_xt926\VRZ_XT926_9.8.1Q-79-1_CFC.xml\boot.img
It's wrong. If instead you have this:
HouseOfMoto\FXZ_xt926\boot.img
It's correct.
DEVICE SUPPORT:
o) xt875
o) xt907
o) xt912
o) xt926
o) xt1030
o) xt1080
NOTES:
o) xtYYY is the device model...i.e. xt1058, xt895, etc
DA FAQ:
Q: What flash mode should I pick?
A: Whether you use RSD or fastboot is a personal choice and completely up to you. If you have problems flashing in one mode, you can switch to the other and try again to see if you get better results.
SUPPORT:
If I tell you to create a log and post it, you are to run the CreateLOG.bat file to your c:\HouseOfMoto directory and post the results in this thread.

OP Plz update on Houseofmoto v1.4 when creating the FXZ version only the phone model, (i.e. FXZ_xt1080) Is needed. Also the Thread name needs to be [GUIDE] Return to stock and stickty IMO

You are a Godsend. The House of Moto website was pretty confusing.

Just want to make sure I'm understanding this right. I rooted my Maxx with PwnMyMoto. I also made some modification to allow for wifi tethering. I'm pretty sure I want to return to 100% stock, so that I can receive OTA updates. I can use House of Moto to accomplish this, and my Maxx will be like it was, fresh outta the box?

Ansky11 said:
Just want to make sure I'm understanding this right. I rooted my Maxx with PwnMyMoto. I also made some modification to allow for wifi tethering. I'm pretty sure I want to return to 100% stock, so that I can receive OTA updates. I can use House of Moto to accomplish this, and my Maxx will be like it was, fresh outta the box?
Click to expand...
Click to collapse
Yes what is better is you can choose the save data fxz and it will return you to stock but leave all your apps and data alone.

Which flash mode do we use? Fastboot [snapdragon]?

bigv5150 said:
** Moderators if this is in the wrong forum please move it also be advised I have contacted Samuri and he is fine with me posting this information.
ALL CREDIT GOES TO SamuriHL
Ok guys we have root this is great but I keep seeing guys having problems with installing it jcase has been great in evolving the root apk to accommodate us. I just thought I would try to lend some assistance because I know he is busy and a lot of us aren't as computer savvy as these guys. If you didn't have a bionic then you may not know who Samuri is but he made a tool for bionic owners it was great and very useful. He has since moved on from the bionic but after I contacted him about a tool for the Maxx he as usual came through. He created a Moto tool for several of the new devices and old. It is located here---> http://www.droidrzr.com/index.php/topic/28162-house-of-moto/ This tool will let you fxz full or fxz save data. If you don't know the difference fxz full will wipe the phone to out of the box fresh. Save data will install just the system but not touch your user data ie apps, wallpaper etc. Now to the good news any one that is having an issue still with root download use the above tool and use the fxz save data option it will wipe out root and you can start fresh. It will give you back your stock recovery as well. I had no problem with root but I tested this to make sure it would work. I just re-rooted the whole process took less than 15 minutes.
Below I will give instructions for the laymen if you find the instructions a little confusing in the House of Moto. If you get stuck PM me and I will try to help I am no genius when it comes to this but I have made most of the mistakes and learned from them. If I can't figure it out then you will have to contact the creator Samuri. But be forewarned he has little patience for stupidity. This is the reason I am taking the time to do this to assist him with the less knowledgeable. Remember he no longer owns a moto phone he did this out of the goodness of his heart.
Set up and installation:
1) install the House of Moto 1.2
2) Run it and let it extract to c:\HouseOfMoto it does this automatically
3) Create an FXZ_xxx_xtYYY directory where xxx is the FXZ version (MR4, 98.72.22, etc) and xtYYY is your device (xt926, xt875, etc) it should look like this FXZ_12.7.7_xt1080. You can go here---> http://sbf.droid-developers.org/ and download the FXZ for your device
4) Add the FXZ files to your new FXZ_xxx_xtYYY directory
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
6) the next step talks about root but we don't need that since we have an apk to re-root so I disregarded this step.
Using the House Of Moto:
1) Run the HouseOfMoto.bat in your c:\HouseOfMoto directory be advised if you make a desktop short cut of the run bat. file it will throw an error stating you need to install rsd which is already installed in the tool. You have to run the House of moto bat. file from within the house of moto folder.
2) On first run: Enter your device model (xt926, xt875, etc) Select flash mode: rsd, fastboot [snapdragon], or fastboot [omap]
3) flash mode can be changed from the main menu
4) device model can be changed from the main menu
5) Select the script you wish to execute ie. Full FXZ Save Data FXZ
6) Follow directions!
There are further instructions in the above thread for creating the FXZ file. I will say this simply when you create the FXZ file it should not have a file folder inside it. Meaning the FXZ file you placed in the House of Moto will say if you have a maxx FXZ_12.7.7_xt1080. When you open this file it shoud contain the whole FXZ not another file you have to open. So extract the FXZ then cut and paste it in the FXZ folder if you don't you will get an error.
This is what your house of moto should look like when you open it:
fastboot_scripts---> will contain Full_xt1080(or whatever phone you use) and Keep-data_xt1080 (or whatever phone you use)
FXZ_12.7.7_xt1080--->again when you open this file you should see the FXZ files not a folder that you have to access.
root
rsd
rsd_scripts---> will contain Full_xt1080(or whatever phone you use) and Keep-data_xt1080 (or whatever phone you use)
utils
flashmode
House of Moto
phone--->you will not see this until you type in what phone you want to use in step 2 above under using the house of moto
Just to sum things up the above tool will put everything where it needs to be except the FXZ that you have to do yourself. Good luck this is truly a useful tool.
One more thing I sent Samuri the xml files for the moto x (verizon and at&t models) also the mini and ultra he said the xml files are so close it was ridiculous. This is a quote from Samuri for being able to use this tool with an ultra mini or moto x
An anonymous donor sent me the xt1030, xt1058, and xt1060 FXZ xml's. They all use the same files as the xt1080 in their respective FXZ's. It's just a matter of me renaming the xt1080 scripts a bunch of times for the different models and packaging them up. Or if people need it before I get them posted, take the xt1080 package and rename the 4 scripts to xt10xx depending on your model and it'll work just fine. Moto's making my life a lot easier that's for sure! In fact I'll write a batch file so that if I ever have to change them for any reason it'll just create them all. LOL.
Click to expand...
Click to collapse
Dammit. I knew I'd be the one idiot.
Followed to the letter and when I run the .BAT, I get :
"Warning: Please check input file. Either XML format is wrong or image files associated with it are missing."
Any ideas that an idiot may be able to follow along with?
FIGURED IT OUT:
Didn't save to C drive. saved it to desktop.

Trying to do this but it seems to fail to install recovery even though it says successful. Tried to download fxz file a couple times and it always gives errors on unpacking, which may be issue.
It was successful at destroying my sim card though.... I have no service now.

One thing to keep in mind that stumped me for a few was the model number. When you go to download the FXZ file the droid maxx is xt1080m. You don't use that as your model number you type into house of moto. Just use xt1080.

Difficulties with howto...
Sorry guys,
I'm having a hell of a time but I have a problem related to this. At current my phone took the OTA while I was rooted and its now boot-looped. I'm trying to revert to the stock firmware, and someone suggested this option. I'm having problems with the step here:
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.​
This step is odd, what scripts are you supposed to add to the RSD/Fastboot scripts? Where do I get the scripts? From the FXZ passage?

Qb411 said:
Sorry guys,
I'm having a hell of a time but I have a problem related to this. At current my phone took the OTA while I was rooted and its now boot-looped. I'm trying to revert to the stock firmware, and someone suggested this option. I'm having problems with the step here:
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.​
This step is odd, what scripts are you supposed to add to the RSD/Fastboot scripts? Where do I get the scripts? From the FXZ passage?
Click to expand...
Click to collapse
the scripts are near the bottom of the post where you download houseofmoto, scroll down til you see Support in bold. theres a link for xt1080 scripts, just download them and place them in the correct folder.

hmmmm
beelow319 said:
the scripts are near the bottom of the post where you download houseofmoto, scroll down til you see Support in bold. theres a link for xt1080 scripts, just download them and place them in the correct folder.
Click to expand...
Click to collapse
I had trouble with this when I chose fastboot omap and did the "keep data" option. It went through said it flashed stuffs, but I still had root. I changed it to fastboot snapdragon and did it again and then it worked. I have a Droid Maxx and used Pwnmymoto a month ago, which flashed my recovery, thus the need to fixor that.
---------- Post added at 07:07 PM ---------- Previous post was at 06:46 PM ----------
the3dolla said:
I had trouble with this when I chose fastboot omap and did the "keep data" option. It went through said it flashed stuffs, but I still had root. I changed it to fastboot snapdragon and did it again and then it worked. I have a Droid Maxx and used Pwnmymoto a month ago, which flashed my recovery, thus the need to fixor that.
Click to expand...
Click to collapse
Also, just FYI, update went fine and hotspot still works, guess I won't worry about adaway working until an easy root method is found, so I can unroot easier for kitkat.

Just chiming in to say if you all need anything let me know. I've helped a lot of people today get their MAXX back to stock so they can take the ota. Seems to be working once people get it setup properly.
Sent from my Xoom using Tapatalk 4

Post for easy access later.
Sent from my DROID MAXX via Tapatalk 4.

BMWPower06 said:
Which flash mode do we use? Fastboot [snapdragon]?
Click to expand...
Click to collapse
I have the same question.

Kinda stuck. Tried using the flash with data for my XT1080 and the screen says waiting on device. I know i did something wrong but not sure what. Any help would be appreciated.
Device is plugged in via USB. I think I have everything in the right folders. Can I just close the command prompt window without hurting the phone?

Ok I updated the instructions I wrote these instructions with the first house of moto and the naming of the fxz changed. Your FXZ file in house of moto should look like this FXZ_xt1080 or what ever phone you are using not FXZ_12.7.7_xt1080. Sorry for the confusion if you were having a problem with house of moto finding the FXZ this is why.
If this was an issue for anyone I am sorry to be honest I stopped checking this thread a while ago. I created this thread on Sept. 19 and kept trying to tell people to download the tool even if they did not need it, better to safe then sorry. I kept checking but no posts or ?'s so after a month or so seeing no one posting here I figured no one cared or wanted this tool and I forgot about it until I received a pm a few days ago. If you have a question I will try to help but please give me as much info as possible.

bigv5150 said:
Ok I updated the instructions I wrote these instructions with the first house of moto and the naming of the fxz changed. Your FXZ file in house of moto should look like this FXZ_xt1080 or what ever phone you are using not FXZ_12.7.7_xt1080. Sorry for the confusion if you were having a problem with house of moto finding the FXZ this is why.
Click to expand...
Click to collapse
That got me passed my issue. Phone rebooted and now its updating. We'll see what happens from here. Thanks for the update.

In regards to what flash mode to use its rsd for the fxz keep data or full fxz. If you want to run fast boot commands then you would chose fastboot snapdragon.

daca1001 said:
That got me passed my issue. Phone rebooted and now its updating. We'll see what happens from here. Thanks for the update.
Click to expand...
Click to collapse
You should be good now this tool is awesome you will use it again and again trust me. You will do something stupid to your phone and have a DOH!!! moment and this will fix it.

Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT

This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.

How is this any easier than the original method....if anything this requires even more work

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.

psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP

Can this be used to inject Xposed as well for those of us with locked BLs.

djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.

psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!

Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:

the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.

The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem

hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx

How to calculator extractly bs/seek/count ?

Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013

optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.

ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.

hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?

BLU R1-HD bootloader unlock script tool, and TWRP install tool.
Download is a zip file, unpack it to somewhere you will remember. Run the dirty-cow-tool.bat // mtk-su-tool.bat
The included files and folders are set to hidden, in effort to keep them safe from accidental delete.
Must have adb+fastboot + drivers installed and setup prior to using tool
Easiest method to install adb + fastboot on windows is with "15 second adb + fastboot install TOOL"
LINK==>ADB+FASTBOOT
It is for windows
In linux :
"sudo apt-get install android-tools-adb"
"sudo apt-get install android-tools-fastboot" Some fastboot commands were missing when i used this one ie "fastboot flashing get_unlock_ability"
"sudo apt-get install fastboot" worked better when I tried. ( i used that command as a check before doing the unlock, so it was needed only for that check)
Using Tool
On Windows?
Unzip the downloaded file to a new folder, open new
folder and click on "dirty-cow-tool.bat". // "mtk-su-tool.bat"
Do the steps in order (1-2-3-4) to be unlocked, then
Step (5) to get to second page where step (1) is root
The rest is optional
On Linux?
Unzip downloaded file to new folder folder .
Open folder. Then open R1-Linux-tool-v2 folder
Open terminal from that folder and type
" . R1-HD-TOOL.sh "
Same order of steps (1,2,3,4) step (5) for extra
Steps (1 on second menu) for superSU root.
Second menu steps (2,3,4,5,6,7,8) are optional.
**Linux Note**
The tool uses "fastboot flashing get_unlock_ability" as one of the methods to check before doing the unlock.
The version of fastboot that installed with "apt-get install android-tools-fastboot" did not recognize
this command. But "apt-get install fastboot" updated some version and then the command was recognized.
******OTHER NOTES****
--- this has been mentioned in the general thread and the modified v17 thread, but It has come up again so I wanted to make note of it.----
--- The newest blu versions (V7.4.2 and V17) Have made changes to "toolbox" and this effects things like "adaway" and "titanium backup"
--- The suggested fix is to install busy-box. I have had success with the version from play store, some prefer to use f-droid version. Either one will do. Install it and open the app. From in the app you need to do an install.
CHANGE LOG
V1:. Initial release : removed
V2:. : fixed typos preventing proper function
V3:.: switch file verification to md5 check instead of "ls-l" comparison.
V4: current version: add extras page, add SU flash, de-bloat script, Added Fm Radio, Added pre-loader roll back
V5: Fixed wrong loop "goto" line that made preloader rollback do "MTK_BLU Debloat v2" instead
V6: Added manual pause to script for mods that need recovery (Extra's 5) . Added redundent recovery flash command .
Few reports of recovery "not Sticking" and needed to run the flash commands manually one by one. Maybe the redundent
flash will make it survive. If still having problem with recovery "staying install" try manually flashing
here is link to the steps needed. FLASH RECOVERY
V7 Improved logs Added line to make batch run as sub-process so if error occurs , will not close
V7.1 : Updated the fm radio install zip and include the needed selinux mode changer app
V8: fixed dependency of needing to be unzipped to location w/o spaces in name. (when used from location with spaces, tool used to fail to push needed files).
.. added more time to allow dirtycow to "spawn" its root shell. Recent testing has shown sometimes it takes longer than the 60 seconds allowed in the script. Now it is looped 3 times.
V9 Added full path to abd push lines for recovery flash files. included fastboot.exe file to address some version issue where user s version would not output text file I coded into script for a verification ( included file is called by script, no need to do anything different with it)
V10: Moved zip file to included folder to help preserve locations when unpacked, added device check before running tool; So tool not used on wrong device, Rearranged order of operations on extra's page. (recovery installed options) Push files while in android before rebooting to recovery( should improve reliability for multiple reports of not automatically installing options for some)
******I have received some reports that some devices are reporting "ro.build.product =R1_HD and not "BLU_R1_HD" like mine, so the added device check is blocking tool from starting If this happens to you , you can make edit to the .bat file like below.
Change this line
Code:
:next_check
find "BLU_R1_HD" "%~dp0workingproduct.txt"
To this
Code:
:next_check
find "R1_HD" "%~dp0workingproduct.txt"
it is line #23
V11: Updated device model verification lines
MTK-SU: Replaced all dirty-cow part with New MTK-SU binary(elf) from @diplomatic
source
Click to expand...
Click to collapse
Credits to @Diplomatic for his work on the Mtk_su that I used used to make this tool work again after Dirty-Cow was patched.
DOWNLOAD LINK
Preferred to use the Downloads tab of this thread.
Archived downloads on android file host also == link
XDA:DevDB Information
R1-HD Dirty-cow Unlock Tool, Tool/Utility for the BLU R1 HD
Contributors
mrmazak, vampirefo for his recovery, lopestom for his recovery, emc2cube for his debloat zips, christianrodher for his dirtycow method,
Source Code: https://github.com/mrmazakblu/DirtyCow-R1_HD
Version Information
Status: Testing
Current Stable Version: V11
Stable Release Date: 2017-04-11
Current Beta Version: MTK-SU
Beta Release Date: 2019-04-14
Created 2017-02-22
Last Updated 2019-04-18

Reserved
Items planed to be addressed in next release:
--Add few more file integrity checks to the extra's page
--Add copy log to clipboard option so it is easier to post log entry if needed-------*********----already-_added to github copy of batch file
--Add a verification step that checks what recovery is installed( to prevent trying to do steps on extra's page with stock recovery)
--Possibly move to a "fastboot boot recovery" instead of "adb reboot recovery" for the same reason as above
--Add wget or similar to the extra's items so initial "TOOL" size is smaller (not that 40-50MB is big, but to some it may be )
--Add additional "selinux mode changer apk" for fm radio install rather than just the note that says it needs to be found.

Reserved

Works great on OEM 6.6, thanks for the tool!

So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function

theredbaron1834 said:
So I got the one-click-root.sh done, maybe. Can some linux users go over it, make sure I didn't do anything stupid? I don't exactly have a device to check it with atm, and I am not pro with scripting, barely novice, so it is a pretty basic conversion of the batch file. Still, it might work . Just would like a few eyes on first.
https://github.com/theredbaron1834/Scripts/blob/master/one-click-root.sh
Also, I looked at dirty-cow-tool.bat. However, wow, more an advanced batch file, and I am not sure what the first half does, so not sure how to convert . However, it seems if anyone does get it, the eqiv of goto for linux is funtions. simple cheatsheet:
Code:
function stuff {
echo "this stuff is run via the function"
{
stuff #goes to stuff and runs function
Click to expand...
Click to collapse
thank you for your input.
As far as the begining of the batch, It is adding a few folders to the "path" variable so help ensure the "adb push" commands find the files it is trying to push. Then it sets some folder "flags" to hidden so that the files the batch needs don't get accidentally moved or changed. Then the large section with mostly "echo" that is to set up the "simulated" G.U.I.
The lines of just "::::::::::" are simply used to help with reading the batch file. i use them to seperate functions. They are not needed.
The lines with only 2 "::" are standard windows comment / remark line entries
The lines with 1 ":" are the beginning line of the loop/ function == the line that "goto *" searches for

Does Works to unlock 7.4.2?

khyr said:
Does Works to unlock 7.4.2?
Click to expand...
Click to collapse
It is supposed to. It is the same base codes used from original script, and that one was confirmed to work. I Do not have first hand use of V7.4.2 so it is only confirmed through other users.
The dirty-cow being used has been patched by google in Dec but blu has not rolled out the patch. So there is no reason for it not to work.

edit:
I have the linux version ready.
-the first step, (ADB Push) is ready. including md5 file checks
-step 2 is ready= running dirty-cow with md5 check before final writing to mmcblk device
-step 3 is ready unlocking bootloader = including check if unlock is done, but need to fix the "unlock_adility" check
I can make to file to compare and grep the line needed, but cannot "sed" the extra information or do a > < comparison
-step 4 is ready .--flash twrp
Finished 90% of tool.
still need to tweek the log feature.
I ran tests on the lop back to menu and test ran
1. push files for dirty-cow and md5 check . then made push fail to verify the check method was valid ==pass
2. run dirty cow commands and md5 verification on resulting file. ==pass
3.unlock bootloader --- I ran it (needed to fake the already unlocked check) it works == pass
4 . flash twrp --installed both version i have, both install fine ===pass
5 extra menus -- ran . install su-----debloat---rebloat--- add fm radio--- preloader roll back =====all pass
(bootloader roll back needs manual intervention to re-enter fastboot during the boot loop that is unavoidable)
6. instruction ====not written yet
7. exit yes it closes == pass
8. logs --- needs completeing

I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system

mrmazak said:
no it does not.
the /sdcard is the internal memory and the Download folder is already there.
you might be having issues but the folder is already part of normal system
Click to expand...
Click to collapse
Fair enough, my restore didn't have /sdcard/Download and I made an assumption that /sdcard was my mounted card. Thanks for the insight.

OOPS
found typo on V4 of tool. batch files sets variables for "return", from loop functions. And two returns were set to same label9, so if you had tried to do extra's menu option #8. "ROLL Back Preloader" , instead it was running option # 5. " MTK_BLU Debloat v2"
fixed and still reading and re-reading to search for errors.
This looks bad.
The reason I put together this tool was I felt it was important to make a way to minimize the problems usually associated with android modifications. By making "typo's" a thing of the past, and I found them in my own script.
re-posted V5 combined with linux V2--

torchredfrc said:
I just loaded this on my OTA updated 7.4.2 device. I would note that the batch file does not actually create the /sdcard/Download folder so you might need to go into the terminal and actually create this on your sdcard... also worth noting that this batch file **requires** an sd card in the device to do any of the loads in the "5" menu.
Click to expand...
Click to collapse
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you

gabriel986 said:
I'm a total noob, and I'd like to know how to proceed with the supersu and all the other parts of step 5. Thank you
Click to expand...
Click to collapse
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.

mrmazak said:
Ok. After you have completed upto twrp install. You can do the options on #5. It is all programed and automatic. What is does is put zip files onto the phone and reboots phone into recovery, then recovery installs them.
Click to expand...
Click to collapse
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
In case it's needed, my R1 HD is running on
BLU_R0010UU_V7.4.2_GENERIC 09-11-2016 13:38

gabriel986 said:
I get up to the recovery installation, but then I can not access such recovery on the phone, If I turn it on with power+vol up, it takes me to the default factory recovery by blu.
And If I try to the super su step with the phone on, it resets it, and get it to the screen with the dead android, while the script just shows the ADB DETECTED message.
Click to expand...
Click to collapse
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.

mrmazak said:
You missed a step in the process.
As tool finishes the recovery install it comes to a "pause" in the script, you need to hold the volume up button on phone "before" pressing button on pc keyboard to continue.
If phone does a normal reboot at this point then the system will replace the newly installed recovery with the stock one.
Giving you the situation you have now.
This step I cannot control, you must press volume button on phone to get the boot menu, and directly boot into recovery to ensure that the install sticks.
Click to expand...
Click to collapse
trying again....
for how long should I press the volume up key?

gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on

mrmazak said:
When tool says Hold button , keep it held. Then continue the script. Phone should reboot to the boot menu. Then let go of volume
Some phones do not accept the fastboot reboot command, on those phones need to hold power to shut off. Then volume and power together to come on, release power when screen come on
Click to expand...
Click to collapse
ok.. trying again
---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------
gabriel986 said:
trying again....
for how long should I press the volume up key?
Click to expand...
Click to collapse
it beat me!
I get stuck in that part of the process, If anyone uploads a video to check what i'm doing wrong, I'll be grateful.