Database Users

[Resolved] HTC Aria 2.1-update 1

^Fixed it. No problem now.

TKTAB911 said:
Am i screwed?
I know 2.2 is basically unrootable [for now], but is 2.1 update 1 the same or am i totally missing something?
I've followed several tutorials on Youtube but got nowhere. I've deleted/uninstalled the standard drives many times. Theres a step that i've seen on other peoples phones but not mine. When Down-volume and power button are held i only get;
-FASTBOOT
-RECOVERY
-CLEAR STORAGE
-SIMLOCK
Help?
Click to expand...
Click to collapse
The AT&T 2.1 update 1 is very rootable. Just use Unrevoked 3.32 at http://unrevoked.com/recovery/

when you power + volume down, wait for it to do its thing then go to recovery lol

Ive tried unrevoked3. It just sits at the main screen telling me its waiting for the device to be connected/enable debug mode and to make sure HTC software is *not* installed.

TKTAB911 said:
Ive tried unrevoked3. It just sits at the main screen telling me its waiting for the device to be connected/enable debug mode and to make sure HTC software is *not* installed.
Click to expand...
Click to collapse
Have you ever installed HTC Sync on the PC? You need to do that because it places some drivers on the PC that Unrevoked needs. After you install HTC Sync you can remove it and it will leave the drivers in place.

Yeah, i've messed with it for about 3 hours now. Uninstalled-reinstalled. Tried doing it all in different order. Tried it on windows 7 [this pc] and Windows Vista.
Figured i'll just cut out all the extra b.s. with drivers and go with this method;
http://forum.xda-developers.com/showthread.php?t=741824

TKTAB911 said:
Am i screwed?
I know 2.2 is basically unrootable [for now], but is 2.1 update 1 the same or am i totally missing something?
I've followed several tutorials on Youtube but got nowhere. I've deleted/uninstalled the standard drives many times. Theres a step that i've seen on other peoples phones but not mine. When Down-volume and power button are held i only get;
-FASTBOOT
-RECOVERY
-CLEAR STORAGE
-SIMLOCK
Help?
Click to expand...
Click to collapse
Im pretty sure I know what youre talking about with that extra step that shows up, The aria doesnt have it all you do is go to recovery. The video which I saw, which may or not may the one you saw, was one where a guy was doing it with an evo which is very similar but the evo includes that extra step.
I had this same problem I didnt know where to start because I didnt see that step but I was told I didnt need it

[Q] Having issues with GB Leak and cant sbf back to .340 need help please.

I flashed the deodexed pre rooted gb leak and have had nothing but problems since flashing it and now i wish to got back to stock using sbf but for some strange reason my droid x is not being seen by rsd lite. I have installed all the appropiate drivers and followed procedure to the letter as far as what i can see on the thread about reverting from leaked gb to .340 based rom and still no luck. Ive googled til my fingers are sore and still no luck. any insight as to what i am doing wrong or what i could do to remedy this situation would be greatly appreciated. for some strange reason i dont have super user access any more and i cant boot into recovery mode either. im running windows 7 64bit edition. if any other info is needed just let me know as ill be around here all day til i can fix this problem. thanks in advance.

I had the same issue for about 2 hours myself, rsd lite apparently has a major malfunction with cooperating with windows 7, what I recommend and what I did was use my netbook with windows xp. So I would suggest trying that if you have access to a computer with it

hanone said:
I had the same issue for about 2 hours myself, rsd lite apparently has a major malfunction with cooperating with windows 7, what I recommend and what I did was use my netbook with windows xp. So I would suggest trying that if you have access to a computer with it
Click to expand...
Click to collapse
Thanks will definitely give that a try and report back my results.

Are you putting your X into bootloader mode? Hold home + power to boot into the bootloader. It should been recognized by RSD after that.

Trongable said:
Are you putting your X into bootloader mode? Hold home + power to boot into the bootloader. It should been recognized by RSD after that.
Click to expand...
Click to collapse
Yes ive tried that method as well as the power + vol down + camera button and still no luck. dont have access to an xp pc atm but as soon as i do im going to give that a shot. still open to suggestions in the mean time. thanks a million to those who have already responded.

config >device id >first come first serve worked for me That is ofcourse after your in bootloader mode.

I had the same issue, win XP worked fine when i had this problem months ago

blueis300 said:
config >device id >first come first serve worked for me That is ofcourse after your in bootloader mode.
Click to expand...
Click to collapse
yes this worked for me too i was having problems too i thot but playing around i found that setting and it worked for me as well

