After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
gaguzman said:
After about 3 weeks of trying everything I could find here on XDA and on Google I stumbled on a possible workaround to get root on KitKat:
I started with:
HTC One dual sim 802w (Chinese Unicom); running stock Chinese Jelly Bean 4.2.2.
Chinese 4.2.2 bootloader unlock, CWM recovery, root, S-off through WWE European 4.4.2 if you're interested:
My initial task upon arrival NIB with Chinese Jelly Bean 4.2.2 was to remove chinese bloatware, install CWM recovery, and root following Marrk Daviid's instructions.
Pounded my head on the wall repeatedly trying to get my Windows 8.1 computer with USB 3.0 to work using assorted usb drivers, installing and removing HTC software and multiple HTC drivers without getting a connection for fastboot or adb to get my id token.
I found tobesedated's thread Guide - Suggestion For S-off On 1.55 HBoot Using Ubuntu , then followed pt's blog posting How to fix the adb no permissions error on Ubuntu Lucid to set the udev/rules.d/51-android.rules file to get adb to work, and I was able to get the bootloader unlocked, run rumrunner S-off, CWM recovery and rooted.
Converting to WWE European ROM 4.2.2 then 4.4.2:
I decided to go European so I could update to a Western KitKat, and used fastboot to flash the WWE ROM from shwetkprabhat's thread Guide--HTC Dual Sim 802w (China Unicom), apply WWE European RUU, OTA & CWM or TWRP ( PN07IMG_M7C_DUG_JB_50_S1_HTC_Europe_2.19.401.1_Radio_1237.21.28.0627_release_326125.zip ) using my old Linux 12.04 (Precise) machine after clearing cache. It installed the stock bootloader also, and I didn't mod or change anything, until I received the two small OTAs and a few hours later, the “big” OTA automatically and OK'd the install for dual sim 4.4.2, and waited until the update completed, and root was GONE.
I then had: WWE international 4.4.2, an unlocked bootloader. S-off, NO root, NO custom recovery,
I (re)installed the modified custom recovery for dual sim (called 802w.img) extracted from HTC_802w_CWM_recovery_6.0.4.8.7z posted with Marrk Daviid's instructions and then installed UPDATE-SuperSU-v194.zip from Chainfire (placed in internal storage) through recovery.
After selecting reboot I selected NO for both options (the defaults) and upon restart I had root. If I repeated the process selecting the fix root option (first question No; second question Yes-Fix root) I lost root. I reinstalled above SuperSU through recovery, answered No to both questions and root was back (Root Checker Pro) and functional (and no tampered flag either).
Do I know why/how it worked? Not a clue, but it did work for me.
This fool has now blindly run where angels fear to tread, I hope this information is helpful to the gurus and cautionary to the brave/foolhardy until confirmed.
Click to expand...
Click to collapse
Alternatively... just install TWRP !!
ascot17 said:
Alternatively... just install TWRP !!
Click to expand...
Click to collapse
Agree it would be much easier and cleaner, if it had worked for me. Touch didn't work after install of 2.7.0.0b, so I gave up on it, and had to reflash CWM to get recovery function and proceed with root. I guess there are still some variations in there that can't be accounted for. I posted this as an interesting observation that might be useful to the devs.
Related
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:1. You should be on SU2-3.3 (Blur 19.6.3) or SU2-3-15 (Blur 19.5.3) rooted and have SafeStrap installed!
2. You have never flashed SU4.21 (Blur 21.11.21) Android version 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
Let's do it and enjoy fully rooted 4.4.4!1 I've done 2 ZIP-files, download one, you prefer:
full rooted stock 4.4.4 SU4.21 with hosts-file ADBLOCK trick.
Download 4.4.4_full here
full rooted Debloated stock 4.4.4 SU4.21, with Touchless Control, Active Display, NFC, Wireless Monitor (inc. Cromecast)
Download 4.4.4_debloated here
Debloated ROM develompent was stopped, due to my smartphone physical damage. Im' sorry.
Regards, Dmitry.
2. Copy downloaded zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select ZIP, you prefer.
5. For locked bootloader: when installation will finish, reboot you device in to bootloader and flash stock kernel from SU4.21
you could take it here or from ZIP-file.
6. After flashing boot.img just reboot you smartphone and enjoy 4.4.4 with root and writable /system
For unlocked bootloader - all done, just reboot your device .
DO NOT PERFORM ANY WIPES!
If something happend with you phone, you can revert to SU2-3-15 (Blur 19.5.3) via RSDLite, get root, install SafeStrap
If you need to clean bloatware, use my Custom Recovery compatibility scripts, could be downloaded in this topic
If you found any features, you need, missing, please, pm me.
i am BL Unlocked, so no need for this for me... but if this is the case and it works then great find my man!!
Given the recent vulnerability published by Dan Rosenberg, I'm hesitant to update to 4.4.4, as it may patch this vulnerability - keeping the bootloader locked indefinitely. I would just keep this in mind if considering this update.
EDIT: Got my information wrong. The date on the OTA is before the date the vulnerability was published. 4.4.4. seems good to go in that case.
has anyone tried this yet?
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
rdenova said:
Thinking about trying this - doing a backup now in Safestrap.
Would like to be able to see this...
"2. You have boot.img from SU4-21, you can download it below "
Where do you see this information? How do I know what version I have in 4.4?
Click to expand...
Click to collapse
Settings>About Phone>Build number
summer.cat said:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
Click to expand...
Click to collapse
This, I see under Build Number.
summer.cat said:
2. You have boot.img from SU4-21, you can download it below
Click to expand...
Click to collapse
This, I do not see any place and is why I asked.
Wait so is this a fully write protection off?
mrwinkle said:
has anyone tried this yet?
Click to expand...
Click to collapse
Looks like this fella did...
http://forum.xda-developers.com/droid-ultra/general/update-19-5-3-obake-t2845903
ceelos218 said:
Wait so is this a fully write protection off?
Click to expand...
Click to collapse
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
summer.cat said:
sertainly)
PS: i've read many questions about build versions and firmware versions, so if you couldn't understand which firmware you have, follow this:
First update 4.4 - SU2.3-15 (suits for gaining root and wp off by @beaups wbegone)
Second update 4.4 - SU2.3-3
Latest update 4.4.4 - SU4.21
hope, it will be helpfull.
Click to expand...
Click to collapse
Instead of using the SU for identifying builds, you should probably the system version number as that is more frequently used. 19.5.3, 19.6.3, 21.11.21
summer.cat said:
Hello guys!
I've found the way for getting Android 4.4.4 rooted without write-protection on root filesystem
Original post on 4pda.ru Warning! Russian language detected!)
So, this is small and very simple instruction:
Preparation:
1. You should be on SU2-3.3 rooted and have SafeStrap installed!
You have never flashed 4.4.4 via RSDLite and you have never taken OTA with 4.4.4!!!
2. You have downloaded boot.img from SU4-21
can be downloaded here https://drive.google.com/file/d/0B_kAWkXp3XK9VmpnSGNaVUZtTDQ/edit?usp=sharing
Let's do it!
1. Download 4.4.4_rooted.zip here
https://drive.google.com/file/d/0B_kAWkXp3XK9amVwNjJKUjk4QmM/edit?usp=sharing
2. Copy 4.4.4_rooted.zip in to device storage.
3. Reboot to SafeStrap
4. Select Insall button, select 4.4.4_rooted.zip
5. After flashing reboot to bootloader and flash via fastboot tools boot.img file from point 2 above
Code:
fastboot flash boot boot.img
6. Reboot after flashing boot.img
7. Enjoy 4.4.4 with root and writable /system
If something happend with you phone, you can revert to SU2-3.15 via RSDLite, get root, install SafeStrap
PS: You flashing clean from bloatware system! As clean as possible, but everything works fine!
Click to expand...
Click to collapse
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
thebenshow said:
....So, does this mean I can finally install some ROMs on my retail Moto? I came from a bootloader-locked 4.4 install with root.
Click to expand...
Click to collapse
i mean, you can use 4.4.4 without write protection
I'm about to try this out to n my xt1080 on 4.4.4... I will update when I'm finished
Can this be used for the droid mini?
I should have read closer I got too excited about about getting root... I already took 4.4.4 OTA... I need root
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
BriCo84 said:
Am I the only one waiting for clear confirmation from someone who was rooted on 19.6.3 that did the steps in this thread that they are now on 4.4.4 with root and write protection permanently off?
Click to expand...
Click to collapse
I am too lol. Been refreshing this thread ever since I ran across it.
Anyone try this?
He is talking about using safestrap on a 4.4 ROM. If you EVER updated to 4.4.4, this will never work for you as you will never be able to disable write-protect to be able to install safestrap.
OP: perhaps you should make this more clear in the original post. Specifically that it will not work if you ever updated to 4.4.4 (Actually, the OP DOES say this...), AND that you're not actually running the 4.4.4 rom, but rather a 4.4.4 stock-based, safestrap-compatible ROM. If you are using this successfully, your bootloader AND your partition table are still on 4.4, which allows you to retain WP-off, safestrap, and root.
But yeah...this will absolutely work if you never updated past 4.4. We have known about this for a long time...I'm surprised a guide was just recently put out about this.
Ok, assuming your bootloader is already unlocked, the easiest way to root your device if you want to keep the stock firmware (including recovery partition) is to flash a special modified boot.img called "Superboot r2" that installs su binaries and SuperSU on your device. It's nothing new, this workaround was originally developed by PaulOBrien, founder of MoDaCo, several months ago. People started to complain since 4.4.2 release saying this method doesn't work anymore... false! They just don't know the trick! I successfully rooted even the 4.4.4:good:
You just need to:
1) have your stock or official firmware flashed
2) clear cache partition through recovery before to flash
3) flash boot.superboot.img using the standard fastboot, not the mfastboot
4) your phone will crash with a disappearing android logo, just press the power button for few second to reboot it
5) if you don't find SuperSu in your drawer just try again
This method doesn't compromises your phone from receive OTA updates, fully tested.
I already re-packed it for you, just run the batch file.
DOWNLOAD
All credits to PaulOBrien.
Clarification
So all one needs to do is run the batch file if the bootloader is already unlocked?
chaserblack said:
So all one needs to do is run the batch file if the bootloader is already unlocked?
Click to expand...
Click to collapse
Yeah, clear cache and run the batch while you're in fasboot mode.:good:
Worked.
1st try, thanks man.
A friend of mine wanted to change the stock rom on his old tmobile MyTouch 4G to CM7.2
It is currently running the latest 2.3.4 (hboot_0.89.0007, radio 12.62.60.27_26.13.04.19), I unlocked the phone following the steps from HTC Dev website. And they explained that unlocking is enough to flash custom rom since it enabled write access to recovery, system and boot http://www.htcdev.com/bootloader/about_unlock_process.
I was able to flash and run both TWRP and CWM (twrp2.2.2.1-glacier-recovery & recovery-clockwork-touch-5.8.1.0-glacier) adn used them to flash CM7.2 stable and the latest nightly and some other custom ROMs i found on the developers forum at XDA, however, not of them do boot. The phone will get stock at the first screen showing Tmobile and myTouch 4g logo.
I followed many threads/steps that recommended downgrading to stock froyo first to turn security off (S-OFF) but it won't let me since it is older version, then some says to downgrade the radio first, but that is also not possible with S-ON and i get signature error. i tried doing it from the sd-card using the file name "PD15IMG.zip" for the stock rom but didn't work neither from the fastboot rebootRUU thingy.
From the recovery i wiped every thing even system, then checked it to make sure it is empty, flashed CM7.2 and mounted system and there are the files as they should be but it won't boot, and "adb devices" won't show anything so i cannot see the log. which means it didn't even start.
Am I missing something trivial?
* BTW, i had to lock the bootloader again to flash the stock 2.3.4 back, but I have the unlock token "Unlock_code.bin" and I can unlock it again if someone knows the answer to this problem
Okay so I have a desire 816 dual SIM A5 DUG S-on model, and wanted to update it to LL then MM in order to use external storage as internal to expand storage.
Tried the OTA update but failed (red triangle appears halfway through the process)
So I decided to try and flash custom Rom's; I unlocked boot loader and installed custom recovery then flashed this Rom:
https://forum.xda-developers.com/desire-816/general/official-rom-desire-816-dual-sim-a5dug-t3552060
After several attempts (both with CWM & TWRP) I got it running, but WiFi wasn't working. Thankfully I made a backup of my stock kitkat before flashing, so I restored it.
After some research here, I found that I needed the LL firmware in order for the WiFi to function, and cannot update to MM directly from kitkat...
Please help, what should I do?
I remember reading something about downloading the OTA package, unzip it and extract firmware.zip then flash it, which should solve the problem. Is that right?
Thanks
xyz
you can relock bootloader and run a RUU with your region or you must s-off, change to super ID and run any RUU. Good luck
link some RUU : gsmhelpful.com/2015/05/htc-desire-816-official-stock-roms.html