AS MY EVITA IS CURRENTLY BOOTLOADER LOCKED, THIS SUPERBOOT IS FOR TEST PURPOSES ONLY. USE AT YOUR OWN RISK!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r2 - DOWNLOAD - MD5: 39a02275706d4b034c3c185b5b9b1a82
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
Ensure your bootloader is unlocked using the htcdev unlock process
Download the Superboot zip file above and extract to a directory
Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
WINDOWS - double click 'install-superboot-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
P
PS Details on how to donate should you wish to do so are in the download topic at MoDaCo.
have a mirror? ...file not found.
JSLEnterprises said:
have a mirror? ...file not found.
Click to expand...
Click to collapse
i just tried it. works for me
edit: nope, didn't work upon actually trying to grab the file
edit: thanks Paul!
Small typo, fixed now.
P
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)
now care to share your repack methods?
I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
Superboot should automatically install the Superuser APK in /system/app?
P
JSLEnterprises said:
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)
now care to share your repack methods?
I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
Click to expand...
Click to collapse
The folder disappears on the next reboot.
P
paulobrien said:
Superboot should automatically install the Superuser APK in /system/app?
P
Click to expand...
Click to collapse
It did, but didnt show up on first boot. wasnt in the appdrawer, but was in the directory.
either a manual reinstall, or a hot restart fixes it. (Dont know why it didnt show up in the app drawer initially)
Just realised the SU binary is slightly out of date on this superboot, uploading new version now.
P
Updated with latest SuperSU.
P
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
JSLEnterprises said:
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse
I'm working on one today...
JSLEnterprises said:
time to start up on a rom. ;D
... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
Click to expand...
Click to collapse
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)
... These are just preliminary comparisons.
If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.
Steve
Click to expand...
Click to collapse
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
Click to expand...
Click to collapse
Thanks. I will check the partitions info on that and use for build.
I am going to start build now. Will let you know how it goes. I should be getting my ATT One X tomorrow, so I will test (unless there are some brave souls out there...).
Steve
danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.
~dan
Click to expand...
Click to collapse
Lte toggle = services.jar (/system/framework) & settings.apk (/system/app)
also, deleting TetheringGuard.apk from the AT&T unit will enable the tethering ability.
JSLEnterprises said:
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)
... These are just preliminary comparisons.
If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
Click to expand...
Click to collapse
Thanks. This doesn't look like anything that would affect boot.img, good to know. Hope ATT won't mind if I brick my device tomorrow, lol.
You guys are doing a fantastic job for both Rogers and AT&T users! Thanks!
Great job, guys!
I'm at work and can't install the USB drivers to operate my device in the Bootloader/Fastboot but you can be damned sure that I'm eager to go home and flash this!!! Been waiting so impatiently for root and you guys did the trick. Thanks so much
Related
Ok so this issue has now been fixed, download the following file and place it on your SD card, start your phone up with, volume down + power and follow the instructions.
PB99IMG.zip
Thanks to everybody who tweeted this in.
o.o adamg - not really! Why did you do that?
That could not mean the end of opendesire and your sense roms could it?
Adam you should have known better, but still look at root method now on my gf's desire will post when I get root
ohh crap i was holding out hoping you'd have an update. hope someone figures it out for your sake if any
I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
I will still be releasing, I have people on the team who test the roms and report the bug errors for me to fix
Click to expand...
Click to collapse
If need more help testing email me I'm global mod on villainrom.co.uk
Email [email protected]
Lots of experience
Cheers
Mike
any chance of getting a full root while were at it? it would be awesome to use metamorph
i'm sorry to hear that adam,
but i seriously lol ...... so sorry.
i love your roms.
i got the same problem
http://htcpedia.com/forum/showthread.php?t=2934
Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
Not possible because you need root to place the flash-executable and the img into a read only directory.
Tried it too but you definitly need a method to execute some lines of code. adb push to /data is not possible because:
- adb is not working
- you can't get root to remount /data rw instead of ro.
Before i flash anything... How did you get there?? Flashed new 2.2 ROM? Or RADIO? or????
after we upgraded the official version throw htc live update
And this?
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Prema999 said:
http://htcpedia.com/forum/showthread.php?t=2934
Click to expand...
Click to collapse
twicejr said:
Isn't it possible to hex edit the version string to trick it into believing it is a newer version?
Click to expand...
Click to collapse
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
wiggy2k said:
that's not so easy, i think it is nearly impossible, you can't hex edit something on a read only phone (if we could edit sth we could flash the 0.80 hboot back), and hex-editing the whole RUU is - as i think - because of encryption and checksum checks etc impossible, too. we have to inject the flash software and the image - and this is impossible without rw / root.
Click to expand...
Click to collapse
damn you htc
madman_cro said:
damn you htc
Click to expand...
Click to collapse
I think there WILL be a root-hack. it is just a cat and mouse game, htc is now in front, but the dev scene will be back soon with successful rooting i think. so dont fear and be patient
the only hardware which was not exploit-hacked for now is the playstation 3. (I hate not having otherOS anymore ...)
yes should they come with a new release because all the new htc devices will come with 0.92 at least
Adam, get on Freenode IRC and query me.
There's a few things I'd like to test with you
(IRC nick = IEF)
same problem impossible to downagrad hboot or install "RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed"
I need someone with the xoom 3G with 3.1 to run this command in an adb shell and post it. I flashed an older boot.img before making a backup
cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Thanks in advance.
I think it's in the update.zip package, as bootloader.bin
Bauxite said:
I think it's in the update.zip package, as bootloader.bin
Click to expand...
Click to collapse
NO, that's the bootloader. The boot.img is the kernel.
Bauxite said:
I think it's in the update.zip package, as bootloader.bin
Click to expand...
Click to collapse
I saw that in there but I decided to flash back to 3.0.1 without wiping my data (the apps really don't like that) and I'm reupdating to 3.1 now. I'll post the boot file when I'm back up and running in case someone else needs it.
Well I forgot I lost root in the manual update so I can't extract it yet. At least you can revert to 3.0.1 if you make the mistake I did and reflash 3.1.
One problem
I get Permission Denied, since I lost root when I applied the 3.1 update.
I was curious, about to try flashing koush's rootboot.img and getting root back; however I wanted a backup of the 3.1 boot.img as well, and only found the boot.img.p in the update and I'm not quite sure if that will do me any good.
At any rate, hope someone can run that command for you (and me)
tekuru said:
I get Permission Denied, since I lost root when I applied the 3.1 update.
I was curious, about to try flashing koush's rootboot.img and getting root back; however I wanted a backup of the 3.1 boot.img as well, and only found the boot.img.p in the update and I'm not quite sure if that will do me any good.
At any rate, hope someone can run that command for you (and me)
Click to expand...
Click to collapse
The boot.img.p is a binary patch that's applied to the original boot. There's an applypatch tool in the Android sources that can apply binary patches, so if you have the stock boot from the previous version and can apply the patch, you have a 3.1 boot.img without doing anything.
tekuru said:
I get Permission Denied, since I lost root when I applied the 3.1 update.
I was curious, about to try flashing koush's rootboot.img and getting root back; however I wanted a backup of the 3.1 boot.img as well, and only found the boot.img.p in the update and I'm not quite sure if that will do me any good.
At any rate, hope someone can run that command for you (and me)
Click to expand...
Click to collapse
Don't flash rootboot, that is what I did that screwed me up. We'll have to wait for another root img to flash that is updated for 3.1.
Excellent, thanks. Going to be on my way doing that, will return if successful.. assuming applypatch can be run in windows, if not I will have to dust off an older ubuntu notebook and get started.
Aaannd thank you, too, glad I came here before taking the plunge. I will do my best to get you the patched boot.img
tekuru said:
Excellent, thanks. Going to be on my way doing that, will return if successful.. assuming applypatch can be run in windows, if not I will have to dust off an older ubuntu notebook and get started.
Click to expand...
Click to collapse
As the android sources only build on 'nix, it's a 'nix executable.
We have both the 3g and the wifi stock images in the irc channel
bwcorvus said:
We have both the 3g and the wifi stock images in the irc channel
Click to expand...
Click to collapse
Mind putting them on multiupload or such for those of us not in the channel?
boot image
*EDIT: Thought I should point out that this is from the Verizon 3G Xoom*
Okay so here is the boot.img that is the result of the patch.
http://www.multiupload.com/LFUP6NY7A7
Since applypatch needs the SHA1 values of the source/target files, I took them from the updater script:
Code:
apply_patch("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/boot:8388608:17c91cba04ae40ebdc28cd7a5cbd9eb5e9bb33fd:8388608:e95341ff1b5f5cb2e246f028cc127083f14e0a40",
"-", e95341ff1b5f5cb2e246f028cc127083f14e0a40, 8388608,
17c91cba04ae40ebdc28cd7a5cbd9eb5e9bb33fd, package_extract_file("patch/boot.img.p"));
Then I wound up with this command, which I ended up running on my evo with the applypatch from the cyanogenmod update package, since my linux notebook wasn't happy being unused for so long.
Code:
# applypatch boot.img boot31.img e95341ff1b5f5cb2e246f028cc127083f14e0a40 8388608 17C91CBA04AE40EBDC28CD7A5CBD9EB5E9BB33FD:boot.img.p
And that resulted in the file I have uploaded, boot31.img. it matches the CRC from the install script, so we should be good to go.
tekuru said:
Mind putting them on multiupload or such for those of us not in the channel?
Click to expand...
Click to collapse
http://www.mediafire.com/?fzet7g9u770v286
Wifi stock 3.1 boot.img
tekuru said:
Then I wound up with this command, which I ended up running on my evo with the applypatch from the cyanogenmod update package, since my linux notebook wasn't happy being unused for so long.
Click to expand...
Click to collapse
Yeah, I'm a doofus, the android sources build a native binary, not a host binary. (You don't even need CM, because it's part of the standard Android tool suite).
But I'm glad you got that working.
ydaraishy said:
Yeah, I'm a doofus, the android sources build a native binary, not a host binary. (You don't even need CM, because it's part of the standard Android tool suite).
But I'm glad you got that working.
Click to expand...
Click to collapse
Guess it kind of worked out then -- I never even got to try on my computer, just thought about using the CM version since thats what was on the handset and I didn't know if I would have issues with an official build or whatnot.. and it just sort of worked. I can luck out occasionally it seems.. now back to OP's original thought, how to get root back
tekuru said:
Guess it kind of worked out then -- I never even got to try on my computer, just thought about using the CM version since thats what was on the handset and I didn't know if I would have issues with an official build or whatnot.. and it just sort of worked. I can luck out occasionally it seems.. now back to OP's original thought, how to get root back
Click to expand...
Click to collapse
Easy. Split the new boot image into kernel and ramdisk, and change ro.secure back, then wrap it all back together.
(Given that your 'nix machine is out of commission, I'm trying to do this for you now.)
Here, I hope this works for rootz, usual disclaimers apply. I can't test it myself because I don't have a device, though, sorry
(But you should have a stock image to work with, though, and if all else fails, flash HRI66 and reapply the update.)
ydaraishy said:
Here, I hope this works for rootz, usual disclaimers apply. I can't test it myself because I don't have a device, though, sorry
(But you should have a stock image to work with, though, and if all else fails, flash HRI66 and reapply the update.)
Click to expand...
Click to collapse
Just flashed it and booting now will let you know if this works
Thanks
Edit: That works. Once I rebooted I just was able to adb remount and push su to /system/bin and chmod it. Now have root on 3.1 Xoom.
Great job
Worked for me as well, thanks
Ok, so after the announcement of the 3.1 update at IO yesterday, were all eagle awaiting the 3.1 update.
For those of us in europe, with 3G xooms we need a different update so don't try flash anything that is currently available.
Second and most important. There are NO Stock boot images for 3G europe, we need someone who has stock recovery to dump it and get in touch with me. WE CANNOT UPDATE IF WE INSTALLED CLOCKWORK MOD.
Once we have a stock recovery image I can post all the stock images for us to flash back to stock for the update.
Use these commands to dump the recovery image (you need to be rooted and/or have a custom kernel like Tiamat (or the one in my thread) installed so you can remount, you may also need to install busybox (use Busybo installer by Stericson from the Android Market, don't forget to open and run it after you install it):
Code:
adb remount
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
adb pull /sdcard/recovery.img
That's it, the image will be on your sdcard and copied to your computer, please upload or PM me a link.
Thanks
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
I had to add "platform" to the path:
adb shell dd if="/dev/block/platform/sdhci-tegra.3/by-name/recovery" of="/sdcard/recovery.img"
Click to expand...
Click to collapse
Hope I did it all right after rooting the device (by your manual - thanks in advance for this!).
Riffer said:
I had to add "platform" to the path:
Click to expand...
Click to collapse
You're right, sorry I typed it from memory, will update it now!
That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
(The recovery ramdisk ro.build.version.release says 3.0.1, maybe the boot image is from 3.0? Has the MZ601 got 3.0.1 yet?)
ydaraishy said:
That's... odd...
The kernels from the boot image that you circulated a while back, plus the kernel from this recovery image, are different.
They should be the same.
Click to expand...
Click to collapse
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
It's also possible that the recovery might be the same as the US one, and the US one runs a differnet kernel to the euro one, so it's not necessarily a problem that it's different.
Oh, and any chance of a link to the recovery image you've dumped? Please.
alias_neo said:
That's normal ... a recovery image would probably have a light weight stripped down kernel, since it doesn't need to boot and run the full OS, just hte recovery OS.
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
No, they should have the same kernel. It's designed that way. (Remember, when you get an OTA, you get a recovery-from-boot.p patch that runs on startup to repatch your recovery image back to stock -- it's deliberately based on the boot image, so the patch is as small as possible)
I didn't dump the recovery image -- look a few posts up (I _still_ don't have a device yet )
ed. And I don't think a US MZ601 is out yet...The above dump looks like it's from a German Xoom, based on ro.product.locale.region.
ydaraishy said:
Has the MZ601 got 3.0.1 yet?)
Click to expand...
Click to collapse
Yes. Mine does have it. Got it without any branding from www.sparhandy.de yesterday.
Should I mention I am german?
alias_neo said:
Oh, and any chance of a link to the recovery image you've dumped? Please.
Click to expand...
Click to collapse
Mine is attached above? Or do you say that to ydaraishy?
Riffer said:
Mine is attached above? Or do you say that to ydaraishy?
Click to expand...
Click to collapse
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?
alias_neo said:
Sorry, didn't see your edit.
EDIT: @ydaraishy: Interesting, I wasn't aware of this as I have never ran an OTA before in my life, and my XOOM was at 3.0.1 when it was released.
So, I wonder what the deal is here, will the euro OTA come with a full kernel? Maybe the method I used to split the kernel and ramdisk I posted (in order to root it) caused some change? How are you comparing them?
Click to expand...
Click to collapse
No, they'll binary patch it like usual.
I split the kernel and ramdisk of the recovery image, then the boot image that you had posted a while back for root, then md5'd both kernel images.
Got my T-Mobile Xoom 3G (3.0.1; MZ601; H.6.1-38-5) today and dumped the recovery.img just after flashing rooted boot.img.
Hope this helps.
Thanks guys, hopefully i can use these to sort something out for us when we get 3.1 update finally.
I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.
MediumO said:
I also have a T-Mobile Xoom and I've used Clockworkmod Recovery to make a dump via dd of system and boot.
All togheter we should now have a complete set of the MZ601 H.6.1-38-5 Firmware.
I put it togheter into one rar-file and uploaded it. But I am not allowed to post links here because of not enough posts.
I will send it to you via PM, hopefully someone of you can post it.
Hope this helps.
Click to expand...
Click to collapse
Your zip you PMd me says boot, recovery and system, surely all 3 can't be stock if you installed clockwork mod to dump it, so which two are stock?
Ok, this one is exactly identical to mine - says Winmerge.
Riffer said:
Ok, this one is exactly identical to mine - says Winmerge.
Click to expand...
Click to collapse
Which one?
I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.
MediumO said:
I used the recovery of Riffer. System and boot are stock from my device.
I just put them togheter in one archive to get a full set.
Click to expand...
Click to collapse
That's great. Now we just gotta wait for 3.1 in Europe!
I have been fallowing this forum for a long time and also I got my Xoom from CPW couple of weeks ago and I have to say that I'm really waiting for this update so bad, just because many people has been reviewing it and they say is really a change in performance, sometimes I find that my Xoom is quite heavy, more when I'm trying to surf the web, and sometimes when I come to the forum from it, and I will like to be an active member of this forum as well, I will try to help with anything I can and I just rooted my Xoom with neo guide.
sorry if my english is not so good.
I'm in London at the moment
and Galaxy SII owner as well
Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)
MediumO said:
Hopefully 3.1 will show up in Europe soon. I read somewhere that T-Mobile Germany had also planned to release the update on 5/11. But no evidence for that until now.
Otherwise we have to port the CDMA Rom ;-)
Click to expand...
Click to collapse
There will be non of that frankenfrak here sonny. We get our own 3.1 or we all go down swinging. :-D
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
Hi!
I just unlocked (S-OFF) and rooted my Sensation according to the tutorial pinned in the development section. Unfortunately, now I am unable to connect to any WiFi-networks. My phone is an unlocked, SIM-free european HTC Sensation.
Restoring the phone backup I created before rooting (with ClockworkMod Recovery) to the unrooted stock ROM didn't work, still no wireles lan.
Does anybody know how to resolve this issue? Any pointers would be greatly appreciated.
Edit: If you flashed an unsafe boot image, page two has the solution.
Maybe try to ask in the IRC channel from #revolutionary on irc.freenode.net (but please recheck this on their website ), joined there today because of a minor problem and they seem very helpful.
PartyMango said:
Hi!
I just unlocked (S-OFF) and rooted my Sensation according to the tutorial pinned in the development section. Unfortunately, now I am unable to connect to any WiFi-networks. My phone is an unlocked, SIM-free european HTC Sensation.
Restoring the phone backup I created before rooting (with ClockworkMod Recovery) to the unrooted stock ROM didn't work, still no wireles lan.
Does anybody know how to resolve this issue? Any pointers would be greatly appreciated.
Click to expand...
Click to collapse
u installed boot.img from cwm? I`m figuring out how to restore the old one..
I did some further investigation, and possibly was to quick on the draw:
While trying to find a solution, I noticed that I was able to connect to some other networks without problems. So I tried changing channels & power-cycling my WiFi access point. Et voilà: Magically, my wireless lan-problems did disappear.
I guess the problem was with the router all along, no fault of unrevoked & AlphaRev which I both want to praise for their excellent work in unlocking this phone.
Next time, I'll try turning it off and on again, first
Glad you fixed it Mr Mango, can you change the Title of your Thread to Fixed then
nicoaraalex said:
u installed boot.img from cwm? I`m figuring out how to restore the old one..
Click to expand...
Click to collapse
I used the boot.img for CWM provided with the tutorial here (Step 2): http://forum.xda-developers.com/showthread.php?t=1192300
ikhzter said:
Glad you fixed it Mr Mango, can you change the Title of your Thread to Fixed then
Click to expand...
Click to collapse
Done.
PartyMango said:
I used the boot.img for CWM provided with the tutorial here (Step 2): http://forum.xda-developers.com/showthread.php?t=1192300
Done.
Click to expand...
Click to collapse
Thanks Mr Flirty Magno
well not working for me.. on Wi-Fi, it says Error... doesn't turn on or off...
nicoaraalex said:
well not working for me.. on Wi-Fi, it says Error... doesn't turn on or off...
Click to expand...
Click to collapse
Exactly the same problem here, nothing to connect to because the wifi won't initiate. Really need help with this too.
dladz said:
Exactly the same problem here, nothing to connect to because the wifi won't initiate. Really need help with this too.
Click to expand...
Click to collapse
Same here! Sensation with Vodaphone branded ROM, no wifi anymore. Says "Error" in wireless menu.
I'm not sure if this was caused by S-OFF itself or by the installation of the "Unsafe" boot image to get root in adb by default.
So far I haven't found a way to make the wifi work again!
I have the exact same "Error" problem with my T-mobile branded sensation
joel.bourquard said:
Same here! Sensation with Vodaphone branded ROM, no wifi anymore. Says "Error" in wireless menu.
I'm not sure if this was caused by S-OFF itself or by the installation of the "Unsafe" boot image to get root in adb by default.
So far I haven't found a way to make the wifi work again!
Click to expand...
Click to collapse
Ok, I think I really found the cause: it happens when I install the "Unsecured Boot.img - Europe" from there:
http://forum.xda-developers.com/showthread.php?t=1122053
Edit: Same problem with the Unsecured boot img (Asia) !
But here's good news: just install a RUU and the Wi-Fi problem will be gone!
joel.bourquard said:
Same here! Sensation with Vodaphone branded ROM, no wifi anymore. Says "Error" in wireless menu.
I'm not sure if this was caused by S-OFF itself or by the installation of the "Unsafe" boot image to get root in adb by default.
So far I haven't found a way to make the wifi work again!
Click to expand...
Click to collapse
UNSAFE boot image was the cause. so i scrapped it
AS Joel said, just reinstall stock rom. and its gone.
for more information visit the guide to S-off, bottom of post 1 will tell you how to debrand or reinstall
Yes, everything works fine now with the un-branded ROM.
So there's no way to get direct root adb access without breaking wi-fi functionality at the moment?
joel.bourquard said:
Yes, everything works fine now with the un-branded ROM.
So there's no way to get direct root adb access without breaking wi-fi functionality at the moment?
Click to expand...
Click to collapse
When users had the wifi break, the rooting file in step 3 was outdated. it was for froyo and eclair only. whcih is why users flashed unsecured boot.img causing the WIFI loss.
NOW!
Read the Guide. If you follow step 3. you WILL get root and YOU WILL NOT LOSE WIFI.
initially Step 3. had a su file called su-ef2.3.6.1.zip which didnt work causing people to use the unsecured boot from binary
but the new one is called su-efgh2.3.6.3zip which is working
the difference, the new supports Gingerbread and Honeycomb
i followed step 3 and hundreds of others have, we are all rooted on stock or custom roms without wifi problems!
ikhzter said:
When users had the wifi break, the rooting file in step 3 was outdated. it was for froyo and eclair only. whcih is why users flashed unsecured boot.img causing the WIFI loss.
NOW!
Read the Guide. If you follow step 3. you WILL get root and YOU WILL NOT LOSE WIFI.
initially Step 3. had a su file called su-ef2.3.6.1.zip which didnt work causing people to use the unsecured boot from binary
but the new one is called su-efgh2.3.6.3zip which is working
the difference, the new supports Gingerbread and Honeycomb
i followed step 3 and hundreds of others have, we are all rooted on stock or custom roms without wifi problems!
Click to expand...
Click to collapse
Sorry, maybe I wasn't being totally clear.
Yes, I flashed ClockworkMod and then "su-2.3.6.3-efgh-signed.zip" and it works great. I'm rooted, no problem with that.
The only thing I'm missing here, is that when I connect with "adb shell" I get the "$" prompt (not root). So I need to type "su" first. Then I'm root.
With the "unsecured boot" I get connected as root right away with "adb shell", but then the Wi-Fi doesn't work.
Therefore I was wondering if some way exists, to enable direct root for "adb shell" without breaking the Wi-Fi.
joel.bourquard said:
Ok, I think I really found the cause: it happens when I install the "Unsecured Boot.img - Europe" from there:
http://forum.xda-developers.com/showthread.php?t=1122053
Edit: Same problem with the Unsecured boot img (Asia) !
But here's good news: just install a RUU and the Wi-Fi problem will be gone!
Click to expand...
Click to collapse
Any recommendation on which RUU to flash? I have a Tmo Sensation. I don't wanna flash anything that will brick my phone now that I finally got S-OFF on this bad boy
joel.bourquard said:
Sorry, maybe I wasn't being totally clear.
Yes, I flashed ClockworkMod and then "su-2.3.6.3-efgh-signed.zip" and it works great. I'm rooted, no problem with that.
The only thing I'm missing here, is that when I connect with "adb shell" I get the "$" prompt (not root). So I need to type "su" first. Then I'm root.
With the "unsecured boot" I get connected as root right away with "adb shell", but then the Wi-Fi doesn't work.
Therefore I was wondering if some way exists, to enable direct root for "adb shell" without breaking the Wi-Fi.
Click to expand...
Click to collapse
I dont think there is a way yet, im not sure if it works directly or not, as i am currently using a custom rom
Beast84 said:
Any recommendation on which RUU to flash? I have a Tmo Sensation. I don't wanna flash anything that will brick my phone now that I finally got S-OFF on this bad boy
Click to expand...
Click to collapse
Check your Build number under the software information in Settings.
it should start with 1.27.531.2 or 1.29.531.2
You can download the exact same one below according to your build number
RUU_Pyramid_TMOUS_1.27.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_192098_signed
http://www.filefactory.com/file/cb5d...098_signed.exe
RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed
http://www.filefactory.com/file/cb7a...714_signed.exe
Ahhh, does this mean we naughty WIFI guys can try to re-root now? I was one of the ones that had WIFI go crap out after the root, and I flashed back to a stock ROM for TMOUS. Does this mean I can try to root again and plan on it working this time?
Matt
Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient
Nice!
suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.
Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.
I just ordered a Bolt, can't wait to play
Screen shots
OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%
More screenshots
Random stuff that can be unlocked hidden in the phone.
urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding