Database Users

haret wont boot android anymore

i have been using xrom for about two months now and just now tried to boot a donut build with the new base files but now Haret wont even boot into linux its stuck at the Haret boot screen... I have formated the SD card and have the newest basefiles with a new system file and how been using android for months now and this has never happened before. Could anyone help with this?

you might have a file named wrong or corrupt or missing file.

no i just used an old kernal and it booted right in to the New Ion build... for now ill stick with this kernal and then try the new ones to see which boot successfully

oh ok what do i know.

zenulator said:
oh ok what do i know.
Click to expand...
Click to collapse
not sure what that means but ok, i just tried different files untill it worked. I know to rename the files and which need to be in the SD card I just have never had that problem before and it was only when I swapped out the kernal that it booted right up. Thanks for the help tho

lazyvegaskid said:
not sure what that means but ok, i just tried different files untill it worked. I know to rename the files and which need to be in the SD card I just have never had that problem before and it was only when I swapped out the kernal that it booted right up. Thanks for the help tho
Click to expand...
Click to collapse
it means you prob had a corrupt file. since you replaced it and it works. but you solved your own problem. what kernel gave you problems? so we can let people know there are problems with it.

no there was no kurupt file and all files are named properly, i have helped many people here in vegas get android on their phone so I would like to think i know what im doing atleast set up wise. I have the correct settings for donut on my default.txt and are using all the newest files from google-vogue. The hang up on haret is becoming a major headache, i replaced the new kernal last time with an old one from sept (last time i upgraded the files) and it booted perectly and quick. Now the last line of code reads "attempting to reset in 3 secs" I have let it sit for 10, 15 and 20 mins with the same results... not a damn thing. I have reformatted the SD card everytime and have no other files but the android files on the SD card. Has anyone else experianced this? If someone using the newest donut build could upload their files somewhere because unless im a huge idiot I swear im following all instructions to a T. Someone please help... Im not as lazy as my name states its just the only name i could think of haha so please no flaming

lazyvegaskid said:
no there was no kurupt file and all files are named properly, i have helped many people here in vegas get android on their phone so I would like to think i know what im doing atleast set up wise. I have the correct settings for donut on my default.txt and are using all the newest files from google-vogue. The hang up on haret is becoming a major headache, i replaced the new kernal last time with an old one from sept (last time i upgraded the files) and it booted perectly and quick. Now the last line of code reads "attempting to reset in 3 secs" I have let it sit for 10, 15 and 20 mins with the same results... not a damn thing. I have reformatted the SD card everytime and have no other files but the android files on the SD card. Has anyone else experianced this? If someone using the newest donut build could upload their files somewhere because unless im a huge idiot I swear im following all instructions to a T. Someone please help... Im not as lazy as my name states its just the only name i could think of haha so please no flaming
Click to expand...
Click to collapse
how far does it get before it says preparing to reset in 3 seconds

jamezelle said:
how far does it get before it says preparing to reset in 3 seconds
Click to expand...
Click to collapse
right after it says "welcome to vogue linux" this is depressing I love my 6.5 WM rom but android is the best way to go

how do I push the car dock from one ROM to another?

I want to take the cardock.apk from one ROM and use it on another. Both are 2.1 flavors, so I thought it would be as easy as taking the apk from one and pushing it to another. It worked for a little while but then it stopped working. I got an error about permissions. When I ran fix_permissions, it disapeared.
lil help?

rudeguy said:
I want to take the cardock.apk from one ROM and use it on another. Both are 2.1 flavors, so I thought it would be as easy as taking the apk from one and pushing it to another. It worked for a little while but then it stopped working. I got an error about permissions. When I ran fix_permissions, it disapeared.
lil help?
Click to expand...
Click to collapse
I would suggest taking the rom with the cardock.apk and running it in android rom kitchen . You can find a video at TheUnlockr showing you how to set it up and create your own rom. What you'll want to do in essence is un-compiled that rom and remove the apk and drop it into the rom you want (which will also be un-compiled ) once thats done just recompile the new rom with your apk in it and sign it, and flash it too your phone. Of course make sure you Nand backup first just incase something doesnt go right.

