Related
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
bur2000 said:
I have a rooted Moto G with CWM Recovery and by stupidity installed the 4.4.4 OTA.
CWM aborts the installation, the phone reboots and unfortunately after the ROM is booted it automatically reboots to once more try and install the OTA.
So what are my options now? When a similar thing happened on my Nexus 7, I just flashed the factory image and all was fine. But I'm not sure what image to use for the Moto G. Is there even an official flashable image? If not, which is closest to stock?
Or is it possible to prevent the phone from automatically rebooting? I can access it with adb and have 10-20 seconds after the boot where I could open some apps.
Click to expand...
Click to collapse
You can find all the stock firmware images here:
http://sbf.droid-developers.org/phone.php?device=14
Flash either with RDS (http://forum.xda-developers.com/showthread.php?t=2637338) or fastboot (http://forum.xda-developers.com/showthread.php?t=2542219)
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
bur2000 said:
Thanks, there's no 4.4.4 for O2 Germany though. Do I need the right carrier/country? Otherwise I'll just go with 4.4.2
I also found this ROM (it's 4.4.4 despire thread titel). Is there any harm in trying it? I did a backup of the current half-broken system.
Click to expand...
Click to collapse
You can flash any firmware you want, except the ones for dual sim version (but if you want to be totally safe flash the retail de image). 4.4.4 images aren't available currently, you have simply to restore the stock 4.4.2, flash the stock recovery and take the OTA update.
The ROM you linked is for Moto G dual sim variant (XT1033), flashing it will probably cause a soft brick.
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
2. How can I flash the rom if the phone keeps doing this?
Any help would be much appreciated. Thank you.
fertchen said:
I have the exact same problem.
1. Is there any way to get the phone out of this loop and get it usable again without a computer?
Click to expand...
Click to collapse
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
2. How can I flash the rom if the phone keeps doing this?
Click to expand...
Click to collapse
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
bur2000 said:
After that no problems.
Click to expand...
Click to collapse
Thank you very much. I will try that when I get home next week. Will be a nice exercise in living without a phone for some time...
bur2000 said:
I would say no. Theoretically it might be possible to quickly do something before the phone reboots.
Just follow the fastboot link in the post by Azarielz. WARNING: If you don't want to loose you user data don't do the mfastboot erase userdata step. For me that still removed the reboot loop while retaining my data and apps. I had some problems with the mobile connection though, only after I manually searched for available carriers and pressed "select automatically" it connected. After that no problems.
Click to expand...
Click to collapse
Just did the same mistake with unlocked & rooted XT1032. I use TWRP and ended up there after every reboot. What I did is use the File Manager under "Advanced" to delete the .zip under /cache. Alternatively you could just wipe cache/ dalvik cache and the update zip should be gone, phone should reboot normally and after app optimization (if you wiped dalvik cache) everything should be back to normal. The first few seconds I got an error when checking for an update, but it went away after a minute.
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
I was in the same situation, with bootloader active from cmd:
mfastboot erase cache
or whatever you use
Any improvement?
Hello everyone,
I had the same problem and had to restore a backup.
But can anyone tell us why this happens? Is Google aware of this and is a fix on the way?
I've seen that the update would fix the annoying incompatibility problem with the class 10 SDCards so I'd like to install this update.
I have seen that some of the improvements would also be :
- coloured tiles in the phone dialer
- ability to pause when you record a video
But I can already do that with my phone right now (I'm in 4.4.3 on a Moto G 4G), is this normal ?
Thank you.
suiller said:
I was in the same situation, with bootloader active from cmd:
Click to expand...
Click to collapse
Thank you very much, suiller. This:
fastboot erase cache
did it for me.
gnayug said:
Not sure if I should go through the trouble of updating to 4.4.4 or wait for Android L that's supposedly coming to the Moto G and X...
Click to expand...
Click to collapse
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
fertchen said:
What would be the easiest/most foolproof way to apply an OTA update when the Moto G is rooted?
Click to expand...
Click to collapse
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me. Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
...Help?
gnayug said:
That's what I want to know as well. XDA has all these devs and freaks and advanced tutorials but nothing at all for the most simple and popular issues for the average user such as applying an OTA with a rooted device. Apparently it's supposed to work with Phil's Flash Recovery, well it didn't, it gave me the same error message that CWM gave me.
Click to expand...
Click to collapse
My guess is that there are just too many versions of phones out there and too many different prerequisites (differences in how the phone was rooted, which apps might have been de-installed, which rom/recovery installed etc) that it is extremely hard and laborious to provide a truly foolproof way. That might be different if there was one standardized manual/tutorial on "Hot to root foolproof and OTA proof for the future" and everyone would follow that precisely.
gnayug said:
Or you're supposed to use "stock recovery", but nobody tells you how to get that in the first place.
Click to expand...
Click to collapse
There is a page that lists all the available stock Moto G Roms in different versions. It would be great if there was such a page for the recovery as well.
If there was a person that decided to take care of all these issues for the Moto G on this forum, he or she could maintain a page with direct links to all the tools, roms and recoveries as well as one general (foolproof) and possibly a handful of alternate ways and fixes.
That is a lot of work, particularly dealing with people who are not willing to read more than one sentence in order to get what they want. And certainly it must be frustrating for a "freak" or dev to encounter us newbies on a daily basis. A 101/primer on what boot/recovery/rom etc is would be helpful - and it does even exist in the wiki. It's that many of us don't find it. That could be changed by a very well thought-out and structured sticky post that provides all the necessary links and knowledge but not too much so that a beginner is frightened by 10 pages of instructions.
But I am certain that a person would be willing to do that if this forum allows it (which I assume is the case). Maybe this person has not been identified yet. Or maybe we have just missed it. I know I will not be this person simply because it would take me a lot of time to gather the necessary knowledge for such a position and right now I have other priorities and I usually use my phone once every 10 days or so.
I am aware that as a user I am not entitled to anyone providing this service. At the same time I am pretty sure that there is someone, maybe even within this great community, who would be willing to do it.
By the way, here is how I ultimately fixed the rooted-Moto G-OTA-update-problem: http://forum.xda-developers.com/moto-g/help/how-to-update-rooted-moto-g-t2828857/post54528345
Thank you for the link and everything you wrote! I was actually thinking the same the last few days... If only I was qualified enough or had the time to gather and polish all the information. I realize I shouldn't have written "Freaks". They're hard-working, skilled individuals that provide us with all this amazing software for us to use free of charge. I just wish they'd put some effort into explaining and laying out the basics etc. for all the "newbs" they encounter each day, because what good do their stuff do when nobody knows how to use it? All those devs that put out kernels and ROMs and then make a thread with changelogs and download links WITHOUT actually saying what they contain and why anyone should use them - I'm looking at you.
I'll go try to get my Moto G to 4.4.4 without losing my stuff using your link now, thanks again!:good:
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
yahboyvictorr said:
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
Click to expand...
Click to collapse
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Jkay7 said:
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Click to expand...
Click to collapse
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
yahboyvictorr said:
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
Click to expand...
Click to collapse
Yes it is definitely a reason. Follow the steps from the guide I linked you step by step, it works 100%
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!
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk