Database Develop

Recovery - Red exclamation mark and red triangle.

- Did google searches and on here but my problems seem different to others or I don't understand the solution.
I installed the stock orange latest rom not knowing it would rid me of root and all that so I'm trying to get back to recovery so I can nanbackup back to leedroid.
What I have done so far -
1) Downgraded (was an absolute pain, took many attempts seems that rooting twice screws things over)
2) Rooted using visionary+ - comfirmed I am rooted
3) Installed rom manager and reflashed recovery with it.
4) Open recovery and get a Red exclamation mark in a red triangle.
Interwebz tells me this means I have no recovery or am not rooted. I am rooted and I have reinstalled recovery.
What have I got to do to fix this?
Please do help
:EDIT:
had an idea while trying to cold boot into it it is reading the file i have on there to downgrade with and I think that is causing the problems.
:EDIT2:
didn't fix it. Sigh. Really need help guys.

8igdave said:
- Did google searches and on here but my problems seem different to others or I don't understand the solution.
I installed the stock orange latest rom not knowing it would rid me of root and all that so I'm trying to get back to recovery so I can nanbackup back to leedroid.
What I have done so far -
1) Downgraded (was an absolute pain, took many attempts seems that rooting twice screws things over)
2) Rooted using visionary+ - comfirmed I am rooted
3) Installed rom manager and reflashed recovery with it.
4) Open recovery and get a Red exclamation mark in a red triangle.
Interwebz tells me this means I have no recovery or am not rooted. I am rooted and I have reinstalled recovery.
What have I got to do to fix this?
Please do help
Click to expand...
Click to collapse
ok my friend this could happen because you are not ablr to root the DHD perhpahs it has the last OTA or used an RUU to actualize to last version, doublecheck the firmware version on the phone, then i will explain a little more (i know its painful already have been victim by the rooting process)
good luck

I am getting so god damn pissed off with this. As I took my battery out for the 100th time I thought to my self mmm this is gonna break if I'm not careful and out pops my volume rocker. Had to bend it to get it back in. Don't evne understand why this is all happening. I did this all fine the first time around.
Firmware is 132.405.6
The rooting isn't the problem, its recovery which is.

Just discovered holding up and pushiung power button is meant to get you into CWM but i get "E:can't open /cache/recovery/command"
Annoyingly it lets me reboot and would ahve saved my volume rocker
:EDIT:
Christ I forgot to plug my phone up to the pc and run s-off. What a bloody moron.
I couldn't hate my self much more right now *strokes his bent volume rocker*
:EDIT2:
S-OFF didn't fix it either :/
Infact I can now no longer boot into recover, it freezes at the HTC logo.

Now that you have S-OFF, go to ROM Manager and reflash the ClockworkMod.
Sent from my Desire HD using Tapatalk

jkoljo said:
Now that you have S-OFF, go to ROM Manager and reflash the ClockworkMod.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
That didn't work, I had to manualy install it in the end. I now have V3.0.0.5 but I can't restore my backup because:
E:Format_volume: no MTD partition "boot"
What does this mean and how do I fix it? I need to get that backup back! It has everything :O
That backup was made with a V3 CWM. But I hear I need V2 to use with froyo? GAHHHHHHHHH.
Got to downgrade CWm now I guess. EURGH!

Rom manager wouldn't downgrade but I tryed upgrading to 3.0.0.6 in a hopeful attempt and appears to be working XD.
Then after alllll this I have to find out how to fix my echoing as it works on the stock rom so must be something i need to do to leedroid. I'm thinking radio change?

so i assume you finally downgraded to a "rooteable" android version... if still need help, send a PM so i will try to help u!
good luck!!

