Develop Bugs

[Q] What to do now, is it a decoration, or can it be saved?

Hi everyone!
I managed to root my DHD last night, used the tool to get S-OFF and ENG-OFF thing, well, everything that I could. I changed my radio, and installed a custom rom, everything went well. Then, I decided I'd want a new theme..... And then everything goes... yeah..
I installed Android Revolution and chose CommonSense as my new theme.
Well, I as I read that you need to use CWM Recovery and install the theme as a .zip from there, so I did. Put the .zip in my sd root and installed the theme from there. But it seems that was not the way to do it.
And as I read the instructions, that was definitely not the way to do it.
So, now my phone boots, HTC with big letters comes up, and then it changes to HTC Quietly Brilliant with a twitch. After being on Quietly Brilliant, it goes to black for 400 ms, and changes back to Quietly Brilliant and starts to loop that.
I tested that I can still do fastboot, and go to CWM Recovery from there..
But, I firstly decided to come up on here to ask what should I do now?

You can reflash the rom or find a working theme and install so that the boot loop will be gone.
Sent from my Desire HD using XDA App

its only a bootloop chillout there are 3 options, 1. find the version of that thme for your rom and flash it again. 2. flash your rom again. 3. push your framework-res.apk to/system/framework/ using adb

Yeah, I think it's being fixed right now.
I tried installing theme again.. THE RIGHT WAY and the RIGHT THEME. But, that didn't help, so now I'm flashing the rom again.
It's a great relief that it was just a "bootloop chillout"
Thanks for your help Lopio & AndroHero!

c4tlub3 said:
Yeah, I think it's being fixed right now.
I tried installing theme again.. THE RIGHT WAY and the RIGHT THEME. But, that didn't help, so now I'm flashing the rom again.
It's a great relief that it was just a "bootloop chillout"
Thanks for your help Lopio & AndroHero!
Click to expand...
Click to collapse
if your going to mod your device expect many bootloops best idea is before you flash anything, do a nandroid backup in recovery, it only takes a minute and if anything goes wrong you dont have to mess about flashing a new rom, you can just restore your old one

next time, backup before you flash from the CWM.
if u have a boot loop, you just need to re-flash the rom.

[Q]

Hello guys,
yesterday, I unlocked my GN and flashed a custom ROM and a kernel. Everything went fine and works really smooth.
The problem is, I forgot to do a NAND back up. Is that a serious issue?
I used to have an HTC desire ages ago and I sometimes did the back up sometimes forgot to.
Thanks for help.

JCUK89 said:
Hello guys,
yesterday, I unlocked my GN and flashed a custom ROM and a kernel. Everything went fine and works really smooth.
The problem is, I forgot to do a NAND back up. Is that a serious issue?
I used to have an HTC desire ages ago and I sometimes did the back up sometimes forgot to.
Thanks for help.
Click to expand...
Click to collapse
No, it's not an issue, as the stock images are freely available.

Stock Img
you can pick up the stock image @
code.google.com/intl/en-uk/android/nexus/images.html
sorry. i was too much lurking through the time - cant post clickable HTML links yet, soz

Please write more than [Q] in the title of a new thread as it really doesnt give users any indication of what the thread is about.
Mod hat off you can install Rom Manager (free) from the Market, then flash ClockworkMod via that, reboot into Recover via Rom Manager and make a NAND backup for future fallback if you need it.
If you have CMW on a stock rom you need to remove the recovery-from-boot.p file from /system or it will restore your stock recovery upon boot.
Mark.

Problem installing a new ROM

Hi Guys, i have searched a few Threads but looks like, im the first one with a problem like that.
Today i installed a new ROM from -> AOKP Milestone 4 to AOSP LIQUIDSMOOTH-v1.2.
But latley i have seen its not Multilanguage Support included. So i tried to go back to my old Milestone 4 ROM via Restore from Recovery Mode.
But its stuck in Bootscreen. So i decided to install it fresh, as i have the last Build still in the internal Storage.
But also i get stuck in Bootscreen and restarts... So back to AOSP and even that is not better, its Booting but then it tries to refresh the Apps and restarts on half way, and i made a full wipe also dalvik cache. I dont know what to do yet... anyone can help?

Silvercn said:
Hi Guys, i have searched a few Threads but looks like, im the first one with a problem like that.
Today i installed a new ROM from -> AOKP Milestone 4 to AOSP LIQUIDSMOOTH-v1.2.
But latley i have seen its not Multilanguage Support included. So i tried to go back to my old Milestone 4 ROM via Restore from Recovery Mode.
But its stuck in Bootscreen. So i decided to install it fresh, as i have the last Build still in the internal Storage.
But also i get stuck in Bootscreen and restarts... So back to AOSP and even that is not better, its Booting but then it tries to refresh the Apps and restarts on half way, and i made a full wipe also dalvik cache. I dont know what to do yet... anyone can help?
Click to expand...
Click to collapse
Can you still get in recovery? I know it is a bit drastic but relocking and unlocking your bootloader , re rooting and reflashinh might be an option. Off course you will loose all your data but you might have your phone back...

