Related
So I have looked at post about installing adk.. I've manually set it up, I've used a repository to setup, I've did the 'idiot proof SoupKit'..... no matter what I try the same thing happens.
I can run 'adb devices' and get a list of the android devices connected via USB. I see them just fine. My udev setup works, the adb commands works.. I have done this by manually installing from Google the latest adk, installing binaries. I can always get adb to see the devices.
When I run 'fastboot devices', it just returns without listing devices at all. Any other fastboot commands simply say < waiting on device > and nothing happens.
Why would adb work and fastboot not?
I have tried this HTC Incredible 1, HTC Incredible 2, and ASUS TF300T tablet...
Any help/advice would be appreciated.
John
A little knowledge goes a long way
Sorry to answer my own question in the forum, but I did not find an answer which I understood... Now I understand what I should have been doing. For the next folk like me:
adb - can communicate with your android device while it is running and has USB debug mode enabled. For ICS this USB debug option was under the developer settings. You can tell adb is communicating properly by running the command 'adb devices' and seeing your device show up in the output list.
fastboot - can communicate with your android device when it has been booted into 'fastboot' mode, not while booted normally form a system image. Running the command 'fastboot devices' when your USB is connected to a device booted into 'fastboot mode' will show a device if it is communicating properly.
From my browsing of many other messages, I did not see clearly articulated the need to BOOT into fastboot mode on the device. Maybe I'm just simple minded.
On my TF300T tablet, I got into fastboot mode by powering it off, and then starting it while holding down the down volume button and the power button at the same time. This brought me to a screen which I could use the volume down button to toggle between three modes, 1) erase data partition 2) fastboot mode (found it!) or 3) normal boot. I used the down volume key to move the selection to fastboot and then the up volume key to select fastboot. It then launched into 'fastboot' mode, awaiting fastboot commands.
Once my device was booted to 'fastboot mode', the latest fastboot executable from google worked. The downloaed exectuable from SoupKit and the downloaded version I found for Windows did not. From my experience, download the latest ADK from Google and use the platform-tools version of fastboot.
I certainly hope this detail helps the next poor soul who googles and read things they don't fulling understand.
P.S. This all start when my ASUS device would not update with the OTA update and after several days of really useless interaction with their support, I decided to take matters into my own hands. You have to love Android which lets you learn and grow without the specific task master of a bad support division.
I've read a couple dozen of the pages from http://forum.xda-developers.com/showthread.php?t=1905674&page=95 titled
Nabi2 root and Gapps install
Click to expand...
Click to collapse
.
Using Win7 x64. Nabi2 version: 1.9.37 recently updated.
Can't post to above thread because this is my first post (restricted to "General" forums).
In "Jmz Nabi Recovery Installer" window it is always stuck in the "If stuck here drivers are not installed" step.
Prior to installing "PdaNet for Android" from http://junefabrics.com/index.php,
I had 2 devices in Control Panel under "Other devices" with a yellow '!'. One of the looked like the Nabi device. The other is named "MTP".
After installing PdaNet, only MTP remains with the yellow exclamation point.
What should the Nabi look like in the Control Panel if its properly configured with a driver and where would it be?
And what is MTP?
Apparently I'm still having a driver/connection problem from adb.
USB Debugging is on in the Nabi.
Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
fastboot devices
It should return a value (fastboot working and drivers are installed)
Let me know how it goes.
Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
Click to expand...
Click to collapse
Part of this command is missing right? Without input parms it just outputs the "uses" message.
fastboot devices
Click to expand...
Click to collapse
Unfortunately this returned nothing for me.
I'm glad you responded. Other suggestions?
Here is how i done it using Windows 8 x64
I done 3 nabi2's this way but had a lot of trouble first so here is what worked for me:
Sadly, i don't have any nabi2 with me now to explain exactly how i done it
1) First boot the Nabi2 normally and turn off usb debugging.
2) When fully booted connect USB cable.
3) Check device manager and drivers should be installed.
4) Unplug USB cable and turn on USB Debugging and Unknown Sources.
5) Reconnect USB Cable.
6) Drivers should install.
7) Install PDA Net on Laptop/PC
8) Select Samsung device from option screen when installing.
9) Wait for install to complete and drivers to install
10) Shut down Nabi2
11) Boot Nabi in fastboot (Hold + and Power buttons)
12) Select fastboot protocol
13) Here i seen Windows 8 take about 60 seconds installing fastboot drivers
To make sure fastboot drivers are installed i went to this thread
Code:
http://forum.xda-developers.com/showthread.php?t=1590800
and download ADB (save it to C:\SDK\platform-tools) and read over the helpful instructions in the thread.
Open command Prompt
Type the following (shown in RED) in the CMD window the opened:
cd\
cd C:\SDK\platform-tools
adb.exe (a list of options should be listed)
fastboot devices (it should list a number after you enter this)
If number displayed then you are good to go.
Reboot Nabi2 and wait to complete
Go to the location you saved jmzrootpackage
Go to files folder inside jmzrootpackage
Double click install.bat
Follow on screen prompts ( I took option 1)
TWRP recovery installs
I had trouble installing GAPPS.zip with an error being displayed about unable to mount /data
I copied GAPPS.zip to a SD Card and inserted to Nabi2
i install zip from EXT-SD Card even though it gives a load of errors about not able to mount /data
Wipe Cache/Dalvik
Reboot Nabi2
Go to daddy/mommy mode and you should have Google Apps installed.
Any problems let me know.
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
After looking at Victoria Antonio's youtube of this process I'm convinced the driver install is still not correct.
Somehow it gets mucked up when I use PdaNet. Not sure how or why.
To make this picture clearer I posted some screen shots on my website: http <colon, 2 forward slashes>skippyvondrake.com
I hope someone can tell me how to unmuck what I've mucked.
skippyV said:
Selected "Continue", and entered(<Vol+>).)
Click to expand...
Click to collapse
Don't press Continue on the Nabi after selecting fastboot protocol
After selecting fastboot protocol leave it.
skippyV said:
> fastboot.exe devices
Click to expand...
Click to collapse
The command is:
fastboot devices
not
fastboot.exe devices
Thanks for telling me about when I'm in fastboot mode.
I DO get a device number when in fastboot mode and from 'fastboot devices'
But adb still cannot "see" the device. All commands using adb result in:
error: device not found
Regardless of what mode the Nabi is in.
SOLVED
I finally decided to try this with a different computer. Same OS and architecture.
But this computer didn't have various android development "kits" installed previously.
And it worked without a hitch.
The youtube by Victoria Antonio pointed out a few nuances I didn't know.
And you helped too, BBKGTTDi, so giving you "thank you" points.
Chow!
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
BBKGTTDi said:
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
Click to expand...
Click to collapse
When I get there - if I figure it out - I'll send you a private email sense that would be a different "thread'. There are other nuances I've noticed too...
show game in Nabi mode after rooting
@BBKGTTDi, I thought there would be a way to send private messages/emails on this forum - but I don't see it.
I ran into the same problem after rooting the Nabi. The "Add Apps" app doesn't work as its supposed to.
It worked prior to rooting.
It does list the newly installed apps, but selecting them for Nabi-Mode, rebooting, and they aren't there.
Only visible in Mommy/Daddy mode.
So if you figure it out please let me know!
The "Add Apps" app is working correctly now. Don't know what happened before.
I must be getting "Nabi-ed out".
Let me know if you're still having troubles.
skippyV said:
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
Click to expand...
Click to collapse
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
arvati said:
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
Click to expand...
Click to collapse
I did have those problems last year. Still think they were driver related.
I use mehtuus's package now. He has a useful install script.
http://forum.xda-developers.com/showthread.php?t=2172843
And when I want to use adb in "manual" mode I just launch a command prompt from his
'adb' directory (package is named 'mn2ri-v1.5.0-beta2.zip').
Try playing with his installer. And see if anything is displayed using:
Code:
adb devices
Thanks skippyV. I got it in fastboot last week with ubuntu and installed TWRP sucessfully.
I installed the custom ADB drivers from this site, I then booted my Shield and am stuck on the command prompt screen as it says
<waiting for devices> when I try to install the thor.img
The Shield is unlocked and the usb debugging option is on.
Cannot work out what the issue is.
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far
pictures
These are the pictures of the command promt when it is in boot mode, unboot mode and the devices installed.
When I go into boot mode on the shield the device called Nvidia Shield ADB dissappears from the computer manager window and the fastboot device has a yellow triangle with an exclamation mark next to it.
Very odd.
Yellow triangle means driver or device error (either one). The rest you have reached the limits of my knowledge.
appreciate the help
appreciate the help from everyone so far. I got through the bootloader stuff easily enough and now the shield is unlocked. This next bit is just knocked me for six as I have followed the instructions step by step and even taught myself some new stuff but this is not going according to plan.
So far:
I downloaded Andriod SDK
Ran SDK
clicked install and it installed lots of stuff including Android SDK tools, SDK platform tools and SDK Platform & ARM EABIv7a a system image in the Android 4.3 section.
I downloaded minimal adb and fastboot v1.1.3
I downloaded Superuser
I downloaded thor-insecure-boot.img
I downloaded the Universal_Naked_Driver_0.73 package
I then installed the Universal Naked Driver package which shows up on computer manager Devices under Android Devices as NVIDIA SHIELD ADB
I then dragged the thor and superuser files into the minimal adb and fastboot folder
I then plugged in my Shiled via USB 2.0
I started up the adb and fastboot CMD window
I first typed in adb devices and the shield showed up.
I then Typed in adb reboot bootloader
The shield went into boot mode.
I then retyped adb devices into the CMD window
The shield did not show up.
I the typed in fastboot boot thor-insecure-boot.img
The CMD window then said <waiting for Devices>
The shield screen showed that the device is unlocked and gave me 5 options:
Continue
Restart Bootloader
Recovery Mode
Reboot
Poweroff.
And then nothing.
This is the point I am at in terms of rooting.
The Device shows up in the Computer/manage window when plugged in but when I execute the adb reboot bootloader command it dissapears.
There is a Device in the Other Devices section of the Computer/manage window called Fastboot. This has a yellow triangle with an exclamation mark in it.
The CMD window can communicate with the Shield as it can make it go into boot mode but that's it.
Appreciate any help that can be given. Apologies for the length of post but it's only fair you know what I have done so far. Knowledge is power etc
I'm on windows 7 64bit os.
Latest pictures of the system
Ok so these are the latest picture of the system as it is now.
Currently there are two drivers showing for the Shield. One under Android Devices as Nvidia Shield ADB
The other is under Portable Devices as SHIELD. (picture 4 from the left)
When in boot mode the Android Device dissappears (picture 2 from the left)
There is a picture of the minimal adb and fastboot folder where I put the Superuser.apk file, the Su file and the Thor file - picture 3 (Is that all correct?)
There is also a picture of the command window when the shield is in boot mode. I type in adb devices and nothing shows up (picture 1)
Android SDK pics
And here is the SDK app running...
When your shield is waiting for fastboot commands it should show up as fastboot in device manager.
I had a terrible time with drivers too. My advice is to uninstall as many shield drivers as you can and then try to manually update the drivers making sure to get the fastboot driver installed. When you select have disk for the drivers the correct one will say Shield Fastboot
time to go fishing!
Ok I will try to uninstall drivers but not sure how to do it due to not exactly knowing which ones there are and where they are kept. Will take a look around. Thanks for the help though will try and find the fastboot drivers
gogul1 said:
Ok I will try to uninstall drivers but not sure how to do it due to not exactly knowing which ones there are and where they are kept. Will take a look around. Thanks for the help though will try and find the fastboot drivers
Click to expand...
Click to collapse
When I did it I plugged in my Shield and went into the device manager and uninstalled everything Shield related. I think it showed up in two places. Then I unplugged the Shield and when I plugged it back in I went back to the device manager and found the Shield again since Windows will auto install some sort of driver when you plug the shield in. I think this is when either there will be a yellow exclamation point next to one of them or windows will actually allow you to update the driver without giving you the stupid "driver is up to date" message.
That's when I right clicked on it and selected to update driver. At that point I made sure to use the "Have Disk" option and browsed to the universal driver folder. Once the universal driver list populated I was able to find the Shield fastboot driver in that list. I think my original problems started when I installed the Shield ADB driver which isn't needed and once that driver is installed the fastboot driver seems impossible to install because stupid windows keeps telling you the driver is up to date. By booting your Shield up using the home and back keys you are manually placing it in fastboot mode so you never need to use adb commands.
It is hard to remember but I do remember uninstalling everything I could and when I did finally update a driver I used the one with the word fastboot in it.
---------- Post added at 12:27 PM ---------- Previous post was at 12:21 PM ----------
gogul1 said:
These are the pictures of the command promt when it is in boot mode, unboot mode and the devices installed.
When I go into boot mode on the shield the device called Nvidia Shield ADB dissappears from the computer manager window and the fastboot device has a yellow triangle with an exclamation mark next to it.
Very odd.
Click to expand...
Click to collapse
If you get to this point again select to update that driver for the exclamation point and go to have disk and find the fastboot driver which you somehow get to by using the "have disk" option and browsing the universal drivers folder when you update the driver. Don't install the other drivers in the list, just the fastboot driver.
don't get the have disk option
uninstalled everything again. Next will be finding the Have disk option.
ah ha
I kinda see, when I go into Update driver Do I go into "let me pick from a list of device drivers?"
I click on that option and it gives me a list of devices but not sure what to choose. There was an android device option so chose that. I then went into the folder and clicked the "Have disk" option. I then navigated to the universal folder but there was nothing like bootloader or boot device in the folder.
I go into computer, right click, choose manage.
Go down to devices.
See OTHER DEVICES
In that folder is the SHIELD device with the yellow triangle next to it.
Right click it, choose update driver.
I choose let me pick from a list of device drivers on my computer.
It opens the window - select your device type from the list below
I choose show all devices
It opens the window - select the device driver you want to install for this hardware
I click the HAVE DISK button
I chose Install from disk option
I clicked the browse button
I navigated to the Universal naked driver folder and clicked open.
List of items in the folder are:
amd64 - folder
i368 - folder
android_apxusb.inf
android_winusb.inf
and that's it. So I chose android_apxusb.inf
right clicked on it to install.
window asking if I wanted to cancel or install anyway popped up.
chose install anyway.
Driver installed but still the same as before.
sigh
hmmmm
ok so this time I installed the ADB driver.
I then deleted the Portable Devices Driver named SHIELD.
I then booted my shield up again.
This time the Android Device Nividia Shield ADB turned into Fastboot and had the yellow triangle on it.
I then clicked on that chose to update drivers.
I then chose the Have Disk option. Chose the android_apxusb.inf file and clicked ok. There was the a long list of devices including asus eepad etc and I scrolled down to Nvidia Shield Fastboot.
I highlighted it clicked ok, it warned me that it didn't know if the driver was reliable, I clicked ok to install it anyway and the driver then went back up into the Android Devices folder in the device manager and was named Nvidia Shield fast boot.
So I opened up minimal adb & fastboot, then typed in adb reboot boot loader. The Shield booted, I then typed in adb devices but nothing showed up.
I then tried to do command the thor.img anyway, it say:
downloading boot.img
OKAY (0.810s)
booting...
OKAY (0.020s)
finished. total time 0.830s
The shield the rebooted and came back on as normal.
I then cut a paste the command lines:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
but when it came to the mount command it said:
mount: operation not permitted.
hmmmm something is not right but cannot put my finger on it....:roll eyes:
When I went back into the Device Manager I saw that under Android Devices there are now two drivers
Nvidia Shield ADB
Nvidia Shield Fastboot
Not easy this stuff eh?
20 times
I have uninstalled and reinstalled the drivers 20 times now. Always the same result.
I am going to start this all over again.
Don't think I will get any luck.
I uninstalled drivers, plugged in the shield, the updated the drivers via the have disk method. The booted shield.
Then changed fastboot driver to updated driver again.
The results of the whole thing can be seen here
Please help
Right I uninstalled all drivers again.
When I restart and plug the shield back in it automatically installs two drivers.
One is in the Other devices folder named SHIELD and has a yellow exclamation mark next to it.
The other is in Portable Devices and looks to install ok.
What am I meant to do with these?
I try to update the Portable device driver but it doesn't allow me to update it.
I update the other one as nvidia shield fastboot but the when I actually boot the Shiled up it moves from the Android devices folder to the other devices folder and calls itself Fastboot (it has a yellow triangle next to it.
So I then update that one to Nvidia shield fastboot and everything goes ok installng the thor.img.
The the shield roboots and reinstalls the same driver... Now I have two Nvidia Shield Fastboot drivers in my Android folder.
Really Really could do with some help people please please please
Ok, if you have the fastboot driver installed which you should if device manager says fastboot without any yellow exclamation. Windows device manager needs to say fastboot while your shield is connected in fastboot mode (hold home and back while powering the shield up) Download these two files that I link below (or go directly to Gnurou's site and get them if you feel more comfortable https://github.com/linux-shield/shield-root) and put them in the same directory that your fastboot android package is in.. They are the two files needed from gnurou's site for rooting. One is a text file and one is some sort of .gz file (don't unzip this .gz file.
http://db.tt/oPHjgctM
http://db.tt/S0p9KMPi
If your shield is not yet unlocked do this:
1. Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
2. Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
3. Connect your SHIELD to your computer using a USB cable.
4. open a command window from your fastboot folder and type this (I am assuming you have the android fastboot all set up properly):
fastboot devices
4a. That should list a big long number. If it does that means your fastboot is working.
5. On your computer, enter the following command:
fastboot oem unlock
6. This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
7. Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting (Shield should be unlocked at this point)
1. turn your shield off.
2. turn your shield on while holding the home and back buttons until you are in the bootloader.
3. plug the shield into the computer
4. open a command window from your fastboot folder and type this (I am assuming you have the android fastboot all set up properly):
fastboot devices
4a. That should list a big long number. If it does that means your fastboot is working.
Now type this:
fastboot boot zImage_dtb ramfs.img.gz
You should see the shield do it's thing with the penguins and then you're rooted.
This is how I rooted mine. It's way easier than doing that manual method. I copied some of the instructions directly from Gnurou's git site but the formatting is a little different. It all boils down to getting those drivers installed properly and you will know those damn things are installed properly when you have your Shield plugged into your computer while in fastboot mode (you held home and back before turning the shield on) and you can type fastboot devices and it lists a long number. I think people are shying away from this method because github can be confusing as far as how to download files and people seem to be confused about what all the other files are for on Gnurou's site when really you only need the two I linked.
Keep at it man. I know you'll get it.
Thanks
I was given a package of developer tegra nvidia drivers adk drivers to install.
Now I can boot my shield
When I type in fastboot devices my shield shows up as a long number
but when I type in fastboot boot zimage_dtb-ramfs.img.gz
I replies
cannot load zImage_dtb': No error
I put the files in the Minimal ADB and Fastboot folder.
Odd.
The drivers I have installed now are in this picture it works up until the point I need to execute the root
View attachment 2209196
This was my original issue in video form so you can see my problem.
http://youtu.be/amk7fkKJtSc
I was going to try and help here but after seeing how many different threads gogul1 has spread his issues though, I don't fell like spending 2 days trying to figure out what order his posts are in from thread to thread.
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
response
droidusr2014 said:
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
Click to expand...
Click to collapse
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Thanks
Thank you so much currently I can't try out your method but it looks like it could work THANK YOU SO MUCH I'm going to try tonight and I'll tell you how it went. I really don't mind factory resetting as long as it saves my phone im all right thanks again :laugh:!!!
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse
Will factory reset erase root??
One more thing I actually am currently rooted by using RockMyMoto so I think that is why the update didn't work but 1 last question when I factory reset will it erase root? I don't mind if it erases root but my main concern is that if root somehow stays I won't be able to do the software update.
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse
Tried the method and it worked!!
I tried what you said and it worked perfectly but it still remembers my Wifi, wallpaper and all it showed the setup screen and I set it up so hopefully im in the clear the phone is downloading the update right now.
It will not allow the update and you will still end in boot loop. Need to remove root first: http://forum.xda-developers.com/showthread.php?t=2577029
Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button
RESERVED
Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.
I guess you can type the path to the installation file instead of dragging.
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502
TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:
Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck
very good
Need Custom rom please
nougat / pie
Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)