Related
Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!
I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.
Hello all.
I have a t-mobile g2, currently S-OFF, which is sitting in hboot/fastboot right now. I will not boot past the HTC screen.
I attained root last night using this method, and it worked without problems. I then gave a few apps (terminal and shark, to be precise) superuser access. Went to sleep.
This morning, I wanted to delete some apps and change some system fonts around (wanted to use the ubuntu font instead of droidsans). deleted photobucket at amazon mp3. while trying to change the fonts, I changed permissions on the /system/ folder to 777 (chmod 777 /system/). Changing the fonts wasn't working out, so i decided to leave it alone and just reboot my device. upon reboot, it would no longer boot past the htc boot screen. It will, however, go into hboot/fastboot mode without a problem. I tried going into recovery mode and using the update.zip (e4aaacea73af.OTA_Vision_TMUS_1.22.531.8-1.1.19.531.1_release_signed.zip renamed). No luck. Also, i tried researching on the forums and using adb to try to unbrick, but adb doesn't recognize any device being plugged in. fastboot did work, though, and i wrote the original recovery.img file into the phone (although I don't know where it goes when this is done...) and now I don't know where to go next. any help?
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Vandale said:
Try wiping your data and flashing a new rom on there. Some roms have a OC kernel so I would also make sure u know what kind of kernel the rom has. If its OCed I would download o non OCed kernel. Reason being some are like OCed to the max which makes the phone not boot, and when turned off sleeping doesn't want to turn back on.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I had stock android that came with the phone, I just got it about a week ago. Is there any way to find the standard/stock android rom for the g2? if anyone could link it and let me know how to flash it, that would be amazing.
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
consciousdawn said:
Update:
I've been doing a bit more research, and I found that it might be possible to flash a stock rom (PC10IMG.zip). I downloaded the TMOUS one provided in this thread and shortened it to PC10IMG.zip. Once I do that, I go into Hboot, and when it checks for the different nbh/zip images, it always tells me "no image"/"no image or wrong image!". HELP!!!
Click to expand...
Click to collapse
Which one did you download? The first few on there were pre-release ROMs. The 1.19.531.1 ROM was the release ROM originally. Most recent G2's come with 1.22 (the OTA update) pre-installed, which we do not currently have a PC10IMG.zip for. If your G2 had 1.22 (e.g., you already had wifi-calling and tethering), you won't be able to use the 1.19 PC10IMG unless you used gfree to obtain S-OFF. If you did not (i.e., you only flashed the engineering HBOOT), you should not try to flash this file (it will replace your HBOOT with the shipping version and then quit mid-flash because it sees you already have a higher version installed). Even if you did obtain S-OFF with gfree, flashing this file will cause you to lose your engineering HBOOT and root (though you will still have S-OFF, so it's easy to re-root).
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
ianmcquinn said:
As was stated earlier, the easiest/best thing to do at this point is flash a custom ROM. If you still want the stock look-and-feel, here is a pre-rooted stock G2 ROM: http://forum.xda-developers.com/showthread.php?t=836042. You want to flash it through ClockworkMod recovery. I'm assuming you hadn't installed this already or you would have a backup of your ROM that you could have simply restored. You can install ClockworkMod recovery through fastboot though (there is a thread in the dev section or you can search for one of the many guides on it).
Also, you will probably want to get the de-odex version of the stock ROM. If you are doing any kind of theming or UI modifications, that is usually required (or your changes will cause a bootloop). Without knowing the details of what you tried to do, I'm guessing this is what happened to you (since the stock ROM is odex'ed).
Click to expand...
Click to collapse
Do you mean this thread? I have been trying to follow along and it's a bit confusing (although I feel that's due largely in part to grammatical/usage errors). what you are saying does help a lot though. I just need to learn how to install Clockworkmod Recovery through fastboot. *googles away* in the meantime, feel free to link me to another thread which helps me do this. Thanks a million.
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
consciousdawn said:
UPDATE:
I finally figured out what I was doing. So I used fastboot to flash a clockworkmod recovery.img onto my g2. When I went to recovery, after booting into hboot, it went to the HTC screen, as it should. Guess what I got? loopboot, once again T_T. Luckily I still have the official recovery.img, and reflashed that. Did I do something wrong? Please let me know.
Click to expand...
Click to collapse
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
That's exactly what happened, and no, not at all. It said it flashed successfully. Maybe I don't have the correct version of Clockworkmod? If you could please link me to a good one, that would be great.
UPDATE!!
So I found an official clockworkmod 2.5.1.2, and now when I boot into recovery, it shows the HTC logo and then goes to clockworkmod. This is amazing. Thank you guys for all your help, I have learned something new today.
Now, can someone explain the difference between odexed and deodexed? please? lol.
ianmcquinn said:
Wait, so what exactly happened? You entered the bootloader (white screen with green Android guys at the bottom), selected to enter recovery (using volume down and power button to select), and then was presented with an HTC logo? That means ClockworkMod recovery did not successfully flash. Did you get any errors when you used flashboot?
Click to expand...
Click to collapse
Looks like I cried victory too quickly. While I do get the menu for clockworkmod (every time I boot, for that matter), every time I issue a command, such as reboot now, or install from SDcard, and even advanced, the screen goes black. GRRR, WHAT AM I DOING WRONG? I've been at this since about 1 today T_T
Just wanted to say that I'm the biggest noob on the planet. While I did upgrade to cwm 3.0.0.5, i didn't know it allowed the use of the main controls. I got my phone up and running now. Thank you for all the help. Good night :]
T-Mobile G2 Bootloop
I have a T-Mobile G2 which is bootlooping on CM7 and Virtuous GLite 1.0.1. I have been running CM7 without problems since it was released. The bootloop started during the night without any prior symptoms. I have searched the xda and other sites extensively for days and tried so many things to fix this, some of which I was unsure about, but figured 'what the hey' since I had such limited success reflashing roms, clearing data, dalvik cache, etc...
Here is some information:
If I immediately put the phone in airplane mode upon bootup while running CM 7.03 it will not go into bootloop. I can use it indefinitely in this state (it seems) but there is only so much fun you can have in airplane mode...
With CM7.03 installed, here is the info from my 'about phone' section:
Model: HTC Vision, Android Version: 2.3.3, Baseband Version: 12.28b.60.140eU_26.03.02.26_M, Kernel Version: 2.6.32.40-cyanogenmod [email protected] #1, Mod Version: CyanogenMod-7.0.3-vision, Build Number: GRI40
I have Rom Manager v4.2.0.2
-----
Some other information:
I am, however, able to run another mod, Stock w/root (http://forum.xda-developers.com/showthread.php?t=836042) which I was able to flash, along with pershoot's kernel (http://forum.xda-developers.com/showthread.php?t=847672). When I run this mod I am not able to activate WiFi. I click to enable it and after a few seconds I get an error and it turns itself off.
Interesting to note- the first boot-up after flashing CM7 I get about 20-30 seconds before it starts bootlooping. During this time I tried to quickly activate WiFi and it errored out the same way is it did running the "Stock w/root" mod listed above.
This made me think (in my limited knowledge) that it could be related to a radio issue... so I tried to flash a couple different radios claiming to be for the G2/desire. No luck there.
-------
I am able to access recovery mode, flash roms, restore roms, etc...
-------
The bottom line for me, I want to run CM7... I know it works(ed) on my phone. How many layers do I have to strip away to get to the point that whatever bad thing is causing my phone to do this with multiple roms is gone?
Rom? Kernel? Radio? what else is there to fix? Any suggestions on where I go from here? What about the no WiFi issue?
I have already searched the forums as I stated, so linking the first 'G2 bootlooping solved' thread you can find probably wont help me. Maybe understanding more about what could be causing this so I can have a direction to persue this further would be most helpful.
Thanks very much!
Did you wipe your phone before applying CM7?
re: did you wipe your phone
blackknightavalon said:
Did you wipe your phone before applying CM7?
Click to expand...
Click to collapse
Yes- in recovery mode I performed a wipe, then cleared cache and dalvik cache before flashing.
---------
Also, to add more info to the original bit of information I shared- last night I flashed CM6 without any bootlooping issues, but the WiFi problem is still there.
Is it possible to set a radio image to read only so that a recovery wipe/dalvik cache clear will not have permission to clear it? If so, maybe when I flashed a radio before I set it that way without knowing (I honestly can't remember, but I do know that at one point a guide had me flashing something using fastboot and setting chmod something-or-other).
^ I guess I can just press Vol down and Power to check my radio version to see what one I am running and check if it is compatible with CM7.
Any suggestions?
Crazy coincidence.. This morning at 7:45 am my wifes G2 started boot looping. I know it was 7:45, because it was about the time the alarm was supposed to go off.
Hers appears to be a bit worse off, as while I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
I curious to see if anyone else is seeing this, and what the fix might be. I haven't really tried much except getting into recovery since I'm cautious to screw it up further.
Anyone have any ideas?
I now firmly hold the hypothesis that my individual bootloop problem is being caused by my wifi adapter. I am able to flash any rom that doesn't use a kernel based on CM7. On every rom that works ('Stock w/root', Cyanogen6, GingerSense) the WiFi is the only problem. On CM7 and another rom I flashed which was based on the CM7 kernel it bootloops.
So, I am convinced that something in the CM7 kernel polls my wifi adapter when it starts up, figures out that it is borked and then craps out and goes into a bootloop. To further reinforce this idea, as I mentioned in an earlier post- I can boot into CM7 based roms while in airplane mode and use them indefinitely that way. As soon as airplane mode is disabled it goes bonkers.
I'm done t/s this issue for my problem, going to replace the device.
sgshanaf said:
...I can get into hboot, it won't let me into recovery (and it boot loops before i see cyanogen logo).
Click to expand...
Click to collapse
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Thanks for responding. I spent a lot of time reading all the different posts I could find with similar issues and decided to take the plunge on this solution:
http://forum.xda-developers.com/showthread.php?t=912399&page=4
and it worked for me.
**UPDATE: below I was having a problem not being able to instal a rom. For whatever reason CM 6.1.1 worked fine. I was then able to go into rom manager and update that way to CM 7.03, and that time it worked. No clue what happened, maybe a bad rom .zip, maybe my SD card is getting flakey. /Shrug
The Phone is booting into that rom fine. Interestingly, while the phone now has eng hboot and working CWM recovery (in addition to still reporting S-OFF), I can't get past the "HTC" splashscreen after installing cyanogen 7 update.zip for the phone. GAPPS or not. I am doing the cache and data wipes
I can get back into recovery fine, but it's just not taking the rom install.
Scott
greenguitar28 said:
What happens when you select recovery from hboot? If nothing, what about trying a factory reset from hboot? I neither work you should have access to fastboot, but I understand your hesitation if that is the only option you have. Some things I have come across in my searches that could cause bootloops were sim cards, sd cards, and a mess of other things. You can try pulling out the two of those one at a time and doing a normal startup to see if anything changes. Let me know how far you get with the HBoot options and I will try and suggest some other things based on that.
Click to expand...
Click to collapse
I'm having trouble installing any roms on my girlfriends desire. Installing roms seems to work fine, right up until i try to boot the phone, it just gets stuck at the HTC screen, I've pulled the battery and tried again, but nothing works. I've tried multiple roms, and with every one, the same problem.
The phone is rooted, HBOOT 0.93.0001, S-ON, Baseband 32.54.00.32U_5.14.05.17
Anyone know what's going on? It's been a while since I've played with android phones, so I'm not current with all the lingo. I'm currently a WP7 user
Thanks for the help!
I'm assuming then it would be a2sd Rom?? Your ext3 or 4 setup? ROM manager sucks for this, use gparted or minitools(I've never used this one) and preferably a card reader.
Sent from my HTC Desire
Ya, I tried ROM manager for the partition, I'll give gparted a shot. thanks!
Ok, formatted the sd card, and repartitioned to FAT32, and 512mb of EXT3 and the same thing happens, it just hangs at the HTC screen after installing a rom.
How long are you giving it before pulling the battery? It can take 10 or 15 minutes on first boot. I'm assuming you've tried a couple of different roms.
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
A Dustman said:
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
Click to expand...
Click to collapse
i'm a previous hero owner, same thing happend to me, desire is different.
on all desire roms the op will tell you what hboot is made for and then to flash the alignement zip even if your sdcard is partioned , you have to otherwise the will never bootup and then you flash the rom plus whatever updates they suggest .
i think your hboot is stock, same as mine, but you need to S-off your phone in order to flash any roms, follow this guide: http://forum.xda-developers.com/showthread.php?t=1016084
try cool sensation or what ever takes your fancy
1-download the alignement zip , the rom and the updates if there are any
2- put all of them on your sd card (mount it or use usb card adapter)
3- go to recovery and flash them in sequence, usually alignement zip first + the rom and then reboot should be about 5 to 10mn any longer you in a bootloop means something wrong.
just have a good read before flashing any rom , and follow what they say.from step 1 till the end.
you'll get there, don't worry it wont brick your phone
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
A Dustman said:
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
Click to expand...
Click to collapse
You don't need s-off to flash roms, I'm not and flashed many. Make sure your installing roms for the stock hboot, cm7 won't work. From what I've seen unless your having problems with your ext the alignment patches can be more trouble than good.
Sent from my HTC Desire
Thanks a lot! I found a rom that works with the stock hboot, and it worked perfectly!
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Ok, so I'm having another issue now... The market is not working, I tap it, and it brings up a white loading screen for about half a second then disappears. I tried a reset, and I still have the same problem. Is there something I need to flash in order for it to work? The rom I'm on is cool sensation v6, and I didn't see anything there about anyone having market issues, so I'm not sure what the problem is.
Thanks again
EDIT: I notice that under accounts and sync, it says that sync is currently experiencing problems
EDIT EDIT: I just remembered that with my old hero, I had to first sync over 3g only, tried that, and it solved my problem.
Under Applications, find the market and try clearing the cache
A Dustman said:
I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
Click to expand...
Click to collapse
Did you create a bootable usb drive?
firepanda said:
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Click to expand...
Click to collapse
It's a bit misleading, cm7 does not refer to cyanogenmod7 but cm7 partion table.
You will usually find 2 different versions of most popular ROMs.
1. A2sd
apps2sd, usually A2sd+. This requires the stock partion table. You do not need to be S-off to flash these ROMs
2. CM7
This refers to the CM7 partion table (custom Hboot). To repartion your nand you need to be S-off. These ROMs are data++ ROMs.
So, no you do not need to be S-off to flash custom ROMs, you do need to be S-off to resize your partion tables. More info in this thread:
This explains Data++ versus A2SD very well:
http://forum.xda-developers.com/showthread.php?p=14615477#post14615477
So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
<-------- new user here. cant post links thanks
iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens
Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.