Don't do it: Reduce LCD Density Setting in Build.Prop For Higher Res Look

hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx

futureshock said:
hi
as the Title says... don't do it...
i've done it... now black Screen...
But no change to edit it back with droidexplorer or adb shell...
file is emtpy...
i'm running with Froyostone V1 maybe someone can send me the build.prop file of this build...
i don't want to restart from scratch...
thx
Click to expand...
Click to collapse
The quickest way would be to load up another clean version changing the original to froyo boot it up & go to astro copy the build from system to SD or to the froyo version & restart then delete new version and paste the build into the original froyo & reboot

so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet

Next time, try backing up the android folder on ur SD card before changing anything.. that way a quick format and a trip to ur computer will get ur phone working again..
Sent from my HTC HD2 using XDA App

futureshock said:
so i got my froyostone back to working
have pulled the build.prop from my shubcraft build... and pushed it to the froyostone build!!
hopefully the trick will work without that problem on my hopefully soon arriving android tablet
Click to expand...
Click to collapse
Can you share this file here? i got the same problem that many applications can't work with full screen, and i didn't backup this file...
thx~

Sorry for my Englisch.
Problems with the screen in fullscreen games.It is easy to change it.
Open the file with a text editor Build.Prop and edit the line of "ro.sf.lcd_density = 220" to "ro.sf.lcd_density = 240"

Followed the instructions and did this mod.
I sorta of like it. Didn't encounter any problems at all. It's hard to tell the difference. Some apps will support it, Sense UI does not.
The bigger question is. Does this impact battery life. I am still testing this..so right now that's debatable.

I set dpi to 192 and love it. Most apps show more info on screen, a few games are not clever enough.
After using WinMo for 2 years, I'm used to high precision "touching" :-D
A tip: download Spare Parts and use it to turn off compatibility mode.

i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2

vua777 said:
i just read http://forum.xda-developers.com/showthread.php?t=765639
will it work with our hd2
Click to expand...
Click to collapse
Not exactly.
The app works but doesn't really make any difference to build.prop file nor does reboot the device.
Your can manually make the changes.
I set it to 200 and I use adw launcher to make usage of the extra space.

Black screen from changing build.prop
So i really wish I found this thread before i tried to change anything. So i also have the black screen when loading android after changing build.prop file, I did copy the file before I changed it. Now i just dont know how to get into the system folder to change it back because when i load android its all black. Can anybody help me here?

[Q] Can I fix my nook without a reset? (resolved)

So today I was trying to look up on how to replace the system icons and such, so I extracted some file I cannot rememeber the name of it and replaced the images from in it with the ones I wanted, then I applyed the stuff with an app and it said I should reboot for it to work, however when it was displaying processing it crashed, and rebooted on its own. It will keep looping in the boot animation, and I'm not sure if I'm gonna have to go back to stock. And fyi I am using manualnooter.
I dont understand how it isnt working and all I edited was pictures, plus a few xmls.
Here are the name of the xmls edited if you need (all of them have nav_ in front of the name)
home.xml, jump.xml, library.xml, quickbutton.xml, search.xml, shop.xml, shop_in_store.xml, web.xml
and if your wondering what pictures were replaced from what I can tell only the status bar stuff was replaced. (i.e. c_back.png)
Also, I was trying to use the SystemUi.apk to change it, but i could not find it. so I found something else that had the icons. (trying to find the name of the file right now)
Edit: I replaced files inside of system\framework-res\drawable-mdpi\
(sort of) Resolved: I had booted a couple different recoveries, until it would get stuck on the 'N', then I did the 8 fail boot and it loaded back up to stock. Guess I'll just reflash manualnooter.

[Q] About customizing roms...

