Database Info

[Q] I am Bricked....i think

Ok, So i rooted my T-mobile G2x 2.3.3 and there were difficulties when i flashed the Cyanogen 7mod. The Rom worked but the only default was i didnt get data. Like i couldnt even get Edge. The only way to use internet and stuff was through wifi. SO then i reflashed it thinking it was a bad flash. But when i reflash through rom manager it gives me the option to downoad with google apps. so i clicked that option. It downloaded fine but on the reboot it stayed stuck on the 2nd LG screen. Am i bricked or if anyone can help id appreciate it alot.

U can't do it via rom manager. U have to flash recovery using nv flash, then u can try to flash custom rom. Remeber to wipe data and format system before flashing any rom.
U r not bricked yet
Check here to nv flash the cwm
http://forum.xda-developers.com/showthread.php?p=13330067
Sent from my LG-P999 using xda premium

Did you flash CWM via NV Flash. If not, do that. Then boot into recovery by holding down the power + volume down keys until you get the second boot logo. Then wipe the dalvik cache and the regular cache. That is usually why a phone refuses to boot.
Also, if your phone turns on it is not bricked. Bricked means when you press the power button nothing happens at all. You can be soft-bricked like you are, but it can be easily fixed. Nothing to panic about.

I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.

iSpooNz said:
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
Click to expand...
Click to collapse
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.

jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
Ok so from CWM do i wipe everything?

jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
@OP, this is is correct. Use tga gunmann's nvflash tool from the development section. The process is super easy. Just make sure to follow his instructions closely. Just fyi, most people get errors during the nvflash process because they don't install the apx drivers appropriately, so take your time and read the instructions carefully.

iSpooNz said:
Ok so from CWM do i wipe everything?
Click to expand...
Click to collapse
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.

phburks said:
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
Click to expand...
Click to collapse
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up

iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.

iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.

phburks said:
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
Click to expand...
Click to collapse
Ok ill try that.
jboxer said:
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
Click to expand...
Click to collapse
Yea i wiped Dalvik cahce and the same result came up. So i factory resetted and same result. So im going to try what phburks said and see what happens.

Im still stuck in the second LG screen :/

iSpooNz said:
Im still stuck in the second LG screen :/
Click to expand...
Click to collapse
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.

phburks said:
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
Click to expand...
Click to collapse
download the rom right?

iSpooNz said:
download the rom right?
Click to expand...
Click to collapse
Yea the rom. Is it cm7 that you're wanting to flash?

phburks said:
Yea the rom. Is it cm7 that you're wanting to flash?
Click to expand...
Click to collapse
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.

phburks said:
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
Click to expand...
Click to collapse
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?

iSpooNz said:
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
Click to expand...
Click to collapse
Not sure. I'd just play it safe, re-download both, wipe data, and reflash both. Sometimes its hard to determine which step went wrong and its best and quicker to just start with a clean slate and redo everything.

I wont be able to post for a while so good luck.

[SOLVED]HTC One S Won't Go Past Boot Animation

I have a rooted phone, with flash cwm recovery (latest), and used the proper boot.img file for that ROM.
I have tried wiping everything (date, cache, dalvik, etc).
When I turn on the phone it goes past the HTC logo, but it stays on the current ROM's logo. It just doesn't go past that.
Any way of fixing this? Thanks in advance.

jjuice525 said:
I have a rooted phone, with flash cwm recovery (latest), and used the proper boot.img file for that ROM.
I have tried wiping everything (date, cache, dalvik, etc).
When I turn on the phone it goes past the HTC logo, but it stays on the current ROM's logo. It just doesn't go past that.
Any way of fixing this? Thanks in advance.
Click to expand...
Click to collapse
wrong forum section dude...
but did u unlocked ur bootloader?

jjuice525 said:
I have a rooted phone, with flash cwm recovery (latest), and used the proper boot.img file for that ROM.
I have tried wiping everything (date, cache, dalvik, etc).
When I turn on the phone it goes past the HTC logo, but it stays on the current ROM's logo. It just doesn't go past that.
Any way of fixing this? Thanks in advance.
Click to expand...
Click to collapse
do you have S3 or S4 ,wich ROM did you flash?
and this is wrong place to post with questions like that ...

