Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Anybody have any ideas?
Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks
Bump...................
voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.
Any luck???
kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .
voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent
kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok
voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees
kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck
Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
Related
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!
now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?
URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.
I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
Hi,
I wanted to flash the just released lollipop image so I unlocked my phone and updated TWRP from 2.8.0.1 to 2.8.1.0. Then I started Recovery and it was doing some werid thing in a list (was too fast), then rebooted. Recovery came up again (only the image of TWRP) and a restart again. Since then always when I try to go into recovery the starting image will show up, after 2-3 secs it gets black for half a second, then the image will show up again. This is a permanent loop. I flashed back to the old recovery but nnothing, still the same (and this one worked before!).
Hopefully someone of you knows whats wrong.
Thanks,
S3cret
reflash twrp recovery. but to correct you on your mistake before you do it, factory imgs are not flashable via any recovery, you can only flash them via fastboot.
I reflashed recovery several times now. I just thought being on the latest recovery version would be good. I know how to flash the lollipop image via fastboot, but I still need recovery for root.
I locked and unlocked the bootloader again and the same happened. Recovery started, doing some weird things and then the loop again.
Edit: Ok, I fixed it, somehow, I dont rly know how...
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
vercety974 said:
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
Click to expand...
Click to collapse
exactly the same here
Yup, dead Android with red warning triangle appears...
My stock recovery is broken after fastbooting the latest 5 image. Shows a red triangle above the laying down android.
How are we supposed to fix this?
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Highway 55 said:
After fastboot flashing the .img files you need to (WITHOUT REBOOTING) flash custom recovery, TWRP etc... After that from the bootloader reboot into TWRP or whatever. When your in the custom recovery you need to adb push a permissive stock kernel or custom kernel as well as suspersu.zip. Again, without rebooting into the system, flash the kernel first then supersu. Now you can reboot into the system. ?
Click to expand...
Click to collapse
vercety974 said:
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Click to expand...
Click to collapse
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Highway 55 said:
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Click to expand...
Click to collapse
It is exactly as he said in the post you linked.
Flash TWRP recovery and immidiately after run auto root. Then TWRP recovery will survive system boots.
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Can you access the bootloader? If yes, then you did not brick it. You probably didn't completely wipe the stock ROM before you flashed the custom one. Also, not a good idea to flash SuperSU before flashing your ROM.
Everything is working has usual, except i cant connect to LTE anymore. I flashed TWRP instead of Clockwork recovery, ill try again with this one...
From where you are now with TWRP installed:
1. In TWRP, go to "Wipe" then go into the advanced wipe options and wipe every partition except the internal storage.
2. Flash ROM.
3. Flash Gapps if needed.
Google "APN"
theesotericone said:
Google "APN"
Click to expand...
Click to collapse
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
insistents said:
From what ive seen, i have to set it up myself?
Also i currently has no ROM installed, and none in my SD card, i tried sideload but it failed, is there a way to transfert the ROM to my memory card in TWRP? If i have to click USB-OTG for it, then nothing happen when i do.
Click to expand...
Click to collapse
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Brushstroke said:
Push the ROM zip file to your phone from within TWRP, don't sideload it. You shouldn't even need to do that though. TWRP now supports MTP so your internal storage should appear when you connect the phone to the PC when you're in TWRP.
Click to expand...
Click to collapse
-snip
Had to turn off MTP
theesotericone said:
So you went from having possible APN issues to completely wiping your device? Slow down before you actually do brick it. Read the stickies. All the info you need is already here.
Click to expand...
Click to collapse
I followed the stickies, im not sure what i could have missed.
insistents said:
I tried "adb push rom.zip /sdcard/"
but it say
error: device not found
Click to expand...
Click to collapse
Nevermind.
insistents said:
Hello, i recently installed the new official lollipop 5.0 android, however it was working like crap so i decided to change with custom firmware.
Heres what i did.
Unlock bootloader
install custom recovery
root with super SU
install custom rom.
It worked, and android started up, however, i cant connect to cellular network anymore, i waited like 10 minute to detect it but it wont, then i tried a different rom, didnt help. Did i bricked my phone? Is there anything to do?
Im with Virgin canada
Thanks
Click to expand...
Click to collapse
Try wiping your cache in TWRP.
Brushstroke said:
My bad. TWRP, as far as I can tell, only allows sideloading as far as ADB commands are concerned. Can you not mount the SD using the Mount option in TWRP?
Click to expand...
Click to collapse
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
insistents said:
I managed to push files by disabling MTP
However, im still waiting on that colour dot loading screen...
Click to expand...
Click to collapse
Which screen are you referring to?
Brushstroke said:
Which screen are you referring to?
Click to expand...
Click to collapse
Boot screen, where there are flying colour dot.
By the way, i only have managed to enter TWRP recovery once, for all the other time, there only was the Teamwin picture, then it reboot to android each times...
insistents said:
Boot screen, where there are flying colour dot.
By the way, i have to do "fastboot flash recovery recovery.img" each time if i want to acess TWRP
Otherwise it wont work, when i go to recovery mode, i can see the TeamWin picture appear for a few second, then the phone reboot to android.
Click to expand...
Click to collapse
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Brushstroke said:
Well, did you flash a ROM or factory image? Earlier you said there was no ROM installed.
And about that TWRP issue...not too sure. That could be the recovery_from_boot.p file restoring the stock recovery. Are you seeing an android with a red exclamation point?
Click to expand...
Click to collapse
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Ah well i think i fixed the recovery, i used an older version and now its starting properly.
insistents said:
There was none earlier untill i managed to push a rom in the memory card, but now the Rom just wont start, its stuck in the boot screen so i will try a different ROM.
Nope no red exclamation point, when i choose recovery mode, the Google boot screen appear, then the Teamwin logo appear for a few second, then screen goes black and then google logo is back, and finnaly android boot up...
Click to expand...
Click to collapse
Which ROM is this? And since you've already wiped the SD card once and the ROM won't boot, why not just flash the factory image so you'll have a clean slate to start with?
Factory image = Official firmware?
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
MrTooPhone said:
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
Click to expand...
Click to collapse
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
First flash system firmware.. then flash TWRP recovery.. then Flash BETA-SuperSU-v2.62-3-20151211162651.zip SuperSU Package.. Done..
sieze.s said:
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
Click to expand...
Click to collapse
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Did the same thing
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
I did the same thing could someone help me? I updated to 6.0 a couple days ago (I just got the phone) and decided to unlock the bootloader. Everything worked fine. I have minimal ADB and fastboot set up and all the drivers are set up properly too.
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
dcalf94 said:
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
Click to expand...
Click to collapse
You should not have installed supersu. Not sure why that option exists.
MrTooPhone said:
You should not have installed supersu. Not sure why that option exists.
Click to expand...
Click to collapse
What can I do to fix it?
dcalf94 said:
What can I do to fix it?
Click to expand...
Click to collapse
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
MrTooPhone said:
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
Click to expand...
Click to collapse
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
dcalf94 said:
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
Click to expand...
Click to collapse
If you are going to reflash, why not 6.0 firmware?
Is flashing my only option since I have no back-up?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
Did you look at http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 or http://firmware.center/firmware/Motorola/Moto G (3rd gen-2015)/Stock/
dcalf94 said:
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
Click to expand...
Click to collapse
You also may want to look at http://forum.xda-developers.com/2015-moto-g/development/rom-stock-motorola-rom-collection-t3296964
MrTooPhone said:
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Click to expand...
Click to collapse
Yes you can.
Edit - My phone was also stuck at this screen only - "Warning Bootloader unlocked"
I also soft bricked my phone 3-4 days ago but got it back.
Follow below steps and you are good to go -
1. Download and install Motorola Moto Drivers
2. download stock firmware from http://forum.xda-developers.com/2015...mages-t3169639 for your Moto G3 model (in my case it was XT1550)
3. download TWRP from http://forum.xda-developers.com/devd...1051#downloads [ i used twrp-osprey-2.8.7-r5.img version ]
4. download SuperSU from http://forum.xda-developers.com/show...25&postcount=3 [make sure you download BETA-SuperSU-v2.62-3-20151211162651.zip version only else you'll again brick your phone]
Now as you have all required things to get your phone back, now follow below steps -
Now flash stock ROM, Instruction here -> http://forum.xda-developers.com/2015...ctory-t3187750
Now flash TWRP - fastboot flash recovery your_recovery_name_here.img
now start your phone (takes 15 minutes around)
now go to recovery and flash BETA-SuperSU-v2.62-3-20151211162651.zip and start your phone [ do not allow TWRP to root your phone when it asks you to root your phone just tap not now (or whatever i don't remember right now)]
Starting up phone now takes 25-30 minutes approx.
Rooted
[Don't brick and blame me , do it at your own risk ]
The point where things went wrong was that last screen where TWRP asks you if you want to root the phone - NEVER let it do that, ever, even after you properly root it the right way (which is manually flashing that specific version of SuperSU or a later version).
I've had instances where on a random reboot into TWRP - on a properly rooted Moto G3 - where that question screen comes up. It should not come up when the phone is actually rooted but I've seen it once or twice. Again, the point is: NEVER EVER let TWRP do it's own internal rooting process because that's what breaks things on the Moto G3.
- flash stock firmware complete
- go back and flash TWRP
- use TWRP to manually flash the SuperSU version (at least 2.62 beta which is what the Moto G3 running Marshmallow requires)
- make sure after that flash of SuperSU you do NOT use the TWRP option to root the device when you close out TWRP, ever
- flash a replacement logo so you don't see the bootloader is locked splash screen
That's about it.
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
guest_2011 said:
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
Click to expand...
Click to collapse
It is basically a factory reset. Not sure you need adb at this point.
MrTooPhone said:
It is basically a factory reset. Not sure you need adb at this point.
Click to expand...
Click to collapse
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
guest_2011 said:
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
Click to expand...
Click to collapse
same problem with me. almost an hour and the same page "BL Unlocked". how long did it take for your phone to spring back to life?