I'm new to flashing GSI. I don't know what I need to wipe in TWRP, I need some tutorial for flashing GSI on my device, which is SM-A125F running Android 12.
Koi3551 said:
I'm new to flashing GSI. I don't know what I need to wipe in TWRP, I need some tutorial for flashing GSI on my device, which is SM-A125F running Android 12.
Click to expand...
Click to collapse
There are quite a few guides on XDA that address your question. Did you search before posting?
As a courtesy, here is a guide; just substitute whatever GSI you want to flash. The principles remain the same.
Thanks man. I just want to make sure my phone won't be bricked.
V0latyle said:
There are quite a few guides on XDA that address your question. Did you search before posting?
As a courtesy, here is a guide; just substitute whatever GSI you want to flash. The principles remain the same.
Click to expand...
Click to collapse
Thank you. I just want to make sure my phone won't be bricked. Sorry if I wasted your time.
Koi3551 said:
Thank you. I just want to make sure my phone won't be bricked. Sorry if I wasted your time.
Click to expand...
Click to collapse
Remember that "brick" means your phone is completely useless - it's about as useful as a brick, and you can do nothing to fix it. This is generally only the case in seriously extenuating circumstances when you REALLY screw something up, like corrupt the bootloader. I don't think it's possible to do this via TWRP, so it's nothing to worry about. If a GSI fails to boot, you can simply boot back into TWRP and try again.
Related
So I have a small problem with my One S (S4).
Whatever ROM I flash I also have to flash fastboot boot.img wheter it's really needed for the ROM or not.
But that's not all.
Every time I want to reboot my phone, whatever ROM it is.. i get stuck in a bootloop and I have to fastboot flash boot.img again.
So basically I can't reboot/restart my phone without connecting it with USB and fastboot..
Really. Not even 1 reply?
Thats what I get for waiting a week and not bumping the thread awesome
I think you got no responses cause this is covered everywhere from OP's to many posts on it in the threads. So, unless I misunderstand your post, you have to flash the boot image all the time if you are on hboot > than .09. Or, you will bootloop. If this is what is happening you need to read up more in the threads before flashing the rom. Also, highly recommend you wipe system along with data and caches before flashing new rom.
Good Luck on it--
rugmankc said:
I think you got no responses cause this is covered everywhere from OP's to many posts on it in the threads. So, unless I misunderstand your post, you have to flash the boot image all the time if you are on hboot > than .09. Or, you will bootloop. If this is what is happening you need to read up more in the threads before flashing the rom. Also, highly recommend you wipe system along with data and caches before flashing new rom.
Good Luck on it--
Click to expand...
Click to collapse
Ya I think you did misunderstand because it sounds like it works but each time he reboots he needs to flash boot.img again which is odd.
HD2kty. said:
Really. Not even 1 reply?
Thats what I get for waiting a week and not bumping the thread awesome
Click to expand...
Click to collapse
No need for the comment like that more so when no one really knows what's up but try Flash Image GUI to flash the boot.img and see how things play out.
Thanks guys !
HD2kty. said:
Thanks guys !
Click to expand...
Click to collapse
So is it fixed then? and if yes how?
Darknites said:
So is it fixed then? and if yes how?
Click to expand...
Click to collapse
Yeah, missed the "every reboot" comment--sorry
If you did resolve it HD2kty, good to let us know so someone else may be helped.
Hope you did get it sorted. Only thing left would be to reformat sdcard and see. As long as you were wiping system also--
Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?
BombasMirko said:
Hello, today I decided to unlock, root my phone. I also decided to install new rom. And everything went fine but befor installing I insted Factory reset I formated data. I don't know what I was thinking. It may be that I was using TWRP Touch for a first time. Can somebody help me get back to at least to Stock if it is possible. Is it possible to connect phone in TWRP to transfer data from computer to it?
Click to expand...
Click to collapse
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.
ttl1982 said:
Does mount usb work on twrp? If so you can copy a rom zip to your device. If not than use search here on xda or google you probably need to unroot again and restore with a factory image.
Click to expand...
Click to collapse
Moutning doesn't work.
I found this: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Will this work for me? I was never in this situation before.
You can either use adb to push a ROM zip to your phone, or just flash the stock images to your phone. http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5
Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?
pyrogoggles said:
Follow this tutorial right here. It'll completely fix EVERYTHING that you are describing.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You'll need the Android SDK for that tutorial, also. Also a brain.
What OS is your PC on?
Click to expand...
Click to collapse
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.
BombasMirko said:
Either Xubuntu or Windows 8.1. What is prefered? Xubuntu probably because you don't need drivers.
Click to expand...
Click to collapse
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!
pyrogoggles said:
You should use Windows 8.1 for this tutorial. It's aimed towards Windows and the command prompt. Followed word by word, that is, for Windows.
Hope this tutorial fixes it!
Click to expand...
Click to collapse
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation
BombasMirko said:
It wen't just fine. Thank you guys. I was really scared that it will be like long, risky and difficult process. Thanks again.
Click to expand...
Click to collapse
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Lol its happened to me so many times that I end up doing it now on purpose just to clean the phone 100% before flashing a new ROM.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Lol I thought I was the only one who does this
Sent from my HAMMERHEAD
Aerowinder said:
Virtually every member here has gotten themselves into a situation that they weren't sure they would be able to fix. It happens to all of us. It's Android initiation
Click to expand...
Click to collapse
Yeah and this is actually the best school to learn new things. Now I know that it is not that bad at all
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
junkshot9112 said:
Hey guys. I really messed up. I was running 7.1 from launch, and have had the systemless root basically since the beginning. I attempted to mount /system as /r/rw (for the stupidest reason) and my phone booted into a "no command" bootloop. Is there any hope for me? I can access recovery (I think). I can get into adb and fastboot and get the device recognized by the computer.
I will donate, buy coffee, anything for some love. Thank you so much for your time!
Click to expand...
Click to collapse
Well if you have an unlocked bootloader you can simple flash the stock images.
NBreunig3 said:
Well if you have an unlocked bootloader you can simple flash the stock images.
Click to expand...
Click to collapse
Thank you so much for the reply. I think I could even do a factory reset from recovery, but I'm not sure. I'm pretty new at this. I was really hoping there may be a way I could backup my data first, or even fix the issue, as I'm pretty sure I know what happened. I think my permissions are set wrong, but I could be entirely wrong. I found this guide that sounds like my issue, but it is for a different device. I've tried adapting it to the best of my ability, but I can't get the phone in ADB mode from recovery. http://www.gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Wouldn't hurt to try knowing you can also just flash stock images.
NBreunig3 said:
Wouldn't hurt to try knowing you can also just flash stock images.
Click to expand...
Click to collapse
Can you point me in the direction of someone who may be able to help me do just that? I've tried just about all I can think to do. I really am new at this and feel I am in over my head. I really appreciate any and all help and would gladly donate to this site or any individual user who is able to help me solve my problems (I hope it isn't against your rules to say things like that).
Thanks again.
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
NBreunig3 said:
This site straight from Google has all the files and instructions. https://developers.google.com/android/images
Follow directions but don't lock bootloader.
Click to expand...
Click to collapse
Sorry, I was unclear, that was my fault. I believe I know how to flash stock images. That is something I have done since the OG Droid. I was asking if you may know anyone who may be able to help me attempt to backup my data, reset my permissions, or even get the phone into ADB mode before I resort to losing everything. Again, apologies for being unclear.
No worries. I would just look online and possibly post another thread here or just wait for replies.
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
cntryby429 said:
Flash the stock image but remove the -w from the script to keep from losing data. Search around here for instructions. It's been described a zillion times.
Click to expand...
Click to collapse
Is this what is referred to as a "dirty flash"?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
robocuff said:
I suppose one could think of it that way but it really isn't. Everything other than data will be wiped and flashed. It'll all be new with the exception of your data partition. Removing the w allows you to keep all your apps and their settings in tact. The rest will all be new though. It can't hurt to try it. If it doesn't fix your problem (which it should) you can always run it again and wipe data along with everything else.
Click to expand...
Click to collapse
I was successful. Thank you so much. What can I do for you to show thanks?
junkshot9112 said:
Is this what is referred to as a "dirty flash"?
Click to expand...
Click to collapse
Yes. But in reality it is not much different than taking an OTA. That never wipes data. I only clean flash if I am having issues after a dirty flash and I can't remember the last time that happened.
Sent from my Pixel XL using XDA Labs
junkshot9112 said:
I was successful. Thank you so much. What can I do for you to show thanks?
Click to expand...
Click to collapse
Your thanks is more than enough.?
The phone is not fully booting.
What?
aholeinthewor1d said:
What?
Click to expand...
Click to collapse
Just because my Verizon pixel ran into a boot loop after Resurrection rom a change grom purenexus. I've known issues from the past to be about build, ( European, ECT.) Or order of operations. Even supersu, usually after the fact for supersu. As a junior member with some xp I started this thread anyway after an Odin to stock. What did I do wrong,? Google pixel, Verizon, NOF26V, unlocked. I flashed twice, then Odin. Still looped.
April fool's ... ? Odin ... Really
piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
I was thinking the same thing
Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?
piperx said:
April fool's ... ? Odin ... Really
Click to expand...
Click to collapse
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash
alladinscastle said:
Yeah, Odin. Download mode. That's how to save a phone from a bad rom flash
Click to expand...
Click to collapse
Odin is a Samsung thing. Fastboot mode or recovery or bootloader mode are the usual terms for a Google phone.
alladinscastle said:
Right so... I wanted to flash Resurrection rom. I did that with TWRP duh. And pixel won't finish it's boot for 30plus minutes after. So what do I do? I Odin stock NOF26V in download mode to get my phone running again. Comprehend?
Click to expand...
Click to collapse
I comprehend just fine, the real question though:
Do you have any idea what your doing ?
piperx said:
I comprehend just fine, the real question though:
Do you have any idea what your doing ?
Click to expand...
Click to collapse
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
Really?
https://forum.xda-developers.com/pixel-xl/development/rom-t3548615
If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?
alladinscastle said:
If im running 7.1.1 and Resurrection is 7.1.0. could the downgrade from flashing cause my problem?
Click to expand...
Click to collapse
wipe your data and cache partitions.
alladinscastle said:
I had no problems flashing pureexus on my Verizon pixel. Resurrection rom is giving me problems. Phone won't boot past Google screen. Matched vendor. It's not that. What Android build is Resurrection Rom based on?
Click to expand...
Click to collapse
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post
Answer this. Resurrection's thread title says 7.1.1. The Op says 7.1.0r7. " users are now asking if the new build will be 7.1.2. " What is is the current build based on. If the Op is outdated, what good is it?
P.s. I have seen some op updates on the rom thread... ok, some things are still outdated.
Your attitude needs work, maybe consider not replying. I do know some things about rom flashing. It is unnecessary to be rude. It is ok to make corrections about a post.
piperx said:
How in the hell do people flash things they know nothing about?
Do you read at least the op of anything you flash?
I'm still tryin to get over the Odin post
Click to expand...
Click to collapse
Do you enjoy showing off? At be more class at it.......
alladinscastle said:
Do you enjoy showing off? At be more class at it.......
Click to expand...
Click to collapse
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
I agree on this. I do the same, read, read, and read some more until I understand what I am doing. I used to root phones that aren't "google" versions and learned how much of a pain it was.. therefore I am owned the last Nexus brand, and the first Pixel. Using a Google phone is so much easier! But yeah, reading is key. I hopped into this thread to see if someone needed some help, read through the posts, and was so lost as to what this user is doing.. Odin? If the user who is having issues is reading this, just boot your phone to bootloader, use fastboot and format userdata the device (wipe/format) and then fastboot flash the stock 7.1.2 image and wait for custom ROMs to update.
piperx said:
Just because I do my homework (read, read some more, read again, read til I fully understand) before I blindly install something is not showing off.
It's called "common sense"
This stuff is not rocket science
Click to expand...
Click to collapse
Alright moving on. Just generic crap on my thread here
Great news. I'm am now running Resurrection ROM. All I did differently for my Verizon pixel was move from 26V to 27B build. I flashed the rom and twrpRC1, Then I rebooted to bootloader mode and flashed the vender using the adb fastboot command. "Fastboot flash vendor vendor.img" need more specific instruction. See me!!! No more problems here.
Ok guys so I rooted my phone with system less magisk and used adb to temporarily use Twrp so I can keep my stock recovery. Now how can I update to Android without losing data?
Mofo50C said:
Ok guys so I rooted my phone with system less magisk and used adb to temporarily use Twrp so I can keep my stock recovery. Now how can I update to Android without losing data?
Click to expand...
Click to collapse
Is the guides for this down? I know atleast 2 have been written.
whizeguy said:
Is the guides for this down? I know atleast 2 have been written.
Click to expand...
Click to collapse
I don't know I checked but it only has guides for devices with twrp mine has stock recovery
whizeguy said:
Is the guides for this down? I know atleast 2 have been written.
Click to expand...
Click to collapse
Rather than post this redundant it would benefit everyone if you linked the two you know of.
I'm in a similar situation, I keep getting a crash dump error, regardless if i start from OB2,OB3, Official 9.0. Tried different recoveries too
Flash or boot TWRP, factory reset and flash a full firmware. It's not that hard.
rickesh1 said:
Rather than post this redundant it would benefit everyone if you linked the two you know of.
I'm in a similar situation, I keep getting a crash dump error, regardless if i start from OB2,OB3, Official 9.0. Tried different recoveries too
Click to expand...
Click to collapse
Rather than being lazy people need to learn how a forum works, and how to use search. People also need to learn what they are doing with their devices.
This was a place for enthusiasts once, now rooting got so easy and more people are getting into this without doing ANY research by themselves.
If you're getting the Qualcomm crash dump, your best bet is to use the MSM download tool (in the guides section). Then update to pie, and root from that point.