Database Info

[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Goodbye Stranger - Upd. 02.25.11

I am sad to say the time has come to retire this post....Now before you get all panicky and ****, just sit your **** down, take your adderall and relax, damn antsy ass people. Anywho, with people our there like xHausx and others that have automated all of this there really isnt a need for me to keep this updated. I will keep the post here for archival purposes but, I will not be updating it, any further. I may pop into the thread here and there but probably not. I would like to thank all those that helped and supported me during this threads run. With out you we would still be stuck.
In the mean time if your looking to root your phone, check out xHausx's thread
here: http://forum.xda-developers.com/showthread.php?t=838448
And no I still dont recommend Clockwork or Unrevoked.
Till next time...Super Tramp - Goodbye Stranger
Archive of the guide as of 2/14/11
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
======================================================
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
Click to expand...
Click to collapse
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
Click to expand...
Click to collapse
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
Click to expand...
Click to collapse
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
Click to expand...
Click to collapse
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
Click to expand...
Click to collapse
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
Click to expand...
Click to collapse
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
Click to expand...
Click to collapse
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
Click to expand...
Click to collapse
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
================================================
UNROOT GUIDE
NOTE: This will erase all data on the phone. (Will not erase data on the SDCard)
1) If your on Hboot 2.10 Download the PC36IMG.zip Here. If your on Hboot 2.02 Download the PC36IMG.zip here then Unrevoked s-on here rename the pc36img file to pc36img.zip copy that and the unrevoked s-on tool to the root of your sd
2) Power your off. Power the Phone back on into the boot loader by holding power and vol-down until your presented with a white screen.
3) It will scan for the pc36img.zip. Select no to flash. Select recovery from the menu. Once in recovery choose flash zip from the menu, and select unrevoked forever s-on.
4) When its done flashing select reboot from the menu.
5) From here either run the official ruu or boot back into the boot loader (see step 2). When it scans and ask you to flash the pc36img.zip select yes then yes to reboot.
Click to expand...
Click to collapse

