Hi. I have a Galaxy Nexus (GSM, maguro, I9250). I use stock Android 4.2.1 (JOP40D), unlocked, rooted (with CWM recovery).
Recently, I've tried to flash several different ROMs.
After every attempt, I got stuck on the boot animation (5+ minutes).
First, I tried to install CyanogenMod 10 (build is the latest stable for maguro from get.cm) together with a gapps package.
This made me get stuck on the boot animation. Restored, tried again without gapps, same result.
Then, I flashed TWRP recovery and tried installing the same build again (without gapps).
Still got stuck on boot animation.
Back to CWM, I got the latest stable build of AOKP for maguro from the offical website's downloads page.
Tried to flash that (without gapps), same result. Stuck on the boot animation.
I'd really appreciate some help with this.
Might sound stupid but... did you wipe ?
Sent from my SGH-T999 using xda premium
---------- Post added at 07:02 PM ---------- Previous post was at 07:01 PM ----------
Also I think you need an unlocked bootloader..
Sent from my SGH-T999 using xda premium
shahkam said:
Might sound stupid but... did you wipe ?
Click to expand...
Click to collapse
Yes I did, on all four attempts.
shahkam said:
Also I think you need an unlocked bootloader..
Click to expand...
Click to collapse
As stated in the OP, I do have an unlocked bootloader.
Factory reset before different roms.. guess you just posted that ya did wipe. How about both dalvik cache and regular cache? fastboot erase cache?
bodh said:
Factory reset before different roms.. guess you just posted that ya did wipe. How about both dalvik cache and regular cache? fastboot erase cache?
Click to expand...
Click to collapse
I'll try installing AOKP with fastboot erase cache instead of CWM's "wipe" functionality.
Related
new to rooting, flashing, etc.
Tried flashing CyanogenMod 6, I believe, using ROM Manager app. I downloaded the ROM to SD card and followed instructions to install. Now it's been stuck booting for an hour. I tried taking the battery out and going into recovery but it just gets stuck at the Odin screen with 'do not turn off target' message.
Any assistance would be appreciated.
Thanks everyone.
CyanogenMod 6??? Why not CM9 or CM10? Did you root the phone ? Follow this tread http://forum.xda-developers.com/showthread.php?t=1739426
---------- Post added at 06:14 PM ---------- Previous post was at 06:06 PM ----------
Also try to boot into recovery and wipe data/factory reset, wipe cache, wipe dalvik and fix permissions
tonymtl said:
CyanogenMod 6??? Why not CM9 or CM10? Did you root the phone ? Follow this tread http://forum.xda-developers.com/showthread.php?t=1739426
---------- Post added at 06:14 PM ---------- Previous post was at 06:06 PM ----------
Also try to boot into recovery and wipe data/factory reset, wipe cache, wipe dalvik and fix permissions
Click to expand...
Click to collapse
I'm not sure what version I attempted to install. It could've been CM9/10...
I did root the phone prior to doing all of this. I did as you suggested: go into recover and wipe data/factory reset, wipe cache, wipe dalvik and fix permissions and when I reboot the phone, the Samsung logo pops up and vibrates, then nothing. I keep having to take out the battery to restart.
john.s.kim79 said:
I'm not sure what version I attempted to install. It could've been CM9/10...
I did root the phone prior to doing all of this. I did as you suggested: go into recover and wipe data/factory reset, wipe cache, wipe dalvik and fix permissions and when I reboot the phone, the Samsung logo pops up and vibrates, then nothing. I keep having to take out the battery to restart.
Click to expand...
Click to collapse
You can go to the tread I posted before, download and flash with odin stock rooted rom it should work. It did for me.
tonymtl said:
You can go to the tread I posted before, download and flash with odin stock rooted rom it should work. It did for me.
Click to expand...
Click to collapse
I downloaded the file to my desktop and when I use Odin to load, it cannot find the file type. I think it has to be a .tar file.
Thanks
Flash the rom twice, then see if that works.
Usually in rom manager it detects your phone and WON'T let you dl a rom not specific to your phone.
Sent from my SAMSUNG-SGH-I747 using xda premium
Wipe data, system, and cache. install cm. Install gapps, reboot
Sent from my Nexus 7 using xda premium
john.s.kim79 said:
I'm not sure what version I attempted to install. It could've been CM9/10...
I did root the phone prior to doing all of this. I did as you suggested: go into recover and wipe data/factory reset, wipe cache, wipe dalvik and fix permissions and when I reboot the phone, the Samsung logo pops up and vibrates, then nothing. I keep having to take out the battery to restart.
Click to expand...
Click to collapse
I suggest that you pay more attention to what your flashing and do some more reading. You can end up with a paperweight easily being this careless
Sent from my SAMSUNG-SGH-I747 using xda premium
john.s.kim79 said:
I downloaded the file to my desktop and when I use Odin to load, it cannot find the file type. I think it has to be a .tar file.
Thanks
Click to expand...
Click to collapse
You need to download a 7z file extractor its like zip or rar, Extract the stock_root67.tar from the .7z file you downloaded.
Hello,
I'm having issues to get the Pacman 19.1a (GSM) to start. It's stuck at boot. I've tried flashing 19.1, which is booting fine, however this is not allowing me to enter a PIN code. This issue was reported fixed in 19.1a which is why I tried.
I'm using the following kernel: boot-HELLBOY-CM10-201212251747.img
Is anyone else experiencing this issue?
Thanks!
Did u do factory reset n cache wipe
Sent from my One V using Tapatalk 2
bahubali67 said:
Did u do factory reset n cache wipe
Click to expand...
Click to collapse
Sorry forgot to mention that; yes I did and I wiped Dalvik as well.
flash the latest kernel then in recovery do a wipe data/factory reset then try to install
FTMC said:
Sorry forgot to mention that; yes I did and I wiped Dalvik as well.
Click to expand...
Click to collapse
The same experience, also fully wiped. Stuck on Pacman logo.
gulsher said:
flash the latest kernel then in recovery do a wipe data/factory reset then try to install
Click to expand...
Click to collapse
As far as I know, I'm using the latest hellboy kernel. I've tried CM9 and CM10, but they both have the same effect. Should I be mistaken, could you provide me with a download link or version number I should get?
@brusell: So it seems I'm not the only one? I would have reported it in the ROM's topic, however my current postcount does not allow me to...
Resolved in Verdion 19.3
Just wanted to post the "solution"; the issue has been resolved in version 19.3.
Ok so I did a factory reset wiped cache and wiped dalvic, installed pacman 19.3 using twrp and then flashed hellboy kernel and rebooted, but I've been stuck at the pacman logo for 2 hours!! Did I do anything wrong? Can you tell me how u got out of it on 19.1?Do i just wait for the battery to die?
nvr mind got it
swhatevers said:
Ok so I did a factory reset wiped cache and wiped dalvic, installed pacman 19.3 using twrp and then flashed hellboy kernel and rebooted, but I've been stuck at the pacman logo for 2 hours!! Did I do anything wrong? Can you tell me how u got out of it on 19.1?Do i just wait for the battery to die?
nvr mind got it
Click to expand...
Click to collapse
Hey mate, i'm having the same problem as you did. Could you post the solution? Thanks in advance!
My HTC One X stuck on "HTC One's Logo" every time I try to format it,
so I restore my backup which works fine and when I tried to format it the same thing happened.
Whenever I try formatting my device it stuck on the logo !!
Please I need your help, what should I do with this strange problem ??
- Updated on May 26 -
Everything was okay one month ago and I was able to format my device normally but know I can't
I tried almost everything:-
1. I formatted my device then installed the ROM & Boot.img (and I was sure that it will not help)
2. I formatted my device from ARHD Aroma installation
3. I restore my ARHD backup then formatted my device again from CWM Recovery
Tips: formatting from recovery don't touch system partition, I'm sure
What do you mean by format? You mean from custom recovery? Factory reset from bootloader?
Maybe because you delete everything ? And without sytem it won't boot.
Sent from my HTC One S using xda app-developers app
vin4yak said:
What do you mean by format? You mean from custom recovery? Factory reset from bootloader?
Click to expand...
Click to collapse
From both, I tried every thing !!
sGollSv said:
Maybe because you delete everything ? And without sytem it won't boot.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
but formatting only format cache & data partitions !!
omar_bazaraa said:
From both, I tried every thing !!
Click to expand...
Click to collapse
If you Factory reset a custom rom, it will bootloop! Because there's nothing to boot beyond the logo!
1. Flash the boot.img from the nandroid backup. Then fastboot erase cache
2. Now go to recovery wipe data/cache/dalvic and then restore the nandroid backup.
3. Reboot. Let the OS load completely.
4. Go to bootloader and then do factory reset.
If your still bootlooping, then download a nandroid backup from http://forum.xda-developers.com/showthread.php?t=1975140 and then restore it! It will work flawlessly!
If you post your main-version, then we can also find a RUU for you?!
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
omar_bazaraa said:
but formatting only format cache & data partitions !!
Click to expand...
Click to collapse
Aah! Wiping data means all the files are gone! The OS won't boot up! :cyclops:
vin4yak said:
Aah! Wiping data means all the files are gone! The OS won't boot up! :cyclops:
Click to expand...
Click to collapse
But I tried this lots of times before and it format only user data, and system partition remain as it is.
I forgot to say that also when I flashed ARHD and checked "wipe data partition" in Aroma, the phone also stuck.
omar_bazaraa said:
But I tried this lots of times before and it format only user data, and system partition remain as it is.
I forgot to say that also when I flashed ARHD and checked "wipe data partition" in Aroma, the phone also stuck.
Click to expand...
Click to collapse
which boot.img are u flashing?
sridheepan said:
which boot.img are u flashing?
Click to expand...
Click to collapse
I'm aware of all these things >> I'm flashing the stock boot.img in ARHD.zip <<
Why do you want to wipe data every now and then?
Install a clean rom and use it...
vin4yak said:
Why do you want to wipe data every now and then?
Install a clean rom and use it...
Click to expand...
Click to collapse
My rom become heavy so I want to clean it
omar_bazaraa said:
My rom become heavy so I want to clean it
Click to expand...
Click to collapse
Which ROM are you currently on? ARHD?
and what do you mean by "I want to clean it"? Use rom cleaner to remove the system apps and to de-sense it!
omar_bazaraa said:
I'm aware of all these things >> I'm flashing the stock boot.img in ARHD.zip <<
Click to expand...
Click to collapse
Ok. start from zero.
Download again ARHD.
format sd card
Put ROM in Sd
Put this one in sd: http://d-h.st/kG0 (t.y for vin4yak for link)
Put boot.img in fastboot folder.
via cmd (i recomend to copy cmd into fastboot folder ((it automaticaly gives acces to that folder))) adb reboot-bootloader
type fastboot flash boot boot.img (fastboot must be in usb)
wait
reboot in recovery. install super wipe (link given)
clear catche, dalvik
install rom
clear catche, dalvik
And IF! it still got boot loop, go to bootloader and repeat fastboot flash boot boot.img command via cmd. It should work.
And after all, if it doesn't, do a full nandroid restore.
Good luck.
Formatting does only wipe cache and dalvic, you should still be able to boot. It does not get rid of Rom. I do it all the time when flashing a custom kernel. So maybe you should try as suggested above.
from my Viped out one x
Command: fastboot erase cache after flashing boot.IMG will fix it I guess. Looks like none of you do that but I always do that and never, I say never had a bootloop. And I switch ROMs weekly with wipes and all.
Hope it helps.
Sent from my HTC One X using xda app-developers app
J_Dutch said:
Command: fastboot erase cache after flashing boot.IMG will fix it I guess. Looks like none of you do that but I always do that and never, I say never had a bootloop. And I switch ROMs weekly with wipes and all.
Hope it helps.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
His question had nothing to do with flashing a boot.IMG, I've never not fast boot erase cache either. He was asking why when he hits the format button in recovery, his phone won't boot. Format in recovery simply wipes cache and dalvic so it should still boot, just like when you format after flashing the modules from a kernel.
DroidIt! said:
His question had nothing to do with flashing a boot.IMG, I've never not fast boot erase cache either. He was asking why when he hits the format button in recovery, his phone won't boot. Format in recovery simply wipes cache and dalvic so it should still boot, just like when you format after flashing the modules from a kernel.
Click to expand...
Click to collapse
O sorry for the misunderstanding.
So basicly OP asks "i took the fuel out of my car, why won`t it drive?"
Depends on wich recovery then cause in twrp a factory reset wipes not only cache and dalvik for sure!
From twrp site: A factory reset wipes data and cache (which includes dalvik cache). A factory reset will also wipe sd-ext and android_secure if your device has those items
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
vin4yak said:
Which ROM are you currently on? ARHD?
and what do you mean by "I want to clean it"? Use rom cleaner to remove the system apps and to de-sense it!
Click to expand...
Click to collapse
Yes, I'm on ARHD. I mean by cleaning the rom is to format it to return fast as it was.
omar_bazaraa said:
Yes, I'm on ARHD. I mean by cleaning the rom is to format it to return fast as it was.
Click to expand...
Click to collapse
Did you flash a custom kernel with modules?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Thanks all for your help but unfortunately all in vain
Before a month I was able to format without any problem, but now I can't.
I tried almost everything:
1. I formatted my device then installed the ROM & Boot.img (and I was knowing that it will not help)
2. I formatted my device from ARHD Aroma installation
3. I restore my ARHD backup then formatted my device again from CWM Recovery
All these attempts but in vain, please I need your help essentially, I need to format my device as I was doing before.
OK. I flashed the wrong kernel on my new Nexus 7 (2013). My stupid, I flashed the kernel (franco) for the old Nexus 7 on the new one.
Luckily, I can still access bootloader and recovery (TWP). Now it's stuck at Google (again, I can still go to bootloader and recoery).
Where can I find the stock kernel that I can use? Or Can I flash a custom kernel?
Thank you in advance and I appreciate every comment.
http://forum.xda-developers.com/showthread.php?t=2380380
I recommend flashing a custom kernel.
Username invalid said:
http://forum.xda-developers.com/showthread.php?t=2380380
I recommend flashing a custom kernel.
Click to expand...
Click to collapse
Thank you indeed.
opticaldh said:
Thank you indeed.
Click to expand...
Click to collapse
I have flashed this kernel http://forum.xda-developers.com/showthread.php?t=2390173
and I'm still stuck at Google, I can go to bootloader and recvery (TWP). Please help me (
Have you considered trying this which will return your Nexus 7 to its original factory settings with a stock image? I haven't used this method but it may get your tablet working again. Also, for future reference, you should always make a nandroid backup before you flash something new in case you run into problems like this.
Wiping the cache/dalvik cache usually works for me when it would hang on the boot screen after a flash.
Username invalid said:
Wiping the cache/dalvik cache usually works for me when it would hang on the boot screen after a flash.
Click to expand...
Click to collapse
I did it but nothing changes
Do you have a ROM installed?
Try restoring to factory settings, reflashing a ROM, and then flashing the kernel. Wipe cache/dalvik once you're done and see if that works.
cyberprodigy said:
Do you have a ROM installed?
Try restoring to factory settings, reflashing a ROM, and then flashing the kernel. Wipe cache/dalvik once you're done and see if that works.
Click to expand...
Click to collapse
I'm running on STock, so I have to download a custom ROM, right?
and how to restoring to factory settngs, btw? in twp, a factory reset is wipes data, cach and dalvik. I did that.
opticaldh said:
I'm running on STock, so I have to download a custom ROM, right?
and how to restoring to factory settngs, btw? in twp, a factory reset is wipes data, cach and dalvik. I did that.
Click to expand...
Click to collapse
Try flashing the stock rooted ROM here.
To restore to factory settings, go to "Wipe" then slide the slider at the bottom of the screen.
Sent from my Nexus 7 using xda app-developers app
opticaldh said:
I'm running on STock, so I have to download a custom ROM, right?
and how to restoring to factory settngs, btw? in twp, a factory reset is wipes data, cach and dalvik. I did that.
Click to expand...
Click to collapse
Thanks cyberprodigy and Username invalid for helping me.
I fixed it.
After flashing 2 custom kernels (all of them were said to be completed install) but I was stuck at Google.
So I tried to flash a stock kernel (I downloaded it from here, sorry for hotlink-ing from another forum: http://droidbasement.com/asus/razor/flo/sys-backup/jb-4.3_ota-full_n7_razor-flo.zip). I will also uploaded the stock kernel file extracted from that link in case somebody needs it but doesn't want to download the whole Stock ROM.
The file extension is .img, so for people not knowing how to flash this file, use this command
"fastboot flash boot <the file name.img>"
Thanks again.
Here is the llink to the stock kernel for N7(2013). it's 16Mb so I can't attach it.
http://www.mediafire.com/download/8t7lu3jc00mt0b9/bootN7.img
Hi ,
I installed CWM and I took the backup of the stock rom.
then flashed with new boot.img and installed MIUI rom, this is working fine.
I did wipe data/factory reset, wipe cache partition and Wipe Dalvik Cache. after that I restored stock rom using CWM, restore went fine.
when I reboot phone stuck in boot loop with htc logo.
did I miss something while restoring ????
glaber said:
Hi ,
I installed CWM and I took the backup of the stock rom.
then flashed with new boot.img and installed MIUI rom, this is working fine.
I did wipe data/factory reset, wipe cache partition and Wipe Dalvik Cache. after that I restored stock rom using CWM, restore went fine.
when I reboot phone stuck in boot loop with htc logo.
did I miss something while restoring ????
Click to expand...
Click to collapse
If your phone is not S-Off then restore can't update boot partition and you have to flash old boot.img manually.
The same way as you did when installing MIUI rom but different kernel image (boot.img compatible with stock rom).
kvestas said:
If your phone is not S-Off then restore can't update boot partition and you have to flash old boot.img manually.
The same way as you did when installing MIUI rom but different kernel image (boot.img compatible with stock rom).
Click to expand...
Click to collapse
My Phone has s-on....
I will find the stock rom supported kernel and flash before restoring the stock rom.
or
I will try to make s-off and restore.
either of one would be fine rite?
thanks:good:
glaber said:
My Phone has s-on....
I will find the stock rom supported kernel and flash before restoring the stock rom.
or
I will try to make s-off and restore.
either of one would be fine rite?
thanks:good:
Click to expand...
Click to collapse
Yes, either should be fine., but the first method is much more easier I guess.
---------- Post added at 09:28 AM ---------- Previous post was at 09:26 AM ----------
And you may flash the right kernel even after restoring or flashing a rom.
kvestas said:
Yes, either should be fine., but the first method is much more easier I guess.
---------- Post added at 09:28 AM ---------- Previous post was at 09:26 AM ----------
And you may flash the right kernel even after restoring or flashing a rom.
Click to expand...
Click to collapse
Thanks dude..
I got my phone back