I flashed the fxz gpe(after flashing the official first) a few weeks ago on my daughter's phone. It worked well until one night she said there were issues. It would not stop force closing just about every app. I did not have a custom recovery on it at that time. I have since attempted to rsd the gpe, the official fxz, a custom recovery. I have used fastboot commands to attempt to wipe userdata etc. All of these say successful, but it reboots back to the broken gpe each time. When I try to use adb shell to mount system it tells me permission denied. Note, this phone is being used as a media and game device, so no sim card and is in airplane mode with wifi on generally. Any ideas guys?
What does rsdlite say when you attempt to flash the official from the Motorola firmware It doesn't make sense that (if it does) when you rsd the official that it boots back to the broken gpe... You could try house of moto and see if it works any better
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
What does rsdlite say when you attempt to flash the official from the Motorola firmware It doesn't make sense that (if it does) when you rsd the official that it boots back to the broken gpe... You could try house of moto and see if it works any better
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After rebooting it back to the bootloader it says pass. House of Moto did not work either unfortunately. I also used his RSD flasher. You are absolutely right when you say it doesn't make sense. That is why I am baffled at this point. I am able only to get in to settings if I am quick enough(launcher crashes if I hit home), I just tried to switch to dalvic as I noticed it was on Art. However when it rebooted, it went back to Art still...
Try booting to recovery as its stock recovery factory reset and clear cache partition then when you select reboot immediately hold the volume up n down then go straight to the fastboot screen from that menu and rsd the official from there... Let us know (I know how important it is to get it working I have a 2 year old with a droid 4 and its the end of the world when it dies I can't imagine if I were in your position...)
Sent from my XT907 using XDA Premium 4 mobile app
Custom Recovery
jamminjon82 said:
I flashed the fxz gpe(after flashing the official first) a few weeks ago on my daughter's phone. It worked well until one night she said there were issues. It would not stop force closing just about every app. I did not have a custom recovery on it at that time. I have since attempted to rsd the gpe, the official fxz, a custom recovery. I have used fastboot commands to attempt to wipe userdata etc. All of these say successful, but it reboots back to the broken gpe each time. When I try to use adb shell to mount system it tells me permission denied. Note, this phone is being used as a media and game device, so no sim card and is in airplane mode with wifi on generally. Any ideas guys?
Click to expand...
Click to collapse
When you're flashing anything, it's a good idea to return to factory settings first & flash a clean stock rom. But when you flash a custom recovery, you need to make sure that it doesn't boot up normally after it's done. If it boots normally it will replace your custom recovery with stock recovery. To avoid this, as soon as its done flashing and begins the normal boot process, press power&volumeup&down simultaneously and scroll down to recovery and go into this. After you do this once, you shouldn't face anymore problems.:good:
ezknives said:
Try booting to recovery as its stock recovery factory reset and clear cache partition then when you select reboot immediately hold the volume up n down then go straight to the fastboot screen from that menu and rsd the official from there... Let us know (I know how important it is to get it working I have a 2 year old with a droid 4 and its the end of the world when it dies I can't imagine if I were in your position...)
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PrankCallPimp said:
When you're flashing anything, it's a good idea to return to factory settings first & flash a clean stock rom. But when you flash a custom recovery, you need to make sure that it doesn't boot up normally after it's done. If it boots normally it will replace your custom recovery with stock recovery. To avoid this, as soon as its done flashing and begins the normal boot process, press power&volumeup&down simultaneously and scroll down to recovery and go into this. After you do this once, you shouldn't face anymore problems.:good:
Click to expand...
Click to collapse
Just tried all of these suggestions and still have stock recovery and rebooting back to the same busted google play edition rom.
OK...just to be clear your using the 6.1.6 rsd lite and the 183.46.10 from sbf devoplers.org... Booting into fastboot letting rsd do its thing then allowing rsd boot the device and when it does it boots to the broken gpe?... let's see if more experienced individuals have an idea @RikRong @ATTACK
Sent from my XT907 using XDA Premium 4 mobile app
That's correct, also have redownloaded numerous times to verify that it didn't happen to be corrupt
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
That's correct, also have redownloaded numerous times to verify that it didn't happen to be corrupt
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Try and flash recovery with mfastboot but boot straight into recovery, then try and flash CM11 nightly.
Type
Code:
mfastboot flash recovery <recovery name>.img
Then
Code:
mfastboot reboot
as soon as you hit enter, press & hold volume up (+) which will take you into recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
still takes me back to this after following those commands
Sent from my VS980 4G using Tapatalk
commands I'm putting in
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
still takes me back to this after following those commands
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Did you run CMD with administrator rights?
ATTACK said:
Did you run CMD with administrator rights?
Click to expand...
Click to collapse
Just did and no luck
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
Just did and no luck
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Have you tried to mfastboot the images separately?
Code:
mfastboot flash...
Code:
modem NON-HLOS.bin
erase modemst1
erase modemst2
boot boot.img
recovery recovery.img
system system.img
erase cache
erase userdata
Just did and still booting into the same gpe Rom
Is there any more info that I can give you that would help us figure out what the heck is going on with this thing?
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
Just did and still booting into the same gpe Rom
Is there any more info that I can give you that would help us figure out what the heck is going on with this thing?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
When you did mfastboot reboot, did it reboot?
Have you tried other USB ports?
Did you get any errors with mfastboot?
Yes it reboots,zero errors reported
Sent from my VS980 4G using Tapatalk
Switched ports
Same as before
Sent from my VS980 4G using Tapatalk
Don't know if this info helps
Sent from my VS980 4G using Tapatalk
jamminjon82 said:
Don't know if this info helps
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
If you could would you please try this, I would like to see if ADB reads your partitions.
Boot to the OS and make sure ADB is on.
In CMD type
Code:
adb shell
Except the dialog that pops up on your phone.
Then Type
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
Related
Hello! I know I have already posted a few threads about this, but I want to be 100% right, that's the only way to learn Android!
So I want to flash CWM touch recovery to my device, and I don't want to use any toolkits like I did before. The only thing I want to have from the toolkit now are drivers, because I won't uninstall them, seems pointless.
This is how I think you have to flash a recovery, but please correct me if I'm wrong!
1.Download fastboot files and place them in any directory (how many files are they? Do I have to extract them?
2.download customrecovery.img and place the file in the same directory as the fastboot files.
3.Open command prompt in that directory and type "fastboot flash recovery customrecovery.img"
Is this the full guide on how to install a recovery? Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
In a nutshell, yes, you are correct. For more detailed answers:
1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.
2. correct
3. this is correct, but you HAVE to be in bootloader mode.
So the order would be:
adb reboot bootloader
fastboot flash recovery customrecovery.img
Easy, and +1 for wanting to learn how to do things the proper way.
rickbosch said:
In a nutshell, yes, you are correct. For more detailed answers:
1. Yes, place them in the same directory as your ADB drivers, that way you won't have to CD when switching between the two.
2. correct
3. this is correct, but you HAVE to be in bootloader mode.
So the order would be:
adb reboot bootloader
fastboot flash recovery customrecovery.img
Easy, and +1 for wanting to learn how to do things the proper way.
Click to expand...
Click to collapse
Ok so the only files I need are adb drivers, fastboot drivers and the recovery. But do I have to extract any of them? Or just download and place them in the directory without changing the files?
Sent from my Nexus 4 using xda app-developers app
that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.
rickbosch said:
that would depend where you got them. I use this, because I don't want to download and install the SDK. Download the zip at the bottom of this post (http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1) named "platform-tools-v16.zip". Extract the contents to an easy to reach folder, I use C:\Android. Then when you want to use terminal commands shift+right click "open command window here", connect your device, ensure USB Debugging is on and that you've given ADB permissions when it asks for the RSA key. Then you can run "adb devices" to see if they work properly.
Click to expand...
Click to collapse
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
And when I've done all that I just have to reboot in bootloader mode and I can flash the recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yessir.
Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thibaultvw said:
Are ADB and fastboot correctly set up now? From now on I just have to download the recovery and I'm good to go?
Click to expand...
Click to collapse
Boot your phone into bootloader mode, connect your phone to your PC with USB cable, run command "fastboot devices" to check if the driver is properly setup. If you can see your device ID then it is good to go.
Else, download google usb drivers here: http://developer.android.com/sdk/win-usb.html
This guy says you have to wipe data/factory reset. I dont think thats needed right? Cause he actually wipes his OS right?
http://youtu.be/nb_MweQpGbQ
You don't have to flash the user data image, but it could result in not getting past the boot screen on initial boot.
http://forum.xda-developers.com/showthread.php?t=2266654
Install Custom Recovery
We’ve 2 custom recoveries available yet for our Nexus 4 viz ClockworkMod and TWRP. ClockworkMod or CWM (in short) comes in 2 variants (Touch UI based & Non-Touch UI based). Below I have mentioned on how to flash each one of them using fastboot. For more info about these two recoveries, visit ClockworkMod and TeamWin websites.
Reboot your device into bootloader mode. Either manually, by powering off and then pressing Volume Down + Power buttons simultaneously or using the following command in CMD/Terminal.
Code:
adb reboot bootloader
Download the latest build of your desired recovery [CWM | TWRP]
Place the downloaded recovery image (.img) file on your desktop.
If in Windows, open CMD and cd it to the desktop using the following command
Code:
cd Desktop
If in OS X or Linux, open terminal and cd it to the desktop using the following command
Code:
cd ~/Desktop
To flash ClockworkMod Non-Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash ClockworkMod Touch, type in the following command:
Code:
fastboot flash recovery recovery-clockwork-touch-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
To flash TWRP, type in the following command:
Code:
fastboot flash recovery openrecovery-twrp-x.x.x.x-mako.img
Replace x.x.x.x with the recovery build no. that you downloaded.
Once flashed, you will prompted on the CMD/Terminal itself.
Now, either reboot your device by using volume keys to highlight Reboot and select using Power button or reboot into the recovery by selecting Recovery mode.
Voila! The next to follow is to root or directly flash a Custom ROM, which is already rooted
And do I have to do a factory reset when that is done?
Thibaultvw said:
And do I have to do a factory reset when that is done?
Click to expand...
Click to collapse
Nope.
If you boot into recovery and see an android lying out with exclamation mark, use "fastboot format cache" in bootloader mode.
ksilver89 said:
Nope.
If you boot into recovery and see an android lying out with exclamation mark, use "fastboot format cache" in bootloader mode.
Click to expand...
Click to collapse
You mean if it boots in stock recovery?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
You mean if it boots in stock recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That will only happens when you use stock rom with install-recovery.sh. if you plan to use custom ROM, safely ignore it.
ksilver89 said:
That will only happens when you use stock rom with install-recovery.sh. if you plan to use custom ROM, safely ignore it.
Click to expand...
Click to collapse
I am currently running the stock rom without any mods, so CWM will stick?
And yes I'm planning to get back my old love CM as soon as it updates to 4.3
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I am currently running the stock rom without any mods, so CWM will stick?
And yes I'm planning to get back my old love CM as soon as it updates to 4.3
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This is getting complication since the introduction of new rooting method for 4.3.....
A: You don't want root
Answer yes if CWM ask you to rename install-recovery.sh, otherwise it won't stick.
B: You want to root with SuperSU
After flashing SuperSU zip, answer No if CWM ask you to rename install-recovery.sh, because the file is modified by SuperSU and it is needed for the root to work.
ksilver89 said:
This is getting complication since the introduction of new rooting method for 4.3.....
A: You don't want root
Answer yes if CWM ask you to rename install-recovery.sh, otherwise it won't stick.
B: You want to root with SuperSU
After flashing SuperSU zip, answer No if CWM ask you to rename install-recovery.sh, because the file is modified by SuperSU and it is needed for the root to work.
Click to expand...
Click to collapse
I want root, so after flashing the supersu zip CWM will ask me? All right!
Will it ask me always after flashing something?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I want root, so after flashing the supersu zip CWM will ask me? All right!
Will it ask me always after flashing something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It will ask every time when you want to reboot from CWM. Alternatively, you can use twrp.
Hello,
my Nexus 7 wasn't turned on since 3 weeks. Yesterday, I tried to boot it but it just shows the Google logo. The same with the Recovery. So I tried to install with N-Cry a Recovery, it shows that the installation was successfull, but it won't change everything. The same with the factory ROM, I tried it to install it via ADB, it shows that the installation was successfull, but it doesn't boot and still stucks in the Google-Screen. Know? What can I do? Is it a hardware problem? That would be terrible, because the gueranty ended august 2013.
Greetz!
Edit: If I try to Shut it down via fastboot, it shows Unrecoverable Bootloader Error.
DELETE
I am having an identical issue. I have experienced and resolved the battery issues before. This is not that. I've tried factory resets, toolkit stock flashes, toolkit OS updates, adb wipes and flashes. Everything always says successfully completed but it only boots to Google logo and occasionally freezes on the nexus logo.
Does anyone have more info on the N7's acutal boot process? I assume the Google logo is the POST. Is the Nexus logo provided by the bootloader, the kernel or after the OS starts running?
Is there a way to install a new bootloader?
Is there a win7 or Debian program program that will show in more detail every single line and process during the boot process?
Yea, there is a way, I've allready done it, but it doesn't boot anyway. With the Baseband Version sorry, but it's my fault, there cannot be a Baseband Version on my Grouper.
My Fastboot shows:
Product Name - grouper
Variant - grouper
HW Version: ER3
Baseband Version - N/A
Serial Number: 015XXXXXXXXXXX
Singing: Not defiened yet
LOCK STATE - UNLOCKED
fixed mine, conflicting driver issue and used pdanet versions instead of universal.
Thanks man. That could be work. I will try it later. Anybody another ideas?
Sent from my GT-I9300 using xda app-developers app
Push! Please, anybody any another ideas? The driver wasn't the problem, it doesn't turn on. I can do anything, flash with ADB, flash with different Toolkits...
PLEASE I need my tab...
PUSH! Please help. I tried it so much times, I deinstalled all drivers and install different drivers again... Please what could I do?
Hi, i have this problem but worse is that the buttons of my tablet are not working. It seems i can not boot pass the fastboot whenever i try to reboot (using Wug's Toolkit). Please, does anybody here who can help?
Have you tried flashing back to stock with fastboot?
Sent from my SGH-I997 using XDA Premium 4 mobile app
yes, i have tried that but it still won't pass fastboot. i don't know what's happening. i even tried disconnecting the power/volume buttton cable and tried rebooting again to check if it was the one causing the problem but still it did the same thing.
akerocks said:
yes, i have tried that but it still won't pass fastboot. i don't know what's happening. i even tried disconnecting the power/volume buttton cable and tried rebooting again to check if it was the one causing the problem but still it did the same thing.
Click to expand...
Click to collapse
So, you downloaded the factory image from google and flashed via fastboot from the pc?
Sent from my SGH-I997 using XDA Premium 4 mobile app
yes, using wug's toolkit
akerocks said:
yes, using wug's toolkit
Click to expand...
Click to collapse
No, not wugs. Forget toolkits. First, go here and download the factory image.
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz
Unzip into same folder on pc where you have fastboot binary.
Next, boot to fastboot. Plug N7 to the pc. Open pc directory where fastboot is. Open a command window. (Click on an empty section of the folder so no files are highlighted, hold shift key on keyboard and right click with mouse. Choose "open command window here" from the dropdown)
Type these commands.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-kot49h.zip
Sent from my SGH-I997 using XDA Premium 4 mobile app
hi, thank you for the reply. i followed your steps but this is what i got...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
akerocks said:
hi, thank you for the reply. i followed your steps but this is what i got...
Click to expand...
Click to collapse
The commands must correspond to the version you downloaded. Jkr16s....4.23...etc. Could you post a screenshot of the folder you have those files in? Ill see what the deal is
You unzipped the tar.gz, correct?
Sent from my SGH-I997 using XDA Premium 4 mobile app
akerocks said:
Click to expand...
Click to collapse
Here is the issue. When you downloaded the tar.gz file that the image-nakasi-kot49h.zip was in, ot also contains the bootloader and some files called .flash-all, .flash....etc. All thoes files need to be in this folder. The image cant be flashed without the bootloader being sucessfully flashed, and the -w command is not recognized withoit the .flash-all.... files. Unzip all the tar.gz contents into the folder and do it again. It will be fine.
Sent from my Nexus 7 using XDA Premium 4 mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay, so I have tested many different root methods on my Moto G. Somehow I managed to screw them all up! So here is how I got my root working. This method should work on Jelly Bean AND KitKat. This is my first guide, so if anything is missing, please notify me. DON'T GUESS! ask others for clarification. So far this is a Windows guide, I am unsure if this will work on Mac or Linux...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Notice: None of these files are my own, not even the method. I just took different files and methods and messed with them until I was able to get root.
Okay, so here we go.
Files Needed:
My root tools
ADB Tools - make sure to add to your Window's Path (step 4 and on)
Moto G drivers
Be sure to place "supersu.motog.zip" on the root of your device
Directions:
1)Unlock your bootloader
2)Reboot into Bootloader
3)Flash Logo Fix
4)Flash TWRP or CWM
5)Reboot into Recovery
6)Flash "supersu.motog.zip"
7)Reboot
Indepth Look:
UNLOCKING BOOTLOADER
Follow this guide from Motorola
REBOOT INTO BOOTLOADER
1) Type mfastboot reboot-bootloader into Command Prompt and hit enter
FLASH LOGO FIX
1) Type fastboot flash logo logo.bin into Command Prompt and hit enter
FLASH RECOVERY
If on JB 4.3
TWRP
1) Type mfastboot flash recovery trecovery.img into Command Prompt and hit enter
or
CWM
1) Type mfastboot flash recovery crecovery.img into Command Prompt and hit enter
If on KK 4.4
TWRP
1) Type fastboot boot 44trecovery.img into Command Prompt and hit enter
or
CWM
1) Type mfastboot flash recovery 44crecovery.img into Commander Prompt and hit enter
REBOOT INTO RECOVERY
1) Press the volume down button
2) Press the volume up button
FLASH "SUPERSU.MOTOG.ZIP"
1) Wait for screen to time out
2) Awaken device with the power button
3) Tap "Install"
4) Select "supersu.motog.zip"
5) Swipe to install
WARNING! The touch screen will be buggy. Just try the best you can. It is possible to install the zip, I have done it. Good luck!
REBOOT
1) Reboot your phone
[CREDITS]
Motorola - for Moto G
Google - for Android
Redmond Pie - for ADB setup guide
@lost101 - for Moto G USB Drivers
@oasoas014 - for 4.3 Bootloader
@paulobrien - for "supersu.motog.zip"
@a1Pha - for TWRP & CWM
@ffosilva - for Logo Clean Up
@danger2u - for trying with CWM
@Paulskiii - for skipping JB Bootloader flash first Brave man right here.
@daothanhduy1996 - for getting me into Android!
@lokeshsaini94 & @Lifehacker7 - for reminding me that who cares about warranties? Root that phone!
Message me if I used your work and forgot to credit you!
Works! Rooted on 4.4 ota xt1034 thanks!
69
Works perfectly. Using CWM 6.0.4.5 and Kitkat. :good:
zyrn said:
Works perfectly. Using CWM 6.0.4.5 and Kitkat. :good:
Click to expand...
Click to collapse
Please be mature with your titles... Anyways, glad that my root method is working for you guys!
Paulskiii said:
Works! Rooted on 4.4 ota xt1034 thanks!
Click to expand...
Click to collapse
you write "4) Select "supersu.motog.zip" "
but where is it? I cna't find on my phone.
If I need to transfer what I downloaded, I don't know how.
I can't transfer to my phone, because I can't chose on usb mass storage , because that is nowhere.
I downloaded, the widget, but it works only rooted device...
I try turn off, and plug usb and turn on, but I don't have usb mass storage nowhere.
Sorry but this 4.3 system is strange to me.
robagp said:
you write "4) Select "supersu.motog.zip" "
but where is it? I cna't find on my phone.
If I need to transfer what I downloaded, I don't know how.
I can't transfer to my phone, because I can't chose on usb mass storage , because that is nowhere.
I downloaded, the widget, but it works only rooted device...
I try turn off, and plug usb and turn on, but I don't have usb mass storage nowhere.
Sorry but this 4.3 system is strange to me.
Click to expand...
Click to collapse
working with CWM 6.0.4.5
just flash this with the comand
fastboot flash recovery recovery.img
then boot into recovery and install Super su
recovery here
http://www27.zippyshare.com/v/10346740/file.html
danger2u said:
working with CWM 6.0.4.5
just flash this with the comand
fastboot flash recovery recovery.img
then boot into recovery and install Super su
recovery here
http://www27.zippyshare.com/v/10346740/file.html
Click to expand...
Click to collapse
Thank you I didn't include CWM because when I tried it, it didn't identify any of my zip files... I will update my Root Tools and OP with this information.
Thanks!
Excellent guide! The other methods did not work for me but this did.
Cooptx said:
WARNING! The touch screen will be buggy. Just try the best you can. It is possible to install the zip, I have done it. Good luck!
Click to expand...
Click to collapse
Glad you included that bit. Getting this part to work took near as long as the rest.
Ok, I found the way.
There is no USB Mass Storage mode on my Moto G.
I check on www.android.com/filetransfer and I need a file on Mac OS X.
Thank you very much!
danger2u said:
working with CWM 6.0.4.5
just flash this with the comand
fastboot flash recovery recovery.img
then boot into recovery and install Super su
recovery here
http://www27.zippyshare.com/v/10346740/file.html
Click to expand...
Click to collapse
Added this information to OP, and added CWM recovery.img to my zip file. Thanks!
I really REALLY appreciate this, but I'm really hoping for a way to Root without unlocking
Cooptx said:
Added this information to OP, and added CWM recovery.img to my zip file. Thanks!
Click to expand...
Click to collapse
if u flash the bootloader for 4.4.2 after u installed root u won t be able to boot into recovery clockworkmod
so u need to stay with 4.3 bootloader to making work the clockworkmod
we need a fix for 4.4.2 bootloader
---------- Post added at 02:00 AM ---------- Previous post was at 01:59 AM ----------
FiliBrushedRed said:
I really REALLY appreciate this, but I'm really hoping for a way to Root without unlocking
Click to expand...
Click to collapse
there is no way untill now
FiliBrushedRed said:
I really REALLY appreciate this, but I'm really hoping for a way to Root without unlocking
Click to expand...
Click to collapse
Sorry, but one of the reasons for the bootloader is to prevent root. I don't think anyone's has rooted with a locked bootloader
Sent from my XT1034 using Tapatalk
Cooptx said:
Sorry, but one of the reasons for the bootloader is to prevent root. I don't think anyone's has rooted with a locked bootloader
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Since this is a Motorola thing, there's no way of getting warranty back right? Not even relocking... I'm considering on doing it... (Sorry I come from Sony Ericsson devices which I used to relock and voila, warranty is on)
Cooptx said:
Sorry, but one of the reasons for the bootloader is to prevent root. I don't think anyone's has rooted with a locked bootloader
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Lol you mean for this phone right? Phones I used before tend to have root and 2nd int well before unlocked boot loader
sent from the kitty kat Atrix HD Maxx
Durteedee said:
Lol you mean for this phone right? Phones I used before tend to have root and 2nd int well before unlocked boot loader
sent from the kitty kat Atrix HD Maxx
Click to expand...
Click to collapse
I find it doubtful that anyone will bother with 2ndinit and other irritating hacks if you can unlock the bootloader so trivially.
root without unlocked bootloader generally requires an exploit to be found in Android (or potentially a driver) and those have gotten increasingly more rare...
from @Entrophy512 (http://forum.xda-developers.com/showthread.php?t=2583652)
Flashing bootloaders is a dangerous operation - it's one of the few ways you can hardbrick your device.
THIS IS TEMPORAL , you take the risk.
Cooptx said:
Sorry, but one of the reasons for the bootloader is to prevent root. I don't think anyone's has rooted with a locked bootloader
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
It's possible for other phones with bl locked. Boot from recovery, w/o flash it, only boot from a custom recovery, from here flash su zip.
I read here that on 4.3 using one of the modaco guides, omitting unlocking bl part, someone rooted his phone w/o unlocking bootloader.
In one of the first topic in this section.
denzel09 said:
It's possible for other phones with bl locked. Boot from recovery, w/o flash it, only boot from a custom recovery, from here flash su zip.
I read here that on 4.3 using one of the modaco guides, omitting unlocking bl part, someone rooted his phone w/o unlocking bootloader.
In one of the first topic in this section.
Click to expand...
Click to collapse
Shouldn't be possible. Like walking through locked door...
Sent from my GT-I8190 using Tapatalk
thanks man
awesome word :good:
Hello people, basically I'm experiencing a problem in which no ROMS will install and I have nothing on the phone itself to fall back on (all partitions wiped.)
I'm using the latest drivers, but the phone has a problem receiving commands via the bootloader for some reason. I've tried side-loading, flashing a zip normally, using the "Flash stock+unroot option" all via the "Nexus Root Tool-kit"; I've tried using the command prompt through Android SDK's ADB flashing tool, but it didn't work.
While trying to side-load via the Nexus root tool-kit it doesn't work, however while sending the command to boot into stock recovery it does show "downloading..." text at the bottom of the screen, but it freezes up and I have to hold power+volume down to get back into the bootloader successfully.
While trying to side-load via the command prompt through ADB side-loading (SDK) however, it recognizes my device and tries to install zip files but says at 1%, 2%, and 4% (depending on the file) and nothing really happens and after I cancel the sideload it says "can't open /tmp/update.zip (bad)", I then tried finding an update.zip file for the recovery but that didn't side-load either (nor TWRP; my preferred recovery)
This all happened after I stupidly downloaded+installed a previous version of CyanogenMod in which afterwards no processes would work, so I factory reset it and nothing's working (here I am.) Early on I hit root on the clockwork mod since it said it wasn't rooted (I hit it anyway, hence it already being rooted), that may be why I can't do anything in the first place (I did this before I even tried flashing a zip); I then wiped all of the partitions this morning, and no changes. I've also tried all 3 drivers for the Google bootloader (Naked drivers)
I'm using Clockwork recovery 6.0.5.0 legacy (non-touch) and have a Nexus 4 that's unlocked+rooted.
Please help, I've tried everything and have spent hours on end with Google searches and troubleshooting to try to fix this.
Have you tried the flash-all.bat file in the factory image while booted into fastboot?
Sent from my Nexus 5 using XDA Free mobile app
Don't see it
jd1639 said:
Have you tried the flash-all.bat file in the factory image while booted into fastboot?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't see a .bat file in either the the stock or liquidsmooth rom. Could you point me to a rom that has one so I may try this? Thanks
xXDustinoXx said:
I don't see a .bat file in either the the stock or liquidsmooth rom. Could you point me to a rom that has one so I may try this? Thanks
Click to expand...
Click to collapse
Google nexus 4 factory image. Download that and extract it using winrar or 7-zip
Sent from my Nexus 5 using XDA Free mobile app
Nothing...
jd1639 said:
Google nexus 4 factory image. Download that and extract it using winrar or 7-zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Darn, I was hoping it was going to work; On my phone in the command line it says:
(Before I sent the file)
sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>
(after I sent the file):
Restarting adbd...
Finding update package...
Opening update package...
E:/can't open /ta[/update.zip
(bad) (there's that error again, except it almost worked)
Installation aborted.
xXDustinoXx said:
Darn, I was hoping it was going to work; On my phone in the command line it says:
(Before I sent the file)
sideload started...
Now send the package you want to apply
to the device with "adb sideload <filename>
(after I sent the file):
Restarting adbd...
Finding update package...
Opening update package...
E:/can't open /ta[/update.zip
(bad) (there's that error again, except it almost worked)
Installation aborted.
Click to expand...
Click to collapse
Just boot into the bootloader with your device connected and double click the bat file. Don't boot into recovery and try to side load it
Sent from my Nexus 5 using XDA Free mobile app
"Downloading"
jd1639 said:
Just boot into the bootloader with your device connected and double click the bat file. Don't boot into recovery and try to side load it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader freezes up and shows "downloading..." on the screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xXDustinoXx said:
The bootloader freezes up and shows "downloading..." on the screen
Click to expand...
Click to collapse
image url attatched for command prompt picture
What should I do?
xXDustinoXx said:
image url attatched for command prompt picture
What should I do?
Click to expand...
Click to collapse
I'm on my phone and can't see your image. What does it say?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'm on my phone and can't see your image. What does it say?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It says:
sending 'bootloader; <2500KB>...
FAILED <data transfer failure <unknown error>>
finsihed. total time:5.007s
rebooting into bootloader...
All the while the device is trying to download the data but freezes up as if it can't accept unsigned code (unrooted)?
xXDustinoXx said:
It says:
sending 'bootloader; <2500KB>...
FAILED <data transfer failure <unknown error>>
finsihed. total time:5.007s
rebooting into bootloader...
All the while the device is trying to download the data but freezes up as if it can't accept unsigned code (unrooted)?
Click to expand...
Click to collapse
Are you trying to flash while booted into recovery? You don't want to be in recovery, just the bootloader, vol down + power
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you trying to flash while booted into recovery? You don't want to be in recovery, just the bootloader, vol down + power
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I was doing it with the bootloader, and I did try it via the adb side load just to see if that'd work after the bootloader wouldn't work
xXDustinoXx said:
Yes, I was doing it with the bootloader, and I did try it via the adb side load just to see if that'd work after the bootloader wouldn't work
Click to expand...
Click to collapse
Then you have something wrong with your device. If you try to relock the boot loader does it stay locked or does it remain unlocked?
fastboot oem lock
Then
fastboot oem device-info
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Then you have something wrong with your device. If you try to relock the boot loader does it stay locked or does it remain unlocked?
fastboot oem lock
Then
fastboot oem device-info
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It was the cord the entire time, that was it! Can't believe that after all of these hours! It's now booting into android! Thanks so much for your help, greatly appreciated
xXDustinoXx said:
It was the cord the entire time, that was it! Can't believe that after all of these hours! It's now booting into android! Thanks so much for your help, greatly appreciated
Click to expand...
Click to collapse
Glad you got it working. Go figure, the cord
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Glad you got it working. Go figure, the cord
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I know right! Thanks again
I was using yu yureka plus. Then i try to root it so i tried to unlock bootloader then i flash recover IMG and then phone stuck at TEAMWIN logo and keep restarting so i tried to flash stock room by using fastboot. It goes well as i thought. But when i try to restart my phone looks like this (as shown in image)and same in fastboot mode(i try to boot in fastboot mode by using volume up key and then plug in pc) help me to solve this thank you
I used this post toflash stock
https://forum.xda-developers.com/yureka/general/yureka-cm12-lollipop-fastboot-zip-t3085621
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Lenovo A6020a40 using XDA-Developers Legacy app
himanshubarala said:
I was using yu yureka plus. Then i try to root it so i tried to unlock bootloader then i flash recover IMG and then phone stuck at TEAMWIN logo and keep restarting so i tried to flash stock room by using fastboot. It goes well as i thought. But when i try to restart my phone looks like this (as shown in image)and same in fastboot mode(i try to boot in fastboot mode by using volume up key and then plug in pc) help me to solve this thank you
I used this post toflash stock
https://forum.xda-developers.com/yureka/general/yureka-cm12-lollipop-fastboot-zip-t3085621
Click to expand...
Click to collapse
Flash ROM using ygdp tool.
Get it from www.firmwarefile.com:good:
nischait said:
Flash ROM using ygdp tool.
Get it from www.firmwarefile.com:good:
Click to expand...
Click to collapse
Thanks man it's help now i am on kitket trying to update... Any suggestions please to update
Sent from my Lenovo A6020a40 using XDA-Developers Legacy app
himanshubarala said:
Thanks man it's help now i am on kitket trying to update... Any suggestions please to update
Click to expand...
Click to collapse
Which version you flashed through ygdp 1st second or last?
I flashed last one but when I unlocked it flash twrp it stucks on yu logo
Then I flashed 1st version then everything works well but not get volte in aosp extended ,quarkos and in miui8 also.
Someone suggests me to install official 12.1 signed zip to get volte but I don't tried it if you have then install it first through twrp or default recovery.
After that install any custom ROM and please report me. Also hit thanks my post which helps you.
I tried from a YouTube video by same method now I am on 4.4.4
Sent from my YU5510A using XDA Free mobile app
himanshubarala said:
I tried from a YouTube video by same method now I am on 4.4.4
Click to expand...
Click to collapse
Unlock bootloader now
In settings developer option
Check OEM unlocking
USB debugging
Update recovery with system updates
Use adb & fastboot commands.
See my op for same.
Achualy I was trying to unlock boot loader after that I stuck at blue lines now little afraid to do that again
Sent from my YU5510A using XDA Free mobile app
himanshubarala said:
Achualy I was trying to unlock boot loader after that I stuck at blue lines now little afraid to do that again
Click to expand...
Click to collapse
You have solution for revive your phone then why are you daring ? Anyway if you are satisfied with stock then don't do unlocking.
I am not satisfied with stock rom... And you are right about unlocking but I will do it when I get another phone...
Sent from my YU5510A using XDA Free mobile app
himanshubarala said:
I am not satisfied with stock rom... And you are right about unlocking but I will do it when I get another phone...
Sent from my YU5510A using XDA Free mobile app
Click to expand...
Click to collapse
Hey buddy i was trying to install recovery but i failed i tryied your mathod to do thata my bouutloader unlock says true(is my bottloader unlocked or not please tell). Than i installed recovery file using recovery command in cmd but nothing is showing in recovery mode when i try to do boot in recovery its just restart and boot into kitkat
Any suggestion how to boot in recovery
Sent from my YU5510A using XDA-Developers Legacy app
himanshubarala said:
Hey buddy i was trying to install recovery but i failed i tryied your mathod to do thata my bouutloader unlock says true(is my bottloader unlocked or not please tell). Than i installed recovery file using recovery command in cmd but nothing is showing in recovery mode when i try to do boot in recovery its just restart and boot into kitkat
Any suggestion how to boot in recovery
Click to expand...
Click to collapse
Your bootloader is unlocked if it showing true
Now flash twrp 2.8.7.0 through fastboot
fastboot -i 0x1ebf flash recovery twrp 2.8.7.0.img
When done
Disconnect phone
Remove battery & insert again after 1 minute
Press and hold volume+ , volume- & power key
When yu logo appears hold volume + & volume -
For few seconds. Twrp logo appears and you got twrp installed successfully.
Miui 8 for yureka
Please help me in this thing . I am very annoyed , when i flash miui 8 it works well but when i use the device it automatically restarts again and again please help me with the rom or give me a step by step tutorial how to fix autorestart or bootloop and heating and battery draining issue of yu yureka
TORAD said:
Please help me in this thing . I am very annoyed , when i flash miui 8 it works well but when i use the device it automatically restarts again and again please help me with the rom or give me a step by step tutorial how to fix autorestart or bootloop and heating and battery draining issue of yu yureka
Click to expand...
Click to collapse
Do a clean flash
Wipe everything
Install ROM
Wipe dalvik cache
Done
Try it