[Q] Please Help Immediately

Please hep immediately!!!!!!!!!!!!!!!!!!!!!! I Recently got a Kindle Fire And immediately when i got home i rooted it with no problems with burritoroot. Then after that I found a way to get The android Market on there And i was so happy. Then After that i began to flash the custom recovery on it everything went perfectly fine until i got to The Yellow Triangle on the the Kindle file and it told me to push the power button and it was waiting for device on laptop. So when i pressed the power button nothing happened so i pressed and held it and it did nothing but turn off and come right back to that screen I was waiting at the screen for an hour till i gave up and exited the Kindle Utility program on cmd and tried it without it now im stuck with this stupid yellow triangle on my screen and wish to got to my kindle os Can someone help me please??????
PS: I have all drivers Installed and followed the Video very thoroughly
I Exited out of Program before completion

It doesn't seem like this is the issue, but you could try changing the boot mode in adb to regular, instead of fastboot, its all i can think of right now. Does the device show up in adb?

Yeah, it sounds like it might be in the wrong boot mode.
Try using this utility if you haven't already. It helps a lot.

I tried That But I cant do that because My device driver is showing up as uknown and it wont let me update it so i cant access it T_T its just sitting there with a yellow triangle

this is where i can't help you, i only know mac stuff, no pc drivers crap and stuff, hope you find help elsewhere.

im bout to sob can someone please help me i just got this with the remainder of my money

oshea1995 said:
im bout to sob can someone please help me i just got this with the remainder of my money
Click to expand...
Click to collapse
You are stuck in fast bootmode, it's not a big deal, there a ton of threads and post about how to get out of it. Search and you should find what you need, if not I can try to walk you through it but I'm no expert.
---------- Post added at 10:09 PM ---------- Previous post was at 10:05 PM ----------
I found this... http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222 it's how I got myself out of fastboot.

You also might try reinstalling the drivers from the device manager. Your situation sounds similar to one I encountered and I solved it by reinstalling the drivers.
Sent from my SAMSUNG-SGH-I727 using xda premium

Like everyone said, it's no big deal. You need to reinstall the drivers and change out of fastboot mode (4002) and into regular boot mode (4000). This thread has it all in the first post:
http://forum.xda-developers.com/showthread.php?t=1417234

don't sob, calm down, it will be alright. I assume you are young, so almost bricking a device may give you a heart attack, but there is almost always a way out of it. For right now, take a break from the device, get your mind off of it, and come back later, it WILL be alright.

Power the kindle all the way off.
Power it all the way back on.
Install drivers.

Vashypooh said:
Power the kindle all the way off.
Power it all the way back on.
Install drivers.
Click to expand...
Click to collapse
This will work!. When Vashypooh says to install the drivers he means to do it manually like this here is a quote from my thread on the complete video guide that would have answered these questions for you and fixed your problem immediately:
• I have also noticed that some people also get stuck at 3:55 in this video at the firefire triangle. The fix for this is fairly easy and is explained in the video if you need a walkthrough step by step for doing this (Updating the drivers)here you go:
- Go to start Menu and right click on computer, Click manage
- In computer Management hit device manager
- I am guessing that you see your kindle connected in there with a yellow ! by it
- Right click on kindle and update driver software
- Click Browse my computer for driver software
- Click let me pick from the list of device drivers on my comp
- Click Next
- Click Have Disk
- Click Browse
- Navigate to your user folder in that window/ or wherever your .android folder is
- Double click on .android folder
- Double click on Driver Folder
- Now Click open
- Now click ok
- Click Next
- ClickInstall driver software anyway
and you should be okay!
Here is that thread on the complete video guide that I find have answered many others questions....
http://forum.xda-developers.com/showthread.php?t=1417234

R2D2 - Bootlooping, SBF failed 0x70BE

Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!

http://droid.koumakan.jp/wiki/SBF
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html

Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!

ezsbf has helped a lot of people
Sent from my MB870 using xda premium

so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas

Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2

did you try wiping cache or data?

delete this

jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up

LG Flash Tool crashed while flashing, phone bricked

