Related
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
robboy said:
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
Click to expand...
Click to collapse
1. make a full nandroid backup
2.download the recovery image
3.turn off your phone and turn on by pressing the on button+the back key (to get into bootloader)
4.open a terminal from the folder which contains the recovery image.
5. type 'fastboot boot cm-hero-recovery.img'
6.type 'adb shell mount /sdcard'
7.type 'adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img'
8.type 'adb shell flash_image recovery /sdcard/cm-hero-recovery.img'
now whenever you want to access the recovery console, you just have to switch your phone on+home key and u'll enter.
To install the rom,
9. download the radio and rom from modaco
10. plug in ur usb and mount sd card
11. copy radio into sd card and rename to update.zip.
12. switch off phone and enter recovery console
13.if you never upgraded the phn , then a wipe is necessary
14. then, select update.zip..
15. u repeat the steps from step9 onwards the same way to update the rom.
hope ie helped.
i mentioned nandroid backup as from step 1 itself.
just came to realise that maybe u have never accessed recovery image from pc.
well dont worry, u can ignore step one but be sure to make the backup after step 8 ..... before installing the new rom
cheers and good luck
Okay so number 4 is my problem. Do o do this from the phone or pc?
robboy said:
Okay so number 4 is my problem. Do o do this from the phone or pc?
Click to expand...
Click to collapse
From the pc. A DOS terminal, if you are on windows.
should I allready have partitioned my sd card before i do this?
This is the error message i get
robboy said:
This is the error message i get
Click to expand...
Click to collapse
As far as I can see, you opened the command-line in the system32 dir from youre PC?! You should open the commandline in the dir where the image-file is. Should look like C:\SDK\tools
See this post to guide you further.
http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38
robboy said:
This is the error message i get
Click to expand...
Click to collapse
To open a terminal( command prompt) from a folder,
1.go to accesories in Windows, copy the command prompt.
2. Go to your folder and paste it there.
3.right click on the command prompt, go on prope
rties.
4. U will find a line containing ' start in : %homedrive%%homepath....'
5. Delete that line so that 'start in' remains blank
6. Apply. And u r good to go
By the way. I supposed u already installed HTC sync right.
okay I thought HTC sync might be causing me problems so i removed it
robboy said:
okay I thought HTC sync might be causing me problems so i removed it
Click to expand...
Click to collapse
You will need to install HTC sync cause it contains the drivers for you phone.
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
okay so now when I'm in the bootloader my device connects as a ADB Interface - HTC Bootloader.
BTW I'm on Vista and i selected the driver that was in x86 folder that I was advised to download. However still no device found
robboy said:
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
Click to expand...
Click to collapse
Yes if your device is recognised as adb ... it's good.
That's how it should be.
Try installing HTC sync before plugging ur phone, then enter bootloader on the phn, plug it in, and then perform the command from the prompt.
P.s try entering bootloader first and only afterwards u plug in ur phone
Try to get the latest driver HTC sync from HTC site. If that doesnt work, try downloading the latest sdk plus drivers. U can find it somewhere on the forum . I think that there is a link on the rooting guide by daysee
I'm a total noob at Android too but theunlockr.com was the easiest and fastest way for me to install the custom Modacco ROM. Check out their site; it'll show you step by step with videos :]
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
No-one interested in a tricky problem challenge???
ForeignGadger said:
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
Click to expand...
Click to collapse
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
ForeignGadger said:
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
Click to expand...
Click to collapse
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
animatechnica said:
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
ForeignGadger said:
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
Click to expand...
Click to collapse
Dude i ask this in another forum you posted, did you use odin to install recovery or not? if you did then just boot into recovery and wipe all - then flash galaxytab or any flashable roms that way.
Sent from my GT-P7510 using Tapatalk
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
ForeignGadger said:
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
Click to expand...
Click to collapse
No your second paragraph said you flashed overcome. Not recovery
So if odin is not installing recovery can you boot into fastboot? Power off then press power n volume down then go to fastboot mode and install recovery that way. Check this thread for info. . http://www.galaxytabforums.net/forum/galaxy-tab-10-1-general-discussions/1044-my-galaxy-tab-10-1-wont-power-up.html
Then flash a cwm flashable ROM
Sent from my GT-P7510 using Tapatalk
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
ForeignGadger said:
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
Click to expand...
Click to collapse
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
animatechnica said:
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Funny, when things get really tough, the helpers disappear.
Still no solution.
Oh dear: silence again.
ForeignGadger said:
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
AFAIK you won't get a response in ADB when the tablet is in download mode but you should when the tablet is in CWM recovery mode.
If it were me I'd odin a stock factory recovery to the device and a stock factory rom for it. Then i'd boot into stock recovery and do the factory reset to see if that cleans things up. You should probably link to the source of the files you're downloading as well as provide specific model of your device so people can verify that you're flashing the right files.
I'm totally confused by your steps here
you went to odin mode and used adb? or did you go into fastboot and adb the recovery?
step by step here
a quick overview of it is to get your tab into ODIN mode and use ODIN to reload a copy of the stock image to your tab. This erases all of your previous data but you can reinstall those later. But at least it gets you back to a working tab - Note this is for the 7510 - the wifi tab
1) Download this file - MEGAUPLOAD - The leading online storage and file delivery service
2) extract the file
you should have the following
a file called GT-P7510_USB_Driver_v1_3_2360_0-Escape - this file is the USB driver for your PC, if you don't have the driver installed already, run this
a folder named Odin3 v1.85 - this contains the ODIN executable file
a folder named KME Odin - which contains 2 files - android_fastboot_emmc_full_p4_16G_32G.pit" and a "P7510XABKME_P7510UEKME_HOME.tar"
3) Power down the tab
4) press POWER and Volume Down at the same time until it powers up and you should see 2 logos - USB and triangle (note the retail wifi version might show 2 different logos, android on right and bag on left - left is recovery and right is Odin/download)
5) press volume down to move the selection to the triangle (or the icon on the right)
6) press volume up to lock in selection. You are now in ODIN/download mode
assuming all your drivers are installed to your PC, plug in the tab via the USB to your PC
run the ODIN executable
only Auto-reboot and F.reset Time should be ticked
after a minute, the ID:Com box should turn yellow -if not you may have driver issues (try this driver http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html)
7) tick PDA and click the PDA button and navigate to the KME Odin folder and select "P7510XABKME_P7510UEKME_HOME.tar"
8) select the PIT button and navigate to the KME Odin folder and select the "android_fastboot_emmc_full_p4_16G_32G.pit"
9) Select START
it should start writing the image to your tab and once done, should reboot you back into stock
in case you want to go ahead and flash 3.2 -
use this pit file - http://forum.xda-developers.com/attachment.php?attachmentid=784889&d=1321486916
and use this for the PDA http://hotfile.com/dl/135008863/06c...EKMM_P7510XABKMM_P7510UEKMM.rar.html?expire=1
if it asks you for Password for the 3,2 file use : sampro.pl
when resorting to odin and first booting up, you might get asked for a password, the way around this is to
a) power off,
b) press power n volume down until you get 2 icons left is recovery right is download.
c) press volume down to select recovery icon then volume up to lock it, you should then see the recovery menu
d) then use volume buttons until wipe data/factory reset is highlighted press power to do it
e)after its done wiping, select reboot n you should be ready
Now the key thing here is installing the right drivers - after installing teh driver, connect the tab and see if the drivers are installed - go to your pc control panel and check if you get a triangle with an exclamation point. If there is, right click on it and select update driver, then manually choose device - navigate through and find the Android or samsung device (cant remember the name off the top of my head)
if you get stuck, report on which part you got stuck on - currently it seems like you're mixing and matching different steps so it is a little confusing
ForeignGadger said:
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
Hi again, sorry to confuse you but I was following your suggestions in post #7 of this thread. when I got to step 5 of that post, I got no response from the device: installed PDAnet to get over the driver issue. and no joy.
When trying to install .tar or PIT files I get a big red box, even though the yellow COM box looks good.
When trying the data erase/ factory reset option in the "Download" mode, I get the error message "Can't access to /system/csc/XEU/system.
Steps 7/8/9 in your post above do not work: I have tried them a few times.
Sorry, I have run out of options, and thank you for your help.
A couple of weeks ago I bricked my HTC Inspire with the ACE toolkit. I've spent the last couple of weeks trying to get it back. At some point I just kept getting the HTC white screen and/or bootloader. While I thought I had ClockworkMod recovery in place, I don't. I've tried copying a PD98IMG.zip directly to the SD card. And, HBOOT will read the PD98IMG.zip, it just doesn't seem to apply it.
So this is what I have done so far to fix it:
1. Installed full Android SDK. With some special USB drivers, I am able to get Froyo files fastboot flashall & its says boot & system were both written successfully.
2. When I reboot the phone it starts the HTC Recovery. Its says "This application will set your phone to factory new condition. It is designed for AT&T Branded HTC Inspire only. Using it...blah,blah,blah....Hit OK to continue or Cancel to reboot to recovery?".
3. So I click OK and it says Running "gfree -s on -c CWS_0001"....Please wait. It goes thru this and seems to install OK & says Success GFree has returned your device to s-on and CID: CWS_001. Press OK to copy factory image to your SD card and continue the process..." So I let it do that with an OK.
4. At the end of the Factory Reset install, it says "Success Your device is s-on and a factory RUU has been copied to your SD card. Pressing OK will reboot you to HBOOT where you will be prompted to go ahead with the RUU install. Press vol-up when prompted." When I look in the Android window behind this message it says: "cp: can't stat 'data/rom.zip' no such file or directory. Copying complete".
5. If I hit OK, one of 3 things happens: a.) HBOOT is shown b.) HTC white screen stays on or c.) it tries to do the Factory Reset install once more.
This is where I am stuck.
6. No matter what I have been able to continue getting Android-SDK to talk to it with fastboot commands using the special USB drivers.
I feel like I am just missing something on this.
UPDATE
I am able to connect to the device with Droid Explorer.
Please, if anyone can help, I would appreciate it.
Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.
Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.
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.