I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?
cnoevl21 said:
I just bought the developer edition for verizon. I unlocked the bootloader successfully, i installed twrp is cmd and it said it installed successfully. I did not, however, open twrp immediately, which may be the problem. because if i go into download mode and click on recovery, nothing happens, my phone just goes black, like it powers off.
I tried opening cmd window again and installing again, only now the cmd window says the device is not connected, even though it is, or says it can't load the file. and ive tried twrp and cwm.
Is it because when i got the phone it was already on 4.4.4?
Click to expand...
Click to collapse
no that does not matter because you are able to unlock your bootloader so android version dose not matter.
when installing your recovery you are running the CMD commands with your phone in bootloader mode correct.
if you are in bootloader mode and still having issues here are a couple things you can try.
1. Restart the phone
2. try a different USB port
3. restart ADB
4. Check drivers
you already know this but once you flash your recovery make sure you boot into the recovery before booting back into android.
if you get it installed Root is simple just download the SuperSU flashable zip and flash it via your custom recovery.
lmk if you are still having issues and we will look into other issues
thanks!
I ended up deleting everything (adb, sdk, fastboot, etc) and redownloading everything. So that got me able to install twrp, but when i tried to boot into recovery it would turn off the phone. Then I realized that in download mode you scroll down to recovery, then hit vol up to select. I am coming from galaxy nexus where the power button is select. So was i figured this out, i got into twrp and installed superuser, so i am rooted now. Time to find a 4.4.4 rom (may have to wait for a stable one since its pretty new) so i can get rid of all this bloatware. I can freeze some of it in titanium, but a lot of it I'm not sure what it does, again, Ive been on samsung for the past 5 years lol. Thanks again for the help.
4.4.4 isn't new. If you want all the Motorola features, stick with a stock-based rom or stock. I prefer stock with Xposed.
Being on vzw, I would recommend Krypton. It's based off the Verizon image and has a lot of bloatware removed. Xposed will get you about all the customizations you might want past that.
i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.
cnoevl21 said:
i was looking in the 'Original' development section an saw mostly 442 roms so i assumed 444 was new and didnt have stable roms yet, but now i know where to look and will probably try the krypton rom. gna have to look into xposed and learn what its about since i never used it before.
Click to expand...
Click to collapse
Right now Android L or 5.0 Roms are New and buggy. Most 4.4.2 and 4.4.4 roms are stable.
Me personally i like Stock with Xposed and gravity box installed, then i use Titanium Backup there is a battery thread somewhere that list what can and can't be removed. just be careful what you remove or you will end up like me with no active display but everything else about my phone is perfect so i dont want to go back to stock and redo everything.
after xposed and TBU i normally find a launcher i like, then maybe a lock screen but i think i ended up with stock. then i find a Text MSG app i like and other little add-ons to make my phone just for me.
here us a list of what i am running on my Stock Sprint 4.4.4\
LockScreen - Stock but tweaked with GravityBox
Launcher - Google Now Launcher
Text App - Google's Messenger App
Gesture Shortcut Menu - Lazy Swipe( i just found this app about a week ago and so far i love it, it allows me to have a very clean homescreen)
everything else changed on my phone is done threw Xposed and gravity Box.
Here are some App's you might want to check out.
AirDroid
Google Calender(if you use a calendar)
Google Keyboard(my keyboard of choice)
GSam Battery Monitor
Lazy Swipe(listed above)
Lucky Patcher(for thous pesky trial apps)
Pushbullet( alternative app for transferring all kinds of files to and from your device)
Zedge(ringtones and wallpapers)
I also attached some screenshots nothing fancy like i said but i love it and its perfect for me
The first one is my lockscreen, second one is my launcher homescreen, Third one is Lazy Swipe just one of the three tabs.
anyways hope this helps get you started post your setup once you get everything set up to your liking
Good Luck
what is that clock/weather widget? Thats pretty sick
http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506
nhizzat said:
http://forum.xda-developers.com/moto-x/themes-apps/droid-turbo-circle-widget-moto-x-t2941506
Click to expand...
Click to collapse
yup that is correct enjoy
error while flashing recovry in cmd ....
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!
commuditi said:
I have already unlock bootloader successfuly... But when i try to flash custome recovery in fastboot mode with cmd it shows error....
I have tried on different laptops but same ....
Already instlall all drivers ...
Pls help me what to do......!!
Click to expand...
Click to collapse
well first thing when u are posting for help you need to include more info. Like for starters what error are you getting so we can figure out what you are doing wrong. post your error and we will go from there.
Thanks
Related
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Seriously?
There aren't enough threads and guides for you to read already? Everything you need is already out there on this forum so why start another thread just because you are too lazy to search and read for yourself?
I have read around and have tried a number of guides a number of times. They haven't worked for me and I'm just wondering what i'm doing wrong. Even though all the information is out there, I don't have the experience to understand it apparently. I've spent hours trying to figure things out but i keep reading conflicting info and half-explained steps and now I'm just confused and would like a clear point in the right direction.
So, do i need to reflash the latest firmware, wait a few hours, then try again on a full charge? Or do i need a euro firmware? Which guide should i follow?
I've downloaded a few applications and driver packages and whatnot but if those could possibly conflict with each other and cause problems i could work with a fresh OS. I'm running OS X but i have linux VMs and friends with clean windows installs (mine is all sorts of messed up)
eatfoodnow said:
I tried to unlock my bootloader, following various guides, and kept getting stuck on the "Download Mode !!!" part. I just want to install the latest stable version of Cyanogenmod on my phone since the stock ROM is being a real pain for me (very slow and unresponsive).
I have:
Android 4.1.2
Build Number: JZ054K
Software Version: AME-XXX
I read online that you need the Euro firmware to unlock the bootloader, can I flash the euro firmware and will it mess with my service? I'm confused as to how the firmware affects things since I've read conflicting information. I didn't flash my firmware a few hours before trying to unlock, so maybe that's the problem?
Click to expand...
Click to collapse
It isn't a question of firmware, the phone needs to have an unlockable bootloader to be able to be, well, unlocked. Here is a list http://forum.xda-developers.com/showthread.php?t=2181581 of P880 bootloader versions. Follow the guide to check which BL your phone has.
Thats obsolete, all versions can be unlocked afaik, either with official method or by fuse editing. No need to keep sim card in,you just need proper drivers
Oh, OK, I didn't know that. But, even better, OP should not have any trouble, provided he follows the BL unlock guide here http://forum.xda-developers.com/showthread.php?t=2224020
Maybe his BL is already unlocked OR is relocked (meaning can't be unlocked anymore).
Its more likely that his drivers are messed up imo.
The fuse editing method should work for everyone, i recommend you give it a try
So the fuse method would be the "BL-unlock.bat" method on that bootloader unlock forum post? I've tried it before, but I'll try it again. The directions only say to run it, is there anything else I need? Now, since it's a .bat file I absolutely have to run it on Windows, right? Because if so I'll use a friend's computer instead of my windows installation.
What are the necessary installations before I run the file? How should I configure settings on my phone? (like what type of usb connection should it be)
There are a lot of things that people expect readers to know but I'm really not very knowledgeable about standard practices for phone stuff so I really need every step. Thanks for helping!
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Flying_Bear said:
Since its.bat file, you can open it in text editor to see which commands it executes. I'd still recommend to do it on windows machine, other OSs may work but aren't tested.
You need abd & fastboot drivers, plus drivers for our device. It's been a while since I've done it, but afaik you can get proper device drivers via lg support tool.
Click to expand...
Click to collapse
Also, correct me if i'm wrong I only had stock for 2hours, but also stock needs usb debugging to be enabled or adb won't work?
Yep, afaik usb debugging needs to be enabled
When you are fast enough, it is possible in charging mode wihle the carger animation is shown. But you have install adb driver very fast...
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
eatfoodnow said:
So I'm pretty sure I got the bootloader unlocked, I ran the .bat file and it went through everything until the part where it checks to see if my bootloader is unlocked, it just froze forever, so I closed it.
How should I go about checking?
Also, what would be my next step now for installing CM10.1.3? I tried to follow the guide on the cyanogenmod wiki (install_CM_for_p880) (I can't post links yet)
...but ran into problems with pushing it into root with adb. It said I didn't have permissions, so I googled some stuff, but just got myself confused.
Thanks for all the help btw!
Click to expand...
Click to collapse
you can check your bl status by entering sw mode (phone off, hold vol+ and insert charger) or reeboting into bl (adb reboot oem-unlock)
to install cm steps are:
-install recovery (you can choose either cwm or twrp, it's more about looks than functions)
-download rom zip onto sd card
-install said zip from said recovery, there's no adb involved
Now my personal opinion, I really don't see the point in flashing 10.1, i would go staright for cm11 if i were you
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
eatfoodnow said:
Ok well I think I got things together more or less, eventually I tried to install CM10.1 with the ROM manager app. I forgot to select the options to wipe my data partitions and now I'm stuck in an endless boot loop every time I turn the phone on. I tried to boot from my backup using CWM which I made with the app prior to trying to install, and it gave me an error about an MD5 checksum failing, no matter what I tried. Should I do the factory reset/wipe option with CWM now? What's my best option.
Also why would you recommend CM11 over CM10.1? I don't want to have to deal with a nightly, all this phone stuff is a supreme headache to me.
Click to expand...
Click to collapse
Factory reset then get nandroid manager app and see if you can restore your stuff with that
CM11 is bugless atm and performance (imo) is way superior
So after a factory reset/data wipe, my phone just booted into CM10.1 and now that's working. And it looks like all of my stuff on the phone is still there (though of course apps aren't installed and whatnot, that wouldn't make sense). Thanks for all the help!
I tried to find a feature list or something to see what exactly is better about CM11, and found out that "stable" doesn't exactly mean stable for CM, and that it looks like a good idea to update, so I think I will try to update to that. Do you know anywhere that has an actual feature list to show me what CM11 does that CM10.1 doesn't?
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
IEcansuckit said:
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
Click to expand...
Click to collapse
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
fury683 said:
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
Click to expand...
Click to collapse
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
IEcansuckit said:
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
Click to expand...
Click to collapse
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
fury683 said:
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
Click to expand...
Click to collapse
Correct. No unlock - no custom recovery.
It also depends on which method you used to achieve wp-off. Is rather not get into the finer details because it's really not important...
Are you using VOL+ to select recovery in the bootloader?
Edit: yes, when you rooted your phone, the stock recovery was overwritten to give you Android with write protection off. Looks like normal Android, but you have write access to system.
Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further
Greetings,
I'm stuck in a very bad place with my Nexus 6 and was hoping someone could help me out of it. I obviously made a grave mistake in doing this so I'm hoping all is not lost. Here are the steps I performed that got me into this mess:
1) Downloaded the latest root .zip file from Chainfire, which notably, does not have a 6.0.
2) Flash Stock ROM to the device Marsh mellow 6.
3) Phone booted up just fine, I then unlocked developer options and then selected allow oem updates.
4) performed a reboot to the bootloader.
5) This is where I went wrong: executed the root-windows.bat script.
Now when the device boots I get an error stating the device is corrupt and cannot be trusted and it immediately shuts off.
UPDATE: I've re-flashed the marshmellow rom on to the device and now on boot I get the same error about the device being corrupt, however, the volume buttons allow me to select "Continue" and it's booting!
Thanks!
Eric
EricSB said:
Greetings,
I'm stuck in a very bad place with my Nexus 6 and was hoping someone could help me out of it. I obviously made a grave mistake in doing this so I'm hoping all is not lost. Here are the steps I performed that got me into this mess:
1) Downloaded the latest root .zip file from Chainfire, which notably, does not have a 6.0.
2) Flash Stock ROM to the device Marsh mellow 6.
3) Phone booted up just fine, I then unlocked developer options and then selected allow oem updates.
4) performed a reboot to the bootloader.
5) This is where I went wrong: executed the root-windows.bat script.
Now when the device boots I get an error stating the device is corrupt and cannot be trusted and it immediately shuts off.
UPDATE: I've re-flashed the marshmellow rom on to the device and now on boot I get the same error about the device being corrupt, however, the volume buttons allow me to select "Continue" and it's booting!
Thanks!
Eric
Click to expand...
Click to collapse
1. use supersu v2.5 or v2.51 for root, not chainfires old .
if you flash marshmallow via factory image, via fastboot. boot up, then back into your bootloader to flash the twrp . flash the recovery, then boot into the recovery and flash a custom kernel for marshmallow, and the supersu file. tgen boot up with root. that message is something that everybody gets. it because of your unlicked , just ignore it.
simms22 said:
1. use supersu v2.5 or v2.51 for root, not chainfires old .
if you flash marshmallow via factory image, via fastboot. boot up, then back into your bootloader to flash the twrp . flash the recovery, then boot into the recovery and flash a custom kernel for marshmallow, and the supersu file. tgen boot up with root. that message is something that everybody gets. it because of your unlicked , just ignore it.
Click to expand...
Click to collapse
Thank you very much! Going to walk through these steps but wanted to tell you thank you before doing so as I imagine it's going to take a bit of time.
I very much appreciate your help!
-Eric
EricSB said:
Thank you very much! Going to walk through these steps but wanted to tell you thank you before doing so as I imagine it's going to take a bit of time.
I very much appreciate your help!
-Eric
Click to expand...
Click to collapse
so far ive used despair and elementalx kernels on marshmellow. if you want root, youre going to have to use a custom kernel.
simms22 said:
so far ive used despair and elementalx kernels on marshmellow. if you want root, youre going to have to use a custom kernel.
Click to expand...
Click to collapse
Bummer - Seem's Google is shying away from root. I imagine it's for security reasons. I've not used a custom kernel before so now is as good a time as any to learn. Which do you prefer despair or elementalx?
Thanks again for all your help!
-Eric
If all else fails use the nexus root toolkit to flash back to stock.
EricSB said:
Bummer - Seem's Google is shying away from root. I imagine it's for security reasons. I've not used a custom kernel before so now is as good a time as any to learn. Which do you prefer despair or elementalx?
Thanks again for all your help!
-Eric
Click to expand...
Click to collapse
they both are fine. elemental uses a different installer that gives you options when flashing via twrp. despair would be simpler. plus, youll need to downliad a kernel control app from thd play store. there are many free and paid versions.
kclive said:
If all else fails use the nexus root toolkit to flash back to stock.
Click to expand...
Click to collapse
That is useful to know, I didn't actually realize there was a toolkit for doing this. I will bookmark it in case I REALLY screw up. Thanks for the help!
I used to be a Windows Phone user, so having all this control and ability to customize down to the kernel level is all very new to me, suffice it to say, I've been missing out and am glad I made the switch and won't ever go back.
-Eric
simms22 said:
they both are fine. elemental uses a different installer that gives you options when flashing via twrp. despair would be simpler. plus, youll need to downliad a kernel control app from thd play store. there are many free and paid versions.
Click to expand...
Click to collapse
You've been a tremendous help and I can't thank you enough. I'm so happy to have my phone back to a working state! I feel like such a n00b, but I guess I've got to start some where. I hate to keep bugging you, but what kernel management app do you prefer to use? I like to make sure I get input from people who know what they are doing and I don't want to choose an app that is going to wind up causing me more issues.
Thanks again!
-Eric
EricSB said:
You've been a tremendous help and I can't thank you enough. I'm so happy to have my phone back to a working state! I feel like such a n00b, but I guess I've got to start some where. I hate to keep bugging you, but what kernel management app do you prefer to use? I like to make sure I get input from people who know what they are doing and I don't want to choose an app that is going to wind up causing me more issues.
Thanks again!
-Eric
Click to expand...
Click to collapse
i use the older elementalx kernel control app. but google pulled it from the store. i bought it, and had a copy, so i use it. trickstermod is a decent free kernek control app
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.
What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?
get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts