Related
Just got my Nexus 5 and I decided to root it. I used the Nexus 5 Multi-Tool to first install the drivers and then continued to unlock the bootloader and root it.
The bootloader unlocked just fine and I got the choice to install CWM or TWRP. I chose CWM first. CWM then gave me a messae that it couldn't mount my sdcard, but it did ask me to fix root permissions. I selected yes and rebooted. My phone then went into bootloop. I tried to restore to avail. Installing TWRP gave me the same message as in CWM (can't flash any ROMs in both recoveries either).
What's weird is, that when I connect my phone to my PC Windows detects it as a MTP USB Device. It isn't supposed to do that if I enabled USB Debugging, right? (I did enable USB Debugging before anything).
How do I proceed? Help is appreciated.
wouwousoft said:
Just got my Nexus 5 and I decided to root it. I used the Nexus 5 Multi-Tool to first install the drivers and then continued to unlock the bootloader and root it.
The bootloader unlocked just fine and I got the choice to install CWM or TWRP. I chose CWM first. CWM then gave me a messae that it couldn't mount my sdcard, but it did ask me to fix root permissions. I selected yes and rebooted. My phone then went into bootloop. I tried to restore to avail. Installing TWRP gave me the same message as in CWM (can't flash any ROMs in both recoveries either).
What's weird is, that when I connect my phone to my PC Windows detects it as a MTP USB Device. It isn't supposed to do that if I enabled USB Debugging, right? (I did enable USB Debugging before anything).
How do I proceed? Help is appreciated.
Click to expand...
Click to collapse
Don`t you guys ever NOT get in trouble when using toolkits. Toolkits are only suitable for users that know what they are doing and can fix the issue they have and not for lesser experienced users that will be stuck when something goes wrong. Learn how to install and use adb and how to flash .img files. Post your question in the toolkit thread bro, maybe someone can help you there. Good luck
Read this http://forum.xda-developers.com/showthread.php?t=2508292 and this http://forum.xda-developers.com/showthread.php?t=2507905 and this http://forum.xda-developers.com/showthread.php?t=2513701 and you`ll never be in trouble again.
Thanks for your reply.
I have done this many times before on my Galaxy Nexus. That's why I used that tool this time aswell.
However, I got it back to stock with the tool, which reverted to stock android and recovery. I then installed TWRP recovery manually and through there I rooted.
I have no idea what went wrong the first time, but in the future I'll just manually install recovery/root devices since it seems to be much safer.
The same thing happened to me today. I managed to get out of it by flashing TWRP (using the tool) and then in TWRP doing a complete wipe and rebooting. Not sure why the CWM wipe did not do the trick, but that worked for me.
[SOLVED]
So after having my Transformer for some time now (unlocked, rooted, and running CROMI) it began to get sluggish. I wanted to upgrade to something else, and decided to try PA HALO http://forum.xda-developers.com/showthread.php?t=2376927
I missed something somewhere, prob the fact that I installed TWRP over my CWM that I had from long ago, instead of upgrading to the new CWM, or the fact that I'm still on the 10.4.4.25 bootloader. I rebooted into recovery, flashed the PA zip, rebooted into recovery, flashed the new GAPPS, and wiped the cache and Delvik. When I went to boot it up the "ParanoidAndroid3+" text and neon jellybean/fish thing show up, then nothing.
I (stupidly) did not make a new backup before doing this change (though there is one from my CWM, but TWRP doesn't seem to recognize it).
ADB does not seem to be working. When I select the USB icon, while using the power+volDown, I get the message "starting fastboot usb download protocol" and ADB does not see the device. If I let the device try and boot (when it gets stuck at the neon jb/fish) ADB sees the device, but gives the error <waiting for device> when I try and flash the new CWM. I seem to be able to access the terminal from TWRP, so I know there is a way to load the old CWM restore files, I just don't know how.
Help is needed.
found a way to do it, but I guess it took away my root when I flashed the new rom. Now I get "su is not recognized" from the terminal..... I'm downloading http://forum.xda-developers.com/showthread.php?t=2107271 and will try to get the os to boot. I can always re root the device, but I kinda need the device to boot into something first.
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
berndblb said:
You missed quite a lot to get yourself into that pickle.
The second line of the PA thread reads:
GET THE LATEST BOOTLOADER AND RECOVERY
The link leads you to the CM 11 thread where it says in no uncertain terms that you need to be on the 10.6.1.14.4 or later bootloader. You think a 10.4.4.25 bootloader will run a JB 4.3 rom?
I hope you get it working.... Good luck
Click to expand...
Click to collapse
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
datboyc said:
Thanks for the kind kick to the nuts guy. I flashed the new bootloader (10.6.1.14.4) http://forum.xda-developers.com/showthread.php?t=2223918 that was already on the root of my tablet, downloaded GAPPS (4.2.2-4.3) http://forum.xda-developers.com/showthread.php?t=2405292 and placed it on MicroSD card, and already had the PA rom http://forum.xda-developers.com/showthread.php?t=2039557
Did some searching and came across a thread (can't find it now) that said to wipe before and after installing GAPPS.
It works now. The process went as follows:
1. Flash bootloader and reboot into recovery
2. Wipe cache/Delvik, flash GAPPS, wipe again
3. Flash rom
4. Reboot and wait for the rom to settle
Something is still wrong, or I'm not understanding the layout of PA, because I'm missing some options and buttons for some apps I've downloaded. I've made a back up with TWRP (for just in case), and am going to try getting CM 10.2 on there.
Click to expand...
Click to collapse
The "kick" was really meant as a friendly slap upside your head which was probably unnecessary since I hope you did that yourself already extensively - so I apologize
Glad you got it working :thumbup:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
No, but could you try the previous version of SuperSU? Just to rule out the new version that I haven't tested please?
I updated to 5.0.1 earlier
Flashed all the img files exact userdata and then booted in to Android.
I then flashed TWRP 2.8.1.0 and used that to flash SuperSU 2.37
All that worked fine.. I then did a play update and SuperSU updated to 2.40
All working fine as far as I can tell. Apps needing root are working!
iowabeakster said:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
Click to expand...
Click to collapse
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
BirchBarlow said:
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
Click to expand...
Click to collapse
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
iowabeakster said:
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
Click to expand...
Click to collapse
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
BirchBarlow said:
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
Click to expand...
Click to collapse
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
iowabeakster said:
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
Click to expand...
Click to collapse
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
snappycg1996 said:
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Click to expand...
Click to collapse
I just backed the /sdcard, to my PC. I just re-ran titanium.
I can deal with "/sdcard issues" from updating to lollipop easy enough. That's a 30 second fix. I can deal with setting up my email accounts to my email client app. I can deal with launcher settings, and all the other apps, widgets, etc. Those are things that I can slowly get back to where I want. They aren't critical. But yeah, very tedious.
I think "starting over" may be much more tedious for me than most people though. I run ssh servers and clients on all PCs, servers, and phones (disabling passwords and using rsa encryption keys for security). It's very nice, once I get it all set up in that I can access everything (from anything) very easily. I do need root for that though also.
But if I can't just hit a "restore" to get it all my ssh addresses, keys, fingerprits, etc back to where it was and then I have to: reverify new fingerprints, generate new keys, re-enable passwords to transmit new keys for everything, then disable passwords (for all machines) ... well... I just get very very grumpy.
anactoraaron said:
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
Click to expand...
Click to collapse
I'll check that out. Thanks.
I started to install pacrom on my verizon galaxy s4 and am havings troubles. I'll start from the beginning.
I rooted the phone via Towelroot app and checked it with rootchecker.
Then i downloaded the following.
downloadandroidrom.com/file/GalaxyS4/SCH-i545/roms/PACMan/pac_jfltevzw-nightly-20130913.zip
downloadandroidrom.com/file/gapps/PA/pa_gapps-full-4.2-20130610-signed.zip
androidfilehost.com/?fid=95784891001603023 this is safestrap for "FOR USERS OF MJ7/MK2" IDK the difference between that and ME7/MI1 but i used MJ7/MK2
From here I opened up the safestrap app and installed the recovery and loaded it up. I left it on the stock rom slot while i continued to wipe everything and install the rom and GAPPS. This was a mistake, however, because i it bootlooped. I tried wiping and installing many different ways and still ended up with a bootloop. I realized in needed to use a rom slot and set that up. I wiped all the necessary things and installed the rom and GAPPS. Still it bootlooped. I have even tried to install without GAPPS with no avail. I forgot to make a backup of the stock and the stock slot just bootloops the pacrom boot screen. I cant find a way to add filed from my computer because whenever i connect it during the boot screen it shows up as a disc drive on my computer. Normally i would choose USB settings and make it where i can transefer data files, but i cant do this. I really need some help with this as I have done all I know to do. The downloads may be the problem, but from what i understand they are the correct ones. Thanks
Download this rom, move it to your phone and flash with recovery.
If you can't get the file on the phone I will help you out.
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
[email protected] said:
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
Click to expand...
Click to collapse
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
I formatted, installed factory image, installed TWRP, flashed Magisk, confirmed root, flashed NetHunter ZIP, same result
Droidriven said:
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So if anyone else is facing the same issuing of wanting to install this old(ish) software onto this old(ish) hardware, and got stuck in the same place as me, here are the three steps that I had to take to succeed that were not in official documentation:
1)When flashing the factory Android image, make sure that you are using the newest version that is supported by NetHunter. At time of writing, this is not the same as the newest version of Android.
2)Remove the -w option from the installation script
3)Be sure to install a compatible kernel from builds.nethunter.com
Thanks again to @Droidriven for the tip on using Magisk