Related
My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
If you're using Galaxy Nexus Toolkit v5.4 from mskip, you don't need to extract anything, just copy .tgz file into the appropriate folder and the toolkit will do the rest for you.
Try reflashing the stock image from google again (make sure you choose the one for CDMA version).
After that, use toolkit to flash CWM, and the touch version is fun.
highmoon said:
My nexus is LTE version, and had stock 4.0.2. I unlocked the boot loader, and rooted successfully, using "Galaxy Nexus Root Toolkit v1.3". I can see that the boot loader is unlocked in FASTBOOT screen.
My computer recognizes both ADB mode and FASTBOOT mode.
Then I did "Temporary Flashing" of ClockworkMod 5.5.0.4 to "Boot" partition, and installed 4.0.4 successfully. And applied the new "su.zip" as well.
After doing this, I could see that the phone boots okay, and everything was perfect, including the root permission.
The problem starts from here.
Since it was temporary flashing of CWM, I wanted CWM to be permanent. So I first erased "/system/recovery-from-boot.p". And then used the toolkit again, but this time I selected "Permanent Flashing" of Clockwork Mod 5.5.0.4 to "Boot" partition.
Now, when I turn on the phone, it boots into CWM recovery(!). Furthermore, if I select "reboot system now", it reboots, but it boots into CWM recovery again(!). I can't get into Android anymore.
I don't know if it is a good thing or not, but when I'm in CWM recovery mode (when booted), my computer recognizes the phone as "ADB mode - recovery".
Oh, and when turning on the phone with VOLUP+VOLDOWN+POWER, it still shows FASTBOOT screen (and yes, the computer still recognizes it as FASTBOOT mode), but when I select "recovery", there's an Android with a red warning sign on it, and system halts. I should do a battery pull.
What should I do??? Help
PS1. I downloaded "mysid-icl53f-factory-blahblah.tgz" from google's depository and extracted "recovery.img". And used the toolkit to "Temp Flashing" to "Boot" partition, but it ends up in the android with the red warning.
Click to expand...
Click to collapse
If you're using Windows. You can be saved at this point. The good thing is that your device is being recognized by ADB in recovery.
The toolkit installed the SDK onto your computer
Here is what you do to go save yourself
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
go to C:\Android-sdk-windows\platform-tools and put the ROM and Gapps in there
Now, with your phone plugged into computer and in recovery, open up a command prompt
In recovery, navigate to "Mounts and Storage" and be sure to select MOUNT DATA
type
cd c:\android-sdk-windows\platform-tools
adb push EXACTNAMEOFROM.ZIP /data/media
(depending on the file size, it will take about a minute or two)
adb push EXACTNAMEOFGAPPS.ZIP /data/media
adb reboot recovery
------
Okay, now that you have rebooted recovery , go to "install zip from sd card" and MAKE SURE you see the ROM and Gapps package, but DON'T flash them yet.
Go back,
Wipe data
Wipe Cache
Go to advanced and select Wipe Dalvik Cache (ignore the SD-EXT error that's normal)
Go to Mounts and Storage - and select Format System
Go back
Go to install zip from sd card, flash ROM, then slect install zip from sd card again and flash Gapps
REBOOT
Enjoy
Again...
Samsuck said:
Download a Galaxy Nexus LTE ROM as well as the Gapps package for it. (AOKP as an example)
Click to expand...
Click to collapse
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Up to you, you can also just flash stock images and start over.
My method should work too, and leave you with root
Your choice
highmoon said:
I'm wondering, as heo_con184 said above, if I can flash the stock ROM? (instead of other ROMs)
Must it be other ROM to make it work?
Thanks in advance.
Click to expand...
Click to collapse
You could do it either way.
Okay, I found a solution without wiping everything.
(Flashing a stock ROM image, or other ROMs would wipe your everything...)
But thanks people!
For those of you, who would encounter something like this (including me again), I'm leaving a note.
0) This problem happens because your Boot partition, overwritten by ClockworkMod recovery image, is no longer compatible with the rest 4.0.4 image. So you need not only "recovery.img", but also "boot.img". Unfortunately, boot.img is not there in the 4.0.4 ROM. But luckily, someone else extracted it.
1) Get the 4.0.4 stock image from here
(android.clients.google.com/packages/ota/verizon_prime/659e0a8f24b4.signed-mysid-IMM30B-from-ICL53F.659e0a8f.zip)
2) Extract "recovery.img" from the file above.
3) Get "boot.img" in here (aospdev.com/rhcp/dev/404boot_root.img)
4) Get into FASTBOOT mode
5) fastboot flash boot boot.img (if not renamed, "404boot_root.img" above)
6) fastboot flash recovery recovery.img
6) Enjoy
I am relatively new to the android rooting scene and have installed a file from zip using clockwork recovery to remove the 3 dot menu from applications but afterward my phone now doesn't boot, its just stuck at the HTC ONE screen i have tried factory reset from clockwork and it didn't work. i am wiling to do anything even if everything is erased and if it could be mac friendly even better but anything is fine
benny_w95 said:
I am relatively new to the android rooting scene and have installed a file from zip using clockwork recovery to remove the 3 dot menu from applications but afterward my phone now doesn't boot, its just stuck at the HTC ONE screen i have tried factory reset from clockwork and it didn't work. i am wiling to do anything even if everything is erased and if it could be mac friendly even better but anything is fine
Click to expand...
Click to collapse
I guess you are on a stock rooted rom?
Seems the version provided in the thread was incompatible with the stock rom version your are currently on:
A few solutions:
1. Search a custom rom in the development threads and flash it, choose an ICS rom though if its a sense rom..flashing a jellybean rom is a bit more advanced and isnt suggested for beginners.
2. If you know which stock rom your are using (1.28, 1.29 or 2.17) you can search for a corresponding rom and push/flash just the android.policy.jar from it back to yoru device - thats the file taht got overwritten when you flashed the 3dot removal zip.
3. If you got a nandroid backup, just revert to your backup in recovery.
...there are a few other solutions, which requires relocking your bootloader etc.
IF your are already rooted I would suggest to flash a custom rom, this is the easiest way to get your oen x back to live and running a custom rom can bring a lot of advantages: better battery life, smoother UI and a lot of stuff that enhances the user experience on the One X.
Cheers, Jan
Restore a nandroid from before you flashed the mod. Or find your relevant ruu, relock your bootloader and run the ruu from your pc
sent from my One X using xda venom premium
j4n87 said:
I guess you are on a stock rooted rom?
Seems the version provided in the thread was incompatible with the stock rom version your are currently on:
A few solutions:
1. Search a custom rom in the development threads and flash it, choose an ICS rom though if its a sense rom..flashing a jellybean rom is a bit more advanced and isnt suggested for beginners.
2. If you know which stock rom your are using (1.28, 1.29 or 2.17) you can search for a corresponding rom and push/flash just the android.policy.jar from it back to yoru device - thats the file taht got overwritten when you flashed the 3dot removal zip.
3. If you got a nandroid backup, just revert to your backup in recovery.
...there are a few other solutions, which requires relocking your bootloader etc.
IF your are already rooted I would suggest to flash a custom rom, this is the easiest way to get your oen x back to live and running a custom rom can bring a lot of advantages: better battery life, smoother UI and a lot of stuff that enhances the user experience on the One X.
Cheers, Jan
Click to expand...
Click to collapse
thanks so much for the great response what would be the best custom rom to install for just a better htc sense UI rom and what would be the best way to do it
EDIT!!!EDIT!!!EDIT!!!EDIT!!!EDIT!!!EDIT!!!EDIT!!!
So i know that i have 1.29 so how would i go about flashing the android.policy.jar could i just download the 3dotremover fix
Flashing a new rom
So how would i go about flashing a CM9 ICS rom to my htc considering that i can't access the sd card as it wont boot
benny_w95 said:
So how would i go about flashing a CM9 ICS rom to my htc considering that i can't access the sd card as it wont boot
Click to expand...
Click to collapse
Accessing sd card even if device does not boot is still possible, using adb in recovery mode.
If You have cwm recovery flashed, just boot into recovery, if you dont flash revocery and boot into it.
If You are unable to flash recovery do direct boot into recovery as follows:
You need fastboot binaries and recovery image
1. reboot device into fastboot
2. open command window ( cmd, bash, whatever )
3. use this command "fastboot.exe boot recovery.img" where recovery.img is filename for recovery image
4. You device should be now in recovery mode.
Now, for the magic
You need adb binaries.
1. open command window
2. type "adb devices" this should show device id confirming adb's ability to communicate with device
3. using recovery on the phone mount sdcard
assuming You use clockworkmod recovery:
3.1. select "mounts and storage"
3.2. select "mount /sdcard", if successfull, this entry will change into "umount /scard", dont select it again, leave Your phone on the desk and proceed
4. to copy files to device sdcard, use command window You opened previously,
5. type "adb push FILE_NAME.ZIP /sdcard/FILE_NAME.ZIP" where filename is rom zip or any other file You want to copy.
6. depending on file size, this may take some time, and it will seem line nothing is happening, just let it run for couple of minutes.
7. go back to You device.
8. select "umount /sdcard"
9. select "+++Go Back+++"
10. flash you rom from copied file if You need.
staviq said:
Accessing sd card even if device does not boot is still possible, using adb in recovery mode.
If You have cwm recovery flashed, just boot into recovery, if you dont flash revocery and boot into it.
If You are unable to flash recovery do direct boot into recovery as follows:
You need fastboot binaries and recovery image
1. reboot device into fastboot
2. open command window ( cmd, bash, whatever )
3. use this command "fastboot.exe boot recovery.img" where recovery.img is filename for recovery image
4. You device should be now in recovery mode.
Now, for the magic
You need adb binaries.
1. open command window
2. type "adb devices" this should show device id confirming adb's ability to communicate with device
3. using recovery on the phone mount sdcard
assuming You use clockworkmod recovery:
3.1. select "mounts and storage"
3.2. select "mount /sdcard", if successfull, this entry will change into "umount /scard", dont select it again, leave Your phone on the desk and proceed
4. to copy files to device sdcard, use command window You opened previously,
5. type "adb push FILE_NAME.ZIP /sdcard/FILE_NAME.ZIP" where filename is rom zip or any other file You want to copy.
6. depending on file size, this may take some time, and it will seem line nothing is happening, just let it run for couple of minutes.
7. go back to You device.
8. select "umount /sdcard"
9. select "+++Go Back+++"
10. flash you rom from copied file if You need.
Click to expand...
Click to collapse
Thanks so much i have spent hours on end searching the web for a fix originally it said that i couldn't mount the sd card but i tried anyway and it worked but thanks a lot
help
staviq said:
Accessing sd card even if device does not boot is still possible, using adb in recovery mode.
If You have cwm recovery flashed, just boot into recovery, if you dont flash revocery and boot into it.
If You are unable to flash recovery do direct boot into recovery as follows:
You need fastboot binaries and recovery image
1. reboot device into fastboot
2. open command window ( cmd, bash, whatever )
3. use this command "fastboot.exe boot recovery.img" where recovery.img is filename for recovery image
4. You device should be now in recovery mode.
Now, for the magic
You need adb binaries.
1. open command window
2. type "adb devices" this should show device id confirming adb's ability to communicate with device
3. using recovery on the phone mount sdcard
assuming You use clockworkmod recovery:
3.1. select "mounts and storage"
3.2. select "mount /sdcard", if successfull, this entry will change into "umount /scard", dont select it again, leave Your phone on the desk and proceed
4. to copy files to device sdcard, use command window You opened previously,
5. type "adb push FILE_NAME.ZIP /sdcard/FILE_NAME.ZIP" where filename is rom zip or any other file You want to copy.
6. depending on file size, this may take some time, and it will seem line nothing is happening, just let it run for couple of minutes.
7. go back to You device.
8. select "umount /sdcard"
9. select "+++Go Back+++"
10. flash you rom from copied file if You need.
Click to expand...
Click to collapse
Hi there, I am trying to follow these instructions but when i type adb devices I dont get a device listed at all, please help as I flashed the boot.img right before I was about to install a new rom but the rom had errors and so the installation was aborted and now im stuck in an eternal boot loop.
please help!
ADB commands only work in recovery or when you're booted in Android (not possible in your case). What you need to do is put your phone in fastboot mode and get into recovery from there (plenty of info on how to do that available on these forums).
Once you're in recovery mode ADB devices list should show your device and then follow the rest of those instructions.
If you can't get into fastboot from your bootloop force phone off by holding power button for 5 second, then once off hold volume down only and phone should boot in fastboot
Paranoid Android Pro Nexus 7 on Tapatalk HD
Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.
If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.
thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:
Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
GhostlessShell said:
Attempted to root phone use ADB and fastboot.
during process noticed difficulty in getting recovery mode open manually and had to use adb reboot recovery, whereupon android recovery picture was there but no menu options.
Could not install TWRP conventionally thus attempted the method shown here.
"NSTALL TWRP
Make sure you have ADB and Fastboot installed.
I always put TWRP.img in the ADB folder - so if I want to boot into TWRP with out installing it this is what I do:
make sure you open a command prompt in the ADB folder "VERY IMPORTANT" and type:
adb reboot bootloader <enter>
fastboot boot TWRP.img <whatever your TWRP image is called in your ADB folder><enter> dont forget the .img at the end
That will re-start your phone straight into TWRP - You can transfer files to and from your computer while in recovery.
If you want to install TWRP permanently, copy your TWRP image to your mobile "while you are in TWRP RECOVERY mode" then press install, then select images, then select recovery NOT BOOT, then swipe to flash. This method does not install TWRP app on your phone, all you need is a reboot app from the play store that will re-boot you into recovery. "
Flashed both twrp image and super-su within the TWRP booted from pc through adb (as shown in the previously mentioned method).
Upon reboot phone has hung at LG symbol. LED is flashing. ADB recognises device as connected however won't respond to reboot requests.
How do i fix this?
Click to expand...
Click to collapse
use you variant KDZ file and flash it with LGUP.
raptorddd said:
use you variant KDZ file and flash it with LGUP.
Click to expand...
Click to collapse
That worked very well. Thankyou raptorddd.
Praise him. Praise him with great praise.
I've been following this guide:
https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591
to try and root my Pixel C. I was initially following a different guide, but I believe I now have:
bootloader-dragon-google_smaug.7900.50.0.img and TWRP_dragon_3.1.0-2.img, loaded through fastboot
I was then able to push
Update.ZIP_PixelC_Ryu_system-vendor-boot_OPP1.zip and SuperSU-v2.79-201612051815.zip to /sdcard/ via adb in TWRP. I then tried to install both, as per the guide.
I was a bit confused when the "flashing system.img... this will take some time" part took no time at all, but it had taken a while to get to that point so I figured maybe the messages were in the wrong order or something. Both said they were successful.
Tried booting to system - just came back to TWRP.
So I thought I'd try to flash the system image back on. But I can't push any files now. Everytime I try, it creates the files then fails and I start getting read-only file system errors
If I try to install update.zip again (the one above), I now get "failed to mount '/data-full' (Device or resource busy)"
So I'm quite stuck at this point. Can't revert to stock image, can't install the new image... any help would be much appreciated!
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
peter73 said:
I would do the following:
Download the full factory image from here. If you want to keep all of your data extract the zip and remove "-w" from flash_all.bat or flash_all.sh (depending on your OS).
If you keep -w it wipes your settings.
Boot into fastboot and run flash_all.
It will write all data from the factory image to your device and it should boot into android again.
If your tablet is up and running you can download twrp and flash it again on your tablet.
I always flash twrp like this:
fastboot flash recovery twrp.img
fastboot boot twrp.img
if i boot into twrp it asks for a decryption-pass. I skip this and go directly to reboot and reboot into recovery. Now i will not be asked for a password and can go on flashing the latest supersu.
Click to expand...
Click to collapse
I second this ^ except for the fastboot boot twrp.img part. Why do you do that? The first line should be enough.