FAQ
FAQ:
Your here cause something went wrong right? Ok thats fine. This list isnt extensive but its here to provide quick answers to some weird or common questions. New questions and problems are added to the bottom.
Q: Will this downgrade my hboot
A: No. I used to have an hboot downgrade but it was bricking peoples phones. However is you want to risk bricking your device, visit this thread here. I I advise against this. This bricked alot of phones which is why I pulled it.
Q: How do I install the Hboot Drivers
A: Check this here
Q: I get "error: more than one device and emulator"
A: kill the adb.exe tasks in task manager or reboot your computer
Q: Step #9 my phone does read the PC36IMg.zip
A: If you renamed the zip file make sure it doesn't say PC36IMG.zip in the name remember that xp and up on windows doesn't show the file ext by default so if you see PC36IMG.zip chances are its named PC36IMG.zip.zip
Q: Why cant I use Clockwork Recovery
A: At the moment its not coded for the new partitions. Just read the first few pages of this thread or check this here
Q: What Hardware does this work for
A: All currently known hardware 0001-0004
Q: What Hboot's does this work for
A: It was built for 2.02 and 2.10 however it will work for all version its just there are easier ways for those
Q: I think I messed up can I just start over.
A: Yes. Its recommended if you want to start over run the official ruu.
Q: This is very complicated
A: It is...thats why there is instructions
Q: Will this erase my data
A: Yes but not from the SDCARD
Q: Can I deleted the files off my SDCARD when done
A: Yes, except for RSA_OEM.KEY and WIMAX.IMG
Q: I get permission denied or device offline when trying to step 10
A: Check here or here or here this might work for you
Q: I used clockwork it seems to work fine.
A: It might but considering the partition information is not correct. You may have just over wrote your wimax keys and broke 4G. Have fun with that like this poor guy here
Q: This uses unrevoked in one of its steps? Explain?
A: There have been some concerns that this uses unrevoked-forever in one of its steps. As far as we know that Unrevoked 3 (not to be conufused with unrevoked-forever) is causing some radio issues with hardware in general and new hardware. Unrevoked-forever does not appear to bork the radio like unrevoked 3 does. This is apparent by the many success stories. However Unrevoked3 could very well possibly destroy your radio/wimax/brick if used.
Q: I get device not found
A: Install the drivers for your phone, (Unrevoked, ADB)
Q: Camera doesnt work after doing this
A: Flash a new rom thats current. Like SteelRom, Fresh, Stock Rooted. The issue here is the Hardware is different. NO CUSTOM KERNELS
A2: Reports say they changed the camera provider/hardware. And the drivers are different! Using a rom based off the latest release and kernel should fix it As Discussed here and here and here
Q: When I go to recovery. I get a red triangle.
A: See Step 10
Q: This doesnt work!
A: Yes it does if you follow the directions, Unless some other bull**** decided to popup!
Q: CM6.x doesnt work
A: See Question 7....Nothing I can do about that if the kernel doesnt support your camera/device.
Q: My phone boot loops now...You broke my ****!
A: I didnt break your ****. You broke your own ****! Its not broken so chill out (well it might be but probably not). What rom did you flash? Did you flash a custom kernel? Did your rom come with a custom kernel? I bet your using a custom kernel. Try a rom like Steel Rom, Sprint Lovers
Q: How do I back up my RSA Keys
A: Check here for the latest up to date information. Or run this command from the shell
cat /dev/mtd/mtd0 > /sdcard/wimax.img
Click to expand...
Click to collapse
Q: My 4g Doesnt work
A: Was it broken prior to the s-off, what steps did you take. Are you running AOSP ROM or Another kernel?, Did you try a different rom? What version is your phone? Do you have SwitchPro Widget installed? (uninstall it), Did you try to run unrevoked3 prior to this? After flashing the radios and stock kernel based rom did you do a data and prl update? Does the mac behind your battery match whats in about phone (4g has to be on to see mac) Also try the tree.xml fix posted
adb shell
ls /data/misc/wimax/
look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)
mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old
4. Start 4G may not connect
5. Do a prl/profile update
6. Power off the phone and power it back on. Try it
7. PRL/Profile. Try it
Click to expand...
Click to collapse
Q: 4G is still broke.
A: Check your RSA keys
adb shell
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
#
It should look just like the above
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
Q: OK I think My Keys are tossed. We made a backup right? So how do I restore it?
A: This post or post should do it for you
Q: My Phone says its not rooted.
A: If you have s-off your rooted. Simple as that. Try a different rom if you want. The second pc36img.zip file you flashed is Sprint Lovers and is a very nice rooted rom.
Q: When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
A: The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Q: Can you tell me what this does?
A: Read the guide? Basically your downgrading the phone, so you can flash unrevoked because htc "comically fixed" the phone. Then your re upgrading the phone back to shipping radios, system, pri, nv, kernel...all the while with keeping s-off
Q: How did you get to be so cool
A: If you have it, you don’t need it. If you need it, you don’t have it. If you have it, you need more of it. If you have more of it, you don’t need less of it. You need it to get it. And you certainly need it to get more of it. But if you already don’t have any of it to begin with, you can’t get any of it to get started. Which means you really have no idea how to get it in the first place, do you? You can share it, sure. You can even stockpile it if you like. But you can’t fake it. Wanting it, needing it, wishing for it. The point is, if you’ve never had any of it, ever, people just seem to know.
Q: Do you really own a vette?
A: Yes, and a backpack with jets!
Q: Whats with you and the dots ...
A: ...
Q: Your Kind of an Cocky Asshole
A: Yea...I Get that. Oh well. I cant fix stupid or ignorant.

What is the point of getting the new HBoot?

sorry, wrong question

abiezer said:
What is the point of getting the new HBoot?
Click to expand...
Click to collapse
there is no point in getting a new hboot....this tool is for those that have phones with the new hboot....that unrevoked wont work on.
this is not the new hboot

Oh I see so this is basically for people who couldn't root to be able to root. Got it. Thanks.

Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?

shepkc said:
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
Click to expand...
Click to collapse
its included in the script it tells you how to do it.

update failed, said main version is older...

its working for some but not others...i dont know why the main version is older thing...

i think we have ironed out the mainversion deal...
looking into it now.

Should be fixed now...so try it I guess.

v2
Looks like your V2 is working, I didn't run into the main version failure. Flashing as I type, I hope slyder got this to work.

Confirmed, V2 works
alright brotha your v2 of the batch file works like a charm. S-OFF confirmed on HBOOT 2.02. Thanks to everyone involved in making this happen.

Outstanding
Sent from my PC36100 using XDA App

On a brand new fresh 2.2 out of the box running HBOOT 2.02 I got "Main version is older". Are there any prerequisites i have to run to get this to work? I just reinstalled 2.2 and ran the script and got main version is older.

did you download version 2
do you have gtalk

I did download v2, and I do have gtalk.

b0r0b said:
I did download v2, and I do have gtalk.
Click to expand...
Click to collapse
you got PM....i want to know exactly whats happening.

