Nothing to major but kinda cool we are still getting some love.
http://www.androidpolice.com/2012/0...ncredible-has-a-small-ota-update-coming-soon/
bobAbooE said:
Nothing to major but kinda cool we are still getting some love.
http://www.androidpolice.com/2012/0...ncredible-has-a-small-ota-update-coming-soon/
Click to expand...
Click to collapse
heh. kinda sucks I don't use any of these
Cool i guess. Not really worth it to update. That being said im one of those type of people who has to have the latest version number displayed in info, so im sure i will update my current setup and my rom Touch of Blue. Cant wait to get ahold of it.
Nice. I like to have the latest too .
Sent from my Droid Incredible using XDA
I'd strongly recommend avoiding this update. It should get pulled. It's causing a boot loop that starts at 2am and happens for about 2 hours. No word on a fix yet.
Just out of curiosity, would this screw up root if the phone has s-on still? I halfway rooted my friend's dinc not too long ago but didn't feel like going through the process of getting s-off since he won't be getting too crazy with it anyway (just wanted to get rid of bloatware and the like)
Sent from my ADR6300 using XDA
Not sure about root with the new update, but my wife's phone isn't the only one doing the 2am 2hrs of boot loop.
https://community.verizonwireless.com/thread/775872
I'm hoping that someone smarter than me can find a fix for this. I just need it to last a couple more weeks until we can get our S3's.
Ironically, the same day, my Dinc's wifi gave up the ghost. It wasn't a good day for HTC in my house.
lackskill said:
Not sure about root with the new update, but my wife's phone isn't the only one doing the 2am 2hrs of boot loop.
https://community.verizonwireless.com/thread/775872
I'm hoping that someone smarter than me can find a fix for this. I just need it to last a couple more weeks until we can get our S3's.
Ironically, the same day, my Dinc's wifi gave up the ghost. It wasn't a good day for HTC in my house.
Click to expand...
Click to collapse
Where did you get the update from? Was it ota or did you download it from somewhere?
cmlusco said:
Where did you get the update from? Was it ota or did you download it from somewhere?
Click to expand...
Click to collapse
It was an OTA push.
New Update
The new push from verizon locks the bootloader, and prevents every root method I know of from working. I have s-off, and have for quite some time, but had to do a complete restore last night. The update pushed automatically, and now at the top of my bootloader screen it says ---LOCKED---
Looking for a way to root, or go back to the previous radio, etc and re-root now
ggoodman1022 said:
The new push from verizon locks the bootloader, and prevents every root method I know of from working. I have s-off, and have for quite some time, but had to do a complete restore last night. The update pushed automatically, and now at the top of my bootloader screen it says ---LOCKED---
Looking for a way to root, or go back to the previous radio, etc and re-root now
Click to expand...
Click to collapse
If your s-off it dosent matter if its locked, just flash cwm recovery through hboot and then flash superuser thru recovery. If your s-on, go to the htcdev site and unlock the bootloader and then fastboot flash cwm recovery and then flash su thru recovery. Bam your rooted.
Thanks
cmlusco said:
If your s-off it dosent matter if its locked, just flash cwm recovery through hboot and then flash superuser thru recovery. If your s-on, go to the htcdev site and unlock the bootloader and then fastboot flash cwm recovery and then flash su thru recovery. Bam your rooted.
Click to expand...
Click to collapse
I'll try it again, but when I tried doing this earlier, it didn't work
ggoodman1022 said:
I'll try it again, but when I tried doing this earlier, it didn't work
Click to expand...
Click to collapse
I am s-off and locked right now, and i can flash what ever i want. Try redownloading cwm hboot flashable http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
What didnt work about it last time, the file wouldnt flash or it flashed but didnt fix the problem?
hboot
cmlusco said:
If your s-off it dosent matter if its locked, just flash cwm recovery through hboot and then flash superuser thru recovery. If your s-on, go to the htcdev site and unlock the bootloader and then fastboot flash cwm recovery and then flash su thru recovery. Bam your rooted.
Click to expand...
Click to collapse
And now it won't even attempt to flash through hboot... I followed instructions precisely :crying:
ggoodman1022 said:
And now it won't even attempt to flash through hboot... I followed instructions precisely :crying:
Click to expand...
Click to collapse
Is it on the root of your sdcard (in no folders) and named PB31IMG.zip? If it is i would use a pc to backup up your sdcard, format it fat32, put the files back, and then try again.
cmlusco said:
I am s-off and locked right now, and i can flash what ever i want. Try redownloading cwm hboot flashable http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
What didnt work about it last time, the file wouldnt flash or it flashed but didnt fix the problem?
Click to expand...
Click to collapse
so, I went into hboot, and it asks about installing the update. I choose yes, and it reboots, but no CWM. But it appears to be working now
---------- Post added at 10:45 PM ---------- Previous post was at 10:37 PM ----------
ggoodman1022 said:
so, I went into hboot, and it asks about installing the update. I choose yes, and it reboots, but no CWM. But it appears to be working now
Click to expand...
Click to collapse
nevermind... still not working. After recovery says files are installed, it hangs up while trying to reboot, or power down. And if I pull the battery and reboot, it's just the same as it was before.
I'll try backing up & formatting the card now, instead
---------- Post added at 10:58 PM ---------- Previous post was at 10:45 PM ----------
ggoodman1022 said:
so, I went into hboot, and it asks about installing the update. I choose yes, and it reboots, but no CWM. But it appears to be working now
---------- Post added at 10:45 PM ---------- Previous post was at 10:37 PM ----------
nevermind... still not working. After recovery says files are installed, it hangs up while trying to reboot, or power down. And if I pull the battery and reboot, it's just the same as it was before.
I'll try backing up & formatting the card now, instead
Click to expand...
Click to collapse
AAAANND, we're back in business now! Don't know why it wasn't working before... But the good news is that it is now
Related
Ok, I have been thrown for a loop and need some help....
I had a Sprint Hero Rooted on 2.1 the .5 sprint update
Tried to run the new update but it kept getting corrupt.
Did a Nandroid backup
So I reverted back to the .5 RUU
Then it wanted me to update to the old .6 update, so I did
Hoping then I would upgrade to the new .6 but it was not able to find a new update?
Wanted to restore my nandroid update.
When I try to boot into the recovery mode I get a picture of a phone with a red Explanation mark in a triangle.
There is a bunch of people on the net that say they have seen or gotten it, but no one says how to get rid of it? So I can not get in to recovery mode at all.
Tried the home+power boot
Tried the volume down + power then home
always ends in the same screen with no recovery.
Tried multiple times to install the .5 RUU
Reset phone
never can get back there to the recovery?
Phone will boot fine into 2.1 and run fine..
Anyone have any ideas, I have tried everything I can think of.
Thanks
Did u try placing the recovery on ur SD card and flashing it threw terminal on ur phone
Root-Hack-Mod-Always™
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
ASimmons said:
You lost root, as far as I remember the .6 update was to block the corrent rooting efforts that you see around here, thats why the rooting instruction say to go back to the .5 ruu.
The corrupted update your getting is just sprints server being bogged down.
What you need todo is go back and re-root your phone. Dont worry about the update untill it gets released into one of the current roms or until you here that its safe todo without losing root.
Click to expand...
Click to collapse
Thanks, I can't believe I missed that! I had never tried a backup before root, so I did not think about that. Now I know and hopefully this will help someone that googles this issue, as there is never a clear answer until yours.
Thanks again...
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Also If you ever run an ruu on your phone you can kiss your root good bye no matter what version you do. but if you have nand backups you can reroot your phone and then restore one of your backups since there stored on your sdcard.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
Correction: If you see this symbol, it means you don't have a custom recovery image in the phone. You can actually be rooted and still get that symbol if you haven't yet flashed a custom recovery after you rooted. You need to have a custom recovery (that requires root) to avoid getting that symbol when you try to boot into recovery.
Most rooting methods on here automatically include flashing a custom recovery as one of the steps, so this isn't really a big issue....but I just wanted to clarify the specifics of this for anyone else who reads.
copc said:
So in closing of this thread:
if you are trying to get into recovery and see "Phone with Explanation mark" image.
it's because your phone is not rooted
So root your phone and it's all good
Click to expand...
Click to collapse
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
brisuth said:
I am running a rooted 2.1 and get this symbol , i installed rom manager and it asked me to install flash clockworkmod recovery and it booted into recovery straight away allowing me to partition my sd card, but if i want to access this mode i have to run flash clockworkmod recovery everytime or it will not work
Any idea why that is anyone?
Click to expand...
Click to collapse
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
ASimmons said:
Nope once its on there you should be able to hold the home key while rebooting to get into recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
brisuth said:
only way can get there is through flash clockworkmod recovery then select either reboot in recovery mode or turn of handset and restart with home and power button, what ever flash clockworkmod recovery does to make it work as soon as it has been used i am guessing it is deleted or modified,
i have tried running it then checking files on sd card but cant see anything different
Click to expand...
Click to collapse
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
chromiumleaf said:
The recovery console isn't on your SD card, it's flashed to a partition inside your phone's memory. So you won't see anything different on your card.
And if you can boot into recovery by "restart with home and power button" like you say, then it's working as it should -- that's how you get into recovery.
Click to expand...
Click to collapse
just had a friendly member point out what i was starting to suspect the problem lies with the custom recovery being flashed back to stock on every restart, the shell command here
/system/etc/install-recovery.sh this stops any custom recovery on reboot. any advice on what tools to edit or remove
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
I always had root that was where the confusion was, what i did not know was the script was running with every boot of the handset and removing the recovery that was there as it was identified as unofficial and exclamation mark could be down to me using many methods to flash i may have renamed original recovery so when it goes to exclamation it is because cant find original recovery whether handset is rooted or not.
danaff37 said:
Delete that file when you get root I guess. Our as soon as you reboot into clockwork recovery, flash a rom. Use nfinitefx if you want a stock one
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
would that have worked? i thought about it many many times but as i had never flashed before was unsure how many times phone would reset and if it did before it was installed could i lose my recovery.
on the plus side the 2 months i have spent trying to solve this i have a much broader view of the workings of my handset and without the many members like yourself who take the time to reply and try to help others i would have given up a long time ago.
Brian
I'm sure if you deleted that script a custom recovery would have stuck
Sent from my HERO200 using XDA App
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. The answer...yes.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want to use or have access to ADB.
In that case you would:
remove your sdcard from your phone
place the zip on the root of the sdcard (using an adapter or another phone) and make sure it is named the appropriate "PG05IMG.zip"
place the sdcard back in your phone
boot to bootloader as if you're installing a radio (power+VolDown from powerOff). It will then find the zip, recognize it as recovery and ask if you want to install (if it does not prompt then select "Bootloader" from hboot).
Follow the instructions and after it finishes flashing pull your battery to power off (since the ROM will be bootlooping and hboot will constantly find the zip)
Now remove the sdcard and delete the zip (via adapter or other phone) like you did to put it on the sdcard, then place the card back in the phone.
Boot back to bootloader (Pwr+VolDwn)
Select "Recovery" and use CWR to wipe data/cache, flash a new rom, restore, or whatever you wish.
Obviously not the only reason since some people prefer this method over RM but clearly in that case the whole sdcard switching mess is unnecessary. Just do steps 2 and 4 and reboot when prompted like you do with radios.
Remember to remove any PGO5IMG.zip from your sdcard when done.
If this isn't useful to you, so be it. I just figured I'd throw this out there. Maybe it will help someone.
I will keep this updated as new versions come out for those few that find it useful.
**Credit to Koush and jcase**
All I did was decide to throw them in a zip that was useful in some situations for panicking users.
Updates
8/9/2011: Added latest official stable for mecha (4.0.1.5) released 8/8/2011.
8/30/2011: Added latest official stable for mecha (5.0.0.1) released less than an hour ago. Added mirror.
8/31/2011: Added latest official stable for mecha (5.0.0.8)
9/1/2011: Added latest official stable for mecha (5.0.1.0)
9/5/2011: Added latest official stable for mecha (5.0.2.1)
2/1/2012: Added touch based CWR released this morning (5.8.0.2) *NOTE: Have not personally tested.
If any of these cause problems please let me know immediately.
Latest Official=5.0.2.1
jcase modded=4.0.0.5
Mirror: http://www.mediafire.com/?9zt68cegl6qa3
MD5:
66750618ecfba292c0b0e42c50c2c3ee - (CWR3.1.0.2)PG05IMG.zip
1f390edad7e87310fe80b3264a57b14b - (CWR4.0.0.5)PG05IMG.zip
6aac529cedcd2b22afac7391a4cb7efb - (CWR4.0.1.5)PG05IMG.zip
bf25b2601441b9fffb7d68954c4ff3b5 - (CWR5.0.0.1)PG05IMG.zip
dfe1ddf0c574977ee2c1828735ef2dc0 - (CWR5.0.0.8)PG05IMG.zip
8474c8d607177b0144eec624dea687b7 - (CWR5.0.1.0)PG05IMG.zip
c4c1d9c5e553fd7b151352551b931369 - (CWR5.0.2.1)PG05IMG.zip
58557e1e355c795d748c2e6c66251f0a - (CWR5.8.0.2)PG05IMG.zip
Absolute_Zero said:
Someone asked if it was possible to flash ClockworkMod Recovery through hboot instead of using RomManager. I didn't see the need at the time but I took a few minutes to throw together a test. Let me know if it works for you or not.
I tested flashing the stock recovery from the custom firmware, confirmed it had replaced CWR, then used this to install CWR back.
Primary reason something of this nature may be useful, as I see it, is if your recovery is damaged, your ROM is bootlooping, and you don't want or have access to ADB. In that case you would just pull your sdcard, place this on the root (via adapter or someone else's phone) named the appropriate "PG05IMG.zip", place back in your phone, and boot to bootloader as if you're installing a radio. It should then find it, recognize it as recovery and ask if you want to install.
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
If this doesn't work and doesn't have any use for anyone, so be it. I just figured I'd throw this out there.
BTW, this is ClockworkMod Recovery 3.1.0.2 (latest for mecha at time of posting).
Note1: Only tested on Engr hboot with S-off obviously
Note2: I don't have access to an MD5 generator where I am so people that test this should have a booting ROM with RomManager or at least know how to manually reflash ClockworkMod Recovery if it doesn't work.
Click to expand...
Click to collapse
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
good post will definitely come in hand props
DroidTh3ory said:
Good work.on this... A LOT of people are going enjoy it!! It is also a great way to install the modded 4.0.0.5 Clockwork with the boot to bootloader option.
I always had to "flash recovery" in adb.
Props!!
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Sword.Zero said:
There's a modded 4.0.0.5 CWM Recovery out there?? Where can I find the post for this ?
Click to expand...
Click to collapse
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Absolute_Zero said:
Post a link to it and I'll make one when I get home. That way I can test again. Hopefully the modded one you speak of is fully stable and functional.
Click to expand...
Click to collapse
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment (CWR4.0.0.5)PG05IMG.zip
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
In your case it would probably be easier to just use flash_image from terminal on the phone (i.e. flash_image recovery /sdcard/recovery.img) assuming your current rom has it (if not just search and download it) or you have RM installed. The main case I saw this being useful was if you didn't have or want to use ADB and your ROM was unusable (e.g. bootlooping). I may add Jcase's modded recovery to the OP as well since it seems useful/wanted by some.
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Mustang302LX said:
I thought the one JCase made had issues with nandroid backups installing? I could be wrong but for some reason I remember that issue for several people.
Click to expand...
Click to collapse
I have been using for a good month now on 3 different bolts... Never had a issue??
Absolute_Zero said:
Additionally, seems if it is as easy as swapping the .img out which is all I did, then the original custom upgrade firmware flashed in the last step of the root guide could include this. Then you'd have CWR immediately after finishing the permaroot guide.
Click to expand...
Click to collapse
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
it is that easy,i have done this,and i have also removed the hboot and stock recovery from PG05IMG RUUs so that i could flash without destroying recovery and my eng bootloader.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
did you make up your own android info file? or what did you take it from?
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
DroidTh3ory said:
Here is your package with the 4.0.0.5 Modded Recovery ready to flash in HBOOT.
JCASE created the Recovery, so him the love for it. I all I have done is use it. LOL It gives you the option under "advanced" to "reboot bootloader". So you can install the ROM, then simply boot into boot loader to flash the radio.
View attachment 661641
Click to expand...
Click to collapse
thanks for the download. has he put up any posts on it? or is it still being developed?
scotty1223 said:
thanks for the download. has he put up any posts on it? or is it still being developed?
Click to expand...
Click to collapse
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
cool,thanx... ill go over there and look for it.
edot:
here if anyone else wants it
Thanks for this. Just flashed 4.0.0.5 after being afraid/too lazy to do it through ADB (which is also a pain because I have it on my Windows partition whereas I regularly use Mac).
scotty1223 said:
actually,thats allready how it is ive rooted mr2 twice and the mr1 upgrade allready has clockwork installed.
Click to expand...
Click to collapse
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
thanks for putting it together and offering the download, it has many uses, as people will see. the biggest one allready having been mentioned,if something screws up your OS and recovery,its easy to get it back.
Click to expand...
Click to collapse
Exactly my reasoning. I've seen to many people unaware of what to do in that situation
did you make up your own android info file? or what did you take it from?
Click to expand...
Click to collapse
I checked a few from the firmware and radios and they all looked the same so I just pulled one of those.
again thanks for posting this,it was commonplace to install inc recoverys in hboot,and ive done it on the eris as well
Click to expand...
Click to collapse
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
DroidTh3ory said:
I believe he has it posted on rootzwiki
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Hey get out of here, you've got candy to make! I keeeed I keeeed! Great work on the recovery guys, VERY useful!
Sent from my ADR6400L using XDA Premium App
DroidTh3ory said:
I have been using for a good month now on 3 different bolts... Never had a issue??
Click to expand...
Click to collapse
Yup. Been using it since it's release. Restored many backups with absolutely no issues.
Absolute_Zero said:
Figures. It was too simple of a concept not to have been done but I didn't see anyone that had done it in Tbolt. I also hadn't seen anyone mention it was in the custom firmware either and I didn't have time to check this morning before I left for work. I guess I can pull that part out of the OP since you say it's already in there.
Click to expand...
Click to collapse
id be willing to bet most people dont know,lol.they prolly just blindly downloAd rom manager and flash it. i checked to see if it was there,after seeing this as one of the last statements in the root post: Reboot your phone. You should now have full root permissions, an engineering kernel and recovery.
Absolute_Zero said:
First HTC android phone I've owned but as I said, makes sense it would have been done a long time ago for other HTC phones.
Click to expand...
Click to collapse
its one of the things i really love about htc. i got used to installing recoverys,splash screens,etc. on my incredible,then started experimenting with img files on my eris,and discovered it was quite possible to simply move the images around kinda neat if you want to try a leaked ruu but dont want to wait for someone to post a CWM flashable roms. just pull out the hboot and stock recovery and flash away
it was quite common to manipulate things in hboot on the inc,but never mentioned in the eris forum,where most of the gurus frowned upon the s-off bootloader.kind of a shame... more bricked eris's prolly could have been revived after the clockwork fiasco if s-off was part of the common root process.
thanx for the android info info. when i make them up,it doesnt seem to matter which one i use. i dont think it even checks the text inside,i think you just need a text document titled "android info" lol
Thank you for the updated 5.0.0.1 cement recovery.
cam30era said:
Thank you for the updated 5.0.0.1 cement recovery.
Click to expand...
Click to collapse
Autocorrect fail? or did you have a problem with 5.0.0.1?
I was trying to install a new kernel so I could overclock, and I could not get it into recovery mode. I tried the normal, turn off+hold volume down key+turn on, method. I also used the boot into recovery mode option from CWM (Acer Recovery)
I thought it may have something to do with my other software issues causing issue, so I did a master reset. It got everything back to normal, reloaded my info and backed up info, and installed rootcheck (which confirmed root and busybox) and superuser, and CWM, and have the kernel on my sd card. I tried booting into recovery mode again and it wont work
The error I get is the little tranlucent android dude with the gears rolling and then suddenly the gears stop and I get the warning sign, yellow triangle with exclamation mark.
Anyone know why this may be?
phoenixbennu said:
I was trying to install a new kernel so I could overclock, and I could not get it into recovery mode. I tried the normal, turn off+hold volume down key+turn on, method. I also used the boot into recovery mode option from CWM (Acer Recovery)
I thought it may have something to do with my other software issues causing issue, so I did a master reset. It got everything back to normal, reloaded my info and backed up info, and installed rootcheck (which confirmed root and busybox) and superuser, and CWM, and have the kernel on my sd card. I tried booting into recovery mode again and it wont work
The error I get is the little tranlucent android dude with the gears rolling and then suddenly the gears stop and I get the warning sign, yellow triangle with exclamation mark.
Anyone know why this may be?
Click to expand...
Click to collapse
Which kernal are you trying to install? Are you installing via cwm? What version are you running? Are you holding vol-key until after the Acer logo shows up and then keeping the vol rocker held until you see "booting recovery..."?
Have you successfully booted into recovery in the past?
thanks for the response. It seems the recovery image was corrupted or unknown according to cwm. i had to install the cwm one and it works just fine.
Great
phoenixbennu said:
thanks for the response. It seems the recovery image was corrupted or unknown according to cwm. i had to install the cwm one and it works just fine.
Click to expand...
Click to collapse
Glad you got it working
Installing Acer recovery installer does not install cwm. You have to select cwm from the list and click install recovery. Sounds like you figured it out, though.
Sent from my A500 using Tapatalk
A500 not switching to recovery
I also have a new A500 which already had 3.2 stock installed and it has never allowed me to go into recovery mode. I can use iconiaroot and get to a certain point with that but to install a custom rom, I haven't been able to. I want to so any ideas? I did however get to install the Acer_A501_0.017.01_PA_ATT which is about as much progress as I have got. My thought was to downgrade first then install a custom rom like Taboonay but I can't get into recovery. Please help.
bmills74 said:
I also have a new A500 which already had 3.2 stock installed and it has never allowed me to go into recovery mode. I can use iconiaroot and get to a certain point with that but to install a custom rom, I haven't been able to. I want to so any ideas? I did however get to install the Acer_A501_0.017.01_PA_ATT which is about as much progress as I have got. My thought was to downgrade first then install a custom rom like Taboonay but I can't get into recovery. Please help.
Click to expand...
Click to collapse
Why are you trying to get into recovery? What is it you are actually trying to do? If you are stock, then getting into recovery has little value, so it would help if we know what you're actually trying to do?
TD
Why recovery
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
bmills74 said:
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
Click to expand...
Click to collapse
I now know that recovery is locked by the system and one has to change the update.zip file. Right?
bmills74 said:
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
I now know that recovery is locked by the system and one has to change the update.zip file. Right?
Click to expand...
Click to collapse
In order to flash a custom rom, you need to flash a custom recovery (in this case cwm) flashing custom roms with the stock Acer recovery isn't possible without out the update.zip being signed by acer.
Sent from my Desire HD using xda premium
bmills74 said:
I am trying to install Taboonay. The way I see it from peoples post is that with a stock 3.2 the only way to install Taboonay is to be able to go into recovery. Do you have a better solution? Or anyone? There is alot of information out there. It's hard to sort through it sometime.
---------- Post added at 05:07 PM ---------- Previous post was at 05:02 PM ----------
I now know that recovery is locked by the system and one has to change the update.zip file. Right?
Click to expand...
Click to collapse
Read through these forms and you'll get the information you need. But, before you can install a custom ROM you need to root(#) your device first. Once you get root then you have to install CWM which is a custom recovery. The Stock Recovery that comes installed will ONLY install updates signed by ACER therefore it is worthless. That's why you need something like CWM.
Hope this helps,
TD
Please do some reading mate as I can predict your future post....
You seem to have read through a bit of info skipping the main and most important parts. If you don't follow instructions TO THE LETTER your next post will be along the lines of "Help, I've bricked my A50*"....
Yes, thank you for replying, but no thanks. If your on here to help people, then help them. Learn some help desk manners.
If your on here to show your knowledge, then you have failed. The whole point of Linux is to help and contribute to a better os then what's available through retail. Careful or the point will get lost in translations.
Sent from my A500 using XDA
Hi guys!
Yesterday, i used towelroot to root my phone, and installed Safestrap with TWRP as my recovery.
I booted my phone after everything was done, and it worked fine. This is where i screw up... I installed Softkeyz (I thought it might work for the Note 3, but...)
After i installed Softkeyz, and rebooted the phone, my status bar was gone, the background was blue and my task manager didnt work. I went back into the softkeyz app and clicked the "backup" button, wich is said to revert everything back to normal. It didnt.
When i booted my phone after the backup, I still had the same problem.
I then did a Titanium Backup, and went into recovery to factory-reset. it seemed to work, but when my phone boots, I get to the languane selection screen, and then this pops up: "KeyguardTestActivity has stopped". If I click 'OK', the same message pops up and im unable to click "next" or select a language.
I went back into recovey, wiped dalvik, wiped cache, I event formated /data in case there was any virus or anything I had downloaded, did a factory reset, and it stil doesnt work....
I had a ROM on my phone, but it used AROMA so that doesnt work with Safetrap... Now my memory is clean, my phone wont boot, and I cant move any files to the SD-card through regular MTP. I guess I have to use ADB (safetrap can sideload ADB) but I have no idea how to use that, and I have no idea what ROM to use, to get my phone up and running.
I use my phone for work and for studies, and the only reason I wanted to root was for AD-blocker and better batterylife...Now I've messed up..
I've tried searching google and the forums, but cant seem to find any fix. Can anyone out there help me? Please?
EDIT: If i boot the phone WITHOUT the simcard, the error message is gone, but if the screen locks, then in wont unlock. Taskmanager still doesnt work. I managed to get to phone running though, but without taskamanager and a working lock-button.... any help?
EDIT2: after rebooting without the simcard, the same error shows...
ipwngeek said:
Hi guys!
Yesterday, i used towelroot to root my phone, and installed Safestrap with TWRP as my recovery.
I booted my phone after everything was done, and it worked fine. This is where i screw up... I installed Softkeyz (I thought it might work for the Note 3, but...)
After i installed Softkeyz, and rebooted the phone, my status bar was gone, the background was blue and my task manager didnt work. I went back into the softkeyz app and clicked the "backup" button, wich is said to revert everything back to normal. It didnt.
When i booted my phone after the backup, I still had the same problem.
I then did a Titanium Backup, and went into recovery to factory-reset. it seemed to work, but when my phone boots, I get to the languane selection screen, and then this pops up: "KeyguardTestActivity has stopped". If I click 'OK', the same message pops up and im unable to click "next" or select a language.
I went back into recovey, wiped dalvik, wiped cache, I event formated /data in case there was any virus or anything I had downloaded, did a factory reset, and it stil doesnt work....
I had a ROM on my phone, but it used AROMA so that doesnt work with Safetrap... Now my memory is clean, my phone wont boot, and I cant move any files to the SD-card through regular MTP. I guess I have to use ADB (safetrap can sideload ADB) but I have no idea how to use that, and I have no idea what ROM to use, to get my phone up and running.
I use my phone for work and for studies, and the only reason I wanted to root was for AD-blocker and better batterylife...Now I've messed up..
I've tried searching google and the forums, but cant seem to find any fix. Can anyone out there help me? Please?
EDIT: If i boot the phone WITHOUT the simcard, the error message is gone, but if the screen locks, then in wont unlock. Taskmanager still doesnt work. I managed to get to phone running though, but without taskamanager and a working lock-button.... any help?
EDIT2: after rebooting without the simcard, the same error shows...
Click to expand...
Click to collapse
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
Hey man!
I'm so embarassed I didn't think of the SD card... Now my only problem is that I cant seem to find a ROM that will work... I tried the heisenberg one, but it says "failed" when trying to flash it...
EDIT2: It seems as its my lockscreen that is broken. would that be assosiated with the Kernal? I got a ROM, and it worked, but the same error still occurs..I'm thinking that the Softkeyz-app messed with my kernel, and now killed the phoes lockscreen/kernal. Need a new kernel I guess... but thats messing with something I've never done... any stock kernel?
Danny201281 said:
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
Greeeat... I tried flashing the Pacman rom, everything seemed ok, but now i can only boot into the safestrap recovery, and when trying to boot into the system, both with pacman and after trying to wipe everything, it just goes into a black screen...
ipwngeek said:
Greeeat... I tried flashing the Pacman rom, everything seemed ok, but now i can only boot into the safestrap recovery, and when trying to boot into the system, both with pacman and after trying to wipe everything, it just goes into a black screen...
Click to expand...
Click to collapse
sorry dude don't know what to suggest, I don't know safestrap, is it necessary to use or can you use a normal recovery? Safestrap seems very different compared with a normal recovery as it bypasses locked bootloaders and allows for multibooting roms. Are you sure you set it up correctly? Did you make a recovery backup before you started flashing anything?
personally best answer I can give you right now is flash an ruu with Odin to get your phone working, then try rooting again after you've researched it a bit.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
---------- Post added at 01:22 PM ---------- Previous post was at 01:06 PM ----------
The link below has a list of stock firmware. Find the correct one for your phone model and download it. At the bottom of the page there is also a link to download Odin and the phone drivers if you need them. As long as you can boot to download mode you can unbrick from pritty much anything with this.
http://www.androidrootz.com/p/galaxy-note-3-stock-firmwares.html?m=1
You can also use Odin to root and install CWM recovery. There's a guide in the link below for this
http://wccftech.com/how-to-root-and-install-cwm-on-galaxy-note-3-sm-900/
Good luck man
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
sorry dude don't know what to suggest, I don't know safestrap, is it necessary to use or can you use a normal recovery? Safestrap seems very different compared with a normal recovery as it bypasses locked bootloaders and allows for multibooting roms. Are you sure you set it up correctly? Did you make a recovery backup before you started flashing anything?
personally best answer I can give you right now is flash an ruu with Odin to get your phone working, then try rooting again after you've researched it a bit.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
---------- Post added at 01:22 PM ---------- Previous post was at 01:06 PM ----------
The link below has a list of stock firmware. Find the correct one for your phone model and download it. At the bottom of the page there is also a link to download Odin and the phone drivers if you need them. As long as you can boot to download mode you can unbrick from pritty much anything with this.
http://www.androidrootz.com/p/galaxy-note-3-stock-firmwares.html?m=1
You can also use Odin to root and install CWM recovery. There's a guide in the link below for this
http://wccftech.com/how-to-root-and-install-cwm-on-galaxy-note-3-sm-900/
Good luck man
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
I'm working on a Odin now... lets hope it works... ghaa...
ipwngeek said:
I'm working on a Odin now... lets hope it works... ghaa...
Click to expand...
Click to collapse
As long as you have correct firmware should be fine, wrong firmware won't flash though so don't panick about that
also make sure you run Odin as administrator and use default options don't tick any boxes manually
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
ipwngeek said:
I'm working on a Odin now... lets hope it works... ghaa...
Click to expand...
Click to collapse
and the verdict?
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
and the verdict?
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
I'm the worst guy ever,... totally forgot to answer (to be honest, I thought I replied, but my phone didnt actually send the message!)
It worked well! I now just got a LG G3 though, so yaay!
OK so I know there is A TON of info on these forums.
I searched around but I did not see anything similar to my situation.
If there is a thread, please just link it and ill delete this thread.
Basically I had rooted my N7 back earlier this year and had a custom rom as the 5.0 OTA made my N7 run like crap.
It was fine until the last few months, it got REALLY slow. I didnt update it, or mod it other then flashing the roms.
So I set out to get a new rom. I figured id try the 6.0 AOSP rom.
DL it, as well as the GAPPS and tried to install it. All I ever got was a continuous error saying, "setup wizard has stopped".
Searched some more and saw that someone fixed it by installing a bare bones GAPPS and then WIPING Dalvik and cache immediately after flashing GAPPS.
I did this and no change. Still an error.
So I noticed that when I was in Windows, my N7 showed as having 5+/- gigs free out of 13gb.
So I figured let me wipe this whole thing clean and start fresh.
BTW- this has all been done with Wugfresh toolkit.
So I went ahead and erased/ formatted and planned to return to stock and then re-root and flash a 4.44 rom as I saw that on the grouper nothing over 4.44 works great and all I want is a stockish N7 that stays fast and works 100%.
Well now all I get is the Google scree with the Unlock icon and a green start icon and when you try to go into bootloader it says booting failed in upper left corner.
Any ideas hahaha.
Thanks!
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
twics said:
I never used Wugfresh ......Are you able to get to recovery? If so what recovery do you have?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------
Check this out I use it on my 2012 N7.......http://forum.xda-developers.com/showthread.php?t=2533035
[ROM][4.4.4 STOCK KTU84P][BSZKitKat v1.6][SuperSU|ZipAlign|DEODEX|ODEX][20/06/14]
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I had the latest twrp recovery, I think 2.08 ?
I can't seem to get to the recovery screen.....only the bootload screen.
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
twics said:
Well your bootloader is unlocked so you should be able to flash recovery again via ADB...when you are pressing the volume buttons to select recovery or bootloader is there an option for recovery? If so what does it say or do why you can't get to recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
NO!! Your device is not toast if it powers on then it should be recoverable, my advice forget WugFresh check out this page on how to get TWRP installed> https://twrp.me/devices/asusnexus72012wifi.html for latest twrp recovery, on this page you will find info how to get ADB running properly, once you have Twrp recovery installed try this Rom it is stock Lolliopop and runs great better than previous ones http://forum.xda-developers.com/nexus-7/development/rom-t2931064
---------- Post added at 02:00 PM ---------- Previous post was at 01:54 PM ----------
Please let me know how you get on. also if you get TWRP installed wipe everything apart from internal storage before install Rom.
1993cb7 said:
Sorry I disappeared, I got busy with school and I just put the device to the side.
I am trying to get it restored but no matter what I do, wugfresh just hangs "waiting for device".
It finds it via ADB...
i tried doing a restore with my backup, tried flashing stock/recovery...
All I get it the main screen with Google and the unlock icon....If I hit the volume rocker I can jump to the bootload screen but when I try to jump to recovery it says "boot failed" in upper left corner.
Any ideas or is this thing toast?
Click to expand...
Click to collapse
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
twics said:
Hi there and a happy new year .....well guess what iv got the same issue as well now and I'm also using WugFresh I can reboot bootloader from NRT but that's it can't get to recovery can't write to recovery can't flash recovery all I can do is to TWRP temporary via NRT ,but still can't write to it, I read somewhere that the internal SD is fried which is why I can't write to system which means can't flash Recovery or Rom which mean can't reboot system so unfortunately for us its looking like a new motherboard or new tablet.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
1993cb7 said:
Did you ever get it sorted out?
Im trying to fix mine because someone wants to buy it so Im going to spend all night working on it. If I get anywhere ill let you know.
Click to expand...
Click to collapse
OK Im back. Roughly an hour and a half. Not bad.
So what I did(if you're stuck on the bootloader screen like me)
Updated to the latest version of Wugfresh.
Made sure it updated all of the files it needed etc.
I then went through the process of uninstalling and reinstalling the drivers for ADB etc. I actually had an issue with it not detecting my device so it recommended installing the generic Google drivers....I did that.
Even after doing that, when I would check ADB connectivity it would say no devices found. I remembered that sometimes it would still communicate with the device even though it said nothing was found. I decided to do a fastboot format under advanced utilities because I knew that i erased it previously and I think that is where I ran into problems.
Sure enough adb found my device and formatted the bootloader no problem. I then continued with the restore to stock/w boot loop function and had patience...it took FOREVER to load the system image and then it took like 10 minutes to reboot but it did and I have a fully functional device right now.
I logged in and turned USB debugging on and re-locked the device. I then did a system wipe from inside the system and will sell it tomorrow.
So have faith, its not over till its over.
and p.s. I changed the USB port that I was plugged into. I have a USB hub that I usually connect too but I figured id connect directly to a USB port on the machine. Not sure if that helped, but people recommend it anyway.