Related
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
Just flash the correct one like you flashed the wrong one. The boot loader does not and should not be relocked, it should be unlocked.
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
is all you flashed, the boot.img or did you flash leedroid too? If you flashed leedroid then do the following:
plug it in to USB while it bootloops type adb reboot recovery
from there you can access your nandroid backup assuming you made one.
if you didn't make a backup then yeah you'll have to flash the 1.85 RUU. To do this, relock the bootloader from adb fastboot oem lock
run the RUU unlock the bootloader then install your recovery and push root files via recovery.
Much easier than having to re-root 1.85 with the new exploit etc.
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
mbh87 said:
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
Click to expand...
Click to collapse
I keep forgetting we have adb through recovery now. Good call. But do we have USB?
Latest TWRP is suppose to have both ADB and USB
You should always back up
Sent from my HTC One XL using Tapatalk 2
kkoshko1 said:
You should always back up
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Amen.
nandroid is always my first step when flashing a ROM
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
mbh87 said:
Latest TWRP is suppose to have both ADB and USB
Click to expand...
Click to collapse
I didn't see any need in backing up because I assumed all would go well and also I don't have any data on here that I want. Lesson learned well though. I will always back up. Now I've gotta get it working...
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
kkoshko1 said:
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thats actually why I re-locked. I've read that before installing an ruu, you need to re-lock.
I can get to fastboot. I tried to unlock via fastboot but it quickly timesout. I'm currently downloading 1.85 .exe ruu. I will give that a try as soon as its done downloading unless you guys have a better idea.
rohan32 said:
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
Click to expand...
Click to collapse
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
shgadwa said:
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
gunnyman said:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
shgadwa said:
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
Click to expand...
Click to collapse
Link is correct. Pay attention to the subforum. It specifically says AT&T One X, if that is the section you are in.
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
smokin1337 said:
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
Click to expand...
Click to collapse
Thank you. I do know how to get into hboot. I flashed boot.img and it is now working!
NVM saw your edit lol...
I got my HOX about 2 weeks now. I really want to flash it with a custom Rom. Tried lots of rooting instructions with no success. Phone is now back to factory reset using RRU method. I got the bootloader unlock. No success loading Clockworkmod on boatloader recovery.
sherwinator said:
I got my HOX about 2 weeks now. I really want to flash it with a custom Rom. Tried lots of rooting instructions with no success. Phone is now back to factory reset using RRU method. I got the bootloader unlock. No success loading Clockworkmod on boatloader recovery.
Click to expand...
Click to collapse
I have the same issue but it says my phone says it is tapered. I want to go back to stock at least. What instructions did you follow for that?
ironnik said:
I have the same issue but it says my phone says it is tapered. I want to go back to stock at least. What instructions did you follow for that?
Click to expand...
Click to collapse
not sure how to remove the "tampered" status but i got it back to stock using RRU method and load a stock Rogers Rom. you need to re-lock it before using RRU. my status now is Tampered and Relock.
sherwinator said:
not sure how to remove the "tampered" status but i got it back to stock using RRU method and load a stock Rogers Rom. you need to re-lock it before using RRU. my status now is Tampered and Relock.
Click to expand...
Click to collapse
Did you use the 1.94 RUU or did you try to Flash the 1.73 original?
You must root on 1.85. Scripts don't work on any other version.
XNine said:
You must root on 1.85. Scripts don't work on any other version.
Click to expand...
Click to collapse
Can I just use RRU to go back to 1.85? Please attach a link.
Thanks
ericth18 said:
Best way to root at this moment would be to unlock your bootloader using HTCDEV and flash TWRP recovery and then flash CleanRom 4.5 which will give you root as long as you kepp that rom on your phone. There could be other roms out there that will give you root access but I've flashed a few and CleanRom 4.5 was the only one that got me rooted. Until they come up with a way to perm root on 1.94 I suggest using this method.
Click to expand...
Click to collapse
If your bootloader is unlocked, you can root with any ROM.
If you unlock and flash a recovery-
fastboot flash recovery nameofrecovery.img
and you cant get it to boot the custom recovery heres the trick, after you flash the recovery type
fastboot boot nameofrecovery.img
Butters619 said:
If your bootloader is unlocked, you can root with any ROM.
Click to expand...
Click to collapse
If this is true, then why can't anyone root their 2.2x phones?
thechilipepper said:
If this is true, then why can't anyone root their 2.2x phones?
Click to expand...
Click to collapse
Cuz att doesn't let us bl unlock our phone HTC dev blocks our cid
Whyyyy is this in general? Please keep all question/help threads in the Q&A section only. Thank you.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Hi I recently obtained a bunch of free smart phones via my job at t-mobile and people upgrading and just not wanting their old smart phones. One of them was a HTC sensation. I have rooted many phones for years now but this one wants to give me issues. I rooted it, got super user installed and CWM recovery and installed jellybean. When it boots into CM10 it never gets past the boot screen. In HBOOT it says son rl HBOOT 1.27.0000. I cannot for the life of me figure out what is wrong. I did a full wipe and everything. Lucky for me this is a play phone but I still would like to get it up and running. If anyone could please help me figure this out. Thank you
First, please do not post questions in the dev section.
Second, you're s-on so you have to flash your boot.img through fastboot. The boot partition is protected with s-on...
And where do I obtain the boot.img? Sorry for posting here I guess nobody had a problem with it in the DINC forums.
GROGG88 said:
First, please do not post questions in the dev section.
Second, you're s-on so you have to flash your boot.img through fastboot. The boot partition is protected with s-on...
Click to expand...
Click to collapse
wetbo529 said:
And where do I obtain the boot.img? Sorry for posting here I guess nobody had a problem with it in the DINC forums.
Click to expand...
Click to collapse
Extract it from your rom.
Ok I did that and when I go into HBOOT how do I flash it? Sorry again for the noob question and thank you for all your help?
GROGG88 said:
Extract it from your rom.
Click to expand...
Click to collapse
wetbo529 said:
Ok I did that and when I go into HBOOT how do I flash it? Sorry again for the noob question and thank you for all your help?
Click to expand...
Click to collapse
First get familiar with fastboot commands: http://wiki.cyanogenmod.com/wiki/Fastboot
You'll need adb and fastboot setup on your computer and you'll use the following command from terminal or cmd prompt:
Code:
fastboot flash boot /path/to/<boot>.img
Your other option is to flash a rom that uses the stock boot image. There are two TMOUS based roms to choose from: mine, or ARHD.
Have you update to Firmwaer 3.33?
/ Sent from my Sensation XE /
lol
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
I have at&t inspire 4g and I unlocked the bootlaoder by EasyAceRootTool and I have read many guides how to downgrade to 1.3 and how to get s-off and eng-off to instill leedroid
and these are the sites which I tried
http://www.addictivetips.com/mobile/install-leedroid-android-rom-on-the-htc-desire-hd-inspire-4g/
http://forum.xda-developers.com/showthread.php?t=905003
http://androidforums.com/inspire-4g...ally-downgrade-root-inspire-4g-desire-hd.html.
I attached the information about my at&t inspire 4g in the attachment files
You don't need S-Off to flash a custom ROM; an unlocked bootloader and a custom recovery is sufficient. More details instructions in the Ace Think Tank thread linked in my signature.
EDIT: why did you start two threads within a couple hours??
thanx but
bananagranola said:
You don't need S-Off to flash a custom ROM; an unlocked bootloader and a custom recovery is sufficient. More details instructions in the Ace Think Tank thread linked in my signature.
EDIT: why did you start two threads within a couple hours??
Click to expand...
Click to collapse
I'm lost cuz I read alot in many sites about how can I flash a custom rom and I faild to do it cuz almost pf the sites I read them . there are many missing files.and I'm new in theses things
plz
1- I have downloaded this rom and I want to instill it in my fone leedroid 2.2.2 in my fone
Can I download it
if so plz tell me the steps to do it
2- how can I make my fone works in another carrier
I will be thankful for you
I will delete the other thread
Like I said. Read the Ace Think Tank thread.
Hint: you need to flash a recovery from fastboot, then flash a ROM from recovery, then flash a boot.img from fastboot. And for carrier compatibility, you need to read the manual S-Off portion.
Inspire 4g update problem
Hello, I have an htc inspire 4g running OS 2.3.3 Gingerbread and I want to root it so I can flash custom rom but I need to downgrade the firmware first or else it wont work.
Other problem facing me is this that I need to flash in pd98img but when unfortunately bootloader is locked in my opinion because it is not detecting the img file.
When I tried to unlock the bootloader it says hboot update needed.
I need to know that how can I update the hboot of HTC inspire 4g.
I would be really thankful if I get a solution
rafayahmed said:
Hello, I have an htc inspire 4g running OS 2.3.3 Gingerbread and I want to root it so I can flash custom rom but I need to downgrade the firmware first or else it wont work.
Other problem facing me is this that I need to flash in pd98img but when unfortunately bootloader is locked in my opinion because it is not detecting the img file.
When I tried to unlock the bootloader it says hboot update needed.
I need to know that how can I update the hboot of HTC inspire 4g.
I would be really thankful if I get a solution
Click to expand...
Click to collapse
Run a RUU that supports bootloader unlocking. If you do this with a PD98IMG.zip you need to put the file in the root of the SD card and name the zip exactly that.
Thanks for the reply.
I really appreciate it but please can you provide me with the link of the RUU because I was unable to find such RUU after several attempts.
thanx but
bananagranola said:
Like I said. Read the Ace Think Tank thread.
Hint: you need to flash a recovery from fastboot, then flash a ROM from recovery, then flash a boot.img from fastboot. And for carrier compatibility, you need to read the manual S-Off portion.
Click to expand...
Click to collapse
this manual for high level and I'm new .could you plz help me with s-off
and I have to tell ya that I'ev tried to flash the the rom which I told ya and it says its 2.0.0
I want 2 ask ya f I flash it after I do adb fast boot for the boot.img of course before I do s-off that wont brick the fone
2- when I tried to flash the rom and it stuck in the splash screen so I did restore and I noticed that bettery is 10% from 100%
what does that mean?
rafayahmed said:
Thanks for the reply.
I really appreciate it but please can you provide me with the link of the RUU because I was unable to find such RUU after several attempts.
Click to expand...
Click to collapse
Your RUU depends on which DHD software version you are running. If you can't find one you need to make s gold card and flash another version's RUU.
sicoooo0 said:
this manual for high level and I'm new .could you plz help me with s-off
and I have to tell ya that I'ev tried to flash the the rom which I told ya and it says its 2.0.0
I want 2 ask ya f I flash it after I do adb fast boot for the boot.img of course before I do s-off that wont brick the fone
2- when I tried to flash the rom and it stuck in the splash screen so I did restore and I noticed that bettery is 10% from 100%
what does that mean?
Click to expand...
Click to collapse
Why are you trying to get S-Off? I'm not willing to help other people with the manual S-Off method because I haven't done it personally and it's a method meant for advanced users who don't need help anyway; if you need help I advise that you stick to just unlocking your bootloader.
ADB and fastboot are two separate things. You can fastboot flash the boot.img without bricking the phone, yes. My signature has instructions for flashing the boot.img.
If the battery level fell, it fell...flashing stuff takes a lot of power. If you let it hang on the splash for awhile I could see it dropping 90%.
bananagranola said:
Your RUU depends on which DHD software version you are running. If you can't find one you need to make s gold card and flash another version's RUU.
Why are you trying to get S-Off? I'm not willing to help other people with the manual S-Off method because I haven't done it personally and it's a method meant for advanced users who don't need help anyway; if you need help I advise that you stick to just unlocking your bootloader.
ADB and fastboot are two separate things. You can fastboot flash the boot.img without bricking the phone, yes. My signature has instructions for flashing the boot.img.
If the battery level fell, it fell...flashing stuff takes a lot of power. If you let it hang on the splash for awhile I could see it dropping 90%.
Click to expand...
Click to collapse
how minutes it takes in the first boot after flashin the new rom
and why ya didnt answer me about this rom leedroid ,can I instill it without downgrade or anything else
sicoooo0 said:
how minutes it takes in the first boot after flashin the new rom
and why ya didnt answer me about this rom leedroid ,can I instill it without downgrade or anything else
Click to expand...
Click to collapse
If it takes more than a minute, you probably didn't flash the boot.img.
Because I didn't understand the question. And still don't. With an unlocked bootloader and a custom recovery, the procedure for flashing all ROMs is the same.
thanx
bananagranola said:
If it takes more than a minute, you probably didn't flash the boot.img.
Because I didn't understand the question. And still don't. With an unlocked bootloader and a custom recovery, the procedure for flashing all ROMs is the same.
Click to expand...
Click to collapse
forget what I asked . I have instilled leedroid2.2.2 and there is no network
sicoooo0 said:
forget what I asked . I have instilled leedroid2.2.2 and there is no network
Click to expand...
Click to collapse
Um...LeeDroid has network. Did you full wipe?
Another Problem
Hello, Now I am facing another problem.
The AAHK says that I have to downgrade my radio through flashing PD98IMG.ZIP but my bootloader is not detecting the file.
The effen-manual says that I have to relock my bootloader.
Now I am not sure that currently my bootloader is locked or unlocked? or else should I have to unlock it first through HTCDev and then relock it?
Please it has been 4 months I am trying to root but I couldnt find a solution.
rafayahmed said:
Hello, Now I am facing another problem.
The AAHK says that I have to downgrade my radio through flashing PD98IMG.ZIP but my bootloader is not detecting the file.
The effen-manual says that I have to relock my bootloader.
Now I am not sure that currently my bootloader is locked or unlocked? or else should I have to unlock it first through HTCDev and then relock it?
Please it has been 4 months I am trying to root but I couldnt find a solution.
Click to expand...
Click to collapse
AAHK is retired and unsupported. Just unlock the bootloader and fastboot flash a recovery. Then flash a ROM from recovery.