Database Develop

So if i intentionally brick my phone...

...the insurance company wont ever be able to figure out that i rooted it and come for money?
I downgraded to the original bootloader but cant get rc29 back on, i just get the gray screen to flash for a split second (it says 'no file...') i still have cyanogen 1.3.1 and i flashed ion to have something to work with but i read that i can pull the battery during a flash and just brick it. thanks

DMaverick50 said:
...the insurance company wont ever be able to figure out that i rooted it and come for money?
I downgraded to the original bootloader but cant get rc29 back on, i just get the gray screen to flash for a split second (it says 'no file...') i still have cyanogen 1.3.1 and i flashed ion to have something to work with but i read that i can pull the battery during a flash and just brick it. thanks
Click to expand...
Click to collapse
Are you sure that your sdcard is formatted to fat32? The no file found usually indicates that it isn't.

h.nocturna said:
Are you sure that your sdcard is formatted to fat32? The no file found usually indicates that it isn't.
Click to expand...
Click to collapse
good call thanks, i may have put it on the new card that came with the new phone, which i suppose isnt set to fat32 by default. But the boot flashed ok, would it do that if it wasnt fat32?

DMaverick50 said:
good call thanks, i may have put it on the new card that came with the new phone, which i suppose isnt set to fat32 by default. But the boot flashed ok, would it do that if it wasnt fat32?
Click to expand...
Click to collapse
No problem, seen it before and just passing the info along. I don't think it should affect the boot.img as that is flashed from terminal, and I don't think terminal is as discriminating as the bootloader.

h.nocturna said:
No problem, seen it before and just passing the info along. I don't think it should affect the boot.img as that is flashed from terminal, and I don't think terminal is as discriminating as the bootloader.
Click to expand...
Click to collapse
that worked its updating, however my trackball doesnt work and i think im supposed to use it after the install. wonder if theres a workaround...
edit: i wound up pulling the battery and it booted up just fine so i think im set to send it back in, thanks again for the help it wouldve cost me up to $300 to the insurance if anything went wrong on my end...the build number says "kila-..." i cant remember if thats original

Nexus one only going to the "Android system recovery <2e>" screen

When booting the Nexus One I get an Android with an explanation point, then I am able to toggle the volume key and power to get into "Android system recovery <2e>" screen which gives me the options
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition
when it's in this screen I can NOT access it through fastboot or adb.
It looks like it is only allowing me to push "officially" signed update.zip files to it and nothing else.
I cannot get it in to hboot or anything else it ONLY boots into "Android system recovery <2e>"
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!

Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?

irishrally said:
Did you try holding trackball and power button when the phone is turned off to bring you directly to fastboot?
Click to expand...
Click to collapse
Yes, with no luck, it just goes straight to the Android and explanation point

Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.

hyperandy said:
Maybe someone has an official update.zip boot image they can send me to or some other idea it would be much appreciated since I cannot use the phone at all.
Thank you in advanced, Please help!!!
Click to expand...
Click to collapse
Heres a thread that contains the official 2.1 update1 zip.
http://forum.xda-developers.com/showthread.php?t=627823
Maybe the volume key or trackball is stuck/damaged?

irishrally said:
Are you rooted? Unlocked bootloader? What did you do to get you into this situation?
Not to worry you, but usually not being able to boot into fastboot is not a good thing.
Click to expand...
Click to collapse
ya at this point I was kinda figuring that but I am hopeful ...I unlocked the boot loader and everything was going great until I partitioned the sd in the recovery image, then I started getting a weird MISC error and couldn't boot up at all, only in recovery but fastboot and everything still worked. Then I saw a post about applying the original image to the device via fastboot, preformed that and ever since then I have had a $500 brink that lights up

I don't think you can brick the N1 by just flashing a ROM, usually this only happens when changing the radio or spl.
I would try taking out your sd card, copy all your files you your computer, format your sd card, copy your files back to your sd card and see what that does for you. Maybe some issue arose when you partitioned your sd card, although you said fastboot still worked until you flashed the ROM. Worth a shot though.
If you can access fastboot then, I would flash Amon Ra's custom recovery image via fastboot and take it from there.

