[Q] Trouble with Desire. - General Questions and Answers

Hi there, before I begin I have no idea where to post my introductory!
So I'll post it here,
HIII! I'm Dave from UK and I own a HTC Desire, Not HD/S
Ok, onto my problem!
Right, a few month ago I rooted my phone, cannot remember how but I did. And I installed Cyanogen. I think it was 7, unfortunately I can't check now.
So these past few weeks my battery has been draining pretty fast, having WiFi on or off didn't make a difference at all and I was charging my phone every 5 hours of so. Remember, this is with the phone on Lock. Not being used!
Yesterday I tried my friends Desire battery fully charged and within 3 hours I got "connect your charger" blah blah..
So I want to try something different, nothing too fancy but mainly something that won't drain my battery as much as that did. Don't get me wrong it an amazing ROM!
Now I went thorough the steps of installing, Flashed Clockwork mod and downloaded a ROM via ROM Manager. I downloaded RunnyMede Stock. Once it had done it prompt me to wipe dalvik, cache and back up and then booted me into Recovery.
From there I got a message, "some went wrong ect.." So I went and made a 1GB EXT partition, took the ROM off my phone and onto my PC and used the Phone to Format the card. Then put the ROM back onto the root and formatted the;
Boot
System
Data
Cache
SD-EXT and then manually wiper the Cache and Dalvik and proceeded with the Flash of RunnyMede
All was well and I chose not to install the App2SD thing.
Phone booted, and got to the Beats Audio and then started to loop.
Tried again and chose the optional App2Sd Mod and same thing.
Tried taking my SD out and booting, different Boot screen but same problem. Phone has been left fo 2 hours with charger in and same thing
I've tried
Cool3d RunnyMede & BlissMede but both do the same thing.
On my HBOOT Menu I have at the top -
BRAVO PVT3 SHIP S-ON
The only ROM I can get to work is Cyanogen, but I want something different.
My Clockwork mod version is 2.5.0.7 if it helps.
Any help will be highly appreciated!
Thanks you, also great Forum!

Related

Problems after getting back to stock ROM from CM7

Hi,
I'va had CM7 a10 flashed on my Sensation for a few days. A couple of days ago I've decided to get back to Stock ROM, and then the problems started. Before installing CM7 everything was fine. After restoring my backup from before flashing CM7 weird things started to happen (apps dissapearing, settings changing on their own, hangs, and other stuff). So I've done a SuperWipe a few times, and flashed a completely new Stock ROM via USB using: RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed file. Then I've done a few factory resets, just in case. But still weird things are happening (eg. now I have a clean phone - once again - and trying to setup the sync options and the options app hangs everytime. and installing something from market is like praying for a miracle). I've tried doing factory reset, clear cache/dalvik (but with dalvik CWM recovery says that the partition or files wasn't found). Don't know what to do. Does anyone have any ideas ?? Please help. Phone worked fine before, and after CM7 everything is f*cked up
Wierd, looks like you've tried everything I could think of while reading the post.
Do you still have a nandroid backup of CM7, if so does that work if you restore ?
Can you use ADB to get to the phone ? If so you could check some things from there.
When you installed the RUU from the PC, did it install without errors ? Presumably you had to re-install CWM after that.
CM7 nand backup works fine after restore.
I can use ADB to comunicate with the phone.
No errors while updating RUU.exe / CWM recovery flashed without problems also after that.
I think that there's something screwed up with the file permissions.
I've downloaded and installed about 20 apps since the last HR, and now I have about 40 apps more queued in Market, and as before the downloads are stuck every 1-2 apps. Then I have to restart to CWM recovery and run fix permissions. After that another 1-2 apps will download and get stuck again, and so on...
Anyone has any ideas what the hell is going on ? Because my I'm getting more then irritated by this, and beggining to think that the best solution will be to send my phone flying through the window.
A few questions first.
What country are you in?
Who is your carrier?
What version did your phone originally come with? I believe 1.5xxxxx RUU was released recently, but I could be wrong.
Did you ever change your CID?
Have you ever flashed a new radio and RIL?
Did you copy all of the data from your SD card to your computer, then format your SD card using the phone?
Answer these questions and try the SD card thing, then report back. I may be able to help.
Poland.
T-Mobile (Sensation) / Play Mobile (Gio)
Don't remeber what version my Sensation originally came with - I have a 1.50.401.1 RUU that I'm flashing with currently.
Yes, I've changed CID to 11111111 some time ago, but I'm back to original HTC__001 now.
No I haven't changed my radio or RIL.
I've tried formatting the SD card using the phone, my laptop, my linux NAS, my other phones.
The weird thing is that yesterday all of this was progressing. It came to a point that after a factory reset or even a whole ROM reflash nothing would install (not even Market update). And this also started to happen on my Samsung Gio. So after very very very frustrating evening, and part of the night I gave up. And in the morning it was still the same (on both my android phones). But now things are starting to work (updates/installs). So I think I'm going to blame the whole thing on Google and Market. I'll see what happens while I'll install all my apps in the next few hours.
Still have to restart the phone every 1-3 apps installed. This is driving me crazy

