Related
So I flashed the Eng-build on my phone and now I cant install any custom rom :/ everytime i wipe the data and try to install it looks as if it installs but nothing changes when I reboot.
Does anybody know what i could do to fix this?
Flash clockworkmod recovery if you havant already done so
Sent from my ADR6300 using XDA App
Can anyone explain how Rom manager works on the slide?
I have never been able to get rom manager to do anything.
It downloads the update.zip and then reboots into recovery, fails and reboots the phone.
Everytime I have had to flash a rom, Ive had to do it the old way.
Any ideas?
Faud said:
Can anyone explain how Rom manager works on the slide?
I have never been able to get rom manager to do anything.
It downloads the update.zip and then reboots into recovery, fails and reboots the phone.
Everytime I have had to flash a rom, Ive had to do it the old way.
Any ideas?
Click to expand...
Click to collapse
Have you flashed the engineering ROM?
No,
I have not flashed the eng rom. I had thought there was a thread by Wes that warned against it?
I have been using the MR1v4 pretty much since the first day I rooted the phone and have never had any problems with it.
I am also aware that flashing a radio can be dangerous and my understanding is that if I flash the eng rom that I have to flash a new radio.
If this is all necessary, well then, so be it, but if it can be avoided that would be preferred.
Thank you
Ive flashed clockwork, and it still doesn't work.
I ended up taking the ENG-build off and rerooted the phone. However it is still having issues loading custom roms :/
No engineering rom = no test keys in recovery = no using rom manager.
Read the whole thread, and the engineering thread. The thread from wes was wrong.
Flashing a radio isn't dangerous. I think you may be referring to the days of the danger spl on the G1. In that instance if the radio wasn't the newest version and three plqanets weren't lined up just right... flashing the danger spl would brick your phone. But flashin a new radio is perfectly safe. There is mention in other threads that since we cannot change the spl for the slide yet that bricking it is rather difficult yet not impossible =) so don't go trying, lol.
SySfS
Hello! I need help on my G2 that doesnt want to flash any roms at all. When i go into Rom Manager and download a rom and go install it, it finish and it boots up but it just stays on the first HTC logo. I leave it there for more then ten minutes relizing the in messed up. So i have to go back into recovery(manualy) and wipe all data and cache and then i flash the Virtuous Rom(because i downloaded it to the sdcard) and it boots up. Also when i try to flash the mods to the rom and it also fail and i have to do the same procedure again and again everytime i try to flash a rom or backup. What should i do? Oh i also have S-OFF if that helps.
have you tried manually downloading and flashing another ROM through recovery?
Also, are you doing full wipes when trying to flash the new ROMs?
martonikaj said:
have you tried manually downloading and flashing another ROM through recovery?
Also, are you doing full wipes when trying to flash the new ROMs?
Click to expand...
Click to collapse
No i havent tried from a diferrent recovery but i will. Also i have benn doing full wipes and cache wipes.
Not a different recovery..the same way you flashed that rom is the same way you can flash others..if you downloaded rom through rom manager you can find it in that folder which is on your sd card called clockworkmod
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Not a different recovery..the same way you flashed that rom is the same way you can flash others..if you downloaded rom through rom manager you can find it in that folder which is on your sd card called clockworkmod
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I downloaded it from a youtube video and manually flashed them. But the problem is i already looked for a rom and i kinda dont want to trust people who post roms because my mytouch 3g got bricked becuase of the that. And i cant any roms i looked everywhere even on my best friend(google).
Sorry not even paying attention but thanks i will try that.
Chassen1236 said:
No i havent tried from a diferrent recovery but i will. Also i have benn doing full wipes and cache wipes.
Click to expand...
Click to collapse
Not a different recovery. Just make sure that your CWM recovery is the latest version. Download a ROM of your choice from the Dev section via your computer, transfer to your SDcard, and flash manually from your phone (not using ROM manager). Do a cache/dalvik cache/full data wipe. Then flash the ROM and reboot.
ROM manager can often have issues with bad downloads that lead to bad flashes. Flashing manually can be a way to troubleshoot and take a potential bad step out of the equation.
martonikaj said:
Not a different recovery. Just make sure that your CWM recovery is the latest version. Download a ROM of your choice from the Dev section via your computer, transfer to your SDcard, and flash manually from your phone (not using ROM manager). Do a cache/dalvik cache/full data wipe. Then flash the ROM and reboot.
ROM manager can often have issues with bad downloads that lead to bad flashes. Flashing manually can be a way to troubleshoot and take a potential bad step out of the equation.
Click to expand...
Click to collapse
You can download roms from dev section from your device as well.
As far as the op..what do you mean you downloaded from a youtube video and you don't trust people who past roms? If you don't trust people don't mess with it. The devs here aren't going to brick you phone..that's a mistake on your end or you not paying attention to what you were flashing
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
You can download roms from dev section from your device as well.
Click to expand...
Click to collapse
I was trying to get him to download via his computer to see if the downloading via his phone was causing bad flashes.
Spastic909 said:
You can download roms from dev section from your device as well.
As far as the op..what do you mean you downloaded from a youtube video and you don't trust people who past roms? If you don't trust people don't mess with it. The devs here aren't going to brick you phone..that's a mistake on your end or you not paying attention to what you were flashing
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Correct me if I'm wrong but if i remember correctly it is extremely difficult to brick ones phone. The worst possible thing that could happen is if your phone some how died during a flash half way through. You can easily boot into bootloader, enter recovery and attempt to do it again.
With CWM you can mount the sd card in the mounts and storage settings so if you forgot or somehow deleted the Rom Zip from your card you can easily and safely access your card using CWM
i'm having the same issue
i have the phone rooted, s-off, and hboot installed
i'll boot into rom manager, wipe the data/cache, install the rom i want, reboot device... i get the white htc screen for about 5 seconds and then the phone restarts.
when it restarts, i get the white htc screen and then it boots into rom manager
what could be causing this? i had my previous g2 rooted and never had these issues when i was flashing roms
Looked urgent huh? That's because it is. I see that most people that have their phones bricked is from using ROM manager to install a rom that they downloaded onto their phone.
LISTEN TO ME WHEN I TELL YOU....
Do not use ROM manager to install a custom ROM that is not listed in the application.
I too have bricked my phone this way and I never made a back up. The quickest solution is to actually re-root your phone again by putting it back into download mode.
Look in the forums for instructions. I'm sure others can explain it better than me.
Only use ROM Manager to install clockwork mod recovery.
From there, do it the manual way. It may be more labor, but it is better than bricking your phone.
There are instructions to do that too. If you can't find it just throw me a PM.
Lol I use it all the time to flash roms never bricked
Sent from my SAMSUNG-SGH-T989 using xda premium
same here. can you elaborate why you think or provide proof that cwm is bricking peoples phones.
I have used cwm on several phones and never had any problems getting to recovery and flashing roms.
you didn't read his post. he is saying not to use Rom manager to get/install roms
Probably because rom manager only wipes data and cache at most. Most of these roms work best with a super wipe
The touch cwm is the worst. Have to toggle signature verification every time, and point it to the internal sd card. Only one brick (soft), though.
That v5 one is notoriously bad on many phones. Just buggy. Not a dealbreaker for me. Is the other touch one better?
Sent from my SAMSUNG-SGH-T989 using xda premium
He's probably referring to the roms listed in ROM manager that are not for our phone.I think there is two of them now
I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.
You guys can stop "trippin" there are 2 roms under the dl section in rom manager for our phone DO NOT IN ANY WAY SHAPE OR FORM FLASH THIS TO YOUR SGH-T989!!! it WILL BRICK YOUR DEVICE!!! Somebody just needs to email koush about it so they can be removed. IMHO dl to your phone or pc and then flash away a superwipe is recommended. I for one am iffy with rom manager because it errors out on restores sometimes.
Sent from MY Juggernaut!!!
zander21510 said:
I think we're confusing Rom Manager with Clockwork Mod...
Rom Manager is an app made by koush, its a downloadable market app thats included with Cyanogenmod and other roms (on other phones) that makes it easy to install a ROM without bothering with booting into recovery. I used it extensively during my Nexus days, though on the t989 many roms you have to super wipe or do a lot of advanced things you can only do inside clockwork mod.
ClockworkMod is a recovery manager for your android phone, also made by Koush. The classic version that has been on all phones is the non-touch type, latest version is 5.0.2.7. You use the power button and volume rocker to navigate. There is another version dubbed ClockworkMod Touch, latest version is 5.8 something...you can actually navigate with touchscreen in this.
Many people's problems, I've experienced it too, is that CWM touch likes to reboot randomly during crucial moments (during a backup, MD5 creation, flashing a ROM...), leaving the potential for (and in some cases it actually has) bricked phones. Plus the touchscreen navigation is tempermental, its just not very responsive or accurate. Very dangerous bugs for such a sensitive area on the phone.
So do yourself a favor...use ClockworkMod, the originial. Its not going to kill you to navigate with the volume rocker and power button...it actually makes you pay attention and go slower so you don't make mistakes and push the wrong thing. Its easy to install...with Rom Manager! Download it from the market, when you open it near the top there will be a button to flash the latest ClockworkMod. It will be the non touch type.
As stated above, I wouldn't use the ROM flashing functions of Rom Manager with our phone, but it does have an easy button to reboot into recovery for roms without the option in the shutdown menu. It's the easiest way to flash CWM though.
Hope this helps.
Click to expand...
Click to collapse
Holy christ time to flash back to original clockworkmod. Later touch recovery.
Sent from my SAMSUNG-SGH-I727 using xda premium
Still rockin the original CWM, never saw all the fuss about the touch stuff. Manually toggling is much safer and reliable IMO
I see that people have mistaken that I was talking about not using CMW. Let me explain. CMW (Clockwork Mod Recovery) and ROM Manager are two different things. You get CMW from ROM Manager. You use CMW to flash ROMs. Some people use ROM Manager to flash ROMs instead of CMW. That's the way you get bricked. By flashing ROM's that aren't on ROM Manager. I hope this clears it up.
I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall
ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread
the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.
rsfaze said:
the OP says it bricked his phone, yet then says he flashed back to stock LOL. If your phone is a BRICK it's dead and does NOTHING.
Click to expand...
Click to collapse
There's also soft brick which can be saved. He was most likely referring to that.
Sharpie603 said:
I was unaware people still used Rom Manager.....
Thought we upgraded to ODIN, ADB and Heimdall
Click to expand...
Click to collapse
ODIN is really crappy software IMO.. Despite its uses.
Even rom manager has its uses...I wouldn't use it to flash ROMS, because often with our phones you need more wiping than just data & cache, which is all it can do before it flashes a rom. It however it can be used to easily flash CWM and for phones without the option in the shutdown menu, you can use rom manager to reboot straight into CWM.
Guy's, what he is trying to tell you is that there are 2 ROMS that can be dowloaded and installed by ROM MANAGER that WILL BRICK YOUR PHONE. They are listed as T989 roms but they are actually for the International SGS2....
sbell7105 said:
ROM manager will not brick your phone! If it does get bricked it was user error! Please close this thread
Click to expand...
Click to collapse
He's accurate about what he described in this thread. I created a similar thread (probably got deleted) yesterday about the same issue. Just because you haven't experienced bricking yours doesn't mean he shouldn't warn others.
I hard-bricked my T989 just simply trying to boot into recovery (non-touch CWM) from the Rom Manager app...and I have read similar issues. The phone goes fcuking dead.
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.
bluepenny65 said:
H
UPS just dropped off my replacement phone today...ready to be rooted for an ICS AOSP ROM if I can find one. Done with CM7 for now.
Click to expand...
Click to collapse
There isn't one that fully works with data and audio
Sent from my SAMSUNG-SGH-T989 using Tapatalk
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
This is probably a stupid and obvious question but...Do I have to root my phone first before flashing CM10.1 on my Note 2 sgh-i317m?
I started off with installing clockwork recovery but when I go into recovery mode I see android system recovery.
if I have to root can someone provide me with a great guide to do so please and thanks.
LeBeast said:
This is probably a stupid and obvious question but...Do I have to root my phone first before flashing CM10.1 on my Note 2 sgh-i317m?
I started off with installing clockwork recovery but when I go into recovery mode I see android system recovery.
if I have to root can someone provide me with a great guide to do so please and thanks.
Click to expand...
Click to collapse
If the recovery install didn't stick then you have to rename the recovery restore files, which requires root.
Use the gnote 2 toolkit to root.
I would just root without installing a recovery and use goomanager to install the latest version of twrp from inside android. Reboot into recovery and flash whatever you want. For my phone needs, CM10.1 is nowhere near ready to be used daily, so make a backup.
simonxliu said:
If the recovery install didn't stick then you have to rename the recovery restore files, which requires root.
Use the gnote 2 toolkit to root.
I would just root without installing a recovery and use goomanager to install the latest version of twrp from inside android. Reboot into recovery and flash whatever you want. For my phone needs, CM10.1 is nowhere near ready to be used daily, so make a backup.
Click to expand...
Click to collapse
I wouldnt go that far. Rootbox now has no issues for me. Bluetooth works perfectly for everything. Camera works great. I dont even know whats not working anymore because most of the daily things I use work perfectly....Phone, Texts, Group Messaging Stock, Bluetooth, Video, Photos. Up until yesterdays update Bluetooth would crash when switching modes or after a call. Then a reboot was necessary but now it works perfectly.
I do agree about the backup plan though.
OK I rooted and flashed CM10.1 on my phone but I'm wondering if I missed something because I don't seem to be getting LTE. I only get H or 3G it seems. When I go into settings > about phone > status, it says Mobile network type: HSPA: 10.
Try changing the apn
Sent from my SGH-I317 using xda app-developers app
Got that to work. LTE was off apparently.
Also, what's with the play store? How come their is so few apps and I can't find many that were there before
LeBeast said:
Got that to work. LTE was off apparently.
Also, what's with the play store? How come their is so few apps and I can't find many that were there before
Click to expand...
Click to collapse
did you make sure you flashed gapps 121212? if you did try it again....I had that problem before and reflashing gapps fixed it.
jbeef86 said:
did you make sure you flashed gapps 121212? if you did try it again....I had that problem before and reflashing gapps fixed it.
Click to expand...
Click to collapse
Yeah I now flashed gapps-jb-20121212-signed.zip a second time and still no luck.