Related
Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.
The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?
yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019
Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.
solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?
assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.
okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.
According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?
no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?
autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.
I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?
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 XDA. First post here. I need the pros.
I may have seriously messed up my Nexus S 4G. The "Google" logo appears when I turn it on but there is no lock on the bottom (there was before) and after that, boot animation of the X keeps restarting. Pull the battery. Hold up and power on. Go into Recovery and I end up with the white triangle and yellow exclamation point inside it.
Did I just brick my phone? Any way to get out of this? I have an upgrade available, but I'd rather check out the Nexus4 before buying the Galaxy Nexus. (Nonreplaceable battery in the Nexus4 might be a killer for me.)
I searched around but no other situations were like mine. Sorry if I missed something. Help me XDA. You're my only hope.
mjnouri said:
Hello XDA. First post here. I need the pros.
I may have seriously messed up my Nexus S 4G. The "Google" logo appears when I turn it on but there is no lock on the bottom (there was before) and after that, boot animation of the X keeps restarting. Pull the battery. Hold up and power on. Go into Recovery and I end up with the white triangle and yellow exclamation point inside it.
Did I just brick my phone? Any way to get out of this? I have an upgrade available, but I'd rather check out the Nexus4 before buying the Galaxy Nexus. (Nonreplaceable battery in the Nexus4 might be a killer for me.)
I searched around but no other situations were like mine. Sorry if I missed something. Help me XDA. You're my only hope.
Click to expand...
Click to collapse
What have you done before this happened?
You have relocked your bootloader?
Fix is easy, you'll lose your data doing so.
Unlock the bootloader using fastboot
Install a custom recovery such as Clockworkmod
From within recovery wipe data
Try to boot like this. If it doesn't boot, go back to recovery, wipe everything and re-install your ROM/stock ROM depending on which you have. You can transfer the flashable zip from within Clockworkmod recovery by mounting your USB storage when connected to your computer.
polobunny said:
What have you done before this happened?
You have relocked your bootloader?
Fix is easy, you'll lose your data doing so.
Unlock the bootloader using fastboot
Install a custom recovery such as Clockworkmod
From within recovery wipe data
Try to boot like this. If it doesn't boot, go back to recovery, wipe everything and re-install your ROM/stock ROM depending on which you have. You can transfer the flashable zip from within Clockworkmod recovery by mounting your USB storage when connected to your computer.
Click to expand...
Click to collapse
First of all, thank you polo for helping me out!!!
At first, I was flashing nandroid backups between AOKP, CM10 M2, and CM7. Then it got stuck in a boot loop of a different sort (don't remember the details) and before I remembered to come over to XDA, I formatted some partitions under Mounts and Storage in CWM like an idiot. However I did wipe data/factory reset, wipe cache, wipe dalvik cache and still nothing.
I just googled some directions on unlocking from fastboot, flashing CWM, and from there let's see how it goes. Wish I brought a cable with me to work, but it'll have to wait a few hours. Thanks polo!
mjnouri said:
First of all, thank you polo for helping me out!!!
At first, I was flashing nandroid backups between AOKP, CM10 M2, and CM7. Then it got stuck in a boot loop of a different sort (don't remember the details) and before I remembered to come over to XDA, I formatted some partitions under Mounts and Storage in CWM like an idiot. However I did wipe data/factory reset, wipe cache, wipe dalvik cache and still nothing.
I just googled some directions on unlocking from fastboot, flashing CWM, and from there let's see how it goes. Wish I brought a cable with me to work, but it'll have to wait a few hours. Thanks polo!
Click to expand...
Click to collapse
Well if you formatted system and the like, you pretty much wiped your ROM. If you installed a stock ROM, it's possible your recovery was replaced by the stock recovery, otherwise there should be no reason for your recovery to get wiped.
Rooting again with the whole unlocking process and re-installing a ROM will get you back online in no time.
Welp, it looks like I need a little more help if you don't mind polo. For someone who was rooted, I guess I didn't know much, but learned a lot from this so far.
I flashed CWM from my desktop via fastboot and can now get into CWM. I then mounted the phone as a USB drive and loaded CM7.2 and then installed it. "Install from sdcard complete." after that. Rebooted and now it's looping at the boot animation for CM7.2. Wiped data/factory reset and same thing happens.
What am I missing here?
After I'm in CM, I plan on going back to stock + root.
Make sure you also wipe cache and dalvik cache. If this doesn't seem to work, in mounts and storage format cache, data, sdcard and system then reinstall your rom. Be sure you have the correct rom for your phone and not the crespo4g version or vice versa.
I just followed those exact instructions and it still loops at the boot animation. Damn.
The world needs more people like you polo. Thanks for trying to help me through this!! I have a genuine gratitude for you my friend.
OK, run a log cat with Adb. First night I had mine had serious issues, nothing worked same problem.
If you don't know how to do log cat
Is
Adb logcat > log.txt
Same as if fastboot. Upload that and we can find your prob instantly.
Sent from my A100 using Tapatalk 2
das_webos_transformer, I just PMed you the dropbox link since I can't post links here, but I don't see it in my sent. Did you get it?
I would try the factory images from Google. Make sure the phone is working as per usual and then take it from there.
There are guides on how to do so on the forums. It is very easy.
albundy2010 said:
I would try the factory images from Google. Make sure the phone is working as per usual and then take it from there.
There are guides on how to do so on the forums. It is very easy.
Click to expand...
Click to collapse
Hey Al. Thanks for replying. My problem is I'm seeing too many guides. I know it's a mortal sin to ask, but can you link me to one that you think is done correctly? Unfortunately I need a little more hand holding if that ok with you guys.
UPDATE - SOMEhow, I got CM10 installed and gapps. Just flashed it it worked. I did nothing differently than before. I installed a bunch of apps and that went well. I had a feeling I wasn't in the clear and now I can't restore a nandroid backup, a fancy widgets transparent background goes missing but the text remains, and Swype won't install. It's just weird. I'm more than willing to go back to stock now. If you can provide a link for how to flash the stock images, I'll definitely give it a shot. Thank you!!!
You're all over place so here are some general FYI.
Depending on which recovery was used to make the nandroid you may not be able to restore it with a different recovery.
When you say you can't restore a nandroid and a widget or swype won't restore I am lost. What are trying to restore it from and with what.
Anyways. Stock images are here https://developers.google.com/android/nexus/images
Make sure you download the ones for your device. The sprint d720.
Once the download is finished extract the file. You should have a few .img files and a update zip in there. Take those files and move them to the directory you have fastboot in.
With the phone in the bootloader enter the commands.
Fastboot flash bootloader bootloader file name.IMG
Fastboot reboot bootloader
Fastboot flash radio radio image name.IMG
Fastboot reboot boot loader
Fastboot -w update image name.zip
You can most likely skip the reboot 2nd and third reboot bootlaoders . People seem to do it for some reason. If your device already has versions of the bootloader and radio installed you can skip those flashes as well.
Make sure you change the commands to the actual file names you're going to flash. Can manually type/ paste the names or just hit tab after you typed the first letter. Example. Fastboot flash radio r tab. It should auto fill it in. Check anyways.
If you're not comfortable with this dont do it. Read some more or find a video on YouTube if you're unsure. I am not responsible if you screw something up . End result will give you factory up to date bootloader radio and rom. It also wipes the phone but not the internal storage. The bootloader will still be unlocked so you can relfash a custom recovery later and do what you want.
Guides are all over. Just make sure you're flashing the correct files for your device. The commands and procedure is the same for all nexus devices.
And last if the factory images give you issues then there most likely is something actually wrong with the device. Or you managed to screw up flashing.
Thanks Al! I did all that and am pretty comfortable with this stuff, but when time came to flash the image...
C:\Users\Nouri\Desktop\Fastboot>fastboot -w update image image-sojus-jro03r.zip
error: failed to load 'image'
Same issue without the -w. I'm starting to think something is wrong with the phone. But how can it. It's functioning. is it possible that a hardware problem can cause these inconsistent issues?
Issues
- When I had CM10 installed, it ran choppy. It ran fine when I flashed it a few days ago. I didn't do much and flashed another ROM, but I know the S 4G is capable of running CM10 smoothly. Swipes between homescreens were choppy and so was bringing up the app drawer.
-I couldn't take a screenshot. "Screenshot not saved" or something to that effect
-Swype would get to 100% download and then halt for a few minutes. I'd hit Install and it would just stay there for a few minutes and nothing would happen.
-I couldn't restore from a CWM nandroid that I just made.
Internal sdcard faulty maybe?
THANK YOU FOR YOUR HELP!!!!!
Nevermind! Back to stock! Thank you so much Al!!!! Holy crap you have made me a happy man before I sleep tonight dude!
The last step was actually fastboot -w update image.zip, but it's all good!!!!! Thank you ALL!!! XDA is a pretty special place where you guys help someone to the best of your knowledge. I'm going to pass this forward.
Polo, das, Al, I can't thank you guys enough. Know that you guys helped someone out big time here. Hopefully this makes your day better too!
Hey all. I just wanted to send a quick update your way. I successfully went back to 100% stock thanks to Al's awesome directions. Still couldn't install swype and there were some files on the internal storage that had all sorts of strange symbols and were .01 to 5 GB in size! Clearly there is something wrong here. I rebooted and that all went away actually. This morning I rebooted and I see a notification saying "Damaged USB storage - USB storage is damaged. Try reformating" I tapped it and successfully formatted the storage, but that's my issue all along. Wish I left the notification up there, but I'll get it back and take it to Sprint. Hopefully get a replacement.
You guys freakin rule. You helped me until we all, especially I, were blue in the face. Thanks again!!!
If you're going to take it sprint you should probably re lock the bootloader. They may not check or care but eh
Fastboot oem lock.
That doesn't wipe anything
Fastboot oem unlock does and that would be needed if you wanted to root and flash your device again .
Thanks and yup! I got pretty good at this whole thing now. I feel very good now learning fastboot. I flashed completely stock like you said. It worked. Problems arose. Locked the bootloader and tucked the phone away. If it wasn't for Google Voice, my life would suck right now! Hopefully my trip to Sprint turns out well. A few short hours.
Hi guys,
A while ago, I've rooted/unlocked my device in order to install Cyanogenmod, installed PhilZ bootloader. Been running through some versions, never happy with the result - slow response, games not running that well, etc. The last time, I got some new update (can't remember which one though ...) which was the worst nightmare. Without any app running, I thought I was on some Eboda tablet, the cheapest one. Last night I've tried to connect the tablet to my laptop, to put some ebooks on it, without success. Nothing I did convinced the 2 devices to see one another. So, I tried to go back to some previous ROM, boot the device in recovery mode and did a wipe. Forgot that at some point I erased all ROMs from it ... now, I still can't connect to it, so that I can copy some version of ROM, any version, although Windows shows it as installed and connected. Bottom line is that now I got no ROM on the tablet, not installed and also not one that I can install, only got the PhilZ bootloader. Is there any way to get my tablet back or is it bricked ?
You are confusing bootloader and recovery. But as long as you can get to the bootloader *or* to your recovery, it is possible to restore your tablet.
To talk to the bootloader, you need to use fastboot.
To talk to the recovery, you need to use adb.
For more details, read berndblb's comprehensive guide in the General section.
_that said:
You are confusing bootloader and recovery
Click to expand...
Click to collapse
You are right, I have to admit I have not been very thorough the first time I went about this
Thank you very much, I will track down this guide, perhaps I will be able to restore my tablet to some use ...
Hi all,
As it turns out, I had only to push one flashable image (used CM11) and was able to put the tablet back on it's feet. Many thanks to berndblb
Have fun!
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!