well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something

hyperandy said:
well I actually tried a completely different sdcard and then none at all. No luck. If it's not letting me into hboot do you think it may have gotten corrupted or something
Click to expand...
Click to collapse
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.

irishrally said:
Honetly, I don't know. Did you try copying the .zip in the link posted above to your sdcard and then applying that zip in recovery?
Hopefully someone that knows more than me will chime in and have some better ideas.
Click to expand...
Click to collapse
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?

hyperandy said:
maybe it's because I just woke up but I am not clear what you are asking, can you rephrase that? The link above my SD card?
Click to expand...
Click to collapse
Did you try copying the .zip file in the link below to your sd card and trying to flash it in recovery?
http://forum.xda-developers.com/showthread.php?t=627823

Thank you, ya I didn't see the link the first time. duh. Yep I tried that and I get a build.prop error (although this update says installing for a second and i see a progress bar, I have tried that same file from a few download locations to make sure it wasn't a bad download too):
file_getprop: Failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/update.zip
(status 7)
Installation aborted
Thank you for all your help!! but I am afraid this isn't looking to good.

I also tried creating that file just to see but since it wasn't officially signed it gave me an error about that

I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.

hyperandy said:
I think at this point it is looking for a specific signed update.zip file, where I find that, I have no idea.
It almost seems like I need the whole update.zip officially signed by google and/or HTC and then it would flash. I highly doubt they are going to hand that over. I am half temped to see if I could send it in to them to be reflashed even for a fee if it means I can get this thing working again, but I don't even know if they would offer that. It's only 2 months old and I think the file I need maybe out there but damned if I have been able to find it anywhere.
Click to expand...
Click to collapse
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.

irishrally said:
I wouldn't give up yet. I'm sure there is someone out there that can tell you you are completely hosed, or help you fix the problem.
If you can't fix it, I have heard it will cost $196 for a new motherboard if you send it in to HTC. They could just reflash your phone but I heard they handle a case like this by charging you for a motherboard swap. Second hand information though.
Click to expand...
Click to collapse
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.

hyperandy said:
I believe that, I work in the field service industry and I see stuff like that all the time. Although I would rather pay the 196 instead of 560+ again. I am almost 100% certain this could be re-flashed with the right file. but I have so far spent 2 full days trying different things, I think I will give it until tomorrow and then send it in (by then I should be good an sick of searching). Unfortunately, I am in love with my Nexus. it's been a while since I had a phone I really enjoyed as much. If I knew another great phone was coming out in a week I would probably say the heck with it and just buy the next one but this is still an awesome device.
Click to expand...
Click to collapse
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????

martin0285 said:
Have you tried every option in all the other "HELP BRICK" posts?? I don't really have time to search (and my nexus is working fine) but I know there has been plenty of threads like this before. Multiple options where tried, some successfully and some not. I would not give up unless it won't power on at all. Does ADB logcat work during a boot? Fastboot Devices? anything??????
Click to expand...
Click to collapse
No haven't tried those checking the Help Brick post I will see what I can find. No adb and not fastboot devices, just says waiting for device if I try anything.

Since you have unlocked the bootloader have you tried a complete reload?
fastboot: flash boot, flash recovery
recovery: wipe everything, reset, install latest CM.

Did you ever figure this out?

[Q] Stuck at Clockwork Recovery screen? HELP!??!

I am currently stuck at the clockwork recovery screen. BTW i did the one click root...didnt break stock bootloader. not sure if this makes a difference or not. i was told it didnt...? i cant get back to stock firmware and i cant load zx2.1 sense i keep getting errors on both and i really have no idea what the hell to do from here. error on zx2.1 is as E:cantchown/mod/system/xbin (no such file or directory)
E:failure at line 17: set_perm_recursive 0 2000 0755 -6755 system:xbin
installation aborted

