Related
Okay guys here's the dealio-
I recently got my transformer prime and I *loved* it. It came pre-loaded with the .21 version of ICS, which can't be rooted as of now so I downgraded to stock .15 with a modified ViperMod and then rooted and installed CWM. Next, I installed the Gummy custom ROM onto my prime (still .15). Well, I started to experience some weird -probably ROM related- issues and I ended up deciding to flash back to stock. ...BIG MISTAKE on my part I found out! I used the modified ViperMod to flash back to the stock .15 and it ran through the process but stopped at the ASUS boot logo with the little loading circle going around and around and around. First I let it sit for a VERY long time-stuck on boot. Then, I tried turning it off and back on-stuck on boot. Next, I tried pushing down the little recovery button-stuck on boot. I tried booting into CWM, but obviously, since I flashed back to the stock .15, all I get is the android guy laying in his side with the red triangle.
I am really really hoping that this is not a hard brick because the error that people are describing is the tablet stuck in the screen with "EeePad" in the middle and then getting something about an "unrecoverable bootloader error". My tablet boots past the EeePad screen and there is no error message-just the endless loading circle.
I am hoping that one of you smart guys could have a clue on how to revive my tablet. Any help would be greatly appreciated, and maybe I can buy you a beer if you bring my baby back to life
Here is a picture of what it looks like (circle is still spinning):
http://img838.imageshack.us/img838/276/img20120322182429.jpg
so you can get into recovery? I saw you said you tried to flash cm9 again. if you caught in a bootloop, jemaine made a zip file you can flash to get you out of it. you have to search for it though in developement section. does your computer still recognize your prime when you hook it up to your computer? you may need to adb commands into prime.
good luck getting it back running.
demandarin said:
so you can get into recovery? I saw you said you tried to flash cm9 again. if you caught in a bootloop, jemaine made a zip file you can flash to get you out of it. you have to search for it though in developement section. does your computer still recognize your prime when you hook it up to your computer? you may need to adb commands into prime.
good luck getting it back running.
Click to expand...
Click to collapse
I no longer have cwm installed, it is just the stock recovery so I cannot install any .zip's. Also, when I plug the tablet in wile its on the Asus loading screen, the computer DOES recognize it. Maybe there is some way to get into it and reflash?
Any suggestions guys?
seanyuan62 said:
Any suggestions guys?
Click to expand...
Click to collapse
When you say your pc can see the prime can you see it with adb? If not go here:
http://forum.xda-developers.com/showthread.php?t=1426502
Once you have adb figured out you should be able to reflash recovery. See this thread:
http://forum.xda-developers.com/showthread.php?t=1576937
I used method 2. You will need to push the blob file to your prime using adb. Hope that helps.
Won't turn off and stuck on Boot screen PANIC!!!!
I'm running CM9 nightlies on my 64gb TF201 and have had no issues with it. I'm using GooManger and Teamwin for recovery and have not had any issues in that department either. Until now.
So 2 days ago a nightly was released that I flashed with out issues. The updated ROM however wanted to open the virtual keyboard when I started typing so I decided to revert back. I did this by just flashing an earlier released nightly. It went through the process and then restarted. The boot screen came on and then never left. If I try and turn it off it just restarts. I can't get it into recovery but I can get into fastboot. However I don't have a little Android symbol just the wipe data and USB. I don't have a backup on my computer that I can push through. I flashed CWM recovery through fastboot in hopes of then being able to get into recovery but with no luck. I used transformerprimerecovery.zip followed all the instructions got an "OK" and "finished" on CMD. At the same time the little progress bar on the TF showed that it did something but no change with my condition.
When I'm connected with fastboot it doesn't show up on my computer as I found to be expected. In device manager Android Phone is listed and when I click on it ASUS Android Bootloader Interface shows up stating device is working properly. If I open CMD and type "cd" it just replies C:\users\Josh>. I tried to wipe data to see if it would and it said it did but still no change. I've been reading for the past two days and haven't found the same set of problems yet. I've found similar issues but not all together.
Please if anybody has a suggestion for me I would be most Thankful. I've not had any luck with my searches
Thanks
Lifewithsuzy, try this, it's what I did when I screwed up my tablet, and it's helped a few others.
geo.z said:
Lifewithsuzy, try this, it's what I did when I screwed up my tablet, and it's helped a few others.
Click to expand...
Click to collapse
I haven't been able to try this yet for I seem to be having ADB issues. SDK is updated and current and I have the latest universal driver setup. I show up in device manager but not in the CMD prompt.
---------- Post added at 08:10 AM ---------- Previous post was at 07:44 AM ----------
I seem to be falling further down the rabbit hole. I mentioned above that I was able to flash CWM recovery via fastboot was not able to access it. I tried the same process with TeamWin recovery. It just stated that the specified path could not be found. So I'm losing features now.
lifewithsuzy said:
I haven't been able to try this yet for I seem to be having ADB issues. SDK is updated and current and I have the latest universal driver setup. I show up in device manager but not in the CMD prompt.
---------- Post added at 08:10 AM ---------- Previous post was at 07:44 AM ----------
I seem to be falling further down the rabbit hole. I mentioned above that I was able to flash CWM recovery via fastboot was not able to access it. I tried the same process with TeamWin recovery. It just stated that the specified path could not be found. So I'm losing features now.
Click to expand...
Click to collapse
When you are trying to flash anything in adb or in fastboot, put the file in the same folder as those .exe files. Manytimes it is a typing mistake on the path that kills you. Also remember to add the.zip at the end of the file name if applicable.
Gage_Hero said:
When you are trying to flash anything in adb or in fastboot, put the file in the same folder as those .exe files. Manytimes it is a typing mistake on the path that kills you. Also remember to add the.zip at the end of the file name if applicable.
Click to expand...
Click to collapse
No luck. I've tried rearranging all the files associated with adb and fastboot I can think of. I've opened the CMD window from about every file as well as from the start menu and I can't get CMD prompt to recognize the tablet. The tablet allows me to get to the point where it states that it is "starting fastboot USB download protocol". Device manager shows Android Phone > ASUS Android Bootloader Interface. And when I remove the device it shows it listed as "fastboot device". I'm stumped on getting into CMD and can't do anything until I do. It just stays on the boot screen until I force it off. And if I'm not holding down the volume up button when I do it, it just recycles on. I've found post regarding the boot screen locked on but everybody has been able to fix it through a properly functioning fastboot/ADB.
lifewithsuzy said:
No luck. I've tried rearranging all the files associated with adb and fastboot I can think of. I've opened the CMD window from about every file as well as from the start menu and I can't get CMD prompt to recognize the tablet. The tablet allows me to get to the point where it states that it is "starting fastboot USB download protocol". Device manager shows Android Phone > ASUS Android Bootloader Interface. And when I remove the device it shows it listed as "fastboot device". I'm stumped on getting into CMD and can't do anything until I do. It just stays on the boot screen until I force it off. And if I'm not holding down the volume up button when I do it, it just recycles on. I've found post regarding the boot screen locked on but everybody has been able to fix it through a properly functioning fastboot/ADB.
Click to expand...
Click to collapse
The command window should be opened from the same window (folder) you have adb.exe or fastboot.exe in otherwise it isn't going to work unless you have the exact path which is easy to kame a mistake on. I would try the following:
If your not on twrp I would fastboot install it first.
Install universal naked driver
Download and unzip nvflash file
In the folder window where adb.exe is, press and hold shift, and right click and select open command prompt here.
Now do adb devices
You should see you device
put you rom in the same folder and push it to the table
reboot to recovery and install
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Oh, and it'll run ICS
...or at least boot it! (can't yet post links)
youtube.com/watch?v=dUmuQULyrAk
You can Fastboot the device and only botched the system image correct? Well, in theory all you need to do is boot ClockworkMod Recovery through Fastboot and restore a dump someone has already done. I think their is one in the Dev Forum already.
ThisIsDave said:
So yes, I tried to flash a different system.img, and am currently bricked, but would like to share some helpful info:
Google's Nexus telephone support will not supply factory image locations
They will also not comment on whether some sort of "internet recovery" (using Ethernet) exists such.
Fastboot can be manually entered by powering up with a palm ove the device, waiting for the red flashing to begin, and once it does, immediately removing your palm. I struggled with this for a little while (as I couldn't connect over adb/fastboot) and am at least in a state now where I could restore the device.
I hope this info's helpful... and if it is, please help me out with some factory image sources over in my "Factory Images?" thread!
Click to expand...
Click to collapse
Thanks for the info, saved me at least 3 or 4 times after soft bricking my Q. One thing that I found to help is while the device is bricked type in command prompt: adb reboot-bootloader ... this will generate a waiting for device tag then once you see that unplug the Nexus Q and plug it in, within one second as soon as you see a hint of blue on the mute button put your palm over it and it typically boots right into fastboot mode. If not just unplug and repete until it goes.
FYI: Also if you try to launch clockwork from an apk and instal a rom you will almost most definitely soft brick it (tried to sideload AOSP JB ROM and some others with no luck).
I'm trying to root my sons phone because of the stupid SD card issues and lack of internal storage. I searched high and low (I thought?) both here and via Google searches but couldn't find anything specific for this firmware version. I am a bit of a noob to this rooting thing, though, so maybe that's it... I tried using this guide here but it didn't work. I'd click restore but the phone would never reboot. It would just briefly say "restore started" then "restore ended" and that would be it. Is there a guide anywhere specific to this firmware? I know it's fairly new-ish. He's using JB 4.1.2, if that makes a difference. Thanks in advance for your assistance.
IntoxicatingToxin said:
I'm trying to root my sons phone because of the stupid SD card issues and lack of internal storage. I searched high and low (I thought?) both here and via Google searches but couldn't find anything specific for this firmware version. I am a bit of a noob to this rooting thing, though, so maybe that's it... I tried using this guide here but it didn't work. I'd click restore but the phone would never reboot. It would just briefly say "restore started" then "restore ended" and that would be it. Is there a guide anywhere specific to this firmware? I know it's fairly new-ish. He's using JB 4.1.2, if that makes a difference. Thanks in advance for your assistance.
Click to expand...
Click to collapse
You should search for "root" in L9 General or FAQ forum, http://forum.xda-developers.com/showthread.php?t=2511695
What worked for me
What is required:
-Phone drivers
-Fastboot (You'll find it in fastboot drivers directorium) and adb
-Fastboot drivers
-Recovery.img (I'd recommend cwm touch, because on my phone twrp has issueswith restoring backups)
-Zip that will root your phone (copyed to external SD card)
Instructions:
1. Install mobile phone drivers
2. Install fastboot drivers
3. Extract ADB
4. In terminal type adb devices to check if your phone is recognised as adb device
5. Type adb oem-unlock (terminal)
==================
Phone reboots to bootloader
==================
6. Read whats on screen
7. If you want to unlock bootloader push vol+
=================
If everything worked as it was supposed, phone will be recognised as fastboot device
=================
8. Type fastboot devices to check if phone is recognised propperly
9. Type fastboot flash (boot) recovery "path_to_your_recovery.img" (flash if you want to change your recovery with cwm/twrp, and boot if you just want to use custom recovery this time)
9.1. Turn off your phone and boot to recovery by holding vol+ home and power, when phone vibrates release just the power button, when you see logo of cwm/twrp release everything*
10. Flash the .zip
11. Reboot phone
*Skip this step if you used boot instead of flash
**All credits go to Cmahendra for submiting the guide
Thanks guys! That second one worked like a charm. I thought I'd searched properly but I guess not.
was it difficult? im not really savy at this .
IntoxicatingToxin said:
Thanks guys! That second one worked like a charm. I thought I'd searched properly but I guess not.
Click to expand...
Click to collapse
Ive been trying to root with frama lpwn.apk one click and zero results. Beginning to lose hope
mikeylee26 said:
Ive been trying to root with frama lpwn.apk one click and zero results. Beginning to lose hope
Click to expand...
Click to collapse
Was easy as pie, actually! I'm pretty new to this too, just follow the instructions exactly. In order to install the phone drives on my PC, all I did was plug my phone into the computer via USB and it prompted all the installations I needed.
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Download mfastboot and redownload the recovery img
hetor99 said:
Download mfastboot and redownload the recovery img
Click to expand...
Click to collapse
Thanks.
Decided to install it on my desktop. While trying various files, my laptop accidentally got hit with Chromium virus. It looked like all required files were there, but kept having problems with a couple of those sdk files (tools/platform tools).
I'm still getting the following error:
( bootloader) has-slot :recovery: not found
And once again the Android SDK Tools and Android SKD Platform-tools that are under Tools (preview channel) are unchecked. Not sure if they are needed.
Follow the instructions of how to install on the general section
hetor99 said:
Follow the instructions of how to install on the general section
Click to expand...
Click to collapse
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
L8Show said:
thanks lol.
I believe I have downloaded and installed/reinstalled everything 2 or 3 times. I have followed the guide here while reading and watching the video. I googled for other guides to fill in any information I didn't understand or see clearly. That was before I made this thread. I was hoping there might be something that is commonly overlooked. Phone seems to be ready, so I am assuming it's on the pc side. I read there is a way to do it with just the phone, but I'll try one more time on my laptop since that's what I have to work on today.
Click to expand...
Click to collapse
How to Install TWRP Recovery and Root MOTO E
https://www.youtube.com/watch?v=9Jh-O2LGL3Y
OK, it is done.
Took a couple days with several hours of clicking, and checking settings, and reading and researching, and watching videos, and downloading, and installing/uninstalling, and restarting, but it's now rooted! Way too much time wasted even though it was raining and the gf and I were just watching movies for a lot of it. She kept asking me why I'd waste so much time and remind me I had a perfectly fine iphone nearby. Today I finally got to the point where I had given up. I figured something was screwed up with the phone after that reset on my computer.
Some highlights that may or may not be helpful for the next moto e rooter:
USB debugging was somehow switched to off a few times after I turned it on. Might have been after resetting phone, but who knows exactly.
I set screen to stay while connected via USB.
I removed all the apps I could and took out the sd card.
Kingoroot stuck at 66% many, many times, and then phone would restart. Research showed it may be accessing the wrong ADB instance or something. So I uninstalled SDK, fastboot, Minimal, etc. Anywhere it could have been hiding. Even did a system restore to last week the day I reinstalled windows. Didn't help one bit. Which is to also say... there are a half dozen or more legit options. Try different ones if you are relatively confident you followed directions the 1st 10 times.
Ministro didn't have moto e in their data base.
Finally back to XDA after checking a dozen videos (I have to admit I was completely dumbfounded and was mad at the whole process). I found XDA Kingroot and right away it worked, but it needed permission to allow apps that were not certified or some thing. I can see how people would think this is so easy. If I had started with this, I'd never have had to ask for help here. Btw, was this my problem all along? Did I miss that in the instructions or was it something else possibly? I don't remember if I did that before since it was 3 days ago.
So far I am thoroughly impressed with the this moto e. I paid $40 for it on a whim and now that I can remove a bunch of bloatware and customize it a bit, I think it may be a good gateway into android devices.
Thanks for looking and all your suggestions.
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
faheyd said:
I've been in the same boat for weeks, thank you. I thought I had already tried KingRoot, but must have not, as it's working now and I have root and twrp installed, http://www.kingroot.net/ . Thanks again !
XT-1526 Sprint Prepaid Moto E 2nd gen.
Click to expand...
Click to collapse
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
L8Show said:
Glad it helped.
So I decided that I try and get TWRP to run on this phone. After researching, I followed a guide using stock firmware and a modified batch file. Phone is working, but wifi/4G/data isn't. I did all the basic trouble shooting and nothing works so I decided to just try install TWRP/supersu. The problem is that ADB isn't working again. It works when phone is on and shows up in adb devices, but not boot mode. Fastboot shows the device. But ADB doesn't show the device while in boot mode and it's not working.
I updated the drivers in the device manager.
I tried minimal fastboot and 15 second adb.
Reinstalled motorola drivers.
Anyone have any ideas?
Thx!
Click to expand...
Click to collapse
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
-z3r0- said:
First of all adb doesn't work in fastboot mode. It only works when the phone is up and running.
Try
fastboot devices
If it shows up your device's serial no. then you're good to go, everything's working fine.
I didn't got what's you're exact problem is. Pardon me
Will you explain what you did before your wifi stopped working.
Click to expand...
Click to collapse
Thanks for that information. I thought I saw adb devices command working in fastboot mode in one of the videos so I thought that was the problem. I thought adb needed to root the phone.
In order of what I've done with the phone so far:
Sent/got codes and unlocked moto e.
Turned on developer options and USB debugging.
Was then unable to get TWRP or the other cw something to work using the command fastboot flash recovery (file name) or fastboot boot... commands.
Gave up and installed Kingroot and everything worked fine.
Decided to try to install TWRP and superSU since kingroot had worked. I read that the phone needed to be flashed back to stock to do this and watched/read a couple of guides. http://forum.xda-developers.com/showthread.php?t=2759495
I used the following named file:
SURNIA_ACG_LTE_5.1_LPI23.29-30_cid9_subsidy-DEFAULT_CFC
The phone was changed back, but data doesn't work. I can't access wifi because as soon as I switch it on, it switches back off. 4G, etc is not working either. So after trying to figure that out I decided to just proceed and put TWRP/superSU on the phone.
I powered off the phone. Powered into fastboot mode connected the phone to my computer.
I opened Minimal fastboot folder and shift/right click to bring up the command prompt.
In the command promt i typed fastboot devices and it shows my phone.
I then type fastboot flash recovery (file name or renamed to recovery or renamed to TWRP or I click the actual file and drag it to the command prompt) and then hit enter.
It says it's doing stuff in so many seconds, but after nothing happens. The phone doesn't reset like some of the videos. If I reset it, it powers on, but not into the TWRP screen.
After that I did more reading and found out that adb doesn't always play nice with windows 8.1 and that you might need to force other drivers to make it work right. I did this next and was going to try all the available options from universal naked driver later, but there were no motorola drivers.
Then I came here and learned something new. ADB devices command doesn't work when the phone is in fastboot mode so that has no effect on installing twrp...
Right now I am considering trying to install the other stock files I have access to:
SURNIA_ACG_LTE_5.1_LPI23.29-20_cid9_subsidy-DEFAULT_CFC (20 instead of 30).
After that I am out of ideas if it's not the adb problem. Might kingroot again and go from there.
Ok after researching, it seems that LTE file may not work on sprint and there was success using the boost file from
http://www.filefactory.com/file/6be...XI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml.zip
(2 hour dl make that 5+ lol)
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'll try that next to get the wifi working and then figure out why it won't root.
Thx!
L8Show said:
Edit: I'm running Windows 8.1 and that is probably the problem. I need find some universal drivers that work for win8.1 with the moto e.
Hi,
I decided to try to root a recently acquired Moto E (XT1526/5.1) and got it unlocked easily enough by following directions online. I have downloaded the motorola usb drivers, TWRP, Android SDK, SuperSU, and tried different versions.
After following the unlock guide, it says DEVICE IS UNLOCKED. STATUS: CODE 3
I open the command prompt in platform-tools and enter fastboot flash recovery recovery.img (file was renamed), and it shows it's sending recovery OK, writing recovery OK, and finished.
After that things don't progress, and there are options that I can scroll through:
Restart Bootloader...
Power off...
Factory Mode - resets it to fac settings I think
Bar Codes...
BP Tools?
QCOM?
Bootloader Logs...
Start - does the warning that it's unlocked and then starts the phone.
Reocvery Mode - flashes the unlocked warning and nothing else. It goes back to fastboot flash screen.
Guides show it going to TWRP screen after running the command prompt, and then options to load up files.
Am I missing something?
TIA
Click to expand...
Click to collapse
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
rakeshwipr said:
Copy the twrp file in the sdk root file(right click the desktop icon and open file loaction ) and rename it as recovery
next step on that folder press shift button and right click and choose option open command window here. and type follwiong command without quotes and press enter "fastboot flash recovery recovery.img" this will flash the twrp onto ur moto e
Click to expand...
Click to collapse
and open the command prompt with admin rights
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
d
Thanks! The devices shows up when on as ADB and in fastboot too. I had to take a break when the kernel download took 8 hours, but I think I got the file that will work to fix the wifi issue. I can't mess with it til I get home tomorrow, but I will read and follow all advice.
For the previous poster, I did do the admin rights and did rename TWRP file to recovery... I aslo tried many other combinations, but will keep it in mind for all further attempts.
Appreciate the help so far. I almost left it with the kingroot, but it was bugging me that I couldn't get it to go. Hopefully I'll have good new tomorrow.
-z3r0- said:
Okay dude first of all get rid of those videos (no offense to youtubers).
Check if your device shows up in adb devices. (When phone is on)
Check if your device shows up in fastboot devices (When phone is in fastboot mode)
If both of them shows positive then your setup is fine. Now move on to next part.
Get the right stock image for your device.
Go to your about phone in settings and match with your build/build number. (or give me a screenshot of your about phone and I'll find it for you)
Avoid using any kind of batch file(If you don't know what's there inside) and try to flash manually one by one.
After that flash your twrp recovery.
When this is completed use volume buttons on your phone to get to "Recovery" options in fastboot mode then press power button to boot into recovery.
You'll successfully boot into recovery then from there flash SuperSU. Avoid using kingroot.
The reason your wifi/data stopped working is because of the wrong boot.img(kernel). Since you've flashed the boot.img of same phone but different variant, you were able to turn on your phone. If it had any wrong boot.img your phone wouldn't have turned on anyway.
Click to expand...
Click to collapse
Device shows up in both instances.
It's stock now and the wifi works. Flashed it back to stock by following Mdkcheatz guide here:
http://forum.xda-developers.com/moto-e-2015/help/sprint-backup-moto-e-2nd-xt1526-cdma-t3099670
I'm stuck where I was when I first started this thread. I've set my account up as administrator. Developer is enabled and so is USB debugging. I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
I confirmed the connection:
fastboot devices
I try to flash it with the:
fastboot flash recovery recovery.img
It says:
target reported max download size of 268435456 bytes
sending 'recovery' (6928 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.359s]
finished total time: 0.578s
C: |Program Files (x86)\Minial ADB and Fastboot>
I'm running windows 8.1 (64 bit). I read that some people had had problems with windows 8. Kingroot worked through the app store. It has been flashed with various stock kernels and that usually takes a few minutes so I don't think it's doing much in half a second. I'll research a bit more, but I think it just a bad combination of this version phone and windows 8.1.
I started the phone after this last attempt. Are there any files in internal storage that I should look for?
L8Show said:
I downloaded 2 different TWRP Condor files (3.0 and 2.7). I tried both and renamed them recovery just in case.
Click to expand...
Click to collapse
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
-z3r0- said:
Flashed the wrong recovery dude. You're flashing twrp of condor.
Here's this might work for you : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
After done flashing. Open recovery mode and flash SuperSU.
Also I don't think there's any problem with windows 8.1
As long as you're opening cmd with admin rights and adb/fastboot commands are working for you everything's fine.
Click to expand...
Click to collapse
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
L8Show said:
Just in time for Easter! You are correct. TYVM! I'm in TWRP and have to see about read only option again (read about it a week ago, I think it said to leave initially). SuperSU is next and then off to the races.
Click to expand...
Click to collapse
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
-z3r0- said:
Be sure to flash the latest SuperSU (the systemless one).
Here's the direct link:
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
I am on v2.65. Should I use this version? I checked root and it's rooted, but I needed to use no bloat app (instead of free titanium) to remove some apps. Is that normal? I thought once rooted and set up, I would have complete control. Some apps seem very invasive so I haven't grabbed many yet. I have some questions about apps, etc., but will probably research and ask in another forum if needed.
Thx again for all the help and pointing out my mistake.
could anyone help with a seemingly bricked tab speed 6, attempted to root using kingoroot and it failed causing connection issues to google so i was unable to add a account, after hard reset and booting in to recovery i have wiped the cache and reset to factory, however now the tablet is stuck on checking connection and doesn't go any further with or without sim card.
after searching and searching i have come up with nothing apart from this threadhttp://forum.xda-developers.com/general/xda-assist/stock-rom-vodafone-speed-tab-6-vf-1397-t3329343
it looks as though he is having the same problem.
assuming kingoroot has corrupted the rom and i need to reflash to repair it,
i don't know if it is a generic tablet it appears to be made by alcatel but im unsure.
i also do not know if i could use a firmware from another device or even custom rom, anything will do as long as it doesn't end up in the bin
i also have another which hasnt been messed with and was wondering if it would be possible to back up the rom from it and reflash it to the bricked one, if so could anyone steer me in the right direction
could anyone help me locate as rom and flashing tool that will help
thanks in advance, apologies if this is posted in the wrong place.
You said you had a second one, you don't have to root it, just follow this tutorial and hopefully you should be good to go.
no bootloader
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
inexperience
thanks for the help I am quiet inexperienced but determined so any help pointing me in the right direction would help thanks
facerolla said:
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
Click to expand...
Click to collapse
What command do you do to tell adb to reboot to download? What command to you give fastboot to flash the recovery?
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
I don't know if download mode is accessed differently I've found this post that seems to Suggest hold volume up and down then connect until battery charging appears http://forum.gsmhosting.com/vbb/f272/vf-1397-a-2047715/ this is for unlocking it seems, but don't seam to be able to get it to work, earlier I removed root with kingoroot from kingoroot app, also to no avail and rooted again both root removal and rooting were successful but still tablet stays on the checking connection screen when rebooted, I was hoping the removal may of fixed the issue but no...., I was thinking if I could get back custom recovery on it I could do the same to the working one I have begrudgingly so I could back up the working ones rom and use it to flash the bricked one, but I don't really want to risk bricking that one either, but was considering finding another rom from another model the same chipset and flash it with that but obviously no download mode means I can't do it..
if it's any help The recovery mode states android system recovery <3e>
LMY47V release keys
reboot system now
wipe data/factory reset
wipe cache partition
power down
enable adb
they are the only options,
again thanks for all your time and effort
facerolla said:
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
Click to expand...
Click to collapse
You can't always unlock the bootloader via that command and you'll need to have the bootloader unlocked to flash a custom recovery, if you can find stock images on the web you can flash them via fastboot.
---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------
Also to restore an adb backup you do "adb restore filename".
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
facerolla said:
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
Click to expand...
Click to collapse
Hello! Remember this?
Also to restore an adb backup you do "adb restore filename".
Click to expand...
Click to collapse
Did it work? I see you left a "thanks" so I assume something happened.
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
facerolla said:
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
Click to expand...
Click to collapse
I have a couple tricks up my sleeve and that is, you know how you said when you ran adb reboot bootloader? Run adb shell instead and it should give you a command explorer, from there, type "su" and report results, you should see either a root request on the device or a hash sign in the coommand shell.
Just a quick question
Did you ever manage to get it working if so how did you go about doing it as i attempted to install a custom boot animation and it appears to be stuck in a constant boot loop as such i'm not really sure what to do with it or if it is savable. Any response would be helpful. Thanks.