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.
Related
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?!
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
Ok guys, these are modded versions of TDJ's tools to add the preload partition. This should allow you to wipe cache and dalvik without jacking up the symlinks. Also for you guys having issues installing a ROM, the superwipe should fix that. First flash the ROM and reboot (important), then if you are having issues flash the super wipe and then the ROM again. Reboot and you should be good.
Thanks again TDJ!!! You rock bro.
Note to other developers: Feel free to link here from your thread, just don't re-upload them please. Thanks
Everyone else: if you see these uploaded anywhere else please let me know. I have no problem with others linking to these but do not want them uploaded anywhere else.Thanks
Saved. . . . . . .
One more. . . . . .
I'm awesome
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
thx for this, i was annoyed by the preload problem.
Is this for CWM recovery or TWRP as well?
Sent from my SGH-T989 using xda app-developers app
Will work for both.
Thanks Jamison this will solve alot of headaches!
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
euklid said:
So whenever we want to wipe cache/dalvik use zip file instead of built in twrp??
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
If on a TMo based 4.1.2 ROM, yes.
Whats the difference between the two downloads?
inpherknow said:
Whats the difference between the two downloads?
Click to expand...
Click to collapse
One is cache/dalvik, superwipe is data/factory reset.
Well before using the scripts ROM would not boot but after super wipe no problems, TWRP 2.5.0.0 :thumbup:
Sent from my SGH-T989 using xda premium
Jamison-does the cache wipe also fix permissions?
Sent from my SGH-T989 using xda app-developers app
Yes it does.
Sent from my dark hole called an office.
I used these scripts installing a ROM and I am having very serious issues. I was using Clockwork and when I rebooted I got stuck in a boot loop. I booted back into recovery but I was not getting fully back into recovery. I tried several times. I finally ODINed back to stock but I can't get the ****ing phone to boot up. It gets toa popup that says ""unfortunatley google partner setup has stopped" and then if I clear that "Google account manager has stopped", "google calender storage has stopped""unfortuantely the process com. android.phone has stopped". ****. I have tried ODIN to 3.5 stock and 4.0.3 both having similar issues.
Anyone have any idea, may have absolutley nothing to do with these scripts but any ideas would be very much appreciated.
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Jamison904 said:
What are you running and what are you trying to flash? Wouldn't be the scripts as they only wipe, format, align the partitions.
Sent from my dark hole called an office.
Click to expand...
Click to collapse
I was running CWM 6.0.2.9 touch and trying to flash the StockWalk ROM. I don't know if you have seen something like this before but it seems like I am totally unable to install any GAPPS even when flashing stock ROM in ODIN. I had flashed the same ROM before attempting to use the scripts, the reason was that I was unable to add my google account (may be a defect in the ROM but others are saying they have not had issue).
*when I say install GAPPS I am just refering to the ones that install on TW ROMS, I am not flashing a GAPPS file of any kind
ArcticFish said:
thx for this, i was annoyed by the preload problem.
Click to expand...
Click to collapse
blackangst said:
If on a TMo based 4.1.2 ROM, yes.
Click to expand...
Click to collapse
OK so I thought I knew enough to not feel like a noob, but here I am with three questions.
First question is what is a "preload problem"?
Second question is this will only work on 4.1.2, and not 4.2.2 (CM 10.1)?
And the third question is will using the original DS wipes mess something up?
T mobiles 4.1.2 loads a preboot partition. Wiping cache with anything but these scripts also wipes these partitions. This script is modified to not do that. No preboot partition = boot loop.
Thus, if you're on anything BUT Tmobiles 4.1.2 you don't need this script and there's no advantage to using it.
Sent from my SGH-T989 using xda app-developers app
I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
XxLostSoulxX said:
I was wondering how in the hell do i get updated to all the new updates and such.
Currently i'm rooted with Twrp 2.3.1.0, i used the toolkit back some time ago and game me the option to basically install custom roms and such but never did anything except for a kernel.
So my question is Im still on LJC, 4.1.1, and i'm sick of the pop ups for the install update, and i know its going to fail so i'd figure can i just install a custom rom and it will take care of all that crap like for instance just go ahead and start fresh and install CyanogenMod?
Click to expand...
Click to collapse
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
That could be an option if you're looking to move over to AOSP but if you wanted to stick with TW you could always just flash a ROM based off stock 4.1.2, MA7 or MC2.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
XxLostSoulxX said:
Well i tried to install CM 10 getting stuck at bootani its seriously pissing me off. i wiped everything and followed directions and nothing is working
Click to expand...
Click to collapse
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
LuigiBull23 said:
Will need more info, like your exact installation process to help you any further.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Click to expand...
Click to collapse
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
When you say CM 10 I'm assuming you're referring to CM 10.1? If so make sure your using the correct gapps and if you still face issues I suggest redownloading the ROM and gapps through Goomanager, make sure the MD5 match up, and then fully wipe and flash again. Keep me updated.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file
XxLostSoulxX said:
Click to expand...
Click to collapse
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
XxLostSoulxX said:
Yess 10.1, and yes i did exactly as it says im uploading a youtube video for you to watch so you can see what im doing exactly.
Just followed Rootbox instructions as i just literally tried that rom out, and same results. i cant match the md5 as it skips it during install process as it says there is no md5 file
Click to expand...
Click to collapse
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Thanks. I'll watch it and get back to you asap.
Sent from my Nexus 4 using xda premium
---------- Post added at 02:36 AM ---------- Previous post was at 02:06 AM ----------
Ok I see what you're doing. My brother had a similar problem and there seems to be something wrong with the kernel script not running through properly and to fix this you will need to perform a factory reset as the OP instructs BUT I would try it twice. Once before the flash and another after the flash. Try it and if that doesn't work try the same steps with a 3rd party kernel. Flashing a kernel after the ROM is not recommended but if it helps to boot up the phone then you'll know it was the stock kernel. Let me know
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
XxLostSoulxX said:
tried with 3rd party kernel i.e matrix kernel and nope still not working WTF.
Click to expand...
Click to collapse
No AOSP ROMs at all? I would go back to complete stock, update to MA7 or MC2 then reroot and try flashing again.
Sent from my Nexus 4 using xda premium
XxLostSoulxX said:
Okay Well i wiped(factory reset under TWRP 2.5) then did advanced wipe and chose system option; then wiped. Then i had flashed CM10 then after flashed GApps, rebooted and bam into bootloop, and as i typing this i 'm doing the avatar rom and same thing bootloop. also i should mention it skips the md5 check and says there is no md5 file.
Just tried rootbox same thing gets as far as the boot ani then bam sits there
Click to expand...
Click to collapse
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Skripka said:
Wipe 3X. Data, System, cache, Dalvik.
Anything less and you're bound to get problems.
Click to expand...
Click to collapse
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
XxLostSoulxX said:
i did; wiped data 3x, system 3x, cach and dalvik 3x, installed cm 10.1 then right after Gapps but again says skip md5 check there is no md5 file and bootloops on CM 10 boot animation
Click to expand...
Click to collapse
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Skripka said:
Does it bootloop...or have you just been impatient? 1st boots of a new ROM can take a while.
Presuming it is stuck at boot splash...either an unstable build, or a corrupt download are possible. Verify the MD5 of your downloads.
Click to expand...
Click to collapse
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
okay i used Toolkit 4.1.0 and chose to flash to stock and it didnt work because i still have root and still on ljc, and same setup as before, i cant update to ma7, however i chose to install stock recovery, but i know if i do update it will fail.
EDIT: **** it wont even reboot to install the update. says rebooting now and nothing. F THIS PHONE.
I CANT EVEN UNROOT
XxLostSoulxX said:
did you watch my video? it was sitting for 5 minutes,on the cyanogenmod boot animation.
i just restored and back on ljc perfectly fine. but i guess my phone does not like flashing as i said and in the video it hangs and skips the md5 check
Click to expand...
Click to collapse
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Every device handles things differently, including first boot up times. It can take anywhere from 5-10min. So don't worry about how short Josh's boot up time was in his video. I highly suggest you:
1) Wipe system, data, cache/dalvik 3x
2) flash ROM and Gapps
3) Go back and perform a "factory reset" 3x
4) Reboot
5) Let phone sit at most 15min.
Just do this one final time exactly as instructed and assuming you've tried earlier nighties, if it doesn't boot up by 15 min then you'll know it's the phone and NOT you.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
XxLostSoulxX said:
what do i do if its the phone? i cant even unroot, i cant even flash to stock WTF! tried using toolkit but nothing. only thing i accomplished was being able to install stock recovery, and went back into android and chose to reboot to install update from OTA wont even reboot when it says rebooting now.
Click to expand...
Click to collapse
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
LuigiBull23 said:
Ok... Do you still have that LJC nandroid backup?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
correct yeah because i restored so i can atleast use my phone to try to fix it using toolkit
EDIT: Hooray i finally got it that did the trick this time. however basband is still LJC but is 4.2.2 because i went through setup this time and was able to boot up
Hi all. I'm going absolutely crazy over here. I have an i747 and I rooted it, no problem. The problem that I am having is that I'm currently running 4.1.2 and for the life of me, cannot figure out how to get it to 4.2. I've tried installing CM10, but every time I try and flash it in CWM, I get a E: Error in /emmc/cm10.zip (Status 7). I've tried installing other 4.2 ROMs like Paranoid Android etc, but get the same/similar error. I can flash other custom ROMs, like Alliance and such. I'm sure I'm over thinking this and just need a fresh set of eyes on the issue and a point in the right direction here. Your help is much appreciated.
What version of cwm are you running?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
jon_yarbrough said:
Hi all. I'm going absolutely crazy over here. I have an i747 and I rooted it, no problem. The problem that I am having is that I'm currently running 4.1.2 and for the life of me, cannot figure out how to get it to 4.2. I've tried installing CM10, but every time I try and flash it in CWM, I get a E: Error in /emmc/cm10.zip (Status 7). I've tried installing other 4.2 ROMs like Paranoid Android etc, but get the same/similar error. I can flash other custom ROMs, like Alliance and such. I'm sure I'm over thinking this and just need a fresh set of eyes on the issue and a point in the right direction here. Your help is much appreciated.
Click to expand...
Click to collapse
Status 7 is an out of date recovery, so make sure that's updated.
Also the newest cm10 and aokp and Pac man need updated bootleggers. Check the cm10 thread for the links to the Odin files.
http://forum.xda-developers.com/showthread.php?p=41535366
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
jon_yarbrough said:
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Read up on what the status 7 error means. Also, I would recommend switching from CWM to TWRP.
jon_yarbrough said:
I'm running cwm 5.5.0.4
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Cwm is up to 6.0.2.8
Just needs an update.
http://forum.xda-developers.com/showthread.php?p=38962585
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
xBeerdroiDx said:
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
Click to expand...
Click to collapse
Lol I did the same thing last time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Lol I did the same thing last time.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hahaha. I thought that was you. Cheers, KorGuy!
Thanks all. I just went into ROM Manager and updated CWM to the current version of 6.0.3 and it worked like a freakin' charm. I will be sure to hit THANKS for you all. Thanks again.
xBeerdroiDx said:
Cwm is actually sitting currently at 6.0.3.1. Here is the latest cwm flashable zip: http://forum.xda-developers.com/attachment.php?attachmentid=1888710&d=1366136727
Flash this in cwm, go to advanced, select reboot recovery. Once back in, make a new backup.
Before you flash a 4.2 rom from 4.1, wipe everything. Save everything you want to an sd card or your PC. Place your desired rom and gapps on a micro sd card. Wipe data, wipe cache and dalvik. Format /system and /data. Flash rom and gapps.
Click to expand...
Click to collapse
It's actually 6.0.3.2 now, but you have to build it yourself to get it as the latest released version is still 6.0.3.1.
https://github.com/CyanogenMod/andr...mmit/6f8d24d326258f2293436c50caca1c50eccab329
klin1344 said:
It's actually 6.0.3.2 now, but you have to build it yourself to get it as the latest released version is still 6.0.3.1.
https://github.com/CyanogenMod/andr...mmit/6f8d24d326258f2293436c50caca1c50eccab329
Click to expand...
Click to collapse
:laugh:
It's not a release until it's released.
Cheers, klin