Related
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
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
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
Hey guys, I recently attempted to root my old phone using the Amaze All in One Kit v5.2. Well, I was able to get the bootloader unlocked and installed TWRP recovery, but was unable to get any roms to load. I was advised I should relock the bootloader and attempt to do a RUU flash since my phone will no longer boot past the HTC screen. Since I relocked the bootloader, I have lost access to TWRP recovery entirely. I also tried the PH85IMG file on my SD card, but it doesn't seem to do anything different after installing and verifying.
My current bootloader screen displays the following:
***RELOCKED***
***Security Warning***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0003
eMMC-boot
Aug 14 2012, 17:22:50
Any advice or direction would be greatly appreciated.
Michael
Flash 4ext recovery and enable smart flash from settings and then flash any ics rom... (4ext has this smart flash feature so even tho you're S-ON you can still flash a rom and the kernel together in twrp recovery only the rom get Flash not the kernel) reason it didn't work for you in the first place..
https://www.dropbox.com/s/ox16mtk02zoi3qf/PH85IMG.zip
If you have a hard time flashing 4ext recovery from all in one kit use it.. (REMOVE EVERY FILE INSIDE IT EXCEPT FOR THE ONE CALLED "recovery.img" and place it in your ext_sd card and go to bootloader and follow instructions) unlock the bootloader 1st if it's locked ...
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Gotcha. Well, I just got the bootloader unlocked again, but I am unable to flash 4EXT recovery through the all in one software. The only other option I saw involved installing from the phone, but since I can only get to the bootloader and TWRP recovery screen, I'm unsure of how exactly to install it. You will have to excuse my ignorance on this stuff. I'm pretty computer literate, but this rooting stuff has gotten the best of me thus far...
jdmroach said:
Gotcha. Well, I just got the bootloader unlocked again, but I am unable to flash 4EXT recovery through the all in one software. The only other option I saw involved installing from the phone, but since I can only get to the bootloader and TWRP recovery screen, I'm unsure of how exactly to install it. You will have to excuse my ignorance on this stuff. I'm pretty computer literate, but this rooting stuff has gotten the best of me thus far...
Click to expand...
Click to collapse
Just follow the things I told in the 2nd para.. Use that zip and flash it from bootloader.. It'll overwrite and flash 4ext recovery
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Just follow the things I told in the 2nd para.. Use that zip and flash it from bootloader.. It'll overwrite and flash 4ext recovery
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, after installing just that file on my SD card and restarting the phone, it went through a file check and parsing phase then when I clicked on recovery it brought back up TWRP. Obviously I'm misunderstanding something.
jdmroach said:
Well, after installing just that file on my SD card and restarting the phone, it went through a file check and parsing phase then when I clicked on recovery it brought back up TWRP. Obviously I'm misunderstanding something.
Click to expand...
Click to collapse
it didn't install the recovery in the process?
ravike14 said:
it didn't install the recovery in the process?
Click to expand...
Click to collapse
It does not appear so. TWRP opened up once again when I clicked on recovery from within the bootloader.
I'm also getting this error "Unable to mount eMMC" as well.
jdmroach said:
It does not appear so. TWRP opened up once again when I clicked on recovery from within the bootloader.
I'm also getting this error "Unable to mount eMMC" as well.
Click to expand...
Click to collapse
i use the same zip when something goes wrong..it works fine for me..no idea why its not flashing.you unlocked the bootloader? deleted other unnecessary files in that zip?
jdmroach said:
It does not appear so. TWRP opened up once again when I clicked on recovery from within the bootloader.
I'm also getting this error "Unable to mount eMMC" as well.
Click to expand...
Click to collapse
Well, cancel that. Finally got the 4EXT recovery flashed. Thanks again for all your help.
ravike14 said:
i use the same zip when something goes wrong..it works fine for me..no idea why its not flashing.you unlocked the bootloader? deleted other unnecessary files in that zip?
Click to expand...
Click to collapse
I think I was doing something incorrectly. Anyways, I just enabled Smart Flash and went to "install from sdcard". When I select "choose zip from sdcard", I get the error "Can't mount /internal sdcard".
jdmroach said:
I think I was doing something incorrectly. Anyways, I just enabled Smart Flash and went to "install from sdcard". When I select "choose zip from sdcard", I get the error "Can't mount /internal sdcard".
Click to expand...
Click to collapse
looks like you're partitions are corrupted :/ ..go to wipe category and do a full wipe except SD cards and see if it works...
ravike14 said:
looks like you're partitions are corrupted :/ ..go to wipe category and do a full wipe except SD cards and see if it works...
Click to expand...
Click to collapse
In the wipe category, my options are as follows:
wipe data/factory reset
wipe cache
wipe cache + dalvik
wipe dalvik cache
wipe battery stats
format system
format data
format boot
format all partitions (except sd card)
format sdcard
Did you mean do a format all except sdcard?
ravike14 said:
looks like you're partitions are corrupted :/ ..go to wipe category and do a full wipe except SD cards and see if it works...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=27844248&postcount=6
I came across this method and it appears to have fixed my internal sdcard issue. It is installing the rom now. I will let you know once I get done flashing the rom if all goes as planned.
jdmroach said:
http://forum.xda-developers.com/showpost.php?p=27844248&postcount=6
I came across this method and it appears to have fixed my internal sdcard issue. It is installing the rom now. I will let you know once I get done flashing the rom if all goes as planned.
Click to expand...
Click to collapse
Sorry for delay, good luck
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Sorry for delay, good luck
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ended up just flashing the Cyanogenmod rom for now. Everything seemed to go fine with the install. I rebooted and it sat at the Cyanogenmod splash screen for almost a hour without proceeding. Any clue?
jdmroach said:
I ended up just flashing the Cyanogenmod rom for now. Everything seemed to go fine with the install. I rebooted and it sat at the Cyanogenmod splash screen for almost a hour without proceeding. Any clue?
Click to expand...
Click to collapse
Did you do a full wipe before flashing the rom? If there are data of your previous rom in your system partition all the data get overwrite and crashes ... Full wipe = format all (except sd card)
(the one in wipe/format category..)
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
Did you do a full wipe before flashing the rom? If there are data of your previous rom in your system partition all the data get overwrite and crashes ... Full wipe = format all (except sd card)
(the one in wipe/format category..)
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ahh okay. I believe I just did the wipe function and not a full format. I will try that and let you know.
jdmroach said:
Ahh okay. I believe I just did the wipe function and not a full format. I will try that and let you know.
Click to expand...
Click to collapse
It has been at the Cyanogenmod screen for about 20 mins now. Does it normally take this long?
jdmroach said:
It has been at the Cyanogenmod screen for about 20 mins now. Does it normally take this long?
Click to expand...
Click to collapse
I just read carefully your 1st post now.. You're hboot is 1.93.003 it's normally 1.93.002.. It's a nasty issue.. Try to flash a stock htc ics rom (arhd 5) and do the s-off.. It's the only way to recover from that issue as far as I know..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
I just read carefully your 1st post now.. You're hboot is 1.93.003 it's normally 1.93.002.. It's a nasty issue.. Try to flash a stock htc ics rom (arhd 5) and do the s-off.. It's the only way to recover from that issue as far as I know..
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
SUCCESS!!! I was able to flash another rom (T-mobile Stock ICS Debloated) and it booted back up like it should. Seriously, thanks again for all of your help buddy.