AlfalfaX said:
wrong forum section dude...
but did u unlocked ur bootloader?
Click to expand...
Click to collapse
Yeah sorry I just realized that.
Yes the bootloader is unlocked.

luxandroid said:
do you have S3 or S4 ,wich ROM did you flash?
and this is wrong place to post with questions like that ...
Click to expand...
Click to collapse
S4?
I flashed this ROM: Unofficial AOKP JellyBean for Ville (HTC One S)

jjuice525 said:
S4?
I flashed this ROM: Unofficial AOKP JellyBean for Ville (HTC One S)
Click to expand...
Click to collapse
S4 with? means you dont know ? so if you have S3 that ROM wil not work at all

luxandroid said:
S4 with? means you dont know ? so if you have S3 that ROM wil not work at all
Click to expand...
Click to collapse
Yes I do know. I meant S4 without the question mark

Thread Moved​
Do not post questions in a dev section.​

Relock
jjuice525 said:
I have a rooted phone, with flash cwm recovery (latest), and used the proper boot.img file for that ROM.
I have tried wiping everything (date, cache, dalvik, etc).
When I turn on the phone it goes past the HTC logo, but it stays on the current ROM's logo. It just doesn't go past that.
Any way of fixing this? Thanks in advance.
Click to expand...
Click to collapse
Relock your phone and Fine your RRU Update after that
Use this Tool to ROOT!!:
http://forum.xda-developers.com/showthread.php?t=1604677
Then Root your phone again and you should have no problem after that
If I was you ill use TWRP Recovery its better then CWM

[SOLVED]
I solved the problem using another method! Thanks everyone for answer this thread though
****
For those searching for a solution of this issue this is what I did to solve the problem:
You need to download twrp boot img ...fastboot flash recovery (recovery name)
wipe factory reset, system, and both caches all x3 then proceed to install
Fastboot erase cache
Fastboot reboot-bootloader
Go into twrp recovery
Flash ROM
Erase both caches (Cache and Dalvik)
On your CPU go to the zip, open it... right click on boot IMG choose extract to where you have your fastboot.
Go into fastboot
Fastboot flash boot (your boot IMG)
Fastboot erase cache
Fastboot reboot
Wait a few mins... if no boot put back in recovery erase both caches manually then reboot system....this will work
Thanks to $droyd$. All credits go to him

[Q] ROMs not working

Hi:
I need ROMS that allow for bluetooth tethering. I have gotten pyr-o-ice_ICS_1.0.2 to work, but it does not seem to want to use 4G. The best I can get is 3G. I am also having problems with some apps I use a lot (like Kindle). So, I would like to try some other ROMS. I have tried Wildchild_IcE_Rom_v0.9 and cm-9.1.0-doubleshot, but both get stuck on their splash screen during boot.
This phone still has S-ON, but I am flashing a new boot.img with each new OS.
So, can I get these ROMs to work? Or, can you guys suggest a ROM I should be using?
Thanks.

What's your wipe method. And are you fastbooting the new kernel? Most likely its one of two things, a bad download (md5 sum not being checked or a failure to wipe the device.
Sent from a KangBanged JellyBAM

strapped365 said:
What's your wipe method. And are you fastbooting the new kernel? Most likely its one of two things, a bad download (md5 sum not being checked or a failure to wipe the device.
Sent from a KangBanged JellyBAM
Click to expand...
Click to collapse
Thanks for the quick reply.
I am using the instructions from http://forum.xda-developers.com/showthread.php?t=1508556. I
Extract the "boot.img" file from the zip file on my PC
Boot the phone into fastboot mode and connect it to the PC
Run fastboot flash boot boot.img. I am making sure I am using the right one.
Reboot the phone into Recovery
Wipe data/factory reset
Wipe cache parition
Flash the zip file.
Reboot the phone
Isn't that right?
I have downloaded cm-9.1.0-doubleshot twice and still no go.