thunderbolt stuck in boot loop

hey all, was hoping someone would be able to help me out, since im still pretty new at all this.
i've had my phone for about 2 months, been rooted since the first week, and have flashed roms before with no problem, this is the first time something like this has happened.
im currently running eternity r186, have been for awhile.
ok, so heres what i did: i downloaded liquid-nonsense 3.2 rom from over at rootzwiki and copied the zip to my SD (this is the rom i was planning to flash)
i made a nandroid of my current rom
i booted into recovery using rom manager (reboot into recovery)
i wiped data and cache, everything went as normal
i went to wipe davlik, hit yes for wipe, and the screen went black and vibrated. then it rebooted to the white htc screen. now it's stuck between the white htc screen that says "quietly brilliant" and the beats audio screen (if you've booted up eternity before you know what i mean)
ive tried holding down power and the vol keys to reboot into recovery but it just takes me back to the bootloop
ive tried a battery pull
i really have no idea wtf to do, please help?
thanks
edit: i figured it out i think. i got into hboot after a battery pull and got into recovery that way, restoring nandroid now. hopefully it restores
but...that was kinda scary for a new flasher such as myself! anyone have any idea why it did that?
Good to hear you got it figured out. Liquid 3.2 is my Fav AOSP.
Since the forums move slower at night next time you have a big problem try and hop on to one of the IRC chats.
No idea why it would do that. Do you have the most recent CWR? If not try and update it. If you do then try and roll back a version unless the rom you're flashing needs the most current version.
Sent from my ADR6400L using Tapatalk
thanks for the reply.
im running the latest version of CWR
after i restored my nandroid I wiped everything as normal and flashes the rom.
i gotta say, i'm really digging this ROM. Barring any major bugs I could see this becoming my daily!

