issues installing JB, help... - Samsung Galaxy Nexus

Hi there everyone
have a weird issue... tried searching and nothing
ok, so i installed the first ROM of bigxie . everything went fine and nothing went wrong in any ways...
i then tried to install v2 of the ROM that came out a couple days later... and it wouldnt boot past the google writing screen... no matter what i do it wont boot into android... i have dont the wipe data, cache, dalvik etc... this isnt my first rodeo lol
i have tried flashing other jelly bean ROMs an nothing... i can restore to my previous ICS perfectly fine but nothing will load JB...
i have tried to restore with Odin but now in bootloader windows wont detect the phone at all... i have kies installed and have separately installed the drivers, nothing is making Odin see the devices, so i cant even use odin to restore to a factory image...
i have the latest bootloader installed and have the latest touch CWM installed as well... currently running the latest kernel from franco and using aokp 40
this is not making any sense to me and i need help to get my device back to JB, as ICS i cant stand anymore LOL
thanks for you help in advance!

http://forum.xda-developers.com/showthread.php?t=1626895

thank you for the link that helped me get the drivers working properly again.
my issue is i cannot load any JB roms at all, via CWM or otherwise... however i can still load ICS roms without issues...
and i still cant get odin to see my device at all, yet galaxy nexus toolkit works fine! ugh... lol i cannot load any OEM images at all... even the nexus toolkit doesnt want to load a OEM image to the device....
thanks again!

c_86 said:
thank you for the link that helped me get the drivers working properly again.
my issue is i cannot load any JB roms at all, via CWM or otherwise... however i can still load ICS roms without issues...
and i still cant get odin to see my device at all, yet galaxy nexus toolkit works fine! ugh... lol i cannot load any OEM images at all... even the nexus toolkit doesnt want to load a OEM image to the device....
thanks again!
Click to expand...
Click to collapse
I have the same problem ics rom work perfectly but jb roms get stuck in the Google screen or the X screen and I tried leaving it alone for a while but it drains the battery and turns off

@ c_86 and kingviper10: not sure what you guys are trying to do, but instructions on how to flash stock images are in the first post of the thread I linked to, and instructions for JB are in the second post. Not sure why you are talking about Odin or toolkits...
Sent from my Galaxy Nexus using Tapatalk 2

Are you sure you have cwm5.5.0.4 installed? NOT the touch version?

SikkNazty said:
Are you sure you have cwm5.5.0.4 installed? NOT the touch version?
Click to expand...
Click to collapse
I'm pretty sure he did say that he was on the touch version of CWR .

@efrant
i am talking about toolkits and odin because i cannot flash a jelly beam rom, OEM or otherwise via CWM at all... thats the issue...
to the other, i have i think 5.8.0.2 touch ClockworkMod Recovery
ugh this is so frustrating... lol i dont understand what is going on....

c_86 said:
@efrant
i am talking about toolkits and odin because i cannot flash a jelly beam rom, OEM or otherwise via CWM at all... thats the issue...
to the other, i have i think 5.8.0.2 touch ClockworkMod Recovery
ugh this is so frustrating... lol i dont understand what is going on....
Click to expand...
Click to collapse
Then you are doing something wrong. Did you follow the instructions in the link I provided you?

Lol like I said. This isn't my first time flashing...
I download the rom. The fix. The radio.
Wipe data
Wipe cache
Wipe dalvik
Flash rom
Flash fix
Flash radio
Wipe cache
Wipe dalvik
Not doing anything wrong... at least I'm pretty Dam sure I'm not.
Sent from my Galaxy Nexus using Tapatalk 2

c_86 said:
Lol like I said. This isn't my first time flashing...
I download the rom. The fix. The radio.
Wipe data
Wipe cache
Wipe dalvik
Flash rom
Flash fix
Flash radio
Wipe cache
Wipe dalvik
Not doing anything wrong... at least I'm pretty Dam sure I'm not.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is "the fix" you are talking about?
And use this recovery, not the one you are using. (The touch one is not entirely stable, even koush said so, so I have no idea why people insist on using it...)

