Database Info

Help I got a Brick

Hi there, can someone help me!!!
So here's my situation:
Not Rooted German G1 with 1.5
first time it booted in 1.5 i checked the box for always using dxtop as standard homescreen. well this was quite stupid, as the screens loaded up but without any icons or anything, couldn't even get into the settings screen...
i just figured i'd reinstall the firmware -> BRICK
now G1 only boots into the recovery screen and when i try to reinstall 1.5 it gives me this message:
E:Can't symlink /system/bin/bugreport
E:Failure at line 626: symlink dumpstate SYSTEM:bin/bugreport
Installation aborted.
any ideas
problem is, i think i could save my baby by installing a root firmware, with goldcard, but i don't have any way to read the CID from a sdcard... so I'm stuck here.
I'm thankfull for any help!!!

What you should have done is a wipe. In fact I would try that even now. From the recovery screen do Alt+W. See if it boots properly. If it still boots to recovery, you can try the update again but I doubt it will work as it is probably looking for the previous version of the firmware.

First thing,
you haven't modded your G1, so you MUST have warranty. Send it to t-mobile.
If you use the goldcard, you loose your warranty.
So think about it first.
A PCI-Cardreader and Ubuntu to read out the CID should do it. But it isn't easy! Or borrow a Windows Mobile-Device from a friend.
This is the easiest solution.
If you have no friend with a WM-Device (Or no friends... ) you could ask someone here for borrowing you a goldcard.
I have one, but actually I need the Stick for my PSP..
Hope that helps.

you bought the g1 on rc9 or u updated it manually to rc9?
its not a guarantee..
but try to reinstall the rc9..so change your update.zip files again and watch if it goes?!

Thanks everyone, now i tried allmost every signed firmware version out there, but nothing worked. seams like the updater won't let me install a smaler version then the one installed... Well I go to the elecronics store today and see if i can get them to let me read out my SD's CID on one of their G1s. should tae care of the problem...

just wondering, you said that you couldn't get icons to load, i can potentially fix that, and it says the install aborted which means it didn't flash. is the phone loading to the home screen?

Did you ever just try uninstalling dxtop through adb?

[Q] Using official HTC unlocker for Sensation, Help installing Cyanogen

I recently "unlocked" my HTC Sensation 4g through HTC's official method. However, after successfully unlocking it, my phone is still set on S-On. Because of this, I am not recognized as a superuser, and so I cant boot into Clockwork Mod Recovery. Can anyone who knows more than me about this please give me a hand? This is my first time attempting any of this.

to make sure i understand this correctly- your phone now says "unlocked" at the top,but is still s-on?
what have you done to root?
once you have a truly unlocked bootloader,you can install a recovery thru that bootloader,and then flash superuser in that recovery.
having superuser permissions within a rom and being able to boot to a recovery shouldnt have anything to do with the bootloader.
if you are unable to install clockwork,or some other custom bootloader thru htcs "unlocked" bootloader,then they have lied to us... its not truly unlocked. that or something happened during the unlock process,possibly.
sorry im not of more help,its been awhile since i looked at the developer website. are there support forums there?
if everything is functioning correctly and you cant load whatever you want thru hboot,this unlock program is a joke. you could have gotten s-off with revolutionary or an xtc clip and not alerted them to the fact that you were messing with software and potentially "voided all or parts" of your warranty.
please keep us updated on this- im very interested to know how it turns out.

Thats exactly what it says. The method I used is on the front page of the htc dev site.
(the forum wont let me post outside urls yet)
The top of my H-boot screen says
"*** UNLOCKED ***
PYRAMID PUT SHIP S-ON RL
HBOOT-1.80.0000
eMMC-BOOT"
So this is a problem. I think...
I just figured the official method through HTC would be the easiest and safest

Oh and when I try and flash Clockwork Mod Recovery through ROM manager this is the message I get
"You must root your phone for ROM Manager to function. Superusuer was not found at /system/bin/su or /system/xbin/su. Use Google Search on your computer to find instructions to root your phone."
or
"An error occurred while attempting to run privileged commands."