Main version is older
I have also tried with V2 and get the "Main version is older".
Baseband
2.15.00.09.01
Software
3.30.651.2
PRL
60671

EVO Design root method

I just wanted to put this out for people looking for a root method with the Design. The Super Tool hasn't worked for me when using the design. I have figured out a way that has work more than a few times now. Here is exactly what I've done to get Unlock Bootloader and able to flash a recovery.
1. Use HTC Unlocker at htcdev.com to unlock bootloader. Must have all files instaled. They will have all the files at htcdev. Follow instructions to the end and you have unlocked your bootloader.
2.http://forum.xda-developers.com/showthread.php?t=1239821 Download the su file and the recovery file that are below the YouTube video.
3. Put the two file into your sdk tool folder where you adb and fastboot.
4. Open a command prompt at that folder. Shift right click on folder and you can open a command prompt right where you need it.
5. in command prompt type "adb push recovery.img /sdcard/"
"adb push su-2.3.6.3.zip /sdcard/" with out quotes.
6. Get to fastboot using "adb reboot bootloader" in command prompt or do a battery pull, hold power and down volume then have your phone connected at fastboot where it should say fastboot usb.
7. Type "fastboot flash recovery recovery.img"
8. Once its finished unplug and hit power button while fastboot is highlighted.
9. Now you see you can use the volume down button to navigate down to recovery. When you are on it hit power button and it will boot into recovery.
9.5 I suggest selecting backup restore and making a back up of your system at this point. I have seen that in using this method if you ever let the phone completely die you can get a problem or two and it is nice to have a backup that is fresh and clean that you can start over with. If this ever does happen to you just navigated yourself to recovery like you are now and when you click backup/restore you can restore your system.
10. Using volume key navigate to instal from zip. "install zip" and then pick the "su-2.3.6.3.zip" Now superuser is installed
11. Navigate back and and reboot to system.
YEA.
This is pretty simpled down explanation but if you get stuck it usually can get worked out. I haven't seen much for ROMs for this phone yet but at least you get superuser and all the goodies that come from having that, Tether anyone, not to mention all the bloat ware you can remover with rootuninstaller from the market. Just dont use rootuninstaller to remove critical like sprintzone and so on.
Ive had good luck using this method and if anyone is developing a rom for it that would be awesome. You dont have S-off so you must do all your flashing using the skilled know how that TWRP offers using command prompts to flash img. and so on but it is not bad and it gets easier and easier to do the more you get hooked on flashing but like I said there isnt much out yet for this phone.
Hope this helps some of you.
Much Love and Many shout outs to TWRP and everyone over there who are just killing it.

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer

Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either

Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.

j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.

Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked

Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"

rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed

Sorry,
I posted before your edit showed up--

Glad to hear.

steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

Droid ultra kitkat update not installing

Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!

response
droidusr2014 said:
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
Click to expand...
Click to collapse
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.

Thanks
Thank you so much currently I can't try out your method but it looks like it could work THANK YOU SO MUCH I'm going to try tonight and I'll tell you how it went. I really don't mind factory resetting as long as it saves my phone im all right thanks again :laugh:!!!
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse

Will factory reset erase root??
One more thing I actually am currently rooted by using RockMyMoto so I think that is why the update didn't work but 1 last question when I factory reset will it erase root? I don't mind if it erases root but my main concern is that if root somehow stays I won't be able to do the software update.
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse

Tried the method and it worked!!
I tried what you said and it worked perfectly but it still remembers my Wifi, wallpaper and all it showed the setup screen and I set it up so hopefully im in the clear the phone is downloading the update right now.

It will not allow the update and you will still end in boot loop. Need to remove root first: http://forum.xda-developers.com/showthread.php?t=2577029

Question [SOLVED] "Pixel Is Starting"

Soft-Bricked my phone this morning flashing a Substratum Theme. Don't ask, I don't know why but it did.
Did a factory reset, Pixel Flasher, set up Magisk, rebooted - got Pixel is Starting. - couldn't get out of it and this was AFTER I recopied all my stuff back over form the last update I had on my Computer and Swift/Google Backups.
Factory reset, same thing happened while doing a reboot at some point int he process.
THIRD Factory reset, got everything done, restored, up and running, just did a reboot and it's back.WTF?? And how do I get out if this?

How are you factory resetting the device?
Also, perhaps something that you are restoring is causing the boot issue. You shouldn't restore data from Swift Backup immediately after fully re-imaging your phone - if that is part of what you are doing.