Hi,
I was about flashing stock rom (following this thread and using CSE Flashing mode), when suddenly LG Flash Tool crashed on windows (I hate windows). Flashing progress stuck at 16%, so I press and hold power button to power phone off. but when I tried to enter to Download Mode, phone start too boot, and after LG logo, screen keeps going on and off (showing black screen)
I tried to enter to recover or factory hard reset, but it going to Factory data reset, even if I confirm reseting data it would try to boot same as when I tried to get Download Mode.
adb does not work
I followed this thread, but /dev/sdb1..36 just available for a few second and then disappear, after a while they are available and then disappear, and this will going on, (I think this is related to that screen on and off thing)
Would someone help me?
Sorry for my bad english, I'm a little nervous right now

Ok, finally I could see sdb1...36 and do what have been said here, and now I stuck at LG logo at boot.
still cannot get the download mode
factory hard reset is back but it'll stuck at "Factory reset processing..."

I have really lost my respect to flashtool after this kind of errors. If someone solve that issue it would be great for our community

please help

IM SORRY
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well

berceniqgil said:
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well
Click to expand...
Click to collapse
Yes I'm still have warranty.
But I hope I can fix it myself

Mine just got this issue too. Repair center denied the phone for repairs, claiming it is user damage.
So yup, I have a neat paperweight now.

berceniqgil said:
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well
Click to expand...
Click to collapse
Zulake said:
Mine just got this issue too. Repair center denied the phone for repairs, claiming it is user damage.
So yup, I have a neat paperweight now.
Click to expand...
Click to collapse
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer

abdulkadiro said:
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer
Click to expand...
Click to collapse
Ubuntu is running in a VM, so I would need Windows to find the phone first.
Unfortunately, Windows never sees the phone.
It's weird though. TWRP got successfully flashed during the QHSUSB_BULK guide method, but I cannot boot into it.

Zulake said:
Ubuntu is running in a VM, so I would need Windows to find the phone first.
Unfortunately, Windows never sees the phone.
It's weird though. TWRP got successfully flashed during the QHSUSB_BULK guide method, but I cannot boot into it.
Click to expand...
Click to collapse
Maybe you had a bad download try an another base

abdulkadiro said:
Maybe you had a bad download try an another base
Click to expand...
Click to collapse
I lost QHSUSB_BULK mode now, the PC won't see the phone anymore and all modes are gone.
No download mode, no recovery, no ADB, no fastboot, factory reset freezes, nothing works.

Zulake said:
I lost QHSUSB_BULK mode now, the PC won't see the phone anymore and all modes are gone.
No download mode, no recovery, no ADB, no fastboot, factory reset freezes, nothing works.
Click to expand...
Click to collapse
If you see the lg logo maybe you will have a change. A guy who had the same results like you brings his phone plugged for 10-15 minutes than he have find his phone in download mode. Of course he plug the cable while holding the down button. I hope you will get your phone back with its functions

abdulkadiro said:
If you see the lg logo maybe you will have a change. A guy who had the same results like you brings his phone plugged for 10-15 minutes than he have find his phone in download mode. Of course he plug the cable while holding the down button. I hope you will get your phone back with its functions
Click to expand...
Click to collapse
Well, that's worth the try.
I just connected it while holding volume up.
Hopefully it will still charge when connected.
//Well, it's been about 15 minutes now and it still displays the LG logo.
Guess I'm outta luck on this one.

Zulake said:
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer
Click to expand...
Click to collapse
I tried that on my ubuntu laptop, ubuntu did not detect the phone
Zulake said:
Well, that's worth the try.
I just connected it while holding volume up.
Hopefully it will still charge when connected.
//Well, it's been about 15 minutes now and it still displays the LG logo.
Guess I'm outta luck on this one.
Click to expand...
Click to collapse
I read this post one more time, this guy who had download mode after 10-15 minute, have discharged the phone then do what he said. have you try that?
I have discharged my phone, but I'm going to work right now, later today I will try and let you know if it was fixed or not

Behzadsh said:
I tried that on my ubuntu laptop, ubuntu did not detect the phone
I read this post one more time, this guy who had download mode after 10-15 minute, have discharged the phone then do what he said. have you try that?
I have discharged my phone, but I'm going to work right now, later today I will try and let you know if it was fixed or not
Click to expand...
Click to collapse
I won't dare doing that, as it doesn't seem to charge anymore.
I'm gonna retry sending it in today, otherwise it's going into the bin.

I tried one more time last night when phone was fully discharged. nothing has been changed.
Zulake said:
I won't dare doing that, as it doesn't seem to charge anymore.
I'm gonna retry sending it in today, otherwise it's going into the bin.
Click to expand...
Click to collapse
Hopefully it start charging.