So what have you done to root besides unlocking the bootloader? Just tried to install rom manager and clockwork?
Unless you have done something else,you are not rooted,you are just unlocked. Search the sensation forum for a PxxxIMG file that is clockwork recovery. When named that,and placed on root of your SD,hopefully your hboot will find and flash it.
Once you have done that,delete the PxxxIMG From your SD card,and place the superuser.zip file on it. Enter recovery thru hboot,and flash superuser.zip.it will install the root files.
After that you should be rooted.
Later I can try and find some links if you can't find them. PxxxIMG will be specific to the pyramid,I'm not sure what it is. For example,this type of file for the thunderbolt is PG05IMG.
Hope that helps.
edit:
here are some links for you:
download clockwork from here or multiupload (found the download in this thread)
download from one of those 2 places. rename the download "PG58IMG" and place on the root of your sd card. boot to hboot(power+vol down). when asked to update chose yes.
download superuser from here (this is the one i always use. found it here)
after deleting or renaming PG58IMG from your sd card,put the superuser.zip,boot to hboot,select recovery,then flash the superuser.zip.
hope it helps
Sent from my ADR6400L using XDA Premium App

Well I tried what you recommended and it did not work. But then I tried revolutionary and I managed to get s-off. However HBOOT doesnt recognize the P58IMG file. It just keeps saying P58IMG.*** NO IMAGE. (*** being different file types).
Im not sure if I need to try the recovery now that Im s-off but I cant flash the superuser file either.

gah! i wish you hadnt run revolutionary yet,as now we wont really know if your "unlocked" s-on hboot would have allowed the flash like a truly s-off one will.
one thing i know for certain,is that the troubles youre having werent because you were s-on. being able to place the superuser app,aND matching binary within the OS is not dependent on the hboot being s-off. s-off is handy,as it allows another method of flashing partitions like the radio and recovery. in the old days,before all the exploits were patched,alot of devices were rooted and a custom recovery installed from within the OS without ever bothering with the bootloader. the eris is a good example- prolly 95% of the eris community is still s-on and they change roms and such all the time.
-so i guess you downloaded the PG58IMG from multiupload? when i tried the first link,there was no valid attachement.
-you did name PG58IMG,correct? if you did name the file "P58IMG" maybe thats the prollem?
-make sure your SD card is formatted FAT32( not just plain FAT) and make sure you put the file on the root(not inside another folder)
*assuming you named the file correctly,have a FAT32 sd card,and placed the file onto the root of the SD,what happend when you went to hboot?
heres what should happen: the green writing flashes,hboot finds a PG58IMG file,then youll see a blue status bar on the far left as the phone unpacks it,then gold as it checks it. since the recovery file is small youll see that very fast. then you should get the "vol up to update" prompt.
if you have named the file correctly,FAT32 card,etc. maybe you just got a bad download. try downloading it again.
i downloaded and checked it- it contains a recovery image and an android info file,so it should be good to go. if you want to verify the integrity,the md5 i got is: 940fa14af3dcd055132adf292f668ad3
last and not least,if you ran revoltuinary it should have installed clockwork for you. if you dont want to keep messing with PG58IMG files,just run revoltionary again. it should detect your s-off,then ask if you want to install clockwork.
im sure youre getting a lil fustrated,but the method for rooting new phones is what im reccomending you to do:
1)unlock bootloader(revolutionary or htc unlock)
2)install recovery thru bootloader
3)install superuser files from recovery
it does work,i promise... ive done it many times on my thunderbolt.

Awesome, everything worked great. I had a few hitches but I figured them out. Thank you so much for all the help, I really appreciate it.

Until just now... I installed cm7 and now when i boot up my phone all I see is about 6 seconds of the cm7 start up animation (the one with the blue android guy on a skateboard). Then the phone starts up that same animation again. Its been doing this for about an hour now.

barnodian said:
Awesome, everything worked great. I had a few hitches but I figured them out. Thank you so much for all the help, I really appreciate it.
Click to expand...
Click to collapse
please list the hitches and what you did to make it work,so others will benefit that find this in future searches.
barnodian said:
Until just now... I installed cm7 and now when i boot up my phone all I see is about 6 seconds of the cm7 start up animation (the one with the blue android guy on a skateboard). Then the phone starts up that same animation again. Its been doing this for about an hour now.
Click to expand...
Click to collapse
sounds like you didnt do a full wipe. pull the pattery,go back to recovery thru hboot,and wipe data/factory reset,wipe cache,wipe dalvik chache,and format /system. i dont usually format /system,but when youre stuck in a bootloop it cant hurt

well it was my own dumb fault... like extracting the .zip files instead of leaving them compressed.
And yeah now i totally have cm7 running! thanks for all the help man. I really appreciate it

No prollem.glad you got it figured out.
Sent from my ADR6325 using XDA App

Well they were my own fault. Like forgetting to leave the .zip files compressed. Otherwise everything is working great and I'm running cyanogen perfectly. Thanks for all the help
Oh thats why I didnt see the response I thought i sent... it was on the second page. my bad. well now you get thanked twice.

[Q] Phone hangs during use - sometimes fails to mount /system or /data

This has been ongoing for a few weeks now. Desire S is currently running Endymion 2.2, but the same thing happened on Cyanogen and Stock roms. Phone will work fine for up to a day, then will completely freeze up during use (has happened in Browser, while entering text, and once just on the lockscreen). During the hang the touchscreen won't respond, connecting USB has no effect (no LED and ADB Devices lists nothing), the 4 buttons give haptic feedback for about 5 seconds after the hang, then nothing. Holding volume+power has no effect, but usually after about 10-20 tries or 15 minutes of doing nothing the phone will return to HTC boot screen, and sit there until I power it off and then remove the battery.
When using clockworkmod, half the time either /system or /data is not mountable (this only happoccasionally get "error mounting /cache/recovery/log"). When this is the case, formatting/factoryreset sometimes gives the "can't mount /data" error, and sometimes works.
Since switching to 4EXT the partitions are always mountable from recovery, but rebooting causes the phone to hang immediately after booting.
Current setup (which at the moment is hanging at the lockscreen)
HBOOT-6.98.2000 (PG88100000)
4EXT Recovery v2.2.7 RC5 (/system /cache and /data all ext4)
Endymion 2.2
tldr: is it possible for /system or /data to break during normal use and sometimes be unmountable? If yes, then can this be prevented? If no, any other suggestions as to what could be going on?

Reads the posts in the eMMC section at the bottom of the index thread, see end if my Sig for link
Swyped from my Desire S using XDA Premium