Yeah but only for flashing the boot.img, so if you followed that exactly and only did what that guide says you didn't wipe the device in recovery at all so that's why its failing to boot
Sent from a KangBanged JellyBAM

strapped365 said:
Yeah but only for flashing the boot.img, so if you followed that exactly and only did what that guide says you didn't wipe the device in recovery at all so that's why its failing to boot
Sent from a KangBanged JellyBAM
Click to expand...
Click to collapse
I do:
Wipe data/factory reset
Wipe cache parition
What else do I need to do?

hallevison said:
I do:
Wipe data/factory reset
Wipe cache parition
What else do I need to do?
Click to expand...
Click to collapse
Format system, data,cache,and dalvik( in mounts menu ), wipe data factory reset then flash
Sent from a KangBanged JellyBAM

You can always
fastboot wipe system -w
Being you'll need to be @ a pc to fastboot flash the kernel
Sent from my HTC Vision using Tapatalk 2

And ALWAYS flash the kernel last. You're going to have a few that work fine but 80% of developers wipe the boot partition when setting the mount points from the updater script before starting the new ROM flash. Not all....but most do.

Thanks! I got things working.
For the record, I
Extract the "boot.img" file from the zip file on my PC
Reboot the phone into Recovery
Perform a nandroid backup
Wipe data/factory reset
Format system,data, and cache (my machine does not have dalvik. Also, I think data and cache were already done by the previous wipes)
Boot the phone into fastboot mode and connect it to the PC
Run fastboot flash boot boot.img
Reboot the phone into Recovery
Flash the zip file
Reboot the phone.
"fastboot wipe system -w" did not work for me. On my version wipe is not an option. Looking on the web, I found "fastbook erase system -w". However when I tried that, I got an error that said "FAILED <remote not allowed>"
Thanks again

Im sorry wasn't thinking
fastboot erase system -w
Is the proper command, you aren't allowed because you don't have an engieneering bootloader, I would definitely recommend one as it can help out wonders if you run into issues in the future
Sent from my Desire Z using xda premium

demkantor said:
Im sorry wasn't thinking
fastboot erase system -w
Is the proper command, you aren't allowed because you don't have an engieneering bootloader, I would definitely recommend one as it can help out wonders if you run into issues in the future
Sent from my Desire Z using xda premium
Click to expand...
Click to collapse
No problem. The other way worked fine. I am happy.

[Q] Juopunutbear successful but still stuck on bootloader screen, HELP!!!

I can't figure out what else I need to do. My HBOOT reads 1.45.1313 now instead of 1.45.0013, which is what it read before. Tried to boot a couple of ROMS but none where successful, now I am back on the stock ROM. Can someone please lead me in the right direction.

Did you wipe your device when your tired a new ROM? Or did you willy nilly just flash everything overtop your current OS

Wiped cache and dalvik
strapped365 said:
Did you wipe your device when your tired a new ROM? Or did you willy nilly just flash everything overtop your current OS
Click to expand...
Click to collapse
I did both of the wipes, cache and dalvik, but nothing past that.

also factory reset and once 4ext recovery is up and running on this phone use the reformat all option (cant wait for 4ext!)
for now a fastboot -w will be next best thing
fastboot erase system -w
also make sure to follow the instructions in op of rom of choice(gapps, seperate kernel, etc)
and remember first boot may take some time - if youre still stuck try and post a logcat

It worked!!!
demkantor said:
also factory reset and once 4ext recovery is up and running on this phone use the reformat all option (cant wait for 4ext!)
for now a fastboot -w will be next best thing
fastboot erase system -w
also make sure to follow the instructions in op of rom of choice(gapps, seperate kernel, etc)
and remember first boot may take some time - if youre still stuck try and post a logcat
Click to expand...
Click to collapse
Did a factory reset and it solved the problem!

