I installed the Pac-Man ROM for my lg p500,earlier today. I wiped data/factory reset, wiped battery stats and dalvik cache before flashing the ROM.Once I flashed the ROM, I flashed Gapps JB light and then used a baseband fix zip file because my phone is on v10c. (I couldn't upgrade earlier as my computer wouldn't recognize it,even after installing all the required LG drivers.) Then, I booted. It was working like a charm.
Afterwards,I realized I hadn't flashed a file called INT2EXT4.exe. I thought it wouldn't make a difference and anyway,flashed it.
To my horror, the bloody thing doesn't go past the second boot image now. All I see is the Pacman boot image. I tried to boot into recovery mode ,but the buttons are simply unresponsive. (Power+ home+ upper volume rocker) . I'm on TWRP 2.2.0.
Please help me.I've hardly installed 3 or 4 ROMS,till date.I'm not fully aware of the dynamics of this yet.
Regards,
Suraj
try home+volume rocker down+power. It should work.
INT2EXT4.exe? Why .exe?
home vol down power is fastboot for me. if you can get there then use shinobisofts recovery flash tool for windows to reflash a recovery. boot into recovery and flash a rom.
not sure why one would think to use a windows EXE on a linux OS...
your phone isnt broken fully. DO NOT GO THE KDZ ROUT YET!!!!
I'm assuming it's the latest Pac-Man and, if that's the case, it's a 4.2.1 ROM and most of the Int2Ext scripts won't work with it.
You need the fixed 4.2.x version which you can get Here.
A little tip though: Get the script out of the zip, or open the zip and browse to /system/etc/init.d where the script is located. It's called 40int2ext. Open the ROM in WinRAR, Zip etc (don't unpack it, just double click it) and drag the script into the same place: /system/etc/init.d and just click OK at the dialog that opens, dont change any of the settings.
Then flash the ROM like that.
Next, and I don't know if this is essential but I had a bootloop by not doing this first, boot into the ROM. Then reboot to recovery and flash Gapps and you should be good.
But above all, as savagephoenix says, you haven't bricked your phone. I've done the same thing and you shouldn't have damaged your recovery partition.
But it's Home, Volume DOWN and Power to get to recovery.
What is pac man rom? I see that allmost every phone have their own rom with pac man...
Related
Is clockwork recovery necessary for all roms or can i download a recovery to my phone?
Well if you could make a recovery based off of something else that had ext. 4 support then you could probably use that. Just the fact that there is already CWM for the MT already makes it easier. If you meant does it need to be installed then yes, you need it installed to flash different roms.
Can CWM be flashed through Rom Mgr? I tried bootloader and mobile and image and recovery img and i think i put in wrong folder. Everytime i try to get back into bootloader with pwr button and vol dwn. It goes right to M screen. How can i fix this?
Ok i get to download mode now where do i put the extracted recovery folder in image? Do i place with recovery img or down at the bottom?. When i take battery out and put back. I pwr and simitaneously vol buttons. I get the triangle !. What am i doing wrong. Oh and im on ver 2.2.2
It's real easy all you need to do is Volume down then power sometimes it's a pain in the ass but keep repeating the steps until you see white writing on the screen, then plug it into your PC, it should bring up a drive called mobile there will be a folder open the folder & replace only the recovery image then reboot. Should be all good. Then press volume up & down & power should boot into clockwork.
Did u install CM7 first?
You can't install CM7 or any other rom "first" using stock recovery. As far as I have seen CWM is the only alternative to the stock recovery.
Hey guys, I'm fairly new to this but I have my One S, H-Boot 1.18, Radio 1.08, unlocked, rooted, TWRP2.4.4.0 and S-Off...
I have successfully installed CM10, and have since restored it to the Stock RUU.
I have tried loading the Viper 2.1.0 5 times now and keep getting stuck on the "white "T-Mobile screen" with the red text on it. I have a few questions about the instructions that are posted.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
10. After you configured it, reboot to your bootloader in fastboot mode
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
Any advice, appreciated, I'm not stopping until this thing is a brick or I figure it out...
thanks ahead of time, and I have tried to read through there are almost 600 posts so if I missed something I apologize ahead of time.
I know exactly how you feel..I went through the same issues as you did. Below are my feedback on what I did, however as I found through other posts, instructions may work for some, but not all phones. So please be careful if you were to follow what I did. I put my feedback in blue and my own direction list on what I did that finally made viper one s work for me.
1. Download the Boot.img Flash Script from http://androidfilehost.com/?fid=9390275921635705217
2. Download the Rom
3. Extract the Boot.img Flash Script on your PC
4. Connect your One S to the PC (USB Disk Mode), copy ViperOneS_xx.zip (the ROM) to your HTC One S
5. Connect your One S via USB and ensure you have HTC Sync installed, you need the drivers to be able to use fastboot
6. Uncheck fastboot in Settings->Power, then shut down your HTC One S completely (don't reboot, shut it down).
7. Press and hold volume down, then press power (keep holding volume down!) until your screen shows the hboot menu, navigate to recovery (use volume keys)and press the power button once to jump into recovery mode.
8. In Recovery choose install zip from sd -> choose zip file and navigate with your volume buttons to the downloaded Rom and hit power and confirm with yes.
I am using TWRP 2.4.4.0 which is supposed to be problem free (something about they fixed the .lib issue from the previous version that the new JB created), I have been wiping System and recovery.
Alright, seems like it's good then, I used CWM to make mine work but I'm pretty sure that you'll be fine with that one.
9. Now the Aroma installer should show, if you have the touch recovery installed you can use your screen to navigate through it, otherwise use the volume buttons and confirm with the power button.
I'm confused on the Kernel prompt during the installation, doesn't the boot.img file that we install in the next step have a new Kernel in it? So do I sellect a custom Kernel or not?
This is what I figured out, as I had the same question when I was going through the installer.
-Yes: Means that you come from a kernel that is not the normal kernel, such as ElementalX.
-No: Means you are using the stock kernel.
Selecting yes will skip the new flashing of the boot.img kernel, while selecting no will flash the boot.img
IMPORTANT: if you come from another Rom, pls choose FULLWIPE
Actually this part was the game changer for me, instead of following this, I wiped the system using my recovery, then selected install without wiping. (As I already wiped it via recovery)
10. After you configured it, reboot to your bootloader in fastboot mode
Even though I have seen numerous posts saying that once the One S is S-off you don't need to boot-flash-script..I clicked restart on the aroma installer and pressed the volume down button and the power, went into boot loader, went into fast boot USB and installed the boot-flash-script anyways..doesn't hurt
11. Now go to your extracted Boot.img Flash Script folder:
Depending on your OS of your PC you need to run the file like normal:
Windows: flash-boot-windows.bat
MAC: flash-boot-mac.sh
Linux: flash-boot-linux.sh
12. When the commands were successful, press power again to go back to the hboot
13. Navigate with your volume button to "Recovery" and reboot or reboot via cmd with "fastboot reboot"
14. Finally we highly recommend specifically for One S to boot again in recovery and wipe cache. Please do that also, whenever you flash any addons or mods – always boot your device first, then boot again in recovery and wipe cache.
15. Recommendation - with "Flash Image GUI" from joeykrim you can alternatively flash boot.img on your device, no need to fastboot anymore - http://forum.xda-developers.com/show...1954121&page=2
This recommendation Should be in the beginning right? Doesn't this flash the Kernel and then tell you to install the ROM directly afterwards? So shouldn't this be step one?
For me, I ignored that, because of that I have no knowledge for this question. :/
I am going off knowledge of what I did, as I had the same trouble you did. I tried to flash the rom countless times, almost bricked my phone, but after a stressful trial and error, I found the bugs that gave me my problems.
My Directions
1. Make nandroid (Just in case rom doesn't work)
2. Backup all apps as wiping phone will wipe all data and apps
2. Put viper 2.1.0 on device folder (I made a folder called roms)
3. Go to recovery
4. Wipe cache, system, and dalvik
5. Start the installer
4. Run through the desired checklists
-Select continue without wipe
-If on normal kernel select no when prompted on the kernel checklist
5. Once complete, click restart
6. Press and hold volume down and power to go to boot loader
7. Install boot-flash-script
9. Start Phone
10. It will be wiped, so go through the HTC start-up instructions
11. Once all that is done and the phone is fullyloaded, boot phone to recovery
12. Wipe Cache (to lessen lag)
13. Reboot again and done!
Don't use twrp 2.4.4.0, there are known problems flashing with it. Go for 2.3.3.0
First Thanks to both of you for the help.
So I down graded to TWRP 2.3.3.0...
Backed up my phone
Restarted phone, mounted and deleted the old back up
Began following the modified instructions
It appeared to work a little better this time ie... The installation screen colors seemed to be right and not all in a blue hue, and when it loaded it went all the way to 100% instead of hanging at 7% and then saying done.
I want to make sure this is correct also when I run the fastboot script, that this is what it should look like...
C:\htc_one\One_S_All-In-One_Kit_v3.4\Data>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (6124 KB)...
OKAY [ 0.850s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.328s
Alas this is still a "no joy" situation.
only good news is that I'm not stuck at the T-Mobile screen any more, the screen goes away after 5 seconds and now I'm sitting on a black screen.
What this has led me to think is that either the rom did not install correctly (duh) or you just downloaded the update for viper one s instead of the whole rom.
So just for clarification, now instead of on the t mobile screen it now goes to a black screen?
-Have you gone back into recovery and wiped cache again?
-Do you have a custom kernel or the stock kernel?
On another note.. Yes, the fastboot script was correct.
Sent from my HTC One S using xda app-developers app
So, I got it working, it seems that because I have my phone in S-Off, I didn't need to run the script. I just let it reboot after reinstalling it and it came up just fine.
I really appreciated the help guys, great support here... Maybe this post itself will help someone. :good:
Like the title says, my Nexus 5 won't boot unless I manually plug it in, hold down volume buttons and power, then wait 15 seconds for fast boot to appear, and then select "start."
Thats the problem. Now for some more information:
1. Nexus 5 32 gb
2. ROM: CM 11 Dec 13s Nightly
3. Kernel: Bricked 3.4.0
4. The phone is totally functional. The only thing wrong with it is that it can't reboot. From the system, TWRP recover, or anything, it simply will not reboot. Every time I must go into fast boot then press the power button when it says "start." After this, the phone works just as I would expect it to. I can still flash kernels and backups through recovery, it just must be restarted manually through the fast boot. This is a problem for me because I don't always want to have to plug it in when I want to reboot it.
When did it start:
Let me start off by saying that I thing the root of all my problems was the TouchControl app that allows the knock to wake function to work. I downloaded the app and was told to install the developers custom kernel. I did and not only did the app not work, it also seemed to brick my phone. I was scared, but, after doing some research, I found the method of plugging it in and holding down all buttons for about 15 seconds and my phone was saved. Ever since then there has been the problem. I must always do this to reboot my phone. Since the app didn't work I decided to install the Bricked Kernel and everything went fine except that I wasn't prompted with the interactive installer. The kernel works fine and I am now using the Knock to wake feature built into the kernel and am very happy.
Seems to be caused by swipe2wake aka knock 2 wake aka knock knock (but not totally sure)
What I've Tried (don't assume I've tried something I haven't. I could have missed something obvious.):
1. Resetting permissions through TWRP (just thought I'd try)
2. Putting back CM 11 Kernel
3. Restoring to a time when my phone did restart
Any help would be greatly appreciated. I will try to keep the original post updated with everything I try.
FIXED with the help of jd1639 and meangreenie
------------------------------------------------------------------
1.Follow jd1639's link in 3rd comment to the page and
A. Install adb and flashboot drivers
B. Install your version of factory images from google (if you are running 4.4.2 get the image for 4.4.2)
2. Plug in phone to AC CHARGER and hold down power and volume buttons for up to 20 seconds. This should put it into fast boot mode
3. After getting phone in fast boot mode, plug it into your mac or pc.
4. Out of all the instructions in the "How to flash a factory image" thread go to method 2 and ONLY DO THE FIRST TWO LINES OF CODE. All that needs to be flashed is the bootloader.img
5. After it says complete and your phone restarts you should be able to push "start" on your phone and be good!
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
jd1639 said:
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
Click to expand...
Click to collapse
So that's essentially flashing the stock ROM?
benaside said:
So that's essentially flashing the stock ROM?
Click to expand...
Click to collapse
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
benaside said:
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
Click to expand...
Click to collapse
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
jd1639 said:
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
Click to expand...
Click to collapse
I downloaded the folder for 4.4.2 from the link developers.google .com/android/nexus/images#hammerhead
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
meangreenie said:
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
Click to expand...
Click to collapse
Will this'd elite all my files and unroot?
Btw thanks so much for the help
benaside said:
Will this'd elite all my files and unroot?
Btw thanks so much for the help
Click to expand...
Click to collapse
no it won't delete your data.. but please triple check your files and fastboot commands before executing
the last resort is to format data if all else fails
Thank you both so much. I have (with both of your help fixed it). I will post how in the original post. Thanks again.
guys,
my tab2 starts up with a system recovery screen.
i started reading on the forum, and according to many threds, i ned to wipe data/factory reset and then flash a ro. so i copied a rom(omni 4.4.2) to my micro sd, wiped data/factory reset but then it stops. There is no flash option in the system recovery screen.
anyone who can help?
thanks ina dvance.
Sounds like you are dealing with the Stock recovery.
To flash a custom ROM you FIRST need to flash a custom recovery to flash the ROM.
- For CM11 flash Philz Touch or CWM Swipe Edition through ODIN3.
- For OMNI flash TWRP through ODIN3.
This means: Get the .tar.md5 from Android Andi's file repository, install ODIN3 + USB drivers on your computer, put the Tablet into Download Mode, start ODIN3, select the recovery file as a "PDA" file, connect the tablet, flash it, disconnect after flashing, get into the custom recovery (Power + Vol UP), flash the ROM + gapps.
Or ... maybe read the OP post of the custom ROM you want to flash with a bit more care and attention - it's usually pointed out that you need a custom recovery in order to flash the ROM (stock recovery won't cut it).
BoneWithABeagle said:
Sounds like you are dealing with the Stock recovery.
To flash a custom ROM you FIRST need to flash a custom recovery to flash the ROM.
- For CM11 flash Philz Touch or CWM Swipe Edition through ODIN3.
- For OMNI flash TWRP through ODIN3.
This means: Get the .tar.md5 from Android Andi's file repository, install ODIN3 + USB drivers on your computer, put the Tablet into Download Mode, start ODIN3, select the recovery file as a "PDA" file, connect the tablet, flash it, disconnect after flashing, get into the custom recovery (Power + Vol UP), flash the ROM + gapps.
Or ... maybe read the OP post of the custom ROM you want to flash with a bit more care and attention - it's usually pointed out that you need a custom recovery in order to flash the ROM (stock recovery won't cut it).
Click to expand...
Click to collapse
thanks for the reply.
SOmehow i got the tab back into flashing to a samsung rom. Am happy it is working again, although it is with a samsung rom(those things are slow )
Will start the procedure youre suggesting.
Regards.
This is simple guide for HTC One S ville2 (s3 variant) users for installing MiUi rom.
I am new to this but surely can be of some help.
You should have rooted device for installing this rom.
Before this I was having ViperS/C2 5.2.1 (Viper ROM by Team Venom ) as HTC stopped future support for this device. And I was dying to feel the new sense5.
And loved this rom.
Coming to MiUi..
I have installed this rom and surprisingly it surprised me Yes it is quite impressive. No lag. Fast interface. iOS like UI. Impressive quick settings.
here is guide for installing this rom and some problems which I faced in the process.
ROM download link- URL is in attatchment.
(In the above link you will find latest ROM currently 4.9.12 and also flashing guide)
First download the rom.
But wait..DON'T FOLLOW "flashing guide"..Cause here only I faced a major problem.
In the flashing guide you can follow the instructions to unlock bootloader if your device is not rooted.
But don’t install the Flashing kit.
PROBLEM-
In the step: “Installing the kernel” they have asked to connect the device to your computer. After connecting you have to install “kernel.bat” which comes along with the flashing kit.
If you try installing it, it will start the phone in fastboot mode and it will install a custom recovery in your device.
So on my device recovery which got installed was “clockworkmod recovery”. This recovery does not work with ville2. And somehow my previous OS i.e. viper got corrupted.
So when I tried entering into recovery mode, my phone got stuck on “Entering Recovery” screen.
And further when I thought I should drop the plan of MiUi and restarted the phone, it just got stuck on HTC logo screen i.e start boot screen.
So don’t followupper step.
Instead do this.
Download the rom in your Sd card. Do not extract the file.
And save a copy of rom on your computer.
From zip file of rom extract “boot.img”.
Now install Teamwin recovery- URL is in attatchment.
If you want to install recovery in fastboot mode follow instructions given on this link- URL is in attatchment.
After installing recovery enter recovery. (i.e. while phone is off press power+vol down to enter fastboot mode..there you will find an opt for recovery)
Take a backup of your previous rom from option given in recovery.
Wipe cache, dalvic cache and do a factory reset.
After doing this just install the rom file.
(If your rom file got erased don’t panic. In recovery press option “Mount”. From there mount sd card. And from computer copy rom file on your device.)
After installing rom enter in fastboot mode (power button + volume down)
Now on your computer install “venom kernel flasher”- URL is in attatchment.
Now open kernel flasher. Click on Manual tab at top.
Locate the “Boot.img” file which you have extracted from rom zip file.
And flash.
DONE.
ROM installation process completes here.
Now when you first start the phone everything will be in Chinese. Don’t panic. Go into setting tap on general setting tab at top and search for the option having small keyboard icon on its right side. Inside it first option is for language.
FINI.:laugh:
This is my first post. If you find anything wrong or any suggestions please do post.