Database Info

TWRP from CWM???

Was gonna give TWRP recovery a try... I am currently using CWM and didn't know if it would be safe to just use the goo app and flash TWRP that way. I have always used CWM and wanted to try something new and just want to be safe when going about it.
Sent from my SCH-I535 using xda app-developers app

I tried it, but I didn't like much. To much switching pages to do things, such as format, erase cashed, and dalvic. But who knows you might just like it.
Sent from my SCH-I535 using xda app-developers app

Yes you can install TWRP any way you like. One recovery will simply overwrite the other. Nothing to worry about.

My only brick
The one time i ever truly bricked a phone after close to 30 times rooting and unlocking boot loaders was with TWRP and this phone. I am talkin complete brick, like qualcom drivers request show up on windows brick, the kind brick that you just throw at a window, because you got no charging light, no vibration, no light what so ever.
Btw i was only flashing a rom
I never touched TWRP after .

Thanks for the input guys..... Gonna stick with CWM for now. Seen a fair amount of negative stuff towards TWRP in the forums and don't want to risk anything.
Sent from my SCH-I535 using xda app-developers app

Been running TWRP since received pre-order device. No problems whatsoever.

prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
Seconded.

Used the gooapp to flash twrp and haven't had any problems. In fact I switched over from cwm because while installing liquidsmooth cwm kept giving me error 7. Everything I googled told me it was a problem with my recovery, so switched to twrp and presto
Although watch which version of twrp because I was reading the Cleanrom lite thread and ppl were having issues with the latest twrp at the time of their postings. It was around end of September that they were saying this, I believe.
Sent from my SCH-I535 using xda premium

prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
Thirded

prdog1 said:
Been running TWRP since received pre-order device. No problems whatsoever.
Click to expand...
Click to collapse
+1
Sent from my SCH-I535 using xda app-developers app

I used to use cwm and now have been using twrp and have never had a problem. This guy above you can't blame twrp for your brick you don't know if that's what it was. Twrp I like better cause I can move my backup folder and copy it even to another computer. Cwm has the blob folder which you can't see which files belong to which backup so you can't just move one backup you have do do them all
Tap'n

evolishesh said:
I tried it, but I didn't like much. To much switching pages to do things, such as format, erase cashed, and dalvic. But who knows you might just like it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Don't know what you were looking out but CWM is the one where the wipes/format are on different pages. All wipe options in TWRP are on the wipe page right next to each other. Newest version now released.

[Q] Reboot get stuck in boot loop

So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.

Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium

It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium

ToxicWaste said:
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Evita

subarudroid said:
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I've tried a couple times with the same result. I'll try again and see if anything different happens. Maybe just by some miracle I'll get it working again

I'm not sure how it works with safari for Mac. I do know that when I download ROMs with crome it some how downloads corrupt zips. On ei9 it works fine.
Sent from my One X using xda premium

uncledoobie said:
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Click to expand...
Click to collapse
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2

ImagioX1 said:
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Ok, I'll give that a shot. I installed CleanRom 5.1 today, ran some reboots and that seemed to clear it up. It might be a Jellybean thing, but who knows. Thanks for all the suggestions and quick responses!

Oh yea there is some discussion about a Rev-a or rev-b that is on your box having issues with 4.2 jb not working. I think its rev-b that everyone is having issues with.
Sent from my One X using xda premium

[Q] {q} HELP! MORON ATTACK! This thing is like a soap opera

