Database Users

[Q] [Solved] Factory Rooted

Hello all, I just had a quick questions for those of you who have unlocked / rooted your Nexus 10 and installed the factory image:
1. Did you all use the toolkit in the Android Dev Forum for Nexus 10 to achieve the root?
2. Once you flashed a custom recovery was installing the factory image as simple as downloading the zip from google (https://developers.google.com/android/nexus/images#mantaray) and then flashing it via recovery and rebooting AFTER you unlock the bootloader etc?
I was under the impression that once you Unlock / Root, you have no OS on your device, is this correct? Or can I root and Android 4.2.1 will still be there, albeit completely wiped of my user data from before.
Thanks for the help, don't wanna get started on this until I know what I'm doing! Don't want a $400 makeshift frisbee disk

You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.

Fromako said:
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Click to expand...
Click to collapse
Thanks! I think I will go through with using the toolkit tonight and see if I can get it to boot into the factory image. Glad that it sticks around (hopefully) if not I can just flash 4.2 from google via TWRP...thats what I needed to know

So really all I need to root is this:
1. fastboot oem unlock
2. fastboot flash recovery [recovery.img]
3. Boot into recovery
4. Flash SuperSU.zip? --- Where can I download SuperSU.zip ?
5. Wipe Cache / Factory Reset via TWRP wipe data
6. Reboot
7. Profit?
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff

TheEmpyre said:
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
Click to expand...
Click to collapse
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.

Fromako said:
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Click to expand...
Click to collapse
I just finished successfully rooting...got hung up after I unlocked the bootloader and flashing TWRP but all I had to do was Format the Data and wipe cache after to successfully boot into the OS. After that I was able to load SuperSU to my SDcard and then flashed it, reboot, did root-checker and I'm all good! Thought I was screwed there for a sec cuz I didn't pre-load SuperSU or the factory image in-case it hit the fan and I wasn't able to mount my SDcard storage via TWRP...Figured it all out though thanks for the help! Glad I was able to do it without the tool-kit!

Lg G2 LS980: Having Problems After Trying To Flash CyanogenMod 12.1

Sprint LS980 in an odd state after trying to flash CyanogenMod 12.1
Ok... so I got two of these Sprint LG G2's. I was able to successfully flash the first one with a minimum amount of problems considering I was just learning how to do it.
This second one is a problem though. Here's what I did:
I tried to root but it could not due to the version of the Sprint firmware on the phone. I did the TOT stock flash to get it back to stock. That worked fine.
Then I was able to root it via ioroot. Once rooted, I installed FreeGee and tried to install TWRP, that didn't seem to work, so I installed CWM Recovery. I did option two on this thread to try to get the loki stuff installed using openrecovery-twrp-2.6.3.4-ls980. That "installed" and I was able to boot into it. I installed cm-12.1-20151125-NIGHTLY-ls980 (same one I used on the other phone). That would not install via CWM and gave an error about not being able to lokify (or something like that).
So I said, OK, I must have done something wrong, so I tried to redo stock flash again. That acts like everything works fine LGFlash does it's thing (using LS980ZVA_01.TOT), but the phone boots up and does not seem to finish the install process. The LG logo comes up and not the Sprint screen that I would expect. I can do this over and over again and the results are the same whether I let it sit for an hour or 10 minutes after flashing. So now, the phone boots, but I can't do anything with the touch screen, and will then go into a reboot loop (getting into the OS but rebooting shortly after). I CAN get into CWM where I can wipe data/factory reset and wipe cache partition. After I do that, the phone will boot and will let me interact with it, but after a short time (a few minutes I think), it will reboot again and be in the same state it was before I went into CWM. I tried to do a factory reset in settings. It would say that two reboots would occur, but then nothing happens.
I'm at a bit of a loss as to where to go from here. I don't think that it's an unrecoverable brick, but heck if I know how to fix it.
In between reboots, ADB does see the device in ADB Devices, but shows that it's offline, so I can push an APK to it.
Here are the options that I get in recovery mode:
Reboot System Now
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Any assistance is greatly appreciated!

Ok.. well.. I downloaded and flashed ZVE and it seems to have greatly stabilized the phone. However, it seems that I have lost the ability to do download mode and recovery mode. I can still get into the device through ADB, but ioroot no longer is able to root the device, so I can't install any recovery. There is a system update available to install, but didn't want to do that unless I'm good an stuck in this mode.
I also don't seem to be able to enable the cellular service. I don't know if the update it wants to install would fix that or not.
Edit: I can still do ADB reboot recovery and get into recovery mode with these options:
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Edit2: I was able to root with Stump. FreeGee won't run on ZVE, so not sure what to do from here. The phone does not work at all. None of the phone info is listed in About Phone. No IMEI or anything.
Edit3: I have been able to get TWRP installed and can boot into it. I have also verified that I can get into download mode now. I'm very concerned about my EFS info though. I did back it up, but not to the PC, so effectively I have no EFS backup and no way to recover the IMEI information. Not cool...

Stuck on Sony logo after TWRP has been run.

Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.

Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.

kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.

Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.

kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.

Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?

Rom and recovery not booting

Hi everyone,
I hope that you all had/are having a lovely christmas. Unfortunately for my S4 christmas has been terrible. The phone has had low storage for a week now and was crashing as a result and I didn't have time to fix it. Yesterday the phone was running horribly and wasn't doing anything that I touched. So I rebooted which took way too long and when I did it again the phone now does not pass the galaxy s4 screen and also TWRP recovery will not pass its boot screen either.
I have attempted flashing stock recovery which said error mounting all partitions, afterwards a reboot allowed me to wipe cache thinking it would allow the phone to boot, but no change.
I am thinking to flash stock samsung rom through download mode since it is still functional so I can recover my data before moving to my new phone. Will this be a good idea considering that the Lineage OS rom is significantly smaller than the stock samsung rom or will it not worsen the situation?
Thanks for your help!

Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?

audit13 said:
Flashing a stock ROM may not allow you to recover the data.
Did you try re-flashing the same version of TWRP or a different version to see if that helps to mount the data partition?
Click to expand...
Click to collapse
Thank you for your response! I have tried flashing flashing both the same TWRP and different version which was in fact smaller. This saw no improvement in the condition and I still can not pass the TWRP boot screen.
What else do you suggest I try?
Thanks for your time!

Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.

audit13 said:
Tried re-flashing the same ROM that was on the phone before the issue started?
Flashing a stock ROM may allow the phone to boot to its desktop without a factory reset. You may want to use this method as a last resort to get the phone into working condition.
It's also possible that the internal memory has failed which means there is no economical way to recover the data.
Click to expand...
Click to collapse
I am actually unable to flash anything without odin because I can't boot into my recovery which hangs on its twrp screen. Also if I have set my partitions to f2fs will this interfere with flashing the stock rom?

I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.

audit13 said:
I am not sure if the file system will interfere with Odin flashing the ROM. Sounds like you may have to try flashing with Odin which will probably result in data loss.
Click to expand...
Click to collapse
Do you think it could possibly be a bootloader or kernel issue? Perhaps I could try flashing those first before a full factory firmware?

I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.

audit13 said:
I don't think it is a bootloader issue as the phone will boot. The bootloader is similar to a computer bios. The computer bios checks to make sure the basic hardware is present and functioning. If the basics are met, the bios hands control of the device to the OS. In this case, the bootloader is handing control of the device to the OS but the OS can't boot.
I doubt that it is a kernel problem because the phone worked before so the kernel is compatible with the phone.
Click to expand...
Click to collapse
So I took the plunge and installed the stock firmware now the phone boots and I'm greeted with a message asking to factory reset because encryption failed. I reinstalled TWRP and for some reason that still can't fully boot. I want to get it working so I can access the storage to remove the important files through either mtp or adb. There is some form of adb working whilst TWRP is booting but it can't access or see anything in the partitions or mount them even running as root.
Any ideas to get TWRP or any other recovery working on the phone? (The stock recovery booted just fine before I flashed TWRP)
Any help is much appreciated!
Kind Regards,
Crapping_Bricks

I think the stock Rom doesn't recognise the file system and thinks the encryption failed.
I'm not sure what else to suggest other than a factory reset since twrp doesn't allow pulling the data via adb or mounting the data partition.

How to root on stock 7.1.1 using Magisk

So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?

auxillium said:
So I installed TWRP recovery using tuliptool and all that, but didn't bother with bootloader unlocking since it said it's not needed. So I tried to install Magisk using the instructions on their thread but after booting it asks me to reset my phone because the data got corrupted.
Luckily I had backed everything up beforehand, so I restored boot image and everything works fine again. Just wanted to know what I did wrong here. Did I miss any steps?
Click to expand...
Click to collapse
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.

marvelljones said:
You probably didn't miss anything if it's the "Your device is corrupt. It can’t be trusted and may not work properly” error, I get the same thing. You messed with the files in the boot partition so ZTE's "safety" features in the stock ROM automatically call them corrupted. I simply hit the power button and continue to boot, my device works fine (actually much better than before being rooted with Magisk). I'm the one who "corrupted" the phone on purpose, so I'm comfortable it's fine. If you're getting another message, I'm not entirely sure why. Maybe try ADB sideloading Magisk in TWRP, it's what "worked" for me.
Click to expand...
Click to collapse
What do you mean by "hitting the power button and continue to boot"? When I hit the power button on the "Decryption unsuccessful" screen it just locks and unlocks like normal, but stays there.

Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.

auxillium said:
Ok I managed to install Magisk after factory reset, but after that my sdcard is not being recognized anymore (but is recognizable in TWRP). So I decided to restore the backup i had, and rebooted. But now I'm stuck on the ZTE logo during boot. I can still open TWRP, though. I've tried wiping system, data, and cache, then restoring the backup, also no good. For now I'm downloading the stock firmware and will try that. Any ideas on how I can fix this before I flash the stock firmware?
EDIT: Ok I managed to fix it by installing the no verity boot image instead. Boots again. I'll probably refrain from trying to root for now. Thanks for the help.
Click to expand...
Click to collapse
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.

marvelljones said:
Well, I wasn't much help, but it sounds like your overall problem was different than mine. My only advice is if you attempt to root with Magisk again, is to connect to your PC/Mac/etc with a cable, use the Advanced menu in TWRP, choose ADB sideload, and sideload Magisk from your PC/Mac/etc. You can find a more advanced explanations on various websites how to use ADB if you don't already know how. For some reason that worked for me and gave me full Magisk and phone functionality when nothing else did.
Click to expand...
Click to collapse
Will this allow me to install magisk without a factory reset?

auxillium said:
Will this allow me to install magisk without a factory reset?
Click to expand...
Click to collapse
I didn't have to, but I can't guarantee it will work for you. I had previously factory reset my phone but at the time I sideloaded Magisk I had been using the phone for at least a week. Just make a backup of everything first to be safe. *edit* I am using the beta version of Magisk (16.4), not sure if that's making a difference.