Related
Hi there,
Today I decided to root my HTC Desire 'Android 2.2 Stock ROM' phone with unrevoked 3 (latest), all went well and was sucessfully accomplished. I was able to use the phone normally, however the problem persisted when I needed to restart my phone, which then I was unable to fully boot as the Startup keeps looping.
The Recovery console that came with unrevoked is ClockworkMod Recovery. Please I ask help and assistance int what to do, note: I do not want to flash/change my rom just fix it so it boots up.
The phone has been flashed without S-OFF.
Thank you!
If you haven no nandroid backup from right after rooting I don't think there is a lot that can be done without flashing a new rom, if you knew what caused the boot loop you might be able to fix it trough recovery and adb. If not, I think, your best bet is to flash the prerooted stock rom without wiping, that way you might no lose any personal data.
Sent from my HTC Desire using XDA App
backup your sdcard with a card reader. boot in recovery and try to wipe everything(data. android secure,cache dalvik cache etc) boot normally.
Deeco7 said:
Hi there,
Today I decided to root my HTC Desire 'Android 2.2 Stock ROM' phone with unrevoked 3 (latest), all went well and was sucessfully accomplished. I was able to use the phone normally, however the problem persisted when I needed to restart my phone, which then I was unable to fully boot as the Startup keeps looping.
The Recovery console that came with unrevoked is ClockworkMod Recovery. Please I ask help and assistance int what to do, note: I do not want to flash/change my rom just fix it so it boots up.
The phone has been flashed without S-OFF.
Thank you!
Click to expand...
Click to collapse
if you can still get into recovery now, then you could do a nand backup then a wipe then restore the backup.
it might work...
mariosraptor said:
backup your sdcard with a card reader. boot in recovery and try to wipe everything(data. android secure,cache dalvik cache etc) boot normally.
Click to expand...
Click to collapse
I hadn't made any backup files using 'nandroid' or other, will this still work what your saying and which recovery should I use, ClockworkMod?
Thank you.
yep, boot into clockworkmod if you can and run a backup.
once that is complete, wipe everything - its in the options in the menu.
then restore the backup you've just made.
let us know how you get on
mikep99 said:
yep, boot into clockworkmod if you can and run a backup.
once that is complete, wipe everything - its in the options in the menu.
then restore the backup you've just made.
let us know how you get on
Click to expand...
Click to collapse
Done all steps metioned, however, now I my boot screen is stuck with no loops. Please help.
You can´t fix this. If you backup your rom, wipe everything and restore it again. Just puts everything back in its previous state.
Just wipe everything and flash a rom of your choice. No harm done, nothing bad, nothing breaking down. Only thing you need to do is set up your stuff again.
Use appbrain next time to restore your installed apps and entering your google account should recover your contacts.
prodygee said:
You can´t fix this. If you backup your rom, wipe everything and restore it again. Just puts everything back in its previous state.
Click to expand...
Click to collapse
I though this might be the case.
prodygee said:
Just wipe everything and flash a rom of your choice. No harm done, nothing bad, nothing breaking down. Only thing you need to do is set up your stuff again.
Click to expand...
Click to collapse
As I have metioned I have a Stock Branded ROM and don't want to reflash my device if it's avoidable.
prodygee said:
Use appbrain next time to restore your installed apps and entering your google account should recover your contacts.
Click to expand...
Click to collapse
I am not worried about the apps or contacts as they have been backed up before.
EDIT: Oh I also want to know, If I flash my phone to a 2.1 STOCK ROM will I be able to update to 2.2 using the inboard update feature normally and will by any stage the flashing of the ROM change my IMEI?
I want to be able return the phone to HTC under warranty.
Please tell me if there is other ways in fixing this problem without flashing a new ROM. If not, What ROM would you recommend?
Many Thanks.
Which rom were you on? Did you take the details before now.
Also, who is it branded to?
Sent from my HTC Desire using XDA App
mikep99 said:
Which rom were you on? Did you take the details before now.
Also, who is it branded to?
Click to expand...
Click to collapse
Code:
Android Version:
2.2
Baseband version:
32.49.00.32U_5.11.05.27
Kernal version
2.6.32.15-gd96f2c0
[email protected] #1
Build number:
2.12.110.4 CL274424 release-keys
Software number:
2.12.110.4
Browser version
WebKit 3.1
Branded to: T-Mobile UK
Ok,
It looks like you may have to flash an RUU. There are a couple available which you can find on shipped-roms.com
If you do decide on this route, make sure you choose a TMO UK one. You will wipe your contacts etc.
Download the RUU, start your phone in fastboot,connect to PC and run the RUU.
You may then have to check for updates on your phone.
Sent from my HTC Desire using XDA App
Thanks, just a few questions...
1) Will my IMEI be affected?
2) If I flash this ROM, will my warranty be still valid or undetected?
3) Is there high risk in flashing using Fast Boot method?
4) Any guide for beginners?
Cheers.
You 'should' be ok but obviously I can't guarantee it 100%.
The rom you end up with will be tmobile so your warranty shouldn't be affected.
I suppose there's a risk with all of this, flashing, rooting etc..
But you don't have a phone that boots at the moment...
I've flashed an RUU before and its been fine.....
Your call I suppose....
Sent from my HTC Desire using XDA App
IMEI wont be affected.
Just follow the guide above.
Sent from my HTC Desire using XDA App
I just found out that my ROM is not on available on the Shipped-Roms.com website. There are TMO version of Android 1.15 and 1.25 and there is one 2.12.112.1 which is a australian version of the Rom.
Do you by any change have atleast the 2.1 ROM for T-Mobile or anyone else? I don't think I should flash my device with the Aussie version.
No, you're right there.
Hopefully, one of the experts on roms, EddyOS, will pick up on this and advise which ruu to use.
Sorry I can't be of further help.
Don't worry tho, your phone will be brought back to life
Sent from my HTC Desire using XDA App
Thank you so much for your time and assistance, Much Appreciated.
To Developers(Experts): Please I am urging someone to please help me with this problem by posting a TMO UK ROM on Android 2.1 or above.
Thank you
Hi, I have a desire that is stuck in bootloop, I can access fastboot and fastboot on my linux box can talk to it. ADB will show it as offline in recovery mode. how can I flash a new rom or get it out of the bootloop? S-on & hboot0.93.0001.
Any help would be great as I have been searchin this forum and trying everything!!
Thanks
What happened to make it boot loop? Were you changing something?
Rooted?Can you get into recovery?
Tried wiping cache / dalvik cache?
Sent from my HTC Desire using Tapatalk
u need and RUU to restore back to factory..
make sure you get the right 1
Hi ... i have same problem wih my desire .... i instaled CyanogenMod-7-02212011-NIGHTLY-Desire .... ma phone stuck in bootloop i cant aces recovery anything ... when i answer a call it reset .... when i unlock my screan my phone reset .... do not now what to do ... i wiped cache / dalvik cache and for some time is ok and again the same problem
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031dRaDIO-5.11.05.27
Baseband version 32.49.00.32U_5.11.05.27
Kernel 2.6.37-cyanogenmod-gbbc25dd
[email protected]#1
Did you do a full wipe before flashing CM7? If not, try a full wipe and reflash CM7.
I'm using CM7 RC1 currently with no problems, did RC1 work for you rather than the nightlies?
Sent from my HTC Desire using Tapatalk
How do I know which one is the right one? the desire was originally on orange. I think I have a working goldcard as I managed to use a stock generic ruu. however it now gives me a 170 error on the windows machine. is it possible to flash from linux using fastboot?
it was rooted but my cm recovery has gone but i can get into recovery. I may have accepted an ota update...
mikep99 said:
Did you do a full wipe before flashing CM7? If not, try a full wipe and reflash CM7.
I'm using CM7 RC1 currently with no problems, did RC1 work for you rather than the nightlies?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Full wipe ... you think wipe data/factory reset, yes i do that
also i wipe cache partition, wipe dalvik cache and then install this mod ...
When i answer a cal thets ok ... but when put phone on ear when activate sensor thet turn of phone screan then phone reset it self and loop-reset in bootloader for some thime .... i can not go undet recovery meny ffor a while .... when reboot 7-8 times i hold vol down all the time and barely go in recovery ... wipe data and phone go on
I try CM7 RC1 to reflash ... one more time ... current mod is cm_bravo_full-5.zip (bravo nightly) are u using update-cm-7.0.0-RC1-Desire-signed.zip (bravo rc) this package thanks a lot
gezza77 said:
How do I know which one is the right one? the desire was originally on orange. I think I have a working goldcard as I managed to use a stock generic ruu. however it now gives me a 170 error on the windows machine. is it possible to flash from linux using fastboot?
it was rooted but my cm recovery has gone but i can get into recovery. I may have accepted an ota update...
Click to expand...
Click to collapse
Did u try shipped-roms.com/shipped/Bravo/OTA_Bravrange_CH-FR_2.22.71.2-1.19.72.3_P_release8xcr7nx2a68060l7.zip ....
Me only work RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release ... try this froyo and after that try orange or update on wi fi
gezza77 said:
How do I know which one is the right one? the desire was originally on orange. I think I have a working goldcard as I managed to use a stock generic ruu. however it now gives me a 170 error on the windows machine. is it possible to flash from linux using fastboot?
it was rooted but my cm recovery has gone but i can get into recovery. I may have accepted an ota update...
Click to expand...
Click to collapse
Right ok, so you applied an OTA to a rooted phone. Try downloading the 2.29.405.5 ruu from www.shipped-roms.com and run that with the goldcard in.
Sent from my HTC Desire using Tapatalk
vido89 said:
Full wipe ... you think wipe data/factory reset, yes i do that
also i wipe cache partition, wipe dalvik cache and then install this mod ...
When i answer a cal thets ok ... but when put phone on ear when activate sensor thet turn of phone screan then phone reset it self and loop-reset in bootloader for some thime .... i can not go undet recovery meny ffor a while .... when reboot 7-8 times i hold vol down all the time and barely go in recovery ... wipe data and phone go on
I try CM7 RC1 to reflash ... one more time ... current mod is cm_bravo_full-5.zip (bravo nightly) are u using update-cm-7.0.0-RC1-Desire-signed.zip (bravo rc) this package thanks a lot
Click to expand...
Click to collapse
Yes, that's the one I'm using.
Sent from my HTC Desire using Tapatalk
cool will try those, with the orange one, do i just rename to update.zip and go to recovery? i have tried with other roms but when i apply update.zip i get a load of file not found errors..? thanks for your help
The Orange one is just an OTA.
What rom are you currently on?
I wouldn't try applying the orange ota after flashing the WWE RUU
Sent from my HTC Desire using Tapatalk
not sure, i was on a froyo leedroid or something but after it went west I tried a few but only one worked not sure which one. it still bootlooped afterwards.. i am going to try the 2.29.405. Thanks
Keep getting 170 error with ruu? strange because if i type "fastboot devices" it shows my phone? any ideas?
Have you googled the error or do you have anymore info?
Phone should be in fastboot mode.
Try turning off any antivirus etc...
Sent from my HTC Desire using Tapatalk
yep its the usb error which is strange, i can see the phone using fastboot, the phone shows in device manager as android bootloader interface. I have disabled antivirus and am about to hit it with a lump hammer..
Are u using win 7 .... try run as admin that .exe ..... or download RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release and try .... it must work
Try reinstalling htc sync if you have it installed. USB debugging enabled on the phone?
Sent from my HTC Desire using Tapatalk
I was just going to try reinstalling htc sync.. Thanks for the help
usb debugging was on but not sure as its boot looping
result!! it has come back to life. reinstalling htc sync sorted the 170 error! ruu flashed successfully.
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. was the one i had and caused the problem.
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00. worked
Thanks for the replys and help
After installing Cyanogenmod 9 on the One X I started to notice extremely poor signal, Mobile and Wi-Fi. Also the phone would crash and randomly reboot when doing simple tasks such as opening messages etc.
Upon trying to get into recovery to install a different rom, the phone now flashes on a black screen and restarts the phone.
To try and solve this issue, I unrooted the phone and restored to stock recovery.
I then re-rooted the phone and installed clockworkmod recovery again.
I can now access clockworkmod recovery although it seems to have no effect. Installations of any rom fail and cyanogenmod always pops straight back up again after rebooting.
Has anyone else had this issue?
Does anyone have a way to fix this? Possibly to force the phone completely back to stock?
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Kamiil29 said:
You can try first "SuperWipe" (from ARHD's thread) and flash a new ROM (don't forget boot.img before...)
Click to expand...
Click to collapse
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
AndyB said:
Thanks for your quick reply, how do I do the super wipe? and where can I download the One X stock roms from?
Click to expand...
Click to collapse
Unfortunately I can't help you with SuperWipe, but you can find the HOX stock ROMs here.
Sent from my HTC One X using Tapatalk 2
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
AndyB said:
Ran superwipe and tried to install the stock rom. Superwipe ran fine and did the job, although the rom installation still failed as it was doing before and I am now stuck with a htc bootloop. The device won't boot into recovery either. Any ideas anyone?
Click to expand...
Click to collapse
Did you try holding down the Power and Volume Down buttons while in the bootloop to enter the bootloader? Hold them down until the lights start to flash, the screen goes off and then the bootloader comes up.
If you can get into recovery with that, factory reset, clear cache and dalvik cache (under advanced) then try install the ROM.
I'm not the best person to be helping, but I hope that works for you!
I had a similar problem once where the phone would just sit on the HTC One X screen, and trying to go into recovery just put the phone back to the HTC screen. I fixed it by flashing the boot.img, factory reseting, clearing out caches and installing the ROM again. No problems since.
I'm afraid if this doesn't work, I may have to abandon you and let someone else take over, as I'm no expert, but I'll see what I can do to help.
Edit: sorry, it is 2AM here and I need some rest for an early start at 6AM. I will check up on this thread when I wake.
Sent from my HTC One X using Tapatalk 2
FIXED!!!
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
AndyB said:
To anyone else having this problem, I downloaded ARHD Flashboot 7.0.0 and ARHD 7.0.0, followed the instructions on what to do and installed ARHD successfully.
This has now completely gotten rid of Cyanogenmod and seems to have got clockworkmod working again.
It's probably work using the "Fix Permissions" option in ROM manager before you attempt this as I believe that is what got clockworkmod working and able to install files again. (I may be wrong)
Thankyou for everyone's assistance.
Click to expand...
Click to collapse
Glad you got if working
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
Help, I will describe the following and any help I would love. I have the PRIMOC VM usa HTC ONE V.
Using Hasoon2000's All in one toolkit I have successfully Unlocked my phone, flashed TWRP recover 2.4.4, got root, and made a backup.
I then continue on to wipe cache and system and Factory reset to prepare to install ANY ROM. When I try to install the rom every time it just says Error in /sdcard/...[wherever rom is] (Status 1) FAILED
So then I proceed to restore my backup (this is why you always make a backup) and that works fine
Does the "(Status 1)" mean anything important?
I thought this was happening because I was running the newer radio so I used the RUU tool and now am using the good radio (not 0928) But this did not fix anything. This same thing happens over again. I have checked to make sure and I do have full root privileges.
I then tried to flash boot.img first and jmz kernel flashed successfully, but no rom will flash.
Why will NO ROM install?
I feel like I am missing something obvious but can't figure it out.
Also, whenever I do the factory restore it goes through all the process then fails when trying to wipe sd:ext , but my card is not partitioned. <I didn't know if that would be any help>
I am not a complete newb at all of this (running lg optimus for years- just new to the htc methods)
NEED Help please...
Can anyone help me out with this?
I have not made any progress since yesterday. I am successful at flashing kernels, I have flashed the boot.img of the sic kernel, but on both kernels I have no WiFi with the stock ROM.
So I either need to find the stock boot.img or have help flashing a ROM that fails everytime.
When every instruction says "Extract ROM" that is only to pull out the boot.img right, we don't flash an extracted package you flash exactly what you downloaded right?
sdxben said:
Help, I will describe the following and any help I would love. I have the PRIMOC VM usa HTC ONE V.
Using Hasoon2000's All in one toolkit I have successfully Unlocked my phone, flashed TWRP recover 2.4.4, got root, and made a backup.
I then continue on to wipe cache and system and Factory reset to prepare to install ANY ROM. When I try to install the rom every time it just says Error in /sdcard/...[wherever rom is] (Status 1) FAILED
So then I proceed to restore my backup (this is why you always make a backup) and that works fine
Does the "(Status 1)" mean anything important?
I thought this was happening because I was running the newer radio so I used the RUU tool and now am using the good radio (not 0928) But this did not fix anything. This same thing happens over again. I have checked to make sure and I do have full root privileges.
I then tried to flash boot.img first and jmz kernel flashed successfully, but no rom will flash.
Why will NO ROM install?
I feel like I am missing something obvious but can't figure it out.
Also, whenever I do the factory restore it goes through all the process then fails when trying to wipe sd:ext , but my card is not partitioned. <I didn't know if that would be any help>
I am not a complete newb at all of this (running lg optimus for years- just new to the htc methods)
Click to expand...
Click to collapse
When u flash sickkernel make sure you also install the zip through your recovery that should fix your WiFi problems and which recovery are you using ? Twrp or cwm?
Sent from my HTC One V using xda app-developers app
Obeezy562 said:
When u flash sickkernel make sure you also install the zip through your recovery that should fix your WiFi problems and which recovery are you using ? Twrp or cwm?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Hi Obeezy562,
my advice is to use the recovery program CMW or TWRP to re-format your external SD card. Then follow the normal instrutions and install the rom from zip using your recovery program. If you still have the same issue just let me know and I'll ponder longer.
regards
mcgi5sr2 said:
Hi Obeezy562,
my advice is to use the recovery program CMW or TWRP to re-format your external SD card. Then follow the normal instrutions and install the rom from zip using your recovery program. If you still have the same issue just let me know and I'll ponder longer.
regards
Click to expand...
Click to collapse
I'm not the one with the issue is sdxben lol I was just helping him but you are correct. I also recommend people cwm.
Sent from my HTC One V using xda app-developers app
Obeezy562 said:
I'm not the one with the issue is sdxben lol I was just helping him but you are correct. I also recommend people cwm.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Ok, so tonight I will reformat my sdcard with TWRP then try to install the ROM. I tried the CWM recovery, but it was not touch based and did not respond to the power button as the OK, only the volume rocker worked.
I will try CWM recovery if someone can provide a link to the latest one, perhaps I was using an old one.
Twrp 2.4.4 I've also had issues with flashing some roms then downgraded to Twrp 2.2.0 and everything has been well since
sentfromtx
I can add that twrp 2.4 does have some issues. I use a cwm I found on google somewhere and if works just fine.
Sent from my HTC One V
http://forum.xda-developers.com/showthread.php?t=1871243
try this one out, should set up everything fine. Let me know if you need any further help