[q] need help bad plz someone

Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
Maybe a bad download.....try to get the rom file again and flash it. I installed CoreDroid V9.3 yesterday no problem at all.....
Check the MD5sum before going through. Make sure that you flashed the multidevice rom and not the Sensation....
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
dont flash from any kind of rom manager software, only do it from recovery (in case you werent)
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
I love Coredroid ROM it is an awesome ROM. I flashed the new one Coredroid 9 and absolutely hatedv it had nothing but issues with it. I'd stick with Coredroid 8.1. Best thing would be remove battery remove SD Card and use and adapter place Coredroid ROM zip on root of SD as well as FULL WIPE 1.5 zip on root of SD. Then enter recovery thru hboot with holding volume down and power button at same time then flash full wipe then flash Coredroid. Should do the job.
I dont know about the Coredroid 9 multi device deal i had issues with it and completely hated it. Though I do love Coredroid but I will stay with Coredroid 8.1cause it works flawless for me. Thou now Im addicted to Absolution (lol)
Good Luck
RE
Ive already done a full wipe can i still take battery out and sd and dowload 8.1 and still put it on my phone i just scared since i did full wipe i wont be able to get back into recovery
drewg0407 said:
Ive already done a full wipe can i still take battery out and sd and dowload 8.1 and still put it on my phone i just scared since i did full wipe i wont be able to get back into recovery
Click to expand...
Click to collapse
Yeah, you can do that. Full wiping shouldn't delete recovery, you should still be able to get into recovery via HBOOT and then from there you can mount your sd card, put 8.1 on there and flash as normal. This is assuming that you haven't done anything already to screw up your recovery..
RE:
all ive done is full wipe and tried installing man i thought i bricked my damn phone i started getting scared my wife is in basic training for the army and this is my only way to talk to her
drewg0407 said:
all ive done is full wipe and tried installing man i thought i bricked my damn phone i started getting scared my wife is in basic training for the army and this is my only way to talk to her
Click to expand...
Click to collapse
My good sir, take a breath and relax...okay good! Alright, the good news is that 90% of the people who think they bricked their phone initially, don't actually have a bricked phone. I don't want to build your hopes up and say you aren't there but let's not say its bricked until it really is!
Let's start from scratch...can you get into HBOOT (holding the vol. down and power). If you can get into HBOOT, all is not lost. Once in HBOOT, you can hit the power button and it will scan for a PD98IMG.zip, hopefully you don't have one on there. After its done scanning you should be able to use the vol. rocker to select recovery. Enter recovery and follow my previous instructions. If you cannot get into recovery, there are some RUUs in the "PD98IMG.zip" form in the stock ROM thread that you can put on your SDcard and flash through HBOOT that will get you into a working ROM and you can reinstall a recovery and get back to flashing as normal.
thx
Ok thanks to all who replied got into bootloader through cmd prompts but im installing rom now ill let yall know how it goes
everything good thank you
Then click the Thanks button of those that helped you. They deserve it.
Good job not hard to fix many issues. We just have to take a deep breath and calm down. Ifs when people freak out that they start doing stupid things to their phones making matters worse. Nothing that a quick search won't cure.
Sent from my Inspire 4G using xda premium

I think I broke it.

I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.

[Q] Rooted and flashed a rom - Did I end up bricking it?

I used Ace Hack Kit to root. It worked.
I flashed a ROM (Sabsa Prime), and, after not being impressed, changed it to ICESense (And I used the wifi fix as well).
Because I was not thinking clearly, I did not back up my stock ROM after running ace. I did, however, back up the Sabsa Prime ROM.
I had AdBlock plus installed from the market on both ROMs. On IceSence, after AdBlock was infuriating me, I uninstalled it. I went to reboot the phone. It loaded, and about 30 seconds after it was done, it froze for a second, and rebooted. the only way for me to stop this cycle was to pull the battery. It can still boot into HBOOT and CWM Recovery, however, the phone will not stay powered on long enough for me to place anything onto the SD card, such as another ROM, or the ZIP for IceSense, because I removed it from the SD card to save space.
So, I went to CWM, did a factory reset, and I restored my Sabsa ROM, only to have the same thing happen with the reboot cycle.
Am I bricked? If not, what would you recommend doing to fix this issue?
Arkona said:
I used Ace Hack Kit to root. It worked.
I flashed a ROM (Sabsa Prime), and, after not being impressed, changed it to ICESense (And I used the wifi fix as well).
Because I was not thinking clearly, I did not back up my stock ROM after running ace. I did, however, back up the Sabsa Prime ROM.
I had AdBlock plus installed from the market on both ROMs. On IceSence, after AdBlock was infuriating me, I uninstalled it. I went to reboot the phone. It loaded, and about 30 seconds after it was done, it froze for a second, and rebooted. the only way for me to stop this cycle was to pull the battery. It can still boot into HBOOT and CWM Recovery, however, the phone will not stay powered on long enough for me to place anything onto the SD card, such as another ROM, or the ZIP for IceSense, because I removed it from the SD card to save space.
So, I went to CWM, did a factory reset, and I restored my Sabsa ROM, only to have the same thing happen with the reboot cycle.
Am I bricked? If not, what would you recommend doing to fix this issue?
Click to expand...
Click to collapse
Have you tried remaining plugged into charger to reflash Rom. Possibly the battery is bad. Or does it only reboot when you mount your USB storage? Do you have another SD card to try?
Sent from my Inspire 4G using xda premium

Categories

Resources