Related
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 :]
Hey everyone,
Just hope to make things a bit easier for all fellow aussies trying to install Cyanogen 7 on there Telstra Defy. Links and attachments at the bottom.
First thing is, so far as i can tell, 2nd-init does not run Clockwork recovery properly from the telstra stock SBF. On this ROM you will probably get the "unable to mount SDcard" error.
Also do NOT install clockwork recovery during any part of this, it comes with
2nd-init and does not need to be installed seperately (can cause problems if you do)
This is the series of steps I took to get it working.
1. Copy Defy-Cyanomod 7 Beta and Google Apps onto SDcard
2. Root phone with SuperOneClick 1.7 (1.8 doesnt seem to work)
3. Install 2nd-init (App is on market or below)
4. Reboot phone twice
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
7. Let the phone cycle through 2 complete loops.
(CM7 seems more stable once I did this)
8. On the third cycle enter 2nd-init (Volume Down when blue light is on)
9. Enter custom recovery from 2nd-init
10. WIPE Data/Cache
11. Install Defy-Cyanogen 7 from SDcard
12. Reboot phone and let CM7 load up
13. Reboot again and enter 2nd-init+custom recovery and install Google
Apps from SDcard
14. Enjoy some CM7 goodness
Thanks to everyone that made these things possible.
Links
Defy-Cyanogen 7
Latest Google Apps
http://forum.xda-developers.com/showthread.php?t=1033654
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/
I'm running cm7 on my telstra,defy. At this stage no problems, only thing was i had already flashed a non-downgradable sbf. But for warranty purposes i can still go back to telstra by flashing a fixed telegraph Sgt and restoring with stock telegraph nandroid backup.
Sent from my MB525 using XDA App
Can you post a picture of the "About Phone" screen after restoring stock from non-downgradeable??
This is my second defy and Telstra wouldnt replace my first one because i didnt have the stock ROM. They can tell if its correct or not.
That's what I was thinking, my about screen after going back to the fixed sbf is not the telstra one.
Sent from my MB525 using XDA App
I will when I get a chance, don't suppose anyone could post an about screenshot of the stock telstra one.
Sent from my MB525 using XDA App
I suppose it depends on which tech you get at telstra, some will report it, others will just fix it.
I bricked mine while trying to produce a bufer overflow and divide by zero in the locked bootloader. Was getting some results until it bricked
This is what my about screen has after restoring nandroid and flashing fixed Telstra sbf.
System version: Blur_Version.2.26.0.MB525.Telstra.en.AU
Model Number: MB525
Firmware version: 2.1-update1
Baseband version: EPU93ST2_U_03.03.00
Kernel version: 2.6.29
[email protected] #1
BPFlex version: USAJRDNEMARAB1BTEL02A.OR
APFlex version: GAS_ASIA_USAJORDANTELSTRA_P033
Build number: JRNEM_U3_2.26.0
I would be intetested so see what a stock Telstra one says.
For now I've returned to Beta3 CM7. I had basically done the same as you to install, only difference is I used this fixed sbf, 3.4.2_155-002_DEBLUR
Cheers
I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen
Thanks, I think the main one that will be different is the kernel version.
Sent from my MB525 using XDA App
Help...
The rom is perfect, very fast, so far so stable. Only
I noticed 2 bugs so far. 1. The camera's zoom, but that nothing
affects. 2. Skype does not connect here, / does anyone know how to solve
this? Put username and password, starts to connect, it restarts.
Someone managed to solve this problem?
CM7 Beta 4.1
Congratulations Quarx
Thanks
Hey, first of all thanks heaps for making this guide, thanks to you CM7 is finally running on my Defy. I have one problem though and just wanted to see if anyone else did: I can't play youtube on my Defy at all (through the app or m.youtube.com).
Is everyone else having this issue?
*Edit* I've seen a lot of forum posts from mid-last year relating to this, is this issue still unresolved or could this be a bug in the Defy CM7 port?
I've discovered that it will play youtube (both wifi and 3G) but it will only play HQ videos... While inconvenient, I can work with that
Thanks for the how-to+
Dazmonic said:
3. Install 2nd-init (App is on market or below)
Click to expand...
Click to collapse
For the idiots like me out there installing 2nd-init from the market isnt enough you have to run the file aswell by installing it from inside the 2nd-init program itself, i needed to reset my phone after using super one click for 2nd-init to be granted "superuser status" so it would run properly.
Also once you've chosen the cryogen mod file from the bootloader you can then go back to install the google apps file.
After stuffing up the 2nd init program I needed to reflash the origional telstra files, then repeat the guide.
All seems good now, and thanks alot for the guide. I'm sure i would have really botched it up with out it.
Dazmonic said:
I'll be changing mine back soon to get some things off my backup.
When i do i'll post up what it has on the "About Phone" screen
Click to expand...
Click to collapse
Have you changed back yet?
Sent from my MB525 using XDA App
hj all !
can u give me link download room fix sbf of KOREA ? i can't download it on 4share,because it's emty..
thanks bro
Dazmonic said:
5. Use RSD Lite and flash the Official Froyo Korean v3.4.2-74 fixed SBF
(This ROM allows you to downgrade back to the stock Telstra ROM and also
allows you to install CM7 from 2nd-init+custom recovery)
6. Reboot phone (2nd-init will still be installed after this SBF is flashed)
Your phone will now go into a Motorola boot loop. (this is ok)
Click to expand...
Click to collapse
My Defy is in the post and I will try install Cyanogen when I get it, however I would also like to try a blur free Froyo Rom so I was planning on installing the Nordic fixed ROM in step 5. and having a play with it before continuing the process. Is this possible or will I get a bootloop like you mention in step 6? Is the Froyo ROM used in step 5. useable or not?
Dazmonic said:
Korean 3.4-74 Fixed SBF
http://defy-sbf.4shared.com/
Click to expand...
Click to collapse
Has anyone got a copy of this SFB they could upload somewhere? It looks like all 4shared data has been pulled... see the updated 1st post here: http://forum.xda-developers.com/showthread.php?t=966537
I'd love to get a copy of this SFB so I can do these instructions by the book...
Thanks
Is there another SBF we could use besides the korean one? Does it mean if we use another SBF then we won't be able to flash back to the default telstra one?
****, Telstra are actually checking firmware versions before repairing known issues like the earpiece?
I flashed the China Froyo ROM from ages ago. Probably not downgrade-able huh. Does the upgrade to CM7 process change if you're already on Froyo?
Official 2.2, looking for some CM7 goodness
Hi guys,
I found this page to be a godsend, detailing exactly what i want for my device.
problem is now that Tesltra have updated to 2.2 and the links to the Korean fixed file seem to have all been nuked, im not sure what to do, im a super noob (yes i watched the intro video
I have rooted and flashed CM7 on my desire and want it on my Defy!
so if someone could kindly explain what substitutions (if any) are needed or a link to the files required as from what i understand, if you flash to an official 2.2rom larger then 50MB then you cant downgrade to factory ?
TLR Have Telstra Defy with Telstra 2.2 want CM7 - Halp please
Whatever I try, using System Recovery/Clockwork Recovery, when I boot up the phone it's still UK 3.4.3-11 Froyo, but now with a red motorola logo (Nordic firmwire I flashed I suppose) .
When wiping in recovery I get these errors: "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!".
I've create a FAT (should this be FAT32?), Ext2 and Linux Swap partition on my SD Card.
My original aim was to install CM7 from Quarx. Here's what I did:
Stock Defy UK (Other than root)
Used clockwork recovery to wipe and update to CM7
Booted fine (CM7/2.3), tried to then install gapps as an update.zip, then got stuck on boot at "M" screen on every boot
Used RSD lite to flash 3.4.3-11 UK with Blur
Superoneclick etc., tried to install CM7 again, had no effect
Used RSD lite to flash 3.4.2_177 Nordic - comes up with red logo, but hasn't updated to the actual blurless froyo
Tried again to install CM7, had no effect, still have the 2 errors on wiping
I've also found that when using stock recovery, it no longer does anything when I press the bottom right of the screen, it just stays at the green robot screen, I have to remove the battery.
I did get an app2sd error, which was why I partitioned the SD card using Clockwork recovery (bad move?), I then did it on my PC instead with an SD card adapter.
The phone's not bricked, since I've got a working 2.2 rom, however I've no clue what I've done to make it like it is now, and I can't install CM7 using clockwork recovery and the default recovery doesn't work.
I think fixing those errors might do the trick? Any help would be appreciated.
I am also not able to install quarx rom, tried several times it does not boot and I had to reflash the sbf to get the phone working. Btw I do no have sd partition.
What I did was from cloclwork I tried restore, shall it be install from zip. No idea why I cannot get it running. I have nordic 005 at the moment
Sent from my MB525 using XDA App
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
[] AL [] said:
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
Click to expand...
Click to collapse
I did in fact read around before I started, obviously in the wrong places or not enough. I've been pretty naive but all the guides I saw recommended that recovery, I must have missed the posts about 2ndinit (which sounds a lot easier). In fact I hardly read the actual CM7 thread since it's around 190 pages long.
It's interesting you noted superoneclick as the first time it worked and I used z4root.
I think for now I'll just use what I've got, which is ultimately better than what I started with (2.1), it's just a bit worrying as those errors I'm getting seem to suggest I've messed up the internal storage; and the default recovery won't work.
Probably installing a beta CM7 wasn't the best idea anyway since I'm very new to this.
Thanks al
I tried with cw recovery only. Tonight will try with 2ndinit. my sys info nordic 177_005 will I be able to get beta4 straight installing the zip
Sent from my MB525 using XDA App
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
binodnepal said:
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Have you read this one:
http://forum.xda-developers.com/showthread.php?t=1043420
and for the recovery:
http://forum.xda-developers.com/showthread.php?t=1032212
Other than that, I will leave it to others to guide you on this...they'll do a better job than I would.
Sorry if I sound/ed rude in my post above...but was before 1st coffee of the day
Last note: on my side, I'm waiting (more or less) patiently...
As seen here http://forum.xda-developers.com/showthread.php?t=1033654&highlight=CM7
CyanogenMod 7 for Motorola Defy
Status Beta4:
Works:Wifi, SD-Card, 3D, Auto-Brightness, LED, Photo Camera with Flash, Video Camera(H264), GSM/3G, Bluetooth +Headset + HID, Sensors, GPS(have bugs)
Not works: aGPS, FM-radio, 720p & WVGA Recording.
BugList:
- some people say that they have wifi problems <---
- DroidWall/Iptables - not work <--- <--- <---
====>>>> So I will wait for that "tiny detail" [DroidWall/IP Tables] to get fixed before testing out any CM7 on my phone.
I like DroidWall apk and I also like to have a relative control on which app can access the internet...
Some of my apks 'might' not be so 'official' [..let say] and who knows what kind of party they're having in my phone....
I got it working and its quite fast. GPS works for me. Camera photo works but not the video. Will test other later. Quadrant score is very high not sure if it is correct. I got 2200
Sent from my MB525 using XDA App
Anyone having issues with music player stopping after few songs in cm7 beta4
Sent from my MB525 using XDA App
So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!
Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App
i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...
Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App
I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.
You can also try wiping /system and /boot.
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)
wow... what a bummer. thanks for the help anyway, it's much appreciated.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium
I'll try it again to verify the code, I'm pretty sure it was "170"
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had
sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468
This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App
=D
Sent from sweet snacks off tapatalk.
OK, here it goes.
I have a R800x CDMA Verizon Xperia Play
I had bootloader unlocked successfully by alejandrissimo.
I am rooted.
Today I decided to try the MIUI rom for CDMA.
It required custom kernel, and recommended Kieren's darkforest kernel.
I installed that kernel via fastboot with no problems.
Upon turning on phone, i get a page that says Sony, then I get ANDROID page.
Then it just stays on ANDROID. I can tell that it is not frozen because I can see the waving lines going across.
SO, I decided to just go back to stock kernel then try again.
BUT, I cannot get into fastboot!!
I hold search while connecting usb, and the led blinks blue once, then continues with boot.
I am at a loss.
I Can get into CWM.
Please Help!
Edit: I just noticed that after holding search then plugging in USB, the light blinks blue once. Then about 25 seconds later, the light turns solid blue for about 3 seconds. Then just to orange for charging. During this time, I can not get fastboot to recognize device, nor does my computer recognize any devices.
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
netizenmt said:
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
Click to expand...
Click to collapse
ok, small problem with that.
when I click to install flashtool, it tells me that it is not available for my region (Central USA).
I do have a nandroid and titanium backups made just before flashing.
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
still stuck
netizenmt said:
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
Click to expand...
Click to collapse
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
zeeky120 said:
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
Click to expand...
Click to collapse
Yeah, that seems to be the wrong boot.img. It should be called boot-v2.img.
EDIT: WOW - I just reread your post after posting mine and realized I pointed you to the same spot!
Try this ROM which is a version of CM9 that Chevyowner got working for our R800x. I know it works because I'm using it. http://www.mediafire.com/?1xnh54i6lvnnh73
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
zeeky120 said:
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
Click to expand...
Click to collapse
just an fyi, you can name kernels whatever you feel like (I'm not sure about spaces, I use linux, so I never have spaces in names anyways )
Sent from my R800x using Tapatalk
Flashing now
OK, I just downloaded and flashed the ROM about 3 minutes ago.
I cleared everything just like you told me to.
It installed with no errors.
You may be right about long boot times for first boot, otherwise I have a really bad kernel.
It has just sat on Sony screen for the past 10 minutes.
It hasn't even went on to the android page that I got before.
Hoping that it will Work.
Assuming that it doesn't, what would be my best next move?
Can I flash a kernel (Such as doom_lord's CDMA Kernel) via clockwork?
I think I saw a video about it for the Samsung fascinate, however I seem to recall something about needing an s2 file or something??
I will update as soon as I get something. (hopefully good news)
Update: It has been about 20 minutes now and still on Sony screen.
Now it has been 30, im starting to get worried. Should I plug in? Should I just let it be? Should I let it die? Should I battery pull?
Major Edit: I got impatient and just battery pulled. I then tried to get into CWM, but failed. THen I got a bright Idea, why not try fastboot with the new rom. IT WORKED. I WILL NOW TRY TO FLASH A NEW KERNEL AND SEE IF THAT HELPS.
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
chevyowner said:
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
Click to expand...
Click to collapse
is this your kernel, or someone else's? If it's yours/you have a working copy, could you post an md5 so the op can double check it?
Sent from my R800x using Tapatalk
nope not my kernel, and i doubt i have an original working copy as i added 2 lines so i could mount my sdext partition.
Finally!
OK, I am now back up and running.
I went through every kernel and rom for CDMA play, and got nowhere.
I ended up getting Doom's kernel to run. It worked, and booted to android... Then stayed at android.
Then I decided to flash my nandroid i made, and am now working on stock rom W/ DoomKernel.
The ROM seems to be lagging a lot.
Since everything is *working* now, what kernel/ROM combo can anyone verify working for the Play R800x CDMA.
I would really like CM9 or ICS based roms.
Thanks for your help getting me out of this mess!!
EDIT: Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
If you're using keiran (darkforest) cm9 kernel the md5sum for it should be: 74a5be2bf95322b8c45780d9daeda4fa
Sent from my R800x using Tapatalk
zeeky120 said:
Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
Click to expand...
Click to collapse
This site has some of the stock FTFs, just extract the kernel.sin from the R800x one http://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html
kernel.sin: http://www.mediafire.com/?e29j13d9wpgdvoj
md5sum: 45116201967408d70895ef63c500ed1e
@zeeky120 - I'm sorry you're having so many problems. For me when everything seemed hosed, I started over by using Flashtool and flashing the ftf file I gave you links for. Then once it came back up as stock, I started again from scratch. Depending on what your goals are, you need to flash the proper kernel for that. Then get into CWM. Clear DATA, CACHE, DALVIK CACHE before you do anything else. Then load via zip file the rom you want to install, making sure it matches the kernel you loaded. And, whether necessary or not, I always wipe the big 3 again, just in case. (Call me paranoid, but it helps! )
Ok now up and running on stock everything working great just like out of box. The only thing I have done so far is to root. I want to do it right this time. I would like to flash cm9 based miui for r 800x. Could anyone provide detailed step by step instructions and links for download. Thanks in advance.
Sent from my R800x using xda premium
Closing Notes
This thread has reached its end, because my problem has been fully solved. Advice to future users, always clear the big three, and when in doubt: use flashtool to reboot the ftf. Right now I am up and running on CM9 (use the link in Chevy's signature to download. I can verify that it works great on CDMA. (faster download speeds than stock!!!) Thanks for everyone for all of their help, and I hope to be contributing to development in the near future.