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.
Related
Does one ever really NEED to update your recovery? I currently have a very early version of koush's touch recovery (v5.0.1? or 5.1.0 something). and also, if i update my recovery, will it erase my entire sd? (like when initially flashing a custom recovery) Thank you
wudien said:
Does one ever really NEED to update your recovery? I currently have a very early version of koush's touch recovery (v5.0.1? or 5.1.0 something). and also, if i update my recovery, will it erase my entire sd? (like when initially flashing a custom recovery) Thank you
Click to expand...
Click to collapse
No it won't erase anything.
And it depends on which version you have. Some versions had bugs that got corrected, some have new features. It's not necessary most of the time unless you got a very old one with bugs, obviously.
wudien said:
Does one ever really NEED to update your recovery? I currently have a very early version of koush's touch recovery (v5.0.1? or 5.1.0 something). and also, if i update my recovery, will it erase my entire sd? (like when initially flashing a custom recovery) Thank you
Click to expand...
Click to collapse
Although it's not "vital" to update the recovery, it's always worth doing so.
having it updated means new feats has been added or bugs have been ironed out.
I, for example, lost my IMEI due to something wrong happened while flashing, caused by either the .zip or the recovery, not sure which one though...
Sent from my Nexus S using xda app-developers app
ozone89 said:
Although it's not "vital" to update the recovery, it's always worth doing so.
having it updated means new feats has been added or bugs have been ironed out.
I, for example, lost my IMEI due to something wrong happened while flashing, caused by either the .zip or the recovery, not sure which one though...
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Likely the zip, not the recovery.
What did losing your imei do? Where you blackballed from your network? Some of us would like not to have a dna-like identification number.
Sent from my Nexus 7 using xda app-developers app
wudien said:
What did losing your imei do? Where you blackballed from your network? Some of us would like not to have a dna-like identification number.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Can't make calls or use the network at all.
there;s no actual need to update your recovery..there arent many major bugs reported
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
Back in the day (droid eris days) there was cwm and twrp and twrp was thought of to cause more issues than anything so it was recommended to use cwm. Now it seems to have changed (at least regarding the gs3). Is this true? IS twrp that much better/stable/safer than cwm? I've never used twrp (have seen videos/screen shots) and it looks alot easier...well user friendly...just curious as to if it is more stable/safer or just as safe as cwm? When it comes to changing the recovery in a phone I view that as updating a bios in your computer...don't do it unless you really really need to (last time I upgraded a bios the power went out the same time....not a good day). Just curious as to fellow flashers opinion on the topic? Seems twrp has been getting alot more updates than cwm as well.
EI
Excessiveidling said:
Back in the day (droid eris days) there was cwm and twrp and twrp was thought of to cause more issues than anything so it was recommended to use cwm. Now it seems to have changed (at least regarding the gs3). Is this true? IS twrp that much better/stable/safer than cwm? I've never used twrp (have seen videos/screen shots) and it looks alot easier...well user friendly...just curious as to if it is more stable/safer or just as safe as cwm? When it comes to changing the recovery in a phone I view that as updating a bios in your computer...don't do it unless you really really need to (last time I upgraded a bios the power went out the same time....not a good day). Just curious as to fellow flashers opinion on the topic? Seems twrp has been getting alot more updates than cwm as well.
EI
Click to expand...
Click to collapse
I only used TWRP, its so much more innovative and easy to use with the touch based interface and i have absolutely no problems with it.
Another another note, probably not the right forum for this thread lol...
Yea I wasn't sure if this was the right forum or not.... But figured recovery deals with development sooooooo...
Sent from my SCH-I535 using xda app-developers app
Excessiveidling said:
Yea I wasn't sure if this was the right forum or not.... But figured recovery deals with development sooooooo...
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You were still in the wrong. Plus, there's already a dedicated TWRP recovery thread in the dev section.
To answer your question, TWRP really is a nice recovery. I usually stay a few versions behind the latest because what works now is good enough for me. I don't think you can go wrong with either TWRP or CWM, but having used CWM for so long I wanted to see what else was out and TWRP didn't disappoint. It's as safe as a custom recovery can be flashing modified software not intended for your phone.
Sent from my SCH-I535 using xda app-developers app
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
ScottBroker said:
What is the best way to install CWM on my TF300T, I am on the 4.2 bootloader, and I tried to put the CORRECT JB 4.2 version of TWRP 2.5.0 and it is like a split screen and will not function. Some time before that it asked for a password when I booted the recovery. I just want to start fresh with Clockwork Mod I guess.
Please point me in the correct direction.
Thank you
Click to expand...
Click to collapse
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Not to be a douche but use the search function. And use twrp. Cwm is too buggy on the tf300. Its very easy for it to bug out and brick your pad.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
ScottBroker said:
well you are being a DB!
Do you not think I would search , too many posts with too many options.
TY for nothing. TWRP on TF3000T is very buggy btw.
Click to expand...
Click to collapse
If you searched you would have seen all your questions are answered in the stickies. Also you would have seen twrp is recommended over cwm due to cwm bricking devices. I'm sure you would prefer that not to happen.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If anyone has some useful information, please let me know.
Thanks
ScottBroker said:
If anyone has some useful information, please let me know.
Thanks
Click to expand...
Click to collapse
First and foremost learn how to search. Its a damn stickied topic. Here is what your looking for took less than a minute to search. http://forum.xda-developers.com/showthread.php?t=2187982
If you learned to read you wouldn't have a double screened twrp.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
ScottBroker said:
I have tried that and still get a split screen, that is why I want to just flash CWM.
I have looked at that thread as well..
Click to expand...
Click to collapse
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mhays705 said:
Update to the most recent boot loader. I'm trying to tell you. You have to use twrp. Cwm bricks the tf300t while flashing ROMs. Everyone advises not to use it. I don't even think there's a guide here for it since its too much of a liability. If your getting a split screen you are doing something wrong. Reading everything and doing everything exactly right is the name of the game here. The tf300 is way to easy to brick. If your having problems just installing a custom recovery your best to just stay away from flashing on this device. You have to pay attention to boot loader version and firmware version or you are going to get errors. Your lucky you haven't hard bricked yet.
I know what I'm talking about. I didn't just fall off the turnip truck.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
ScottBroker said:
Thanks for the advise, but as you can see, I have almost 3 times the thanks than you have posts. But anyway, I have been flashing for years, I have had every Iphone, and every Galaxy and have not had problems like with the tablet. I like TWRP, I have the latest bootloader, I am on 4.2.....
Maybe I will just return to stock and start fresh again...
Thanks anyway
Click to expand...
Click to collapse
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
ScottBroker said:
FYI, I went back to stock, and reflashed, and now with your helpful guide, I am back on TWRP.
TY
Click to expand...
Click to collapse
This is defiantly one of the most sensitive device to do everything on. Asus wasn't to friendly. Its like they want you to brick. And my bad about the rudeness extreme lack of sleep has made me very irritable.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
sbdags said:
Indeed flashing cwm is another way to brick the TF300. Lucky you didn't flash it.
The problem is that the latest bootloader changes the partition table on the TF300 - it makes /system larger in order to accommodate the larger Asus ROM. The issue is most of the legacy recoveries including the non 4.2 twrp and cwm don't understand this and thus the device becomes bricked as the partition table is now messed up.
Click to expand...
Click to collapse
Gotta love sbdags knowledge and amazing rom
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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 ?