Related
(removed --> see post #2)
WARNING: This tutorial is for RogersDream users only! It does not apply to G1/dream users. If your wireless telephone carrier is not Rogers, this tutorial is not for you!
This how-to/tutorial's intent is to provide clear/safe/concise steps for Rogers users to keep root, update to the latest RogersRadio & Build and get your data connection back from Rogers, while keeping your root! Since I do not want to dis-rotate on the various potential setups you may or may not have currently installed, this is a start-to-finish guide. Meaning, this guide will work, so long as you are ALREADY ROOTED! If you're not already rooted, <this apparently is not solved yet, sorry>).
The only other note I'll make is that if you currently already have the latest RogersRadio installed (3.22.26.17), the ENG-1.33.2005-SPL and a testkeys recovery image (Amon_RA's 1.5.2R preferred) you may directly proceed to installing a rooted/custom ROM made specifically for EBI1 device layouts.
In order to determine what your RogersDream currently has installed on it, perform the following.
1) Determine Radio & SPL Version.
- PowerOff your phone.
- Press and Hold your Camera button and tap the power button, this will load the bootloader.
- Read the versions, if you see "RADIO-3.22.26.17" and "HBOOT-1.33.2005", then you have the proper radio/spl, if not, perform the steps in this guide.
2) Determine Recovery Image Version.
- PowerOff your phone.
- Press and Hold the Home button and tap the power button, this will load the recovery image.
- If you see "Build: RA-dream-v1.5.2R" at the bottom of your screen, you have the correct recovery image. If you see a Triangle with an "!" mark or you see nothing at all after the Rogers SPLASH SCREEN, perform the steps in this guide.
General Step Sections
1) Backup your phone and sdcard, just to be safe!
2) Charge your battery fully!
3) Gather/Download the prerequisite files/tools, check the MD5's, unpack and copy to your sdcard.
4) Downgrade your RogersDream to gain root and ensure proper EBI1 setup/layout.
5) Install flashrec to install Amon_RA's 1.5.2R recovery image.
6) Upgrade/Convert your SPL to 1.33.2005 ENG, to ensure root going forward.
7) Install Rogers latest Radio Update, version 3.22.26.17.
8) Confirm everything updated correctly.
9) Install Custom/Rooted ROM w/EBI1 kernel support.
THE GUIDE
Section 1) Backup your phone and sdcard, just to be safe!
a) Seriously do this! Backup whatever you deem necessary on the phone, however you see fit. This guide is not meant to walk you through this process. One suggestion though, if you're currently rooted, perform a nandroid backup in recovery, then backup all of your sdcard's contents to a computer. If you need help with this step, search around. If that doesn't help, then perhaps rooting (or this guide) is not for you, perhaps.
Section 2) Charge your battery fully!
a) Seriously do this! Just make sure you have well over 90% battery charge, just to be 100% safe. Also make sure you're battery is very secure during this process, meaning never pull the battery and if you know that your battery is prone to falling out or something like that, fix it somehow b/c you don't want it falling out during this process, k? Nuf Said.
Section 3) Gather/Download the prerequisite files/tools, check the MD5's, unpack and copy to your sdcard.
a) You're going to need adb setup and functioning for section #5, in order to install flashrec w/out a data connection. You *may* be able to get installed via wifi, by downloading it directly from the internet, but don't count on this!!! I will only cover the adb method in this how-to. So get adb installed on your computer and test/make-sure it functions before following this guide! If you don't get adb tested/installed before going through with this guide, you'll be stuck at section-#5 until you do! If you need help with this step, search around. There is plenty of information on xda for getting adb setup and tested.
b) Download this ZIP file, check it's MD5 checksum and make sure it matches the one in this post! If it matches, great!, unpack the contents and copy them to your phone's sdcard. If it doesn't match, redownload the ZIP file. You will need approxiately 114MB of freespace on your phone's sdcard for the unpacked contents.
Rogers_RootUpdate_SDCARD_files.zip
MD5: 013ed64ca02dbebb5e49a8a8474bebe1
I) Files in the zip that need to be copied to your phone's sdcard are ...
--- DREAIMG.nbh
--- ar152r-rec.img
--- rogers_radio_3.22.26.17_update.zip
--- rogers_spl_1.33.2005_update.zip
c) Download this flashrec.apk, check it's MD5 checksum and make sure it matches! Keep this handy on your computer to install with adb later.
flashrec.apk
MD5: 4634f88b8dfdb2332b447c0d85ff4bb6
Secion 4) Downgrade your RogersDream to gain root and ensure proper EBI1 setup/layout.
a) PowerOff your phone.
b) Press and Hold the Camera button and tap the Power button, this will boot into the bootloader.
c) At this point the bootloader should automagically detect the presence of DREAIMG.nbh on the sdcard and prompt you to "update" your phone with the message, "Do you want to start update?". It should say "<ACTION> Yes" and "<POWER> No". Press the rollerball in (this is the action button) to begin the update.
d) The update process will begin (really a downgrade to version 146733-1.85.631.5) ... it will go through the update process, wait till this process is 100% finished! You will be prompted once it is finished, with a reboot prompt with a similar "<ACTION> YES" and "<POWER> NO" prompt. Go ahead and reboot by pressing the rollerball.
e) You are now downgraded and ready to root.
Section 5) Install flashrec to install Amon_RA's 1.5.2R recovery image.
a) Once your phone is booted up, skip through the setupwizard by hitting the series of skip and next buttons.
b) Go into Settings, Applications and check the box for "Unknown sources", press 'OK' at the prompt.
c) Then press the "Development" button and check the box for "USB debugging".
d) Plug your phone into your computer via the USB cable.
e) Install flashrec.apk via adb with the command "adb install flashrec.apk". You should receive a success message and be able to confirm that "Recovery Flasher" is installed by viewing the phone's apps now.
f) Launch the "Recovery Flasher" app.
g) If there is a URL in the textedit box, remove (backspace it) completely. And enter the following
Code:
/sdcard/ar152r-rec.img
This should change the "Download Recovery Image" button into the "Flash Recovery Image" button. If not, make sure you typed the above properly and have that file on your sdcard.
h) Now press the "Backup Recovery Image", which will backup the original image, once it's complete the "Flash Recovery Image" button will enable itself.
i) Press the "Flash Recovery Image" button, which will install Amon_RA's v1.5.2R recovery image. Let it finish, you now have a rooted recovery image installed. Proceed to section-#6.
Section 6) Upgrade/Convert your SPL to 1.33.2005 ENG, to ensure root going forward.
a) PowerOff your phone.
b) Press and Hold the Home button and tap the power button, this will load Amon_RA's recovery image.
c) Use the rollerball to scroll down the "[Alt+F] Flash zip from sdcard" option and press-in on the rollerball.
d) You should see an entry in the list labeled "SDCARD:rogers_spl_1.33.2005_upd", roll the rollerball over this to highlight it and press-in on the rollerball.
e) You will prompted to confirm your selection, ensure the prompt says "SDCARD:rogers_spl_1.33.2005_update.zip" and if so, press the Home button to confirm.
f) It will flash through quickly with a message indicating "Extracting hboot image ..." and then a message saying "Reboot via home+back or menu to complete installation".
g) The rollerball will already have the top option highlighted "[Home+Back] Reboot system now", press in the on the rollerball. You should quickly see "writing hboot image ..." on the bottom ... followed by a quick reboot showing an "HTC" logo ... followed by another reboot which returns to Amon_RA's recovery. Proceed to section-#7.
(SEE POST #3 for Next Steps)
Section 7) Install Rogers latest Radio Update, version 3.22.26.17.
a) Use the rollerball to scroll down the "[Alt+F] Flash zip from sdcard" option and press-in on the rollerball.
b) You should see an entry in the list labeled "SDCARD:rogers_radio_3.22.26.27_", roll the rollerball over this to highlight it and press-in on the rollerball.
c) You will prompted to confirm your selection, ensure the prompt says "SDCARD:rogers_radio_3.22.26.27_update.zip" and if so, press the Home button to confirm.
d) It will flash through quickly with a message indicating "Extracting radio image ..." and then a message saying "Reboot via home+back or menu to complete installation".
e) The rollerball will already have the top option highlighted "[Home+Back] Reboot system now", press in the on the rollerball. You should see "writing radio image ..." on the bottom ... followed by a reboot showing an "HTC" logo for a few moments ... followed by another reboot which returns to Amon_RA's recovery. Proceed to section-#8.
Section 8) Confirm everything updated correctly.
a) At this point you should be back in Amon_RA's recovery.
b) Make sure the rollerball is highlighting the top option "[Home+Back] Reboot system now", then Press and Hold the Camera button, then tap/press-in the rollerball.
c) This will reboot you into the bootloader, at which point the Radio and SPL versions will be presented. If all went well you should now have "HBOOT-1.33.2005 (DREA10000)" and "RADIO-3.22.26.17".
Section 9) Install Custom/Rooted ROM w/EBI1 kernel support.
a) You are now ready to flash a custom ROM w/EBI1 support. If you flash my "TheOfficial Rogers v2.0.1 EBI1", it is a mirror image of everything necessary to get your data turned back on from Rogers. I'm also aware that CyanogenMOD has an EBI1 support/patch for RogersDream users, and I "hear" it works too in terms of not shutting off your data plan.
TheOfficial Rogers v2.0.1-EBI1 can be found here ... http://forum.xda-developers.com/showthread.php?t=556933 .
Simply download the v2.0.1-EBI1 version of the ROM (at the bottom of POST#1), copy it to your sdcard, boot into recovery, perform a data wipe, flash the ROM and reboot. And you'll be all set.
CyanogenMOD for EBI1 ... reference his wiki here ... http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod ... not 100% sure how the full install goes, but skip to "updating cyanogenmod" section and probe his thread for ROM+gapps installation process, etc. ... or visit them on freenode #cyanogenmod, they're always very happy to help.
Reserved......
Doing it right now! I'll give you an update on how it went. Thank you soooo much!
Is this supposed to work even on Rogers Dream with 1.89.631.1 applied (911 fix)?
I receive the following screen output when trying to flash DREAIMG.nbh:
Main Version is older!
Update Fail!
Do you want to reboot device?
bt1980 said:
Is this supposed to work even on Rogers Dream with 1.89.631.1 applied (911 fix)?
I receive the following screen output when trying to flash DREAIMG.nbh:
Main Version is older!
Update Fail!
Do you want to reboot device?
Click to expand...
Click to collapse
Not sure ... I had thought that Haykuro was suggesting it would. Honestly I do not have a personal experience with that update so I can't say for sure. But the message you are receiving would imply that ... what SPL version do you have ?
~enom~
enomther said:
Not sure ... I had thought that Haykuro was suggesting it would. Honestly I do not have a personal experience with that update so I can't say for sure. But the message you are receiving would imply that ... what SPL version do you have ?
~enom~
Click to expand...
Click to collapse
from my HBOOT:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
June 2 2009,21:33:16
bt1980 said:
from my HBOOT:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
June 2 2009,21:33:16
Click to expand...
Click to collapse
Yea ... again not sure ... if you reference (like I did) Haykuro's thread ... here ...
http://forum.xda-developers.com/showthread.php?t=625073
It seemed to me that it was suggesting you could indeed downgrade with that image. The image is one and the same.
EDIT: OK apparently they never found a fix if you're already running the latest non-rooted rogers update. So apparently you need to be rooted already. Sorry 'bout that. I'll update the OP with this information.
~enom~
bt1980 said:
from my HBOOT:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
June 2 2009,21:33:16
Click to expand...
Click to collapse
I updated the OP with this information. Sorry ... the testing Rogers devices I had access to were already rooted. Didn't take enough care to read that entire thread.
Hopefully a solution will be found soon via GoldCard or the like.
~enom~
Upgrade
I just finished my upgrade and I will wait for me data to return. Fingers are crossed!!
Also, acore seems to crash quite often. Is this normal?
AndroidFann said:
I just finished my upgrade and I will wait for me data to return. Fingers are crossed!!
Also, acore seems to crash quite often. Is this normal?
Click to expand...
Click to collapse
Did you wipe before installing the new ROM ? That can cause the acore FC problem if you didn't.
If so ... wipe again in recovery and if you used Apps2SD ...make sure you ext partition is wiped too.
~enom~
Hey, I'm already rooted with CM 1.4's recovery and HBOOT 1.33.2005. Is Amon_Ra and the ENG version of HBOOT really needed or can the Radio just be updated?
Sorry if this has been addressed in other threads already.
Thanks,
Tom
Welll so far, it's working. Now I just have to wait for my data to be restored. Thank you!
anonymoustom said:
Hey, I'm already rooted with CM 1.4's recovery and HBOOT 1.33.2005. Is Amon_Ra and the ENG version of HBOOT really needed or can the Radio just be updated?
Sorry if this has been addressed in other threads already.
Thanks,
Tom
Click to expand...
Click to collapse
I'm really recommending ALL versions match. Really knowing which ROM your running says it all.
If you're running my TheOfficial Rogers EBI0 ... meaning the "original" ROM ... and not the new EBI1 ROM, then you must update.
But simply as the first post states, if you're running an older radio ... such as 2.22.19.26I ... you must follow all of the steps. It's a complete rebuild to get you to EBI1, to support the newer radio.
~enom~
darkspirit386 said:
Welll so far, it's working. Now I just have to wait for my data to be restored. Thank you!
Click to expand...
Click to collapse
Awesome! Not sure if you'll have to beg Rogers to cut back on your data now or not, but once it's on, you should be golden.
~enom~
I am currently running your rogers original. I will update. Quick question however, does Amon_Ra's support SwitchROM? I really love that script!
anonymoustom said:
I am currently running your rogers original. I will update. Quick question however, does Amon_Ra's support SwitchROM? I really love that script!
Click to expand...
Click to collapse
Yes it does, just goto console and type switchrom -s WhateverYouWannaCallIt to save and switchrom -r to restore.
anonymoustom said:
I am currently running your rogers original. I will update. Quick question however, does Amon_Ra's support SwitchROM? I really love that script!
Click to expand...
Click to collapse
Yea it does ... but again ... with moving to an EBI1 setup, your ROM choices will be much more limited now.
I'm only aware of my RogersEBI1 and the CyanogenMOD w/EBI1 kernel patch working. There may be others, I haven't bothered to dig around enough ... but the point is ... limited options, as virtually all of the ROM's in this section are EBI0 ROM's.
~enom~
Thanks shadow (I don't like your avatar)
I need the full exchange support that your ROMs offer. I have been very limited in my choices anyways. Good thing you make excellent ROM's!
This method has now been updated using the newly released 1.47.651.1 RUU. The portion of this post in light gray is kept for historical interest only.
This PC36IMG.zip contains a complete set of firmwares from the latest RUU (hboot, boot, recovery, system, userdata, microprocessor, radio, and WiMAX), except the HBOOT has been replaced with the one from the engineering build (to give you unlocked NAND) and the recovery has been replaced with Amon RA 1.7.0.1 (so you can flash updates signed with the test keys).
Note: This process will only work if you already have the engineering HBOOT. (If you have NAND unlocked, you already have it and can proceed confidently.) If you'd like to check the actual version, you can boot into HBOOT and look near the top of the screen: it should say HBOOT-0.76.2000, not 0.79.0000. If you have 0.79.0000, you will need to do Toast's Part 2 first before starting here.
Download this file, rename it PC36IMG.zip, and put it on the root of your SD card however you like.
PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1.zip (md5=1ae574c403e9a2694de97706391255c0)
Power off your phone.
Hold down the Volume Down and Power buttons until the white screen appears.
HBOOT will scan the PC36IMG.zip file. You'll see a blue progress bar on the right side of the screen.
When it's finished scanning, it will ask if you want to start the update. Press the Volume Up button to answer Yes.
Wait a while for it to flash all the images.
If you get a "Fail-PU" error on the recovery image, see below.
When it finishes and asks if you want to reboot the device, press the Volume Up button to answer Yes.
After the phone has rebooted, delete the PC36IMG.zip file from your SD card.
Download this file to your SD card:
su-2.1-e-unsecure-signed.zip (md5=a055c916168db7e61a75a37a13993cd6)
Power off your phone.
Hold down the Volume Down and Power buttons until the white screen appears.
If you forgot to delete PC36IMG.zip from your SD card, HBOOT will scan it again now. When it asks if you want to start the update, press Volume Down to answer No. When it asks if you want to reboot, press Volume Down again.
Now you should be at the HBOOT menu. Press Volume Down to move the selection to RECOVERY and press the Power button to select it.
In a moment, you'll be at a different looking menu.
Using the Volume and Power buttons as before, select "Flash zip from sdcard."
Select su-2.1-e-unsecure-signed.zip from the list and follow the prompts to flash it.
When that's finished and you're back at the menu, choose "Reboot system now."
You should now have root, unlocked NAND, working WiMAX, and great battery life.
You're finished! The remainder of this post is supplemental information for those who are interested.
Fail-PU error
It seems some EVOs just don't want to take the Amon RA recovery. If you're running into the infamous "Fail-PU" error, try deleting the recovery image from the PC36IMG.zip and flashing again. Do note, if you currently have the stock recovery loaded, doing this will mean that you will be unable to install the su-2.1-e-unsecure-signed.zip package to get root/superuser, as described above, until after you've flashed a custom recovery, which you can't do from within the system using flash_image unless you have root. The only way in that case is to use fastboot. If you're coming right from Toast's Part 2, then none of this should be a problem, since you'll already have a custom recovery, albeit an old and crusty one.
After you've done this procedure, this is how you make changes to /system:
whitslack said:
To make changes to /system, you have to remount it read/write.
After switching to a root shell (# prompt), type mount and press Enter.
Look for a line that includes the word /system. On that line, look at the part that says /dev/block/mtdblockN, where N is a digit. That is the partition that your system lives on.
Type "mount -o remount,rw -t yaffs2 /dev/block/mtdblockN /system", substituting the digit you saw in the previous step for N.
Now your system is mounted read/write and you can make changes. Proceed cautiously.
Click to expand...
Click to collapse
Here's how you can tell if you're royally boned:
whitslack said:
If you have the engineering HBOOT, you can flash anything you want at any time. That's why it's so crucial to have it.
The point of no return looks like this:
You have the release HBOOT, AND
You are running system 1.47.*, AND
You have the stock recovery, AND
You do not have root access.
In other words, if one or more of the following are true, you can get all the rest:
You have the engineering HBOOT, OR
You are running system 1.32.*, OR
You have a custom recovery, OR
You have root access.
Click to expand...
Click to collapse
~~~~~ beyond this point is for historical interest only ~~~~~
If you're looking for a way to have working WiMAX with the 1.47.651.1 update and keep your root access, try this. It exhibits some interesting behavior at the end that is not seen with other update methods, which leads me to believe that this method does correctly upgrade the WiMAX.
There is confirmation that this method yields a working WiMAX/4G. And screen grabs.
Step 1: Revert to the initial release of everything
This PC36IMG.zip contains all the original firmwares from the first released RUU (hboot, boot, recovery, system, userdata, microprocessor, touch panel, radio, and WiMAX), except the HBOOT has been replaced with the one from the engineering build (to give you unlocked NAND) and the recovery has been replaced with Amon RA 1.7.0.1 (so you can flash updates signed with the test keys).
Note: This process will only work if you already have the engineering HBOOT. (If you have NAND unlocked, you already have it and can proceed confidently.) If you'd like to check the actual version, you can boot into HBOOT and look near the top of the screen: it should say HBOOT-0.76.2000, not 0.79.0000. If you have 0.79.0000, you will need to do Toast's Part 2 first before starting here.
Download this file, rename it PC36IMG.zip, and put it on the root of your SD card however you like.
PC36IMG-1.32.651.1_eng-hboot_RA-1.7.0.1.zip (md5=413285641ee70e8c197f38cea649205b)
Power off your phone.
Hold down the Volume Down and Power buttons until the white screen appears.
HBOOT will scan the PC36IMG.zip file. You'll see a blue progress bar on the right side of the screen.
When it's finished scanning, it will ask if you want to start the update. Press the Volume Up button to answer Yes.
Wait a while for it to flash all the images.
When it finishes and asks if you want to reboot the device, press the Volume Up button to answer Yes.
Your device is brand new again, except you have unlocked NAND and a custom recovery.
Delete the PC36IMG.zip file from your SD card.
Note: You will not have root at this point. This is to be expected, as you are running a totally stock system partition now. The key is that you have a custom recovery installed, meaning you can apply the su-2.1-e-unsecure-signed.zip update as described below, which will install the su and Superuser.apk files (i.e., give you root access).
Step 2: Rapid-fire updates
Download these three files to your SD card:
su-2.1-e-unsecure-signed.zip (md5=a055c916168db7e61a75a37a13993cd6)
OTA_Supersonic_1.32.651.6-1.32.651.1_rootsafe.zip (md5=7ecc89be93b3834babd782ca17e97b39)
OTA_Supersonic_1.47.651.1-1.32.651.6_rootsafe.zip (md5=1326bf00bcdcb6937a8cccd2a82c69fb)
Power off your phone.
Hold down the Volume Down and Power buttons until the white screen appears.
If you forgot to delete PC36IMG.zip from your SD card, HBOOT will scan it again now. When it asks if you want to start the update, press Volume Down to answer No. When it asks if you want to reboot, press Volume Down again.
Now you should be at the HBOOT menu. Press Volume Down to move the selection to RECOVERY and press the Power button to select it.
In a moment, you'll be at a different looking menu.
Using the Volume and Power buttons as before, select "Flash zip from sdcard."
Select su-2.1-e-unsecure-signed.zip from the list and follow the prompts to flash it.
When that's finished and you're back at the menu, select "Flash zip from sdcard" again, choose OTA_Supersonic_1.32.651.6-1.32.651.1_rootsafe.zip, and follow the prompts to flash it.
You will now be updated to 1.32.651.6.
Ignore the warning that says "ignoring attempt to do multiple firmware updates."
It will say "Reboot via menu to complete installation." Do as it says and choose "Reboot system now" from the menu.
Now the first radio baseband update will be installed. Don't touch anything. The phone will reboot on its own, and you'll wind up back at the recovery menu.
Choose "Flash zip from sdcard," select the second OTA update, OTA_Supersonic_1.47.651.1-1.32-651.6_rootsafe.zip, and follow the prompts to flash it.
You will now be updated to 1.47.651.1. This one takes a while. Let it do its thing.
When it's finished flashing, it will tell you to reboot. Do as it says and choose "Reboot system now" from the menu.
Now the second radio baseband update and the WiMAX update will be installed. This takes a long time and doesn't display any progress on the screen, just an icon with a green circle of arrows. Don't touch it. It will reboot on its own.
After the reboot, you'll see some things you haven't seen by any other update method, including a barber pole progress bar and a dialog box that says "Checking for firmware update, please wait." (It shouldn't find one.)
When the home screen comes back up, you'll get a message box telling you "Your phone has been updated successfully to version 1.47.651.1."
You still have root and should have working WiMAX.
You can delete the three files off your SD card if you wish.
If your 4G keeps scanning but never connects, you might be helped by this post.
Extraneous images
(for use with fastboot flash)
These are just here in case they might be useful to someone. They are NOT NEEDED for the update procedure described above. Don't download them unless you know what to do with them.
HBOOT images
hboot-0.76.2000.7z (md5=0297a81509b6da5f102b1cc63893b9ad) – distributed with system 1.17.651.1 (engineering build)
hboot-0.79.0000.7z (md5=d38bff771f5015d420589f1d158d16af) – distributed with system 1.32.651.1 (initial release)
Boot images
boot-1.17.651.1.7z (md5=2a1a9d14f9b0405d92da31f0061b6915) – distributed with system 1.17.651.1 (engineering build)
boot-1.32.651.1.7z (md5=452bd071474e670d0d93aff34044a380) – distributed with system 1.32.651.1 (initial release)
boot-1.47.651.1.7z (md5=91f4bc8785e668afaefb9e55720e14a2) – distributed with system 1.47.651.1
System partition images (raw, not rooted!)
system-1.17.651.1.7z (md5=129ef3dbcb5359112b8edb610e930d6e) – engineering build
system-1.32.651.1.7z (md5=d7ea4d72e907065ebb10b3527e19ced0) – initial release; extracted directly from the original 1.32.651.1 RUU
system-1.32.651.6-OTA.7z (md5=9c7262db87caf03a729dc84db5a1fba6) – the preceding with the 1.32.651.6 incremental OTA update applied
system-1.47.651.1-OTA.7z (md5=6676cfa942469e4b4c66ef1364b3195f) – the preceding with the 1.47.651.1 incremental OTA update applied
system-1.47.651.1.7z (md5=5b8a1298da2daf99d5c2763ae151d9aa) – extracted directly from the 1.47.651.1 RUU
Warning: Don't flash system 1.47.651.1 without the engineering HBOOT installed!
Radio firmware images
radio-1.36.00.04.02.7z (md5=c66e6f1c689b2c5fe8431e50360d1a08) – distributed with system 1.17.651.1 (engineering build)
radio-1.39.00.04.26.7z (md5=9fea76170a5248ae2b96bde983f3ca3c) – distributed with system 1.32.651.1 (initial release)
radio-1.39.00.05.31.7z (md5=7873e091e321e8099b6edcb15cdcd8bd) – distributed with system 1.32.651.6
radio-2.05.00.06.10.7z (md5=9d8c21a453c0eb80c9206fb57c7c2557) – distributed with system 1.47.651.1
radio-2.05.00.09.01.7z (md5=c41569f876a9b87fec2feba0078c7bca) – distributed with system 3.29.651.5
WiMAX firmware images
wimax-4.6.2.2_v24722.7z (md5=44cebb3ebb8964fbbaa6ce09f6a22e0d) – distributed with system 1.17.651.1 (engineering build)
wimax-4.6.2.2v25043_R04.7z (md5=77a7b5a2258cc4270f9c29b135337894) – distributed with system 1.32.651.1 (initial release)
wimax-4.6.2.2v25641_R01.7z (md5=7e95eed2182ed38de85bdb085e842dbd) – distributed with system 1.47.651.1
wimax-4.6.2.2v26023_R01.7z (md5=0b4c80d131eb95dab0874876ffb81586) – distributed with system 3.29.651.5
I'll be a guinea pig and try this out soon as my phone is done charging.
Quick question, though. Have you done this yet yourself? If you have, are you able to write to /system outside of recovery after flashing everything?
This is interesting and certainly worth watching.
So...after this procedure we are basically left with a stock (1.47xxxx) ROM?
trying this as soon the files finish downloading!!
Land Master said:
This is interesting and certainly worth watching.
So...after this procedure we are basically left with a stock (1.47xxxx) ROM?
Click to expand...
Click to collapse
The contents of your /system will be exactly as though you had never heard of xda-developers, with these exceptions:
/system/xbin/su is added
/system/bin/su (a symlink to /system/xbin/su) is added
/system/app/Superuser.apk is added
Everything else is identical to stock, and in fact, future OTA updates would apply without complaining (and rob you of your root, so always decline them!).
Pardon my ignorance, but I didn't see it mentioned, will this bypass the "mainver" check that prevents me from reflashing the original PC36IMG.ZIP?
Thanks for you effort!
bprinehart said:
Pardon my ignorance, but I didn't see it mentioned, will this bypass the "mainver" check that prevents me from reflashing the original PC36IMG.ZIP?
Thanks for you effort!
Click to expand...
Click to collapse
I actually did this process twice, back to back. So yes, I was able to flash the PC36IMG.zip linked in the OP directly over the latest 1.47.651.1 with the latest radio. Nothing complained of a MainVer.
Dude...if this works...I'm going to hunt you down and kiss you. Or at least buy you a six-pack!! I'm dead in the water right now, I can boot into the hboot menu, or fastboot, but nothing else. Going to try right now!
whitslack said:
The contents of your /system will be exactly as though you had never heard of xda-developers, with these exceptions:
/system/xbin/su is added
/system/bin/su (a symlink to /system/xbin/su) is added
/system/app/Superuser.apk is added
Everything else is identical to stock, and in fact, future OTA updates would apply without complaining (and rob you of your root, so always decline them!).
Click to expand...
Click to collapse
WOW! Keeping my fingers crossed on this one. Its exactly what I was waiting (hoping) for.
Is NAND unlocked?
Assuming yes..... then we would still need to stick with ROM's that are based on the 1.47xx code correct?
The radio/wimax debacle would stick from this point forward?
Thanks!
Edit: Nevermind the NAND question. I re-read the OP and see that it is. Just install Clockwork and rock and roll...
awesomeindeed said:
Quick question, though. Have you done this yet yourself? If you have, are you able to write to /system outside of recovery after flashing everything?
Click to expand...
Click to collapse
Yes, I have. I made a backup of the su binary in another directory on /system, as a little insurance against a future stealth OTA update. NAND is definitely unlocked.
flashing 1st file the Pc file!!
Land Master said:
Assuming yes..... then we would still need to stick with ROM's that are based on the 1.47xx code correct?
The radio/wimax debacle would stick from this point forward?
Click to expand...
Click to collapse
Unless the ROM you're going to install comes with its own radio+WiMAX images (and you're confident that it actually installs them correctly), you would want to stick with ROMs that are based on the 1.47.651.1 system, yes.
Damnit...no dice for me. Just got to the second checking PC36IMG.zip stage and then went back to hboot menu. Thank you for at least giving me a shred of hope for a second.
whitslack said:
Unless the ROM you're going to install comes with its own radio+WiMAX images (and you're confident that it actually installs them correctly), you would want to stick with ROMs that are based on the 1.47.651.1 system, yes.
Click to expand...
Click to collapse
Excellent!! Thanks.
Honestly if this works I would hope the other Dev's just incorporate it rather than package a separate radio + WiMax. I have been following this for three days and I'm not confident in anything at this point.
Truly have my fingers crossed for yours.
bprinehart said:
Damnit...no dice for me. Just got to the second checking PC36IMG.zip stage and then went back to hboot menu. Thank you for at least giving me a shred of hope for a second.
Click to expand...
Click to collapse
What version of HBOOT are you running? (It will say at the top of the HBOOT screen.)
Have you tried going into FASTBOOT and flashing the mtd-eng.img to the misc partition?
If you have fastboot access, you can flash any image you want to any partition. You could even flash the system and userdata partitions to get yourself back into a working state. Try unzipping the PC36IMG.zip on your computer and using the fastboot utility to flash the system.img to the system partition and the userdata.img to the userdata partition.
bprinehart said:
Damnit...no dice for me. Just got to the second checking PC36IMG.zip stage and then went back to hboot menu. Thank you for at least giving me a shred of hope for a second.
Click to expand...
Click to collapse
i am already installing the last file!!! hopefully it works nd we get 4g, i live in a 4g city!!
Land Master said:
Excellent!! Thanks.
Honestly if this works I would hope the other Dev's just incorporate it rather than package a separate radio + WiMax. I have been following this for three days and I'm not confident in anything at this point.
Truly have my fingers crossed for yours.
Click to expand...
Click to collapse
*shrug* Really no credit is due to me. These files are almost straight from HTC. The only change I made to the OTAs was to add one line so they don't blow away the setuid-root permissions on /system/xbin/su.
Flashing the last file as well... here's to hoping.
whitslack said:
What version of HBOOT are you running? (It will say at the top of the HBOOT screen.)
Have you tried going into FASTBOOT and flashing the mtd-eng.img to the misc partition?
Click to expand...
Click to collapse
hboot version: 0.79.0000
Whenever I try to flash, I get a signature verification failure, or a remote: not allowed
Any ideas?
We tried, 4g, went on scan and then went off!!
trying to update profile!!
Alright guys,
This is for everyone that is not using windows or mac.
First of all - congrats! You made the right decision by not using them. Ha-ha!
Also - Thanks to everyone that was involved in getting us the so much needed S-OFF - Developers and Testers.
Now, to get S-Off you need to go to http://revolutionary.io/
Just in case - read everything that is in there, and remember that this is a Beta release, so sh*t can go wrong.
Click on "Download For Linux" . This will download revolutionary-0.3pre7.tgz
Now open Home folder, navigate to Downloads, find the file that you just downloaded, right click, and choose "extract here".
Or if you are using the console - you need to do this:
Navigate to the Downloads folder and
Code:
tar -zxf revolutionary-0.3-pre7.tgz
Now open your terminal, and navigate to the Downloads folder. You can do that by typing
Code:
cd ~/Downloads
Once you are in there - do the following:
Code:
sudo ./revolutionary
or if you are root, just do
Code:
./revolutionary
In general, its not a very good idea to stay logged in constantly as root, so yeah.
Once you downloaded the file - it redirected you to the Generator, where you need to put in your information about the phone.
Once you run revolutionary - you can find all the information needed in there, just put in the information, click on "generate", highlight the code, right click, copy, and then go to the console, right click, paste, and hit enter.
Once you get root and everything else, it will ask you if you want to install CWM. It is important to have that, so please choose "Y".
And now you can sit back and enjoy how this is magic
[EDIT]
If you have any problems with revolutionary finding the device - please make sure that you did add the appropriate udev rules to the file /etc/rules.d/51-android.rules
To make sure that your computer sees the phone - just type
Code:
adb devices
If you see it as "??????????????" - then you do need to follow the next guide to add the udev rules.
For more information on how to do that - please follow THIS GUIDE
For more information on how to use ADB under Ubuntu - please check out THIS GUIDE
Thanks, this worked like a charm! Thank to the devs that brought this to us! I've been eagerly awaiting this, almost took my bro's MT4G just to get my flashing fix!! All I need is an AOSP Rom and I'm golden, lol
I'm getting "waiting for device..."
Is there a certain point when I need to plug in my Sensation? I'm able to mount the phone with no issues in linux, but for some reason revolutionary won't identify it.
Wow, 2 minutes with no hiccups on a UK Vodafone branded Sensation. Just carrying out a quick nandroid. Thanks for the tut, much appreciated.
Thanks, will be using this to S-OFF my Sensation when I get home later today!
Ubuntu ftw
Sent from my HTC Sensation using XDA Premium App
Thareal1 said:
I'm getting "waiting for device..."
Is there a certain point when I need to plug in my Sensation? I'm able to mount the phone with no issues in linux, but for some reason revolutionary won't identify it.
Click to expand...
Click to collapse
Did you add the add appropriate udev rules to the file /etc/rules.d/51-android.rules ?
Or with other words, when you are using adb under ubuntu - when you do adb devices - do you see your device with "?????????????" or do you see it like its really installed with numbers ?
If you havent added the udev rules - you can find more information on how to do it HERE
t0ny0 said:
Alright guys,
This is for everyone that is not using windows or mac.
Click to expand...
Click to collapse
Holy smokes, was this easy!! Between your guide and ikhzter's sticky, I had root in about 10 mins. 15 mins later I had a full TB backup. Outstanding!
marcjw said:
Holy smokes, was this easy!! Between your guide and ikhzter's sticky, I had root in about 10 mins. 15 mins later I had a full TB backup. Outstanding!
Click to expand...
Click to collapse
Glad I could help. Plus the guys that made Revolutionary really did their best to make life easy for us
Hi
I've tried to do that but :
Acquiring root (method 3)...
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Rebooting to fastboot (again)...
Rebooting to fastboot (yet again)...
Rebooting to fastboot (Once moar...)
SUCCESS - Life gave us lemons, we didn't make lemonade!
Do you want to download (Internet connection required) and flash ClockworkMod Recovery? [Y/n] y
Downloading recovery for your phone (pyramid)...
^C
Click to expand...
Click to collapse
At this section i've lost my internet connection and nothing happend, then i did ctrl+c and after rebooting i've tried to do it again:
Waiting for device...
Found your device: HTC Sensation Z710e (pyramid-1.17.1011, Android: 2.3.3, ROM version: 1.35.720.1)
Your device is not supported at this time.
Click to expand...
Click to collapse
now i dont have ClockworkMod.
I've installed rom manager to install ClockworkMod, the romManager says that it couldnt find sudo user at /system/(x)bin/su
when im rebooting into recovery mod, it says that device is S-OFF.
to access root i found this on http://revolutionary.io/
Does Revolutionary give me root?
No. You will need to flash this zipfile from recovery.
Click to expand...
Click to collapse
when i tried to flash it, it says that signauture verification failed...
i've read from this page that i must install clockworkMod to disable signature verification but rom manager says "an error occured while attemting to run privileged commands!"
it seems that im in a loop...
pezhman32 said:
Hi
I've tried to do that but :
At this section i've lost my internet connection and nothing happend, then i did ctrl+c and after rebooting i've tried to do it again:
now i dont have ClockworkMod.
I've installed rom manager to install ClockworkMod, the romManager says that it couldnt find sudo user at /system/(x)bin/su
when im rebooting into recovery mod, it says that device is S-OFF.
so where doese my root gone?! what should i do now?!
Click to expand...
Click to collapse
You can find more information here - http://forum.xda-developers.com/showthread.php?t=1192300
Or to be exact - you need this:
ikhzter said:
STEP 2. To INSTALL Clockwork Recovery mod- v4.0.1.4 from Revolutionary. Issue With not charging when Device is completely switched off - DOES CHARGE WHEN HIBERNATING (SWITCHING OFF on stock rom) WITH FASTBOOT ENABLED
YOU MUST READ ABOUT THE CHARGING ISSUE in post 3 below before installing!!!!!
1. Download clockworkmod recovery by Revolutionary for the Sensation HERE:
2. Copy the PG58IMG file into the Root folder of your SD card (The main Folder of your Memory Card)
3. Turn off your phone FUlly and reboot into the Bootloader/HBOOT screen (see post above on how to get to hboot screen)
4. Press Volume up to Accept when it asks" Do you want to start the update"
5. Press Power Off to Reboot back to android after installation is successful (normal screen with homescreen)
6. Delete PG58IMG from your memory card and you can now root using step 3 below or install a custom ROM using CWM (Customs Roms are already rooted)
7. Turn the phone back on. click settings > Power > ensure fastboot is enabled (ticked). This will help you charge incase your battery dies. If you hibernate (or switch off on stock roms) with fastboot enabled your phone will still charge
IF YOUR BATTERY IS LOW, SWITCH OFF WITH FASTBOOT ENABLED TILL YOU CAN CHARGE IT (Press Hibernate (on stock Roms) or power off if you don't have hibernate)
IF YOUR PHONE BATTERY DIES WHILST YOU ARE USING IT. DO NOT POWER IT ON OR PULL THE BATTERY OUT.
Make sure you have had it on charge for at least a few minutes then turn it on as normal and continue charging
Currently with fastboot enabled when your phone dies it will hibernate. allowing you to still charge it. If you plug in your charger then switch on, it will boot back up in a few seconds as fastboot is active and it will resume from where you left off.
Turning off without fastboot means your phone will fully turn off not hibernate and your phone will not charge when turned off.
Step 3. To permanently root your Sensation - (This means you will NOT LOSE ROOT on rebooting) DOES NOT AFFECT WIFI
1. Download the file su-2.3.6.3-ef-signed.zip from here: DOWNLOAD
2. Copy su-2.3.6.3-ef-signed.zip to your SD card root folder (main folder of your memory card)
3. Start clockworkmod recovery (instructions below)
4. BACKUP YOUR ROM USING CWM BEFORE ATTEMPTING ROOT!
5. Navigate to "Backup & Restore" using the Volume Down button and press select (power button to select) then select "Backup"
6. Select "install zip from sdcard" after backing up
7. Then select "Choose zip from sdcard"
8. Then select "su-2.3.6.3-efgh-signed.zip"
9. Then select "Yes - install su-2.3.6.3-efgh-signed.zip" to confirm
10. Then go back
11. Then reboot.
12. You're rooted!
Click to expand...
Click to collapse
t0ny0 said:
Alright guys,
Code:
cd /home/username/Downloads
where "username" is the username that you are using.
Click to expand...
Click to collapse
Not trying to be a troll but a little friendly advice =)
instead of /home/username/ and having them put in their username (which some might not know) use ~/Downloads
"~" replaces "/home/username" =)
nice little write up
jassycliq said:
Not trying to be a troll but a little friendly advice =)
instead of /home/username/ and having them put in their username (which some might not know) use ~/Downloads
"~" replaces "/home/username" =)
nice little write up
Click to expand...
Click to collapse
Always appreciating advises
Changed it, thanks !
Yay delighted been waiting for this for like aaaaaaaages and now I'm happy hahahah Cheers lads fair play to yeas,,
@t0ny0 : that was a complete answer which solved my problem
thx G
pezhman32 said:
@t0ny0 : that was a complete answer which solved my problem
thx G
Click to expand...
Click to collapse
Glad I could help
To start off everyone should know that messing with your phone can brick it!! You should not mess with your phone if you are unsure of what you are doing. You will get this (or a similar) warning while following the unlock instructions from Motorola as well. Following these instructions also voids your warranty!
I only use Motorola's official firmware for the moment and these instructions were originally performed on the ASA14 firmware. They should be useful for previous versions of the firmware but I will not be testing those. These instructions may not work for releases after ASA14.
While following this guide you need to be on a Windows PC with the administrator account or an account with administrative privileges. If you do not have these privileges you will likely run into issues. All instructions are written for a PC running Windows 7 as that is the only PC I have access to. If anyone has any instructions using a different version of Windows I will gladly add them in.
Windows commands:
dir - Lists all directories (folders) and files of the directory you are currently in.
cd {directory name} - Moves into the named directory. The directory names are case-sensitive.
cd.. - Moves to the directory before the one you are currently in. For instance if you are in C:\Users\Public and perform cd.. you will move to C:\Users
{Unlocking the Bootloader}
I'm writing this pretty late and formatting takes forever so I'll update this section later with my own set of instructions. For now use this guide which I plan on using for inspiration since I can't really repeat the unlock process.
Below is my work in progress. This is incomplete and will be unhidden when it is completed.
Updated Unlock
1. Download the Android SDK
2. Unzip the file. If you don't have a program to unzip the file 7-zip is great.
3. Move the unzipped folder to a location that is easy to locate. For me I put this in "Documents".
4. Rename the folder to something shorter, that way it's easier to type in later. "ADT" is easy to use and remember.
5. Download the drivers for the phone.
6. Open "MotorolaDeviceManager_2.3.9.exe" and install the drivers.
7. Go here
8. Click "PROCEED ANYWAY"
9. Register an account with Motorola.
10. Go to Start > All Programs > Accessories
11. Open “Command Prompt”
12. Use the cd commands to navigate to your “platform-tools” folder.
13. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
14. Turn it back on using the power button + volume up + volume down combination
15. Select “Fastboot” (volume down cycles through, volume up selects the option)
16. Connect your phone to your PC.
17. Type "fastboot oem get_unlock_data" in Command Prompt.
{Installing a New Recovery}
For the recovery we’re going to install the Photon Q Open Recovery. Every recovery has its advantages and disadvantages. This one is familiar to me and so I chose it for this guide.
1. Download the recovery image
2. Place the image in the Android SDK “platform-tools” folder which is in the "sdk" folder
3. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Fastboot” (volume down cycles through, volume up selects the option)
6. Connect your phone to your PC
7. Go to Start > All Programs > Accessories
8. Right-click “Command Prompt”
9. Click “Run as administrator”
10. Use the cd commands to navigate to your “platform-tools” folder (Unfortunately I cannot tell you where this is as each computer will have it placed differently)
11. Type in “fasboot flash recovery open_recovery_206_05_06_2013.img”
{Getting Root}
1. Download the zip file for rooting
2. Place the file in the root (ie. not within a folder) of your phone’s SD card
3. Turn your phone off
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Recovery” (volume down cycles through, volume up selects the option)
6. Select “Apply Update” (In recovery the the controls change. Volume up and volume down move in the list, the camera button at the bottom right of the device selects.)
7. Select the file you placed on your SD card from step 2
8. Wait for the update to apply, it should say that it finished successfully
9. Select “Reboot Phone”
Credit for all of this goes to their respective creators. I will name them all by name at a later date, but the credit can also be found following the linked material. Hopefully that doesn't bother the creators, writers, or hosts.
The Open Recovery port was done by Skrilax_CZ.
SuperSU is hosted by shabbypenguin and developed by Chainfire.
Please don't re-post this how-to without crediting. I've had it happen before and it was a huge disincentive for updating and making new guides.
section "{Installing a New Bootloader}" and "1. Download the bootloader image" below it are actually reffering to recovery (probably the best one out there). Not a bootloader.
Bootloader boots the system. Depending on keys pressed during boot (if any, or if instructed by commands) it can boot to bootloader menu, recovery, system (android)...
Ah, thanks. I would have known that if I rechecked but I haven't had time to.
Edit:
While I was editing I noticed I referenced it as recovery multiple times and was switching between the two as the guide went on!
unlocking bootloader failed
ok so i got the device id went to the motorola site said it was good got the unlock key did the step and typed it in the command prompt and it says
(bootloader) password incorrect
(bootloader) oem unlock failure
FAILED <remote failure>
sorry if this is a noob question usualy dont post first time last time i rooted a fone was on an evo 4g so never really messed with command prompts and unlock keys to much i repeted the whole process 3 times already and i still get the same message
edit: nvm got it to work hahaha forgot to capslock the letter in the key thanks for the write up man
demi_god_619 said:
ok so i got the device id went to the motorola site said it was good got the unlock key did the step and typed it in the command prompt and it says
(bootloader) password incorrect
(bootloader) oem unlock failure
FAILED <remote failure>
sorry if this is a noob question usualy dont post first time last time i rooted a fone was on an evo 4g so never really messed with command prompts and unlock keys to much i repeted the whole process 3 times already and i still get the same message
edit: nvm got it to work hahaha forgot to capslock the letter in the key thanks for the write up man
Click to expand...
Click to collapse
Yeah, unfortunately there's are a few points where unlocking get's confusing. I had to enter my stuff from the command prompt to Motorola's site like 5 times before I figured out where the copy/paste had spaces. It took me a while to figure out I had pasted an extra space at the end. This was the first phone for Motorola's bootloader unlock plan so I'm hoping they improve on it for their future phones.
The OP is updated with some more color-coding, updated credits (though I didn't try to get everyone just yet), and changed the link to an updated SuperSU. This should work on the Jellybean update though I won't know for sure unless someone confirms it in this thread. I've taken a break from messing with my personal phone for a while so I won't be checking the boards as often but I'll still be checking every few days.
Solust said:
The OP is updated with some more color-coding, updated credits (though I didn't try to get everyone just yet), and changed the link to an updated SuperSU. This should work on the Jellybean update though I won't know for sure unless someone confirms it in this thread. I've taken a break from messing with my personal phone for a while so I won't be checking the boards as often but I'll still be checking every few days.
Click to expand...
Click to collapse
FYI, if you install TWRP it will detect whether you have root or not and offer to install it for you.
Simplifies the guide a bit, and IMHO TWRP is a great recovery - all touch based, no more mashing the volume keys .
Nicely done regardless.
I noticed I was missing a step in the {Getting Root} section. It was an implied step but I added it for clarity.
I also had forgotten to mention that once you get into recovery the buttons used to control things change slightly. You can use the keyboard in addition to the device buttons.
Thanks for the How-to!:good: I was wondering if you would mind if I gave you or added some instructions for Linux users?
xaelith said:
Thanks for the How-to!:good: I was wondering if you would mind if I gave you or added some instructions for Linux users?
Click to expand...
Click to collapse
Yeah that would be fine. PM me the instructions and I'll test them out on my Linux partition. It'll probably take a few days as I have things coming up.
I've updated the links in the OP to Open Recovery 2.06 (changing the name in the command accordingly) and started writing my own set of bootloader unlock steps. They aren't complete yet but if someone is having troubles understanding the first few steps of the linked article mine should be broken down to be a bit easier to digest.
Solust said:
I've updated the links in the OP to Open Recovery 2.06 (changing the name in the command accordingly) and started writing my own set of bootloader unlock steps. They aren't complete yet but if someone is having troubles understanding the first few steps of the linked article mine should be broken down to be a bit easier to digest.
Click to expand...
Click to collapse
Open Recovery is on version 2.09 now. Has anyone tried it? I tried it using the posted steps but I got the same result as when I tried cmwrecovery, the phone doesn't boot to it, it boots to an image of the android guy on his back with his belly open and a red exclamation point hovering over him. Any advise? It's a Photon Q using Android version 4.1.2 nand I have successfully unlocked the bootloader.
I never changed versions because most of the updates target Kit-Kat based custom ROMs. Make sure your phone is NOT plugged in when you try to get into recovery. If it doesn't work when not attached to anything re-download the recovery and try installing again.
Entomology onsaboo
Solust said:
I never changed versions because most of the updates target Kit-Kat based custom ROMs. Make sure your phone is NOT plugged in when you try to get into recovery. If it doesn't work when not attached to anything re-download the recovery and try installing again.
Click to expand...
Click to collapse
I have tried to get into recovery both plugged in and not plugged in. I tried downloading and re downloading both CMWrecovery and open recovery 2.09 both.
Are you saying Open Recovery 2.09 is targeted at Kit-Kat custom ROMs and won't work on my phone? Should I try the version in your OP?
It should work in theory regardless of Kit-Kat, but if you've already tried all of that then give the older version a shot. I really post only what I know and have tried in the original post. It's beyond the scope of my thread though so you may have better luck asking in the recovery threads if you can't get any version to work. I'm on my phone for the time being or I would link you to the appropriate threads myself.
Solust said:
It should work in theory regardless of Kit-Kat, but if you've already tried all of that then give the older version a shot. I really post only what I know and have tried in the original post. It's beyond the scope of my thread though so you may have better luck asking in the recovery threads if you can't get any version to work. I'm on my phone for the time being or I would link you to the appropriate threads myself.
Click to expand...
Click to collapse
I couldn't fine a copy of the older version anywhere.
I understand, and I thank you for your help.
Solust said:
To start off everyone should know that messing with your phone can brick it!! You should not mess with your phone if you are unsure of what you are doing. You will get this (or a similar) warning while following the unlock instructions from Motorola as well. Following these instructions also voids your warranty!
I only use Motorola's official firmware for the moment and these instructions were originally performed on the ASA14 firmware. They should be useful for previous versions of the firmware but I will not be testing those. These instructions may not work for releases after ASA14.
While following this guide you need to be on a Windows PC with the administrator account or an account with administrative privileges. If you do not have these privileges you will likely run into issues. All instructions are written for a PC running Windows 7 as that is the only PC I have access to. If anyone has any instructions using a different version of Windows I will gladly add them in.
Windows commands:
dir - Lists all directories (folders) and files of the directory you are currently in.
cd {directory name} - Moves into the named directory. The directory names are case-sensitive.
cd.. - Moves to the directory before the one you are currently in. For instance if you are in C:\Users\Public and perform cd.. you will move to C:\Users
{Unlocking the Bootloader}
I'm writing this pretty late and formatting takes forever so I'll update this section later with my own set of instructions. For now use this guide which I plan on using for inspiration since I can't really repeat the unlock process.
Below is my work in progress. This is incomplete and will be unhidden when it is completed.
Updated Unlock
1. Download the Android SDK
2. Unzip the file. If you don't have a program to unzip the file 7-zip is great.
3. Move the unzipped folder to a location that is easy to locate. For me I put this in "Documents".
4. Rename the folder to something shorter, that way it's easier to type in later. "ADT" is easy to use and remember.
5. Download the drivers for the phone.
6. Open "MotorolaDeviceManager_2.3.9.exe" and install the drivers.
7. Go here
8. Click "PROCEED ANYWAY"
9. Register an account with Motorola.
10. Go to Start > All Programs > Accessories
11. Open “Command Prompt”
12. Use the cd commands to navigate to your “platform-tools” folder.
13. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
14. Turn it back on using the power button + volume up + volume down combination
15. Select “Fastboot” (volume down cycles through, volume up selects the option)
16. Connect your phone to your PC.
17. Type "fastboot oem get_unlock_data" in Command Prompt.
{Installing a New Recovery}
For the recovery we’re going to install the Photon Q Open Recovery. Every recovery has its advantages and disadvantages. This one is familiar to me and so I chose it for this guide.
1. Download the recovery image
2. Place the image in the Android SDK “platform-tools” folder which is in the "sdk" folder
3. Turn off your phone (power button + volume down if you can't select any options to turn off the phone)
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Fastboot” (volume down cycles through, volume up selects the option)
6. Connect your phone to your PC
7. Go to Start > All Programs > Accessories
8. Right-click “Command Prompt”
9. Click “Run as administrator”
10. Use the cd commands to navigate to your “platform-tools” folder (Unfortunately I cannot tell you where this is as each computer will have it placed differently)
11. Type in “fasboot flash recovery open_recovery_206_05_06_2013.img”
{Getting Root}
1. Download the zip file for rooting
2. Place the file in the root (ie. not within a folder) of your phone’s SD card
3. Turn your phone off
4. Turn it back on using the power button + volume up + volume down combination
5. Select “Recovery” (volume down cycles through, volume up selects the option)
6. Select “Apply Update” (In recovery the the controls change. Volume up and volume down move in the list, the camera button at the bottom right of the device selects.)
7. Select the file you placed on your SD card from step 2
8. Wait for the update to apply, it should say that it finished successfully
9. Select “Reboot Phone”
Credit for all of this goes to their respective creators. I will name them all by name at a later date, but the credit can also be found following the linked material. Hopefully that doesn't bother the creators, writers, or hosts.
The Open Recovery port was done by Skrilax_CZ.
SuperSU is hosted by shabbypenguin and developed by Chainfire.
Please don't re-post this how-to without crediting. I've had it happen before and it was a huge disincentive for updating and making new guides.
Click to expand...
Click to collapse
I got an error when I clicked on the recovery image download link. Is there a better method?
EpicSaga said:
I got an error when I clicked on the recovery image download link. Is there a better method?
Click to expand...
Click to collapse
See the OpenRecovery thread for a valid link to that recovery... the links are a bit outdated for OR, look near the end of the thread.
I have the link to the Open Recovery thread at the very start of the section about installing recovery. It's there in case links die, someone wants more info on what they're installing, or someone has support questions pertaining to Open Recovery. This thread didn't seem to be very popular compared to one I made for an older phone so I haven't kept it up to date. The phone has been out for some time as well so I likely won't be updating this thread.
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming. Being a noob at the time, i was also extremely nervous that i could possibly brick my phone or screw something up. i didn't, and no part of this should brick yours either. ***However - if you do somehow break your device in any way, that is on you. by completing these steps, you assume full responsibility. now that we have that out of the way, lets continue. at the end of this guide, you should have a rooted device with your choice of os (7 or 8 - or even a custom rom if you choose!). you should also have twrp. this guide would not have been possible without users runningnak3d and clsA
**** Also, during this Proccess, Your Phone WILL be wiped clean!!! don't forget to back up photos, videos, etc...*****
don't download any other files than from this guide.
1. download these files (required) https://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz (for a rootable os that we can flash, - get this also (required) https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 this program is called lg up and has been patched to work with this phone. you will also need this. https://androidfilehost.com/?fid=1322778262903990218. these are the root files and need to be all in the same folder as where lg up is installed. you will also need to have access to fastboot and need to have adb installed. that is pretty easy, give it a google search if you still need help.
if you are running 32 bit, get this https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
this is the OS. get nougat, which has like three less steps (you can't upgrade to oreo on this os once rooted) or scroll down and get the oreo file. nougat (really old version) https://drive.google.com/file/d/1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X/view
Oreo - get this first file, and the ones under it. https://www.androidfilehost.com/?fid=1322778262904015326
***https://androidfilehost.com/?w=files&flid=283977*** You have to have this file if getting oreo. if you chose nougat, then don't get this.
2. Now that you have everything downloaded and installed, put your phone into download mode. (power it off, hold the volume down button and plug in a usb c cable attached to your pc. don't stop holding volume down until you see download mode.)
3. once it is in download mode, open up lg up. select your device, (it should be in standby mode, according to lg up) and click dump (this is a total backup of the phone, you are lucky you know this right now, I didn't when i rooted mine) . it will bring up a file explorer, select where you want it to save to. (I chose my desktop). once you have a folder selected., it will bring up a bunch of options for partitions. click select all and uncheck user data. ****Make SURE that you don't unplug your phone during any part of this process or any other process in this guide, it will permanently brick it. ***** ow that you have selected everything but userdata, click start.
4. once that finishes, you will have made a full backup of your phone in case something goes wrong.
then click the partition DL button and select the h915 v10e kdz file (the file that i said was the rootable os we can flash) (the first file you downloaded). make sure bin file stays checked. then click start. once that finishes, your phone should automatically reboot into an old nougat operating system. then go to settings, enable developer options, and turn on usb debugging. that is easy, if you can't figure it out, google is your friend. now you should have no cellular signal. this is not the permanent ROM.
5. go to the play store and download terminal emulator for android. (once usb debugging has been enabled
then go ahead and go to the folder where you extracted the root files/package. hold shift and right click to open a command windows there or powershell, whatever your pc says. open 2 of those windows. then, in the first one, type, adb logcat -s dirtysanta
****don't close this window.*****
then in the other window, type STEP1.BAT
*****don't close this window.***** It may take a minute, but after a while it will let you type again. once you can, type run-as con
chmod 0777 /storage/emulated/0/*
6. then, pull up the window you used the logcat command in. leave it there so you can watch it
then, on your phone, go to the terminal emulator and type applypatch /system/bin/atd /storage/emulated/0/dirtysanta
once you do that, glance at the logcat window. once it says to run step 2, go to the window where you typed step1.bat. type STEP2.BAT
at this point, your phone should go ahead and reboot and say fastboot mode up at the top. now, go to your window where you typed all the .bats and type STEP3.BAT. wait until your phone reboots and you will see a screen saying that you can;'t use your phone. this is bogus, just ignore it and wait like 10-15 seconds for it to get past that screen. then it will boot that android and you should get a green screen.
Now, quickly, pull the battery from your phone. leave it out for a little while while we prepare the next steps.
If you want oreo, scroll to where it says OREO in capital letters. if you want nougat, scroll to where it says NOUGAT.
NOUGAT
use the file that you downloaded if you selected nougat - it should be a zip. it will be called h910-10r. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the h910 zip file and install it. then go ahead and reboot your phone, you will have a rooted android 7 rom. you will also have signal. then download supersu from the play store and open it to have root.
OREO
use the file that you downloaded if you selected oreo - it should be a zip. it will be called something along the lines of full stock oreo rooted. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. also, go to your root package folder and find the twrp image file and put that on your sd card. then go get the mk200 zip file and also place that on your sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the oreo full rooted zip and install it then, install the mk2000 file. after you have done this, click install image and select the twrp. the reason you need to re flash this is because that oreo file re installs the stock recovery. then install the twrp. now reboot your phone. you will have a rooted android 8 rom. you will also have signal. then download a magisk 6.0 manager apk from chrome browser to have root.
IF this worked and your enjoying root give me a thanks.
This is redundant to the existing h910 root guide, all you did was copy their work and re-post it
Sent from my LG-H910 using XDA Labs
cnjax said:
This is redundant to the existing h910 root guide, all you did was copy their work and re-post it
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Yes, that is why i gave them credit. However, It is more noob friendly and takes the time to explain what they are doing to their own phones as well as give them the option for nougat or oreo, something that none of the other guides have.
Ok, so I did it sucessfully, it's was still very complicated for me as some info is vague for a beginner. But after searching and retrying, and retrying, it worked. but go to runningnak3d post to get more info, and he wanted me to use sd card to root, but that did not work for me.. Your method worked for me. Thanks
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming....
Click to expand...
Click to collapse
your guide is good
+1 for for linking to the missing files from the old guide
+1 for mentioning me and @runningnak3d
you could break up the long paragraphs and bullet style the steps in order so it's easy to follow
theirs a video here of the steps and how the command windows should look > https://www.youtube.com/watch?v=jnRWnSHLGSc
this is where allot get confused in the guide.
I also don't remember you mentioning doing the battery pull after STEP1 when the phone sometimes hangs then run STEP2
I would also change the link to the H915 kdz to the android file host file in case LG changes it.
Their was a guy recently that could not get LGUP working you could make note that you may need the 32 bit VS 2010 > https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Any how, the guide is OK and the steps are not that bad, after a few tries most anyone can learn it.
clsA said:
your guide is good
+1 for for linking to the missing files from the old guide
+1 for mentioning me and @runningnak3d
you could break up the long paragraphs and bullet style the steps in order so it's easy to follow
theirs a video here of the steps and how the command windows should look > https://www.youtube.com/watch?v=jnRWnSHLGSc
this is where allot get confused in the guide.
I also don't remember you mentioning doing the battery pull after STEP1 when the phone sometimes hangs then run STEP2
I would also change the link to the H915 kdz to the android file host file in case LG changes it.
Their was a guy recently that could not get LGUP working you could make note that you may need the 32 bit VS 2010 > https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
Any how, the guide is OK and the steps are not that bad, after a few tries most anyone can learn it.
Click to expand...
Click to collapse
alright, thank you so much for the advice! 1. i don't want to switch to bullets because when i was trying runningnak3d's guide, it seemed overwhelming. also people can comment on the step number that they were lost at. 2. i will change the kdz to something else if the file does change. i did in fact mention the battery pull step, if you ever need to find something in a page, hit control and f and then search the page.. i will add the 32 bit file. Thanks!
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available
. . .
this guide would not have been possible without users runningnak3d and clsA
IF this worked and your enjoying root give me a thanks.
Click to expand...
Click to collapse
W O W . . .
What a way to rip-off runningnak3d's guide.
I mean, I can understand rewriting it... I did the same. But, just to parse it out for me to follow better.
But your statement "...there was no root guides available..." is just BS.
Below is my guide... for me to do the process.
Creation date on the text file was November 7, 2017. Just over a week after runningnak3d made the original post.
Difference is, I didn't feel the need to post someone else's work, in an attempt to try claiming credit for it, due to nothing more than a "rewrite".
What you meant to do is this: (FIFY)
Cool guide for rooting your LG V20. Works for 20h, too!
--------------------------------------------------------------------------------------------------------------------
Materials:
8+GB microSD Card - formatted exFAT or ext4
LG Up (patched)
C:\Program Files (x86)\LG Electronics\LGUP <- install here, or it won't read DLL correctly
ADB
DirtySanta root package - (No working Link)
H91510e_00_VTR_CA_OP_1205.kdz - http://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz
h910-10r.zip - https://drive.google.com/open?id=1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X
- Check the SHA hash: 5451146030393e490dcfba3558b620badefe75cd
Terminal Emulator APK
Root Checker APK
Settings Database Editor APK
1) Copy h910-10r.zip, SuperSU-v2.82.ZIP, SuperSU.Pro.APK, Terminal Emulator, Root Checker, and Settings Database Editor to microSD Card and insert into phone.
2) Put phone into download mode (power off / hold vol. up & plug in USB cable)
Use LG UP to dump phone. When you run it, there will be additional radio buttons.
- Pick the one that says DUMP and click Start. You will be asked what partitions to dump, click the "select all" checkbox, and then you can uncheck "userdata".
3) When finished with the Dump, click the PARTITION DL radio button, pick the H915 v10e KDZ, and click start. Make sure all partitions are checked.
- Select H91510e_00_VTR_CA_OP_1205.kdz, Tick box to set as input file.
- Select all partitions
- Confirm all partition changes
- Once it is complete, phone will reboot into old Freedom Mobile ROM
- Disconnect USB Cable
- Complete Android setup, and you may not have signal (this is normal).
- Enable developer mode, and enable USB debugging.
- Enable Unknown Sources
- Connect USB Cable
- Make sure that your PC is authorized (tick always allow, and then OK).
4) Install Terminal Emulator for Android -- NOT Termux.
5) Extract root kit somewhere that you can run adb and fastboot from.
6) Open [2] Command Prompts in the directory containing ADB.EXE.
A) In first window, execute: adb logcat -s dirtysanta
B) In the secxond window, excute: STEP1.BAT
- Wait until prompt returns (several minutes)
C) Window 2: run-as con
D) Window 2: chmod 0777 /storage/emulated/0/*
E) Open Terminal Emulator on phone, enter: applypatch /system/bin/atd /storage/emulated/0/dirtysanta
- Watch window 1. Wait for "Finished. Please run Step 2 now."
F) Window 2: "exit"
- Window 2. "exit" again.
- STEP2.BAT (adb reboot bootloader)
- Phone now shows FASTBOOT MODE
G) STEP3.BAT
- This flashes TWRP and WW 2.0 kernal
- Phone will reboot on completion
7) If phone reboots to Android, in Window 2 execute: adb reboot recovery
- If phone is stuck at secure start-up, pull battery and boot into TWRP (same as factory reset)
8) In TWRP:
A) Settings: UN-Check Enable Screen timeout
B) Format Data (type "yes" to proceed)
C) Wipe Cache & Dalvic Cache
D) Install (flash) h910-10r.zip
E) Install (flash) SuperSU-v2.82.zip
F) Format Data
G) Reboot Phone
Problem Occured:
I seem to have a problem at running this, "run-as con chmod 0777 /storage/emulated/0/*" command.
the error i get is,
xelsa:/ $run-as con
chmod 0777 /storage/emulated/0/*run-as con
run-as: Package 'con' is unknown
Help?
SheMi363 said:
I seem to have a problem at running this, "run-as con chmod 0777 /storage/emulated/0/*" command.
the error i get is,
xelsa:/ $run-as con
chmod 0777 /storage/emulated/0/*run-as con
run-as: Package 'con' is unknown
Help?
Click to expand...
Click to collapse
This "run-as con chmod 0777 /storage/emulated/0/*" actually is a two commands:
- first type "run-as con" and press ENTER
- second type "chmod 0777 /storage/emulated/0/*" and press ENTER
Search in You Tube for "How to Root install TWRP for LG V20 H910 Edition!" from user NewTechBegins. This is very good video tutorial, step by step.
Hello, so nothing happens for me after I enter the code into terminal emulator, what am I missing?
After all these done I'm rebooted to secure start-up where I need to enter password. Tried my 4 digit VIN and didn't work. As suggested earlier in this thread I pulled battery and wipe everything and install Oreo_full_rooted.zip, mk2000, and TWRP 3.3.1-0. It boots up the same to the secure start-up.
I might have done differently in process.
1. H91510e_00_VTR_CA_OP_1205.kdz I downloaded did NOT match MD5 on its download page. Tried twice and it was the same. I went ahead and used it.
2. I ran into "adb server is out of date, killing.." message but was able to download an adbfix and somehow got through
3. STEP1.BAT and the rest of BAT were not accepted in Win10 powershell so I had to enter them by hand and it went smoothly with no error
4. I used twrp 3.3.1-0 as suggested in NewTechBegins' youtube clip
5. Phone boots into scramble messages like shattered warning sign before LG logo appeals. It will eventually enter twrp or secure start-up after some wait. Takes longer than it should, 5 minutes or so.
Wish to stay on Oreo but might try the 10R Rom if I have no other choice.
Please help.
(Secure start-up appeared the first time after step 3 where it was supposedly be a green screen and I can pull battery. It didn't. It went to secure start-up. I pulled battery anyways and rebooted into TWRP, I was asked to enter password again. After a few wrong attempts I was able to bypass it and enter TWRP to proceed with install)
edit: Eventually succeed by not installing TWRP after flashing OREO and MK2000. Rebooted into Secured Start-up again, pull battery and rebooted into FACTORY Recovery and deleted all user data from there. Rebooted and Android setup began.
Note: BE SURE TO FORMAT DATA AGAIN in TWRP after flashing OREO and MK2000 to have a clean start. Would be nice if it was mentioned in this tutorial.
the_R00ter said:
i am making this post because i have an lg v20 running 20h. there was no root guides available, so i decided to root mine using an older guide. it succeeded, but was very hard and time consuming. Being a noob at the time, i was also extremely nervous that i could possibly brick my phone or screw something up. i didn't, and no part of this should brick yours either. ***However - if you do somehow break your device in any way, that is on you. by completing these steps, you assume full responsibility. now that we have that out of the way, lets continue. at the end of this guide, you should have a rooted device with your choice of os (7 or 8 - or even a custom rom if you choose!). you should also have twrp. this guide would not have been possible without users runningnak3d and clsA
**** Also, during this Proccess, Your Phone WILL be wiped clean!!! don't forget to back up photos, videos, etc...*****
don't download any other files than from this guide.
1. download these files (required) https://lg-firmwares.com/downloads-file/4578/H91510e_00_VTR_CA_OP_1205.kdz (for a rootable os that we can flash, - get this also (required) https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 this program is called lg up and has been patched to work with this phone. you will also need this. https://androidfilehost.com/?fid=1322778262903990218. these are the root files and need to be all in the same folder as where lg up is installed. you will also need to have access to fastboot and need to have adb installed. that is pretty easy, give it a google search if you still need help.
if you are running 32 bit, get this https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
this is the OS. get nougat, which has like three less steps (you can't upgrade to oreo on this os once rooted) or scroll down and get the oreo file. nougat (really old version) https://drive.google.com/file/d/1S82HVNt2rAtXgBY499IBJnoCVFnpCf_X/view
Oreo - get this first file, and the ones under it. https://www.androidfilehost.com/?fid=1322778262904015326
***https://androidfilehost.com/?w=files&flid=283977*** You have to have this file if getting oreo. if you chose nougat, then don't get this.
2. Now that you have everything downloaded and installed, put your phone into download mode. (power it off, hold the volume down button and plug in a usb c cable attached to your pc. don't stop holding volume down until you see download mode.)
3. once it is in download mode, open up lg up. select your device, (it should be in standby mode, according to lg up) and click dump (this is a total backup of the phone, you are lucky you know this right now, I didn't when i rooted mine) . it will bring up a file explorer, select where you want it to save to. (I chose my desktop). once you have a folder selected., it will bring up a bunch of options for partitions. click select all and uncheck user data. ****Make SURE that you don't unplug your phone during any part of this process or any other process in this guide, it will permanently brick it. ***** ow that you have selected everything but userdata, click start.
4. once that finishes, you will have made a full backup of your phone in case something goes wrong.
then click the partition DL button and select the h915 v10e kdz file (the file that i said was the rootable os we can flash) (the first file you downloaded). make sure bin file stays checked. then click start. once that finishes, your phone should automatically reboot into an old nougat operating system. then go to settings, enable developer options, and turn on usb debugging. that is easy, if you can't figure it out, google is your friend. now you should have no cellular signal. this is not the permanent ROM.
5. go to the play store and download terminal emulator for android. (once usb debugging has been enabled
then go ahead and go to the folder where you extracted the root files/package. hold shift and right click to open a command windows there or powershell, whatever your pc says. open 2 of those windows. then, in the first one, type, adb logcat -s dirtysanta
****don't close this window.*****
then in the other window, type STEP1.BAT
*****don't close this window.***** It may take a minute, but after a while it will let you type again. once you can, type run-as con
chmod 0777 /storage/emulated/0/*
6. then, pull up the window you used the logcat command in. leave it there so you can watch it
then, on your phone, go to the terminal emulator and type applypatch /system/bin/atd /storage/emulated/0/dirtysanta
once you do that, glance at the logcat window. once it says to run step 2, go to the window where you typed step1.bat. type STEP2.BAT
at this point, your phone should go ahead and reboot and say fastboot mode up at the top. now, go to your window where you typed all the .bats and type STEP3.BAT. wait until your phone reboots and you will see a screen saying that you can;'t use your phone. this is bogus, just ignore it and wait like 10-15 seconds for it to get past that screen. then it will boot that android and you should get a green screen.
Now, quickly, pull the battery from your phone. leave it out for a little while while we prepare the next steps.
If you want oreo, scroll to where it says OREO in capital letters. if you want nougat, scroll to where it says NOUGAT.
NOUGAT
use the file that you downloaded if you selected nougat - it should be a zip. it will be called h910-10r. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the h910 zip file and install it. then go ahead and reboot your phone, you will have a rooted android 7 rom. you will also have signal. then download supersu from the play store and open it to have root.
OREO
use the file that you downloaded if you selected oreo - it should be a zip. it will be called something along the lines of full stock oreo rooted. DO NOT, I REPEAT, DO NOT UNZIP THE FILE. place it on a pre formatted micro sd card. also, go to your root package folder and find the twrp image file and put that on your sd card. then go get the mk200 zip file and also place that on your sd card. then, place the battery and sd card back in your phone. also, unplug the phone. then, hold down the volume down key and hold hold the power key. once you see the lg logo, release the power key and immediately hold the power key again. then, you should get a screen that asks if you want to reset your phone. use your volume keys to navigate and select yes, then again confirm it. then, after letting it reboot, it should go into twrp. once there, go to wipe\and select format data. then type yes to confirm. then, go back to the main screen and click wipe again. go ahead and click advanced and wipe your dalvik cache. once done, go to home screen and click install. select the select storage option down at the bottom and change to sd card. then find the oreo full rooted zip and install it then, install the mk2000 file. after you have done this, click install image and select the twrp. the reason you need to re flash this is because that oreo file re installs the stock recovery. then install the twrp. now reboot your phone. you will have a rooted android 8 rom. you will also have signal. then download a magisk 6.0 manager apk from chrome browser to have root.
IF this worked and your enjoying root give me a thanks.
Click to expand...
Click to collapse
hey reply to me fast is it ok to flash h915 firmware in my h910 10I cuz already hard bricked the previous h918 motherboard cuz I don't know I accidentally flashed h990 firmware plz tell me also is it necessary to flash h915 in h910 to root and TWRP.
Isn't that what it says in the OP?
pakwarrior said:
hey reply to me fast is it ok to flash h915 firmware in my h910 10I ....
Click to expand...
Click to collapse
MaverickNextDoor said:
Isn't that what it says in the OP?
Click to expand...
Click to collapse
Dont try to install h915 instead just try dirty santa method which will install temporary twrp recovery there install h910 20h pre rooted 8.0 rom and install mk2000 v2.2 kernel and install newer version of twrp and you are good to go
No bricking risk and nothing dont try to do corss flashing of h915 its not that accurate also there is model issue in crossflashing instead doing that do dirsty santa and install h910 20h simple
pakwarrior said:
Dont try to install h915 instead just try dirty santa method which will install temporary twrp recovery there install h910 20h pre rooted 8.0 rom and install mk2000 v2.2 kernel and install newer version of twrp and you are good to go
No bricking risk and nothing dont try to do corss flashing of h915 its not that accurate also there is model issue in crossflashing instead doing that do dirsty santa and install h910 20h simple
Click to expand...
Click to collapse
So how do you use dirty santa method for h910 20h? All the guides I've seen want you to crossflash.
jxsilicon9 said:
So how do you use dirty santa method for h910 20h? All the guides I've seen want you to crossflash.
Click to expand...
Click to collapse
I didn't do crossflashing i first installed twrp throught dirty santa which then you have to open from recovery then there is android 8.0 h910 stock rom pre rooted i used or you can use your custom rom to flash then there is an kernel mk2000 file also to flash from twrp after you installed new rom for fixing errors like static screen and like that thats it also if you flash android 8.0 stock of h910 rom you will get a password during booting process just attempt it wrongs for many trys wrotten on it until you see wipe the data prompt and you will factory reset your phone and its ready to go maybe you will be promoted to twrp so you have to factory reset through wipe option ok and you are good to go one thing do it only on h910 not other model there is 0% chance of hard bricking your phone if you did this and no signal problem
Also to understand more go a see my qna with author of this post in this post obviously ok or if you meed more help reply me i will text you
pakwarrior said:
I didn't do crossflashing i first installed twrp throught dirty santa which then you have to open from recovery then there is android 8.0 h910 stock rom pre rooted i used or you can use your custom rom to flash then there is an kernel mk2000 file also to flash from twrp after you installed new rom for fixing errors like static screen and like that thats it also if you flash android 8.0 stock of h910 rom you will get a password during booting process just attempt it wrongs for many trys wrotten on it until you see wipe the data prompt and you will factory reset your phone and its ready to go maybe you will be promoted to twrp so you have to factory reset through wipe option ok and you are good to go one thing do it only on h910 not other model there is 0% chance of hard bricking your phone if you did this and no signal problem
Also to understand more go a see my qna with author of this post in this post obviously ok or if you meed more help reply me i will text you
Click to expand...
Click to collapse
Ok,you know where to get the latest firmware and files? Most dirtysanta tutorials bat have the downgrade added. How do I just add the twrp without the downgrade? Any dirtysanta bat and files?
jxsilicon9 said:
Ok,you know where to get the latest firmware and files? Most dirtysanta tutorials bat have the downgrade added. How do I just add the twrp without the downgrade? Any dirtysanta bat and files?
Click to expand...
Click to collapse
no no need to downgrade anything just find any video which says TWRP installation for LG v20 h910 dirty Santa and flash it but wait I seen in all zip files of dirty Santa there will a final step in that folder called step 3 that file is a batch file just open it in notepad and you will see there is written TWRP for I think us995 just rename it all of them to that name which TWRP in that folder ok for example if the name of the TWRP in dirty Santa folder is twrph910.img
you have to rewrite the same and exact name with .img in that batch file this ting will not tell any YouTuber or in the website cuz, I find it in curiosity and founded that the TWRP name was wrong so I just renamed it in that batch file and it worked before it it wasn't working also download the exact LG v20 h910 TWRP, not any other model TWRP or you will hard brick it man it feels so bad I one time hard bricked my LG next day I bought the device now I just sold it I change the mobo to LG h910 then I did all that root things and then I sell that phone no I have sony xz3 which is way better and have snapdragon 845 octa-core which is the thing I needed in just 135$ I found that it was japan model refurbished but has all things new and original like poled panel and stuff... well if you need more help just don't reply m on XDA you will not get the answer quickly here my social media account
discord: PAKWARRIOR#6115
Facebook: https://www.facebook.com/hafiz.saad.712161/
Instagram: https://www.instagram.com/zero_saad_sixs/
reply me on that I am online all the time but not online on XDA all the time ok
Installed twrp no problem. Had installation issues (error 7) and edited the file. Tried it again and came up with error 1. Saw someone else on xda say to extract the boot img and mount to the recovery partition successfully. Welp, I guess I wasn't so lucky. I can not get into twrp recovery or any recovery and my v20 (910) boots into the Lg android splash screen. My desktop can not see any adb device but it registers a device being plugged in. What's the verdict, soft or hard bricked? Everything was cleared besides twrp prior to error 7 and 1.
Lgv20usr said:
Installed twrp no problem. Had installation issues (error 7) and edited the file. Tried it again and came up with error 1. Saw someone else on xda say to extract the boot img and mount to the recovery partition successfully. Welp, I guess I wasn't so lucky. I can not get into twrp recovery or any recovery and my v20 (910) boots into the Lg android splash screen. My desktop can not see any adb device but it registers a device being plugged in. What's the verdict, soft or hard bricked? Everything was cleared besides twrp prior to error 7 and 1.
Click to expand...
Click to collapse
Re-flash the H91510e_00_VTR_CA_OP_1205.kdz with LG UP. And again.