Related
hi guys,
system win7x64, moto g retail uk
in order to root i unlocked the bootloader from motorola page. successfully unlocked and rooted but...
problem nr 1 - from that day i was unable to access recovery by any means. every time i accessed it the withe screen with the motorola warning after unlocking came and nothing happened. i discovered this thread forum.xda-developers.com/showthread.php?t=2585755 and was able to change the boot logo from that screen to a regular one, but the problem persisted. tried to solve the problem and came to this thread forum.developers.com/showthread.php?t=2037808. "There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it."
converted that install_recovery.sh to bak and rebooted.
problem nr 2 - no access to recovery. lost root privileges. no acess to bootloader. the phone does a full reboot everytime (goes on reding every android app).
tried to upload an new "install_recovery.sh" (the same but renamed) but have no privileges through airdroid.
any suggestions highly appreciated. can i push the file through adb or sanything else?
after opening /system/etc/install-recovery.sh with notepad it reads like this. i guess it was changing the name from .sh to .bak that broke rooting
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh
install-recovery.sh is altered by superSU. You lost root as this file is required for root.
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone.
Anyway - without root the only way to get the file back in place is to flash the file (ie as a flashable zip) from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Maybe search XDA and see if there is some other key combination to access bootloader.
scott_doyland said:
install-recovery.sh is altered by superSU. You lost root as this file is required for root. RIGHT! I altered its extension to .bak, rebooted and lost root access
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option. Really dont know if that was the mistake. I lost recovery access (but not bootloader) immediately after unlocking the bootloader, when i saw the screen turning blue/violet i took the usb cable and it might have been the mistake.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow. I altered the boot logo because everytime i tried to acess recovery the phone gave me the motorola warning and didn't go to recovery, just booted, after altering the logo the behaviour stayed the same, no recovery, juts normal booting.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone. Yes, no bootloader by any means, the phoe just cold boots and checks every app (it takes a lot of time)
Anyway - without root the only way to get the file back in place is to flash from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Click to expand...
Click to collapse
Right. Already tried different forms of adb (mount, remount, su, push, but NADA). Didint go for the custom recovery because i'm noob and dunno what it is (yet) but i'll try to find out. If you can guide me i any direction i really appreciate :good:
Despite all this mess, at least i hope this knowledge serves the community.
If you can't access bootloader and no longer rooted I don't think you are going to be able to flash a custom recovery anyway (custom recovery allows you to backup/restore entire device and flash ROMS).
Without bootloader access you are in a mess as can't access recovery and can't root.
You can't even reflash entire stock ROM inc recovery etc.
Basically unless you get bootloader access you are screwed AFAIK.
Hopefully someone else may have an idea.
As I mentioned before - search XDA and see if there are some button combos that may get you to bootloader rather than normal combos. Or any button combos to hard reset bootloader etc. It doesn't look good though.
screwed is the word scott. at least its a "normal phone", for now, it works normally, the only drag is the slow booting everytime i shut it down, oh and it doesnt shutdown, just reboots
scott
i have bootloader again, dontt know how but i do. can you point me how to root the phone again?
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
scott_doyland said:
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
Click to expand...
Click to collapse
Thanks Scott.
The situation got a little worse. Now SO (w7x64 and x32 i have both) do not recognize moto g. I connect usb cable and it only charges.
- if i connect it while off it reboots (every time rebuilds dalvik cache)
- if i connect it while on it only charges but windows doesn't make any sound (nothing at device manager)
- if i connect usb cable (while in bootloder screen) windows recognizes it only as android adb but not as media player (drivers installed). when i do 'adb devices' nothing comes although the phone says usb connected.
at settings i have USB-MTP, USB debugging enabled.
i can power off and acess bootloader screen but at that screen if i choose any option it just cold reboots. no recovery acess, nada! no adb acess.
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
scott_doyland said:
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
Click to expand...
Click to collapse
It was a good tip Scott, it kept me walking and this morning i was about to give up :good:
Below you can see what happened. I flashed cwm (for 4.4.2) successfully but when trying to access it phone cold reboots as usual. Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it?
...\root motorola>fastboot devices
TA8830L7VY fastboot
...\root motorola>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7604 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.461s]
finished. total time: 0.728s
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.267s]
booting...
OKAY [ 0.504s]
finished. total time: 0.772s After this it does a cold reboot
you said i could re-flash a stock image. the phone came with 4.3 but in the meanwhile upgraded to 4.4.2. can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2?. i managed to download both firmwares.
Having read that 4.4.2 bootloader is having trouble with accessing recovery (my case also) i tried to upload 4.3 bootloader. this was the result
...>fastboot-moto-windows.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.836s]
finished. total time: 1.934s
...>fastboot-moto-windows.exe reboot-
bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
i guess everything went right. the phone didnt a cold reboot and went right away to the bootloader. after selecting recovery in this new bootloader i finally managed to have acess to the last CWM 6.0.4.6 recovery. UFFFF!!!
After that i did a wipe cache partition and rebooted. Phone did a cold reboot. after that i follwed the post you mentioned and flashed SUper SU.through CWM
As seen before after renaming install-recovery.sh to .bak root was lost I checked and the file is there again along with the bak so i guess super su created it again.
Check list: Have bootloader. have recovery. have root, i'm on 4.4.2 with 4.3 bootloader. one thing thats not ok, everytime phone reboots android goes on with the following message "android is upgrading --- optimising app x of y" which takes a lot of time. even if i ask for a fast reboot. that was not the usual procedure, the phone just did a fast reboot and nothing more. any advice on this one?
What a enormous trip for someone that didnt knew much about this. Kudos to you for keeping the help!
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone.
You said you already wiped cache via CWM but may as well wipe that again as well.
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort).
To attempt to answer your other questions:
***************
** can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2? **
I think so, if you have the entire firmware it includes recovery, bootlloader, android, radio images, kernel etc so flashing it in the correct sequence as can be found in other threads should give you complete 4.3 as it was out of the box. However please read other posts related to this as its not something I have done or have read much about.
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself?
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Good morning Steve, thanks for your helpful info, once again.
scott_doyland said:
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone. Again, the same messages.
You said you already wiped cache via CWM but may as well wipe that again as well.
At CWMR there's also these options besides dalvik cache, a) wipe data/factory reset and wipe cache partition. factory reset is pretty obvious, it cleans all your data but does not fully restore 4.4.2 functionality (or does it? and it goes back to 4.3). Wipe cache partition is the same as settings/storgae/cached data?
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort). Does it go back to 4.3?
To attempt to answer your other questions:
***************
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc. It might not be "entire". What i have 4.3 is 400MB, 4.4.2 is 180 MB, might be an upgrade.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone. it didint in 4.4.2, now it does.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue. I did, but without sucess.
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself? Both things failed, the phone just rebooted.
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick. it did not.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root. I probably will take that road.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root. Yes, at least i know that works.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Click to expand...
Click to collapse
In brief: Rebooting problem persists even when wiping dalvik cache twice. Now the device is not recognized in windows. Neither on desktop pc w7x64 nor laptop w7x32. have motorola drivers on both. It used to recognize device as mtp (media player xt1032) but not anymore. When connected in bootloader device manager recognizes as android adb. I feel the problem is from the phone and not SO. I'll try to fix it this morning.
If i reflash 4.3 do i have to do anything before? Wipe something? Do a nandroid backup? Do a normal backup? I have a few backup apps but never used any of them.
Great appreciation for your help Steve. Have a nice Sunday.
About the phone not being recognized as mtp, after a brief search it has to do with locking. If it's locked then windows explorer is denied any access for security reasons. As soon as i unlocked it windows recognized the device immediately. -1 problem. only the rebooting stuff now.
:good:
rebooting ptoblem
wyped dalvik and cache data several times
also wiped odex files
fixed permissions in rom manager
behaviour persists. after wiping, the phone goes "upgrading android - optimising 225 apps" after that when rebooting the phone goes "android is upgrading... - optimising 103 apps". factory reset as last resort sigh... i hate that :crying:
I am having the same issue with the phone being boot loader unlocked and when I try to get into recovery through fastboot it just reboots.
Do you have the stock files that you used along the way?
Thanks. I have never had a phone give me this much hassle before ??:'(
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Nastybutler said:
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Click to expand...
Click to collapse
you need to unlock the bootloader
Daniele12 said:
you need to unlock the bootloader
Click to expand...
Click to collapse
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
VijayBais said:
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
Click to expand...
Click to collapse
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Keithn said:
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Click to expand...
Click to collapse
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
VijayBais said:
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
Click to expand...
Click to collapse
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Keithn said:
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Click to expand...
Click to collapse
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
I know this won't help VijayBais, but after a while I guess the stock kernel and everything settled in and it stopped random restarting and when I did restart, after installing apps and whatnot, it booted right back up. Now that I'm on 5.1, I haven't had any issues with it freezing up, or random restarts. Crisis averted.
VijayBais said:
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
Click to expand...
Click to collapse
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Keithn said:
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Click to expand...
Click to collapse
No, I haven't done any factory reset till now.
Even the recovery option doesn't proceed to further options on bootloader page.
You can't get into the recovery menu? When you chose it and get the dead android do you quickly tap the power+volume up combo?
Hi,
I am totally lost and need help to get my personal data (images, videos most important) back from my bootlooping phone.
I browsed the privacy guard settings and disabled some boot and caller rights for google services and google play (with the intention to prevent it from looking up for updates constantly and drain my battery).
Then it restarted itself as I plugged it in for charge and is bootlopping since.
I have no root, the latest official CM update and a the build in Cyanogen recovery, since it came out of nowhere no usb bugging enabled (I believe).
When I try to enter the phone via ABD sideload from the CM Recovery "pull" my folders it says error:closed. adb backup wont work either.
It tells me: adb: unable to connect for backup: closed
This whole topic is kind a new for me - I never was in that situation and for now all I want is my images and videos back from my phone at least. I will try any method to save them.
I hope some can help me - I don´t know what to do anymore
This should theoretically work.
Flash TWRP by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Thank you so much for this hint!
I will try that.
So I Just change my recoverer with this method right? This is possible without root and usb debugging?
Joshwin Aranha said:
This should theoretically work.
FlashTWRP] by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Click to expand...
Click to collapse
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Sore6 said:
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Click to expand...
Click to collapse
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Joshwin Aranha said:
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Click to expand...
Click to collapse
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Sore6 said:
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Click to expand...
Click to collapse
I was just about to say to try booting into the recovery, follow @nitrobg's instructions, get the recovery and instead of flashing the recovery, just try booting into it, command is
fastboot boot recovery.img
Hope it helps you, the pain of losing precious data isn't unknown to the best of us
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
Click to expand...
Click to collapse
I disabled some google play and google services from booting via the official cm privacy settings
Reason was to disable the battery drain by play when searching constantly for GOOGLE android updates...
Needed to disable that in cm12 back then and it helped.
nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
I will try that! Thank you.
I get back here with the result.
nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
Unfortunately it gives me this in the commandline:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.430s
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
nitrobg said:
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
Click to expand...
Click to collapse
Sadly no - all adb commands end in "error:closed"
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
nitrobg said:
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
Click to expand...
Click to collapse
Didnt work because as far as i know one has to be in the android ui - hold pwer off key and then hold the restart menu item and then the volume buttons + power buttons code should work.
Thanks anyway - i wiped it now.
it works but all data is gone
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
nitrobg said:
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
Click to expand...
Click to collapse
Honestly - I held it for 4 Minutes. There was a Vibrate Signal everytime it wanted to boot up into android but it didnt. Then it kept the cynogenmod loader til the next little vibration. It was a loop with no entry to android GUI
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Joshwin Aranha said:
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Click to expand...
Click to collapse
Thanks man - jeah I took care of such case beforehand now and rooted, bought titaniuam backup and enabled usb debugging instantly...
Also I am now using TWRP.
Lesson learned.
Thanks to you all for helping me!
I am really thankful for your effort.
Kind regards
Some kind thanks on my replies maybe ?
Haha, anyway. Take care.
Ive scoured the web for the solution to this but for the life of me can not get my boot loader to unlock. I know enough of this to get me by, but obviously I am not an expert by any means. This is one of the pre recall tablets that I had rooted to avoid the kill code. It was so long ago when I did this that I don't completely remember how I did it. But apparently I didn't have to unlock the bootloader to root it.
I haven't used this tablet in ages and decided to pick it up again but was getting errors that I needed to update google play services but it was not allowing me to do so. I have the Custom Rom Blisspop installed but it appears that they have quite support for it. So I was going to wipe that off and load Lineage. so I tried to get into recovery and it kept just stalling at the loading screen. So now I am wondering if I even flashed a recovery to it to make a backup. Regardless I wouldn't want to restore and risk getting the kill code delivered.
So the next thing I tried to do was flash twrp (and yes I did use the NVidia shield tablet version) and it said that it was successful but still could not boot into recovery. Then I noticed that it said my bootloader was locked on the bootloader screen. So I installed the platform tools and the drivers and adb was recognizing my tablet and everything was good. Until.... I did "adb reboot bootloader" and then "fastboot devices" or even "fastboot oem unlock" nothing worked. No devices would show up. But this whole time adb works. No matter what drivers I install or anything, I cannot get fastboot to recognize the device. I even changed the USB port to the back of my pc straight off the mobo and ran the cmd as admin and nothing is working.
I am starting to get discourage that my efforts are going to be for naught. Expecially since I am not sure exactly how I rooted it in the first place? which is completely my fault for not documenting it. Any and all help is greatly appreciate and I apologize if this has already been solved else were or is being posted to an incorrect location.
Thank you!
Brandon
Ok, i finally figured out that the fastboot driver wasnt working. I ran "adb reboot bootloader" and while in fastboot mode, i found in the PC's device manager that there was an error with the driver. I manually updated it and i am finally able to successfully run "fastboot oem unlock".
But now im getting an error with it saying it failed....
Code:
C:\WINDOWS\system32>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I am unsure what this means and will do some more researching. I will post back if i make any headway. Once again, i thank anyone in advance for any assistance they may be able to provide.
Apparently i had to unplug the tablet after installing the driver for fastboot before "fastboot oem unlock" would work. But it now says "Device = unlocked"!!!! hopefully i dont mess anything else up...
So now the tablet is "unlocked". I went to do "fastboot flash recovery twrp.img" and said it succeeded. I then proceeded to to do "fastboot reboot" and read that you should immediately load back into bootloader because some tablets will overwrite the recovery to stock if twrp isnt given a chance to correct this. So i did just that then volume keyed down to recovery and its back to doing the same thing where i am stuck on the nvidia logo loading screen. Does anyone have any suggestions on a fix for this? It appears that the tablet is refusing to enter recovery mode?
The reason why i need to get into recovery is for A: to make a backup. and B: to clear my current blisspop rom so that i can load a different Rom. I doubt it would be a good idea to install an OS on top of another OS. But who knows, maybe thats fine?
Code:
C:\Users\bwach>fastboot flash recovery twrp.img
target reported max download size of 570425344 bytes
sending 'recovery' (12426 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.579s]
finished. total time: 1.015s
C:\Users\bwach>fastboot reboot
rebooting...
finished. total time: 0.004s
Once again, I thank you for the help.
I was up all hours of the no ight last night trying to solve this with no luck. Is there anyone here who might be able to help me?
Still can't get recovery to load... Tried everything. I did "fastboot - w", I tried flashing lineage on top of bliss pop. Nothing I do will give me access to recovery...
Any ideas?
You have to use hardware keys combination (power + volume + or - not sure exactly which) to boot to twrp for the first time after flashing. So hold the combination while you're still in fastboot (bootloader) mode and release when you see nvidia logo. Good luck
Edit : fastboot reboot is a command that takes you to system, not recovery, to reboot to recovery by using commands you habe to type fastboot reboot recovery. But still, I believe you have to enter for the first time using the buttons combination but it may work with fastboot reboot recovery
It's possible the bootloader is too old for the current twrp release to boot. Which version of android is on the tablet? If it's like L, then you'll have to either update the bootloader manually or update stock first, then twrp will work. There's a note about this on the twrp device page.
I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.
Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.
Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.
Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk
It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse
domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse
And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock
In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it
Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.
Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.