Related
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
Hello everyone
I'm trying to sideload KTU84P 4.4.4 Nexus 5 to 5.0 LRX21O but I keep getting an error about my "system/build.prop" has unexpected content I only changed the dpi setting, but I have since changed that back to default of 480 in order to do the update but I'm still getting this error. Unfortunately I've done a rookie mistake and thinking that I'm only changing one setting I have not made a backup....
Is anyone is possession of stock KTU84P 4.4.4 build.prop that they could share? Any help would be much appreciated. Thanks!!!!
I changed DPI to 445 on mine, too, other than that it's stock
thor1k said:
I changed DPI to 445 on mine, too, other than that it's stock
Click to expand...
Click to collapse
Could you please share the file? Maybe yours will be better than mine. I've done lots of system changes after changing the dpi setting so I'm thinking that some of them might of written to the file, that's the only explanation I have.
stock
babyjesuz said:
stock
Click to expand...
Click to collapse
also there's a stock rooted 4.4.4 zip you could open up and get the build.prop from
let me know if that build.rar doesn't work and I'll get mine out
thor1k said:
also there's a stock rooted 4.4.4 zip you could open up and get the build.prop from
let me know if that build.rar doesn't work and I'll get mine out
Click to expand...
Click to collapse
Thank you for this, but I think I might need a rooted one as my phone is rooted. (this has soft bricked my phone). I would much apprecieate if you could uploaded the rotted one. Thanks!
neopl666 said:
Thank you for this, but I think I might need a rooted one as my phone is rooted. (this has soft bricked my phone). I would much apprecieate if you could uploaded the rotted one. Thanks!
Click to expand...
Click to collapse
Just flash the system.img in fastboot. It'll take care of all the system mods you did
Sent from my Nexus 9 using XDA Free mobile app
I managed in the end. My phone got stuck in boot loop with the stock build.prop but because it was stock I was able to flash 5.0 OTA and all is back to normal. Had absolute pain trying to re-root. I was flashing supersu in TWRP which was successful but when booting the phone supersu told me that it is missing the binary. I managed to do CF-AutoRoot which got me stuck in another boot loop but at that point I got into TWRP and flashed supersu 2.26 beta which finally got me out of the loop and got the phone rooted..... what a mission, and this isn't even my phone!
All right you losers and screwups! Everyone who sucked hard at rooting has reason to rejoice!
Soft-bricking your phone may have been the best thing to happen to you.
Luck smiles on the unfortunate and the stupid today!
Use a download manager to get these files, and check the MD5 of your downloaded file against AndroidFileHost.
Here's the latest rooted version from @diedemus
Here's the original rooted image for the H810PRa-310-410.
Know what you are doing before attempting to flash these files! Flashing the H810PR firmware is done mostly as a last resort for people who have bootlooping AT&T H810s.
Read all the instructions carefully, then follow the instructions in the root thread 1 through 6, except ignore the parts in step 4 where it mentions tar.gz and the filename since you have a rar file and already had to extract the image file from it and rename it to system.img.
You'll see that we have a different command to flash the H810PR compared to what was used on the H810. Here is the code to copy and paste at the # prompt in the command window:
Code:
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Paste the above code in the command window, then hit enter and pucker your butt.
Wait for the # prompt to reappear.
Type LEAVE and hit enter.
Prepare to crap your pants again or savor the sweet taste of victory!
Good luck!
Feel free to ask questions, but try searching for an answer first please. XDA is loaded with information, but it's squirreled away deep in various threads. Learning to search XDA is a valuable skill. Even if you don't find an answer to your specific question, you'll learn something anyway.
H810PR is much better IMO than stock AT&T except for the danger of the green blob in the camera. There's hardly any bloat (like 100 less packages on the phone, seriously!), and no CarrierIQ to have to bother disabling. All the stuff AT&T broke is working too.
Cons so far:
Big ol' green dot in the camera. I wouldn't flash this rom unless I had to because of this issue.
No VoLte (voice over LTE). The phone drops to 3G in phone calls. Follow this post to enable LTE outside of a voice call.
Voicemail settings are grayed out. To set up, put your SIM in another phone or call ATT.
Editing options in camera are overwhelming! There's too many things you can change!
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 100 less.
The stuff AT&T removed or broke is not broke.
Editing options in camera are amazing! There's so many things you can change!
No CarrierIQ
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
This is pretty sweet! I always wanted to post in the dev folder, and make a reserve post. Not that I really did anything worthy of it, but I'm leaving the post here anyway.
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
It worked! It was a bumpy road, thank you for all your help! (oh sweet ad blockers, how I love you)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Yes to all your questions.
I repeated the code to flash here to make sure people noticed it was different for H810PR. It's the same in both posts.
Just noticed i no longer have volte with this image. (yes, i have lte)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
user787 said:
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
Click to expand...
Click to collapse
Copy OP's code @up..for me i follow till step 9 from THIS then follow this PAGE from 6 to 9 then paste OP code to flash image root
Please read carefully before anything bad happened
faizalotai said:
Please read carefully before anything bad happened
Click to expand...
Click to collapse
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
No problem bud
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
I edited the OP to make the instructions more clear. Hope it helps!
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
noamaniac said:
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
Click to expand...
Click to collapse
Yes.
What is the LTE icon for this build? I have the 4G icon, but not sure this means LTE.
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
bobloadmire said:
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
Click to expand...
Click to collapse
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T (I don't know why I keep thinking this is possible, it isn't, bootloader is flashed by the KDZ and not compatible with the ATT versions anymore), but I'm going to stick it out on this image for awhile.
I'm keeping an updated list of the pros and cons in the OP.
phineous said:
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T, but I'm going to stick it out on this image for awhile.
Cons so far:
No VoLte (voice over LTE). The phone drops to 3G in phone calls.
Possible problems with voicemail.
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 150 less.
Click to expand...
Click to collapse
Would you Say the phone is snappier overall or is it mainly just to save storage?
bobloadmire said:
Would you Say the phone is snappier overall or is it mainly just to save storage?
Click to expand...
Click to collapse
I ran Debloater and blocked around 98 packages when I was on the AT&T H81010e non-root image. The phone was pretty fast, but something had a memory leak and I'd have to reboot it every morning. This image hasn't had that problem yet, but I've only been using it for a couple of days.
You might want to wait a little while for the people who had to use it to discover any more downsides. I think it'll be easy to switch back to an AT&T image, but I'm not 100% sure because I haven't tested it yet. (not possible till there's a TOT.)
In any case, I think it's a good idea to follow the instructions in the original root thread to extract an image of your working phone, name it something you'll remember, and keep it on the internal storage as an emergency recovery image.
Totes mah gotes. Thanks man.
Anyone that's on this Firmware having issues with voicemail? I can't seem to get google voice to work and when people call my regular voicemail it is saying i'm not available. I've tried entering the code into the dialer and i'm getting an error saying connection error or wrong MMI code.
I went into the forwarding settings in the phone and entered my GV # and received unexpected error from network.
Hi guys,
While Android 8.0 for Bolt and 10 Evo is not out yet ( or maybe never :v ), another dev is maintaining it - S.Team.
Yesterday (15/10/2018), they released the newest build for Bolt and 10 Evo ( as well as 10, Ultra ... )
I'm not the owner . I just download and share.
Orinal thread : https://tw.weibo.com/sundream1988/4295491971342435
Baidu link : http://t.cn/E7rx8UK ( pass : face ) - will be expired after 12h
Drive link : https://drive.google.com/file/d/1vtded5hvHJXTEfqk610GWR0rNndT8Hwi/view?usp=sharing
------------------------------------------------------------------------------------------------------------------------------------------
p/s : SO SORRY GUYS, MY HTC 10EVO/BOLT NOW HAS BROKEN SIM'S BOARD AND CANNOT BE REPLACED. SO I QUIT HTC
Was wondering if this new version was tried by anyone. I had some issues with data on one of the older versions
I'm using this ROM daily, everything is ok.
lcdkhoa said:
I'm using this ROM daily, everything is ok.
Click to expand...
Click to collapse
On HTC u or Bolt?
I get some bug with my Bolt. The boot+ can't start.
Camera don't work in pro mode. It's stuck on intro screen and there's no button like OK or start..etc
Will try it againt. Keep it up man.
Thanks. Sorry for my bad English.
thaiduong2009 said:
On HTC u or Bolt?
I get some bug with my Bolt. The boot+ can't start.
Camera don't work in pro mode. It's stuck on intro screen and there's no button like OK or start..etc
Will try it againt. Keep it up man.
Thanks. Sorry for my bad English.
Click to expand...
Click to collapse
Mine is HTC 10 Evo and Pro - mode works perfectly.
You can try these ways :
1. Back to stock ROM, then install S.Team ROM as an Update.
or
2. Booting to TWRP, fully wipe your phone and format it. Then install S.Team ROM
lcdkhoa said:
Mine is HTC 10 Evo and Pro - mode works perfectly.
You can try these ways :
1. Back to stock ROM, then install S.Team ROM as an Update.
or
2. Booting to TWRP, fully wipe your phone and format it. Then install S.Team ROM
Click to expand...
Click to collapse
I do the 2nd way (twrp) but need del the boot+_china folder in system/priv-app. Then boot+ work againt.
Thanks for rep .
I tried this rom coming from bad boyz. I can't get data going and cannot manually set the apn. I'm on the bolt
Maybe if I dirty flash the data settings will stick? Well.....that didn't work. Giving up for now. Without data, it's sort of pointless to use
I'm on 10 evo with cricket GSM. This Tom won't mess with the GSM capabilities right?
hey guys,
did you choose your carrier in Setting menu for Data ?
lcdkhoa said:
hey guys,
did you choose your carrier in Setting menu for Data ?
Click to expand...
Click to collapse
I did go in and choose sprint. Didn't seem to do anything. If anyone can enlighten me on how they got it working on sprint I would greatly appreciate it
Is based on Oreo?
I'm going to download and try it on my HTC BOLT, thanks
boot stopped and I can not uninstall it asks for security pattern before desistalarla
bleichtman said:
I did go in and choose sprint. Didn't seem to do anything. If anyone can enlighten me on how they got it working on sprint I would greatly appreciate it
Click to expand...
Click to collapse
There was a fix for this posted in a previous s-rom forum that was deleted. I don't remember exactly where you need to go but what you will need is a valid sprint rom with the proper carrier configs in it. I copied them out of an htc 10 leedroid rom before, but you can use any rom that has the US sprint config files in it. Open up with an unzip program the s.team rom in your pc and copy the sprint config files to the carrier folder where they belong. The rom should auto rezip the file with the new config back in when you close it. Flash the rom with the updated configs. I don't remember the exact path from the file names since those posts are deleted but that is how we got it working on his last bolt rom. I was checking through my folders, and thought I could pull up the config files to send you but I just can't remember where the were. Someone that knows a bit more about it may be able to give clearer instructions. -actually now that i think about, you might be one of the guys that got it working with 7.1! if not check with roadkill42 cause i think he got it working too. I'll have to play around with this download later when I have time since these things take some tweaking to get working.
EDIT: Ok found them, for example in the leedroid htc rom they are located here: LeeDrOiD_10_V5.2.1-R146-Stable.zip\extras\carriers\Sprint
I think its different for every rom, but that is the folder that you need to copy and put in a similar folder in the s.team rom. Not sure where since I haven't download it yet. Like I said, you should be able to pull the files from any other rom that has the sprint configs in them. Can't upload them cause the files 40mb. Of course there may be another way as well...
Rudielki said:
Is based on Oreo?
Click to expand...
Click to collapse
Android 7.1.2
How to switch form SU to magisk
Where can I find S.team.ROM kernel or boot inage without SU. I Flashed stock boot image but it doesn't work.
Sorry for bad English Hope you got me.
IronicalWolf said:
Where can I find S.team.ROM kernel or boot inage without SU. I Flashed stock boot image but it doesn't work.
Sorry for bad English Hope you got me.
Click to expand...
Click to collapse
You download an software on PC named "pack_unpack tool v3.8", then unpack "boot.img". After that, del folder "S.ROM" in "Out-put" folder. Repack it.
lcdkhoa said:
You download an software on PC named "pack_unpack tool v3.8", then unpack "boot.img". After that, del folder "S.ROM" in "Out-put" folder. Repack it.
Click to expand...
Click to collapse
Thank you so much brother but Its not working phone turns on and off only show HTC and in second turn off can you send me evo boot img for S.rom please
hi how should i install the rom zip file ?
i tried the stock recovery for installing zip but it faild
should i have to install custom recovery like twrp for the rom?
So a month or so ago I was having issues with my HTC U11 not letting my phone pair with my new Smart Watch. After much trouble shooting decided to do a factory reset. Afterwards found out that do to a glitch Google Backup's weren't going thru and now my phone won't ask for Anything other a PIN number that I don't know. Here is screen shot from Fastboot, phone responds to ADB commands but sadly bootloader is locked S-On and no way to turn on USB debugging or access Developer options from the locked state. I've been trying to flash RRU but so fare no joy all are either failing because they aren't signed or not the correct version. Anyone have any ideas?
I have already bought a new Oneplus Nord N10 and I have an HTC 10 CDMA unlocked and a HTC 10 Bolt CDMA unlocked, so I don't really need the phone... But I'm pissed that my prettiest one is currently bricked and I feel like I'm soooo close to fixing it, just need to find the Right combo... I'm even willing to pay a reasonable amount to anyone that helps get the think working lol I know it can be fixed I just can't figure it out.
danth3hitman said:
So a month or so ago I was having issues with my HTC U11 not letting my phone pair with my new Smart Watch. After much trouble shooting decided to do a factory reset. Afterwards found out that do to a glitch Google Backup's weren't going thru and now my phone won't ask for Anything other a PIN number that I don't know. Here is screen shot from Fastboot, phone responds to ADB commands but sadly bootloader is locked S-On and no way to turn on USB debugging or access Developer options from the locked state. I've been trying to flash RRU but so fare no joy all are either failing because they aren't signed or not the correct version. Anyone have any ideas?
I have already bought a new Oneplus Nord N10 and I have an HTC 10 CDMA unlocked and a HTC 10 Bolt CDMA unlocked, so I don't really need the phone... But I'm pissed that my prettiest one is currently bricked and I feel like I'm soooo close to fixing it, just need to find the Right combo... I'm even willing to pay a reasonable amount to anyone that helps get the think working lol I know it can be fixed I just can't figure it out.
Click to expand...
Click to collapse
you should be able to find the correct one here
Search Files Results for "2pzcimg" | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I have a known good pie ruu that i use so if all else fails i could give u a download load link,, hth,,,
I'd gladly try it, I used the RUU decoder tool to extract the zips from the RUU that I should be the correct one. I was able to boot into RRU mode and flashed all the zips one at a time that but still no joy. The only error I had during the whole thing was on the first zip and I just flashed it again and it went though without an errors but after reboot it did the little android encryption thingy and then still FRP. if you have a good RUU I'm more than willing to try...
danth3hitman said:
I'd gladly try it, I used the RUU decoder tool to extract the zips from the RUU that I should be the correct one. I was able to boot into RRU mode and flashed all the zips one at a time that but still no joy. The only error I had during the whole thing was on the first zip and I just flashed it again and it went though without an errors but after reboot it did the little android encryption thingy and then still FRP. if you have a good RUU I'm more than willing to try...
Click to expand...
Click to collapse
Another thing you could try if you havent already is go in to your stock recovery partition, there you can select factory reset just to see if that works, if you need help getting to the stock recovery just google it or ask here, also i will pm you with the ruu download link,, hth
Already did that lol I'm downloading the RUU now I'll let you know if that works thanks
JOY! phone fixed and unbricked! OMG hammered58 is a god!
danth3hitman said:
JOY! phone fixed and unbricked! OMG hammered58 is a god!
Click to expand...
Click to collapse
Please , just good luck,, glad it worked,,
The U11 has always been one of my favorite phones and with HTC no longer supporting it I'm glad there's still people like you that are here to keep thier legacy of quietly brilliant phones going
hammered58 said:
Another thing you could try if you havent already is go in to your stock recovery partition, there you can select factory reset just to see if that works, if you need help getting to the stock recovery just google it or ask here, also i will pm you with the ruu download link,, hth
Click to expand...
Click to collapse
hi there! I have the same issue here...can u send me also that llink ? thnx in advance!
kwintie said:
hi there! I have the same issue here...can u send me also that llink ? thnx in advance!
Click to expand...
Click to collapse
I just sent u a pm,, hope it helps
kwintie said:
hi there! I have the same issue here...can u send me also that llink ? thnx in advance!
Click to expand...
Click to collapse
Did it fix your issue?