So, yesterday, I had a perfectly functioning, stock 4.1.1/rooted unit.
Got a little frisky and decided to try out Liquid Smooth. Flashed that through recovery (it's a 4.2.1 Beta 2) but forgot to do the bootlocker.
The latest LS has a Bluetooth sound problem that's pretty bad. So, I thought I'd switch over to CM10.1, their 4.2.1 effort.
Well, without the bootlocker in place, you can pretty much guess how that worked out.
So now, I've odin'ed a variety of roms and so forth; no clue what happened to my backup.
My main focus has been what I call the dunce-cap routine, of going back to stock and starting over.
The problem? I did that and now I'm stuck in roaming mode and my calls don't work.
I'm dead without this phone (considering how long I've been working on this, since 8 pm or so yesterday except for a couple of hours of sleep, I might be dead, period.) and I've got to have one functioning. It's so bad that I'm considering just trashing it and buying another one, even thought THAT would hurt.
Almost everything I try winds up either getting the yellow triangle or the odin fail.
Now, thanks to some help I've gotten here that focused me into understanding this total screw up is MY fault completely, I believe I know what has to be done.
The plan was to go back to stock, root and DO THE DAMNED BOOTLOCKER, then go back into CM10.1 and make some changes in subscribing to CDMA or something (don't have that in front of me this second) to get the phone part of the phone operational but I can't get there.
In the guide here I have completed step 1, flashing the factory image.
The next step is blowing me up. I have used the file I have for the Recovery: CWM6023TouchVZW.tar.md5.tar, maybe 4 times.
NOW when I try it, odin fails and the phone tells me "secure check fail : recovery."
And help would be appreciated. Before I feed this thing to my Doberman Cavalier Spaniel. Or something.

Have you tried Odin with a completely stock rom?
Sent from my SCH-I535 using xda app-developers app

Jarredw said:
Have you tried Odin with a completely stock rom?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yup. Completely stock rom is installed. The next step was installing the recovery... and using a file that I had used before, that's where I'm running into the problem of the secure check fail.
That very file HAS worked before, 3 or 4 times with no problem.

Why does the file end in ".tar.md5.tar"? It's supposed to end in ".tar.md5" Since owning this phone, I've never seen a file with ".tar" twice in the file name.
Sent from my SCH-I535 using xda app-developers app

kage87z said:
Yup. Completely stock rom is installed. The next step was installing the recovery... and using a file that I had used before, that's where I'm running into the problem of the secure check fail.
That very file HAS worked before, 3 or 4 times with no problem.
Click to expand...
Click to collapse
Disregard that, I'll be back in a minute with some help. I'm pretty sure the new boot chain will not except custom recovery. Try this guide.
http://forum.xda-developers.com/showthread.php?p=35418324
Sent from my VS920 4G using xda app-developers app

If you were able to Odin a stock rom then Odin a stock rom that has been pre rooted and then just use ez recovery from the play store to flash cwm
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
Disregard that, I'll be back in a minute with some help. I'm pretty sure the new boot chain will not except custom recovery. Try this guide.
http://forum.xda-developers.com/showthread.php?p=35418324
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
OK.... working this.
Looks good. Booted into the rom with no warnings... It says "pass."

Jarredw said:
If you were able to Odin a stock rom then Odin a stock rom that has been pre rooted and then just use ez recovery from the play store to flash cwm
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
this was going to be my suggestion also.

ddurandSGS3 said:
this was going to be my suggestion also.
Click to expand...
Click to collapse
Any suggestions as to where I might get one of those?
The 5 minute time limit can be a PITA.

SlimSnoopOS said:
Why does the file end in ".tar.md5.tar"? It's supposed to end in ".tar.md5" Since owning this phone, I've never seen a file with ".tar" twice in the file name.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The problem is that when I unzip it, I don't get an md5 file, I get an "image" file of some sort.

kage87z said:
Any suggestions as to where I might get one of those?
The 5 minute time limit can be a PITA.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda app-developers app

Update: OK... have gone through the guide which went brilliantly.
Now, do I just boot this thing into recovery and flash the CM10.1?
Is there anything I've overlooked? Anything else I need to do?
And do I do the factory reset/wipe dalvik and the rest before, or after?
I presume I have to use ezlock to unlock the bootloader again after this, right?

No, you still need to unlock bootloader and backup your IMEI. You may want to do quite a bit of reading, CM 10 is not as easy to fix some of the potential problems that you could possibly encounter.
I am not hating on them, but don't think it is as simple as one of the TW ROMS.

HHF2 said:
No, you still need to unlock bootloader and backup your IMEI. You may want to do quite a bit of reading, CM 10 is not as easy to fix some of the potential problems that you could possibly encounter.
I am not hating on them, but don't think it is as simple as one of the TW ROMS.
Click to expand...
Click to collapse
When I try this method to back up the IMEI it doesn't do anything after entering the *#7284# and if I hit the phone, it just sends me to a Verizon intercept operator.
The only reason I'm trying to get into a 4.2.1 ROM again was this:
http://forum.xda-developers.com/showpost.php?p=36396278&postcount=5
Just flash cm10.1 and fix your mobile settings. CDMA subscription > ruim/sim and toggle airplane mode.
This isn't the first time someone has had this problem.
Sent from my SCH-I535 using xda app-developers app
4.1.1 doesn't have this capability, and up to now, I haven't seen any other way to address the original issue.

Of you followed the guide I linked you are unlocked with cwm so boot into recovery wipe caches and reset and flash cm10.1 and gapps. First verify you are unlocked
Sent from my VS920 4G using xda app-developers app

kintwofan said:
Of you followed the guide I linked you are unlocked with cwm so boot into recovery wipe caches and reset and flash cm10.1 and gapps. First verify you are unlocked
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
OK, using EZLock I unlocked it successfully, but the status in EZLock is still listed as "unknown."

kage87z said:
The only reason I'm trying to get into a 4.2.1 ROM again was this:
http://forum.xda-developers.com/showpost.php?p=36396278&postcount=5
Just flash cm10.1 and fix your mobile settings. CDMA subscription > ruim/sim and toggle airplane mode.
This isn't the first time someone has had this problem.
Sent from my SCH-I535 using xda app-developers app
4.1.1 doesn't have this capability, and up to now, I haven't seen any other way to address the original issue.
Click to expand...
Click to collapse
If you can't figure it out you can pm me
Sent from my SCH-I535 using xda app-developers app

kage87z said:
OK, using EZLock I unlocked it successfully, but the status in EZLock is still listed as "unknown."
Click to expand...
Click to collapse
Just power on your phone if Samsung flashes very fast you're unlocked
Sent from my VS920 4G using xda app-developers app

kintwofan said:
Just power on your phone if Samsung flashes very fast you're unlocked
Sent from my VS920 4G using xda app-developers app
Click to expand...
Click to collapse
OK... it did... I'm going for it.
Stuck on "waiting for network."
Used the four taps method to get past it
I have no APN listed..

kage87z said:
OK... it did... I'm going for it.
Stuck on "waiting for network."
Used the four taps method to get past it
I have no APN listed..
Click to expand...
Click to collapse
Have you changed the subscription type to sim and toggled airplane mode
Sent from my VS920 4G using xda app-developers app

RAZR HD Maxx rootability

Just replaced Samsung Galaxy Nexus with this razor. Should be a step up right? Apparently I'm spoiled. Wife has the bionic so I'm familiar with the basic process.
Doing research, resetting the device like 15 times and reading a ton of threads in the last couple days, it looks like I have the phone itself actually rooted however I'm not able to fully install safe strap.
What's interesting to me is that I can use programs that require root access far as I can tell with no issue, root checker shows root is available as well. Trying to reboot into recovery though does not give me the safety strap splash screen to choose any kind of recovery option. Just rolls into DROID...
Is this pretty normal if the previous owner accepted the OTA update to take me to 9.18.79? Are we stuck?
Sent from my DROID RAZR HD using xda app-developers app

Did you open safestrap and install recovery?
Sent from my XT912 using Tapatalk 4

Sure did. Says installed and from all the videos I've seen explaining the install/usage and my wife phone installation, I'm quite sure it's installed.
I've tried multiple versions just to be sure clearing data and uninstalling previous versions etc.
At this point I'm just not sure if this is normal or not because of the OTA version that's on here.
Sent from my DROID RAZR HD using xda app-developers app

Thinking that the safe strap process should be the same but realized that there is a set of HD XT926 forums I should probably be posting in. Didn't realize the differences.
Mod move this post if needed.
Thanks anyways.
Sent from my DROID RAZR HD using xda app-developers app

You can prove with BMM hmmmmm!!!

vegaIT said:
You can prove with BMM hmmmmm!!!
Click to expand...
Click to collapse
Tried to install bmm from the Play Store however it did not seem compatible with my XT 926. Am I missing something?
Sent from my DROID RAZR HD using xda app-developers app

Going to try something called philz touch. Let's see if I get better results. Anyone try it?
Sent from my DROID RAZR HD using xda app-developers app

Just wondering, it wasn't clear, are you on the 9.18.79 build or not sure? A screen shot of your "about phone" screen could tell unless someone rolled back. Only reason I ask is, safest rap is great if there are no options but unlocked is where the real profit is.
Sent from my XT926 using XDA Premium 4 mobile app

bweN diorD said:
Just wondering, it wasn't clear, are you on the 9.18.79 build or not sure? A screen shot of your "about phone" screen could tell unless someone rolled back. Only reason I ask is, safest rap is great if there are no options but unlocked is where the real profit is.
Sent from my XT926 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep, that's the version I'm at. I think I mentioned that in the original post. From everything I'm reading I should be able to install and run safe strap with no issues but it just doesn't ever bring up the menu. At this point I'm looking for alternatives I guess.

grnsl2 said:
yep, that's the version I'm at. I think I mentioned that in the original post. From everything I'm reading I should be able to install and run safe strap with no issues but it just doesn't ever bring up the menu. At this point I'm looking for alternatives I guess.
Click to expand...
Click to collapse
are you sure its not already unlocked?
if you havent already, i would flash back to clean stock, not just wipe/"reset", and try again. wiping wont get rid of or fix anything in the system directory.

First off don't attempt to flash any aftermarket recovery if your BL is locked, you might run into issues. Second, SafeStrap doesn't replace your stock recovery because you can't replace your stock recovery if you have a locked BL. To get into SS, just boot your phone normally. Once the phone boots, you'll get the SS screen that allows you to go into SS recovery or boot into OS normally. Once in SS, then you can start running backups, flashing, etc.

i didnt see anyone suggest he flash a stock recovery.
he got the phone used, maybe its already unlocked, i didnt see that possibility confirmed or denied.

bweN diorD said:
are you sure its not already unlocked?
if you havent already, i would flash back to clean stock, not just wipe/"reset", and try again. wiping wont get rid of or fix anything in the system directory.
Click to expand...
Click to collapse
When you say UNLOCKED, are you referring to the Boot Loader? If so, I do not believe that it is, just Root at this time.
RikRong said:
First off don't attempt to flash any aftermarket recovery if your BL is locked, you might run into issues. Second, SafeStrap doesn't replace your stock recovery because you can't replace your stock recovery if you have a locked BL. To get into SS, just boot your phone normally. Once the phone boots, you'll get the SS screen that allows you to go into SS recovery or boot into OS normally. Once in SS, then you can start running backups, flashing, etc.
Click to expand...
Click to collapse
100% agree with this, should be that simple. Happens properly on the Mrs Bionic so I'm familiar with that process. This phone doesn't produce the menu no matter what version of Safe Strap is installed (tried multiple).
bweN diorD said:
i didnt see anyone suggest he flash a stock recovery.
he got the phone used, maybe its already unlocked, i didnt see that possibility confirmed or denied.
Click to expand...
Click to collapse
Planning to go back to stock stock, beyond the wipe. I believe a previous poster mentioned that the standard wipe doesn't remove root. A fresh start may be my next step. Hoping the 1.32 Droid Razr Utility by Mattlgrof http://forum.xda-developers.com/showthread.php?t=2474393 will do that for me.

grnsl2 said:
When you say UNLOCKED, are you referring to the Boot Loader? If so, I do not believe that it is, just Root at this time.
100% agree with this, should be that simple. Happens properly on the Mrs Bionic so I'm familiar with that process. This phone doesn't produce the menu no matter what version of Safe Strap is installed (tried multiple).
Planning to go back to stock stock, beyond the wipe. I believe a previous poster mentioned that the standard wipe doesn't remove root. A fresh start may be my next step. Hoping the 1.32 Droid Razr Utility by Mattlgrof http://forum.xda-developers.com/showthread.php?t=2474393 will do that for me.
Click to expand...
Click to collapse
just boot into the bootloader screen (vol+power) and see if it says device locked or unlocked (may have to choose "fastboot", to see it i dont recall)
yes Matts utility will clean the phone for you, i updated it to 1.3+ for him

Used the utility to wipe the phone and reflash back to stock, at least that version. All seems good however moto chopper doesn't fully install root with superuser. I get the typical su binary needs to be installed and that fails.I did tried to run the updates in Play Store that was available as well as clearing data etc with no luck. I think the last time that I was able to successfully Foot I used a different Root program, razor maybe?

grnsl2 said:
Used the utility to wipe the phone and reflash back to stock, at least that version. All seems good however moto chopper doesn't fully install root with superuser. I get the typical su binary needs to be installed and that fails.I did tried to run the updates in Play Store that was available as well as clearing data etc with no luck. I think the last time that I was able to successfully Foot I used a different Root program, razor maybe?
Click to expand...
Click to collapse
read the post from the utility, the root in the utility is not the one you need to use. the correct one is in the post. (it actually says it in the command window of the tool too)
when i get time, ill try to integrate the new root.

Okay, my apologies, I thought it was updated 2 or 3 times in the last couple days and thought that was updated that as well. :thumbup:
Sent from my DROID RAZR HD using xda app-developers app

grnsl2 said:
Okay, my apologies, I thought it was updated 2 or 3 times in the last couple days and thought that was updated that as well. :thumbup:
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
np, i did update it a few times, but working 6 days a week, i dont feel like messing with the root right now.

So I've just done option 1 with the factory reset, then ran moto chopper 1.32 and have good root. Confirmed. Ver. 9.20.1
Safe strap seems to be the only issue I keep having. The menu just simply doesn't come up while booting. Doesn't matter if the phone is completely shut off and turned on or rebooted.
Puzzled.
Sent from my DROID RAZR HD using xda app-developers app

bweN diorD said:
i didnt see anyone suggest he flash a stock recovery.
he got the phone used, maybe its already unlocked, i didnt see that possibility confirmed or denied.
Click to expand...
Click to collapse
Grns did mention that he might try flashing PhilZ recovery, that's why I said what I did. His OP also mentioned that the previous owner took the latest OTA, so it's highly probably that he's locked up (though, not 100% certain). I'm only suggesting these things in advance, so that he doesn't run into problems.
As for your SS issues, that's kind of weird. You should get the options as soon as the phone boots up.

[Q] Can't access /system from recovery !

Hi guys.
I have some problems with my recovery, here is my story.
I was running last TWRP, and while doing an update of my favorite ROM, the installation was stuck at fomatting system... I tried to reboot several times and nothing to do it couldn't work.
So I installed (in a dirty way) CWM to try it. Formatting seemed to work and it's still working (or at least it's written that the operation is done) BUT when I want to update my ROM and when the script needs at the beginning to format system, it's stuck for several minutes. Sometimes it works only after 3 or 4 times (or maybe it's because I don't wait enough) and so then everything works out but I've got a message like "the error was system", can't remember sorry, if you need what is exactly written I'll tell you.
So why should I do ?
Thanks.
Hope you understood me, my english kinda sucks..

