I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
berdo said:
I have an AT&T Note that I rooted using the Odin method. I was running stock ICS and I know the root worked because I was able to install Google Now and it worked fine.
So I decided I wanted to try a different ROM. I just wanted to install bigfau's cleaned up stock rom found here. I put the zip file on my phone, booted into CWM, did a wipe, found the zip, said it installed fine and then I rebooted. At boot it just sits at the Samsung screen. I let it sit for 30 minutes, still nodda.
So I grab odin and flash back to stock ICS. Use the same method to root and I try a different ROM. This time the Pure Stock ICS from bigfau, same problem.
Odin back to stock, root, and I try parandoidandroid found here - same problem.
Do it all again and try a ROM from another site called HYFR Only One, which is a SGS3 based rom. Same deal.
The only thing I can get it to do is ODIN to stock. Am I missing something?
(I have another rooted galaxy note that I do not have any issues with flashing roms but it was already rooted when I got it.)
Click to expand...
Click to collapse
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
btw there is a Q&A section.
bigjoe2675 said:
Rooted has nothing to do with flashing a ROM, having CWM or TWRP will give you the cap to flash a ROM.
I have used these Recovery types for flashing:
Touch CWM: http://forum.xda-developers.com/showthread.php?t=1584576
TWRP: http://forum.xda-developers.com/showthread.php?t=1647575
After you have CWM of some type ensure you are doing a clean wipe, this is how I perform my wipes:
1. Download to sdcard
2. Reboot to CWM-based Recovery
3. Wipe data/factory reset
4. Wipe Cache partition
5 Go into advanced> Wipe Dalvik Cache
6. Go into> Mounts & Storage
a. Format /data
b. Format /system
c. Format /cache
Install rom & Reboot
After the first boot up let it sit for a few min to build...then do your set ups.
Click to expand...
Click to collapse
I apologize if I did not make this clear but I have Rom Manager installed and CWM was updated to the latest version. I would reboot into CWM, do a factory reset, wipe cache, dalvik caceh, install rom and reboot. It would just sit at the samsung screen. I did not go into mounts and storage and do that but I will now. The process I use on my AT&T note is the same process I used on my Rogers note and I am able to install any ROM i want on my rogers note.
I have flashed roms probably over 100 times since my samsung captivate. I just didn't know if the note had another step involved. Like S-Off on HTC phones for example.
I have been using the standard version of cwm but I am trying the touch version now. Will update.
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
did you check if bootloader is unlocked?
berdo said:
Same problem. I am uploading a video to youtube now. I will post in a minute or so.
Click to expand...
Click to collapse
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
animatechnica said:
did you check if bootloader is unlocked?
Click to expand...
Click to collapse
elry567 said:
U have busy box installed?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Animatechnica - It is my understanding that the bootloader is not locked on the Galaxy Note. I have not seen anything about unlocking the bootloader in any thread on the i717.
elry567 - do not have busy box installed - never saw anything requiring it to be installed. I will try that as well.
Well this time I got a status 7 error in CWM which can be a lot of different things. I am up to date on CWM, the rom I know works for the galaxy note (I am running it on my other one AND I have seen video of it working on an AT&T branded Note) so I don't know. I did a google search on the error and everything I found does not seem to apply. It is really starting to piss me off. Any help is appreciated.
Here is the video, sorry about my cam skills but you get the gist. I took this video with a i717r that is running the rom I want to install on the phone in the video.
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
rangercaptain said:
Are you entering recovery with the phone off then using the buttons, or flashing from rom manager?
You should be doing it by the button method.
Click to expand...
Click to collapse
Done both, doesn't seem to make a difference. I will definitely use the button method from here on out though.
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Zwarx said:
Try using TWRP? It seems CWM doesn't want to work for you, so try using TWRP instead.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
+1
berdo said:
HOLY F&(%*&G $&!t twrp may have worked. I had to go full back to 100% stock with 3e recovery and 0 flash counter. Use a new root method, flash twrp via goo app and so far so good.
Seriously I do not know who you are but I could kiss you. I wonder why CWM wouldn't work? I have used it to load custom roms on just about every other android phone I have had.
OH well, consider this solved.
Click to expand...
Click to collapse
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
bigjoe2675 said:
+1
Sir, he is one of many, that is part of this great Community the GNote. As you can see we just provide the tools and point you to the way we went...it is up to you to get it going, and you did by the see of it....slap a thanks to all these that posted in your thread, (not me) due to the fact, I have seen threads go viewed many times that have no one replies to it, but not around here....
glad it worked out..
Click to expand...
Click to collapse
Done.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Related
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Mycotopian said:
Hey folks,
So the end of Q3 came with no ICS so I decided it was time to learn about modding these phones. I have modded Xboxes etc so I figured I would try to take this on.
My Phone:
AT&T MB860 bone stock with 4591 on it when I started.
I was able to unlock the phone following a tutorial on youtube. Then I tried to reflash CWM and CM7 using AUTOMATIC_UNLOCK_V4.2. Thats where things went wrong. The phone got stuck at the Dual core screen (to be honest I might not have waited 10 minutes after flashing).
So now here I am the battery is drained so I am using a cut off USB cable for power. When the phone is booting it says "unlocked" in the top left corner I can access all of the menus. When I choose recovery the phone boots into ClockWork Mod recovery. I am hoping I am half way there and the kind folks here can guide me to the finish. If not I'm open to starting from scratch whichever is going to be fastest. I'll attach a few pics for reference
Click to expand...
Click to collapse
(I went through this today, I needed to use option 6 in automatic unlock 4.2 before I could get a Rom on my phone.) this was wrong, tried so many things I got confused, go to this thread:
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5 in ATRIX android development
and download one of the zipped recoveries, flash through recovery to get a modified CWM that left me install a Rom. I was stuck at the same screen as you before I did this now I'm up and running with MROM.
Your recovery is too old. Get a newer version of CWM. Try flashing this. If you can't you will have to fastboot flash a newer recovery.
Flash ROMs with CWM, not automated tools. CWM is the safest way. As soon as you get a new recovery installed create a backup. Good luck!
okay guys I'm jammed up I download the file CWM_Atrix4G_5.0.2.0 and copied it to a clean microsd. Then I went through the recovery menu
Install zip from sdcard>choose zip from sdcard>
In the next folder list I am unable to find the CWM file. Any tips on how to get the file straight onto the phones internal flash? Maybe through RSD?
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
ravilov said:
Dude, you're trying to install recovery from the recovery... Doesn't really make sense, does it?
Use fastboot instead.
Avoid RSD at all costs.
Click to expand...
Click to collapse
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
upndwn4par said:
You can't do a first install of recovery from recovery. But you can update (assuming recovery is functioning - even partially).
Click to expand...
Click to collapse
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
ravilov said:
Yeah, I know. You posted a flashable ZIP, the only one I am aware of.
I'd still recommend a standard fastboot flash though.
Click to expand...
Click to collapse
Huh? The only one? Did you search?
upndwn4par said:
Huh? The only one? Did you search?
Click to expand...
Click to collapse
No... Not really.
Hey, I said "that I'm aware of".
ravilov said:
No... Not really.
Hey, I said "that I'm aware of".
Click to expand...
Click to collapse
I have flashed recovery with fastboot exactly once - when I unlocked by bootloader. Ever since it has been flashable zips.
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Mycotopian said:
Okay I successfully flashed the new recovery to v5.0.2. Then I chose "apply /sdcard/update.zip" I received the "Install from sdcard complete message" I then chose "+Go Back+" then "reboot". The phone rebooted and sat at the logo with "unlocked" in the corner for a few minutes. I thought maybe I needed to clear it by pulling the battery for a few seconds, which I did. then I let it sit on my desk for 20 minutes at the logo screen.
do need to go in and clear cache? is there another file I should try to flash?
Any input would be appreciated.
Click to expand...
Click to collapse
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
upndwn4par said:
You probably need to re-flash your ROM.
Wipe data, cache, Dalvik, then flash ROM.
Click to expand...
Click to collapse
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Mycotopian said:
I ran the wipe, cache, davlik then reran the update.zip.
I am still stuck at dual core screen with unlocked the corner.
Click to expand...
Click to collapse
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
ravilov said:
Umm... That would just install the recovery again. You need to flash a ROM. Seems like your boot partition (aka. the kernel) is borked.
Click to expand...
Click to collapse
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
I just installed CM7 on my Atrix last week. Don't forget to install gapps like I did. I had to install them as a zip from the recovery, but I think it's also possible to use the ROM Manager app.
Look for the Google Apps section on this thread: forum.xda-developers.com/showthread.php?t=1257574 This will have the Market (now Google Play) so you can download more apps.
After that, play with all the features! I started with Menu > Settings > CyanogenMod Settings and started playing around. Don't play with the performance settings without knowing what they do.
Also, Make a backup! Make a backup! Make a backup! It may save you when little else will.
Sent from my MB860 using xda app-developers app
Mycotopian said:
Success!
Thank you to everyone that helped.
Now that its done is there a link to outline what all my new perks and features are now that I am rooted and running?
Click to expand...
Click to collapse
Awesome! Enjoy!
I recently attempted to root my HTC thunderbolt, and to do so I used the htc dev unlocker and then this "HTC Thunderbolt Tool'
rootzwiki.com/topic/27310-all-in-one-the-htc-thunderbolt-tool
After that I downloaded a rom and installed it through the 4ext recovery, it all install fine and I did do a factory/data reset but whenever I reboot after the rom install, I get the HTC white bootloader and then the screen become black with a back light to it.
I have tried a number of times to re-install the rom and have tried to use other roms but all of them seem to end the same way.
I have used:
BAMF FOREVER 1.1
BAMF MECHA ICS
AIRBORNE GOUI
Killsense 3.7.19
Lightning501
few more
My phone is a HTC Thunderbolt and when I attempted to root the phone it had a hboot version of 1.0.8 and had a stock version of ICS installed.
Sadly I have a phone without a working rom and I had forgot to make a backup so if anyone can help it would be greatly appreciated. Preferably I would like to keep the phone rooted but its not necessary.
Thank You
I'm a total xda-developor noob, so I hope I didn't mis a thread with a the solution all ready on it.
Make sure you do the factory reset, wipe dalvik and cache. Flash the ROM and reboot. Sounds like your missing a step somewhere 8)
Sent from my ADR6400L using xda app-developers app
tburns said:
Make sure you do the factory reset, wipe dalvik and cache. Flash the ROM and reboot. Sounds like your missing a step somewhere 8)
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
I have tried clearing everything but still doesn't seem to work.
One thing I forgot to mention is sometimes if I wait long enough on the blank screen It boots me back into the 4ext recovery, don't know if that makes much of a difference.
The way I have been installing the rom
Load ROM onto the SD
Do a "wipe data/factory reset"
Go into install sd and choose the Rom which is in a .zip file
I think this is how its supposed to be done, but not sure.
aplysenko said:
I have tried clearing everything but still doesn't seem to work.
One thing I forgot to mention is sometimes if I wait long enough on the blank screen It boots me back into the 4ext recovery, don't know if that makes much of a difference.
The way I have been installing the rom
Load ROM onto the SD
Do a "wipe data/factory reset"
Go into install sd and choose the Rom which is in a .zip file
I think this is how its supposed to be done, but not sure.
Click to expand...
Click to collapse
You need to wipe cache and dalvik cache too.
Sent from my Nexus 7 using Tapatalk 2
disconnecktie said:
You need to wipe cache and dalvik cache too.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have done that.
Problem is you were coming from the ICS OTA.
The All In One Tool alone will not get you rooted after taking the OTA.
In order to fully root and s-off after having the OTA loaded, you would need to follow the steps outlined HERE
santod040 said:
Problem is you were coming from the ICS OTA.
The All In One Tool alone will not get you rooted after taking the OTA.
In order to fully root and s-off after having the OTA loaded, you would need to follow the steps outlined HERE.
Click to expand...
Click to collapse
Your link dont work for me, id assume you were pointing to this wonderful thread
Milimbar said:
Your link dont work for me, id assume you were pointing to this wonderful thread
Click to expand...
Click to collapse
Correct Thanks I fixed the link in my first post.
I am using the thread and so far its working, just one last question. Do I have to install and use 4ext, or can I just use clockwork mod?
aplysenko said:
I am using the thread and so far its working, just one last question. Do I have to install and use 4ext, or can I just use clockwork mod?
Click to expand...
Click to collapse
You can use whatever Recovery you want, Clockwork Mod is old and not really suggested to use, especially with newer roms.
I miss the RA recovery I had on my first bolt. I use the ext4 recovery now. Glad Santod was able to help you out!!
Sent from my ADR6400L using xda app-developers app
I have a p4wifi that is stuck in a boot loop. I think the term is 'soft bricked'.
Basically, last night I turned my tab on for the first time in ages, and it all worked fine. I had rooted and flashed custom roms before (I'd been running a nightly of CyanogenMod for a long time, and it worked well), and I considered myself an expert. I updated loads of apps and stuff, and then realised I wanted a new font. I went into ROM manager and found the font I wanted, Ubuntu. It told me there was an update to ClockworkMod recovery so I wen ahead and updated it, checking the thing for Touch (I'd already bought it). That want ahead and it updated, throwing me back into the OS. I then went to get Ubuntu (I downloaded it within ROM manager), and didn't deem it necessary to create a backup, nor wipe anything. It processed it but returned an error, I though ok but never mind and I told it to reboot. Again that worked fine. I realised I was on a very old verson of CyanogenMod (probably ICS, it was around 201304). As I always do, I grabbed the latest version (again, in ROM manager), and elected to install it. I didn't wipe the delvik cache or whatever, and hit 'Reboot into recovery'. That was where the problem occurred. It wouldn't go any further than the 'Samsung Galaxy Tab 10.1' boot screen (see attachment) into recovery. A similar thing happened before, but it just eventually went away after an hour or so. This has been running for a day, and there has been no progress. I've tried various key combos, like the normal way to get into recovery, but they won't work.
If I need I could find the instructions I followed, but it would be hard.
Is it completely broken? Can a save my data? Will I have to factory reset it? Will I keep my root/ClockworkMod? Will I keep my rom?
Thanks in advance to the person who can answer this
Do you have any ROM zips in your SD card? If you do, boot into recovery, full wipe and flash it. Piece of advice, don't use the recovery in ROM manager. Download pershoot's version of cwm instead in here. www.droidbasement.com
Sent from my GT-P7500 using Tapatalk HD
I have a few nandroid backups, if that counts? I do have a few ROM zips on my SD card too, though. Will a full wipe delete photos etc? I'm guessing it'll get rid of the apps, but that's no problem. But how would I get into recovery? I've already tried to get in with no success.
FelixJ20000 said:
I have a few nandroid backups, if that counts? I do have a few ROM zips on my SD card too, though. Will a full wipe delete photos etc? I'm guessing it'll get rid of the apps, but that's no problem. But how would I get into recovery? I've already tried to get in with no success.
Click to expand...
Click to collapse
If you can find a way to get into recovery, then yes you can use your nandroid. You problem now is you can't get into recovery or download mode, right? Well can you try using adb? If you can then type adb reboot recovery in command prompt to reboot to recovery.
Oh yeah, full wipe won't delete photos etc unless you wipe your internal storage/SD card.
Sent from my GT-P7500 using Tapatalk HD
Oh, thanks. I've got ADB already installed (I used it in trying to root my HTC Hero). Have I said thanks? You're a life saver
Oh dear, it seems that it's not showing up as an ADB device. Are there any other ways to get into recovery?
FelixJ20000 said:
Oh dear, it seems that it's not showing up as an ADB device. Are there any other ways to get into recovery?
Click to expand...
Click to collapse
I don't know. The hold down power button + volume down didn't work? You have to hold for at least 10 seconds.
Don't just say thanks...hit my thanks button.
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
I don't know. The hold down power button + volume down didn't work? You have to hold for at least 10 seconds.
Don't just say thanks...hit my thanks button.
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Just tried that, when I selected recovery it just turned off
So you can get into download mode?
Download mode, yes. I've got it open now, in fact
Now that's easy. Your tab can't boot because it doesn't have any sort of recovery(don't ask me why I don't know ). Apparently ROM Manager wiped your recovery clean and didn't flash the new one. Just flash cwm or twrp via Odin and try to boot. If it still can't boot, then restore your nandroid. Ironically, the same thing happened to me yesterday when I tried to flash latest twrp using Mobile Odin.
Sent from my GT-P7500 using Tapatalk HD
What's odin?
Ok, It's all sorted now! Thanks for your help!
FelixJ20000 said:
What's odin?
Click to expand...
Click to collapse
You have never used Odin before? Then how on earth did you root?
Sent from my GT-P7500 using Tapatalk HD
eushaun99 said:
You have never used Odin before? Then how on earth did you root?
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
I actually have no idea. I think I used a program similar to Odin that did the job. I remember booting into download more before. Oh yes, I flashed the disk image for the root and CWM using the default windows tool. Anyway, I've fixed it now. I couldn't find a .tar to do the job so I converted a random file to a .tar and flashed it that way, tricking it into thinking it had a recovery and therefore booting. In the OS I used ROM Manager to get CWM.
FelixJ20000 said:
I actually have no idea. I think I used a program similar to Odin that did the job. I remember booting into download more before. Oh yes, I flashed the disk image for the root and CWM using the default windows tool. Anyway, I've fixed it now. I couldn't find a .tar to do the job so I converted a random file to a .tar and flashed it that way, tricking it into thinking it had a recovery and therefore booting. In the OS I used ROM Manager to get CWM.
Click to expand...
Click to collapse
Sent from my AWESOME Ponified HTC Sensation using Tapatalk 4
Suddenly I cannot flash ROMs. I've downloaded, and have tried to flash, 2 ROMs. They are downloaded correctly, too. I've downloaded them multiple times as well.
When I try to flash, it gives me a bunch of prop errors and then gives me an error that the ROM cannot be flashed. I am able to restore backups, though.
I'm not sure what's causing this, as it happened out of the blue. A few days ago I flashed a ROM fine but reverted back to my original ROM because I did not like the other ROM.
I always wipe data and wipe system, and have even wiped cache. Really I'm at a loss her so any help would be greatly appreciated.
what two roms are you trying to flash and on what recovery/version?
B_I_N_G_E said:
what two roms are you trying to flash and on what recovery/version?
Click to expand...
Click to collapse
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
BoostinBen said:
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
Click to expand...
Click to collapse
Download goo manager from play store. Open, menu button, install OpenRecoveryScript. That will update TWRP. Then try again.
Sent From My Sticky Note, Too?
B_I_N_G_E said:
what two roms are you trying to flash and on what recovery/version?
Click to expand...
Click to collapse
BoostedB18C said:
Download goo manager from play store. Open, menu button, install OpenRecoveryScript. That will update TWRP. Then try again.
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
Unfortunately I got the same error, albeit it seemed to move along a little more than before. The exact error is as follows:
"file_getprop: failed to stat /sdcard/kernal.pro. Error flashing zip (and a few other irrelevant things)"
BoostinBen said:
Tried the Pac-Man ROM and another ROM that I forgot the name of. Recovery is TWRP but I'm not sure what version. It's the version that installed a long time ago when I first rooted and unlocked the device, so it's definitely not the newest version.
Click to expand...
Click to collapse
In the older Casual root methods the installed recovery was for the international Note 2. and caused some issues on our VZW version.
As was mentioned, install the newest TWRP or CWM and you should be fine.
Also.... remember flashing between a 4.3 ROM and 4.2 and earlier have some differences. Make sure to really read and reread the OP to any ROM you are flashing as most have subtle differences in the recommended method to flash and recovery suggested.
Milimbar said:
In the older Casual root methods the installed recovery was for the international Note 2. and caused some issues on our VZW version.
As was mentioned, install the newest TWRP or CWM and you should be fine.
Also.... remember flashing between a 4.3 ROM and 4.2 and earlier have some differences. Make sure to really read and reread the OP to any ROM you are flashing as most have subtle differences in the recommended method to flash and recovery suggested.
Click to expand...
Click to collapse
Right now I'm on JellyBeans, which is a great ROM. I just wanted to try something different. That ROM is 4.1.2, IIRC.
CWM works? Hrm...gotta give that a try considering I bought it a while ago.
BoostinBen said:
Right now I'm on JellyBeans, which is a great ROM. I just wanted to try something different. That ROM is 4.1.2, IIRC.
CWM works? Hrm...gotta give that a try considering I bought it a while ago.
Click to expand...
Click to collapse
Tried CMW and I get the same error about the kernal.prop
I'm running Saber's kernal. Could it be something with that?
BoostinBen said:
Tried CMW and I get the same error about the kernal.prop
I'm running Saber's kernal. Could it be something with that?
Click to expand...
Click to collapse
I'm going to say the quote.
"Its time for a date with Odin." - @droidstyle
http://forum.xda-developers.com/showthread.php?p=34891181
Just start from scratch and you will be good.
Sent from my Nook Tablet
BoostedB18C said:
I'm going to say the quote.
"Its time for a date with Odin." - @droidstyle
http://forum.xda-developers.com/showthread.php?p=34891181
Just start from scratch and you will be good.
Sent from my Nook Tablet
Click to expand...
Click to collapse
Thanks. I'll give this a try and report back.
Sent from my SCH-I605 using Tapatalk 2
Interesting. I am able to load ROMs with the Aroma installer just fine, just not any that are regular ZIP files.
BoostinBen said:
Interesting. I am able to load ROMs with the Aroma installer just fine, just not any that are regular ZIP files.
Click to expand...
Click to collapse
Any ideas why zip installs give me a kernal.prop error?
BoostinBen said:
Any ideas why zip installs give me a kernal.prop error?
Click to expand...
Click to collapse
Have you tried just flashing a new kernel? there was some issues with a few versions of sabre kernel.... get the newest one or Perseus or something else.
Install the newest version of your recovery (CWM or TWRP)
Boot into recovery.
Clear dalvik/cache
Flash your kernel
Clear dalvik and cache again (just because thats what i do, no idea if its needed)
Test your installed ROM or just install a new ROM following the instructions in the OP of the ROM thread...
If there is no install instructions, I always:
Make a nandroid backup!
Clear dalvik/cache
Factory reset (wipe all but SD card, depending on your recovery)
Install ROM
Clear dalvik and cache again
Install GAPPS (Google Apps package) if not included in ROM
Reboot system
Profit?
Good Luck, report success/failure
BoostinBen said:
Any ideas why zip installs give me a kernal.prop error?
Click to expand...
Click to collapse
What kernel are you using?
Sent from my SCH-I605 using Tapatalk 2
michigan66 said:
What kernel are you using?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I'm using Saber's overclocked one. I will grab another kernal and give it a shot and report back.
Got this fixed by switching to another kernel.
Hey guys, I need help.
I consider myself fairly adept at handling rooted devices, but I have not been following development for the GS4 for the last several months and have been running the last release of Synergy before their hiatus.
I was going to try out something different. I always enjoyed Beanstown's Jelly 'Beans', and thought I would try Build 7.
Now I am stuck at the Samsug Galaxy Boot Logo and it never goes to the Custom Boot Screen.
WORSE...I managed to break my recovery...so it will not boot their either.
Only mode I can boot to is Download.
Maybe I am just blind but I searched and could not find any Odin flashable recoveries...does anyone have one? Is there a rooted MDK file out there that I can flash via Odin?
Someone please help
Did you do the proper wipes when flashing the new rom? There arent any odin flashable recoveries for the s4. I would probably use the no wipe mdk image to recover (wont lose any user data) since you have no custom recovery to flash something with. Youll have to start over but youll have a working phone at least.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
jbg25 said:
Yes...I always wipe well when I am flashing. Almost every problem I have ever had going back to the Droid 1 was from a Dirty Wipe. I also tried searching for issues and warnings before moving forward...but did not find anything with my searches.
So just to be sure I have this right...start with this
http://forum.xda-developers.com/showthread.php?t=2301259&highlight=mdk
Then re-root as I did originally
http://forum.xda-developers.com/showthread.php?t=2290798
Then I can reflash CWM Recovery from Rom Manager? Will it automatically flash loki'd version?
Finally once there...can I just flash Beantown's Jelly Beans Build 7 or do I need to update the radios first? Can I use the just the MJ7 modem from the post below or do I need other parts updated too?
http://forum.xda-developers.com/showthread.php?t=2487298
Thanks all!
Click to expand...
Click to collapse
Yeah looks like you got everything in order. Rom manager or rom toolbox will auto loki the recoveries. No need to update radios when flashing beans either. Itll already have the radios included unless your wanting to flash the mj7 radio seperately then I believe youll be ok doing that. I havent done alot of reading on the newest radios.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
jbg25 said:
Back up and running with stock rooted MDK and CWM Recovery.
Now to try and flash a ROM.
Click to expand...
Click to collapse
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
beanstown106 said:
good deal just saw your pm was gonna say flash mdk odin but it looks like you found it
Click to expand...
Click to collapse
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
jbg25 said:
Thanks for getting back to me! :good:
I am up and running...but with but not with 'Beans' Build 7 ... I have tried everything...and no matter what it stalls at the SGS4 Splash Screen and never progresses.
I thought maybe it was the new recovery I flashed ( CWM Touch Recovery 6.0.4.4) .... BUT I got Hyperdrive to install and boot. So maybe my SGS4 just doesn't like Beans...which sucks cause I ran that almost exclusively on my SGS3.
Click to expand...
Click to collapse
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Try TWRP 2.5.0.2.
Most of the devs use it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
jbg25 said:
I downloaded and installed the latest TWRP 2.6.3.0 from DsLNeXuS's Recovery Tools App as Goo Manager is not finding a recovery for my device.
Still no good...nothing I do makes Beans Build 7 work ....
Click to expand...
Click to collapse
Go here. Get 2.5.0.2
http://techerrata.com/browse/twrp2/jfltevzw
Instructions
http://teamw.in/project/twrp2/181
At the bottom of the page.
Edit;
Or flash this in recovery
http://forum.xda-developers.com/showthread.php?p=45006486
I would reboot to recovery after flashing to make you got it on the right version.
Then make sure you can still boot back to your rom.
Then go back to recovery
Wipe
Factory reset.
Advanced
Check system, Data, davlik and cache
Wipe
Go back to main screen
Install
Fund your rom to flash.
Sent from my SCH-I545 using xda app-developers app
Me too. I tried the [ROM][TW4.3]STOCK-ROOTED-MJ7-AROMA-LOKI'd ROM with CWMR. Wiped Dalvik. Cache, Ractory Rest/Data. Seemed to install fine but then hung at "Custom". Fortunately I was able to a Nandroid Restore but not sure where this went wrong. Finally got TWRP to install after several failed GooManager attempts over the past month. May CWMR is the problem.