Related
Hi guys,
I'm an admitted noob at flashing android phones, I followed AlexDP's guide to rooting the Telus DHD (http://forum.xda-developers.com/showthread.php?t=954997) everything went smooth. So I tried to flash the Android Revolution 3.2, it seemed to install properly, but when the phone rebooted it got stuck in a boot loop. I rebooted into recovery and tried to flash RaidRoid 1.32.405.6, but I'm still stuck in a boot loop.
I understand from reading the forums that a boot loop isn't necessarily a big deal, but I'm a little unsure as to what to do to recover from it?
Can I choose wipe data/factory reset from ClockworkMod Recovery, or do I need to try another rom?
Thanks for any help.
choose wipe data in clockwork mod, then re-flash whatever rom you want.
Ok, thanks descenpet
So did that help you to get out of the boot loop?
Maybe the zip file is corrupted, try downloading it again
I was in the middle of trying to re install the PD98IMG.zip file from the downgrade process when descenpet replied. It was successful, and I am out of the bootloop, but now I'm unsure as to where that leaves me? Am I running raidroid now, or have I gone back to what I had before rooting/flashing?
Thanks guys
Just noticed I no longer have superuser, so I guess that answers my question.
Thanks again.
if you use PD98IMG.zip, it will go back to stock. only thing that could remain is radio s-off if you did it. you will have to re do everything else starting from temproot.
Thanks for your help descenpet. I'm up and running with Raidroid now. Going to do a nandroid backup and redownload Android revolution.
Thanks again, really appreciate the quick responses.
I was a newbie, and i didn't take a backup from my stock rom, and i couldn't find it at all as it was "1.29.709.12" so with help of a friend of mine we managed to install ARHD 7.1.0 instead.
and after a while i decided to install CyanogenMod9 Beta1, so i toke a CWM 5.8.4.0 recovery backup and installed it and everything was fine, then i came across an unleashed cm9 v18 which has more fixes and i installed it, but the BT was not working at all, so i managed to get back to the backed up CM9 but the same problem occurred and the BT is not working at all, it doesn't even wanna change the on/off button.
so i tried to revert to the ARHD 7.1.0 and i restored it but it loops in quietly brilliant screen, i used aa super wipe patch and i installed it again and the same behavior happening, looping and looping
now the only rom that opened up is the "IceCold build 7"
please guys advice me what shall i do, every time i clear cash, I install the proper boot.img, wipe data/factory reset, and wipe cash partition. then whats wrong with my steps? why it doesn't work?
I advise you to stop fuking about and learn before you play.... its kind of like school but its more expensive.
crsnwby said:
I advise you to stop fuking about and learn before you play.... its kind of like school but its more expensive.
Click to expand...
Click to collapse
thanks for your advise, i promise i won't play again, but what about the this situation am in? any recommendations, tweaks, that can solve my problem will be really appreciated.
i need to get back to my stock or at least to be able to install a sense custom rom like the ARHD.
please guys help, please just give me any solution for this.
Relock flash ruu for phone and start again from begining this should sort your issue out
Sent from my HTC One X using xda app-developers app
dryan433 said:
Relock flash ruu for phone and start again from begining this should sort your issue out
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
the problem is that my RUU is "1.29.709.12" which is not exists at all, it looks like my phone is the only one world wide that has this RUU
is there anyway to flash another RUU without having "ERORR: 155"?
The RUU doesn't do anything special, it just wraps it up into a nice easy to use package. There must be quite a few threads and hundreds of posts explaining how to fix this.
Off the top of my head, quite possibly wrong.
Unlock.
Flash recovery
Flash boot.img
Fastboot erase cache
Superwipe
Flash Rom
Flash modules.
Relock
Search and you'll find.
im puzzled, why didnt u full wipe every restore?
After flashing boot image, did you do fast boot erase cache
Sent from my HTC One X using Tapatalk 2
Hi All, let me start with a warning…
total Android n00b here, doing his first ROM flash on a newly rooted T-Mobile G2. I’ve read and searched a bit in the forum threads to see if I could solve this on my own, but I do need help.
VISION PVT SHIP S-OFF
HBOOT - 0.82.0000 (PC1010000)
MICROP - 0425
RADIO - 26.02.01.15_M2
eMMC - boot
Aug 20 2010, 16:51:01
This is from using the instructions in Strawmetal’s PDF guide to Downgrading from Gingerbread to Froyo and Root. I am working with a G2 phone that was set to Factory Reset before rooting, so there is no user data to backup or worry about.
1. I downloaded the Andromadus Mimicry 1.1.2 ROM image, and verified the md5 checksum on my sdcard using the AFV Legacy application. The Gapps image also was verified as well.
2. Using ROM Manager 5.0.0.8 from the Google Market, I ran Clockwork Recovery to install the Andromadus image. I left all settings on defaults and the installer ran fine.
3. When it restarted, I was left stuck at the white HTC screen for ages… the longest I left it was 20 mins. After that, I pulled the battery and restarted. Same white HTC screen.
4. I tried using Volume (+) key and Power On to get back to Clockwork Recovery, but the phone vibrated (buzzed) 3x times quickly, and the Power LED lamp pulsed an amber color. Again, yank battery, restart, same white HTC screen.
5. finally I decided to read more of the help for adb, and found the command “adb reboot-bootloader”. This let me get into the default Recovery mode, and it proceeded to find the PC10IMG.zip I still had on the sdcard from doing the Froyo downgrade. Recovery checked it out, ran it and restored the stock Froyo image and my phone did a proper restart. WHEW.
After that, I had to run adb to install the hboot recovery image file, and the busybox checksums were valid according to Strawmetal’s PDF instructions to get permanent root back after restoring the stock Froyo image.
I have done this process about 4 times, and am really good at typing inside adb now
But I’m lost…
-did I pick a ROM that doesn’t work with the G2? Other posters to the forum thread appear to be using the HTC Vision or G2.
-is ROM Manager not a good way to install a ROM?
-when I tried to get back into Recovery, what do the 3x buzzes/amber power LED mean?
-I never got to install the Gapps image; was I supposed to install that first, then the ROM image?
I imagine I did something wrong (duh!), but I can’t spot it. If someone can help me through this, I’d appreciate some advice very much.
thanks!
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Hi Nospin,
Thank you very much for your suggestions!
I will revise my root and remove Clockwork, and switch to 4EXT instead.
I appreciate the idea of "superwipe"; I will look for that as well today.
If I understand everything right...
-replace CWM with 4EXT
-place superwipe.zip, Gapps.zip and the Mimicry ROM.zip on the top level of the sdcard first.
-reboot the phone and run 4EXT recovery
-select superwipe to run first, then the ROM and then Gapps
-then restart the phone
When I used CWM before to install the ROM, it rebooted on its own before I could install Gapps. Will 4EXT let me do each install right after each other or do I have to return to 4EXT for each separate install?
regards,
motionmonk
Nospin said:
Rather than clockwork, use 4EXT recovery, much better for our device. ROM manager and clockwork have grown very iffy over the past year. Don't use rom manager to install a rom, download the zip yourself and manually install it in recovery.
Next you need to find the "superwipe+ext4.zip" floating around here, it is indispensable for FULLY wiping your phone when switching roms.
Mimicry works fine on the G2, in fact everything (except a few sense roms that need a Desire Z hboot) in the development section runs fine on the G2.
So....get the ROM, GApps for that ROM, the Superwipe zip (you will flash this right before you begin flashing the rom) on your SD card and make sure you are using 4EXT recovery (find the link in the dev section).
Make sure before you do ANYTHING you make a Nandroid backup (using your recovery).
Click to expand...
Click to collapse
Hi blk_jack,
I went back to the Mimicry page and re-read the FAQ section.
I think what I got out of it the first time was that if the ROM flash failed, it could be a corrupt ROM image. I will definitely use 4EXT to repartition before I try again with a ROM flash.
I guess I am still getting used to the terms for everything; can 4EXT do the nandroid backup? or is there a better process for setting that up?
thank you!
motionmonk
blk_jack said:
Your issue is actually addressed in the Mimicry OP, please read it first. That said, the problem is almost certainly because you're coming from GB without a full wipe. You can use 4ext to repartiton/wipe all, or you can use superwipe+ext4 as mentioned by Nospin.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes, you should be able to flash the rom and then GApps without rebooting. Give me a few and I will send you a PM with a few links....
Shot you a PM.
Thanks! I'll check it out :good:
Nospin said:
Shot you a PM.
Click to expand...
Click to collapse
Update-not working
Ok...
I re-flashed back to stock Froyo, and did a permanent root.
Installed 4ext Recovery (instead of Clockwork), and got a copy of SuperwipeG2+ext4;
I copied new checksum'd copies of Mimicry 1.1.2 ROM and GApps to my sdcard.
Booted into 4ext Recovery and installed from .zip the SuperwipeG2+ext4 file.
System, data and cache are all converted to ext4 partitions.
Wiped the system and data and cache partitions.
Installed from inside Recovery the Mimicry ROM and then the GApps archives.
No errors reported.
Upon reboot, I still get the white HTC screen. UGH.
I've left it on in that state for 30 mins... I had to yank the battery after that in shame...
I have tried to make sure that I read up on background steps, and I feel I do understand the overall process, but something is still getting in the way. I am doing this as I mentioned in an earlier post on a factory reset G2 with a clean erased SD card (has the stock Froyo image, Andromadus Mimicry ROM and GApps only). There is no SIM card installed either, wifi is off (to avoid OTA upgrade requests).
Are there other things I can try, or info I can supply that would help? I think I'm so close to getting this done... I must be overlooking something obvious.
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Hi amogil,
Just to be sure I understand, are you saying you are swapping between Andromadus and CM9 beta on your phone?
Did you flash CM9 first? and then Andromadus?
or just carrying the CM9 beta image and running Andromadus?
Sorry, I'm all sorts of confused here lol
thanks
amogil said:
I run that by rom along with Cm9 beta..... Try adding that to your boot process. Just Cm9 beta..... Other than version of crash.... That's just what I have experienced
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
It's definitely a thought, and I believe that's what amogil is telling me too...
Ya, I can try a different ROM and report back.
I guess I should go back to stock Froyo and then start from CM7.2, and if that boots, try Mimicry again?
-from the Andromadus FAQ, it says it if a different ROM is based on ICS9, you shouldn't have to wipe. But with CM7, I'd have to wipe the Dalvik cache, yes?
-since CM7 is obviously not based on ICS9, would being able to launch into that show some details I can't see at present? Just was curious.
Or, do you think it better to go stock Froyo and then the older Mimicry ROM?
Either way, I'll make sure that I use the Superwipe to set things to ext4 first.
thanks guys for the ideas,
motionmonk
Nospin said:
Ugh....it's frustrating isn't it?
Can you boot into any other rom? For example if you downloaded CM7.2? If you don't have any problems we can eliminate some possibilities.....
I had a similar problem booting into Mimicry my first time, in that I could get past the white HTC screen but after that my screen would just go black. After a couple frustrating hours what ended up working for me was downloading the older version (1.1.1 I think?) and that booted up fine . Then after letting that boot I went back into recovery and flashed 1.1.2 without wiping (I might have wiped cache and dalvik...). Everything worked great after that. Not the same problem as you, but similar.....
Click to expand...
Click to collapse
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
SUCCESS!
Woohoo!
It works!
Since I had an ICS9 ROM already in place and was planning to wipe back to stock anyways, I tried flashing the older Andromadus 1.1.0 ROM.
What a surprise and treat to see the startup animation!
After poking around for an hour inside it, I then tried Recovery to reflash to the newest 1.1.2 ROM.
YAY! It works!
OMG, having a new ROM is like having a new phone-- there are so many improvements to the UI and it's quick and speedy versus GB. Dang, I'm happy now :victory:
Observations:
1. I did notice that inside Recovery, my touchscreen was barely functional when I tried to update from 1.1.0 up to 1.1.2-- I had to use the Volume +/- and the d-pad button to make selections. After the flash, the touchscreen is as responsive as ever.
2. it's got me thinking, that there must be a setting that is expected in the v1.1.2 ROM that the v1.1.0 ROM installed. Or could something else be the issue? I mean absolutely no disrespect to the developers... but on the technical side, I'm just curious what possibilities exist that might lead to this situation.
3. backup question... when I use MyBackup Pro, I know I can make an archive of the apps I've installed, and an archive of the data (documents, music, settings). Is a nandroid backup different from that? when I see the backup/restore options inside of 4ext Recovery, what are those doing that's different from what I get from MyBackup Pro?
thanks for all the help and encouragement. I have a new ROM installed! :good:
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Oooh, a possibility. We will see if he can boot a different rom.
Whenever you switch roms (even if they are using the same Android version as a base) I suggest a full wipe. (Wipe all user data + Dalvik Cache + Cache, or just flash the superwipe zip). When upgrading the rom you are currently on (say upgrading CM Nightlies or going from Mimicry 1.1.1 to 1.1.2) you only need to really wipe cache and dalvik cache. Unless the dev states otherwise of course.
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
strawmetal said:
The boot.img should be the issue for a rom to not boot from the. Htc whitescreen. My guess is that you have a false s-off.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Thank You All!
A big shout out to:
Nospin
blk_jack
amogil
strawmetal
for taking the time out to help a total n00b stumble through his first ROM flash.
I really appreciate the points you guys made, and the help provided.
Thank you!
I hope that one day I can help someone else out with a problem and pass the kindness forward.
Yay! I have a working ROM!
motionmonk
motionmonk said:
Hi strawmetal,
It turns out that I did have s-off after all...
1. after one of the many attempts to flash the ROM image and restoring back to stock Froyo, I said that "I'm gonna start this entire process over to be sure." So I get stuck using the fre3vo tool for about 30 minutes, rebooting and trying different address ranges to find the exploit.
Never found one... oh no, what did I do to the phone now??
-then it hit me; if it can't find an exploit... then it must already been used!
2. also, I did check each time I was in bootloader that my S-OFF was there and the radio and hboot were not changing versions.
3. Hehe, and the best indication was... being able to boot up finally!
I also have your Strawmetal.CM.V6.zip on my sdcard; if the downflash (?) to the Andromadus older ROM didn't work, yours was the CM7 image I wanted to try. If it's ok, I think I want to play around inside CM9 for a bit and then try yours out after that. I don't want to overwhelm my poor brain!
thank you for your suggestion... that definitely would be something to check as well.
Click to expand...
Click to collapse
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
WOW. i just realized there is SO MUCH I need to catch up on!
I'll have to look up some of these guides later today... but the RUU is the ROM upgrade, right?
Did you ever find a reason why you got the false S-OFF flag? It's clear that the way I was looking at the failed fre3vo exploit as proof of S-OFF isn't always going to be true... but how would you separate a false S-OFF flag from lets say a wrong hboot image?
BTW, your PDF on downgrading and rooting the G2 was a godsend. Very very helpful and clear.
One of the reasons why I took so long to try rooting was that I was confused by the different methods and the replies of X not working, Y is a better way... going through your guide and the info here on xda cleared alot of things up. :good:
strawmetal said:
The bootloader can show a false s-off. I've personally experienced this. By the time "HTCDev bootloader unlock" came out i was already rooted. But as curious as I was I decided to try it out. Flashed an RUU ( my my why would I do that ) Got back s-on( guess this was false too) then I used HTCDev method to prove i'm a total noob. Then i relocked it using Nipqer's guide and followed setherio's method again. I was able to use the stock froyo, but no other rom would boot( false s-off being the culprit ). This time I ran to #g2root on freenode. Nipqer saved me.
Click to expand...
Click to collapse
At the moment it's on a bootloop with the HTC screen, although I've managed (just now) to flash CM10 which is now stuck on a loop of the CM10 Android splash screen
I'm feeling confident that this can be sorted as I can access phone through fastboot/adb and can mount the SD so all isn't lost... I'm on UK O2 HOX
Just looking for a little direction, I used to be fairly confident around the inside of my old HTC desire, but lost interest... Things are rather different with the HOX and I suspect I've maybe screwed up with some misguided bravado...
Mr Hofs has provided some excellent learning material on his responses to issues similar to mine but to no avail...
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Just looking for pointers on where to go next!
Starting to become concerned I've made a proper mess...
mathesonewan said:
I've tried a lot of things, bootloader is unlocked, flashed boot.img and recovery.img but when I flashed x.xx.206.x - O2 UK (United Kingdom) firmware.zip with hboot 1.36 it said it failed (with no information as to why)
Click to expand...
Click to collapse
Additional to this - I've been through 10-12 pages of various fixes (searched bootloop within HOX forum) that's why the above is a little vague... They've all merged into one...
1: what hboot do you have now ?
2: what recovery are you on ?
and put the phone in the recovery in the mean time. it charges the battery there
Are you flashing cm10 or cm10.1 'cause cm10 does not support hboot 1.36.
Recovery is TWRP v2.4.1
HBoot is 1.36
and I'd read that somewhere about not supporting 1.36 and I've just checked it's 10.1 I was trying to flash
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
Mr Hofs said:
Yep....and otherwise the way around ! because i helped somebody on team-V ...it didnt work the way TT described. but actually did work the other way around
in recovery a full wipe....
install the rom and gapps
adb reboot bootloader
and flash the boot.img followed by
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
mathesonewan said:
Right I'll try these out - If TTs method isn't successful is there anything I would need to be aware of inbetween these two methods? Or are both pretty much starting from scratch? (I hope you understand what I mean..?)
Click to expand...
Click to collapse
TToivanen said:
Everything sounds good to me.
Try again with my instructions:
1. Flash boot
2. Full wipe
3. Flash rom
4. Flash gapps
It should boot.
Click to expand...
Click to collapse
I've expanded on the above steps to ensure I'm completing them correctly
1. Extracted the boot.img from the firmware zip contained within the CM10.1 zip, then ran fastboot flash boot boot.img from cmd line - this completed and reported "OKAY"
2. Full wipe done using TWRP - system wipe - for good measure wiped everything else too (wasn't sure if system was a catch all for the others or not)
3. Rom Flashed using TWRP install cmd (I've assumed this is the correct way to do it...)
4. Flashed Gapps similarly
It's now past the HTC "quietly brilliant" splash (very very quiet just now...) and is stuck on the CyanogenMod splash just circling round and round...
Going to try the other method see if I have anymore luck!
OK... So haven't had any luck with either method...
When flashing the boot.img it's behaving differently to how it did before - it now triggers the phone to reboot whereas it never did before... Is that normal?
Is there any more information I can give you guys that might narrow down the issue?
Thanks in advance!
i would try a stanrd sense based rom ..... just to check its all fine, i have seen more people that didnt get it booted, why ? no clue....
did a proper wipe....factory reset,wipe caches, dalvik cache, data, system ?
then it should work !
Just downloading the stock rom just now, going to try from there... At this point in time I'll be happy to just have a working phone!
Success!
I tried going back to the stock rom but something mad happened with the recovery (i.e. it didn't work anymore) and was replaced with a graphic of a flat HOX with a sync symbol and then the sync symbol was replaced by a red cross...
So had a minor panic, realised that something wasn't right with TWRP, so flashed on CWM, then flashed the boot.img from the stock zip, and flashed the rom perfectly.
I'm tempting fate but I started this process wanting a new rom and I will finish it, but I'm glad my phone isn't bricked!
Thanks to you both for your input, your faith certainly encouraged me to not give in!
Keep up the awesome work!
Well you can always try again to install CM10.1.....again but now with cwm.
I went with viper - which has flashed successfully, but everytime I unlock the screen it comes up with a white HTC screen... haha time to start trawling the viper forum... or go for CM again!
Strange.....tho i have the idea you missed something in the wiping process ?
Funnily enough for a "low stress" option I wiped everything (CWM > advanced > wipe em all) then reflashed the boot.img from CM10.1, then flashed the rom and it's loading into CM10 but repeatedly flashes "unfortunately the process com.android.phone has stopped"
There is something funny going on if no custom roms are working no?
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
That should do it.....
ohhhhh the mounts and storage one is new to me... I'll try that now with a custom...
Meh didn't work... I'm going to reflash the stock and go to bed I think!
hey so i was wondering if there are any requirements for flashing a new 4.2.1 rom or later cos i have tried to flash cm10.1 and jelly bam correctly and remembered to erase the cache yet they still dont work i get stuck at the htc screen or the nexus logo for cm10.1 any help would be greatly appreciated. also can you diagnose a screen not working on software or is it completely hardware cos my screen is cracked but just after i rooted my phone it seems the digitiser has stopped working for some reason
What is your hboot? You need a JB Hboot (1.31+) to run 4.2 roms!
Have you wiped data/cache/dalvic before flashing the rom? Did you flash the correct boot.img?
Screen not working might be because of number of reasons m8! And since you got a cracked screen, it could be hardware fault as well..
vin4yak said:
What is your hboot? You need a JB Hboot (1.31+) to run 4.2 roms!
Have you wiped data/cache/dalvic before flashing the rom? Did you flash the correct boot.img?
Screen not working might be because of number of reasons m8! And since you got a cracked screen, it could be hardware fault as well..
Click to expand...
Click to collapse
i have done all that wiped everything and flashed the correct boot image but still not working for anything over 4.0 so far, my hboot is 1.39 cos i rooted from htc official jelly bean update so anyway if there are a million and one reasons for a broken screen might have to find a new phone anyway thanks
benny_w95 said:
i have done all that wiped everything and flashed the correct boot image but still not working for anything over 4.0 so far, my hboot is 1.39 cos i rooted from htc official jelly bean update so anyway if there are a million and one reasons for a broken screen might have to find a new phone anyway thanks
Click to expand...
Click to collapse
Ohkk! So you have the latest hboot (1.39) so you should be able to run any roms out here!! So now that things aside...
Have you wiped your cache after flashing boot.img? 'fastboot erase cache'?
Wait for 5-6 mins for the 1st boot.. it can take sometime!
vin4yak said:
Ohkk! So you have the latest hboot (1.39) so you should be able to run any roms out here!! So now that things aside...
Have you wiped your cache after flashing boot.img? 'fastboot erase cache'?
Wait for 5-6 mins for the 1st boot.. it can take sometime!
Click to expand...
Click to collapse
yep as much as my screen doesnt work i still dont understand why this doesnt work, at one point in time i left a rom all night to boot to see what would happen next morning nothing. i have been wiping the cache as well so i dont understand