I think your best bet at this point would be flashing the factory images and starting fresh. I don't use twrp myself, but for what I've read here, it's best to let it finish what it's doing and not reboot.
Sent from my Nexus 5 using Tapatalk

adrman said:
I think your best bet at this point would be flashing the factory images and starting fresh. I don't use twrp myself, but for what I've read here, it's best to let it finish what it's doing and not reboot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well when it's endless I can't let him finish I guess...
I don't know why system image would change anything because it has nothing to do with recovery. Maybe you meant stock recovery and then put back CWM ?

Up please I need an answer

Tomatot- said:
Well when it's endless I can't let him finish I guess...
I don't know why system image would change anything because it has nothing to do with recovery. Maybe you meant stock recovery and then put back CWM ?
Click to expand...
Click to collapse
Same thing happened to me. In fact posted a similar post earlier. I used the nexus recovery tool once to get back to stock and that worked but erased everything on my phone.
Did it one other time successfully flashed one rom and then some thing happened but this time I had a backup in twrp and was able to restore that.
The only thing now is my battery won't charge past 77%.
Sent from my Nexus 5 using XDA Premium 4 mobile app

You guys really need to understand what you're doing before flashing. Start with these
http://forum.xda-developers.com/showthread.php?p=47025283
http://forum.xda-developers.com/showthread.php?p=47096456

