Related
www.androidpolice.com/2011/06/25/ex...gingerbread-update-for-htc-incredible-2-leak/
Surprised I haven't seen anything about this on here already.
Sent from my ADR6400L using XDA App
Hopefully this what will be the rumored OTA update.
Right now, you have to be one of the lucky few to be set S-OFF and rooted by AlphaRevX and running ClockworkMod recovery in order to flash the pre-rooted ROM. For those who are not that lucky (yet), enjoy the pictures and videos while we all wait for AlphaRevX to release the full unlock for the Incredible 2. Note: Please note that we recommend against flashing the full signed RUU (i.e. the original un-rooted leak), as it will prevent the root and unlock method by AlphaRevX.
***someone was going to ask so I figured I'd just post it n save everyone the dumb questions***
Side note... "Enjoy the video n pictures and keep drooling cause we still havent rolled out our new beta"
.... Jerks...
I decided against posting it at XDA for the time being, as I don't want to support the thread.
While on topic. How are these upgrades usually done, do they work fine being upgraded with all your stuff alongside. Is there benefit in doing a factory reset of your phone and doing a clean install, sort of like regular computers benefit from.
Or are android os updates usually good enough to simply upgrade without doing anything else?
PharmCAT said:
While on topic. How are these upgrades usually done, do they work fine being upgraded with all your stuff alongside. Is there benefit in doing a factory reset of your phone and doing a clean install, sort of like regular computers benefit from.
Or are android os updates usually good enough to simply upgrade without doing anything else?
Click to expand...
Click to collapse
If its an ota upgrade, you simply install it. If you are changing roms (after a root) or upgrading a non stock rom it is usually recommended that you wipe and clear your cache for optimal results.
Hmm... Have a 2nd Inc 2 that has to go back to assurion for speaker issues, thinking of loading the ruu on phone just to have a peek.. wonder if they'd notice?
Sent from my ADR6350 using XDA App
marcg611 said:
Hmm... Have a 2nd Inc 2 that has to go back to assurion for speaker issues, thinking of loading the ruu on phone just to have a peek.. wonder if they'd notice?
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
They will certainly notice, will they do something about it? Maybe, probably.
marcg611 said:
Hmm... Have a 2nd Inc 2 that has to go back to assurion for speaker issues, thinking of loading the ruu on phone just to have a peek.. wonder if they'd notice?
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
why send a phone to assurion. if you have insurance Verizon does it free. doesn't assurion cost you money
drewcam888 said:
why send a phone to assurion. if you have insurance Verizon does it free. doesn't assurion cost you money
Click to expand...
Click to collapse
Because if he got it replaced by them he has to go to them for warranty replacement now too
Sent from my ADR6350 using XDA App
has anybody installed the original untouched file?
this file the original leak one can install in a unrooted phone right?
I hope we get to uninstall the bloat too with this update. That would be great!
...or we will get more haha
Sent from my ADR6350 using XDA App
Just about a week or two ago, I installed the new gingerbread update that Android pushed out, but I didn't know I wasn't suppose to if I wanted to root, is there anyway to get back to Froyo, I haven't did any rooting or flashing, or anything to the phone.
You can not as of now. Not to sound like a douche, but there is no less than 2 or 3 threads on this exact question. 95% of your questions have probably been answered somewhere on this forum, if you use the search button.
I too have a un-rooted Dinc2 that has GB on it and am patiently waiting for someone WAY smarter than me to find a way to root it. I can't stand the bloat
You could just be impatient and get a payg xtc clip. They're like 30 bucks.
Sent from my ADR6350 using XDA App
times_infinity said:
You could just be impatient and get a payg xtc clip. They're like 30 bucks.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
That's what I did. But more like $50 with shipping and exchange rate. I don't know how much another credit costs though
Sent from my stock, bloated ADR6350 using XDA Premium App
x Jumpman23 x said:
Just about a week or two ago, I installed the new gingerbread update that Android pushed out, but I didn't know I wasn't suppose to if I wanted to root, is there anyway to get back to Froyo, I haven't did any rooting or flashing, or anything to the phone.
Click to expand...
Click to collapse
Why don't you just factory reset... And it'll bring you back to Froyo-than you can S-Off and root your phone, and if you want GB just download the rooted, debloated deodexed OTA? :/
I'm not too sure about the Dinc2, seeing as how I came from Fascinate but with the GB-Froyo officially-a factory reset always reset it to the stock rom it shipped with.. which it SHOULD be the same to all android devices regardless of make. YMMV
Just a suggestion.
Sent from my ADR6350 using XDA App
Slic|< said:
Why don't you just factory reset... And it'll bring you back to Froyo-than you can S-Off and root your phone, and if you want GB just download the rooted, debloated deodexed OTA? :/
I'm not too sure about the Dinc2, seeing as how I came from Fascinate but with the GB-Froyo officially-a factory reset always reset it to the stock rom it shipped with.. which it SHOULD be the same to all android devices regardless of make. YMMV
Just a suggestion.
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Sorry but that is incorrect advice on the HTC Android platform. Once you upgrade to a new ROM, that is the ROM that is restored when you do a factory reset. There is no permanent storage of the 'factory shipped' ROM.
tpbklake said:
Sorry but that is incorrect advice on the HTC Android platform. Once you upgrade to a new ROM, that is the ROM that is restored when you do a factory reset. There is no permanent storage of the 'factory shipped' ROM.
Click to expand...
Click to collapse
Oh **** :X... Didn't know man. Sorry was just tryna help out. Guess HTC is less forgiving than Sammy.. :/
With the fascinate that usually did the trick to rollback, at least it did for me.. :/. Like I said new to HTC.
Sent from my ADR6350 using XDA App
There is a rumoured new update coming out. Of you are rooted or want root please hold off as you might lose your root ability. Just a warning of friendly advice.
Sent from my Incredible 2 using xda premium
Edit: Dang its late. Sorry I can't spell. Glad that's not what the army paid me for. Lol
Yeah. I just got the phone today for my wife and it updated while it was charging before I could root it...which sucks since rooting it played a HUGE role in the decision to get this phone.
I'm guessing I could really break something if I just tried the unrevoked/alpharev/revolutionary approach regardless of the fact that I now have hboot 0.98 huh?
chrisanthropic said:
Yeah. I just got the phone today for my wife and it updated while it was charging before I could root it...which sucks since rooting it played a HUGE role in the decision to get this phone.
I'm guessing I could really break something if I just tried the unrevoked/alpharev/revolutionary approach regardless of the fact that I now have hboot 0.98 huh?
Click to expand...
Click to collapse
I don't recommend it lol. Esp if its a different hboot
Sent from my Incredible 2 using xda premium
Can you fix the "knew" in the title to "new." It really hurts my brain.
knipp21 said:
I don't recommend it lol. Esp if its a different hboot
Click to expand...
Click to collapse
****, I was afraid of that. Now I wonder if I should try to return it and try again...damnit.
Is the update going to try and force itself or will it does it have to be a manual update?
Also, if you are running a custom rom will this still effect people, or just people running stock root?
Unless things are different from my Original Droid then custom roms don't need to worry about it since most of them have OTA updates turned off.
trystan.snyder said:
Can you fix the "knew" in the title to "new." It really hurts my brain.
Click to expand...
Click to collapse
Sorry..was doing it by phone so it took a while. Thank you for your thoughtful post though.
kubes069 said:
Is the update going to try and force itself or will it does it have to be a manual update?
Also, if you are running a custom rom will this still effect people, or just people running stock root?
Click to expand...
Click to collapse
If it is a stock based Rom without OTA removed...then yes it prob will...and you will lose root...you can remove the update service yourself with a root explorer app
Sent from my Incredible 2 using xda premium
You will want to switch to a custom for sure. Was about to go to sleep for the night. I am still running my own stock debloat. I caught the ota pop up with the countdown clock. Luckily I was able to pull battery and flash bliss real fast.
Sent from my ADR6350 using xda premium
zax10 said:
You will want to switch to a custom for sure. Was about to go to sleep for the night. I am still running my own stock debloat. I caught the ota pop up with the countdown clock. Luckily I was able to pull battery and flash bliss real fast.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Yep that's what I thought lol luckily I'm running miui. I hope I got this out on time to save some ppl...what happened to Verizon asking if you wanted to update first...
Sent from my Incredible 2 using xda premium
I'm new to the Inc2, can I turn S-off somehow and then downgrade to the original hboot? Is that possible? Or is the Revolutionary method the only way to turn S-off?
chrisanthropic said:
I'm new to the Inc2, can I turn S-off somehow and then downgrade to the original hboot? Is that possible? Or is the Revolutionary method the only way to turn S-off?
Click to expand...
Click to collapse
Unless you have an overpriced xtc clip..you're screwed for now.
Sent from my Incredible 2 using xda premium
trystan.snyder said:
Can you fix the "knew" in the title to "new." It really hurts my brain.
Click to expand...
Click to collapse
Glad two of your 7 posts have been to correct me btw. Way to add to the community
Sent from my Incredible 2 using xda premium
If you take the ota to 2.3.4 kiss rooting goodbye.
Sent from my ADR6350 using Tapatalk
For some reason the curious side of me wants to down load. Can't be that big oh a change. Right???
How long for the exploit on 2.3.4 since we already have 2.3.2 done.
Sent from my ADR6350 using xda premium
My crystal ball says it will take 3 months and 9 days to find the next exploit, and 4 months 15 days for the next patch that kills it.
It seems that one of the biggest benefits of custom roms are freedom of forced updates. I guess this is the answer to all the people concerned about getting s-on for the event of a return.
Sent from my Incredible 2 using Tapatalk
Wow, this thing pushes through without user consent? Holy crap am I glad I'm running CM7.
Just a thought - would users who have received the update against their will have the option of flashing the previously released gingerbread RUU? I'm guessing that even if they could, they'd still be stuck with the updated hboot and therefore unable to get s-off. I'm not really sure how all that works though. Anybody smarter than me have any thoughts?
Sent from my Incredible 2 using XDA App
The new OTA is pushed to your phone but it offers the option to accept, postpone or reject.
I am rooted (stock rom) and made the error of accepting. After the update my phone would not boot completely (erred with white triangle, yellow exclamation point, blue android). You can follow Conduitz's fix found in this thread: http://forum.xda-developers.com/showthread.php?t=1233267
NOOB Question
If I want the update and could wait for Root (have root now), how does one go about getting S-ON again? I used the alpharev method.
thanks in advance.
Since I have my E4GT rooted, is it safe to push the OVA update for signal Los that Spring just pushed out? It's just that I keep getting the notification that I have the update ready to download and it is becoming extremely annoying.
Same here
Sent from my SPH-D710 using xda premium
Rule #1 of rooting, never take an OTA. If you want to take it. You must first completely unroot, then accept the OTA. Otherwise wait for a dev to release a rooted version.
Sent from my SPH-D710 using Tapatalk
Khilbron said:
Rule #1 of rooting, never take an OTA. If you want to take it. You must first completely unroot, then accept the OTA. Otherwise wait for a dev to release a rooted version.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I wouldn't really say that's rule #1, probably more like rule #23 or #24... the first like 20 rules mainly include Modding, getting sh*t for free, and banging b*itchs
Sent from my SPH-D710 using xda premium
Thanks for the advice guys I truly appreciate it....will probably just wait like you said and until then just keep clearing the notification.
hijewpositive said:
I wouldn't really say that's rule #1, probably more like rule #23 or #24... the first like 20 rules mainly include Modding, getting sh*t for free, and banging b*itchs
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Like!
- Sent from my GSII using Fat Fingers to type.
ReubenRene said:
Since I have my E4GT rooted, is it safe to push the OVA update for signal Los that Spring just pushed out? It's just that I keep getting the notification that I have the update ready to download and it is becoming extremely annoying.
Click to expand...
Click to collapse
If you're rooted or running any other system modification, the OTA won't apply to your phone. Even if you try, it will fail and you'll just reboot back to your normal phone. Your best bet is to actually install an EK02-based ROM. If you want to stick to stock with just the new modem and kernel, and keep root, I recommend the UnNamed ROM that was recently posted. It's basically a rooted, debloated stock with CIQ removed.
Basically exactly what I was looking for.
It also includes the latest CWM, making future flashes nice and easy.
ReubenRene said:
Thanks for the advice guys I truly appreciate it....will probably just wait like you said and until then just keep clearing the notification.
Click to expand...
Click to collapse
There was a trick to keeping it cleared until you reboot when i had my nexus s, but i can't remember what it was. Try searching the the nexus s forums for it. It'll keep you from going insane from clearing it 20times a day.
Sent from my SPH-D710 using xda premium
no OTA for me...
i have stock non-rooted phone. mine is running 2.3.4
i try and go into settings to update my system and it says i have the most current version. any reason it's not pushing to my phone yet?
any idea what the sprint update included? would it be worth reverting to a stock rom to get it?
jsny said:
i have stock non-rooted phone. mine is running 2.3.4
i try and go into settings to update my system and it says i have the most current version. any reason it's not pushing to my phone yet?
Click to expand...
Click to collapse
no, not really. sprint said they'd be updating customers randomly from the 7th to like the 15th or so. maybe your number just hasnt been called yet.
---------- Post added at 12:20 AM ---------- Previous post was at 12:17 AM ----------
tensux said:
any idea what the sprint update included? would it be worth reverting to a stock rom to get it?
Click to expand...
Click to collapse
Sprint said that its a minor update thats primary fixes are for:
- 4G Sprint Hotspot disconnects when in a phone call
- Radio loses signal and may require power cycle
Couldn't hurt i guess. But there are a bunch of roms already out there that are using the ek02 update. Just use one of those so you dont have to do double the work.
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4
Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium
player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.
Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.
smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.
I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app
Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app
player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app
Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app
Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium
Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.
You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app