Related
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
mapko11 said:
I got myself into a interesting situation. A quick answer would be greatly appreciated:
1. I'm rooted.
2. Trying to install the OTA so I can run 2.2 the right way.
3. I started a thread asking for help because I was confused on unrooting my phone. Didn't get much help, a quick flame, and last someone chimed in to install the OTA from Rom Manager. I asked if I could do this with Root and the thread was killed.
4. I did. The boot screen was the new one. But the radio wasn't updated.
5. I then attempted to unroot my phone. Followed the PB31IMG.zip method. Phone booted normally. Root was lost.
6. This is where I am now.
7. My question is, if I install the OTA now renamed update.zip on my SD card, will I run the chance of bricking my phone because I installed it once from Rom Manager while I had root (#3/#4)??????
Please advise so I don't MOD EDIT up my phone.................
And if you're going to flame and insist I should of just followed the 2.2 leak instructions, you're correct. But I took someone's quick answer and tried it assuming they knew a better method.
Click to expand...
Click to collapse
Wat is the hboot versoin?
Sent from my Incredible using XDA App
Where do I find that out?
mapko11 said:
Where do I find that out?
Click to expand...
Click to collapse
In the bootloader it should say.
Sent from my Incredible using XDA App
Hboot-0.79.0000
mapko11 said:
2. Trying to install the OTA so I can run 2.2 the right way.
Click to expand...
Click to collapse
Well, "the right way" would be to wait for the actual OTA. Verizon would also have your back if you brick. But, anyway...
If you're still on the 1.00.03.04.06 radio, you can probably follow the instructions in that thread now that you've flashed back to the stock ROM. However, there still seem to be a few cases of people bricking their phones or being stuck in a bootloop after flashing leaks.
If you are confused/concerned/afraid of bricks then you just shouldn't flash the leaked OTA. This is not a flame, this is sound advice. Wait for the real one.
I'm fine with flashing. I just keep hearing about this "double install OTA and brick your phone" issue and I'm trying to avoid doing that. If the one guy didn't chime in with the suggestion to use ROM Manager, I wouldn't of had this issue.
My radio is still 1.00.03.04.06. I just want to make sure I don't run a risk of bricking.
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
jdkoreclipse said:
If the hboot updated, i would say not to apply again. If it didnt update then i would say to see what happens, but dont take my word for it 100%
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
How do I know if the HBOOT has been updated? I posted my version above?
mapko11 said:
How do I know if the HBOOT has been updated? I posted my version above?
Click to expand...
Click to collapse
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Anyway to undo this and go back?
mapko11 said:
Anyway to undo this and go back?
Click to expand...
Click to collapse
Try the PB13IMG.
Sent from my Incredible using XDA App
jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
And you needed to un root before applying the ota
Sent from my Incredible using XDA App
jdkoreclipse said:
The 79 hboot is the updated one. I would use caution in re flashing the ota.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May, and she sure as hell didn't have no 720p camcorder. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
But absolutely, running the PB13IMG should ensure that he's as far back as he can go, so why not try it just to be safe...
jdkoreclipse said:
Try the PB13IMG.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
That's what I just did before I posted this thread. I installed the PB13IMG and restored everything back to stock. You asked about the HBOOT version and that's .79. I'm comfortable flashing and doing the update. What should HBOOT say? Has anyone successfully updated the OTA from .79 HBOOT?
Thank you for the help. Sorry for the questions. I completely comfortable with rooting, flashing roms, and kernals. This is going back to unroot stock is just new.
I want to install the OTA and I'm good to go. Just making sure it's safe now....
alexdw369 said:
I personally have had a .77 HBOOT since I got my phone in April. My mom's phone, on the other hand, had the .79, which she has had since May. I don't think that the OP's phone having .79 means with any certainty that the OTA already applied once. I think the radio version listed on the HBOOT screen would be a better indicator.
Click to expand...
Click to collapse
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
jdkoreclipse said:
Thats a high possibility that hboot means nothing in this scenaroi, but im not gonn. Be risky with someome elses phone. I only provide methods of doing things that i would use on my phone too.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
alexdw369 said:
Agreed, however, I noticed after running the PB13IMG, my HBOOT was also .79, which could have only come from the PB13IMG since I hadn't tried to do the OTA yet. Just trying to add pieces to the puzzle to get a better picture for future reference...I'm sure this guy wont be the last to ask...
Click to expand...
Click to collapse
I appreciate the help guys. I guess my question would be if I ran PB13IMG, lost my root, back to stock, my HBOOT is .79 and my radio is still 1.00.03.04.06 and not 2.05.00.06.11, I should be at the same point as everyone else for installing the OTA from my SD card. Right or wrong?
When you read these threads and people are installing the OTA twice and bricking, are they installing the OTA again when the radio is already updated to 2.05.00.06.11?
Yep. I think you can flash it again, but be real cautious, as this is your second time flashing it, but if the radio is still the old versoin, you should be safe.
Sent from my Incredible using XDA App
The phone is the incredible 2
I have somewhat of a recent update my phone is running 2.3.4.
I did see the tread about rooting only if your running 2.3.3, I did not read all 24 pages to find out if there is any info on there about rooting newer updates.
Lino. said:
The phone is the incredible 2
I have somewhat of a recent update my phone is running 2.3.4.
I did see the tread about rooting only if your running 2.3.3, I did not read all 24 pages to find out if there is any info on there about rooting newer updates.
Click to expand...
Click to collapse
if hboot version is 0.98 theres no software root available right now. only way right now is xtc clip
Sent from my Incredible 2 using XDA App
How would I know the hboot version?
Turn the phone off, then turn it back on while pressing the volume down button.
If your Hboot version is .97 then great you can still root. If it is .98 then great you have an opportunity to read up and become more familiar with your device before rooting. I would recommend reading through a step by step guide on how to root and install cwm on your phone. It will be a little abstract since you won't be actually performing the steps but it is good to know what you are getting into.
Sent from my Incredible 2 using Tapatalk
Skyboxer1968 said:
Turn the phone off, then turn it back on while pressing the volume down button.
If your Hboot version is .97 then great you can still root. If it is .98 then great you have an opportunity to read up and become more familiar with your device before rooting. I would recommend reading through a step by step guide on how to root and install cwm on your phone. It will be a little abstract since you won't be actually performing the steps but it is good to know what you are getting into.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
I was gonna "let me Google that for you" lol
Sent from my Incredible 2 using xda premium
OK, I tried holding down the volume and powering up, and boots up normal.
This is bad right.
Did you turn fastboot off in power settings??
Sent from my rooted MIUI Dinc2
my hboot is 6.13.1002 is that correct ? i didnt root the phone i got it like that but i was considering about going back to complete stock and reroot and everything else !
ghostv7142 said:
my hboot is 6.13.1002 is that correct ? i didnt root the phone i got it like that but i was considering about going back to complete stock and reroot and everything else !
Click to expand...
Click to collapse
6.13.1002??????
ghostv7142 said:
my hboot is 6.13.1002 is that correct ? i didnt root the phone i got it like that but i was considering about going back to complete stock and reroot and everything else !
Click to expand...
Click to collapse
that means you got a CLNR that was returned s-off and never put back s-on before being sent back.
Sent from my Incredible 2 using XDA App
andybones said:
6.13.1002??????
Click to expand...
Click to collapse
thats the hboot you get after running revolutionary. same as mine
Sent from my ADR6350 using xda premium
What are the next steps in rooting? Follow the usual using Revolutionary? Install CWM manually?
Would appreciate your help folks!
Thanks
Agreed! With the bootlaoder now unlocked, what are the steps to rooting this beast? Do we still need to downgrade? Please pardon my noobness.
You wouldn't need to downgrade, I do know that. But as far as the rest, Idk. I did mine with revolutionary a while back before the 2.3.4 update, so I've been kicking ever since.
Sent from my Mikrunny'd Superphone using Forum Runner
I would see if you can install superuser from the market.
EDIT: I would also see if you can install CWM and ROM manager. If all those install ok you should be able to load a custom ROM.
HogFan77 said:
Agreed! With the bootlaoder now unlocked, what are the steps to rooting this beast? Do we still need to downgrade? Please pardon my noobness.
Click to expand...
Click to collapse
You do not have to downgrade if you unlocked. You should be able to install a new recovery image like Clockwork.
valorian13 said:
I would see if you can install superuser from the market.
EDIT: I would also see if you can install CWM and ROM manager. If all those install ok you should be able to load a custom ROM.
Click to expand...
Click to collapse
An unlocked bootloader does not equal root.
iNcorruptible said:
What are the next steps in rooting? Follow the usual using Revolutionary? Install CWM manually?
Would appreciate your help folks!
Thanks
Click to expand...
Click to collapse
I am in the same dilema....
---------- Post added at 10:19 PM ---------- Previous post was at 10:12 PM ----------
mza929 said:
I am in the same dilema....
Click to expand...
Click to collapse
This may point us in the right direction;
http://forum.xda-developers.com/showthread.php?t=1239821
If I run this, and unlock my incREDible2, what are my next steps to flashing/running some CM7.1 love? TIA
Installed CWM 5.0, superuser and after wiping data/cache and flashing a rom... Stuck at HTC White screen!
Flashed several roms, can't get passed it.
It's frustrating... No idea what to do next. I'm going to try flashing an earlier version of CWM and retry flashing a ROM.
Will update with progress.
iNcorruptible said:
Installed CWM 5.0, superuser and after wiping data/cache and flashing a rom... Stuck at HTC White screen!
Flashed several roms, can't get passed it.
It's frustrating... No idea what to do next. I'm going to try flashing an earlier version of CWM and retry flashing a ROM.
Will update with progress.
Click to expand...
Click to collapse
How long are you waiting bro..?
First. You should have not used the htcdev garbage. You should have used revolutionary.
That is all.
Sorry I can't help you. I use a ns4g. And that's all I know about the htcdev unlocker
Sent from my Nexus S 4G using XDA App
Over 30 minutes. Also tried flashing older version of CWM. Did not work. Will try restoring to stock with PG32IMG
Tried flashing back RUU, PB32IMG. Failed. Still stuck at HTC White screen. So much for unlocking the bootloader! No idea what to do next... help!
iNcorruptible said:
Tried flashing back RUU, PB32IMG. Failed. Still stuck at HTC White screen. So much for unlocking the bootloader! No idea what to do next... help!
Click to expand...
Click to collapse
When you flash a custom ROM from CWM on an unlocked HBOOT, you then need to manually extract the boot.img from the custom ROM zip file and manually flash it in Fastboot mode using the command
Fastboot flash boot [path to the boot.img file]
This has been documented multiple times in this forum.
tpbklake said:
When you flash a custom ROM from CWM on an unlocked HBOOT, you then need to manually extract the boot.img from the custom ROM zip file and manually flash it in Fastboot mode using the command
Fastboot flash boot [path to the boot.img file]
This has been documented multiple times in this forum.
Click to expand...
Click to collapse
thank you, i ran into the same problem....this worked
Appreciated. Tried it, didn't work Any other suggestions?
iNcorruptible said:
Appreciated. Tried it, didn't work Any other suggestions?
Click to expand...
Click to collapse
Yes in your case you will need to relock the bootloader in order to flash the RUU/PG32IMG.zip file. You cannot flash a RUU on an unlocked bootloader.
I'm guessing you guys have something other than .98 hboot? I'll find out soon when my wifes replacement comes in but I was not intending to use the HTC unlocker if I didn't have to. I was planning to try the tool attn1 has posted in the dev section unless the hboot changed with the ota.
Sent from my ADR6350 using xda premium
CondemnedSoul said:
I'm guessing you guys have something other than .98 hboot? I'll find out soon when my wifes replacement comes in but I was not intending to use the HTC unlocker if I didn't have to. I was planning to try the tool attn1 has posted in the dev section unless the hboot changed with the ota.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Still at Hboot 0.98!
iNcorruptible said:
Still at Hboot 0.98!
Click to expand...
Click to collapse
Good to hear kinda thought it was. I'll be using the method attn1 has posted then. I don't trust the unlock method through HTC for one main reason which is this... Unlocking bootloader and rooting voids warranty as we all know. So what happens when HTC knows your bootloader was unlocked because you used their tool and they have the serial number?
Sent from my ADR6350 using xda premium
Hi let me start off saying ive been on forum for a while so im not a noob with research or reading.
my problem is im now one of the group who are having infinite bootloop (htc white splash screen to black blankness back to splash screen. my phone was rooted by unrevoked method, soff hboot 2.18 radio 2.15.00.12.19.
steps I've tried:
taking out battery and replacing
hboot into recovery. usually takes me out of bootloop.
redoing smelkus recovery which allowed me to get to recovery for 5 seconds then back to bootloop.
then i tried 4.67 RUU for my radio version. 1st time i ran it the only thing changed was my phone is locked however its still s-off? I've tried RUU 3x each time program says successful but still bootloop and still soff.
does anyone see a step i missed? have any suggestions? I've read on this forum and a few others about the bootloop headache. would returning to soff then unrooting work? or flashing to different radio and RUU version?
thanks in advance
i want my og back. :what::screwy:
Sent from my VM670 using XDA
Sent from my VM670 using XDA
dtowngs4g said:
Hi let me start off saying ive been on forum for a while so im not a noob with research or reading.
my problem is im now one of the group who are having infinite bootloop (htc white splash screen to black blankness back to splash screen. my phone was rooted by unrevoked method, soff hboot 2.18 radio 2.15.00.12.19.
steps I've tried:
taking out battery and replacing
hboot into recovery. usually takes me out of bootloop.
redoing smelkus recovery which allowed me to get to recovery for 5 seconds then back to bootloop.
then i tried 4.67 RUU for my radio version. 1st time i ran it the only thing changed was my phone is locked however its still s-off? I've tried RUU 3x each time program says successful but still bootloop and still soff.
does anyone see a step i missed? have any suggestions? I've read on this forum and a few others about the bootloop headache. would returning to soff then unrooting work? or flashing to different radio and RUU version?
thanks in advance
i want my og back. :what::screwy:
Sent from my VM670 using XDA
Sent from my VM670 using XDA
Click to expand...
Click to collapse
Have you tried wiping everything,except your sd card, then flashing a new rom? Like CM7 as an example?
i cant get into recovery. i did clear storage from hboot screen
Sent from my VM670 using XDA
Try flashing another recovery.
This happens often.
Use amonra its in the link below
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Crossrocker said:
Try flashing another recovery.
This happens often.
Use amonra its in the link below
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Click to expand...
Click to collapse
I'll try this 1. thanks
Sent from my VM670 using XDA
Or if you can, move all ur files on a computer and do a full SD card format...works for me all the time unless ur SD card is unsalvageble.
Using Awesome Expressed EVO XDA Craziness!
formatted sd cars last week. tried captains s*on method everything changes but s-off and bootloop.
Sent from my VM670 using XDA
dtowngs4g said:
formatted sd cars last week. tried captains s*on method everything changes but s-off and bootloop.
Sent from my VM670 using XDA
Click to expand...
Click to collapse
Did you try flashing recovery from bootloader?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Crossrocker said:
Did you try flashing recovery from bootloader?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Click to expand...
Click to collapse
yep. back to researching more. :banghead:
Sent from my VM670 using XDA
dtowngs4g said:
yep. back to researching more. :banghead:
Sent from my VM670 using XDA
Click to expand...
Click to collapse
No I think that should be your solution. Because if my solution didn't work your pretty much screwed.
Tell me what happened when you put the amonra file on the root of your SD card and flashed from bootloader.
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
i think when ruu locked bootloader it's keeping me from getting recovery. i tried captains method to unroot but need to unlock and see if that does the trick
Sent from my VM670 using XDA
dtowngs4g said:
i think when ruu locked bootloader it's keeping me from getting recovery. i tried captains method to unroot but need to unlock and see if that does the trick
Sent from my VM670 using XDA
Click to expand...
Click to collapse
Well remember for next time. You didnt have to wipe anything, all you needed to do was flash a new recovery.
Is flashing an ruu not fixing it for you?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
no it only locked my bootloader. in process of trying to unlock again
Sent from my VM670 using XDA
dtowngs4g said:
no it only locked my bootloader. in process of trying to unlock again
Sent from my VM670 using XDA
Click to expand...
Click to collapse
So your phone is s-on, but it wont boot up?
Take it to sprint and act dum dum
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Try the RUU
I know you said you tried it but I remember having similar issue a while back when I was trying to update the wimax. I had to boot to windows and run the RUU. You might have installed the htc drivers or htc sync on your computer, reinstall all of them, reboot your computer and run the RUU tool. Good luck dude
dtowngs4g said:
no it only locked my bootloader. in process of trying to unlock again
Sent from my VM670 using XDA
Click to expand...
Click to collapse
*Steps into the fray*
You said in the op that you tried flashing an ruu based on your radio; the RUU you need to flash needs to correspond to you hboot version. I think you should re-examine that step and make sure you flashed the correct ruu to begin with.
Crossrocker said:
So your phone is s-on, but it wont boot up?
Take it to sprint and act dum dum
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Click to expand...
Click to collapse
no it was weird ruu locked (pink locked oow top of hboot screen ) bootloader but i was still s-off.
i tried unlock process again which appeared to not take but when i went to hboot pink locked oow bar is gone so will retry pushing recovery thru bootloader. im currently on hboot 2.10 and looking for 2.18 upgrade. sigh if this dont work i give up. for a lil while at least.
Sent from my VM670 using XDA
dtowngs4g said:
no it was weird ruu locked (pink locked oow top of hboot screen ) bootloader but i was still s-off.
i tried unlock process again which appeared to not take but when i went to hboot pink locked oow bar is gone so will retry pushing recovery thru bootloader. im currently on hboot 2.10 and looking for 2.18 upgrade. sigh if this dont work i give up. for a lil while at least.
Sent from my VM670 using XDA
Click to expand...
Click to collapse
I would strongly recommend you NOT update to the 2.18 bootloader...re-rooting after that is a pain, and not worth the headache. 2.10 is nice and simple.
ok but i did upgrade to 2.18 months ago after rooting and getting s-off. unfortunately my sd card got wiped so im having worst time finding 2.18 thru my searching. will redo recovery cuz pushing or trying to push thru adb didn't work last night.
Sent from my VM670 using XDA
Your gonna have to go thru a LOT of trial and error now. don't give up.
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
I ran a zip file that was supposed to set super user, and now I am stuck at the main screen. I am using revolutionmod and it won't get past this screen. Any and all help is appreciated. Thanks.
Need some info. Are you s-off or htcdev unlock or just stock? What did you flash it in? Adb or recovery?
Sent from my Paranoid Android via XDA
antoniodz95 said:
I ran a zip file that was supposed to set super user, and now I am stuck at the main screen. I am using revolutionmod and it won't get past this screen. Any and all help is appreciated. Thanks.
Click to expand...
Click to collapse
If you are using revolutionary to root it does everything for you so there would be no need to run an extra su zip. From what you are saying it sounds like you are trying to root.
What is your hboot and what Rom are you running? If you are on stock android unrooted 2.3.4 then you will need to downgrade so you will be able to use revolutionary correctly.
Also do NOT use the HTC unlock for the bootloader. You will not be s-off and will regret it.
Sent from my HTC Incredible 2 using xda premium
Thanks for the replies guys. I was gone all day yesterday and figured what the issue was. I forgot to put the updated radio on my SD and then update it. It fixed it and now I'm running Liquid Gingerbread 3.2
Thanks again for the help guys!
Antonio
Stuck on HTC screen
First I would like to apologize if this is the wrong way to do this as this is my first post as a new member. Please let me know the correct protocal if this is wrong.
I unlocked using HTC bootloader unlock
I rooted Android 2.3.4 using Superoneclick
Deleted Verizon bloatware
I have/had CWM v5.0.2.0-vivow and ROM Manager
Tried to flash custom ROM directly from Rom Manager
Everything seemed like it went well but froze on white HTC screen in reboot
Tried to flash MIUI with CWM and it successfully flashed but stuck on same HTC screen
Tried to restore
Tried to do Factory Data Reset (wiped everything)
Tried the IMG.zip trick and bootloader doesn't read it. (not sure if I have the right ones I need for 2.3.4)
Boots into bootloader and CWM fine but can't get past the HTC screen
Please help or direct me to someone that can so I can SIM unlock for my GF. She has to use a crap phone right now.
I appreciate your time and any effort
1. Htcdev unlock isn't full s off so flashing stuff is more complicated.
2. Name it to PG32IMG.zip
3. You'll get faster replies of you make your own question thread
sent from my paranoid android
JehC said:
Need some info. Are you s-off or htcdev unlock or just stock? What did you flash it in? Adb or recovery?
Sent from my Paranoid Android via XDA
Click to expand...
Click to collapse
Q
Thvjye y
Sent from my ADR6350 using xda premium
skunkle88 said:
Q
Thvjye y
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
It's htcdev unlocked
I used ROM manager to download and flash
Then when it froze I tried using CWM to flash MIUI
It said it was successful but still stuck on HTC screen
Try downloading a stock RUU and name it to PG32IMG.zip and put it in the root of your SD card and boot into hboot. Then I would personally suggest going for full s off because flashing ROMs is 10 times easier. But if not, after reverting to stock re flash any ROM you want through whatever process you have to for htcdev unlock
sent from my paranoid android