Did you fix permissions after flashing the ROM and fix?
Try factory reset, wipe cache, dalvik cache, wipe system, then install ROM and fix, then fix permissions, then reboot.
Sent from my Galaxy Nexus using xda premium

Thanks I'll try that recovery and see if that works. I'll report back later.
As for fixing permissions. Yes I've tried that as well. No luck either.
Sent from my Galaxy Nexus using Tapatalk 2

c_86 said:
Lol like I said. This isn't my first time flashing...
I download the rom. The fix. The radio.
Wipe data
Wipe cache
Wipe dalvik
Flash rom
Flash fix
Flash radio
Wipe cache
Wipe dalvik
Not doing anything wrong... at least I'm pretty Dam sure I'm not.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Why do you wipe cache and dalvik cache twice?
707BeastMode707 said:
Did you fix permissions after flashing the ROM and fix?
Try factory reset, wipe cache, dalvik cache, wipe system, then install ROM and fix, then fix permissions, then reboot.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
This makes more sense. And yeah, try the recovery image efrant kindly linked you to, i didnt have any issues with twrp 2.1.2 either, if i may.
sent from my i9250

ooook... no go on that recovery image either...
i flashed the 5.5.0.2 recovery and same issue... will not boot past the google writing screen... i really dont know what else to do...
anyone?!

Related

T989Kang ROM wont boot

http://forum.xda-developers.com/showthread.php?t=1786202
when trying to install the rom from that thread i get stuck at the boot animation even though i followed all the necessary instructions. what do?
Wipe cache and dalvik cache. When it boots go back to recovery and go advance > fix permission.
Sent from my Galaxy Nexus using xda app-developers app
i did that and it hasnt worked. i dont know whats causing it since i followed everything OP said to do
Bad download? Its happened to me before.
Sent from my SAMSUNG-SGH-T989 using xda premium
Mine too... bricked!
hey, i don't know if this will help with your rom, but i will tell you something that helped me.
i was having the same problem trying to install cm9. this is what to do. don't wipe with recovery.
use darkside super wipe. i run it twice. then flash rom. while still in recover flash darkside cache wipe, not super wipe!!
for some reason when i wiped with the tools inside recovery i would get bootloop. can't lie don't know why but i did this and it woked.
hope this helps..
YummyLaxatives said:
http://forum.xda-developers.com/showthread.php?t=1786202
when trying to install the rom from that thread i get stuck at the boot animation even though i followed all the necessary instructions. what do?
Click to expand...
Click to collapse
Have you tried.
Downloading rom again?
Are you doing a full wipe before installing?
Trying a Cache wipe using the darkside flash?
What recovery are you using?
Are you flashing anything with it, a kernel? or a mod?

[HOW-TO] Proper method to flash a ROM

