Here's my situation--I had been running MeanBean for a while and decided to try Kush's KK build (http://forum.xda-developers.com/showthread.php?t=2518211&highlight=loop). I flashed the recovery he linked to, then installed the rom and gapps he linked to. TWRP said everything went successfully. But, when I reboot, the phone just hung at the HTC splash screen. I tried flashing again, downloading fresh and flashing again, wiping the cache, etc. Nothing worked.
So, I decided to go back to my last nandroid of MeanBean. But, after TWRP "successfully" recovered to the latest nandroid, I got stuck in a boot loop. The phone gets through the first part of the boot animation, then freezes and reboots. I tried installing a fresh version of MeanBean, flashing back to TWRP 2.6.3, but nothing has eliminated the boot loop.
I'm s-off and I've never gotten stuck like this before. Anyone have any thoughts?
Reboot to the bootloader and run the command "fastboot erase cache" from a command prompt, then try a fresh install. Are you sure you're S-off?
Sent from my HTC EVO 4G LTE
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
tbhtjd said:
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot image from the rom? You shouldn't need to if you're s-off but couldn't hurt if you're still getting boot loops.
Sent from my EVO LTE
Thanks, Fin. I tried fastboot flashing to boot.img separately (which shouldn't be necessary with s-off) after a fresh install, and I'm still in the boot loop. Any other ideas?
Go to recovery, do a full system wipe (data, system, Dalvik & cache) and re-flash the ROM after a fresh download. Really, though, you shouldn't have to wipe cache, since it's under /data.
Sent from my HTC EVO 4G LTE
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
tbhtjd said:
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
Click to expand...
Click to collapse
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Trying to flash MeanBean, which is what I've been using previously. I flashed the regular 2.6.3 Jewel TWRP.
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
fredgar75 said:
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
Click to expand...
Click to collapse
Hmm, don't think that's it. I've been able to mount internal storage and wipe the cache, etc. just fine.
I'm at a loss at this point as to what the problem might be. If you shoot me a PM I have one last option for you.
Sent from my HTC EVO 4G LTE
Related
Okay I know this is a noob question so PLEASE excuse my noob-ism. Not sure if this should be in Q&A or Dev so please move to the correct section if I posted in the wrong one.
Okay, so my phone was originally 4.0.4 with a 1.19 HBOOT and 4.1 Sense. I rooted my phone, read up on a couple of threads and youtube videos regarding how to flash CM10 and from what I got if you have 1.19 HBOOT you can't just flash it using TWRP because you can't go S-OFF. Here is where I was a bit confused and think I went wrong. I read in the description of this video http://www.youtube.com/watch?v=HsQKOhqdPpM that if you aren't S-OFF that there is a workaround, which linked me to this page http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397 . So the 1st option said that it's possible to flash using Flash Image GUI to flash CM10 THEN to flash it in recovery, which I did. However now that I look closely at the pics it says only for EVO4G and the 3D. Here's where I'm at, Flashed using Flash Image GUI, then rebooted to HBOOT, then recovery, then flashed using TWRP. It looked like a success after rebooting because I seen the CyanogenMod boot screen but it's been about 25 minutes and it's just stuck there. Read up on it some more and it said that it should only take about 5-7 minutes for the first boot. I don't know what to do from here. Is there any way to still boot CM10 on my device since it seems essentially stuck at the "CM" boot screen? If not, what ROM would take me back to where I initially started off previous to trying to flash CM10 (like sense essentially)?
Once again, sorry for the noob-ism but kinda stuck here. Thanks!
I would try going into recovery and wipe Dalvik, Cache and then factory reset, do not wipe system just the 2 I mentioned and reboot, if it stays on boot anim, go to bootloader and fastboot kernel and reboot
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
drlzanej said:
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
Click to expand...
Click to collapse
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
om4 said:
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
Click to expand...
Click to collapse
THANK YOU! IT WORKED!
mista_k said:
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
THANK YOU! IT WORKED!
Click to expand...
Click to collapse
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
om4 said:
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
Click to expand...
Click to collapse
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
EdRF said:
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
Click to expand...
Click to collapse
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
om4 said:
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
Click to expand...
Click to collapse
Following this step of the process fixed this same issue for me.
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
corcgaigh said:
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
Click to expand...
Click to collapse
CaptinStabN said:
Following this step of the process fixed this same issue for me.
Click to expand...
Click to collapse
EdRF said:
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hmm...well this time I just went to recovery. Made a backup and erased, cache, dalvik, system. Did a factory reset as well (didn't do that before) and in the end did as you guys suggested. Flashed rom and then boot.img via fastboot. Thank you very much!!! :victory:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Nothing works!
om4 said:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Click to expand...
Click to collapse
Okay so I did all of this and still..... doesn't work. I'm not really a phone wiz. I paid someone to root my phone before and I used the CM10 ROM, everything was fine until I tried to change my font, the phone rebooted and got stuck on the CM 10 boot screen. I went to recovery and restored my phone from September. I then went to Flash Image GUI and flashed the boot.img for CM!0. Then went into recovery and flashed CM!0 and gaaps and wiped the cache, delv cache, system and factory reset. When I rebooted I was still stuck on the boot screen. :/ I am able to restore back to September but my camera or wifi doesn't work. Anyone know how to help me?
Try flashing meanrom, it has the kernel installer and doesn't require flash image or fastboot. If you still have any issues with the camera then relock the bootloader and flash ruu. If that doesn't fix the camera then its most likely hardware failure.
flash gui image htc evo lte
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
SunnyDNuts said:
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
Click to expand...
Click to collapse
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
I tried. It either says the file is to big or don't have the right file
I tried all the files on the backup
---------- Post added at 09:40 PM ---------- Previous post was at 09:15 PM ----------
FinZ28 said:
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I tried compressing the backup file so GUI would search for the
Kernel but it can't find the image
Bootloop Battery Issue
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
ross7alex said:
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
Click to expand...
Click to collapse
Do you have android sdk setup on your PC?
No but I can download it. Where should I find it?
---------- Post added at 05:27 AM ---------- Previous post was at 05:21 AM ----------
bigdaddy619 said:
Do you have android sdk setup on your PC?
Click to expand...
Click to collapse
Ok I found it and Im downloading it now. How will this help me?
So I am S-On, running CM 10.1.3 stable.
I was on OTA 3.16.651.3 with 2.09 hboot when I successfully unlocked my bootloader using HTCDev unlock and installed TWRP and SU using BigDaddy619's kit.
I wanted to try out CM 10.1.3 stable ROM. I was able to transfer the zip via usb to the Internal SD, then Installed inside TWRP. I then realized I needed to do the boot.img kernel flash using fastboot. I did this, and the phone booted up!
I have tried CM for the last 3 days, and like some aspects, but I really want GPS and Bluetooth to work.
So I tried to flash back to zhaus's stock ROM. The problem is I no longer have an internal SD mounted, and the phone won't let me download files. I can not for the life of me figure out how to remount the internal SD so I can download to it. Plus, the phone won't allow me to fastboot update or push the file to the phone using ADB. It's weird, since fastboot works but errors, but ADB doesn't even find my device.
Another odd thing is when I enter TWRP and try to do a factory reset/wipe, it always says FAILED.
I am super confused on how to proceed in switching back to a stock ROM. Hoping someone can throw me a life preserver.
You need to format your internal storage. To do this, boot into recovery and connect your phone to your PC. Select the 'Mount' option, then select your internal storage. You should then be prompted to format your storage on your computer.
Also, when wiping with TWRP, choose the advanced wipe option and select Dalvik cache, cache, data & system.
GPS should be working on that build of CM. You may need to try the GPS fix from a Sense ROM before dismissing the issue as GPS simply not working.
Sent from my HTC EVO 4G LTE
bman3333 said:
I have tried CM for the last 3 days, and like some aspects, but I really want GPS and Bluetooth to work.
Click to expand...
Click to collapse
I'm confused, because both of those things work fine on CM10.1. Methinks you should S-OFF to avoid these types of issues going forward . . . .
Captain_Throwback said:
I'm confused, because both of those things work fine on CM10.1. Methinks you should S-OFF to avoid these types of issues going forward . . . .
Click to expand...
Click to collapse
I don't think I properly installed CM 10.1. I initially tried to flash cm-10.1.3-jewel inside TWRP, BEFORE flashing the kernel with the extracted boot.img in fastboot. I never tried to re-flash the cm-10.1.3-jewel zip after flashing the kernel.
My second mistake was selecting factory reset in the bootloader, which screwed up the Internal SD mount.
Thank you guys for the replies.
bman3333 said:
I don't think I properly installed CM 10.1. I initially tried to flash cm-10.1.3-jewel inside TWRP, BEFORE flashing the kernel with the extracted boot.img in fastboot. I never tried to re-flash the cm-10.1.3-jewel zip after flashing the kernel.
My second mistake was selecting factory reset in the bootloader, which screwed up the Internal SD mount.
Thank you guys for the replies.
Click to expand...
Click to collapse
It's best to avoid a factory reset from the bootloader. Anything you do as far as wiping should be done from recovery. Don't sweat it, though, you aren't the first person who has done it and you surely won't be the last
Sent from my HTC EVO 4G LTE
Today I decided to root my phone, and after successfully doing that, decided I wanted to try out installing a custom ROM. Obviously by the title that didn't work out too well.
I'm using ClockworkMod as recovery, and I attempted to flash CyanogenMod using ROMManager. I created backups before I tried flashing, but that didn't help. Once I hit Install ROM from SD Card I made sure to back up again, but I did not check clear the cache which I probably should have done. My phone then rebooted into ClockworkMod and I then went to install zip from sdcard and chose the .zip that contained the latest CyanogenMod, it ran through the process alright then rebooted.
At that point I got stuck in a boot loop, I think it might've been either that I didn't clear the cache before or if it was that I had the .zip on an external SD card or not. I then looked up ways to fix the loop such as clearing the Dalvik cache, wiping the cache partition, then eventually I tried to wipe the data/factory reset on the recovery option but that all did nothing. During all this I also tried my backup hoping that would end my problem, but I got an error with the MD5 mismatching so I can't use that backup, I do have other backups on my computer, but I can't get them onto the SD card, and ADB isn't detecting my phone so I can't try a way to fix the backup that way either.
Anyone have any idea how to fix this? I can provide more information if needed. Any help would be great.
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig for more info. Also, TWRP recovery is recommended on the EVO LTE, not CWM, which is no longer supported, at least on this device.
Sent from my HTC EVO 4G LTE
FinZ28 said:
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig for more info. Also, TWRP recovery is recommended on the EVO LTE, not CWM, which is no longer supported, at least on this device.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Ok, thank you so much for your response this actually got me back on track after switching to TWRP and flashing the kernel first with CWM being the big issue for me. Now I'm just waiting for CyanogenMod to load, which I assume just takes a few minutes at the loading screen.
Got it fully working, thanks again
Not a problem.
Sent from my HTC EVO 4G LTE
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
Hello All,
After replacing my shattered screen, I left my sd card in while pulling the red case out and damaged the sd card housing. With a little more troubleshooting, the sd card slot fell out and disintegrated. I filled in the contacts with solder, however ever since (before and after) it gets stuck in a boot loop. I am able to connect to it through adb and push roms, even update them, but on reboot they dont work.
I followed the steps to a T. http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing_2
I have amon RA recovery, wiped all data/factory reset, wiped cache and dalvik cache. Flashed rom. Cleared cache and dalvik again. rebooted, nothing.
I am attaching a logfile. It is big, but I didn't know where it started and where it ended.
http://pastebin.ca/2488280
Any help is appreciated.
thefonzz2625 said:
Hello All,
After replacing my shattered screen, I left my sd card in while pulling the red case out and damaged the sd card housing. With a little more troubleshooting, the sd card slot fell out and disintegrated. I filled in the contacts with solder, however ever since (before and after) it gets stuck in a boot loop. I am able to connect to it through adb and push roms, even update them, but on reboot they dont work.
I followed the steps to a T. http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android#ROM_Flashing_2
I have amon RA recovery, wiped all data/factory reset, wiped cache and dalvik cache. Flashed rom. Cleared cache and dalvik again. rebooted, nothing.
I am attaching a logfile. It is big, but I didn't know where it started and where it ended.
http://pastebin.ca/2488280
Any help is appreciated.
Click to expand...
Click to collapse
if s-on are you flashing the boot.img from that rom in fastboot?
REV3NT3CH said:
if s-on are you flashing the boot.img from that rom in fastboot?
Click to expand...
Click to collapse
You're right, I am s-on. So i did that, but I am hitting the same problem.
Namely:
"cutils-trace: Error opening trace file: No such file or directory
"JNI posting fatal error: Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
Followed this: androidforums.com/gsm-evo-3d-all-things-root/723480-how-install-custom-rom-s.html
thefonzz2625 said:
You're right, I am s-on. So i did that, but I am hitting the same problem.
Namely:
"cutils-trace: Error opening trace file: No such file or directory
"JNI posting fatal error: Native registration unable to find class 'android/media/videoeditor/VideoEditorProfile', aborting
Followed this: androidforums.com/gsm-evo-3d-all-things-root/723480-how-install-custom-rom-s.html
Click to expand...
Click to collapse
you do realize thats for the evo 3d and not for the rezound right....2 different devices and setups
what rom are you trying to flash and ill step by step you with what you need to do
REV3NT3CH said:
you do realize thats for the evo 3d and not for the rezound right....2 different devices and setups
what rom are you trying to flash and ill step by step you with what you need to do
Click to expand...
Click to collapse
I'm trying to flash Pac-Man http://forum.xda-developers.com/showthread.php?t=2425473 . I did a wipe data/cache on amon ra, wipe system, wipe dalvik. Adb push the pacman zip, push the gapps zip, push the boot.img zip. I flashed them to internal_sd.( Other times, when I flashed them to /data/ and then used recovery --upgrade_package=DATA:file_name.zip It would either say the install completed or hang and in either instance not work.) After flashing to internal_sd, i used the flash_zip functionality from amon_ra which lets you pick from internal_sd. I flashed pacman, it said it was successful, gapps successful. I rebooted the bootloader as directed into fastboot, i issued the fastboot boot /path/to/boot.img and it gave an OK. I rebooted back into recovery, cleared dalvik, cleared cache and rebooted. Thats what I got above.
Let me know if I should do something different. Thank you for the help.
thefonzz2625 said:
I'm trying to flash Pac-Man http://forum.xda-developers.com/showthread.php?t=2425473 . I did a wipe data/cache on amon ra, wipe system, wipe dalvik. Adb push the pacman zip, push the gapps zip, push the boot.img zip. I flashed them to internal_sd.( Other times, when I flashed them to /data/ and then used recovery --upgrade_package=DATA:file_name.zip It would either say the install completed or hang and in either instance not work.) After flashing to internal_sd, i used the flash_zip functionality from amon_ra which lets you pick from internal_sd. I flashed pacman, it said it was successful, gapps successful. I rebooted the bootloader as directed into fastboot, i issued the fastboot boot /path/to/boot.img and it gave an OK. I rebooted back into recovery, cleared dalvik, cleared cache and rebooted. Thats what I got above.
Let me know if I should do something different. Thank you for the help.
Click to expand...
Click to collapse
Bump?
Flashed phone to cm 10.2. Problem Solved.
thefonzz2625 said:
I'm trying to flash Pac-Man http://forum.xda-developers.com/showthread.php?t=2425473 . I did a wipe data/cache on amon ra, wipe system, wipe dalvik. Adb push the pacman zip, push the gapps zip, push the boot.img zip. I flashed them to internal_sd.( Other times, when I flashed them to /data/ and then used recovery --upgrade_package=DATA:file_name.zip It would either say the install completed or hang and in either instance not work.) After flashing to internal_sd, i used the flash_zip functionality from amon_ra which lets you pick from internal_sd. I flashed pacman, it said it was successful, gapps successful. I rebooted the bootloader as directed into fastboot, i issued the fastboot boot /path/to/boot.img and it gave an OK. I rebooted back into recovery, cleared dalvik, cleared cache and rebooted. Thats what I got above.
Let me know if I should do something different. Thank you for the help.
Click to expand...
Click to collapse
use twrp or cwm.... amon ra is not recommended as it will give many bugs with flashing any rom higher than ice cream sandwhich....such as many random reboots...overheating...bad signal...etc....i suggest not doing adb method....only flash rom and gapps in recovery then reboot to botloader and select fastboot and plug it in so it says fastboot usb... in your fastboot folder on pc place the boot.img in it....open commabd prompt and cd to that folder and type: fastboot flash boot boot.img
again amonra will not work on ny jb or kit kat roms....a good thorough reading from the users and comments will ensure this....adb only works in certain recoveries or in rom with android debugging enabled...