Related
First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL. (There's another link in the forum to do this, I can't find it at the moment)
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Galaxy S i9000 as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
If you can't seem to get ROM Manager off the market, you can get it from my homepage:
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just installed! Working great!
Installed with ROM manager. Works like a charm! Thanx alot Koush!
works fine
works like a charm
Installed, everything working without problems.
To install roms with clockwork we need roms in *.zip format? Where to get them?
Sent from my GT-I9000 using Tapatalk
Just got my phone
will try it after charging ]
YOU ARE THE MAN
thank you and thanks all Xda devs and members
hmm ... I know this might sound stupid but, acually GSG is my first android phone, though I know how to flash roms with odin and how to apply update.zip and all that but what is the difference between this and ClockworkMod Recovery ?? and does it use the same components as odin ? (I mean CODE, CSC, MODEM and Pit) ?
Stickied. Closing the other one. Not sure why you would start a new thread instead of modifying the old one though...
Thanks Koush your the man. Coming from a htc magic I hate this odin bull
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
Click to expand...
Click to collapse
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
kalpik said:
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
Click to expand...
Click to collapse
Ahhh... I guess I'm not very used to this "Internal SD Card" thing... there was the update.zip I used to root the phone there and I only checked my regular External SD.
Everything is fine now, sorry for bothering.
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Click to expand...
Click to collapse
I had the same issue. Must have been the update.zip, but I didnt remove it, just pressed the other option, went into manual recovery mode, rebooted went into rom manager and backed up my files. Worked a charm
Does this mean there will be no more work on a permanent recovery solution?
I have the Korean version M110S - and it does not have the standard recovery (it is crippled - no apply:update.zip). Is there and abd command to "apply update.zip" ?
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
This may sound stupid, but I'm kinda new to Android modding (SGS is my first droid, moving here from WiMo on SE-X1) and.... What is Clockwork?
So if I ever needed to send this phone in for warranty purposes, I could just flash the backup of my stock ROM in and I should be good to go?
does this method works for captivate and vibrant???
edit: just install/ captivate and vibrant option available.
Rithina said:
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
Click to expand...
Click to collapse
Worked for me with mimocan ext4 fix
I have the Galaxy S III SGH-i747m model on stock Jelly Bean 4.1.1 ROM on the Canadian Rogers network. (I live in BC)
I have been trying, unsuccessfully, to install a custom ROM. I have rooted and installed Super User, and have flashed the TWRP Recovery ROM v2.4.1.0 I still have the stock kernel and haven't mucked around in the permissions besides installing SuperUser SU app from Google Play store. Right now, I have managed to wipe out my entire internal storage. I have everything backed up on the google server, so I'm not too worried, but I have no OS right now. Regardless, I have tried many times with many different custom ROMs, and everytime I get a Status 7 error and a failed ROM flash. I have been trying for weeks to find out what I'm doing wrong, but can't seem to find anything that works. Can anyone please help me out with a step by step guide to install a custom rom? Heck, even to re-install my stock ROM would be better than nothing at this point. The last guide I tried to follow was Cyanogenmod 10.1. The file was called Liquid Smooth.
I currently have the ROM file and the gapps pakage on my external SD card, but, everytime I try to install it I get that Status 7 error.
Thanks in advance.
AuricPaulin said:
I have the Galaxy S III SGH-i747m model on stock Jelly Bean 4.1.1 ROM on the Canadian Rogers network. (I live in BC)
I have been trying, unsuccessfully, to install a custom ROM. I have rooted and installed Super User, and have flashed the TWRP Recovery ROM v2.4.1.0 I still have the stock kernel and haven't mucked around in the permissions besides installing SuperUser SU app from Google Play store. Right now, I have managed to wipe out my entire internal storage. I have everything backed up on the google server, so I'm not too worried, but I have no OS right now. Regardless, I have tried many times with many different custom ROMs, and everytime I get a Status 7 error and a failed ROM flash. I have been trying for weeks to find out what I'm doing wrong, but can't seem to find anything that works. Can anyone please help me out with a step by step guide to install a custom rom? Heck, even to re-install my stock ROM would be better than nothing at this point. The last guide I tried to follow was Cyanogenmod 10.1. The file was called Liquid Smooth.
I currently have the ROM file and the gapps pakage on my external SD card, but, everytime I try to install it I get that Status 7 error.
Thanks in advance.
Click to expand...
Click to collapse
did you just wipe data/factory reset or did you also format /system?
you're getting the status 7 error because you arent using the latest recovery version. hit me back
xBeerdroiDx said:
did you just wipe data/factory reset or did you also format /system?
you're getting the status 7 error because you arent using the latest recovery version. hit me back
Click to expand...
Click to collapse
Yes...stupidly... I formatted as well, thinking that that might solve the problem. Where can I get the latest recovery version? And, sorry, I'm new, so, not sure what you mean by "hit me back". But thanks for the reply.
AuricPaulin said:
Yes...stupidly... I formatted as well, thinking that that might solve the problem. Where can I get the latest recovery version? And, sorry, I'm new, so, not sure what you mean by "hit me back". But thanks for the reply.
Click to expand...
Click to collapse
in twrp, when you select "reboot" or "advanced", does it give you the option to reboot into recovery? i'm asking as i use CWM, not TWRP
thirty oniesl
xBeerdroiDx said:
in twrp, when you select "reboot" or "advanced", does it give you the option to reboot into recovery? i'm asking as i use CWM, not TWRP
Click to expand...
Click to collapse
Yes, I can reboot into recovery.
AuricPaulin said:
Yes, I can reboot into recovery.
Click to expand...
Click to collapse
make sure you have the correct ROM and gapps (compatible with your model). then i would try a different recovery.
you could download this flashable clockworkmod recovery zip and place it on your external sd card: http://d-h.st/8qP
it's not a touch version. you'll have to use the vol up and vol down buttons to navigate and the power button the select.
in twrp, mount external sd and then flash the CWM recovery like you would a rom. reboot into recovery.
make sure the external sd is still mounted and flash ROM & gapps twice. reboot
---------- Post added at 09:55 PM ---------- Previous post was at 09:49 PM ----------
hit me back is American for "reply back"
I can't seem to do anything now. Did I brick my phone?
Can you not get into recovery any more? If you can why dont you post the links for the rom you are trying to install and we can tell you if its the right one. Also do you have a external SD card to put the ROM and Gapps on
AuricPaulin said:
I can't seem to do anything now. Did I brick my phone?
Click to expand...
Click to collapse
Pbwizkid said:
Can you not get into recovery any more? If you can why dont you post the links for the rom you are trying to install and we can tell you if its the right one. Also do you have a external SD card to put the ROM and Gapps on
Click to expand...
Click to collapse
he has the rom and gapps on the external already.
if you can get into download mode, i'd try restoring via odin
http://forum.xda-developers.com/showthread.php?t=1968625&highlight=stock+firmware
1. Extract contents of the zip/rar archives
2. Wipe data-factory reset/cache/dalvik-cache
3. Plug phone into PC
4. Place the phone in Download Mode (vol dwn + home + power). Press volume up when prompted
5. Open Odin and ensure the COM box is highlighted, detecting your device
6. Uncheck the Auto Reboot option
7. In the PDA box, select the .tar.md5 file you downloaded
8. Flash the file by hitting Start
9. Once you get a Success message, pull the battery and then replace. Immediately go into recovery (vol up + home + power. release power button at Galaxy S3 logo and/or vibrate).
10. Select Wipe data/factory reset, then wipe cache. Reboot
you can then do some research and decide what files/procedures you want to try if you wish to root again and flash custom firmware
Thanks for the help guys. I am attempting to restore my phone right now. Will let you know how it went.
OK! Up and running! And I have it rooted with the latest TWRP recovery image installed. Now I just need to find a good custom ROM. Thanks againg guys!
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
dosada said:
Hello
I have purchased a second hand Nexus. It is rooted and has got custom rom. Also Teamwinner or so is installed. When i boot into recovery to install some other rom it exits with error 7. Same when i try to update the teamwinner to the newest version.
Any idea what to try?
Click to expand...
Click to collapse
i remember seeing error 7 before on a rom i tried to flash.. i was using CWM so its not the recovery's fault. turns out there was a problem with the rom...
so find another rom to flash would be my answer for now.
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
dosada said:
The problem is that i get this error whatever i tried to flah. Even cwm or some other rom result in same error
Click to expand...
Click to collapse
What procedure are you using to flash? What file are you trying to flash and where did you get it from?
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
dosada said:
I start up the phone using volume down and power. Then in teamwinner i chose install zip and then the file
so far have tried, all downloaded from here or linked from here, those files
CWM-Touch-6.0.2.5-DJ
Hellybean-20130405-crespo
TWRP-2.4.4.0-DJ
jellyshot_crespo-v3.3
nothing works. all of them exist with error 7
Click to expand...
Click to collapse
.....
This is the Galaxy Nexus forums, that firmware aka ROM is for crespo aka Nexus S
Sent from my Nexus
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
I wouldn't be surprised if your recovery is either not for your device or not even a flash able zip.
dosada said:
Fair enough about the roms, but why cant i even install cwm? This shows me just the error 7 too
Click to expand...
Click to collapse
Where did you get that CWM? http://www.clockworkmod.com/rommanager? If so those are img files, for flashing from fastboot. But I have no idea what "DJ" is for. To flash from recovery it needs to be packaged in a flashable zip.
Or you can install CWM from the ROM Manager app. Or TWRP from GooManager.
quite frankly i wouldnt use CWM. The UI is annoying as hell, and it tends ot be a lot slower, at least from my own experience.
I recommand TWRP, http://www.teamw.in/project/twrp2/90 latest version here for maguro.
if you have adb set up, installing twrp is cake, simply open adb and type:
1) adb reboot bootloader
2) fastboot flash recovery TWRP.img <-----assuming you are in the directory of that img file you just downloaded, and TWRP is just the name of the img file, its usually attached with version, so i would rename it for easier access.
3) after you flashed it just boot into recovery and start flashing your new rom.
If all else fail.....use the toolkit and flash factory image for a fresh start, i havnt failed with factory image yet
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!