Alright guys I have a pixel 6a and was wanting to try this Rom out and I can't seem to figure how I'm suppose to flash it since TWRP isn't supported. I tried using the pixel flasher and it kept aborting the install for some reason and I tried using adb side loading and it gave a error saying it couldn't read the signature or something along those lines. Could someone please help me out thanks in advance
your question needs meaningful heading and more details. "this rom" means nothing to me. I am pretty sure it comes with installation instructions. read it before asking, mention exact steps and on which step it failed.
Didn't think it mattered what I was trying and the instructions was read a few times. Still didn't work that's why I posted about it. On the phone it said it was successful but the command prompt said otherwise and phone went into a loop
I think it's my laptop Asus N4020 because I have the same issues with my OnePlus device as well.
Related
Hi guys,
Tried following the directions to root my Nexus S (at&t & 2.3.4) by following this guide:
http://forum.xda-developers.com/show...0#post19647210
I have the same problem as the poster on this page, I am stuck at the Google splash screen when booting. Someone responded to him, but I find the answer unhelpful. Can someone please help? Thanks.
Your link doesn't work.
Sent from my Nexus S 4G using xda premium
Sorry about that... Here's the URL.
http://forum.xda-developers.com/showthread.php?p=19647210#post19647210
That works for me, should work for you, but let me know if it still doesn't work...
Read my question in dev thread. Also, someone responded to you in the original thread.
To answer your question from the Dev threat, I have flashed Clockwork and the bootloader is unlocked. When you ask if I have "set up" fastboot or adb yet, I'm not sure what you mean. I'm using a Mac, not a PC, so this is a little trickier (at least in terms of me finding directions). I have adb files unzipped on my desktop that I'm using in terminal... Basically, I followed this guide:
http://forum.xda-developers.com/showthread.php?t=878446
I then tried to use the MoDaCo Superboot method as explained in the thread, which is how I got to the problem i'm at now. I'm following the advice of the poster who replied to the original thread as we speak... I'll let you know how it goes. His advice is basically to just flash a custom rom since I already have custom recovery and an unlocked bootloader. Although I tried flashing one of the ICS ROMs and ran into an error trying to flash it. I'll update this shorlty with results of another ROM.
jmusso said:
To answer your question from the Dev threat, I have flashed Clockwork and the bootloader is unlocked. When you ask if I have "set up" fastboot or adb yet, I'm not sure what you mean. I'm using a Mac, not a PC, so this is a little trickier (at least in terms of me finding directions). I have adb files unzipped on my desktop that I'm using in terminal... Basically, I followed this guide:
http://forum.xda-developers.com/showthread.php?t=878446
I then tried to use the MoDaCo Superboot method as explained in the thread, which is how I got to the problem i'm at now. I'm following the advice of the poster who replied to the original thread as we speak... I'll let you know how it goes. His advice is basically to just flash a custom rom since I already have custom recovery and an unlocked bootloader. Although I tried flashing one of the ICS ROMs and ran into an error trying to flash it. I'll update this shorlty with results of another ROM.
Click to expand...
Click to collapse
If like you said you have the exact same problem as the other poster and you also see the android and triangle then you don't have a custom recovery installed. You would have to have gotten fastboot setup to flash the custom recovery.
Sorry, I may have been misinformed when I said that I had the "exact same problem." I'm having a similar one, but I have the custom recovery installed. I just posted on the original thread, located here...
http://forum.xda-developers.com/showthread.php?p=19648719#post19648719
It might be easier if we all worked/posted on that thread, also in case someone else Google's this later on and has the same problem, continuity will be helpful.
Thanks again.
So,a few days ago I decided on advice from a friend to root my phone, a Galaxy S 4G (T959) from T-Mobs I got in January. The process itself was easy and made me feel (apparently) over confident.
After doing a little reading I decided if it was that easy, I should upgrade it from 2.3.6 Gingerbread up to Ice Cream Sandwich, I mean what could possibly go wrong?
I ran into more than my fair share of glitches.
Well at some point I tried solutions for problems with ExRom 2.0
E:Short write of /tmp/sideload/package.zip (no space left on device)
and then from code.google zip
E:signature verification failed
New ROM Data fix
E:failed to verify whole-file signature
E:signature verification failed
At some point I should have stopped myself, but I kept reading tips and solutions. 9 hours of reading post on XDA and half a dozen other forums, thinking, "I used to build desktops, I'm sure I can do this myself." Trial and error, again, what could possibly go wrong?
Now 3 days later and some 35 hours of reading posts, I've managed to get my phone to a point where, no three button combo seems to bring it download mode, perhaps its actually stuck in download mode. It will only bring up "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and an image of phone to computer when i hit any key or plug it into a USB power source (this is download mode, no?).
I'm assuming this is the everlasting reference I keep finding of "soft bricking" as I can't do much with the phone.
So, I've got Odin v1.85 and a bunch of downloads I don't think I know which are which anymore. I keep finding threads where I think, "this is it!" only to find a cold link. I've not spent the better part of 35 hours in the past three days trying to fix my phone. I'm on the road for work and the only communication tool I have is my laptop (thank goodness for this at least).
Since my brain is fried, could someone tell me is it fixable, or is it really what I think and the phone just doesn't like me anymore and wants to do nothing? Could someone point me to right files for ICS for T959 and installation instructions, or to the *correct* thread with instructions. I'm worried I followed the wrong instructions enough already. Any help would be appreciated.
Right now, any time i plug my phone in or touch a power button or any combo i get this the image of phone to computer, "Firmware encountered an issue..." Odin will give me a yellow window (0:[COM4]) so it does see it which I believe leaves me in good condition to save the phone. I can find the pit file, I just need perhaps a ROM or a tar for ICS for my T959V?
THANKS GUYS,
Regards
The image you see is download mode. Follow the guide in the second link of my signature and flash with bootloaders. You will be fixed up.
We don't have ICS yet. Only flash ROM's from this forum to your phone. And after following the guide - only flash Gingerbread based ROM's. The guide in the first link of my signature can help you with that.
P.S. I only read the first and last paragraph of your post.
lumin30 said:
The image you see is download mode. Follow the guide in the second link of my signature and flash with bootloaders. You will be fixed up.
We don't have ICS yet. Only flash ROM's from this forum to your phone. And after following the guide - only flash Gingerbread based ROM's. The guide in the first link of my signature can help you with that.
P.S. I only read the first and last paragraph of your post.
Click to expand...
Click to collapse
Thanks so much for responding, funny enough, I found another post similar to mine that you responded to, and decided while I wait I would follow that link... Maybe I'm capable afterall! Will follow up this afternoon!
Thanks again for responding!
orlandodiesel80 said:
Thanks so much for responding, funny enough, I found another post similar to mine that you responded to, and decided while I wait I would follow that link... Maybe I'm capable afterall! Will follow up this afternoon!
Thanks again for responding!
Click to expand...
Click to collapse
Also you said that you have a SGH-T959V, so I'd stay on the T959V forums and flash nothing else from any other forum, unless of course you want an expensive paperweight.
Okay, I rooted my TF101 B90 model and all was good. I installed rom manager and flashed its custom recovery and had that whole issue that the sd card wasn't read and such. After much frustration I finally tried Wheelie (Nvflash) and it keeps failing and now I have nothing on my tablet. I can get into APX mode and flashing the stock rom using many custom utilites always fails (Usually says something like command failure :go failure or could not load bootloader to device) I'm sure it's probably fixable, I just need someone to type it out for me (I'm pretty smart when it comes to Android but I'm honestly stumped right now) Or please redirect me to a post that could help, However I have read a lot of the posts about this and everyone is getting there's to work and I can't get mine. Thank you!!!
Andrew
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
Hi there,
I know this is probably redundant but I've been searching these forums and I'm a bit overwhelmed. Mainly I am trying to discern whether I need to factory reset my phone before I root it or not. If anyone would be kind enough to break it down for a rooting noob, but fairly tech savvy chick, I would really appreciate it. Or just direct me to the most applicable thread for my situation. I have a PC running Windows 8.1 also, if that helps.
Thanks!!!
http://forum.xda-developers.com/lg-g-stylo/how-to/guide-lg-g-stylo-how-to-root-t-mobile-6-t3333916
Factory reset is not necessary.
stuck
i tried following the guide , igot the bootloader unlocked but when i tried to do the flash recovery.img it kept saying it couldn;t find the directory. i moved the img file to the same place as where the adb is installed but that didn't help. i ended up rebooting my phone and it was in oem state. I installed a backup for now but I tried to attempt it again and i couldn't get it to come up in the adb devices anymore. Advice?
never mind
fabuliz said:
i tried following the guide , igot the bootloader unlocked but when i tried to do the flash recovery.img it kept saying it couldn;t find the directory. i moved the img file to the same place as where the adb is installed but that didn't help. i ended up rebooting my phone and it was in oem state. I installed a backup for now but I tried to attempt it again and i couldn't get it to come up in the adb devices anymore. Advice?
Click to expand...
Click to collapse
i figured it out, thanks for your guidance
dammit
I swear I did everything right but now my phone is on LG screen and I cant do anything
fabuliz said:
I swear I did everything right but now my phone is on LG screen and I cant do anything
Click to expand...
Click to collapse
I think there is a typo in this set of directions.
Try this one:
http://androidforums.com/threads/guide-how-to-root-t-mobile-6-0-update.1008880/
(Step 7 is correct here)