The following is provided FYI
I have been using the ROM here: http://forum.xda-developers.com/showthread.php?t=1773362 version 8.1 with great success for a while now, but when I decided to try another ROM, I got into major trouble and barely escaped.
My chronicle of woe began when I decided to first update to indirect's latest CWM release. I'm not criticizing him at all, he has done incredible and ground-breaking work on the NT, but in latter developments, I do think this was the source of the problem, and I cannot comment on his Dev thread about it.
After this I tried to flash an AOSP rom - I truly can't remember which anymore - and found myself stuck in a boot loop. I've flashed several roms in the past, so I tried again and got the same symptom. No biggie, back to 8.1 I go...
Except it had the identical problem. Now I'm worried, so back to the trusty team-B CM7...
Uh-oh, now I'm out of the boot loop, but the touchscreen is dead, and I cannot access recovery. If I'd thought this through better, I'd have realized the 5-point touch firmware upgrade made CM7 incompatible. Blast...
After some fiddling around, the NT started booting again into CWM (yay) all on it's own. I restored 8.1 again, back to the boot loop, but at least I can reliably reach CWM again.
Next, I tried Adam Outler's famed Ubuntu restore SD. Many have been saved by this clever piece of code, and I am not criticising him either (in fact, I'm hoping he'll produce a full Ubuntu eventually). But between CWM and Cyanoboot, his card would not work it's magic for me...
As a last ditch effort, I hunted around on the web and found this: http://forum.xda-developers.com/showthread.php?t=1640958 (gotta love XDA)
I followed the instructions for flash_CM9_CM10 version, rebooted back into recovery, installed 8.1, and voila - got my nook back.
Was it Indirect's update that got me in a pickle, or some combination of things I did? Was my new ROM not compatible somehow? I dunno, would take a mightier mind than mine to sort that out. My take-aways are as follows:
1. Consider carefully before flashing Indirect's CWM update.
2. Mr Outler's Ubuntu recovery is not a universal "get out of jail free" card. Remember, there can be consequences and repercussions for tinkering with your NT's innards.
3. When you get something that works satisfactory, consider sticking with it - refer to #2 above.
Thanks,
TM
I appreciate your sharing of your experience, and I wholeheartedly agree with your point 2.
There is no such thing as a 100% get out of jail card!
Therefore you need to do research and read up before you start poking around. Something you didn't do, and almost had to pay for. That's the lesson to be learned from this and what needs to be pointed out in big letters. Not to avoid a specific app/script.
For example: If by Indirect's CWM you mean his app it's pretty clear if you read the topic that it's out of date and that it could also possibly cause trouble. I make it a habit of always checking out the last few pages/comments/reviews of anything I'm thinking of installing/flashing to get the latest news on it. My tip for future explorations, should you decide to not go with your no.3, but keep having fun trying new stuff!
Also this is yet another reminder that people need to be aware what they are doing when installing multitouch! Don't just click "yes I understand" (or whatever it says) unless you at least have thought about it!
Glad you got away with just a raised heartbeat this time! I've had couple of hickups myself when getting careless (starting to do something when I REALLY should have gone to get some sleep instead...), and the repart.img has done good things here as well!
---------- Post added at 03:23 PM ---------- Previous post was at 03:04 PM ----------
To clarify: I have tried Indirect's app (if that is what's referred to here) recently and posted in the topic about it. It didn't cause me any trouble at all, but it didn't install CWM 6.x.x like I hoped it would. It installed 5.x.x and to flash CM10 ROM you need CWM 6.x.x. Even though it says on the first page it does flash 6.x.x all I could see in the topic was that no one actually had any success with that lately. Maybe the OP's bootloop was caused by trying to flash a ROM that required CWM 6.x.x. with CWM 5.x.x?
Hi Asawi,
Thanks for the reply. To put my experience in context, the devs here are the guys who build custom hot rods for street racing, and I am the guy who can change his spark plugs, but just barely. I readily admit 90% of everything goes right over my head around here.
It's more about "read carefully" in my case rather than "research", and even more specifically, "check the date". Exactly as you say, I saw a post from Indirect stating "Safety Fixes, PLEASE DOWNLOAD!" (his caps, not mine), and plunged in without noticing that the post was nearly a year old.
As I said, no disrespect to anyone, I wish I had the skill the devs here demonstrate every day. This misadventure was my fault, not Indirect's. One quibble - I stand by my statement to carefully consider the update, because if I had carefully considered it, I'd have caught on that it was old
I guess my attitude towards trying new roms and such is that there are always going to be bugs, it's just a question of can you live with them? I tried 8.2 and 8.3 in the post above, and both had issues relative to 8.1, so I rolled back. I'll probably try 8.4 when it comes out as well, just because I'm a fan, and I love seeing what these guys can accomplish.
Besides, it's self-correcting: I got in trouble with XDA, I got out with XDA. Gotta love XDA
As for multi-touch, I did read the info on it, and was aware that going back to an older ROM would create a problem - I just plain forgot about it in the panic. Meh, I'm only human. Since I'm at no harm now, if anybody reads this and takes heed, then it's all good.
Lastly, yes it's the CWM app exactly as you describe, and behaved as you describe. Interestingly, though, I was unaware it took CWM6 to flash a CM10 mod. I've been using the CWM from Indirect's very first root how-to from over a year ago to flash CM10 without troubles, and that was 5.x.x.x. I don't know how I got away with it, but that's where I was when all of this started.
Thanks again for the response
TM
Related
I received my new GTablet day before yesterday from Amazon. I read through a lot of forums before deciding to buy it. Out of the box, I charged it and connected it to the wireless network. Worked fine. It got updated as well. I tried few options and play with it a bit and then the most awful thing happened. I got this message "Sorry The application Dashboard Home (process com.tapntap.homne) has stopped unexpectedly. Please try again"
I tried power + volume but it didnt help. I want to go through the whole clockmod and tnt 2.4 update but right now I am stuck. Viewsonic supports recommed to send it back to Amazon and a get a newone. But if there is a way to start using my Gtablet 'now', please let me know. If I use the Clockmod, will I get stuck and will never be able to return it? I NEEED HELP...
coolrazas said:
I received my new GTablet day before yesterday from Amazon. I read through a lot of forums before deciding to buy it. Out of the box, I charged it and connected it to the wireless network. Worked fine. It got updated as well. I tried few options and play with it a bit and then the most awful thing happened. I got this message "Sorry The application Dashboard Home (process com.tapntap.homne) has stopped unexpectedly. Please try again"
I tried power + volume but it didnt help. I want to go through the whole clockmod and tnt 2.4 update but right now I am stuck. Viewsonic supports recommed to send it back to Amazon and a get a newone. But if there is a way to start using my Gtablet 'now', please let me know. If I use the Clockmod, will I get stuck and will never be able to return it? I NEEED HELP...
Click to expand...
Click to collapse
Do you have clockwork mod on it? If you DO put it on there, you CAN get it back off and return the unit to stock, so don't worry too much about that. You have to perform an nvflash though (which is not necessarily harder than installing clockwork mod or a custom rom, but can be problematic at times.)
The thread on that is here: http://forum.xda-developers.com/showthread.php?t=861950
If it were me, I would give installing clockwork mod a try and update to the newest viewsonic rom or try one of the custom roms such as Vegan, TnT Lite or TwoTapsX.
Hopefully it works out for you - I'm confident it will. These things are almost impossible to brick.
Thanks a lot for a quick reply. So the way I understood....
1: I need to install Clockmod and that will bring the Gtablet back to Stock
2: After that I need to do the nvflash
3: and then I can install tnt2.4
Does that make sense.... Do I need to do the nvflash.. Just from the look of it, it seems kind of complex.
Again I really appreciate your quick reply on this.
gogorman said:
Do you have clockwork mod on it? If you DO put it on there, you CAN get it back off and return the unit to stock, so don't worry too much about that. You have to perform an nvflash though (which is not necessarily harder than installing clockwork mod or a custom rom, but can be problematic at times.)
The thread on that is here: http://forum.xda-developers.com/showthread.php?t=861950
If it were me, I would give installing clockwork mod a try and update to the newest viewsonic rom or try one of the custom roms such as Vegan, TnT Lite or TwoTapsX.
Hopefully it works out for you - I'm confident it will. These things are almost impossible to brick.
Click to expand...
Click to collapse
coolrazas said:
Thanks a lot for a quick reply. So the way I understood....
1: I need to install Clockmod and that will bring the Gtablet back to Stock
2: After that I need to do the nvflash
3: and then I can install tnt2.4
Does that make sense.... Do I need to do the nvflash.. Just from the look of it, it seems kind of complex.
Again I really appreciate your quick reply on this.
Click to expand...
Click to collapse
1. No. ClockworkMod does not bring the tablet back to stock. It makes it easier to flash custom ROM's and backup your tablet.
2. No. You do not have to nvflash after installing Clockwork. That would remove it.
3. Sort of. You can go right to installing a custom ROM as soon as you have ClockworkMod installed. DO NOT use TwoTapsX if you have installed ClockworkMod. It will not work and will result in you having to do an nvflash. TnT_Lite will work just fine.
coolrazas,
I think you should be cautious!! VS has told you to exchange it. That might not be a
bad idea.
BUT, it all depends on how serious the original error was. And I haven't heard an
authoritative answer on that yet.
IF you can handle all the stuff that's been suggested -- you might make it good as
new. But you also could have more problems.
I know you are anxious to have the tab and be up and running -- but I'd make darn
sure I had a good one first even if that means sending it back.
Rev
I agree. I think I can handle the techie stuff (new to android but seasoned on Windows platform) but you are right. If the hardware is faulty then I will be facing the same problem again. When I called Viewsonic Customer support, they said that they are aware of this issue so just send it back. She was pretty straight on the phone.
And again, I have to ask this question. Why in the world isn't viewsonic spending more resources on software? With better software, the gtab would be in direct competition with both the xoom and ipad 2.
I completely agree. If the issues are known and after reading tons of information on xda forum, its insane not to listen to this large customer base and really bring this tablet to the next level and capture a larger chunk of the market. Pretty amazing.
K J Rad said:
1. No. ClockworkMod does not bring the tablet back to stock. It makes it easier to flash custom ROM's and backup your tablet.
2. No. You do not have to nvflash after installing Clockwork. That would remove it.
3. Sort of. You can go right to installing a custom ROM as soon as you have ClockworkMod installed. DO NOT use TwoTapsX if you have installed ClockworkMod. It will not work and will result in you having to do an nvflash. TnT_Lite will work just fine.
Click to expand...
Click to collapse
This is an excellent point - I should have mentioned this in my original reply.
coolrazas said:
I tried power + volume but it didnt help.
Click to expand...
Click to collapse
Did you let it actually restore the factory default? My Gtab did the same thing (I just got it last week) and I had to reset it. It's odd that the factory reset is different than what it ships with. But, either way, you have to wait for the message on the screen that it's reloading the image BEFORE you let go of the volume+ button.
Can Be Finicky....
coolrazas,
It also can be said that even in the best of times, the G-Tablet can be a
little finicky. One of my tablets the other day was a normal as could be.
I shut it down and the next day turned it back on. Continual "android.process.acore" errors. Had to fix it.
I say be conservative, be consistent in what you do, use only the "approved"
stuff, don't take advice you can't verify is good, and read, read, read, read!
Good luck to you. BTW, what I did was buy a second G-Tablet so I always have one up for use while working with the other!!!
Right now one is on OTA 3991 with plans to go back to 3588 when the new OTA comes out (if it does!). The other is
TwoTapX .9.0.2 and will stay there until VS lets us know the directions they are going -- and the roebeet will move ahead.
Hope this helps you. Enjoy!
Rev
I have decided to return this one and hope that the newone will not have an issue so I can move on with Clockmod and TNTlite. I will mail it today and hope I will get the new Gtablet from Amazon sometimes this week... Ah... Few more days. Thanks for everyone's input here. I will be getting back on this forum a lot more as I have to learn LOT more......
Is somebody get the same problems because of which it were necessary to return g-tablet?
Or having patience and endurance it is possible to solve any problem?
Getting my new Gtablet today
So finallly I am going to get my new replaced G-Tablet today . Just checked the UPS tracker and it says that it will be delivered this evening. Here are my plans now.... And please correct me if I am planning to do something wrong here.
After unpacking it,
1: Upgrade to the new Viewsonic firmware.... I believe it does it by default once you are connected to the wireless network.
2: Install Clockwork mod
3: Install TnT 2.4
Hopefully this will work this time. Any suggestions.....
use most recent
"3: Install TnT 2.4"
I would suggest using the most recent version of TnT. ie 4.4.0.
For this one you don't have to use use clockworkmod, but it will work ok with
clockworkmod.
If you're still unsure, you may want to try these steps:
www blendblog net/Default.aspx?tabid=36&EntryID=67
(can't post links, but a . where the space is...)
It helps that everything is layed out step by step.
Seems like the link that you provided talks about installing VEGAn. there is another embedded link in the post that talks about TnT4.4 installation as well. Considering the two platforms, which one would you guys prefer? By teh way, got my new Gtablet and ready to roll this evening with this process.
Hint: Look at the sticky force closing thread in this forum. Pay close attention to the original post.
I'm still puzzled why people aren't pointing new people to that thread.
goodintentions said:
Hint: Look at the sticky force closing thread in this forum. Pay close attention to the original post.
I'm still puzzled why people aren't pointing new people to that thread.
Click to expand...
Click to collapse
Well. He sent that tab back and now presumably has one without that issue.
coolrazas said:
Seems like the link that you provided talks about installing VEGAn. there is another embedded link in the post that talks about TnT4.4 installation as well. Considering the two platforms, which one would you guys prefer? By teh way, got my new Gtablet and ready to roll this evening with this process.
Click to expand...
Click to collapse
You are correct. The link does provide steps to install vegan. I meant it as an alternative to tnt.
For me and my tab, vegan with pershoots kernel is much more responsive than tnt alone.
If you google vegan tab you'll find gojim's website. There hasn't been any updates in a few days but it sounds like one will be forthcoming. Im waiting and watching for that one as well as waiting for an update on calkulins rom. It also sounds pretty snappy.
So, firstly, big thanks to the devs here. Gt ADB up and running and started the seemingly easy process f flashing ClockworkMod.
However, I'm not getting to ClockworkMod after resetting. If I try booting into recovery, it stays on the birdie splash screen with "Recvery key detected" and "Booting recovery kernel image" in the upper left.
Not finding any options for alternate recoveries or a fix for this.
I bought it used and the original owner had done some stuff to it so perhaps I was not meant to flash Clockwork from here.
Tap UI version is TnT Lite v5.0.0
Kernel version is 2.6.32.9-00001-g0e0c333-dirty
The standard ClockworkMod does not work properly with TnTLite 5.0. You need the one that was specifically compiled for that ROM.
Go here: http://forum.xda-developers.com/showthread.php?t=998663
and scroll down to the bottom of the first post for a link to the compatible version.
I thought that might be the case although I was told I could flash CLockworkmod once 5.0 was on there.
I'm normally a bit better at figuring all this out but starting in the middle of someone else's work has me at an awkward spot.
I've been searching with little luck. Any chance of pointing me in the right direction?
What about a complete factory reset? Would it be advised at this point?
I editted my previous post with a link to TwoTapsX (Experimental) which is identical to TnTLite 5.0. That should get you going but I'm not sure how much damage might be done at this point. I would try just installing the compatible version of CWM and see if that works. If not, we can look at other recovery options.
Just in case... Are you familiar with nvflash? http://forum.xda-developers.com/showthread.php?t=861950
Just started reading about nvFlash and paused to ask the questions before hacking away blindly at my new toy.
I really appreciate you pointing me in the right direction.
I enjoyed the ROM he put on here but, like the poster under me, my data suddenly got deleted and I like to try various ROMs anyway so I set to work.
I rarely leave my tablet running the same ROM for more than 12 hours ;-)
Be aware that switching away from this particular one can be a bit tricky. I find that doing a cache and data wipe before starting helps to boost the success rate. I also try to down grade to stock 1.1-3588 before loading anything else. If that fails it usually results in nvflashing back to factory stock.
Ack! Okay, in what is sure to be yet another Windows 7 issue, I'm having trouble running the .bat file for nvflash.
Are you sure it is the Bat file. Windoz7 64 need a different driver for NVFLASH.
The drivers I used appeared to work. I will try again.
Damn, I'm sorry. I swear I'm usually better at figuring all this crap out for myself. Once I'm back to stock, I can work from the beginning. This is like being dropped into the middle of a David Lynch flick with zero context.
When I run the batch command, it says that nvflash.exe is not recognized as an internal or external command. Weird.
Did you extract both archives to the same directory?
I sure did. I did take it to mean the gtab folder should remain intact within the nvflash folder instead of mixing the contents altogether in one folder. Right?
Everything else seems to be in order.
Putting any recovery zip on the sdcard produces the same results. Thankfully, everything seems to be working aside from the recovery. Maddening!
I think they need to be intermixed. Would have to check the original thread or look at the .bat and .cfg files to be sure... but if I recall properly they do.
All the files from both zips should be in the same folder, otherwise the batch file can't find nvflash and you get that error.
Good luck!
Wow. If that's what it was they need to put a dunce cap on my avi. Thanks for all the help. I shoulda had the guy put it to stock so I could start from scratch.
I'll try that when I get home.
Thanks again!
Sent from my HTC Vision using XDA Premium App
Sleef,
You are in a world of hurt -- and I say that not making any negative comment
toward the advice you already have been given.
TnT Lite 5.0.0 (which is now TwoTapsx) is a second generation ROM Roebeet did
based on the UAT 3991 update posted by VS in a kind of test mode.
The second generation ROM is not compatible in many respects with the original ROMS
up to 3588 -- some of the internals that normally are changed in an update have been modified.
So, as you have been properly warned by others, you cannot run stock CWM. You
also have to be careful downgrading to stock before moving to stock or another ROM.
To get out of 5.0.0 you need to:
1. Read Roebeet's TwoTapsX thread so you know what you are working with:
http://forum.xda-developers.com/showthread.php?t=998663
2. You need to NVFlash back down to stock. Normally we'd tell you to follow
the thread:
http://forum.xda-developers.com/showthread.php?t=861950
Since you already have been working with this, I'd step-by-step make
sure of your setup and that it is right.
My best suggestion would be for you to set up and follow the NVFlash thread above
exactly and see if you can get a good flash. If you do, it will take you down to what
we call bekit 1105, which is stock version 2638. If you get there and boot successfully,
then when you turn on wifi it will soon update you to OTA 3588. Then
you can carefully pretty much do what you want.
If you don't get a successful flash (because the tab has had so many different,
difficult to handle things on it), then all of us will have to help you find a successful
path.
Good luck,
Rev
P. S. -- What the other guys have been telling you is good -- I've just tried to
put it in perspective so you'd understand where you're at and be organized in
your approach.
Quick clarification... I think Rev meant to say "Is NOW TwoTapsX" rather than not which is why that thread is referenced later. The name change was necessary to differentiate the two development paths.
Thanks for popping in Rev. I've been meaning to pop in but I've been... practicing my recovery methods... don't ask...
Yep.
Fumblefingers strikes again. Thanks.
Rev
I have been reading around for a while now, and noticed a lot of ppl soft-brick there device and are asking devs for help. I have noticed a lot of issues revolve around people trying to hop form on ROM to another.
A very easy way to recover from any sort of brick(or issue) is to use nvFlash. Its is very easy to setup and use and I highly recommend that everyone should setup nvFlash. You can find the guide on how to set it up from http://forum.xda-developers.com/showthread.php?t=861950
I think after the update last night a lot of people will brick there devices trying to mod it, and nvFlash will help you recover. I think we can really help out the dev if we all learn how to use nvFlash, because then they wont have to ans to alot of the support issues that keep coming up, and it will free up some of there time which they can use to create newer roms that will work with the new update.
If for some reason you follow that guide and are not scussefull in setting up nvFlash, then feel free to leave me a pm and i'll help you set it up.
Good post!!
You absolutely right because most of them (especially new users) won't take time to read stuff about the new update, which will in most cases soft brick the tab when coming from a non stock rom.
So yea they all should have Nvflash setup, just in case
Great advice.
I was messing around with Vegan Ginger the other night and wound up borking my gTab. Followed the instructions in that thread and had no problem using NVFlash to get everything back to normal.
Noob here Hi!
I Actually used the NVFlash yesterday to clear up some issues i was having. it works well and was easy to use.
Some how i screwed up my copy of Clockworkmod. When ever i attempted to flash any Custom ROM it would just sit at the view sonic boot screen...Although TNTLite always flashed with no issue.
I used NVFlash to get back to defaults then updated to 3588 then Reflashed CWM. Now I am able to load Vegan
Thanks for the post i think it will be helpfull for us N00Bz
WildBidoof said:
Noob here Hi!
I Actually used the NVFlash yesterday to clear up some issues i was having. it works well and was easy to use.
Some how i screwed up my copy of Clockworkmod. When ever i attempted to flash any Custom ROM it would just sit at the view sonic boot screen...Although TNTLite always flashed with no issue.
I used NVFlash to get back to defaults then updated to 3588 then Reflashed CWM. Now I am able to load Vegan
Thanks for the post i think it will be helpfull for us N00Bz
Click to expand...
Click to collapse
Actually, you probably didn't screw anything up. Some Gtabs have a partitioning issue (I had it) which is only corrected during nvflash. I was unable to install any ginger roms until I nvflashed. Worked like a dream after nvflash.
I'm gonna go out on a limb here & ask a question that's been on my mind for a while, so bear with me. But first, let me give you some background so there's no confusion & no unnecessary questions asked. I'm by no means a "pro" at modifying my Note 3, I just follow instructions carefully & then implement those directions to achieve results. That's how I rooted my Note 3 but could still care less that I tripped Knox in the end.
I have the 32 GB Sprint Galaxy Note 3 with an 8 GB microSD. It's rooted using Chainfire's method. I also have TWRP for a recovery, but I'm using the stock Sprint ROM that came with it. I have a few root apps installed (Titanium backup, AdAway & Root Explorer) but the rest are what Sprint (& Android) put in there, minus a few that are totally unnecessary for me...(chat apps, picture drawings, step counting & so on) that were removed with Titanuim. It's still on 4.3 Jellybean with PUBMJ4 baseband. I also have the Wi-Fi hotspot fixed through 2 file replacements using Root Explorer.
Now that you know what I have, onto the question...
I see many, many ROMs in other threads that I'd like to try out, but don't know how to go about doing this. Before you jump right in & answer, here's my problem. If I try a ROM but don't like it, or it doesn't suit my needs, how can I go about going back to what I have now in the best (& fewest) steps necessary? In other words, to go back to exactly what ROM I have now, the apps installed, baseband, the whole nine yards. Just like a computer backup, it's a bit-for-bit restore, completely mirroring the hard drive. Understand?
Maybe you could explain to me like I'm seven years old what apps I need, what procedures are taken, the order in which they happen & so on. If I need an app or two to do just this, I have approximately $20 Google Play credit left.
Can a DEV or an experienced person that's done just this help a fellow out? Don't get me wrong, the stock ROM I'm using works for me, but there's ROMs posted that look just awesome! It's all about "personalization", am I right?
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
kingdazy said:
Easy, since you have a custom recovery installed (twrp) , you simply do a "nandroid" backup (I personally like to backup to an external SD card, so get a bigger one) before wiping and installing something new. If you like what you got, fine. If you want to go back, wipe and restore! Easy Peasy!
Sorry, being a father means sometimes your time suddenly becomes unavailable. But believe me, it's really easy once you figure out twrp.
I'll let another fine member get more details if you actually need them. ?
Sent from my calculator watch.
Click to expand...
Click to collapse
Doing a Nandroid backup as we speak! I didn't realize TWRP could do that. (duh! ) I only installed TWRP because I just liked the name of it. TWERP!! (gotta nice sound to it, doesn't it??) Thanks a bunch! :good:
tonyevo52 said:
So did you figure it all out?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I did. I found a Youtube link on how to do a TWRP backup on the Sprint Note 3. Easy Peasy as said above! I'll try some ROMs this weekend (can't promise nuthin' cause it's gonna be 70 degrees this weekend & I'm itchin' to ride my mountainbike along the boardwalk at the Virginia Beach.)
But now that the hard part is outta the way, it's all easy street from here!
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
kingdazy said:
Just be sure to Please, oh god Please, read all instructions on any rom you decide to try. Doesn't hurt to read the last 10 pages of each too, get an idea of Current issues that may not be documented in the OP.
And don't get lazy, follow word for word. The only times I f*cked stuff up was when I didn't follow instructions (ie, thought my experience meant I knew best), or just got sloppy.
And, don't forget to wipe! (I wipe 3X, everytime, as a habit. Some people will give you reasons why that's unnecessary, but I can say confidently, if perhaps anecdotally, that I Never have the issues others have with bad flashes, softbricks, FCs, etc.)
Something to get comfortable with, even though you may never need it is ODIN. It's most common use is a utility for flashing stock ROMs and firmwares, great for recovery from bad things. Again, you may never need it, but have it ready in your Pc with a stock ROM file, just in case.
Finally, Titantium Backup can be your best friend, if used properly. It can also be a real pain, so don't become too dependant on it.
FIN
Sent from my calculator watch.
Click to expand...
Click to collapse
No worries! As I said in the OP, I follow directions carefully. I read everything.
Odin is my friend as well. I have it installed on my laptop. That's how I flashed basebands & deodexed stock rooted ROMs on my Galaxy S III. I also have the original stock Sprint ROM for this GN3 "just in case", in a folder sitting on my desktop with a few extra tools. I've never bricked a phone, unless you count using Samsung's online update (can't think of the name at the moment). It said 4.3 was available, so I downloaded it. It flashed, rebooted, but stuck there. Never finished the boot, just gave me an error code. Samsung's own update killed my GS3 & was unrecoverable. Believe me, I tried everything. What was strange, was the ROM was 4.3 but the baseband was the previous version, not the newer one, so the phone just puked. It never updated the baseband so it bricked. Now, I tried (and used) different radios with no problems before the update. Everything worked in harmony. Go figure!
Time for sleep my friend. Gotta work in the morning!
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
vagfyt said:
Hi guys I want to post my experience for future reference. Bought this phone (in Athens, Greece) because it's crazy value for money. After a week or so I was really satisfied with it. Just wanted some more Marshmallow features, like multiwindow. So I did my research and ended up following a related guide : steps-to-root-moto-e-2nd ge n. Everything went well, I unlocked the bootloader, flashed twrp, the phone rebooted and I chose to flash SD card as internal, and I was able to install my apps and settings. Then again following the guide steps I tried to flash SuperSU. This resulted to an endless bootloop, where the message " YOU HAVE UNLOCKED THE PHONE S BOOTLOADER....." kept showing up. So I started reading related post from many forums, most of them reproducing the same solutions, like "find your phone's official firmware and reflash". I downloaded many firmwares, all of them appeared (to me at least) suitable for my phone, but none of them had any result. The bootloop continued. I couldn't even flash ROMS from SD card, obviously because of the internal memory format I had done the first and only time the phone booted. Two days had passed and I was really frustrated, ready to take it to service ( or throw it against the wall). Until now I didn't want anything else but the official firmware. But what the heck, after so much efforts, anger and disappointment there is nothing wrong in trying new things. So when I came across the guide about installing cyanogen 13 on my phone, I decided to give it a try. TOTAL SUCCESS!!!! Now my phone is really "flying", is really fast and the most important: is really working again. Although I went through a second flashing of cyanogen 13 because I had the lame persisting idea to flash SuperSU again, with the same frustrating results. So the bottom line, and the reason for this post is : do not flash SuperSU on this phone because you will soft brick it, and don't get caught up with a "hunt" for the right firmware, you will only loose time and some sanity. This is my advice: Go ahead and install cyanogen, it is really great and has insane features. Big thanks to all the guys developing and contributing, you really saved me big time!!!!
Click to expand...
Click to collapse
There's an issue with SuperSU when it tries to install in systemless mode.
Flashing it this way seems to do the trick, and has been confirmed by multiple users on this board: http://androiding.how/root-moto-g-2014-marshmallow/
If you're using CM13, there is no need to flash SuperSU. CM13 has its own root pre-installed, you can turn it on in Developer Options.