8igdave said:
I am getting so god damn pissed off with this. As I took my battery out for the 100th time I thought to my self mmm this is gonna break if I'm not careful and out pops my volume rocker. Had to bend it to get it back in. Don't evne understand why this is all happening. I did this all fine the first time around.
Firmware is 132.405.6
The rooting isn't the problem, its recovery which is.
Click to expand...
Click to collapse
.... got it, you hace to plug the hd to pc, debbugginng on, (charge only) download the rom manager, reflash the klockwork, and try again
good luck!

Please help. Phone not bricked but cant root

Good Evening everyone. As the title says i need help.
I have had my phone rooted fine in the past but went ahead and did the .893 update wich is where something went screwy. It booted fine after doing the .893 update however after doing a reboot it would not boot. just stayed at the M dual core. I think something went wrong on the update because all my apps were still there when it did boot.
So i tried doing a return to stock using the RSD lite program..that fails right away no matter what i do.
So i went and tried to do the One click fastboot system restore program.
Now when i did that the INFOpreflash validation failure showed up however everything else went through fine. the phone reboots and everything works just not great the signal strenght is very low.
The version that got installed says 5.5.1_84_dbn-55. So i try Pete's root method and it go thru to step 2 but then fails at rebooting for the second time saying it could not get root via local.prop.
If anyone could please help me get back to normal stock it would be much appreciated

Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium

P.S. You are stock now.
Sent from my DROID BIONIC using xda premium

harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App

dubsx said:
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Or XDA?
Sent from my DROID BIONIC using xda premium

I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed

that too, haha...
Sent from my DROID BIONIC using XDA App

Sidewind75 said:
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
Click to expand...
Click to collapse
Well, you didn't list that in the OP.
At this point, I don't know. Here is all I got: enter stock recovery and wipe everything. Reboot. Cross your fingers.
Sent from my DROID BIONIC using xda premium

mistawolfe said:
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!

quentin0 said:
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
Click to expand...
Click to collapse
Sometimes the truth hurts. He messed up. Don't shoot the messenger.

Moderator Message
Breathe in, breathe out!!!!

I'll breathe when this .893 goes through and I keep root

There is also some very seriously contradictory info in the OP. While castigating him for being a noob did anyone notice that he claims to have flashed the update and then reverted to stock?
This is impossible from our current understanding of how the bootloader works.
More information about the exact steps followed and the exact results at each step would be very helpful to try and figure out what really happened.
OK?
Less heat and more light...

I just got a little frustrated, as every time I open XDA today I see the same/similar post.
Cell - I didn't see in the OP where he said he flashed back. I read where he tried, but I didn't see any mention of 896.

I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated.
Oh and i have also tried to unroot it..it also fails at adb not being able to gain root access

Sidewind75 said:
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated
Click to expand...
Click to collapse
This isn't going to help your current issue, but how long did you let it sit (after installing 893) before you decided it wouldn't boot? I ask because the guy who was ballsy enough to do it here said the first boot takes about 7 minutes.
EDIT: Nevermind - mine booted in 2 minutes.

it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible

Sidewind75 said:
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Click to expand...
Click to collapse
Try to do the fastboot again and root it through there. Or, if you did that already (root in fastboot restore) try rooting afterwards.

Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.

tghockey07 said:
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
Click to expand...
Click to collapse
yes I did and i checked it twice after making sure root explore was closed reopened and checked the file the chmods where there...but now they are not. and seeing as how i cant root i cannot get them back on it

Revolution Problems

Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"

Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.

My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.

Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App

Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.

Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk

Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.

Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.

STUCK on Android is Updating" Starting Apps Swirl"

Okay, so now we have 3 Atrix HD's in the house and except for the unremoveable battery thing, and the short "battery life" when actively using it, I'd say we pretty much love them. However, I decided to remove some apps, etc. and managed to get my messages, camera and gallery to the "not working" and basically non-existent point. Now on startup I'm getting the Android is Updating message with the never-ending swirl of Starting Apps... I'm positive I've waited long enough as I set it down and went back to bed just to wake up and still see it.
Info - phone IS rooted
running the "jellybean" update
Unfortuanately a couple weeks ago, I UNCHECKED the sync photots for both facebook and gmail, so there are pictures I really don't want to lose.....
I'm definitely not a "pro" like lots of them up here, but am capable of following directions. I'm pretty sure I have to "unroot" my phone via USB/SD card through my laptop....Any help would be greatly appreciated... and the more specific the directions the better!! :cyclops: LOL... Thanks so much.
/COLOR]

Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?

