Related
Hi unlocked and rooted OneX with TWRP is it possible to install the latest ? Viper ROM using TWRP or do need to use clockwork if so any walk through showing a new to custom Roms a step by step guide Googled for it and only get reviews of the ROM
Thanks.....
BedrockFred said:
Hi unlocked and rooted OneX with TWRP is it possible to install the latest ? Viper ROM using TWRP or do need to use clockwork if so any walk through showing a new to custom Roms a step by step guide Googled for it and only get reviews of the ROM
Thanks.....
Click to expand...
Click to collapse
It won't make a difference it will be flashable through TWRP.
Just depends what recovery your most comfortable with !
Wilks3y said:
It won't make a difference it will be flashable through TWRP.
Just depends what recovery your most comfortable with !
Click to expand...
Click to collapse
Thanks for that, now is there instructions on how to download and install Viper is it straightforward read on some sites about flashing kernels etc really a bit puzzling to me although I have flashed a ROM on my Nexus 7 tablet it seemed much more straight forward
Sorry for the newbie questions (
BedrockFred said:
Thanks for that, now is there instructions on how to download and install Viper is it straightforward read on some sites about flashing kernels etc really a bit puzzling to me although I have flashed a ROM on my Nexus 7 tablet it seemed much more straight forward
Sorry for the newbie questions (
Click to expand...
Click to collapse
here's the link. you can find instruction there. http://forum.xda-developers.com/showthread.php?t=1745176
robchongke said:
here's the link. you can find instruction there. http://forum.xda-developers.com/showthread.php?t=1745176
Click to expand...
Click to collapse
Thanks for that, little nervous as the last time I installed a custom ROM (other than my nexus 7) I thought I'd bricked my phone took me two days to get it working (HTC Desire)..
So following those instructions will do the job ?
I need to understand the terminology kernels , boot.img , ROMS, RUU but following those instructions and download the ROM extract the boot.img install that on my phone with fast boot on my PC then boot into TWRP and install the ROM and that's it ?
BedrockFred said:
Thanks for that, little nervous as the last time I installed a custom ROM (other than my nexus 7) I thought I'd bricked my phone took me two days to get it working (HTC Desire)..
So following those instructions will do the job ?
I need to understand the terminology kernels , boot.img , ROMS, RUU but following those instructions and download the ROM extract the boot.img install that on my phone with fast boot on my PC then boot into TWRP and install the ROM and that's it ?
Click to expand...
Click to collapse
you need fastboot folders with fastboot files inside. you can find it here in xda. if this is your first time to flash i suggest you watch video tutorials.
robchongke said:
you need fastboot folders with fastboot files inside. you can find it here in xda. if this is your first time to flash i suggest you watch video tutorials.
Click to expand...
Click to collapse
Yes I have fastboot folder and files just downloaded the Viper ROM extracted the boot.img I have connected my phone checked devices in fastboot and the serial number shows so its there
Acording to the Viper instructions I now need to flash the boot.img then fastboot erase cache is that correct
Where are these videos please
BedrockFred said:
Yes I have fastboot folder and files just downloaded the Viper ROM extracted the boot.img I have connected my phone checked devices in fastboot and the serial number shows so its there
Acording to the Viper instructions I now need to flash the boot.img then fastboot erase cache is that correct
Where are these videos please
Click to expand...
Click to collapse
Correct, flash the boot.img with the command fastboot flash boot boot.img
then fastboot erase cache
then boot to recovery and install the rom.zip via recovery.
Thanks so it really is that simple or am I missing something seen lots having problems with boot loops etc is there anything else I need to be aware of
As far as I can see the order and actions I need to do bearing in mind my HTC is already bootloader unlocked and rooted
1Download the ROM copy to phone
2 Extract Boot.IMG from the ROM
3 Boot my phone into boot loader
4 Connect to PC and in fastboot (phone shows fastbootusb) fast boot flash boot boot.img
5 Still in fastboot fastboot erase cache
5 Boot into recovery (connected to PC or not?) Full wipe then install the ROM followed by installing the updates through recovery
Thanks again
BedrockFred said:
Thanks so it really is that simple or am I missing something seen lots having problems with boot loops etc is there anything else I need to be aware of
As far as I can see the order and actions I need to do bearing in mind my HTC is already bootloader unlocked and rooted
1Download the ROM copy to phone
2 Extract Boot.IMG from the ROM
3 Boot my phone into boot loader
4 Connect to PC and in fastboot (phone shows fastbootusb) fast boot flash boot boot.img
5 Still in fastboot fastboot erase cache
5 Boot into recovery (connected to PC or not?) Full wipe then install the ROM followed by installing the updates through recovery
Thanks again
Click to expand...
Click to collapse
1 Download the ROM copy to phone
2 Extract Boot.IMG from the ROM place it inside the fastboot folder
3 Boot my phone into boot loader
4 Connect to PC and in fastboot (phone shows fastbootusb) fastboot flash boot boot.img
5 Still in fastboot fastboot erase cache
6 Boot into recovery (connected to PC or not?) Full wipe then install the ROM followed by installing the updates through recovery. connected or not you can flash the rom. don forget to wipe dalvik cache and wipe cache. you can update your rom OTA or if it doesnt show up you can just download the update ang flash it through recovery. no need to full wipe and flash the boot.img when flashing the update
Thanks for the help guys I'm all done, now on the Viper Rom first impressions its pretty darn good plenty to play around with
The HUB don't seem to do anything when trying to use the various links just get please wait and then a white screen,
Once again big thanks for the help
BedrockFred said:
Thanks for the help guys I'm all done, now on the Viper Rom first impressions its pretty darn good plenty to play around with
The HUB don't seem to do anything when trying to use the various links just get please wait and then a white screen,
Once again big thanks for the help
Click to expand...
Click to collapse
I believe the Venom hub is down at the moment.......
Glad you got it all sorted, it really is painless if you take your time and follow the guides.:good:
craftycarper1 said:
I believe the Venom hub is down at the moment.......
Glad you got it all sorted, it really is painless if you take your time and follow the guides.:good:
Click to expand...
Click to collapse
Certainly is, think all these warnings re briking your phone makes me nervous that and the problems I had on my old Desire took 2 days to get a ROM on that lol
The more I play with Viper the more I like it, its like having a new phone
BedrockFred said:
Thanks for the help guys I'm all done, now on the Viper Rom first impressions its pretty darn good plenty to play around with
The HUB don't seem to do anything when trying to use the various links just get please wait and then a white screen,
Once again big thanks for the help
Click to expand...
Click to collapse
So did you use twrp to flash the ROM or your PC? Is it possible to use twrp?
Dude ....you are bumping a thread from November last year ! What do you expect to hear ! A Rom is always flashed with a custom recovery and the boot.img file with the pc. Always have been like that
So i'v been trying to get cm10 on my xperia s.
I have unlocked my bootloader, and followed this guide
https://www.youtube.com/watch?v=O52IeX93Jek
Steps i took:
1.Factory reset
2.I placed the ziped "FXP221-cm-10-20130524-UNOFFICIAL-nozomi" and "gapps-jb-20121011-signed" files on the sd card
3. flashed boot.img using fast boot
4. Installed the rom and then the gaps
5. reboot
But when i reboot i'm stuck in the boot loop.
I've now tried this 3 times but always get the boot loop. What can i do to avoid that?
Just format system & then flash rom.Everything will be fine
Sent from my Xperia SL using xda premium
I'm knew to the concept of installing new roms so i need a bit more elaborate answers.
At the moment I'm back on the stock rom and would like to know what i have to do different so that i can install cm10 without getting a boot loop.
I was successful in installing a new rom.
schpongo said:
I'm knew to the concept of installing new roms so i need a bit more elaborate answers.
At the moment I'm back on the stock rom and would like to know what i have to do different so that i can install cm10 without getting a boot loop.
I was successful in installing a new rom.
Click to expand...
Click to collapse
The Reason Why You Are Getting A Bootloop.
Flashing of Boot.img is Not Proper.
What You Need To Do.
Flash boot.img using FLASHTOOL.
In the zip file you have got, extract boot.img in the zip and place it on desktop or anywhere you can find.
Keep zip file in your phone storage.
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (from desktop if you have extracted there)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
In Recovery
-Whip Cache Partion,
-Cache,
-Dalvik Cache,
-Fix Permissions,
Flash The ROM
(Step By Step GUIDE With Images)
http://forum.xda-developers.com/showthread.php?t=1963961
little problem
dwarkesh2492 said:
The Reason Why You Are Getting A Bootloop.
Flashing of Boot.img is Not Proper.
What You Need To Do.
Flash boot.img using FLASHTOOL.
In the zip file you have got, extract boot.img in the zip and place it on desktop or anywhere you can find.
Keep zip file in your phone storage.
Set USB Debugging On from Settings - Developer Options.
Connect the phone to the PC.
Click 1 - Click the Lightning icon.
Select 2 - Select the Fastboot Mode.
Click 3 - Click Ok.
Click 4 - Select Reboot Into Fastboot Via Adb and wait for the phone to go into fastboot mode. (Blue led).
Click 5 - Select Reboot Into Fastboot Via Fastboot and wait for the phone to go into fastboot mode. (Blue led).
Click 6 and 7 - Select the boot.img (from desktop if you have extracted there)
Click 8 - Reboot phone. After reboot, the phone will be in recovery mode.
In Recovery
-Whip Cache Partion,
-Cache,
-Dalvik Cache,
-Fix Permissions,
Flash The ROM
(Step By Step GUIDE With Images)
http://forum.xda-developers.com/showthread.php?t=1963961
Click to expand...
Click to collapse
Don't know why, but it doesn't work for me.
Got a XPeria Go with formerly CM9 on it, updated to 4.1.2 and follow this guide: http://go.apeboys.org/index-de.html wich with CM9 worked perfectly. But, now with CM10 i got everytime a Bootloop and not able to fix it.
i used also your guide for flashing the boot.img but it even doesn't work
i tried it several times, and searched for reasons and another guids and tipps, but nothing worked, and since my x10 mini got a sim-lock wich i can't fix, im a little afraid about exotic tipps.
i got an open Bootloader and everything should be ready to do this....
so my question is: How can i fix that?
thanks for help and sry for my bad english.
Exact same problem here
Aaskereija said:
Don't know why, but it doesn't work for me.
Got a XPeria Go with formerly CM9 on it, updated to 4.1.2 and follow this guide: http://go.apeboys.org/index-de.html wich with CM9 worked perfectly. But, now with CM10 i got everytime a Bootloop and not able to fix it.
i used also your guide for flashing the boot.img but it even doesn't work
i tried it several times, and searched for reasons and another guids and tipps, but nothing worked, and since my x10 mini got a sim-lock wich i can't fix, im a little afraid about exotic tipps.
i got an open Bootloader and everything should be ready to do this....
so my question is: How can i fix that?
thanks for help and sry for my bad english.
Click to expand...
Click to collapse
I don't know what's the problem here. The last thing that would cause this would be the fact that I changed the .zip's name (I did that).
AlexBurnout77 said:
I don't know what's the problem here. The last thing that would cause this would be the fact that I changed the .zip's name (I did that).
Click to expand...
Click to collapse
Thank you for the answer.
I fixed the Problem be reflashing the rom and kernel.
How?
schpongo said:
Thank you for the answer.
I fixed the Problem be reflashing the rom and kernel.
Click to expand...
Click to collapse
BTW this is still a problem for me. Nothing seems to work. I flashed everything and wiped everything before flashing but still no satisfying outcome.
I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices
I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.
We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...
Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!
You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device
k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"
ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.
k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me
Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.
When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?
Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.
@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.
motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse
Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?
Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL
edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!