If you want my opinion, be drastic about your approach to this. Start from the ground up, that way you will be able to more or less narrow down the problem you are experiencing.
1. Change your HBOOT to 0.98.2000 (As you are using the revolutionary HBOOT, you will need to change this using a different method).
1a. Download HBOOT 0.98.2000 from this thread.
1b. Taken from this thread, use this method to change your HBOOT using adb. If you don't know how to use adb .. >_<.
Copy the hboot.img to your SDCARD.
In adb type:
adb devices
adb shell
su (doesn't matter if it says /system/sbin/su not found)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18​
2. Format all your partitions again using your recovery.
3. Re-install a FRESH ROM, try to avoid backups.​
Don't care if anyone thinks differently, this is just what I would do if I was having this problem.

Totally agree with the above post.
But I would suggest even more drastic approach. Restore to complete Stock and S-ON. There are Guides here how to do this. Then do a testing for a couple of days, maybe a week. At the moment when (if) this problem appears again run to your provider and insist a replacement.
IMO this way you will spare yourself a lot of nerves and troubles in future.

ben_pyett said:
Reads the posts in the eMMC section at the bottom of the index thread
Click to expand...
Click to collapse
sorry, didn't mention this in op - checked for eMMC issues when it first started happening and everything seemed okay, so I'm confident it's not a hardware fault. Not sure if there is a different problem that can result in similar, but sporadic, results.
Going to S-ON and try stock rom again and see how it goes.
Thanks guys

I checked mine and was also confident i had an ok emmc but alas, if you have the bad chip, you have a bad chip.
It may manifest it's self in different ways but eventually it's more than likely to fail. You would be wise to proceed with that caveat.
Sent from my HTC Desire

psimyn, how did it go? Also is it a telstra branded handset?

Sorry for the slow reply, finally got a response from the seller.
Handset was unbranded, bought from HK. The seller requested $40 for shipping both ways, which was apparently going to be refunded if the phone was covered by warranty.
Instead, I got an email yesterday claiming that the phone suffered a "software corruption" and that I had to pay an additional $45 for Labour and Administration. When I asked why the response was "I am just explaining to you that the labour cost and all administration are $45".
For now I just want the damn thing back, so it's been paid and they will hopefully send it today.

Inspire 4G: Rooted -> ROM'd (ARHD) -> ENG S-OFF'd -> Weird behavior now

First of all, I'm a TOTAL noob, I've been reading a lot and I've got further than I thought I would and I have learned A LOT.
Now, for my problem I've searched and read several threads but I can't find a solution that is suitable.
I'll describe what I've done so far and the results, I'm trying to be as explicit and specific as possible, so please read the whole thing:
1 - Got an Inspire 4G with Gingerbread, I got it unlocked (i.e. works with other carriers, like TELCEL) in Mexico, which is where I live.
2 - I checked to see if it was rooted or S-OFF'd and it wasn't.
3 - Used the Ace Hack Kit to root it (Successful)
4 - Installed Android Revolution 7.0.3 using Clockwork (Successful)
5 - In the ROM thread it says it's recommended to flash the radio to 12.65.60.29_26.14.04.28_M, which I tried to do and that's where my problems started.
I downloaded a ZIP file that contains the following files:
- adb.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll
- fastboot.exe
- guide.txt
- radio.img
I followed the instructions but I got an error, the error was very early in the process so the phone had no modifications done to it. I searched the forums and I found one that said that ENG S-OFF had to be done, so I found the CoreDroid thread and it says to use "easy S-OFF.zip" to do just that.
I ran the application and when I clicked the button to do it, my phone shut down.
I removed the battery, the sd card and every other thing I found on the forums to no avail. I thought I had bricked it.
Then, after 7 or 8 minutes it would turn itself on, show the white HTC screen for 3 minutes (while vibrating non-stop) and then it would boot into ARHD.
Everything seemed to work, but the phone wasn't detecting the SD card, so I formatted it to FAT32 (slow format) and the phone detects the card again, BUT every time I turn it off, or try to reboot it, it will do that (nothing for 7 minutes, then HTC white screen with vibration, then boot into ARHD).
I found in other threads that it might be a corrupted hboot, and that I needed to flash it with an RUU. I tried that, didn't work. The stock RUUs that I downloaded are the following:
RUU_ACE_CINGULAR_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed.exe
RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe
The would run and connect to the phone, but I would get error 155 I believe, that said to "get the correct ROM for the phone".
Of course, I can't get into recovery mode or into clockwork, because pressing the volume rocker + power does nothing, just does the long-ass-vibrating-weird-boot as described above.
Continuing my search in the forums, I found that I could RUU to return the phone to stock (and re-do the whole thing later) using the ace hack kit, which is where I'm at now.
I plugged the phone to the PC (charge mode), ran the AHK, selected the option to back to stock, selected ATT GINGERBREAD, and the RUU started to download.
After the RUU was downloaded, AHK asked to confirm if I wanted to FLASH RUU: YES, and SET S-ON: YES, so I did.
The first thing it did was to reboot the phone, but of course, it wouldn't boot normally, so it stayed dead for 7 minutes, then turned itself on, vibrated for a while, and then showed a black HTC screen.
The AHK said:
Erasing the cache: OKAY
Be patient sending update...
Sending ZIP (15824 KB): OKAY
Writing zip...
And that's where it got stuck, and still is after more than 1 hour.
I don't know if I should unplug it or to do what, and the phone is getting warm because the screen has been on all along (I've put a fan next to it)
Can you help me?
Thanks and sorry for the long post.