Hi, yeah thats what i have done yet!
I thought there is may another way to get on the storage and getting my files. But however, got a fresh Rom now

MIUI boot loop

Hi guys, I'm new on xda forum. If there is already a topic like this one i'm very sorry but the search function does not work right now so i cannot search what i am looking for because of the 51+ pages. I have a recently bought Gio. I rooted it and I wanted to install this rom on it (MIUI v4 -http://forum.xda-developers.com/showthread.php?t=1863260 ). I followed every single! instruction and I ended up with infinite bootloop. I think loose my mind...I don't want to mess up my phone. I searched the internet and some say it's normal to take 20 minutes at first boot, others say to reflash the rom many times and others say to format the partition from rfs ( i think) into ext4. I really need your help. Thank you
I mention i flashed the rom several times erasing every time dalvik cache and cache and reseting to factory but nothing works. Maybe it's CWM's fault.

You have make a full-wipe after flashing.
If this doesn't help, then flash CM7 and then MIUI.

To98 said:
You have make a full-wipe after flashing.
If this doesn't help, then flash CM7 and then MIUI.
Click to expand...
Click to collapse
I flashed CM 7.2 and unbelievable! it bootloops in cyanogen too

I had a same trouble too, my phone was bootlop on samsung logo
i think MIUI isn't support for gio

boyanboyan said:
I had a same trouble too, my phone was bootlop on samsung logo
i think MIUI isn't support for gio
Click to expand...
Click to collapse
So why it's even on Gio's dedicated forum if it's not working, but anyway other people seem to have MIUI running very well on their Gio. Mine it's stuck at MI logo. What scares me more is that I heard some roms can brick your phone days later after install. I did a backup of the original but i still want to have MIUI running because it's very fast and bugfree and very good looking. If you find something to make it run make sure you post here. Thanks.
Please people, I need some help here

happend to me too.. just wipe everything

Any idea why no rom will work? (CDMA)

I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.

Did you do a full wipe ???

ryansinibaldi said:
I recently recieved my One V and finally decided on rooting/installing a custom rom. I came from an Optimus V and had no problems installing a custom rom in that.
However it seems that no matter what kernel/rom I use they eventually lock up within the first 5 minutes of booting and restart. I've tried practically everything and can't get them to work. I wanted to ideally run the CDMA Pacman Rom w/ the Supersick kernel. Any help would be greatly appreciated so I have can have this working before work tomorrow.
Click to expand...
Click to collapse
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...

donhashem.dh said:
Did you do a full wipe ???
Click to expand...
Click to collapse
Full wipe as in? (sorry, still a bit new). I did do a factory reset in CWM before installing whichever ROM I was trying at the time. I wiped all caches too.
slack04 said:
"It ain't workin" isn't enough information for anyone to troubleshoot from.
Be more specific on what you did, which instructions you followed, what ROM and what kernel, what sort of computer you're running, where you're downloading from, and the steps you are taking. If none of the ROMs are working, the problem is probably not the ROM, if you know what I mean...
Click to expand...
Click to collapse
I used the HTC One V AIO Toolkit to unlock the bootloader, get root, install CWM 6.0, create a backup and then install a kernel (I used the Super Sick JB one). From there I used CWM to gain access to my SD card and transferred over the CDMA Pacman ROM (after wiping everything clean) and then installed the ROM. It booted up successfully however as stated in a minute or so it would freeze up and restart itself. Even if I don't do anything after a reboot it'll still reboot itself anyways.
I did a bit of research and I'm thinking it could be due to the OTA Radio update from 2-3 weeks ago? I'm at my bootloader now and it says I have radio version 1.00.00.0928.
Any further help to resolve this issue would be greatly appreciated. It's worth noting that I've tried many different Kernels (repeating all the steps above with full wipes every time) and different ROMs that were supported by the kernels. I've even tried to restore my phone back to stock and it just starts skipping at the VM Boot screen.
Oh, and I'm running Windows 7.

You mean the Rom booted normally right ?? If yes then the problem is with the Rom

donhashem.dh said:
You mean the Rom booted normally right ?? If yes then the problem is with the Rom
Click to expand...
Click to collapse
Pardon my ignorance but that just doesn't make sense. I've tried several different ROMs with the correct kernel's (Pacman, CM9/10, AOKP JB) and it's all the same scenario. They all boot (or occasionally don't boot and restart themselves at the boot animation) and then reboot themselves once they're pass the lock screen.
Like I said even currently if I restore my stock rom file it just loops at the VM Boot animation (which doesn't play fluidly).

Figured out the issue . It was radio version 1.00.00.0928 messing up my kernel.