If you have stock SPL those roms will not fit ito your system partition. They need danger spl or the recent mtd partiton hack.
You can also try a donut rom without sense, they usually fit stock spl system.
€: If you want to go back to stock rom, you need the correct dreamimg.nbh for your device on your sd card and flash it via bootloader. This will obviously break root.
Sent from my HTC Dream using XDA App

mblaster said:
If you have stock SPL those roms will not fit ito your system partition. They need danger spl or the recent mtd partiton hack.
You can also try a donut rom without sense, they usually fit stock spl system.
€: If you want to go back to stock rom, you need the correct dreamimg.nbh for your device on your sd card and flash it via bootloader. This will obviously break root.
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
How can i get it flashed via bootloader when i cannot load anything on it? i cant get past the clockwork recovery screen. ive downloaded the dreamimg and i just dont know wth to do

BenDiesel said:
How can i get it flashed via bootloader when i cannot load anything on it? i cant get past the clockwork recovery screen. ive downloaded the dreamimg and i just dont know wth to do
Click to expand...
Click to collapse
This is the guide I used to downgrade. Make sure you have the right image file for your phone, and make sure your battery is fully charged and the process is not interrupted.
http://forum.xda-developers.com/sho...&highlight=original+spl+downgrade#post5640154

oldnoob said:
This is the guide I used to downgrade. Make sure you have the right image file for your phone, and make sure your battery is fully charged and the process is not interrupted.
http://forum.xda-developers.com/sho...&highlight=original+spl+downgrade#post5640154
Click to expand...
Click to collapse
ive given up. my computer will not read my g1. its like its not there. and ive downloaded 5 dreamimg's and for some reason the g1 says theres no image file. i just boot to clockwork recovery and thats it...

BenDiesel said:
ive given up. my computer will not read my g1. its like its not there. and ive downloaded 5 dreamimg's and for some reason the g1 says theres no image file. i just boot to clockwork recovery and thats it...
Click to expand...
Click to collapse
The computer doesn't need to see the phone. Put the file on the root of the sd card, the name of the file has to be correct and is case sensitive, DREAIMG.nbh IIRC. Power down the phone, insert the sd card, press and hold the camera button while you power it on until you see the bootloader screen. The phone should see the file and take it from there.

oldnoob said:
The computer doesn't need to see the phone. Put the file on the root of the sd card, the name of the file has to be correct and is case sensitive, DREAIMG.nbh IIRC. Power down the phone, insert the sd card, press and hold the camera button while you power it on until you see the bootloader screen. The phone should see the file and take it from there.
Click to expand...
Click to collapse
It was already in all caps...exactly as you said it had to be. not sure what the iirc means but it still is doing the same. some people have said it could be corrupted but how the hell can it be corrupted after 5 different ones. i feel like throwing the damn thing in the furnace!

BenDiesel said:
It was already in all caps...exactly as you said it had to be. not sure what the iirc means but it still is doing the same. some people have said it could be corrupted but how the hell can it be corrupted after 5 different ones. i feel like throwing the damn thing in the furnace!
Click to expand...
Click to collapse
Sorry, IIRC = If I Remember Correctly.
The file name is upper case, the .nbh is lower case. To check the validity of the file you can search for and download an MD5 sum checker, but after 5 attempts I doubt that would be it. The only things I can think of is either a problem with the card, or something with the phone. Try reformatting the card making sure it's a FAT32 full format, not a quick format. Hopefully one of the Android gods around here will see this have some better ideas.

oldnoob said:
Sorry, IIRC = If I Remember Correctly.
The file name is upper case, the .nbh is lower case. To check the validity of the file you can search for and download an MD5 sum checker, but after 5 attempts I doubt that would be it. The only things I can think of is either a problem with the card, or something with the phone. Try reformatting the card making sure it's a FAT32 full format, not a quick format. Hopefully one of the Android gods around here will see this have some better ideas.
Click to expand...
Click to collapse
ya its jus like this DREAIMG.nbh man i did the one click root didnt break bootloader....tried to boot load the regular rom and nothing man. im done with it. its tottally effed in my opinion....ive tried everything i can think of...