Don't remeber...
ai6908 said:
Sounds like you deleted a critical OS file. You need to flash back to stock again. Is your boot loader locked or unlocked?
Click to expand...
Click to collapse
I Don't rememer if I unlocked the bootloader. Is there a way to check? Thanks.

Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html

ai6908 said:
Follow what's in the website to reload your stock image...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html
Click to expand...
Click to collapse
I've been trying and I've fallowed everything to the T but everytime it says it falls.

I'm not sure...I have used it before and was able to restore...are you sure it's not a hardware issue?
Sent from my HTC_Flyer_P512_NA using xda app-developers app

Okay, here's where we're at.... it is no longer frozen on that screen and goes thru the setup w/ my gmail, etc.... but then I have a black screen (except for the top row icons...). I can pull down the settings menu and see everything there, but I have no "homescreen"....It's black. It seems like we're in the right direction and I know it's not dead. Anything??
Also wanted to thank you for the help. This place is ALWAYS amazing....

Hey, my son and I are wondering since it's already running 4.1.1 and we can't downgrade, what about flashing a custom rom? Will that flash a totally complete, full home page and everything?? Just a thought.

While trying to search for answers I came across a "xoom forums??" post with a tablet that was doing exactly the same thing....multiple people had that problem, but doesn't seem to have been answered...... not sure if I'm suppose to post links to that or not, but at least I know I'm not alone.....

If you're rooted, than I'm assuming ADB debugging is on. You should be able to unlock your boot loader and load CWM recovery. From there you can wipe cache and dalvik cache. If that doesn't help, you can reflash a stock ROM zip from Skeevys thread. Flashing a zip won't touch your SD card

There is official 4.1.1 available...you can try flashing that...you dont need to downgrade.

Okay, my son installed safetystrap (whatever that is...lol) and when you click Operating system, it says "there is no operating system installed are you sure you want to reboot????
Is this fixable?
Note: We have two other identical Atrix HD's in the house if that helps for any reason.....

Well that's what we are trying to figure out is how to install OS...Lol..
Try install system using fastboot... Look for skeevedudes guide...its in this forum somewhere...
Sent from my MB886 using xda premium

LOL....okay, so do yoiu see why my son says I'm not "ALLOWED" to have a rooted phone if this happens again..... Guess I was just glad to SEE it written out, so that it's a little more def what's going on - but I'm sure everyone up here (except me) already knew that!!!
He's not around today, so my phone is just "sitting" saying "creating rom slot" but never gets off that screen. The good thing is that we can see it's actually charging and we weren't sure before....... Does this sound like something that will eventually be repairable??

You have a soft brick...yes it is fixable...

Okay, thought I had already posted this before but I guess I never hit the submit ....
Before safety strap was installed, we could get the phone (minus the homescreen and os) to come on....the settings, wifi etc.....No we can't seem to get to that point with the safetystrap on. It just goes completely blank and won't let safestrap connect to the computer via usb.
Apparently there is also no way to remove SS without an opperating system. This doesn't sound promising.....ugggg..... I so want my phone back.
Any help would be greatly appreciated.

OK dude. Follow my instructions.
Hold down power and both volume buttons all at once until the phone screen turns black, then continue holding the volume buttons. You will get a menu. Go to AP fastboot mode using the volume down button, select it with the volume up button. Plug your phone into your computer with a data cable. Download RSD lite and the MOTOROLA drivers from the MOTOROLA website. Install both. Download the 4.1.1 sbf file for your phone, there is a thread for it here in the AHD forum. Its a zip file, extract it to your desktop. Open RSD lite, click the browse for file button, select the XML file inside the folder you just unzipped. Hit flash. If you get any errors, let me know I'll send you a different XML file with the getvar lines removed.

