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.
Related
Hey, im new here, and completely new to the whole "custom rom flashing" thing.
I would like to get into rooting my phone and then installing a custom rom like resurrection for example, but I have a couple of questions.
1. Do I need an SD card in my phone, to be able to root my phone/install custom roms? or can I just use the phones internal 16gb memory?
2. Would someone be kind enough to point me to a guide to rooting/installing custom roms for complete newbies like myself? I have searched the forums, but theres so many threads about different stuff, like clockworkmod/odin/cyanogenmod etc, my head is completely boggled. I just don't know where to begin with any of it.
Cheers.
1) No.
2) Everything you need to know is in the Stickies.
MistahBungle said:
1) No.
2) Everything you need to know is in the Stickies.
Click to expand...
Click to collapse
1. No you cant root without an SD card? or No you don't need an SD card? elaborate please.
2. Nothing in that thread helps someone like me who is totally new. I don't know what any of it means. Surely there is a simple guide that explains exactly how to root your phone, without linking you to 7 other threads in the process? That's all I've found up until now.
This requires sdcard
http://forum.xda-developers.com/showthread.php?t=1501719
This doesn't
http://forum.xda-developers.com/showthread.php?t=1103399
Thanks, thats what I was looking for.
One more thing, just so I dont make a mistake, could you tell me which kernel to download? my kernel version is 3.0.15-I9100BVLPB-CL310231
cheers.
Read the bit in bold read which says 'Help ! Which file do I use ?'. This short section answers your question exactly.
ok well i tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5-PROPER.zip and my phone no longer boots....
tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5.zip and I get the same thing, so im stuck now. great.
I can get into CWM recovery, but I have no idea how to copy the rom I want to use onto the phone when its in recovery mode. This is something that is just not explained anywhere
help?
Right. In order of importance:-
1) No bumping threads within 37 minutes. Not cool. This is not your personal tech support forum.
2) You're having problems. Why ? Who knows. We're not there looking over your shoulder so we have no idea exactly what you did. I suspect you're having problems because you are in too much of a hurry/took shortcuts & didn't do what was suggested immediately after your OP.
3) However...Given the situation you find yourself in, I recommend you do one of two things:-
A) If you are absolutely sure you have CWM Recovery & not Android recovery (I say this because if your phone isn't booting normally, that normally means the flash didn't work & normally CWM wouldn't be successfully installed either), follow whatever instructions the rom you're wanting to flash has.
Every single rom on here has flashing instructions, normally on the first post on the first page of the thread on here devoted to the rom. If you can't be bothered reading those, I can't help you.
or
B) Go to Samfirmware.com. Search for the firmware that was on your phone before you tried to root it. Download this firmware. Flash the firmware you download following the instructions here. If you also end up with a .dll file, bin it. You don't need it. This will give you a clean install of stock. From there, I strongly suggest you read the CFRoot thread very carefully before you attempt to root your phone again. I also strongly recommend you read the Stickies linked to above, so you have some sort of understanding around what's what with this phone.
If you don't, being a betting man, I'll wager there's a fair chance you'll find yourself in the situation you currently find yourself in again (best case scenario), or worst case you'll end up with a 135gm paperweight as many people have on here over the past few days.
It's all up to you now. Your phone's destiny is in your hands.
Thanks for the reply, much appreciated.
Sorry for bumping, I panicked a little when my phone wouldnt boot. I just expected it to work because I have done things like this in the past and never had problems. Im a pretty tech savvy person really, im just new to android.
I wish it was as simple as reading one thread, but there are dozens of different threads on how to root this phone, and different methods, its extremely confusing.
Im downloading the stock kernel now (300+mb for some reason, and its going to take over an hour to download)
Once I get my phone back to normal, I'll read through some more threads and try and get a better understanding on how to root my phone.
I had it rooted properly as the recovery mode stated CWM in the corner, I think the issue I had was not being able to copy the rom I wanted to use, onto the phone, because I dont have an SD card.
Anyway, thanks for the help, and fingers crossed I can at least get my phone to boot again.
Man, I've never come across anything so complicated in all my life lol.
Edit: Sorted! Flashed back to original kernel and its working as it was before I started. Thanks very much for your help mate, and at least now I know how to restore my phone if I mess it up again in the future.
just thought I would update this thread and say I finally accomplished what I wanted.
Incase anyone is wondering, this is what I did:
Restored my phone back to factory settings/firmware/kernel
Booted the phone up, and copied my rom of choice to the internal memory via USB connection, and enabled debug mode.
restarted in download mode and flashed cf-root kernel (ended up with bootloop)
went ahead and installed the rom via clockwork recovery (creating a backup first)
The phone now boots into the rom im using (Resurrection Remix)
So if anyone is a little worried by getting the bootloop (but can still get into clockwork recovery) try flashing your required rom. Your phone may boot fine with new rom anyway. Mine did.
Hi everyone,
It seems I messed up my Prime and I think I know why it happened. I'll first ask my question and then detail what I think happened at the end. I've been reading around the forums for the past few days and I think I'm experiencing brick number 3 as detailed in this thread: http://forum.xda-developers.com/showthread.php?t=1514088 I followed the link provided under option 3 which links to a thread about an Transformer Prime IRC channel: http://forum.xda-developers.com/showthread.php?t=1367016 I logged in into the IRC channel and someone greeted me by asking for the binaries...frankly, I've no idea what to do in that channel.
I was on the stock Asus Jellybean Rom. I used the Asus Unlock tool and installed TWRP via fastboot as explained in their website (installed the JB.blob). Everything worked fine. I then committed a mistake. I was going to perform a data wipe before installing the new ROM (latest CM nightly) but in retrospect I think that I only performed a factory reset. It was my first time using TWRP and when I got into the wipe menu I selected wipe but I recall that the button for wiping read "slide to perform factory reset". I thought that I was wiping the data on my device but I think that I got confused and only performed a factory reset. I didn't realize that at the time and proceeded to flash the new ROM. When I restarted the device it got stuck in the Asus/Nvida splash screen.
I'm able to go into the recovery menu. I've wiped data properly many times after this and flashed CM many times but the device won't get past that splash screen. I tried flashing the ROM via ADB but whenever I enter the command the terminal shows me a list of the actions that can be performed via ADB and nothing else happens.
I've tried looking around for a solution but I've been unable to find one. Should I install/flash a stock blob rom? The links above say it may do more harm than good and no longer advice users to do that but I haven't found any other alternative. There are many threads pertaining this issue but each case is slightly different and I haven't found one that applies to my situation.
I'm mad at myself because I've had flashed so many custom roms on other devices before and had never had any problems whatsoever that I got careless when flashing the Prime. I know this is completely my fault and I don't want to waste anyone's time on this. I just would like for someone to tell me exactly what to read or where to look so that I can try and fix this situation.
just in case...I just remembered that I didn't root before flashing...could that have been the problem?
I was checking out, once again, the options in TWRP and I did wipe the device correctly. I didn't mess up as I once thought. I can't understand why this happened.
Nearly the same problem for me, case n°3 and don't know what to do. I know have a very expensive black mirror...
FIXED
YES! I was able to fix it BUT I'd be careful before trying what I did. Basically, I did what forum members had advised not to do; I flashed the Asus stock rom via fastboot. As I said before I had read plenty about the various issues with the Transformer Prime. I noticed that some people were flashing the stock rom when confronted with my situation and exhorted others to do the same since they had luck with the procedure. After that, it seems plenty of people bricked their devices by following the same procedure. This caused various senior members in XDA to no longer advise others to try to fix their tablet with that method since it was causing more harm than good (see: http://forum.xda-developers.com/showthread.php?t=1514088)
Sadly, I had no other choice but to try that method. We were advised to go to the #Asus-Transformer IRC channel but, understandingly, there aren't many people participating in that channel (it's very old!. I was able to get assistance from a very helpful (as always) android geek but we couldn't get anything to work since I was having problems with ADB recognizing my device.
So, knowing full well the possible consequences of flashing a stock asus rom I decided to go for it. After all, the worst thing that could happen was to end with a hard bricked device and the soft brick I was experiencing wasn't as different as that (i.e. I couldn't use the device anyway). So I decided to play russian roulette and see what happened. Luckily the rom installed fine and I was able to boot past the, dreadful Asus/nvidia splashscreen! I was super lucky! Even though I'm back to the stock rom I'm happy because I can use my device once again! I really wanted to try out Cyanogen on my tablet but I will have to pass on that...I will never install a custom ROM again on my Prime
So, if anyone is feeling adventurous and has lost all hope then why not play russian roulette and check out what happens when you install the asus stock rom? I downloaded the asus image from here http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+Prime+TF201&os=32 and followed the instructions here http://forum.xda-developers.com/showthread.php?t=1680570 (just step three and four at the end since I already had a custom recovery installed). I had to unzip the download twice (it has a zip inside a zip) and copied the blob file into my fastboot directory (in the PC). I then renamed it to "update.blob" and flashed it.
Don't try it unless you are fully aware of the consequences!
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.
I rooted my sprint Note 3 when I first got it three years ago and flashed it with a custom ROM. I used it for a year and then got a cell phone from work, so I basically stopped using the Note 3 except occasionally. I decided the other day that I wanted to try updating to a newer version of android on the Note 3. It's been a long time since I messed around with rooting, ROMs, and such, and I did not pay close attention to what I was doing and flashed a ROM that was incompatible. When I restarted, I got a Set Warranty Bit Kernel error. I can get the phone into download mode, but I'm unsure of what to do next to get it back to a usable state.
Is there a guide somewhere to walk me through this process?
Thanks!
Solved
Well, I got the phone working again. I basically followed this guide I found. I tried to paste in the link but I'm still too much of a noob. Anyway, it was on android central, and part of the url was how-flash-stock-rom-via-odin-new-interface. Hope that helps someone.
There was one step not covered in that guide - odin kept saying that the md5 value was invalid. I found a youtube video that said to change the extension of the firmware (it was .tar.md5, changed to .tar). After that, it worked and my phone is back.
Is there a guide somewhere to walk me through this process?
Click to expand...
Click to collapse
There's guides everywhere on this site! Just gotta find the right ones lol. Makes it that much better when you finally find em. Next time make a complete backup of your phone first. I like to use TWRP, you can download it directly from the Play Store. I got my Stock Firmware from this archive:
http://samsung-updates.com/device/?id=SM-N900P
Make a backup of that then flash away! It'll be a lot easier/faster to recover with TWRP. What ROM did you flash to yours? Just curious cause every one I've tried had multiple issues to where I wasn't even able to use half my phone smh. Then I root it with CF-Auto:
https://forum.xda-developers.com/showthread.php?t=2466423
Through Odin:
http://odindownload.com/download/#.WYX1A4jyuyJ
Then I make a another separate TWRP backup of my Rooted Stock Phone just in case lol. Lemme know if you run into problems again I'll try to help find it and/or fix it. The more problems I deal with the more I learn! :fingers-crossed:
Might wanna get a USB storage or something too cause ALL these backups take up time and space. (My external SD Card slot hasn't worked for awhile!)... does yours?