jd1639 said:
You guys really need to understand what you're doing before flashing. Start with these
http://forum.xda-developers.com/showthread.php?p=47025283
http://forum.xda-developers.com/showthread.php?p=47096456
Click to expand...
Click to collapse
Yeah that is a great how to but I've already rooted and unlocked phone. I understand how to flash roms, I have at least 10 android devices in my home that I flash roms to.
I know the process, it is the same on most devices. The problem with this one is when you go to flash a new rom it says it can't mount system and gets stuck in endless install.
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
Same thing happened to me. In fact posted a similar post earlier. I used the nexus recovery tool once to get back to stock and that worked but erased everything on my phone.
Did it one other time successfully flashed one rom and then some thing happened but this time I had a backup in twrp and was able to restore that.
The only thing now is my battery won't charge past 77%.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same issue flashing elemental kernel. After the reboot I couldn't access my SD and my baseband weren't recognised. So I reloaded a nandroid backup but the issue was still present. I have never encountered a so strange problem. Resolved reverting to stock and reflashing elementalx.

jd1639 said:
You guys really need to understand what you're doing before flashing. Start with these
http://forum.xda-developers.com/showthread.php?p=47025283
http://forum.xda-developers.com/showthread.php?p=47096456
Click to expand...
Click to collapse
You must be kidding me... Did you even read my post ?