You really have to make sure you got the right DREAMIMG.nbh. If you have e.g. a T-Mobile G1 get the newest for T-Mobile. Be sure to have the newest, as it is possible that older versions are not flashable either. There are lots of those images around, and if you try them at random they are quite sure not to work.
Also there might be problems if the SD-Card is not formated properly. If you have an external reader, take it out and format it on your pc. Then put the (correct) image on it.
Perhaps if you tell us the brand of your mobile, we can try to guide you to the right image.

mblaster said:
You really have to make sure you got the right DREAMIMG.nbh. If you have e.g. a T-Mobile G1 get the newest for T-Mobile. Be sure to have the newest, as it is possible that older versions are not flashable either. There are lots of those images around, and if you try them at random they are quite sure not to work.
Also there might be problems if the SD-Card is not formated properly. If you have an external reader, take it out and format it on your pc. Then put the (correct) image on it.
Perhaps if you tell us the brand of your mobile, we can try to guide you to the right image.
Click to expand...
Click to collapse
no longer a newb....got this f'er working again and boy flashed a rom! back in the game!

[Q] I have totally messed up my Nook Color

Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.

MentalDragon said:
Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.
Click to expand...
Click to collapse
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.

BarryR1 said:
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.
Click to expand...
Click to collapse
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838

khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Is this going to help me. My original firmware was 1.0.1.

Just grab the CWR 1.1 Recovery image from the development forum. Burn that onto an SD Card and reboot. Wipe data boot system cache and flash. done.

Find rootpack in dev section, write that to sd card, add the flashable restore to stock zip from samuelhalffs restore to stock thread in the dev section to your sdcard, boot to sdcard with the rootpack on it, flash the restore to stock zip after formatting system and data. Wala, fixed! All info can be found in my dummies guide to my nook won't boot a few threads down.

Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.

MentalDragon said:
Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.
Click to expand...
Click to collapse
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?

khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Oops. My bad. Sorry for the misinformation.

MentalDragon said:
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=949699
Try this Thread, "Dummies Guide to Fixing 'My Nook Won't Boot'""
This should work and get you back to stock so you can start all over.

Soft Bricked Boost 510 / Won't go past second HTC boot screen

Minding my own business one day when a Google services app on the phone stopped working and kept popping up, so I rebooted to help fix it. The phone now hangs at the HTC boot screen after the boost logo had already come up. Completely stock, never unlocked or rooted, and I have no idea what went wrong. Unfortunately, I can't do a factory reset from HBOOT because there's important documents on the phone's internal storage. What can I do to fix this? Any help would be appreciated, thanks in advance!

Jay_P11 said:
Minding my own business one day when a Google services app on the phone stopped working and kept popping up, so I rebooted to help fix it. The phone now hangs at the HTC boot screen after the boost logo had already come up. Completely stock, never unlocked or rooted, and I have no idea what went wrong. Unfortunately, I can't do a factory reset from HBOOT because there's important documents on the phone's internal storage. What can I do to fix this? Any help would be appreciated, thanks in advance!
Click to expand...
Click to collapse
There's not much you can do. You're gonna have to factory reset because even if you unlock the boot loader at this point the phone is going to reset anyway.. You should always keep stuff that's important on the sd card not internal.
There may be a way using adb and a computer using adb pull but I think that's just for the sd card I don't know if you can navigate to internal using a pc because I don't have that type of issue.
Try hooking it up to the pc and see if you can get into the internal storage.

Jay_P11 said:
Minding my own business one day when a Google services app on the phone stopped working and kept popping up, so I rebooted to help fix it. The phone now hangs at the HTC boot screen after the boost logo had already come up. Completely stock, never unlocked or rooted, and I have no idea what went wrong. Unfortunately, I can't do a factory reset from HBOOT because there's important documents on the phone's internal storage. What can I do to fix this? Any help would be appreciated, thanks in advance!
Click to expand...
Click to collapse
Try to boot into safe mode. As soon as you see the first HTC screen on boot up, hold the Down volume button and keep holding it until the phone boots or at least for about 15 seconds to see if it will work.