camsoup01 said:
Did a factory reset and it solved the problem!
Click to expand...
Click to collapse
Now nextime either use every wipe option in recovery or the fastboot wipe or nothing will boot
Sent from my myTouch 4G Slide using Tapatalk 2

[Q] Possible Brick?

All,
I updated to the latest RebelRom today but had an issue with the email client so tried to re-flash the previous version (forgot to make a backup...). Somehow during this re-flash the phone rebooted so the flashing never took.
Now when I go into recovery(TWRP) I get the TWRP splash screen and then it boot loops.
I've tried flashing the recovery again (2.4.0.0) and flashing the boot.img again however this continues to happen.
I tried a factory reset and it too just boot loops on me.
Any suggestions or is this bricked good?

overkil6 said:
All,
I updated to the latest RebelRom today but had an issue with the email client so tried to re-flash the previous version (forgot to make a backup...). Somehow during this re-flash the phone rebooted so the flashing never took.
Now when I go into recovery(TWRP) I get the TWRP splash screen and then it boot loops.
I've tried flashing the recovery again (2.4.0.0) and flashing the boot.img again however this continues to happen.
I tried a factory reset and it too just boot loops on me.
Any suggestions or is this bricked good?
Click to expand...
Click to collapse
Ruu and start over

a box of kittens said:
Ruu and start over
Click to expand...
Click to collapse
Ruu? Can you go into some details, please?

Shouldnt have to ruu.. Download latest twrp. Verify checksum. Fastboot flash recovery recovery.img then download clean rom or viper put on sd, wipe cache, dalvik, system, factory reset in twrp and install rom.
Sent from my One X using xda app-developers app

exad said:
Shouldnt have to ruu.. Download latest twrp. Verify checksum. Fastboot flash recovery recovery.img then download clean rom or viper put on sd, wipe cache, dalvik, system, factory reset in twrp and install rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I can flash the recovery fine but I can't get into recovery. Just the splash screen then it reboots to the HTC screen and loops.

overkil6 said:
I can flash the recovery fine but I can't get into recovery. Just the splash screen then it reboots to the HTC screen and loops.
Click to expand...
Click to collapse
If it's boot looping then you're not flashing recovery just fine.... If recovery flashed fine then when you select recovery from the bootloader, it would boot to recovery..
Sent from my One X using xda app-developers app

overkil6 said:
I tried a factory reset and it too just boot loops on me.
Click to expand...
Click to collapse
Factory reset is not what you think it is. It just formats the user partition. If the ROM is not properly flashed, factory reset isn't going to help. Common mistake, since the term "factory reset" is a bit of a misnomer. It implies that it returns the phone to factory condition, which is quite often not the case.

hi
overkil6 said:
All,
I updated to the latest RebelRom today but had an issue with the email client so tried to re-flash the previous version (forgot to make a backup...). Somehow during this re-flash the phone rebooted so the flashing never took.
Now when I go into recovery(TWRP) I get the TWRP splash screen and then it boot loops.
I've tried flashing the recovery again (2.4.0.0) and flashing the boot.img again however this continues to happen.
I tried a factory reset and it too just boot loops on me.
Any suggestions or is this bricked good?
Click to expand...
Click to collapse
try to do
Fastboot erase cache
then again install recovery, may be it work for you.

What screen shows up when you choose recovery in bootloader?
Sent from my One X using Tapatalk 2

Do the following:
Turn your HTC On.
Holdbfhe power for 15-20 seconds.
Release, when the device flashes.
Press and hold the volume down button.
Press the power button for 3 seconds, and release.
Keep your finger on the volume down button.
This should take you to bootloader, download the latest
TWRP For your HTC.
Flash it with fast boot flash recovery twrp.Evita.version here.IMG
You should now be able to enter Recovery. I suggest getting the Avatar ROM, experiencing no current errors IMO If this has worked, please reply.

arunkarnwal1981 said:
try to do
Fastboot erase cache
then again install recovery, may be it work for you.
Click to expand...
Click to collapse
Found this tidbit elsewhere and it indeed worked! Thanks!