The problem is after flashing the rom and rebooting my phone, when the phone tells me to insert some details like a new phone. It's just stop and reboot. How can i stop this problem and enjoy customs rom on my htc?
This always happens after flashing a new rom. You are wiping the system partition and installing the os from scratch. Every new rom flash will require you to set up the phone upon the first boot.
Edit:
Oops, sorry, I misread your post. It sounds like it's rebooting before you can set up the phone?
A couple possible issues (without knowing what you've done) :
Perhaps you didn't do a wipe before flashing the rom? Try wiping system, data, boot, cache & dalvik. Don't wipe the SD card.
Then try installing the rom again.
Depending on the rom, does it require that you flash a gapps package? This depends on the rom. If it's a stock ics rom, probably not. If it's a jellybean rom you most likely need to.
Possibly you got a bad download. Check the md5 or re-download the rom.
Did you follow all the rom instructions for flashing?
Anyway, those are a few things off the top of my head. Without knowing more detail about your current setup and what rom you are flashing, it's hard to pinpoint the exact issue.
Problem in installing a rom
Brian706 said:
This always happens after flashing a new rom. You are wiping the system partition and installing the os from scratch. Every new rom flash will require you to set up the phone upon the first boot.
Edit:
Oops, sorry, I misread your post. It sounds like it's rebooting before you can set up the phone?
A couple possible issues (without knowing what you've done) :
Perhaps you didn't do a wipe before flashing the rom? Try wiping system, data, boot, cache & dalvik. Don't wipe the SD card.
Then try installing the rom again.
Depending on the rom, does it require that you flash a gapps package? This depends on the rom. If it's a stock ics rom, probably not. If it's a jellybean rom you most likely need to.
Possibly you got a bad download. Check the md5 or re-download the rom.
Did you follow all the rom instructions for flashing?
Anyway, those are a few things off the top of my head. Without knowing more detail about your current setup and what rom you are flashing, it's hard to pinpoint the exact issue.
Click to expand...
Click to collapse
I flashed vipers sense 5.0 in my htc sensation xe with hboot 1.27.1111.
but when the installation is finished, it has to reboot.
When rebooting it remains on the screen writing HTC SENSATION XE.
And freeze.
I have tried cyanogenmod jellybean for my htc sensation xe, it started on the home screen and asked for some information and then it freezes.
Okay, this was in the Evo 3d section. Just want to be clear that I don't have any experience with your specific device.
That said, all HTC devices share some similarities. There are two major reasons why a rom won't boot on an HTC.
1.) The rom isn't compatible with your current firmware. Hboot mainly.
2.) Your device is s-on and will not allow you to flash the kernel with the rom.
There are two ways around this while s-on. Since you already flashed the rom, you can place a copy of the rom on your pc. Extract the boot.img from the rom.zip and Put it in your fastboot directory. Use the command: fastboot flash boot boot.img
As long as the rom is compatible, it should boot after flashing the boot.img (which contains the kernel).
The other method is to keep a copy of your recovery.img in your fastboot directory. Then when you want to flash a rom boot the recovery using this command: fastboot boot recovery.img
The Phone should boot into recovery and you should be able to flash the rom normally. No need to flash the boot.img separately when booting recovery this way.
One more alternative (possibly) is use 4ext recovery, if it's available for your device. http://4ext.net/
It has a feature that can be enabled called smart flash that will allow you to flash roms while s-on without the need for a pc like the two methods above.
Moved to Sensation XL forum, since it's the closes to this phone.
Related
Hi all
firstly I must give all the devs a thumbs up on their work in creating some great ICS roms, but infortunately i find the lag a little annoying so I want to go back to Gingerbread.
I still have S-on, I used HTC dev to unlock bootloader and installed clockworkmod, and currently running cooldroid rom.
Radio-3822.10.08.28_M and HBOOT - 2.00
I made a nandroid backup of my Optus GB bloatware rom but unsure of how to re-instalI...
I tried booting into clockwork recovery, and restoring backup, but phone didn't get past HTC splash screen after that, and then booted to recovery.
so i booted back into recovery and did a full format inc. delvic wipe and then restored backup, and still boots to splashcreen, switches off then boots to recovery...
i even tried extracting the boot image from optus backup and flashed that seperately using command prompt...
Am I missing a step here...
or should i just download a zip copy of the orig rom from the topic in the dev section eg:
RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085A ( but radio not the same ... )
reflashed back to cooldroid for time being.
any help would be apprieciated
Addy
That's am RUU you have to install those from a PC you cannot do them from your phone.
You could try a GB from the dev section. Nik trinity v5 is meant to be a good gb Rom ?
Sent from my HTC Incredible S using xda premium
You might want to try this sequence:
Restore nandroid from recovery
Format cache and wipe dalvik
Flash boot.img in fastboot
Nonverbose said:
You might want to try this sequence:
Restore nandroid from recovery
Format cache and wipe dalvik
Flash boot.img in fastboot
Click to expand...
Click to collapse
Yes you will have to flash the boot.img from the backup directory in Fastboot mode.
tpbklake said:
Yes you will have to flash the boot.img from the backup directory in Fastboot mode.
Click to expand...
Click to collapse
OP mentioned flashing the boot.img in command prompt already, I was just assuming that doing the full wipe before restoring the nandroid as he was doing may have flashed a cache that was causing issues with bootup so I suggested wiping it after initial restore. I haven't had a grease deal of experience with stock Rom backups so I would like to hear your thoughts about it.
@addyhash another user (n1cnak) has located the Optus sense 3 ruu which would be the same version as you had installed. I have asked in his thread if he could upload it and if all else fails it would be a better solution than the ruu you mentioned in your post ( unless you planned to go s-off)
Nonverbose said:
OP mentioned flashing the boot.img in command prompt already, I was just assuming that doing the full wipe before restoring the nandroid as he was doing may have flashed a cache that was causing issues with bootup so I suggested wiping it after initial restore. I haven't had a grease deal of experience with stock Rom backups so I would like to hear your thoughts about it.
@addyhash another user (n1cnak) has located the Optus sense 3 ruu which would be the same version as you had installed. I have asked in his thread if he could upload it and if all else fails it would be a better solution than the ruu you mentioned in your post ( unless you planned to go s-off)
Click to expand...
Click to collapse
thanks for your prompt replay guys much appreciated, I ended up using this rom :
vivo_signed_RUU_VIVO_SENSE30_WWE_3.11.405.2_ROM.zip - ZIP , from this thread:
http://forum.xda-developers.com/showthread.php?t=1136463 ,
carried out full format inc dalvik wipe, and installed zip from recovery, restarted in fastboot and flashed boot image seperate and hey presto, completely unbloated gingerbread [email protected]! i now have HTC dock mode back, and there's enough memory that it doesn't take seven seconds for the camera settings screen to pop up lol...
thanks again
ÂÐÐ¥ © ™
I have a Sprint HTC One M7WLS, unlocked, S-ON, Clockwork Recovery.
The problems started with me flashing Revolution HD. I wasn't aware Revolution wasn't available for the WLS (Sprint) model, so I installed it as 'International + Non-listed Models'. The phone booted up into the ROM after installation, but with limited connectivity. The phone would reboot about a minute after loading. I wiped Cache, Dalvik, System, SDCard, Data (everything CWM allows me to format). Reinstalled a new ROM, still experienced reboot issue. The new ROM (TrickMod) gave me a 'Process System Not Responding' error, and then a reboot about thirty seconds after error. All ROMs are having wifi issues. In initial setup, if I'm able to get the keyboard to type in the WiFi Password, my device refuses to connect due to 'temporarily avoiding poor connection' error. I believe this may be the root of, or related to my problems. I get no cellular signal, and am unable to launch 'Activate Device' on any ROM. So far all the ROMs I've tried include:
Revolution HD, TrickMod, SuperNexus, and D3rp. Not all give the 'Process System Not Responding' error, but none of them can connect to WiFi, none can activate the device, and all of them reboot about a minute or two after boot.
Any ideas or solutions?
---
PS: Before flashing Revolution HD (my phone was still running on factory stock ROM), I used TWRP to backup all partitions. After Revolution HD, I attempted to restore all partitions, but the phone would boot up, error, and reboot as with all other ROMs that I tried after this. I installed CWM for TrickMod, SuperNexus, and D3rp so I could sideload ROMs (TWRP would hang on sideload, and I can't boot into the system to transfer ROMs to the sdcard).
---
Edit: I also wiped Dalvik and Cache and Fixed Permissions after ROM install. Still erroring out.
CM 10.1
We can add CM 10.1 to the list of ROMs that don't work.
Have you tried the Ruu?
oppressedtoaster said:
We can add CM 10.1 to the list of ROMs that don't work.
Click to expand...
Click to collapse
SOUNDS LIKE YOU need to flash a stock kernel.
RUU
gmentals said:
Have you tried the Ruu?
Click to expand...
Click to collapse
I downloaded the RUU. Using the All-in-One Toolkit informed me I needed to relock my device and restore stock recovery. I haven't done either of those things yet. I don't know how to reinstall stock recovery.
What exactly does the RUU do though?
Have you tried to flash a stock kernal as suggested above?
I haven't used the toolkit but I read it will relock the bootloader for you. The stock recovery will be flashed during the Ruu process.
Flashing Stock Kernel
Aldo101t said:
SOUNDS LIKE YOU need to flash a stock kernel.
Click to expand...
Click to collapse
Don't many of these ROMs flash their own kernels?
It's my understanding I'll need an unsecure boot.img to flash a stock kernel.
How do I unsecure my boot.img?
Where can I find stock kernel download?
Yes, the roms flash a kernal. Have you tried any of the sprint specific roms since this started happening? I would suggest you try one of viperboys roms.
Viper ROM
gmentals said:
Yes, the roms flash a kernal. Have you tried any of the sprint specific roms since this started happening? I would suggest you try one of viperboys roms.
Click to expand...
Click to collapse
All ROMs have been found on Sprint HTC One Development forums. Except Revolution HD, which I installed as 'International' since 'Sprint' wasn't an option. That's when everything went foul, including my Nandroid restores. This leads me to believe a botched install of Revolution is the cause of my problems.
I'm downloading Viper for Sprint One right now, give it a go.
Just tried Tranquility, still got reboot issues.
If Viper doesn't work, I'm going to try the RUU. RUU will flash stock kernel, correct?
RUU Worked!
oppressedtoaster said:
All ROMs have been found on Sprint HTC One Development forums. Except Revolution HD, which I installed as 'International' since 'Sprint' wasn't an option. That's when everything went foul, including my Nandroid restores. This leads me to believe a botched install of Revolution is the cause of my problems.
I'm downloading Viper for Sprint One right now, give it a go.
Just tried Tranquility, still got reboot issues.
If Viper doesn't work, I'm going to try the RUU. RUU will flash stock kernel, correct?
Click to expand...
Click to collapse
RUU worked! Lovely! So happy!
I'm going to install a ROM now and mess it all up again xD
Thanks everyone!
I'm glad you got it figured out.
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.
Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?
Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.
bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.
Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
As the title states, is there a way to flash a new rom without being tied down to a PC / laptop?
Bootloader's unlocked, rooted, it's strange how with this phone we're forced to stay locked down to a PC.
Have never flashed anything from the Original Dev section on this phone yet, would that be the same method as normal rom's like monx's and IHackers?
Cheers.
huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.
tomascus said:
huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.
Click to expand...
Click to collapse
FTF's are not just for returning to stock, not at all, they're used to flash rom's too as the kernel and baseband needs to be flashed also.
Check out monx's thread, the instructions for install states to flash the rom and then without allowing a reboot, flash kernel and system (afaik)
Simply flashing the rom wouldn't be enough without flashing those files via flashtool.
What i'm trying to ascertain is do I have to do this every time as it's a pain in the backside.
Quote from Monx
LOCKED & UNLOCKED BOOTLOADER
BACKUP any critical data to microSD
Copy this rom zip package to microSD
Reboot in recovery, (do nandroid backup), do factory reset & install rom until finish
IGNORE RECOVERY INSTALLATION WARNING. SELECT NO & PROCEED AT THE END OF RECOVERY IF USING CWM RECOVERY
Skip (x) steps if u already running same base firmware with latest monxDIFIED base rom. Else, proceed.
(x) Turn off device. (Hold power button + vol up until vibrates 3 times) [or use recovery turn off device option, if any]
(x) Flash latest Sony's firmware (FTF) matching current latest monxDIFIED base rom using latest flashtools. UNCKECK all WIPE options and CHECK only SYSTEM & TA in EXCLUDE options.
(x) Disconnect USB cable & turn on phone. Done.
Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk
tomascus said:
Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.
dladz said:
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.
Click to expand...
Click to collapse
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.
tomascus said:
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.
Click to expand...
Click to collapse
Nice one m8, that's put an end to my misery, cheers for that, makes a lot of sense now, i wasn't aware of how Sony rom's were flashed, it's strange as the bootloader is unlocked? What more is needed lol.
As for the one x, that's the only HTC i skipped and glad i did apparently they had a lot of problems with flashing and stuff, S-OFF.
Anyway, thanks m8.