Database Users

Any advise?

I recently upgraded my G1 to the cyanogenmod 2.1 ROM and everything went fine untill i went to the market and installed a program called ROM manager. while i was using ROM manager it had an option, i cant remember what its name was, that said it fixes FC's if needed. Well i was getting those in ROM manager so i clicked it. It did a bunch of stuff and then suddenly tossed an error at me. Next thing i know im getting LOTS of FC's and when i rebooted my phone im suddenly stuck staring at the G1 boot screen and thats where it stays......indefinetly.
I cant get into recovery mode, already tried that. And so far the only thing(that i know of) that i can do is get into fastboot. Does anyone know how i can fix this? Its gotta be software related from whatever that ROM Manager program did to my permissions. But now im basically bricked and cant do anything.
My storage card still has all of the ROM's and files from when i flashed last but i dont know if or how i can use that to re-flash my phone again and start over.
Any suggestions?

I had a similar issue just yesterday. Dowloaded rom manager from the marketplace - attempted to flash recovery - pulled an error and ended up on the G1 screen. Could not get into recovery, but fastboot was available.
I followed these instructions
( reboot holding camera button, connect usb and press back button )
on pc
HTML Code:
fastboot erase system -w
fastboot flash recovery <recovery.img>where <recovery.img> is the full path to the recovery you want to flash
I had to do a full erase in fastboot - that is the first line of text above, I then flashed my recovery.img again - that is the second line of text above (I placed my recovery.img file directly in the adb folder - so it easy to find )
Once I was able to get back into recovery - I restored my last back-up, and the phone booted once again.
If you do not have any backups - I am not aware of the next step. Hopefully someone with more experience can direct you accordingly
Good luck

How is it that you send the commands? I plug in my USB, then hit back and it says FASTBOOT USB but how do i input the HTML codes to get it to do anything?
Do i make an HTML file on the pc and upload it, if so, how? I understand all of it except how to get the commands into it.
Well that and what the full path will be for the recovery.img.

well i feel like a total moron !!! lol
I had been being a script kiddie for the last few years and forgot my roots. I got it figured out and got the commands sent to fastboot in a CMD prompt.
Ugh, i gotta stop using google so much and finding all the easy ways out of things that others have already written.
Thanks for the help, much appreciated and worked a treat. I flashed everything and its working great again

[Q] No fastboot -- is this Ion recoverable?