blaqueknight said:
Try to boot into safe mode. As soon as you see the first HTC screen on boot up, hold the Down volume button and keep holding it until the phone boots or at least for about 15 seconds to see if it will work.
Click to expand...
Click to collapse
I totally forgot about safe mode bro lol

ADB won't work because I never enabled USB debugging, unless ADB pull doesn't require that. Computer doesn't see anything when it hangs. Safe mode was a no-go either :/ I don't have an SD card to put stuff on right now, although I really should've. Just didn't expect something like this to ever happen so suddenly. Thank you guys

MrMike2182 said:
I totally forgot about safe mode bro lol
Click to expand...
Click to collapse
I did too for a minute, but I'm totally lost as to what could fix this problem. I'm just throwing out any answer and hopefully it helps.
---------- Post added at 04:16 AM ---------- Previous post was at 04:14 AM ----------
Jay_P11 said:
ADB won't work because I never enabled USB debugging, unless ADB pull doesn't require that. Computer doesn't see anything when it hangs. Safe mode was a no-go either :/ I don't have an SD card to put stuff on right now, although I really should've. Just didn't expect something like this to ever happen so suddenly. Thank you guys
Click to expand...
Click to collapse
The last thing I can think of is take it back to the place you bought it from, if that is possible. Especially if you didn't mod the phone. I've never heard of this problem.

I'm trying something really creative that I remember doing on an old One V. Starting the latest RUU, pulling the ROM from the temp files, placing it on an SD card, applying it in the stock recovery. It's a long shot, but its a shot. The only problem is knowing what to name the zip, update.zip doesn't seem to work.

Jay_P11 said:
I'm trying something really creative that I remember doing on an old One V. Starting the latest RUU, pulling the ROM from the temp files, placing it on an SD card, applying it in the stock recovery. It's a long shot, but its a shot. The only problem is knowing what to name the zip, update.zip doesn't seem to work.
Click to expand...
Click to collapse
Good luck

blaqueknight said:
Good luck
Click to expand...
Click to collapse
I'm still scratching my head on this one because I've never heard of this happening with the 510.
---------- Post added at 01:15 AM ---------- Previous post was at 01:11 AM ----------
Jay_P11 said:
I'm trying something really creative that I remember doing on an old One V. Starting the latest RUU, pulling the ROM from the temp files, placing it on an SD card, applying it in the stock recovery. It's a long shot, but its a shot. The only problem is knowing what to name the zip, update.zip doesn't seem to work.
Click to expand...
Click to collapse
Did you happen to do anything to the phone before this started? Did you delete any files or programs? Did the phone do an over the air update? Anything you can remember?

MrMike2182 said:
Did you happen to do anything to the phone before this started? Did you delete any files or programs? Did the phone do an over the air update? Anything you can remember?
Click to expand...
Click to collapse
Nothing of the sort, just browsing social media. News on what I tried: renamed the pulled ROM zip 0PCVIMG.zip and booted HBOOT. HBOOT accepted it as an update and I "updated" it, however, it wiped the phone. It's alive and well, but it's wiped. However, I'm left with something really off. The storage settings show 3.15GB of "other" on the internal storage, which I'm thinking might be my old data. My Files doesn't show anything as well as when hooked up to my PC. I'm going to be forever scratching my head on this as well.

Jay_P11 said:
Nothing of the sort, just browsing social media. News on what I tried: renamed the pulled ROM zip 0PCVIMG.zip and booted HBOOT. HBOOT accepted it as an update and I "updated" it, however, it wiped the phone. It's alive and well, but it's wiped. However, I'm left with something really off. The storage settings show 3.15GB of "other" on the internal storage, which I'm thinking might be my old data. My Files doesn't show anything as well as when hooked up to my PC. I'm going to be forever scratching my head on this as well.
Click to expand...
Click to collapse
That's basically the carriers crap/programs on there... Mine says that too but a bit less since I've gotten rid of a lot of bloatware.
May I ask how you managed to get the phone to accept that as an update?