NippleSauce said:
How are you factory resetting the device?
Also, perhaps something that you are restoring is causing the boot issue. You shouldn't restore data from Swift Backup immediately after fully re-imaging your phone - if that is part of what you are doing.
Click to expand...
Click to collapse
No, I’m doing the factory reset in recovery. Then when the phone booths up just going through the bare minimum of settings to get to the home screen so I can flash the newest update and get routed. Since it’s a factory update and I need to disable verity and verification I have to wipe again anyway and then I go through the whole set up process, let google restore all my apps and stuff and then I use swift back up to restore my apps and data.
I wonder if when I do my back up from Swift I should just do data instead of letting the apps overwrite them selves

Searching online it looks like I can still connect with ADB. I’ll see if I can use the flashing tool and maybe re-flash without wiping

Ahh, gotcha. You can try what you said but I would also suggest re-imaging your phone with the matching factory image that you are currently running. You can do a proper, full re-image through recovery without wiping your phone.

NippleSauce said:
Ahh, gotcha. You can try what you said but I would also suggest re-imaging your phone with the matching factory image that you are currently running. You can do a proper, full re-image through recovery without wiping your phone.
Click to expand...
Click to collapse
How do I do that?

HipKat said:
How do I do that?
Click to expand...
Click to collapse
A lot of commands lol. I will update this comment in just a moment once I head over to my desktop. Typing this out on my phone would be a real disaster, haha.
Alrighty! Here is that update:
1. Ensure that you have the latest version of platform-tools somewhere on your hard drive. Also ensure that your phone has ADB enabled - which you said yours has enabled already - so you should be all good there.
2. Download the correct, most updated factory image here:
--> https://developers.google.com/android/images
3. Extract the contents of the factory image into your platform-tools folder. If you want to root, also be sure to extract the init_boot.img from image.zip file that is inside of the main factory image zip file.
4. Right-click and edit the flash-all.bat file and remove the "-w" near the bottom of the document. "-w" means "wipe". Make sure to save the document after making this change.
5. Copy the directory of your platform-tools folder.
6. Open CMD as an administrator.
7. In CMD, change directories to your platform-tools folder. The command is:
cd DirectoryLocationYouCopiedGoesHere
8. Connect your phone to your PC over USB.
9. In CMD once it is navigated to the platform-tools folder (which should also contain the extracted factory image files at this point), type the following commands:
adb reboot-bootloader
**This will reboot your phone into the bootloader**
flash-all
**This will run the flash-all.bat script which will re-image your phone with the downloaded factory image. It will not wipe your phone if you remembered to remove the "-w" line as mentioned above. Also, DO NOT interact with your phone while this command is running. It will automatically boot itself once it is done - which can take up to 5-10 minutes.
10. You can probably do the rest on your own from this point. But the basis of what comes next would be installing Magisk, copying the init_boot.img over to your phone, patching it in Magisk, copying the patched init_boot.img back over to your computer, booting your phone into recovery mode once again (via CMD) and then running the following command in CMD as admin:
fastboot flash init_boot MagiskPatchedInitBootFileNameGoesHere.img
**This will flash the patched init_boot.img file**
Then use this command:
fastboot reboot
**That will take your phone out of recovery and cause it to boot normally**.
I actually have to run to a birthday party right now so I can't write any more specific details. If you don't feel comfortable doing this all, please let me know. If that's the case, I'll make a video showing how to do this tomorrow or something, haha.

NippleSauce said:
A lot of commands lol. I will update this comment in just a moment once I head over to my desktop. Typing this out on my phone would be a real disaster, haha.
Click to expand...
Click to collapse
Lol,I’m hip

