Related
So I powered the phone down for class, and when I turned it back on three hours later, it hung at the boot animation, and then eventually just went to a black screen. Battery is at 100%, I had it charged that morning. Is there any way to fix my phone?
Need a little more info from you. Did you root, install any lag fixes, did you make a nandroid backup? One way that's sure to fix it is the Odin One Click Downloader listed in the development section of the Captivate forums, its always worked for me, but if you didn't have a backup it will wipe your settings and info and you'll be starting from scratch.
I was rooted, I was in the process of the 'one-step lag fix' when I realized busybox was giving me an error. It was version 1.18.1 instead of 1.17.1. So I went back to the recovery menu thing and reinstalled packages.
I have no clue what Nandroid is honestly. I'll look into Odin, but is there a Mac version?
As far as I know there isn't a Mac version of Odin yet....once you root download Rom Manager from the market place and then have it install the Clockwork Mod Recovery image, once thats done if your rom is stable use Backup current rom. I'd check if theres a wiki for Mac users, I use windows so I have no clue. I know you can download a new version of busybox installer from the market that lets you choose which version of busybox to install now. The ext2 lag fixes are pretty unstable and have caused some headaches (worked fine for me, but I still reverted back to normal). I'll post back later if I figure out a way for you to return to stock with a mac, but you might be able to just flash one of the stock roms through rom manager now after you change its name to update.zip, or flash one of the new roms that root for you (I've had pretty good luck with those so far).
Captivate doesnt work
I don't know if we have the same problem, but i got stuck on that black screen and wont boot up. I was able to recover it by doing that one click root for samsung captivate. (check it out on one of the threads) Just run the one click root/unroot it doesnt matter. Now when you're on the phone recovery screen instead of clicking "reinstall something" go to delete data, click it. as well as delete cache. then go up to do a reboot. Thats it, Worked for me hope it works for you!
p.s. Don't know if you can do it on a mac though, or you can always borrow a friends pc.
big99gt said:
As far as I know there isn't a Mac version of Odin yet....once you root download Rom Manager from the market place and then have it install the Clockwork Mod Recovery image, once thats done if your rom is stable use Backup current rom. I'd check if theres a wiki for Mac users, I use windows so I have no clue. I know you can download a new version of busybox installer from the market that lets you choose which version of busybox to install now. The ext2 lag fixes are pretty unstable and have caused some headaches (worked fine for me, but I still reverted back to normal). I'll post back later if I figure out a way for you to return to stock with a mac, but you might be able to just flash one of the stock roms through rom manager now after you change its name to update.zip, or flash one of the new roms that root for you (I've had pretty good luck with those so far).
Click to expand...
Click to collapse
My computer doesn't recognize my captivate at all, so I don't know how I can put an update.zip on the phone.
big32 said:
I don't know if we have the same problem, but i got stuck on that black screen and wont boot up. I was able to recover it by doing that one click root for samsung captivate. (check it out on one of the threads) Just run the one click root/unroot it doesnt matter. Now when you're on the phone recovery screen instead of clicking "reinstall something" go to delete data, click it. as well as delete cache. then go up to do a reboot. Thats it, Worked for me hope it works for you!
p.s. Don't know if you can do it on a mac though, or you can always borrow a friends pc.
Click to expand...
Click to collapse
I'm gonna try the delete cache/data.
You're most likely going to have to do an Odin flash.
If you are doing the ext2 fix, and busybox throws you an error, there are instructions that say run Remove to back off and fix busybox before rebooting, or this happens.
does anyone know exactly what the 'delete all user data' does?
Does it just delete downloaded apps and your contacts and music and stuff? Or will it like completely destroy my phone?
The only way to completely destroy your phone, is with physical violence, immolation, etc.
so it just goes back to a stock ROM without downloaded apps/root/whatnot?
li1on said:
so it just goes back to a stock ROM without downloaded apps/root/whatnot?
Click to expand...
Click to collapse
Odin will return the phone to an out of the box state, delete all user info will just remove you settings and personal info. I've read in other forums that you don't even need to download drivers to get your phone connected to a Mac, have you gone into settings>applications>development and enabled usb debugging? Try that and then plug your phones usb cable in. The Odin One Click Downloader thread also says you don't need drivers for Mac. I asked in the wiki thread for someone to post some info for Mac users, maybe it'll help.
EDIT: Also I know its a pain but you can get Astro File Manager from the market (free) and go into Preferences and enable browser download, then just download the update.zip on your phone and move it around and rename it with Root Explorer (a paid app but worth the money) that should let you flash roms and so on from your own phone after rooting of course.
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
you have one option, flash the fxz and reroot.
start over.
there is a great nOOb thread telling how to do it.
http://forum.xda-developers.com/showthread.php?t=1396650
ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
How did you back up?
If you used CWM (from the A2 Bootstrapper) just reboot into CWM, go to backup and restore, select restore, and select the backup that you made.
If you didn't use CWM or you can't find the backup then you will have to flash the fxz as said above. It will completely remove all of your apps and return you to stock 2.3.5. Make sure that you follow the directions about replacing files.
Thank you matt99017d I will check the link and cogeary I did the back up CWM I'll go that route first if that doesnt work, I'll go back to the beginning. Thank you again for the help
I could not find the backup in CWM so I flashed fxz following the instruction on the link you provided and the info. I'm back to 2.3.6 and it is rooted. Thats as far as I'm going for now, thanks for the help you all provided.
I see at /system/etc/init.d 2 files with sd-card optimization. 03sdtweak and 99override. Is there right or needed to delete one of them?
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Douchewithaphone said:
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Click to expand...
Click to collapse
https://market.android.com/mylibrary
^ shows everything you've installed from the Android Market. You should have records somewhere if you got things from the Amazon Appstore.
I haven't tried it myself but if you've made a backup in CWM you have the option to only restore apps/data.
Well I decided to give SuperCharged V5 with update 1, and when I disconnected form the charger this morning it was stuck in the boot animation. It has been stuck in that position for the last 30 minutes.
I connected it to PC and it doesnt show as being connected. I've done a search and can't find anything on how to fix it.
I did a battery pull, took SD card out to see if I could maybe transfer something from it to desktop, but everything that was on it is gone.
Don't know what happened.
Can someone point me in the right direction?? In the mean time I'll keep looking.
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
ej_424 said:
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
Click to expand...
Click to collapse
I am sorry to say, but if you can't get into fastboot it's probably bricked
so i installed V5 and update 2 and i am getting the force closes and my phone won't show up when i plug the usb into my computer
and i can't delete or edit files in my files and i can't open any websites or connect to airdroid on wifi, or use data so i can't get any files onto my phone
help...
flashing the stock fxz worked
Man...and I was gonna do this...flash the supercharged ROM. Nevermind.
after i flashed the 2.3.5 fxz like the bootstrapping thread instructed, i installed the ota update and rooted my phone again and then i tried the custom rom again just for fun
but this time i did v5 and then update 1. then instead of doing update 2, i flashed the image of the rom that's linked right under update 2 in the supercharged thread
it works flawlessly for me now
so i would just recommend that
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.
Thread closed.
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!