Hey, I've searched both here and on CM forums and even tho Firerat was the only person who gave coherent advice to the people with similar problems I figured I'd ask.
I have a Google Ion as my backup and I've been playing with the 2.2 T-Mobile OTA on it, but since it required non-engineering SPL I've decided to bring it back to CM side. I've made the goldcard and flashed the 1.5 Magic ROM using goldcard. The 1.5 booted fine on it and I've verified S-OFF in the fastboot.
I then downloaded the 1.6 OTA/recovery file for Ion from developer.htc.com and flashed it using built-in recovery (didn't flash custom recovery via fastboot first which I regret now).
Now the phone is stuck in the splash -- I've tried booting it in either recovery or fastboot and it doesn't work -- it goes into splash and stays there.
I've tried both back and Vol Down together with power to get into fastboot -- neither worked.
Did I brick it? Is there still a way to get into fastboot? Any advice/help you guys can lend?
Thanks!

stangri said:
Hey, I've searched both here and on CM forums and even tho Firerat was the only person who gave coherent advice to the people with similar problems I figured I'd ask.
I have a Google Ion as my backup and I've been playing with the 2.2 T-Mobile OTA on it, but since it required non-engineering SPL I've decided to bring it back to CM side. I've made the goldcard and flashed the 1.5 Magic ROM using goldcard. The 1.5 booted fine on it and I've verified S-OFF in the fastboot.
I then downloaded the 1.6 OTA/recovery file for Ion from developer.htc.com and flashed it using built-in recovery (didn't flash custom recovery via fastboot first which I regret now).
Now the phone is stuck in the splash -- I've tried booting it in either recovery or fastboot and it doesn't work -- it goes into splash and stays there.
I've tried both back and Vol Down together with power to get into fastboot -- neither worked.
Did I brick it? Is there still a way to get into fastboot? Any advice/help you guys can lend?
Thanks!
Click to expand...
Click to collapse
If you turn on your phone and connect the usb to your computer to you see a red box pop up at the top saying fastboot usb?

cloths55 said:
If you turn on your phone and connect the usb to your computer to you see a red box pop up at the top saying fastboot usb?
Click to expand...
Click to collapse
Nope, the phone stays in the splash screen, usb connected or not. I can get to a blue led but that's pretty much it.

well your phone is probably bricked then. If you cannot get to fastboot, recovery, or boot up then your phone is pretty much dead (it has happened to me recently too)
since your radio works (blue led) you can use a jtag adapter if you want and shock device back to life.
I am pretty sure that is your only option at this point

I thought as much, but was hoping there's an easier way to trick it to take spl and run it in a fastboot.
What did you do with your phone? Is there anyone on this forum who has the jtag cables/software to bring it back to life?

My phone is still bricked. my plan is to use a jtag adapter to save it, eventually.
Many people I am sure have the necessary hardware to get your phone in working order, and the software is free.
I have too low of a post count to post links but there are tutorials around the forums to debrick your phone with jtag adapter.
look in the dream development forum for the thread on how to debrick your phone. Also look in the general tab on the sapphire forum for the wiki page which has a link at the bottom of the wiki page to bebrick your phone.
I've read from another user that you can buy cheap jtag adapters off ebay.
It's obviously a harder process to debrick your phone than to root it but maybe its worth it to you, idk.

Bricked DHD after ARHD, Sense3.0 and CRT-ScreenON/OFF

Hey there
i debranded, rooted, downgraded and flashed Android Revoltion HD 5.1.7 on my DHD.
Everything worked fine.
Then I flashed some Sense 3 Addons (in the right order)
And everything worked fine.
THEN I flashed the CRT Addon (which was really cool :-D)
And everthing worked fine.
Well, 2 days later, I wanted to shut down my DHD over the night.
It didnt worked well, cant describe it anymore, but I had to push the POWER button more then twice to finally shut it down.
And on the next morning: the DHD only booted to the HTC Logo.
Bootloader was still there BUT the recovery couldnt be loaded.
SO, after that I used the PD98IMG and flashed it over.
But it didnt worked.
And today, the DHD doesnt even turns on.
My plan was, to connect it to the PC and flash a 1.32. via RUU.
But now, its pretty much dead.
It doesnt even lights up, when its plugged in to charge
Is there anything I could do or try?

Hi,
When you remove & reinsert your battery & plug into your PC do you get an Orange charging LED? Don't try to turn your handset on just yet.

Just tried it, and: yes, orange LED is on
/edit:
Well... that means what?
Is there a chance for hope?
or is it bricked, regardless of that

There is always hope.
While plugged in and with the Orange light showing open a cmd window and navigate to your SDK/platform-tools folder
now run
Code:
adb devices
you should get a readout of your HTC device
now run,
Code:
adb reboot recovery
You should now boot into recovery.
Perform a full wipe, system, data, cache, and dalvik cache. Then reflash ARHD again, and reboot once complete.
You will lose all un-backedup data, but your SDcard data is safe.

Damn..
When I type adb devices, it wont find the DHD..

Its definately plugged into your PC & the Orange LED is on?

Yes.
But i have to say, i had similiar problems in the past:
i couldnt use those "one click tools" for S-Off and stuff.

Have you tried to access the bootloader? Vol Down + Power.

Sure.
But that doesnt work. The DHD doesnt do anything...
Instead of the orange LED when plugged in (but only if i not tried to boot)
Btw.:
after unplugging it from the pc: the orange LED stays on. it wont go off..

i tried it on another pc,
adb devices gives out the list,
but my DHD is not listed

How many HTC devices do you have plugged in? The information it returns should look similar to
Code:
<Your SDK\platform-tools path>adb devices
List of devices attached
HT0[B]xxxxxxxx[/B]6 recovery

I have no other HTC devices plugged in.
and in my case, it looks like:
Code:
<Your SDK\platform-tools path>adb devices
List of devices attached
its just empty -.-
it DID worked on my pc - it was listed and i could 'communicate' over usb
but now, its not listed..

Keep trying, once you get a positive return
run
Code:
adb reboot recovery
or
Code:
adb reboot bootloader
Preferably recovery first.

is it still possible that it works, even if it doesnt at the moment?
ok, i'm gonna try it then
hope dies last..

try reinstall HTC Sync.

Yep just keep trying. Android is a bit unpredictable this way.
Also, just to make sure you have no other factors involved, take out the Sim card and the SD card. Just to make sure no other factors are involved.

thx for the help mates, but i dont think this gonna work.
tried it several times now, and on 3 different pc's.
it just wont work.
i called my provider yesterday and gonna send it in tomorrow
hope it wont take to long AND it wont cost to much (if the find out that its my fault ; )

If PD98IMG.zip cannot restore your phone (did it even load? It should in every case), nothing can. You have to send it to HTC. I would suggest to try PD98IMG.zip again.

Sorry - Testing -

jkoljo said:
If PD98IMG.zip cannot restore your phone (did it even load? It should in every case), nothing can. You have to send it to HTC. I would suggest to try PD98IMG.zip again.
Click to expand...
Click to collapse
At first still could access bootloader and flashed the PD98IMG
But it didnt work.
And now: i cant access bootloader anymore - dhd doesnt boot.
so yeah, i got to send it in

[Q] CM installer bricked my nexus

As the title says, I wanted to try CM installer, and I was on everything stock, not rooted. I downloaded PC, and android programs, followed the instructions, however at one point CM installer on my PC said it cannot communicate with my phone, and it was when it was trying to flash recovery. It said I should try different cable, or USB port, but no luck with either, and now it says my phone is not supported.
I tried to enter recovery, but I only get CM guy and it's stuck, even when I turn off the phone, it turns itself on automatically, and to fully turn it off I need to enter fastboot mode, and then turn off. I tried flashing full stock image (I know how to do that, and I have previous experience on this phone), but my fastboot crashes (Fastboot.exe Has stoped Working), tried to download fastboot again, but nothing helped. I also tried to flash recovery only, and I get the same thing... Also tried to do that with custom recovery, but nothing....
Is there something I can do, or do I need a new phone?
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?

Looks more like issues with your pc communicating with your device, which might have causes other side effects due to that. But I have not tried CM Installer yet.
You should see about getting fastboot working correctly first and getting the right adb/fastboot driver (such as latest Universal Naked Driver, link in my sig). You should also use the latest adb/fastboot .exe from Google, download their latest ADT package. If it still crash, use it on a different machine, if you're on Windows 8 try Windows 7 or Ubuntu.
Also make sure the factory image isn't corrupt, I always have issues downloading it from Google.
Also, I had like 70% battery when I started, so I am afraid to keep trying, cause if I go out of juice, it's game over, right?
Click to expand...
Click to collapse
If the battery goes to 0%, just charge it, do you think everyone throw away their N4 when the battery goes to 0? There is the red light problem, but its an easy fix.

Thanks for answering, I fixed it with a strange method (to me). On CM forum j_cor told me this:
"Your device appears to be stuck in sideload. So the good news is no, you are not bricked. Here is what I would try to do:
1. Boot the device - wait for the "stuck" CM guy to display
2. Plug phone to PC and open a command prompt to the directory to C:\Users\enter_your_name\cminstaller\bundle\win32
3. from the prompt "C:\Users\enter_your_name\cminstaller\bundle\win32>" type "adb.exe sideload ClockwordMod.cer" (no quotes) and hit enter
4. This will try and sideload this .cer file and will fail - but it should kick you out to the main recovery screen. Select the Reboot option from Recovery
5. Device should boot back up. It will most likely still be the stock ROM. My guess would be that something disrupted the sideload process when installing the system.zip with CM."
However, this did not fix my problem, but it got my phone to communicate with fastboot. So I was able to flash custom recovery, and do a factory reset, which brought me to the stock ROM, I flashed CM the old-fashioned way then.....
And my PHONE IS UP AND WORKING AGAIN!!!
The main problem in communication was that phone blocked every time I booted into fastboot, and plugged USB cable in.... It immediately became unresponsive to any commands, after I did this, phone wasn't getting stuck in fastboot, so that solved my issue.

I know it's the wrong forum, but....please take a look

I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end

Try fastbooting a recovery like TWRP thati s updated then flash a rom.

disclaimer: I might be no help at all!
You have fastboot -- go learn all the fastboot commands... you need to know the tools and figure a solution!
erase... hmm? why? What about factory reset? I see you are not using LOS 13 but stock image... need root? Basically, I would factory reset/wipe sdcard, then install recovery (TWRP) [okay, so first you would need to use fastboot to install custom recovery)...THEN, push (fastboot an image.zip (LOS or stock) to sdcards, install, and reboot!
Good to have WUG... another tool in the chest (I have never seen it or used it)
Ok, so one clue is that if your computer cannot see it, that says to me RED FLAG... ADB drivers? but you say fastboot works, hmm... I think this is the problem... Koush's universal ADB drivers? official Google drivers? Could these help!
Erasing screen? Hmm...
I would say, for the hell of it, try flashing different ROMs, Recoveries, and Drivers.... you are basically trying to...
Factory Reset/wipe SDcard [system, cache, ... everything], Flash custom recovery (optional), then, some how (fastboot or mycomputer) get an image on to /sdcard, then, install, then, reboot!
Good luck!
luckyheel said:
I really need the help of one or more of this forums intelligent minds. As I'm sure you'll see, I've posted this in the QA forum, but have had no hits so far....thus the reason for posting here.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance! I'm at my wits' end
Click to expand...
Click to collapse

Why not try this
I have not had this problem with my Nexus 10 but I did once with my Nexus 7 and it may help you.
Instead of trying to flash TWRP and run it (which is not working for you) why not boot into a temporary copy of TWRP and then work from that? To flash TWRP normally (persuming you had renamed the img file to TWRP which makes it easier) you would enter 'fastboot flash recovery twrp.img'. Instead of doing that type 'fastboot boot twrp.img'. This boots into TRWP and from there you will be able run all the options and from there flash TWRP and other images as normal.
If you are having problems with drivers have you used 'USBDeview' ? Run this as Administrator and delete all references to any phone or tablet USB driver and particularly look for devices with Vendor ID '18d1' or '04e8'. Just select them, right click on them and select 'Uninstall Selected Devices'. When they are all cleared reboot your computer and plug your tablet in and it should install the correct driver.
Another option I used successfully with a Nexus 7 in a boot loop was to connect it while running Linux. I don't have a Linux on a computer so I installed one in 'Oracle VM VirtualBox' I don't know Linux but after Googling for help I installed Peppermint Linux and then ADB for Linux. I downloaded the 'TWP' image into a folder in Linux and any other images I wanted. Connect your tablet to the USB port and then on the top menu in VirtualBox select 'Devices' then 'USB' and tick the option which shows your tablet. I then went into what we call a command prompt in Windows but which they call 'Terminal'. Then type 'ADB devices' and if you see it on the list use ADB instead of fastboot. As I mentioned my Nexus 7 was in a boot loop so I typed 'ADB wait-for-device' and as soon as it looped to a point where ADB could see it then the looping stopped and I could flash the images and recover the tablet.
All the best. I hope you are successful.

As long as you can get into bootloader mode, your good.
NOW
If you can't get into boot loader mode? as far as I know...
You're ****ed.
Unless you want to set up usb boot (might not work on Exynos, idk, this is magic to me) and solder the connectors and flash it like they do in factories. That's next level **** too, and considering an N10 is 100$ on amazon you're better off just grabbing a new one.