I dont have a PC so i've added files to the CM13 rom with ZArchiver. Is it still flashable?
Will it break everything or it will just refuse to flash?
I've added files to app, priv-app, permissions and framework.
I cant try on my HD2, bc usb is broken and doesnt have magdlr.

Myrmeko said:
I dont have a PC so i've added files to the CM13 rom with ZArchiver. Is it still flashable?
Will it break everything or it will just refuse to flash?
I've added files to app, priv-app, permissions and framework.
I cant try on my HD2, bc usb is broken and doesnt have magdlr.
Click to expand...
Click to collapse
try it and see. if putting apks in /system/app or /system/priv-app, they need to be in their own folder I think.
backup first though.

Robbie P said:
try it and see. if putting apks in /system/app or /system/priv-app, they need to be in their own folder I think.
backup first though.
Click to expand...
Click to collapse
Can i post a link to XDA for somebody to try it?
Or that would be a kind of a douchebag move?
My HD2 is zombie-ish right now. I gotta buy a new motherboard... I found out that the broken USB ripped a part of it, and now there is no way to fix it, ever, bc there is literally a hole in the motherboard.
I went to a service and they told me that. They were able to reattach the charging pins, but not the PC connection pin.

I suppose it depends on what apks you are trying to add, whether it would be allowed to be posted here. some apps are copyright protected.
what exactly are you trying to do?

Robbie P said:
I suppose it depends on what apks you are trying to add, whether it would be allowed to be posted here. some apps are copyright protected.
what exactly are you trying to do?
Click to expand...
Click to collapse
I know i cant upload people's apps without permissions or credit. That is just bad.
I just put HTC apps.
Like A2K did with his Sense rom for Galaxy S3. Removed CM apps and replaced them with Sense.

what rom do you have installed on your phone?

Robbie P said:
what rom do you have installed on your phone?
Click to expand...
Click to collapse
Stock 5.1.1 Sense 7 on my One M9.
Stock WM6.5 on my HD2.
Why does that matter tho? .-.
Is there any way to put MAGDLR on HD2 without a PC?
Anyway, just asked if adding a few apks to a rom (just adding files to a zip with ZArchiver) will break the flashing script or whatever. Like it will make it unusable. Or i dunno, make the phone bootloop or something...
I will not upload any link. Not gonna waste people's time with stuff that doesnt work.
Also, how do you delete a thread. I will like to delete this one.

Myrmeko said:
Stock 5.1.1 Sense 7 on my One M9.
Stock WM6.5 on my HD2.
Why does that matter tho? .-.
Is there any way to put MAGDLR on HD2 without a PC?
Anyway, just asked if adding a few apks to a rom (just adding files to a zip with ZArchiver) will break the flashing script or whatever. Like it will make it unusable. Or i dunno, make the phone bootloop or something...
I will not upload any link. Not gonna waste people's time with stuff that doesnt work.
Also, how do you delete a thread. I will like to delete this one.
Click to expand...
Click to collapse
It matters because cm13 on hd2 will not boot from wm6.5 because it uses 3.0.x kernel.
see this thread http://forum.xda-developers.com/showthread.php?t=949671 for installing magldr from sdcard, not tried it myself.
You should be able to add stuff to the cm13 rom, it installs to sdcard partitions, worst result is it wont boot.
You can use the report button (triangle) and ask a friendly Mod to delete this thread at their discretion. Please tell us how you get on first though.

Robbie P said:
It matters because cm13 on hd2 will not boot from wm6.5 because it uses 3.0.x kernel.
see this thread http://forum.xda-developers.com/showthread.php?t=949671 for installing magldr from sdcard, not tried it myself.
You should be able to add stuff to the cm13 rom, it installs to sdcard partitions, worst result is it wont boot.
You can use the report button (triangle) and ask a friendly Mod to delete this thread at their discretion. Please tell us how you get on first though.
Click to expand...
Click to collapse
Awesome! Thanks for the help!
If the worst result is not booting, is totally fine.
About MAGDLR, i would just buy another HTC HD2 and replace the motherboard.

Thread closed at OP's request.