NippleSauce said:
A lot of commands lol. I will update this comment in just a moment once I head over to my desktop. Typing this out on my phone would be a real disaster, haha.
Alrighty! Here is that update:
1. Ensure that you have the latest version of platform-tools somewhere on your hard drive. Also ensure that your phone has ADB enabled - which you said yours has enabled already - so you should be all good there.
2. Download the correct, most updated factory image here:
--> https://developers.google.com/android/images
3. Extract the contents of the factory image into your platform-tools folder. If you want to root, also be sure to extract the init_boot.img from image.zip file that is inside of the main factory image zip file.
4. Right-click and edit the flash-all.bat file and remove the "-w" near the bottom of the document. "-w" means "wipe". Make sure to save the document after making this change.
5. Copy the directory of your platform-tools folder.
6. Open CMD as an administrator.
7. In CMD, change directories to your platform-tools folder. The command is:
cd DirectoryLocationYouCopiedGoesHere
8. Connect your phone to your PC over USB.
9. In CMD once it is navigated to the platform-tools folder (which should also contain the extracted factory image files at this point), type the following commands:
adb reboot-bootloader
**This will reboot your phone into the bootloader**
flash-all
**This will run the flash-all.bat script which will re-image your phone with the downloaded factory image. It will not wipe your phone if you remembered to remove the "-w" line as mentioned above. Also, DO NOT interact with your phone while this command is running. It will automatically boot itself once it is done - which can take up to 5-10 minutes.
10. You can probably do the rest on your own from this point. But the basis of what comes next would be installing Magisk, copying the init_boot.img over to your phone, patching it in Magisk, copying the patched init_boot.img back over to your computer, booting your phone into recovery mode once again (via CMD) and then running the following command in CMD as admin:
fastboot flash init_boot MagiskPatchedInitBootFileNameGoesHere.img
**This will flash the patched init_boot.img file**
Then use this command:
fastboot reboot
**That will take your phone out of recovery and cause it to boot normally**.
I actually have to run to a birthday party right now so I can't write any more specific details. If you don't feel comfortable doing this all, please let me know. If that's the case, I'll make a video showing how to do this tomorrow or something, haha.
Click to expand...
Click to collapse
Flashing now. For future reference, in CMD, you need to run adb kill-server, then adb-devices before rebooting to bootloader (I'm not a TOTAL ADB noob lol). In my case, none were found so I just disconnected and reconnected the USB from the phone and it found it.
Also, Pixel Flasher was not able to work in Recovery or in the Pixel Is Starting state, which shows up on the tool as ADB - probably not rooted.
I'll update when it's done

Grrrr, no luck. Right back to Pixel is Starting.
Back to the hard way

HipKat said:
Grrrr, no luck. Right back to Pixel is Starting.
Back to the hard way
Click to expand...
Click to collapse
When you're on this screen, normally it's a launcher thing. Have you flashed any mods for launchers?
If you're still able to access your settings through the notification bar, you should be able to go to apps in your settings and open the Play Store to temporarily download another launcher. This will at least allow you to get some usage from your phone.

Curiousn00b said:
When you're on this screen, normally it's a launcher thing. Have you flashed any mods for launchers?
If you're still able to access your settings through the notification bar, you should be able to go to apps in your settings and open the Play Store to temporarily download another launcher. This will at least allow you to get some usage from your phone.
Click to expand...
Click to collapse
It's an encryption thing with the unlock method, pin, fingerprint, etc form everything I've read, and I read a lot and no one has been able to get past it without a wipe. I've used Nova Pro with the same settings over many devices
You can't get to apps. You can get to settings but if you select Apps and try to open an app, the only options are Uninstall and Force Stop

It's in the data on the Swift Restore. Everything is good after restoring Google Backup, and Swift missing Apps. I restored only data on system apps and user apps and the next reboot gave me this error. I wonder if I should NOT restore system data... I almost didn't just to see what happened, but I would have anyway

Confirmed, not restoring System Data was the fix. Funny, I have restored Sys Data Twice before today....

HipKat said:
Flashing now. For future reference, in CMD, you need to run adb kill-server, then adb-devices before rebooting to bootloader (I'm not a TOTAL ADB noob lol). In my case, none were found so I just disconnected and reconnected the USB from the phone and it found it.
Click to expand...
Click to collapse
In adb you do not have to run those commands. Adb devices would just let you check if an adb enabled device is connected. Adb kill-server only needs to be run if you had already used adb commands with your connected device, disconnected it and then reconnected it. That would kill the originally established and utilized adb connection which would then allow you to establish another one - which I suppose I should have mentioned considering you had tried things over adb prior to my comment, haha. My apologies.
But regardless, I'm glad that you got it working again! So it was that Swift Backup restore after all? That is good to know. Awesome stuff.

NippleSauce said:
In adb you do not have to run those commands. Adb devices would just let you check if an adb enabled device is connected. Adb kill-server only needs to be run if you had already used adb commands with your connected device, disconnected it and then reconnected it. That would kill the originally established and utilized adb connection which would then allow you to establish another one - which I suppose I should have mentioned considering you had tried things over adb prior to my comment, haha. My apologies.
But regardless, I'm glad that you got it working again! So it was that Swift Backup restore after all? That is good to know. Awesome stuff.
Click to expand...
Click to collapse
Yeah, I should know better than to restore old System Data. It used to be a no-no, but the first 2 times I did a restore after first rooting and then a wipe a few weeks ago, I hadn't even thought of it. That's what 78 years away from the Rooting game does to you.
As for those commands, ADB-Devices came back with nothing till I did kill-server. Probably just something on my end