MrMike2182 said:
That's basically the carriers crap/programs on there... Mine says that too but a bit less since I've gotten rid of a lot of bloatware.
May I ask how you managed to get the phone to accept that as an update?
Click to expand...
Click to collapse
I went through the official HTC RUU's temp files to find a zip called "rom.zip". I copied that to a clean SD card, renamed it to 0PCVIMG.zip (in HBOOT, it would check to see if those files were on the SD card before coming to the main screen), then the phone unzipped it and asked if I wanted to update. Thinking it would act as a normal update, I hit " yes". It took about 10 min to finish flashing in HBOOT (not recovery). It rebooted to a clean slate 510.

Jay_P11 said:
I went through the official HTC RUU's temp files to find a zip called "rom.zip". I copied that to a clean SD card, renamed it to 0PCVIMG.zip (in HBOOT, it would check to see if those files were on the SD card before coming to the main screen), then the phone unzipped it and asked if I wanted to update. Thinking it would act as a normal update, I hit " yes". It took about 10 min to finish flashing in HBOOT (not recovery). It rebooted to a clean slate 510.
Click to expand...
Click to collapse
I was just curious because I thought you didn't have an sd card but glad it's working again albeit wiped.

MrMike2182 said:
I was just curious because I thought you didn't have an sd card but glad it's working again albeit wiped.
Click to expand...
Click to collapse
Yeah I went out and bought one in hopes I could move everything to it. I've been using OTG drives for a while on everything else I have and thought SD cards were a pain, boy was I wrong.

Jay_P11 said:
Yeah I went out and bought one in hopes I could move everything to it. I've been using OTG drives for a while on everything else I have and thought SD cards were a pain, boy was I wrong.
Click to expand...
Click to collapse
The SD card for this phone is rather pretty important if you ask me because with the very limited amount of space we have on it is a major problem when it comes to installing a lot of the programs/apps we use... I think the SD card is a lifeline since it keeps the backups and personal stuff on it and if anything goes wrong that little card saves you lol...

Jay_P11 said:
Nothing of the sort, just browsing social media. News on what I tried: renamed the pulled ROM zip 0PCVIMG.zip and booted HBOOT. HBOOT accepted it as an update and I "updated" it, however, it wiped the phone. It's alive and well, but it's wiped. However, I'm left with something really off. The storage settings show 3.15GB of "other" on the internal storage, which I'm thinking might be my old data. My Files doesn't show anything as well as when hooked up to my PC. I'm going to be forever scratching my head on this as well.
Click to expand...
Click to collapse
I just factory reset my phone and I only have 2.75GB in Other. I wonder what that stuff is on your phone. What is 0PCVIMG.zip? Where did you get it from?

blaqueknight said:
I just factory reset my phone and I only have 2.75GB in Other. I wonder what that stuff is on your phone. What is 0PCVIMG.zip? Where did you get it from?
Click to expand...
Click to collapse
I ran the RUU for my phone and found its temp files by opening the process' file location. Scroll through the files and find rom.zip that the RUU creates. Wait for it to copy and then close the RUU. Renamed the rom.zip to 0PCVIMG.zip because of the model of the phone, and HBOOT looking for the image. As for the space, I have no idea either. I'm going to get it swapped out at best buy if I can.

blaqueknight said:
I just factory reset my phone and I only have 2.75GB in Other. I wonder what that stuff is on your phone. What is 0PCVIMG.zip? Where did you get it from?
Click to expand...
Click to collapse
I'm fairly certain that the 2.75GB of used space is your carriers bloatware crap.. It's even on it's own partition and you can gather that information from running adb shell and then cat proc/emmc