Tomatot- said:
You must be kidding me... Did you even read my post ?
Click to expand...
Click to collapse
Twrp system may not automatically mount. From twrp select mounts and system. Or reboot recovery.
Sent from my Nexus 5 using Tapatalk

jwhyte said:
Twrp system may not automatically mount. From twrp select mounts and system. Or reboot recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried that when I shaving that problem but system would not Allow me to mount system. It would let me check off everything but that.
Sent from my Nexus 5 using XDA Premium 4 mobile app

nelomen said:
I tried that when I shaving that problem but system would not Allow me to mount system. It would let me check off everything but that.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing twrp with adb again? Not sure why it wont mount system.
Sent from my Nexus 5 using Tapatalk

jwhyte said:
Twrp system may not automatically mount. From twrp select mounts and system. Or reboot recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'll try that but it's weird because it never happenned to me before and now it's happenning to me every time.

Tomatot- said:
I'll try that but it's weird because it never happenned to me before and now it's happenning to me every time.
Click to expand...
Click to collapse
I have already gone back to stock completely and started all over to verify I did everything correct. I got sane results not sure if Tomatot has tried more than once.
Not sure if it makes a difference but my N5 is the t-mobile store version.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Mine is from Google Play. Today I flashed a ROM and before I mounted system. The installation was very long (more than usual i'd say) but it finally worked !

Tomatot- said:
Mine is from Google Play. Today I flashed a ROM and before I mounted system. The installation was very long (more than usual i'd say) but it finally worked !
Click to expand...
Click to collapse
Glad to see yours is working. I was able to flash the stock 4.4.1 but it was still feeling a little wonky. Battery got stuck again this time at 35% so I used nexus tool to return to stock completely but still same issue with battery. I think I'm going to lock it and exchange it at the T mobile store.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Here is what's happenning :
"
Formatting /system (takes about 5 minutes)
Extracting /system
Symlinking
Flashing boot.img
Yeah !
Script succeeded : resultat was [/system]
Can it help you guys ?