Well, after a very long time with the phone just sitting there showing the HTC black screen doing nothing, the process continued showing the following, while a green bar appeared on the screen:
INFOzip info parsing...
INFOchecking model ID...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,23
INFO[RUU]UZ,recovery,47
INFO[RUU]UZ,recovery,70
INFO[RUU]UZ,recovery,95
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,20
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,70
INFO[RUU]UZ,radio,79
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,99
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,100
OKAY [7047.254s]
finished. total time: 7050.016s
rebooting...
finished. total time: 0.203s
At this point the phone did its usual long-weird-boot, and after showing the HTC white screen for a while it rebooted again (another long boot), in the meantime this is showing in the CMD window:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Press any key to continue . . .
error: device not found
And after its latest long boot the phone screen is showing ClockworkMod, and lower down it says:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I'm unsure what option to select:
*reboot system now
*apply update from sdcard
*wipe data/factory reset
*wipe cache partition
*install zip from sdcard
*backup and restore
*mounts and storage
*advanced
*poweroff
The CMD window still says "device not found".

Another piece of information, I selected Reboot system it goes into it's long-weird-boot and then booted into ARHD, so nothing was wiped apparently? Just the radio?
I need to get this thing back to full stock so I can re-root and re-ROM, but I don't seem to be getting anywhere :\

ivan13 said:
Another piece of information, I selected Reboot system it goes into it's long-weird-boot and then booted into ARHD, so nothing was wiped apparently? Just the radio?
I need to get this thing back to full stock so I can re-root and re-ROM, but I don't seem to be getting anywhere :\
Click to expand...
Click to collapse
By doing all those different steps from different places you botched your bootloader. Hit up the Ace hack kit thread and join the IRC chat and they maybe able to get you fixed up. The ace HAck kit does everything for you.

zelendel said:
By doing all those different steps from different places you botched your bootloader. Hit up the Ace hack kit thread and join the IRC chat and they maybe able to get you fixed up. The ace HAck kit does everything for you.
Click to expand...
Click to collapse
Thank you.
Do I open a new thread over there? Should I reference this thread or should I copy and paste it there? Or should this thread be moved?

ivan13 said:
Thank you.
Do I open a new thread over there? Should I reference this thread or should I copy and paste it there? Or should this thread be moved?
Click to expand...
Click to collapse
The IRC is an internet related chat room. Go to the AHK thread and you will find a link to the room.

dont root
if you are a noob, which u are, then i wouldnt root

adam11209 said:
if you are a noob, which u are, then i wouldnt root
Click to expand...
Click to collapse
if you are a troll, which you are, then i wouldnt post

adam11209 said:
if you are a noob, which u are, then i wouldnt root
Click to expand...
Click to collapse
Well, the rooting itself wasn't the problem, flashing the radios was (apparently).
Fortunately, the people here and the guys at the IRC channel (namely attn1) were kind enough to help me solve it, by pushing a copy of hboot into the phone, they are/were great.
And yes, I am a noob, and as a noob I'll break stuff before I can gather any usable knowledge, to know what NOT to do. Some people call it "learning".

