I have a TF300T coming in the mail Wed and I'm going to start playing with it here soon, I've been flashing my SPH-L710 for over a year now using CWM and I am very familiar with it but I keep hearing in the forums not to use it, but can't find a reason. I do have about 20 plus hours of reading in the TF300T thread, most people are saying to use TWRP. Just wondering why? I will most likely be running PACman just because I love that ROM.
Sent from my SPH-L710 using xda app-developers app
cmdmoto said:
I have a TF300T coming in the mail Wed and I'm going to start playing with it here soon, I've been flashing my SPH-L710 for over a year now using CWM and I am very familiar with it but I keep hearing in the forums not to use it, but can't find a reason. I do have about 20 plus hours of reading in the TF300T thread, most people are saying to use TWRP. Just wondering why? I will most likely be running PACman just because I love that ROM.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I'm on Pac-man welcome
Personally TWRP is easier to use and you save your volume buttons from being over pressed. I think there was some bug about CWM not being able to flash some ROMs, but I've never run into any problems with TWRP ( that weren't caused by my own stupidity ).
Tip:
Before flashing, make sure your bootloader is compatible with everything you are flashing. Also make NvFlash Backups ASAP.
Ty cmendonc2, that's what I thought about CWM not being able to flash some ROMS. I was reading through the NVflash thread last night and it looks to be very intimidating at first as well as the bootloader. I'm sure it's not that bad, I just need to get the tablet here so I can start playing with it. Sound to me that the bootloader is main central nerve of the tablet. EVERTHING revolves around it.
Sent from my SPH-L710 using xda app-developers app
I'm using cwm 6.0.1.3...I keep getting errors flashing so far anything I've tried since I was on clean ROM which flashed perfectly fine...I'd switch to twrp but my screen was cracked and the replacement screen has no touch response is there a non touch recovery other then cwm that I can use?
Sent from my SAMSUNG-SGH-T989 using xda app-developers ap
I've used cwm for a long time until now
I find twrp so much better. I especially like the touch features.
schkeet said:
I'm using cwm 6.0.1.3...I keep getting errors flashing so far anything I've tried since I was on clean ROM which flashed perfectly fine...I'd switch to twrp but my screen was cracked and the replacement screen has no touch response is there a non touch recovery other then cwm that I can use?
Sent from my SAMSUNG-SGH-T989 using xda app-developers ap
Click to expand...
Click to collapse
CWM has problems on this device since JB. It can cause bricks so stay with TWRP which is better anyway.
I'd love to switch to twrp it seems like it would fix my problem ..but I was saying I need a non touch recovery cause the touch has not been working on my tablet since the screen broke are there any other recoveries that will work using the hardware keys?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
schkeet said:
I'd love to switch to twrp it seems like it would fix my problem ..but I was saying I need a non touch recovery cause the touch has not been working on my tablet since the screen broke are there any other recoveries that will work using the hardware keys?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
To be safe, do the NvFlash backups and use the modified CWM recovery that you have to install with that.
Related
Hey guys. A question for you. I'm coming from galaxy s. I'm no noob. With the sgs you could restore your backup in clockwork if you screwed up. Can't you do this with o3d (reading about people bricking their device) . If not, what's the point with a backup?
Sent from my LG-P920 using Tapatalk
Bump...
Sent from my LG-P920 using Tapatalk
Where did you hear the backups aren't working?
Works fine, no bricks. I used the backups a lot when I'm tweaking my phone.
I believe the people who were getting bricked phones from cwm are just using a different recovery. Something like thrill using Optimus 3D's recovery
Sent from my LG-P920 using XDA App
DevJackey said:
Where did you hear the backups aren't working?
Works fine, no bricks. I used the backups a lot when I'm tweaking my phone.
I believe the people who were getting bricked phones from cwm are just using a different recovery. Something like thrill using Optimus 3D's recovery
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Just what i thought from reading the "unbrick" thread.
So like with other devices if can get in to CWM and have a backup im "safe"?
borelis said:
Just what i thought from reading the "unbrick" thread.
So like with other devices if can get in to CWM and have a backup im "safe"?
Click to expand...
Click to collapse
Most users don't have a bricking problem. Yea CWM works like its supposed to. For example, yesterday, I was changing build.prop. Caused a boot loop. Pulled battery, Went to recovery, restored backup.
Never bricked my phone, but there are many reasons for bricking, you'll be fine.
Sent from my LG-P920 using XDA App
DevJackey said:
Most users don't have a bricking problem. Yea CWM works like its supposed to. For example, yesterday, I was changing build.prop. Caused a boot loop. Pulled battery, Went to recovery, restored backup.
Never bricked my phone, but there are many reasons for bricking, you'll be fine.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
hey just out of curosity what are the most common ways to brick the LG? just want a heads up on what to avoid doing, because i bought my lg 3d from a friend already rooted cwm and aura rom. Just wondering if i wanted to go back to like rogers stock what would i have to do?
The "bricking" with CWM is caused when you update the system with an LG Rom via OTA or Web Updater and you have the CWM recovery partition instead of the LG original one.
If you install the same ROM from a zip via CWM backup recovery it works like a charm.
Sent from my LG-P920 using Tapatalk
Beriaru said:
The "bricking" with CWM is caused when you update the system with an LG Rom via OTA or Web Updater and you have the CWM recovery partition instead of the LG original one.
If you install the same ROM from a zip via CWM backup recovery it works like a charm.
Sent from my LG-P920 using Tapatalk
Click to expand...
Click to collapse
Thank you
Sent from my LG-P920 using Tapatalk
Over the last month or so, I have been getting random kernel panics. Doesn't seem to matter what ROM I am using.
What are my options for fixing this?
Thanks!
Sent from my SAMSUNG-SGH-I997 using xda premium
GR8CDNPumpkin said:
Over the last month or so, I have been getting random kernel panics. Doesn't seem to matter what ROM I am using.
What are my options for fixing this?
Thanks!
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
OK I'll bite.... What is " Kernel Panic "?
It is about the same thing as a Blue Screen of Death in Windows.
Something went terribly wrong for me to get a Kernel Panic
I just don't know how to see what caused it.
Sent from my SAMSUNG-SGH-I997 using xda premium
GR8CDNPumpkin said:
It is about the same thing as a Blue Screen of Death in Windows.
Something went terribly wrong for me to get a Kernel Panic
I just don't know how to see what caused it.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Flash a different kernel?
Had something like this happen before, unbrick to stock and start over, in my case it was hardware issues so I did a warranty replace.
Sent from my SAMSUNG-SGH-I997 using xda premium
I am thinking hardware as it has creeped into several ROMs
Sent from my SAMSUNG-SGH-I997 using xda premium
Kernel panic upload mode
I was flashing custom ROMS from couple of months and did dozens of times.
But when I was flashing resurrection ROM an updated version, it completed but when I rebooted it was stuck in the kernel panic upload mode after the boot screen(galaxy s2). It was not going to clockworkmod recovery too. Then using the odin I tried to flash the stock ROM as well as custom ones. But it will finish, will stuck in the boot screen. Then flashed recovery using Odin and tried to flash custom roms. Couple of ROMS worked but most of them failed and stuck in the boot screen. I could able to restore the stock version which I saved previously.
But I cant try most of the ROMs now. CM9 didnt work.. But MIUI worked.
Can anyone help me.???
I roooted the phone and installed a recovery installed black bean succesfully. when the phone rebooted the phone greated me with the verizon sign that said I was using unauthorized software take it back to a verizon store. Any ideas what did I do wrong?
I already reset it to factory with odin, but I would like to know what am I missing here?
Sounds like you didn't unlock your bootloader. Download ez unlock from the play store, unlock and try again.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Sounds like you didn't unlock your bootloader. Download ez unlock from the play store, unlock and try again.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
let me try one more time, thanks for the quick response.
Wait a minute, are you sure you have the
Correct rom? I have not seen a blackbean rom for the verizon S3, only the international.
Sent from my SCH-I535 using xda premium
I believe your trying to flash the wrong Rom, your lucky it didn't brick it.
annoyingduck said:
Wait a minute, are you sure you have the
Correct rom? I have not seen a blackbean rom for the verizon S3, only the international.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm noticing there's one on Rootzwiki that was released today. Hope that's what they flashed.
Sent from my SCH-I535 using xda app-developers app
The rom is Baked Blackbean and its compatible with the vzw gs3... the problem is the op simply did not unlock his bootloader. Now he needs to follow section 6 of my guide linked in sig and then unlock the bootloader with ez unlock!
This time I got everything correct now, after i got my phone rooted i installed ez unlock and ez revovery, and this time booted just fine. Thanks for all your help.
Nice, now scrap that ez recovery and install rom manager. From there you can install cwm touch recovery 6.0.1.2 which is awesome. The version in ez recovery does not support jelly bean, so be careful.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Nice, now scrap that ez recovery and install rom manager. From there you can install cwm touch recovery 6.0.1.2 which is awesome. The version in ez recovery does not support jelly bean, so be careful.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I installed the cwm 6.0.1.0, is that the one you are talking about? I installed just fine fine with it, I really would like to use the touch screen one like twrp, what do you guys think about it?
Cwm has a touch version that you can install through their rom manager app. It's the same 6.0.1.2 version. EZ recovery only has the 5. something version of cwm touch which cannot be used on jb. Download rom manager app from play store, install current cwm recovery through the app, then choose install cwm touch recovery option on bottom, choose download from website (it's free there, paid through the market for some reason), choose your phone model, and that's it.
Sent from my SCH-I535 using xda premium
annoyingduck said:
Nice, now scrap that ez recovery and install rom manager. From there you can install cwm touch recovery 6.0.1.2 which is awesome. The version in ez recovery does not support jelly bean, so be careful.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
incorrect...the cwm6.0.1 version in ez recovery works just fine!
---------- Post added at 10:44 AM ---------- Previous post was at 10:43 AM ----------
annoyingduck said:
Cwm has a touch version that you can install through their rom manager app. It's the same 6.0.1.2 version. EZ recovery only has the 5. something version of cwm touch which cannot be used on jb. Download rom manager app from play store, install current cwm recovery through the app, then choose install cwm touch recovery option on bottom, choose download from website (it's free there, paid through the market for some reason), choose your phone model, and that's it.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
incorrect again! Imo rom manager can cause more problems then its worth...op follow section 5 of my guide for flashing anything aosp jb related.
It's not the touch version 6.0.1.2. It's the regular one. The touch available in that application is 5.8 version, not wise to run with jb. How can I be any clearer? That app will not give you cwm touch 6.0.1.2.
Sent from my SCH-I535 using xda premium
annoyingduck said:
It's not the touch version 6.0.1.2. It's the regular one. The touch available in that application is 5.8 version, not wise to run with jb. How can I be any clearer? That app will not give you cwm touch 6.0.1.2.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
you dont need cwm touch...regular cwm6.0.1 works just fine from the ez recovery app. not to mention it works for everything. the reason im saying this is because new users need to learn how to manually flash things first to get a better understanding of what they are doing. rom manager can cause more trouble for folks like the op who flash things before doing research. sorry not trying to give ya a hard time as what you said is correct, i just dont think its a good recomendation for the op.
Wow, seriously, have you read the post? Op wanted a TOUCH recovery compatible with jb based rom's. That's the info I gave him on how to correctly install the most current version. Why are you trying to negate my absolute CORRECT answer to his questions?
Sent from my SCH-I535 using xda premium
annoyingduck said:
Wow, seriously, have you read the post? Op wanted a TOUCH recovery compatible with jb based rom's. That's the info I gave him on how to correctly install the most current version. Why are you trying to negate my absolute CORRECT answer to his questions?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
reread my last post...
Gotcha, thanks
Sent from my SCH-I535 using xda premium
delete
Ok I know my boot loader is unlocked, and I'm running slim bean which is AOSP, if I installed any of the tw ROMS would I encounter any problems?
maurogg84 said:
Ok I know my boot loader is unlocked, and I'm running slim bean which is AOSP, if I installed any of the tw ROMS would I encounter any problems?
Click to expand...
Click to collapse
just make sure to wipe data before flashing and you will be fine.
Here's phone info prior to the mess:
v21y
mokeeOS
latest gb harsh kernel
CWM v5.0.2.0
I went ahead and tried to flash a new rom and a new kernel. I guess it wasn't compatible and got stuck on boot animation for over 30mins. So i thought I'd pulled the battery. I did a nandroid restore (used it before and works) and it wont boot into the system. It just goes back to recovery.
Then I tried to flash mokeeOS and harsh kernel. After rebooting it goes back into recovery.
I tried many roms / kernels that previously work and it still goes back to recovery. I tried nvflashing recoveries (CWM touch, twrp), same thing happens. Now what should I do?
update: I flashed stock recovery. It shows an arrow going out the box and an android.
update: this clean up batch tool fixed it for me: http://forum.xda-developers.com/showthread.php?p=24635755
Never heard you say you wiped/formatted anything
if not there will be residue from your old ROM/kernel and you may have the same situation
Sent from my Nexus 7 using xda premium
Hey buddy, click this link http://forum.xda-developers.com/showthread.php?p=24635755, download the tool, follow directions and you'll be golden. It's happened to me and this fixed it right up. Hope you get it straight, PM me if you have any more questions.
Sent from my LG-P999 using xda app-developers app
mustangtim49 said:
Hey buddy, click this link http://forum.xda-developers.com/showthread.php?p=24635755, download the tool, follow directions and you'll be golden. It's happened to me and this fixed it right up. Hope you get it straight, PM me if you have any more questions.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
ya i found it before i received an answer. that tool worked great. thanks xda
Sent via G2x mokee OS
Np
Sent from my LG-P999 using xda app-developers app
Okay so I bought a Blaze a few days ago and I was messing around with it and I rooted it. When I rooted it I flashed a ROM and when the ROM booted up and got to the welcome screen it instantly turned rebooted itself, so I let it boot up again but it constantly reboots. Then I went back to a backup of the stock ROM and it still does the same thing. So I followed a guide that updated me to the ICS update in hopes of it fixing it but it still does the same thing! Now I don't know what to do with it. I was hoping maybe someone can help or if this has happened to anyone? Thanks in advance
Favelarx said:
Okay so I bought a Blaze a few days ago and I was messing around with it and I rooted it. When I rooted it I flashed a ROM and when the ROM booted up and got to the welcome screen it instantly turned rebooted itself, so I let it boot up again but it constantly reboots. Then I went back to a backup of the stock ROM and it still does the same thing. So I followed a guide that updated me to the ICS update in hopes of it fixing it but it still does the same thing! Now I don't know what to do with it. I was hoping maybe someone can help or if this has happened to anyone? Thanks in advance
Click to expand...
Click to collapse
did you wipe data/cache/dalvik in recovery?
Yes I did all of that like a billion times and still nothing
I see you only have ten post so my first question is are you just new to xda and have knowledge and experience with root and recovery and custom roms or is this all new to you?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Jserrano56 said:
I see you only have ten post so my first question is are you just new to xda and have knowledge and experience with root and recovery and custom roms or is this all new to you?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've been a member for a while I just don't post much but no this is not all new to me, I have some experience and knowledge with rooting, and installing ROM's and such. I am new to this phone though.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
What ROM and kernel were you trying to flash? What recovery did you flash?
Romman0 said:
What ROM and kernel were you trying to flash? What recovery did you flash?
Click to expand...
Click to collapse
I was trying to flash the MIUI build and I think it came with a kernel that I had to download but I'm not sure. I flashed CWM I forgot what version it was
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Yes, the miui we have has a link to racing's blue lightning. I would try miui or another ROM again, but make sure to format /system along with wiping data, cache, and davlik. Or use black hole wipe. If you don't have anything important on the internal SD (or back it up) it might be worth it to format the emmc also.
Romman0 said:
Yes, the miui we have has a link to racing's blue lightning. I would try miui or another ROM again, but make sure to format /system along with wiping data, cache, and davlik. Or use black hole wipe. If you don't have anything important on the internal SD (or back it up) it might be worth it to format the emmc also.
Click to expand...
Click to collapse
Well I already went back to stock with one of the guides posted and it still does the same thing I don't know what to do with it anymore
Sent from my SAMSUNG-SGH-T989 using xda app-developers app