Okay, will get it started..... Thanks so much. My son has been working on this for hours and hours. You have no idea how much I appreciate this place and everyone who helps out!! You guys rock! Will let you know what we get.

Here is the website for what youngunn mentioned...
http://www.andromods.com/tips-trick...-qinara-stock-original-firmware-fastboot.html

[FONT="Comic [SIZE="3"]Okay, my son (BlackestPain) is too new here to post the picture links, so I copied and pasted. They're just downloads from his camera pictures. This is where we are right now after following suggestions....[/SIZE]MS"][/FONT]
Okay, here is what I've (chixwithkidz5' son) tried.... Please cut me some slack because I haven't been doing this stuff long....
Getvar file
Getvar removed
RSD Lite connected
RSD Lite failed
\
***** this is what the phone reads after everything
What am I missing ? Thanks - I can use all the decent help I can get.

HTC One Can't Update With Root?

Ok please bare with me I'm new to the rooting scene. Ok, so as some of you may know there's a new update (6.10.531.10 - something about audio issues). So, I keep getting the notification to update and I've been trying to update for a while. Now, my phone (HTC One T-mobile) is rooted and every time I tried updating it would take me to the TeamWIN reboot thing (I don't know what to call that). So, I did some research and it turns out I had to install a stock recovery, update, then reinstall my custom recovery. So, I did install a custom recovery and everything is fine (not sure If it was, but my CID is TMOB010, something like that). However, the problem occurs everytime I press install it reboots fine and it goes into the green triangle downloading, then it goes all the way or close to it and it switches to a Red Triangle With an Exclamation Mark, and theres nothing I can do from there. The only thing I can do from there is hold the power button and wait for it to restart and it goes back to normal, and the cycle repeats again. Can someone please help me?
Edit: IDK if it helps but I have S-ON.

2DTheBeast said:
Ok please bare with me I'm new to the rooting scene. Ok, so as some of you may know there's a new update (6.10.531.10 - something about audio issues). So, I keep getting the notification to update and I've been trying to update for a while. Now, my phone (HTC One T-mobile) is rooted and every time I tried updating it would take me to the TeamWIN reboot thing (I don't know what to call that). So, I did some research and it turns out I had to install a stock recovery, update, then reinstall my custom recovery. So, I did install a custom recovery and everything is fine (not sure If it was, but my CID is TMOB010, something like that). However, the problem occurs everytime I press install it reboots fine and it goes into the green triangle downloading, then it goes all the way or close to it and it switches to a Red Triangle With an Exclamation Mark, and theres nothing I can do from there. The only thing I can do from there is hold the power button and wait for it to restart and it goes back to normal, and the cycle repeats again. Can someone please help me?
Edit: IDK if it helps but I have S-ON.
Click to expand...
Click to collapse
This post will explain what the OTA is looking for: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
This post will explain how to find out what you are missing: http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Once you know which files are missing then you can find the files and try the OTA again.
Or, run the last RUU to reset your system then download the OTA.

majmoz said:
This post will explain what the OTA is looking for: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
This post will explain how to find out what you are missing: http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Once you know which files are missing then you can find the files and try the OTA again.
Or, run the last RUU to reset your system then download the OTA.
Click to expand...
Click to collapse
How do I find the last RUU and how do I do that. Do I just download it straight from my phone and then run it within the phone itself then I update. Also, will I still have my Root Access?

2DTheBeast said:
How do I find the last RUU and how do I do that. Do I just download it straight from my phone and then run it within the phone itself then I update. Also, will I still have my Root Access?
Click to expand...
Click to collapse
Please follow the rules you agreed to when you joined. All this info has been covered hundreds if not thousands of times already.