First off if you're on ANY recovery that isn't CWM 5.0.2.7 you DO NOT NEED TDJS SUPER WIPE OR CACHE WIPE SCRIPTS!!!! Seriously stop flashing these people you're filling up threads with problems caused by both of these scripts and bad flashing methods. Here's how to PROPERLY flash a ROM..
If on CWM 6.0.x.x
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
If you're on a Cyanogenmod nightly a full wipe IS NOT REQUIRED. The proper method of dirty flashing is just wiping cache, ( NOT FORMAT CACHE IN MOUNTS & STORAGE )
wiping dalvik and flashing your ROM. Simple as that.
If using TWRP 2.2+ the steps are essentially the same or use TDJs wipe scripts. They work perfectly fine with TWRP. Feel free to wipe 2x or even 3x if it makes you feel safer about your installation.
And THAT'S IT. People are cluttering up threads with issues than can totally be avoided by flashing the right way. I hope this helps some of you iron out these insane tiny quirks I keep reading about.
Happy flashing folks.
EDIT:
I forgot to note.. if you're still using one of TDJs roms or any other rom that automatically wipes with TDJs SUPER CACHE WIPE, do NOT use any other recoveries other than CWM 5.0.2.7 or TWRP 2.2+. With any other recovery such as CWM 6.0.x.x+, the wipe script breaks the roms ability to reboot properly and the only way to solve this is to use TDJs CACHE WIPE which in turn breaks your recoveries ability to work properly.
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks man this was needed. Yes threads get filled with this so often. I dirty flash like you mentioned accept I format system first. I also clean flash like you mentioned but never formatted cache and dalvik just system. That's good to know. Thanks
But I will add those new steps. I format system when dirty flashing because on the cm10 Site they mentioned that.
Again thanks
Sent from my SAMSUNG-SGH-T989 using xda premium
I edited OP with a little bit more information for safer flashing.
Sent from my SGH-T989 using xda premium
Sad we need to keep telling people how to flash. If you are not sure what you are doing I think you should be very careful before you destroy your expensive toy. Everyone should have an idea on how to flash and restore from a bad flash before they even root. Also as my sig says let Google be your friend people if you run into issues instead of running to a thread and clogging it up...
Thanks for post and this is a bump to keep it on page 1 and hopefully more people will notice it.
So I messed up and used the darkside scripts with 6.0.1.4 and I can't get my phone to boot, like you mentioned. It also destroyed the recovery, does nothing at all. What can I do, if anything, to fix?
Goofy317 said:
So I messed up and used the darkside scripts with 6.0.1.4 and I can't get my phone to boot, like you mentioned. It also destroyed the recovery, does nothing at all. What can I do, if anything, to fix?
Click to expand...
Click to collapse
Can you boot into recovery at all? If you can.. download the TWRP 2.2.2.0 zip in its thread and flash it. Its going to hang in the install process but should say twrp has been installed. At that point reset your phone by holding the power button. As soon as you feel the phone vibrate hold down both volume buttons and you should boot into TWRP recovery.
Sent from my SAMSUNG-SGH-T989 using xda premium
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
tickerman said:
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
Click to expand...
Click to collapse
Darkside superwipe will only mess your ROMs ability to reboot on touchwiz ROMs. The only way to fix this is flashing the darkside cache wipe which WILL break clockwork mod 6.0.1.4 like the user above. Point is.. don't use either scripts at all on CWM. Wipe the old fashioned way.
Sent from my SAMSUNG-SGH-T989 using xda premium
tickerman said:
I have been using the darkside wipe! It has been working great. I don't think that it will brick my phone or anything.....
Click to expand...
Click to collapse
I agree. even after switching to twrp I still find the script useful. But op warning about using script with cwm version 6xxx might be true. I have issue with boot when i was on cwm 6 and i had to Odin cwm 5.0.2.7 again to get into recovery menu.
Sent from my SGH-T989 using xda app-developers app
Thanks, always forgot the formatting steps
ultratt said:
Thanks, always forgot the formatting steps
Click to expand...
Click to collapse
Never forget those! Those completely format your partitions.. like formatting a hard drive before you install Windows.
Sent from my SGH-T989 using xda app-developers app
RushAOZ said:
Never forget those! Those completely format your partitions.. like formatting a hard drive before you install Windows.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the guide. One question, how do you format partitions on TWRP? Do you need to?
Davy Jones said:
Thanks for the guide. One question, how do you format partitions on TWRP? Do you need to?
Click to expand...
Click to collapse
Luckily enough, TWRP does this in the wipe section already when you hit system, cache and dalvik. Its an awesome and well thought out recovery!
Sent from my SGH-T989 using xda premium
RushAOZ said:
Luckily enough, TWRP does this in the wipe section already when you hit system, cache and dalvik. Its an awesome and well thought out recovery!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Oh cool, I was already really liking TWRP and this makes it even better.
This thread should be a sticky.
Khameleon said:
This thread should be a sticky.
Click to expand...
Click to collapse
Agree.
Sub'n.
I just followed this and it answers many questions. I have great luck with CWR 5.0.2.7 and the darkside scripts. Everytime I had an issue, I would run the darkside cache script and all was fixed.
Now, since I upgraded CWR, I have had issues installing ROMS, bad recovery installs, etc. Just as you mentioned.
Got a new phone today. Flashed an odin CWR (didn't know the version). It turned out to be an older touch version. I CWR flashed the latest Sk8's recovery. I then followed your instructions. Installed JB ROM and Gapps and it was a success. Not boot loop.
Questions: What do I do if I want to wipe cache and dalvik or fix permissions in the future? What radio is recommended with the latest JB nightly?
apicia said:
Agree.
Sub'n.
I just followed this and it answers many questions. I have great luck with CWR 5.0.2.7 and the darkside scripts. Everytime I had an issue, I would run the darkside cache script and all was fixed.
Now, since I upgraded CWR, I have had issues installing ROMS, bad recovery installs, etc. Just as you mentioned.
Got a new phone today. Flashed an odin CWR (didn't know the version). It turned out to be an older touch version. I CWR flashed the latest Sk8's recovery. I then followed your instructions. Installed JB ROM and Gapps and it was a success. Not boot loop.
Questions: What do I do if I want to wipe cache and dalvik or fix permissions in the future? What radio is recommended with the latest JB nightly?
Click to expand...
Click to collapse
Just go into CWM and wipe cache in the main menu and dalvik in the advanced menu. To be honest though you don't need to do this whatsoever. Only when dirty flashing a new nightly. In my experience atleast lol as far as gapps go..
http://goo.im/gapps/gapps-jb-20121011-signed.zip
These should work just fine
Sent from my SAMSUNG-SGH-T989 using xda premium
Bump fer new users yo
Sent from my SGH-T989 using xda premium
Bump for new users
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks

[Q] (status 7) some symlinks failed when installing ROMs.

when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Edit: Thanks for all the help guys. I'm still having this problem.
Things i have tried: go into mounts and remove the top X on the list.(TWRP)
flashing a stock kernel gets me stuck in a boot loop.
I am using the franco kernel and had this same issue using CWM before switching to TWRP.
You can try this...
simms22 said:
try booting out of recovery into the bootloader, then back to recovery to reflash.
Click to expand...
Click to collapse
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
qbanlinxx said:
If you do a Google search you should find some information on it. Its something with the Franco kernel changing the sdcard. Have to download And move the original back into it's correct place
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
natheist411 said:
when trying to install a new rom i get the same error (status 7: some symlinks failed) with the cm10 and eclipse ROMs. I don't seem to have any trouble with Buglessbeast and euroskank. I have googled and searched XDA but none of the other threads are for the toroplus.
Click to expand...
Click to collapse
Are you using TWRP recovery? If you are that's the issue. The latest update has a flaw, you have to go into recovery, go into mounts and remove the top X on the list. They said they where working on releasing a correction for it. If your not on TWRP then I don't know what's going on.
Sent from my Galaxy Nexus
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
natheist411 said:
I was using cwm but switched to TWRP to retry. Same issue.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
bk201doesntexist said:
Huh?
Op never even made mention to the word "kernel" in his post.
Not to mention kernel is not even running in recovery (which itself is a small os).
Sent from my i9250
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda premium
qbanlinxx said:
I had this same issue yesterday, and it was related to flashing a kernel. Sorry for trying to help
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have also seen something similar. What most people don't realize is the some kernels, including Franco, change things in /system as well, which messes with some things.
Sent from my Galaxy Nexus using Tapatalk 2
Okay, thanks. I was not aware of this. Will checkout some kernel zips to see what's going on.
edfunkycold said:
Try it when you get into recovery, go to mounts, remove the X on the top option on the list then flash the rom see if it works.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I tried this. Still the same outcome. Thanks anyways.
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Milamber said:
Has this been fixed? I cant install any ROM!
I have exactly the same problem! I am using stock kernal, was using franco kernal before that.
Click to expand...
Click to collapse
no one here was help but i think i figured it out myself.
try this and see if it works.
when you go to install the rom, before doing so wipe data (factory reset) three times.
i was so frustrated about it i finally said **** it and didnt care if i lost everything, but i didnt loose anything so all is well.
let me know if that works
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
I'm tryied many recoveryes and kernels, but the problem is in copying process(now all zip's have good CRC, and MD5). . Give me a beer
JeyLo said:
(status 7) some symlinks failed
I'm fixed this problem, PLEASE ADD THIS POST TO FAQ . Just install Android Commander and copy ROM to phone via it, now i'm on JellyBam android 4.1.2.
1.Install root+busybox.
2.Install via stock recovery siyah 5.0b2
3.In siyah recovery do factory reset
4.Flash any custom ROM
5.Do factory reset, wipe cache, wipe Dalvik cache.
6.Be happy, enjoy.
Click to expand...
Click to collapse
Huh? What is siyah 5.0b2???
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Milamber said:
Huh? What is siyah 5.0b2???
Click to expand...
Click to collapse
He's on a different device.
Sent from my i9250
chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Wipe/Factory reset does not touch the system partition at all. This is normal. It only wipes the userdata partition.
chrisjenx2001 said:
I did a manual "format /system" from Clock Work Recovery, fixed it for me, Seems the Wipe/Factory reset does not reset the system partition correctly for some strange reason.
This was an issue after a custom kernel.
Click to expand...
Click to collapse
Had a bad download and on initial install I formatted system however it failed. Went back and formatted system and cache manually and worked for me.
I'm not sure if this is related, but I read in the MMuzzy's Jelly Bean 4.2.1 thread (http://forum.xda-developers.com/showthread.php?t=1762846, first post specifically) that unmounting /system fixes this problem, and sure enough it solved the problem for me when I tried to flash that ROM.

CM10 M2 Bootloop Gnex

Need some quick help here. I unlocked and rooted my gnex. I have done this several times before and with all my other android phones. As soon as I rooted it, I flashed the new 4.2 gapps package. Upon booting, the launcher would not respond and thusly I could not access my home screen or app drawer. I had to open my apps from the google now target on the lock screen. As I read more, I heard not to flash the 4.2 gapps unless you have flashed another rom.
So I went to chrome, dl'ed the cm10 m2 zip, went into rom manager and flashed the cm10 and 4.2 gapps again. Now upon booting, the cyanogenmod icon is bootlooping, and has been for the last ten minutes. I went back into recovery and tried the process again, this time wiping the cache and dalvik, to no avail...same bootloop.
Please help!
Install a stock ROM using fastboot.....
Beamed from my Maguro.
If it helps at all, it's a Verizon galaxy nexus. Please help! Also if it is at all possible to save pictures, please let me know. Wiping would be my last resort.
Thanks
Mach3.2 said:
Install a stock ROM using fastboot.....
Beamed from my Maguro.
Click to expand...
Click to collapse
Is there a way of flashing stock that does not require a wipe?
Also I did make a nandroid of the stock rooted rom, but for some reason, after flashing that, the cyanogenmod logo stilled appeared at boot...
swimman2867 said:
If it helps at all, it's a Verizon galaxy nexus. Please help! Also if it is at all possible to save pictures, please let me know. Wiping would be my last resort.
Thanks
Click to expand...
Click to collapse
U need to wipe cache/dalvik/factory reset/system(u need to do this every time before flashing a ROM) , do it like 3 times and re-flash ROM. Don't worry about ur photos, they r in the internal memory and u don't need to wipe it, so u won't lose them.
Sent from my Galaxy Nexus using xda premium
Which file did you flash? You could've used the 'maguro' (GSM) one instead of the 'toro' (Verizon) one
pr0xyw0rm said:
U need to wipe cache/dalvik/factory reset/system(u need to do this every time before flashing a ROM) , do it like 3 times and re-flash ROM. Don't worry about ur photos, they r in the internal memory and u don't need to wipe it, so u won't lose them.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When you factory reset, the entire phone is wiped, no? And how can I factory reset from recovery?
EddyOS said:
Which file did you flash? You could've used the 'maguro' (GSM) one instead of the 'toro' (Verizon) one
Click to expand...
Click to collapse
I was sure to flash the toro file. I don't believe that is the problem.
swimman2867 said:
When you factory reset, the entire phone is wiped, no? And how can I factory reset from recovery?
.
Click to expand...
Click to collapse
Nope. Factory Reset doesn't wipe the internal SD. It should be located inside the wiping options(I'm using TWRP recovery). Anyways u should wipe cache/dalvik/factory reset/system before flashing a ROM not just factory reset.
Sent from my Galaxy Nexus using xda premium
adb pull /sdcard in recovery
download stock image from Google and flash
https://developers.google.com/android/nexus/images
fastboot oem lock
Got home from class, wiped cahce, dalvik, and data, flashed cm10 m2 and gapps 4.2. Everythings great and I still have my pics. Thanks guys
It was just taking that plunge of wiping data that was freaking me out. I had some pics that i absolutely could not lose, but after reading on it more, it makes sense that the wipe would not format the internal sd.
Thanks again!
swimman2867 said:
Got home from class, wiped cahce, dalvik, and data, flashed cm10 m2 and gapps 4.2. Everythings great and I still have my pics. Thanks guys
It was just taking that plunge of wiping data that was freaking me out. I had some pics that i absolutely could not lose, but after reading on it more, it makes sense that the wipe would not format the internal sd.
Thanks again!
Click to expand...
Click to collapse
U r welcome. I'm glad to hear that.
Sent from my Galaxy Nexus using xda premium

[Q] Doing something wrong trying to flash JB

I've installed ROMs before so I'm not a complete noob, but I'm clearly doing something wrong and would like some help.
I've tried installing 3 different JB ROMs (Kobridge tweaked FL04, Jellyverse0.3, JB Black Bean) and everytime I boot up into the Sprint animation and it hangs every single time at the big 4G. I'm coming from BluKuban which I return to every time after flashing EL29 direct boot through pc Odin.
This is what I've been doing:
Installed EL29 direct boot or EL26 stock
cleared cache, davlik and run Format_All_X2
Installed JB modem
installed ROM
run Format All X2 again
A couple of files might be different depending on the ROM instructions, but that's what I've been doing.
Any ideas what I'm doing wrong?
flamand said:
I've installed ROMs before so I'm not a complete noob, but I'm clearly doing something wrong and would like some help.
I've tried installing 3 different JB ROMs (Kobridge tweaked FL04, Jellyverse0.3, JB Black Bean) and everytime I boot up into the Sprint animation and it hangs every single time at the big 4G. I'm coming from BluKuban which I return to every time after flashing EL29 direct boot through pc Odin.
This is what I've been doing:
Installed EL29 direct boot or EL26 stock
cleared cache, davlik and run Format_All_X2
Installed JB modem
installed ROM
run Format All X2 again
A couple of files might be different depending on the ROM instructions, but that's what I've been doing.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Don't flash format all zip after flashing rom zip.
You are wiping system right after flashing rom so there is no system and thus you don't boot.
Sent from my SPH-D710 using xda app-developers app
Thanks for the suggestion, but format_all_x2.zip just wipes data, cache and dalvik, doesn't it? I use it all the time when reflashing Ruj's BluKuban.
BluesRulez said:
Don't flash format all zip after flashing rom zip.
You are wiping system right after flashing rom so there is no system and thus you don't boot.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
flamand said:
Thanks for the suggestion, but format_all_x2.zip just wipes data, cache and dalvik, doesn't it? I use it all the time when reflashing Ruj's BluKuban.
Click to expand...
Click to collapse
It wipes system, not dalvik.
flamand said:
Thanks for the suggestion, but format_all_x2.zip just wipes data, cache and dalvik, doesn't it? I use it all the time when reflashing Ruj's BluKuban.
Click to expand...
Click to collapse
Its not a suggestion. Its your FIX. It wipes system. I hope you are not confusing format all x2 zip with modified_format all zip. The modified zip wipes only the caches.
As such there is NO need to wipe after flashing the ROM..
Are you following the directions on the OP of each ROM?
If not... do it, that is how you fix your problem.
Sent from my SPH-D710 using xda premium
Yes I am, unless I'm misunderstanding something. That list is what seemed to be in common to all three.
I'll try to do it again tomorrow when I have a few hours.
Mattix724 said:
Are you following the directions on the OP of each ROM?
If not... do it, that is how you fix your problem.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse

Categories

Resources