i wanted to start using custom themes; however, i'm unfimiliar with deodexing.
how is it done?
thanks
Milenko2121 said:
i wanted to start using custom themes; however, i'm unfimiliar with deodexing.
how is it done?
thanks
Click to expand...
Click to collapse
I recommend you use one of the ROMs that already is deodexed.
I'm currently using Ninja Speed Freak v0.4.5. which is working out great:
http://forum.xda-developers.com/showthread.php?t=1173843
mpalatsi said:
I recommend you use one of the ROMs that already is deodexed.
I'm currently using Ninja Speed Freak v0.4.5. which is working out great:
http://forum.xda-developers.com/showthread.php?t=1173843
Click to expand...
Click to collapse
never used a rom before >_<
all i've done is root and webtop hack.
currently using the OTA update from yesterday.
how do i use a rom?
Milenko2121 said:
never used a rom before >_<
all i've done is root and webtop hack.
currently using the OTA update from yesterday.
how do i use a rom?
Click to expand...
Click to collapse
Is your bootloader unlocked?
mpalatsi said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
no, i've been worried i'd hardbrick from trying to unlock it.
Milenko2121 said:
no, i've been worried i'd hardbrick from trying to unlock it.
Click to expand...
Click to collapse
You're not going to hard-brick as long as you don't downgrade your firmware.
I recommend you flash this:
http://forum.xda-developers.com/showthread.php?t=1182526
mpalatsi said:
You're not going to hard-brick as long as you don't downgrade your firmware.
I recommend you flash this:
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
i'm reading the warning and it states this...
"If you already updated to OTA without unlock, and are not unlocked, then you will soft brick(0x1000 error). To fix it you have to unlock."
i'm confused, do i flash this to unlock, or will it softbrick me because i'm using the OTA update and not unlocked?
also, one other question, will this wipe my internal memory?
Milenko2121 said:
i'm reading the warning and it states this...
"If you already updated to OTA without unlock, and are not unlocked, then you will soft brick(0x1000 error). To fix it you have to unlock."
i'm confused, do i flash this to unlock, or will it softbrick me because i'm using the OTA update and not unlocked?
also, one other question, will this wipe my internal memory?
Click to expand...
Click to collapse
If you already installed OTA without an unlock. Then you have the fuse burned that prevents you from downgrading to the official 1.8.3 sbf. If you do, you will brick your phone.
This sbf should work over the OTA. Think of it like a full reinstall of Windows, but in this case it is Android. To extend the metaphor further, this sbf is like having SP1 slipstreamed in, in that it has the unlocked bootloader integrated.
It will wipe your data, backup!
alright, well i'm downloading the file now.
hopefully all goes well
i'll come back once it's flashed.
thanks for all your help so far
Milenko2121 said:
alright, well i'm downloading the file now.
hopefully all goes well
i'll come back once it's flashed.
thanks for all your help so far
Click to expand...
Click to collapse
Not a problem, if you have any issues I'll be sure to help, I think I might be pulling an all-nighter.
mpalatsi said:
Not a problem, if you have any issues I'll be sure to help, I think I might be pulling an all-nighter.
Click to expand...
Click to collapse
hmm, was reading more through that thread and saw this...
REDFOCZ "Ok well, and using this after getting the ota update bricked my phone, and I am getting the 0x1000 failed to boot message...."
The phone turns on just long enough to give the SVF:105.1:2 Failed to boot 0X1000, and for split second and then power off ... I dont have an option to go into fast boot ...
So i can not do the fast boot oem unlock command
Milenko2121 said:
hmm, was reading more through that thread and saw this...
REDFOCZ "Ok well, and using this after getting the ota update bricked my phone, and I am getting the 0x1000 failed to boot message...."
The phone turns on just long enough to give the SVF:105.1:2 Failed to boot 0X1000, and for split second and then power off ... I dont have an option to go into fast boot ...
So i can not do the fast boot oem unlock command
Click to expand...
Click to collapse
According to the OP you should be able to log into fastboot and use "oem unlock" command but I have not attempted this myself.
I'm not sure if the gentleman above did something incorrectly but he should be able to access fastboot.
Related
How do I go back to out of the box stock? I flashed the new Ruu the other day, 2.11.605.0, and now my bootloader is locked.
So how do I fix it if I can't flash anything???
Sent from my ADR6400L using XDA App
You will need to flash the stock RUU. This thread should help you out.
http://teambamf.net/showthread.php/650-All-ruu-s
nm
PilotML said:
I did the same and have the same problem. Did this work?
Click to expand...
Click to collapse
Have not done it yet, although I am wondering if DirtyFingers misunderstood my question.
What got me to this problem was BECAUSE of flashing the latest RUU, from here: http://www.droid-life.com/2011/08/2...ruu-leaked-version-2-11-605-0-of-gingerbread/
Soooo... how do I flash a file to fix it if my Bootloader is locked and I can't flash anything???
dirtyfingers said:
You will need to flash the stock RUU. This thread should help you out.
http://teambamf.net/showthread.php/650-All-ruu-s
Click to expand...
Click to collapse
How in the heck do I flash anything if my Bootloader is locked?????
flashing any official RUU = locked and stocked
you've gotta go through the root process again if you wanna flash anything again
rickyray9 said:
flashing any official RUU = locked and stocked
you've gotta go through the root process again if you wanna flash anything again
Click to expand...
Click to collapse
So rooting my phone will unlock my bootloader?
How do I root 2.11.605.0? Is there a different method you are supposed to use?
oops delete me
flooritnfly said:
So rooting my phone will unlock my bootloader?
How do I root 2.11.605.0? Is there a different method you are supposed to use?
Click to expand...
Click to collapse
http://revolutionary.io
Sent from my HTC Thunderbolt
nm
PilotML said:
Unless you have a Mac.... Which is where I'm stuck. Tried this on a friends computer and it wouldn't recognize the device.
Click to expand...
Click to collapse
Read the whole page and the link to the full documentation. There are some prerequisites to running it. Mainly the HTC fastboot drivers for Windows that they provide on their documentation page. You also might need the Android SDK set up but I'm not sure about that.
Sent from my HTC Thunderbolt
you just take the sim card out put in another phone delete your 2.11 or put it in your downloads folder then put the sim card back in your phone and you should be able to get back to recovery. make sure you unmout the card before you take it out.
Had to use my cousin's (windows) computer but it worked.
Really PilotML? What is your bootloader version? I've tried revolutionary to unlock a bunch of times on my Gingerbread 2.3.4 device to no avail. I'm on the 605.9 bootloader and i'm thinking that is the problem.
I made the mistake of letting my phone update all the way after I purchased it last week and now I can't seem to root or unlock or anything and those 10000 verizon apps are driving me insane. : (
I asked this in another thread but didnt get an answer...
This morning, I checked my system updates and got the OTA for ICS. It downloaded fine, and I hit install now. My phone powered off like it should have, and when it came back on my screen has has a weird green X in the middle of the screen. Is this normal? should I keep waiting? I didnt think it should have takin this long, and Ive never seen this weird X before...can someone please help...
Are you rooted/Bootloader unlocked?
Dark Nightmare said:
Are you rooted/Bootloader unlocked?
Click to expand...
Click to collapse
yes, both actually. Ive never flashed any roms or anything though, just stuck with the stock cuz I was scared to mess things up...lol
Unroot, restore stock recovery then relock the bootloader, then try again. It won't allow the update with an unlocked bootloader.
Dark Nightmare said:
Unroot, restore stock recovery then relock the bootloader, then try again. It won't allow the update with an unlocked bootloader.
Click to expand...
Click to collapse
To be completely honest, I have NO IDEA how to do that. I had Binery walk me through the rooting process, and I dont know how to restore it..
papeshfoo said:
To be completely honest, I have NO IDEA how to do that. I had Binery walk me through the rooting process, and I dont know how to restore it..
Click to expand...
Click to collapse
Use the Amaze toolkit, it has everything as a button, do it in this order and you should be fineL
1. restore stock recovery
2. relock the bootloader (oem_relock)
3. retry updating.
Dark Nightmare said:
Use the Amaze toolkit, it has everything as a button, do it in this order and you should be fineL
1. restore stock recovery
2. relock the bootloader (oem_relock)
3. retry updating.
Click to expand...
Click to collapse
thanks, one more question, where do I get the toolkit?
Here ya go: http://forum.xda-developers.com/showthread.php?t=1493905
Dark Nightmare said:
Here ya go: http://forum.xda-developers.com/showthread.php?t=1493905
Click to expand...
Click to collapse
thank you sir...
Welcome buddy ^_^
Hey Dark, I flashed the stock recovery, relocked the bootloader, ran the update again and now I get a phone pic with a red triangle and exclamation mark...any ideas?
Download one of the GB stock RUU files, rename it and place it on your external sd card and reboot into HBoot, it should automatically detect the file and take your entire phone back to complete stock, there shouldn't be any stops from updating.
Stock RUU thread: http://forum.xda-developers.com/showthread.php?t=1617644
rename the file to PH85IMG.zip when you place in on your sd card.
Dark Nightmare said:
Unroot, restore stock recovery then relock the bootloader, then try again. It won't allow the update with an unlocked bootloader.
Click to expand...
Click to collapse
As I posted in another thread, I have an unlocked bootloader with no other mods done, and I flashed the OTA without a problem.
great, I dont have and SD card...lol
Awe man, what's not stock on your current set up? Maybe we can just restore files. Don't you have a nandroid backup?
Dark Nightmare said:
Awe man, what's not stock on your current set up? Maybe we can just restore files. Don't you have a nandroid backup?
Click to expand...
Click to collapse
well, when I unlocked my bootloader I used the HTC site, then I had Binery help me with root. he came up with a one-click root while we were doing it. After that I haven't done anything else to it besides get rid of the bloat cuz that's the only reason I wanted root.
Everything should be fine then, stock recovery, stock rom, locked bootloader, tried re-downloading the update?
Dark Nightmare said:
Everything should be fine then, stock recovery, stock rom, locked bootloader, tried re-downloading the update?
Click to expand...
Click to collapse
I just did a factory reset, re-downloaded the update, Im about to try the install now. I did notice one thing though when I was using Hasoon, I think it said Failed when I flashed the stock recovery...
Yep, The update failed to install again.
What radio is on the new OTA update? Can someone who has done the update, post?
No clue where recovery files go on the amaze or we could do it via recovery, just retry flashing stock recovery, if not we'll have to wait until someone pulls the file and makes a zip file to flash it, did you try flashing the recovery using the tool while the phone was in fastboot? That's probably a requirement.
So Sprint finally said there was a system update to ICS so I downloaded it and installed and it instantly popped up an error, didn't have any words it was just a picture of the guy with the warning sign. So I waited and it never did anything. I figured I would clear everything/factory reset and see if that fixed it. Nope. Even moreso, it wouldn't let me install any other ROM either. I did enough superwipes and stuff that I finally got the stock ROM to work so I'm back where I started.. One clue might be that I cannot seem to clear the sd-ext, it gives me an error there.
With it back in working order, if I don't clear anything and just try and install ICS from bootloader, what I show in the pic is what happens.
The last part about the E:error in sd card is what I was getting when all the other ROM's were screwing up.
Maybe bad sdcard
Sent from my PG86100 using Tapatalk 2
I don't see how when it works fine now. It's like something is messing with it but I have no clue what.
Re-lock your device and apply the update again.
Just do a fastboot command "fastboot oem lock".
Ugh, you cannot take an OTA if you are rooted with a custom recovery.
sitlet said:
Ugh, you cannot take an OTA if you are rooted with a custom recovery.
Click to expand...
Click to collapse
I had Revolutionary with CWM installed on mine w/ Gingerbread. Installed via EXE method and everything works.....
js593 said:
I had Revolutionary with CWM installed on mine w/ Gingerbread. Installed via EXE method and everything works.....
Click to expand...
Click to collapse
Right, that is not an OTA.
Sent from my PG86100 using xda app-developers app
wow! are you F***ing serious? OH I'M ROOTING AND I'M GOING TO TAKE AN OTA? SERIOUSLY!? lmao! Other than that, I'm not going to say anything more. lol. I WISH I WAS ROOTED AND HAD 1.4 INSTALLED WHEN I GOT MY PHONE! but no! it came with 1.5 and it took a year to figure out how to downgrade. lol. oh well. now they've figured everything out. can s-off with being on 1.5. love everyone on here. Anyway, DO NOT TAKE AN OTA!
I am not the greatest with these things. You are saying I need to unroot my phone for this to work? And I need to somehow get rid of the revolutionary recovery thing? I don't know what OTA means but I can see it's part of the file name. Is there a non-OTA version of it that I can use? For some reason a lot of ROM's don't work. I have hboot 1.5 with s-on and cynogenmod and a lot of ICS ROM's just hang on the HTC screen.
You are saying I need to unroot my phone for this to work? And I need to somehow get rid of the revolutionary recovery thing?
Click to expand...
Click to collapse
You don't need to unroot, but you need to lock your bootloader and get the stock recovery back to take the OTA. The easiest way to upgrade to ICS without doing all that is to flash the new firmware, then flash a stock rooted rom if you want to stay on the stock rom.
I don't know what OTA means but I can see it's part of the file name.
Click to expand...
Click to collapse
Over The Air, i.e. the update that Sprint sends out.
Is there a non-OTA version of it that I can use?
Click to expand...
Click to collapse
Upgrade firmware through bootloader, then flash a stock rooted rom or a custom rom based on ICS. If you want to use the new kernel, you will have to upgrade hboot as well, or you can keep your current hboot and use the VM leak kernel.
For some reason a lot of ROM's don't work.
Click to expand...
Click to collapse
Could be a number of reasons, you need the new firmware to run an ICS rom, and you need the new hboot if those roms use the new kernel.
I have hboot 1.5 with s-on and cynogenmod and a lot of ICS ROM's just hang on the HTC screen.
Click to expand...
Click to collapse
You can't flash kernels with s-on, so you will need to get s-off before you want to use an ICS rom.
Now that we have our own specific forum, would it be plausible to get some sort of step-by-step guide on how to go about installing the KitKat OTA if you're rooted? In browsing through the megathread from before, I get the impression that I will need to flash the stock recovery and relock my bootloader, then unlock once again once I've updated, but the thread itself is a bit daunting and the advice is pretty well scattered amid the various conversations there. Can we get some sort of consolidated guide from someone more knowledgeable than myself?
(Thank you in advance, by the way. I know I will be highly appreciative.)
groverXIII said:
Now that we have our own specific forum, would it be plausible to get some sort of step-by-step guide on how to go about installing the KitKat OTA if you're rooted? In browsing through the megathread from before, I get the impression that I will need to flash the stock recovery and relock my bootloader, then unlock once again once I've updated, but the thread itself is a bit daunting and the advice is pretty well scattered amid the various conversations there. Can we get some sort of consolidated guide from someone more knowledgeable than myself?
(Thank you in advance, by the way. I know I will be highly appreciative.)
Click to expand...
Click to collapse
This is what I followed, though you are going to lose data...
TehFlash said:
If you have the different partition layout that was introduced with the KitKat update, and also have the upgraded HBOOT then I guess i'll write up this guide. To get the phone back in proper working order, you need to do this.
1) Make sure you have the HTC drivers installed, and HTC Sync Manager fully uninstalled. ADB/Fastboot and such in working order, etc.
2) Download the KitKat OTA ZIP from Duir's Drive Folder here https://drive.google.com/uc?id=0B-kSF8g8H7KudEFRU1hPMjRObU0&export=download and open it up and take out firmware.zip
3) Get into HBOOT on the phone, and flash that firmware.zip file by running fastboot flash zip firmware.zip and also run fastboot flash update firmware.zip both will say FAIL but for me that worked if that didn't work then relock your device by running fastboot oem lock and then get back to fastboot and run fastboot oem rebootRUU (case-sensitive) and then issue fastboot flash zip firmware.zip and also run fastboot flash update firmware.zip and reboot to fastboot again
4) If you had to relock your device unlock it by getting your Unlock_code.bin from HTCdev and issue this command when you're in fastboot which is fastboot flash unlocktoken Unlock_code.bin
5) download Duir's TWRP recovery built for KitKat which is located here https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing grab the openrecovery-twrp-2.7.1.1-zaracl.img and then flash that by issuing fastboot flash recovery openrecovery-twrp-2.7.1.1-zaracl.img
6) Boot up into recovery, and format Data middle button on the right and type in 'Yes' and then wipe everything (you might have to reboot back into recovery again and then wipe everything) The reason to format Data using that button is because of KitKat remapping the partitions
7) Grab the KitKat TWRP backup from here https://docs.google.com/file/d/0B8-7I2_Vt73ldUNPd2c4X0xoQXc/edit
8) while that downloads make a pseudo backup, and then when thats finished mount your SDcard and open up the KitKat TWRP backup on windows and just overwrite all the files in zara_cl442/zara_cl442 and then reboot back into recovery again.
9) Restore the Backup you made and overwrote with the KitKat TWRP backup
10) go into fastboot and go back to Duir's drive located here https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing and grab KK_stock_boot.img and then flash that by issuing fastboot flash boot KK_stock_boot.img in a command prompt
11) Reboot into the System and it should work
Click to expand...
Click to collapse
Kit Kat OTA
That seems really complicated and sort of risky. Can't we just restore stock recovery and boot. Relock boot loader. And then install the ota as downloaded.
The_Greatest_Juan said:
That seems really complicated and sort of risky. Can't we just restore stock recovery and boot. Relock boot loader. And then install the ota as downloaded.
Click to expand...
Click to collapse
That's what I was wondering. I'm alright with re-rooting afterward (and after that I'm going S-OFF so I can use Viper4Android).
On a side note, has anyone noticed higher battery consumption with KitKat? My wife (who is unrooted and generally doesn't mess with her phone) updated and her battery died twice yesterday with no real increase in usage.
groverXIII said:
That's what I was wondering. I'm alright with re-rooting afterward (and after that I'm going S-OFF so I can use Viper4Android).
On a side note, has anyone noticed higher battery consumption with KitKat? My wife (who is unrooted and generally doesn't mess with her phone) updated and her battery died twice yesterday with no real increase in usage.
Click to expand...
Click to collapse
Get s-off first then update kk bec if things go wrong during the update u can downgrade hboot. With s-on u cant downgrade hboot. U get stuck and theres no way to fix ur device. Ive seen this happen to somebody
Child's Play said:
Get s-off first then update kk bec if things go wrong during the update u can downgrade hboot. With s-on u cant downgrade hboot. U get stuck and theres no way to fix ur device. Ive seen this happen to somebody
Click to expand...
Click to collapse
Good to know. Got a link to how to get S-OFF that would prevent me from searching through the massive thread?
groverXIII said:
Good to know. Got a link to how to get S-OFF that would prevent me from searching through the massive thread?
Click to expand...
Click to collapse
Read the instructions http://rumrunner.us/instructions/ then download rumrunner 0.5.0 under "htc universal downloads" and run it as administrator
The only thing I changed on my phone was gain root, unlock bootloader and flash Philz Touch cwm recovery. I haven't gotten s-off or changed H-boot. I don't want to change anything else if I don't have to. Is there anyway to get the update. I don't care if I lose root.
The_Greatest_Juan said:
The only thing I changed on my phone was gain root, unlock bootloader and flash Philz Touch cwm recovery. I haven't gotten s-off or changed H-boot. I don't want to change anything else if I don't have to. Is there anyway to get the update. I don't care if I lose root.
Click to expand...
Click to collapse
U should get s-off then flash stock recovery, unroot ur device and relock the bootloader then update kk by tapping "system updates" in settings or run the ruu to get everything back to stock. S-off wont be affected
Child's Play said:
U should get s-off then flash stock recovery, unroot ur device and relock the bootloader then update kk by tapping "system updates" in settings or run the ruu to get everything back to stock. S-off wont be affected
Click to expand...
Click to collapse
Alright I'll try that when I get home and let you know how it goes. Thanks a bunch.
Alright. So it didn't work. It works fine at first but at about 40% through the update it shows a red exclamation mark inside a red triangle on the phone. I unrooted and flashed the stock recovery from the development thread on the new forum. The jelly bean one. And relocked the
Bootloader. Ugh. This is really frustrating. What am I doing wrong? Do I have to get rid of s-off as well. That's fine if I do.
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
Alright. So it didn't work. It works fine at first but at about 40% through the update it shows a red exclamation mark inside a red triangle on the phone. I unrooted and flashed the stock recovery from the development thread on the new forum. The jelly bean one. And relocked the
Bootloader. Ugh. This is really frustrating. What am I doing wrong? Do I have to get rid of s-off as well. That's fine if I do.
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Did u delete the hcheck file when u got s-off?
Child's Play said:
Did u delete the hcheck file when u got s-off?
Click to expand...
Click to collapse
So I did not. Can you walk me through that please
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
So I did not. Can you walk me through that please
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Ok u didnt. Make sure everything is stock. Im not sure why its stuck at 40%
Child's Play said:
Ok u didnt. Make sure everything is stock. Im not sure why its stuck at 40%
Click to expand...
Click to collapse
So should I just run the RUU
Sent from my HTC0P4E1 using XDA Free mobile app
Some ppl had the same issue. There r instructions in the post. Whats the hboot version? Get into bootloader and tell me
Child's Play said:
Some ppl had the same issue. There r instructions in the post. Whats the hboot version? Get into bootloader and tell me
Click to expand...
Click to collapse
What post? The massive thread before we got a forum? My hboot is 2.22.0000
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
What post? The massive thread before we got a forum? My hboot is 2.22.0000
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. U r using kk. We need a guide for ur issue we dont have to look thru all posts. Im gonna post a thread
Child's Play said:
Yes. U r using kk. We need a guide for ur issue we dont have to look thru all posts. Im gonna post a thread
Click to expand...
Click to collapse
Ok so how do I fix it?
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
Ok so how do I fix it?
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure what u need to do. Somebody knows
someone please help
im not sure what part did the damage. but i was trying to flash a new rom. it screwed up. didnt work. kept trying a few things. but long story short i accidently formated my external containing my back up, and nothing else worked on my phone.
end result, phones not recognized by Adb but can be seen on fastboot it has no OS and somehow its now S-ON and im stuck with out a phone.
i just redownloaded all my sprint drivers, sdk including, also have a fresh version of htc sync manager.
im lost. dont know what to do. this is my last resort till smash it and claim insurance
sirbrixalot said:
someone please help
im not sure what part did the damage. but i was trying to flash a new rom. it screwed up. didnt work. kept trying a few things. but long story short i accidently formated my external containing my back up, and nothing else worked on my phone.
end result, phones not recognized by Adb but can be seen on fastboot it has no OS and somehow its now S-ON and im stuck with out a phone.
i just redownloaded all my sprint drivers, sdk including, also have a fresh version of htc sync manager.
im lost. dont know what to do. this is my last resort till smash it and claim insurance
Click to expand...
Click to collapse
What os and firmware version? Its fixable dude.
dottat said:
What os and firmware version? Its fixable dude.
Click to expand...
Click to collapse
honestly, im not even sure, im not wicked unto this stuff, just want a functioning phone. i was trying to get a better radio driver.
but as of right now, i just want this back to stock.
sirbrixalot said:
honestly, im not even sure, im not wicked unto this stuff, just want a functioning phone. i was trying to get a better radio driver.
but as of right now, i just want this back to stock.
Click to expand...
Click to collapse
What is your availability tomorrow morning for a team viewer session?
dottat said:
What is your availability tomorrow morning for a team viewer session?
Click to expand...
Click to collapse
morning is zero. i have to work from 6-2 eastern time. what do you suspect that i ****ed up so aybe i can look. id gladly do a team view tho
sirbrixalot said:
morning is zero. i have to work from 6-2 eastern time. what do you suspect that i ****ed up so aybe i can look. id gladly do a team view tho
Click to expand...
Click to collapse
Well...since you are Sprint you probably unlocked via HTC dev. You can flash your unlock token again which will allow you to flash a custom recovery. You can then flash the current rooted Rom and use sunshine to s off again. The hard option is flashing an older Rom to use firewater as doing so will make your phone reboot about every thirty seconds because of the firmware mismatch. I can help you get it done that way if you want...up to you. Six of one half dozen of the other. You can almost always fix a phone that still boots to hboot and is unlockable. You won't have adb in the current mode either btw....
dottat said:
Well...since you are Sprint you probably unlocked via HTC dev. You can flash your unlock token again which will allow you to flash a custom recovery. You can then flash the current rooted Rom and use sunshine to s off again. The hard option is flashing an older Rom to use firewater as doing so will make your phone reboot about every thirty seconds becaui se of the firmware mismatch. I can help you get it done that way if you want...up to you. Six of one half dozen of the other. You can almost always fix a phone that still boots to hboot and is unlockable. You won't have adb in the current mode either btw....
Click to expand...
Click to collapse
i noticed adb wont work. lol'
i already used anothe runlock token, but it wouldnt take another rom how ever, i tried the guru reset via twrp install and a maximushd rom. neither of which took, im lost man, exhaused my options in my knowlage base, i need help; i eventried a ruu.exe but it wouldnt take due to some kind of unknown error. and tried a ruu hboot flash of the same **** and that didnt keep either
sirbrixalot said:
i noticed adb wont work. lol'
i already used anothe runlock token, but it wouldnt take another rom how ever, i tried the guru reset via twrp install and a maximushd rom. neither of which took, im lost man, exhaused my options in my knowlage base, i need help; i eventried a ruu.exe but it wouldnt take due to some kind of unknown error. and tried a ruu hboot flash of the same **** and that didnt keep either
Click to expand...
Click to collapse
You are on the current firmware... So you would need a current ruu to do that. Does your phone show unlocked now?
sirbrixalot said:
i noticed adb wont work. lol'
i already used anothe runlock token, but it wouldnt take another rom how ever, i tried the guru reset via twrp install and a maximushd rom. neither of which took, im lost man, exhaused my options in my knowlage base, i need help; i eventried a ruu.exe but it wouldnt take due to some kind of unknown error. and tried a ruu hboot flash of the same **** and that didnt keep either
Click to expand...
Click to collapse
hi
if you're bootloader showing unlocked try to install twrp recovery image
and then try to download stock nandroid rom for you're Sprint mobile then place it in you're mobile using adb push command then restore the the rom that you have placed at the end flash the image boot from the bootloader and you're done.
dottat said:
You are on the current firmware... So you would need a current ruu to do that. Does your phone show unlocked now?
Click to expand...
Click to collapse
yeah im fairly sure it says unlocked and tampered at the top of hboot, and it also says s-on some how. i tried fastboot command oem unluck and that didnt change it, i feel like this s-on nonsense is my main problem.
sirbrixalot said:
yeah im fairly sure it says unlocked and tampered at the top of hboot, and it also says s-on some how. i tried fastboot command oem unluck and that didnt change it, i feel like this s-on nonsense is my main problem.
Click to expand...
Click to collapse
Flash this. Let me know.
https://www.androidfilehost.com/?fid=23486521113837641
ahmedj31 said:
hi
if you're bootloader showing unlocked try to install twrp recovery image
and then try to download stock nandroid rom for you're Sprint mobile then place it in you're mobile using adb push command then restore the the rom that you have placed at the end flash the image boot from the bootloader and you're done.
Click to expand...
Click to collapse
hi friend,
if you had read the above posts you would know i dont have adb suppot thanks tho
dottat said:
Flash this. Let me know.
https://www.androidfilehost.com/?fid=23486521113837641[/
how should i go about it? twrp?
Click to expand...
Click to collapse
sirbrixalot said:
dottat said:
Flash this. Let me know.
https://www.androidfilehost.com/?fid=23486521113837641[/
how should i go about it? twrp?
Click to expand...
Click to collapse
Twrp
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
Twrp
Click to expand...
Click to collapse
tried that just now. it only said fail, no reason.
Click to expand...
Click to collapse
sirbrixalot said:
dottat said:
tried that just now. it only said fail, no reason.
Click to expand...
Click to collapse
What version twrp do you have and what did you do prior to flashing in twrp (wipe etc)?
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
What version twrp do you have and what did you do prior to flashing in twrp (wipe etc)?
Click to expand...
Click to collapse
i thinki just got a new version. 2.8.0.1 and i tried a wipe and cache wipe and allthat jazzz
Click to expand...
Click to collapse
sirbrixalot said:
dottat said:
i thinki just got a new version. 2.8.0.1 and i tried a wipe and cache wipe and allthat jazzz
Click to expand...
Click to collapse
Don't wipe system especially. Reboot to boot loader. Choose reboot boot loader. Go back into recovery and flash. Don't wipe anything
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
Don't wipe system especially. Reboot to boot loader. Choose reboot boot loader. Go back into recovery and flash. Don't wipe anything
Click to expand...
Click to collapse
says unable to open zip file on that try
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
Don't wipe system especially. Reboot to boot loader. Choose reboot boot loader. Go back into recovery and flash. Don't wipe anything
Click to expand...
Click to collapse
i got a hammer on one hand and my laptop(s) in the other. this hammer idea is looking pretty good hahaha
Click to expand...
Click to collapse