ivan13 said:
Well, the rooting itself wasn't the problem, flashing the radios was (apparently).
Fortunately, the people here and the guys at the IRC channel (namely attn1) were kind enough to help me solve it, by pushing a copy of hboot into the phone, they are/were great.
And yes, I am a noob, and as a noob I'll break stuff before I can gather any usable knowledge, to know what NOT to do. Some people call it "learning".
Click to expand...
Click to collapse
Ivan, do as Zel told you and hit the IRC channel. You have messed your bootloader and need to be fixed in order to have a working phone again. You should have flashed the radio in the PD98IMG.zip fashion, that is what The Effen manual states.
The IRC channel is:
webchat.freenode.net
channel (#aahkSupport)

glevitan said:
Ivan, do as Zel told you and hit the IRC channel. You have messed your bootloader and need to be fixed in order to have a working phone again. You should have flashed the radio in the PD98IMG.zip fashion, that is what The Effen manual states.
The IRC channel is:
webchat.freenode.net
channel (#aahkSupport)
Click to expand...
Click to collapse
Thanks glevitan, already did several hours ago, attn1 helped me solve my issue in part and I took care of a couple other (uncomplicated issues) afterwards. I'm happy now

ivan13 said:
Thanks glevitan, already did several hours ago, attn1 helped me solve my issue in part and I took care of a couple other (uncomplicated issues) afterwards. I'm happy now
Click to expand...
Click to collapse
Yeah, aatn1 is the man. Glad you are back...

Glad you got it resolved. Thread closed

[Q] Need Help, HTC One XL Australia, recovery wont load SD Card

HTC One XL stuck in boot loop, recovery will no load System, or SD Card, so i cannot retrieve my restores. have fastboot usb capabilities still, Does anyone know how to resolve this problem?

More information required. Please state your bootloader details, current ROM and kernel, current recovery, and a detailed description of the effects that lead to this situation.
Sent from my Evita

HBOOT 2.15.0000 --- S-Off & Unlocked
Radio 1.31a.32.45.16_2
ROM Viper xl
Recovery TWRP 2.5
I flashed oxp_elitekernel_130413, which i now realize was wrong, which led to the boot loop, So i tried to flash back to previous Kernal but it cam up with error device not found.
So i tried to access recovery and it just kept bootlooping. So i then flashed recovery again, now i have recovery but sd and system won't load.

You need to update your recovery, TWRP 2.5 is full of bugs. Get 2.6 or above from here and flash it using fastboot. Out of interest, how exactly did you try to flash back to your original kernel? You said you got a "device not found" message which doesn't seem right.
I'm not sure where you found that oxp_elitekernel but it certainly wasn't from within our device forum. You need to make sure you don't stray into other forums, nothing outside of our forum is compatible with our device, you're actually very lucky you didn't brick your phone. Our device forum main page is here:
http://forum.xda-developers.com/one-x-att
Bookmark that page and make sure you stay within it.
Sent from my Evita

I think i have bricked it....lol. Nothing is loading.

I flashed in fastboot cmd prompt. Because the sdcard isn't loading anymore it can't write or read the phone. so i don't care if i have to format the whole dam thing, i just dont know how to do it, without risking what little access i have left.

All Good, i worked it out in the end
Thanks to all who gave me feedback but i ended up figuring it out. If anyone has that problem in the future, all you have to do is format system and sdcard, (yeah i know you loose everything, but thats better than losing the whole phone.) then mount sdcard in TWRP, and place on the zip files for your roms, un-mount the partitions, then install the zips. If your S-ON, i guess you would flash boot image (unless S-ON stops you from wiping those partitions, in which case your screwed.) . But if you're S-OFF Just install and your back.

S-on doesn't stop you from wiping any partitions. Good to see you worked it out though. You might benefit from reading the Evita FAQ and How-To Guide For Beginners threads in my signature.
Sent from my Evita

I am not really a beginner, started hacking my phones 3.5 years ago. Been in love with it ever since, I was at the end of three nights with no sleep, and I wasn't thinking very clearly, and so I failed to notice that I had strayed into just the one x+ forum, and flashed the wrong kernal, very nearly bricking it in the process. Rookie mistake, one I'm not likely to repeat. Scared the crap outa me...lol.
Thanks for your help once again bud.
Sent from my HTC One XL using xda app-developers app

All good, no offence intended.
Sent from my Evita

Oh I know, was explaining more out of my own embarrassment then anything else..lol
Sent from my HTC One XL using xda app-developers app