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 ??:'(
Related
Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.
i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.
Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!
Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.
just hold up like normal after
fastboot reboot
ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.
Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.
arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>
Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !
Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app
4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:
I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.
Guys I'm new to the forum as a writer.
I read threads here since 2013 and until this week all that I want was in one of those.
So let me explain the problem and what I've found and execute.
Device is a XT1033 running 5.0.2 OTA, no mods, bootlocker locked, not rooted, debug off, just an normal user. The device ran out of battery, and when boot up normally after the logo then the black screen (several threads about this), now and then the device boots normally but show an error called process.goggle.phone.com,.
Now what I've done tried to flash various 4.4.4 roms and higher, flash boot.img, flash recovery.img, custom recovery, adb sideload, wipe data, wipe cache, flashall, and nothing seems to even change whats in the emmc.
Currently I´m with unlock bootloader, I used device info and was able to retrieve some info these are in the first picture, I´m @ work right now, but if you guys need I can póst a log of device info.
My doubts are there is a way to enable debug mode from fastboot enviroment?
There is a way to root via some windows/linux tool?
When the device boots ot show mtp @ the windows but thats it, sometimes ot shows a !xt1033 in device manager.
I'll put some images here.
Can anyone help? I've read about blankflash, but not sure if it would work.
I was thinking about an otg solution via fastboot or something else.
HTCDreamOn said:
A word of advice: I strongly recommend temporarily booting any images (be it recoveries or kernels) you are about to flash to your device. This is simply a case of using the command "fastboot boot blahblah.img" whether blahblah.img is a recovery or kernel.
Click to expand...
Click to collapse
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
purplepizza said:
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
Click to expand...
Click to collapse
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
HTCDreamOn said:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
Click to expand...
Click to collapse
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
acejavelin said:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
Click to expand...
Click to collapse
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
purplepizza said:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
Click to expand...
Click to collapse
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
purplepizza said:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
Click to expand...
Click to collapse
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
acejavelin said:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
Click to expand...
Click to collapse
Just curious, how did you go from 5.1.1 to 6.0?
purplepizza said:
Just curious, how did you go from 5.1.1 to 6.0?
Click to expand...
Click to collapse
OTA... part of soak test on December 22.
acejavelin said:
OTA... part of soak test on December 22.
Click to expand...
Click to collapse
Hey thanks for helping to answer this, your explanation was much better I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now.
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.
I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
purplepizza said:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
Click to expand...
Click to collapse
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
acejavelin said:
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
purplepizza said:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
Click to expand...
Click to collapse
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
HTCDreamOn said:
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
Click to expand...
Click to collapse
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
purplepizza said:
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
Click to expand...
Click to collapse
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
acejavelin said:
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
Click to expand...
Click to collapse
Any recommendations how to proceed?
I also need help with my soft bricked moto g3
Moto g3 (xt 1550, Indian dual sim 16 gb version)
I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).
I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery
So I first successfully unlocked my bootloader using the official motorola method.
I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.
I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).
Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.
However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader. I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.
Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.
I can press vol down+power and enter fastboot , where adb works fine.
I can enter stock recovery from the fastboot sceen too.
Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.
USB Debugging is also enabled, and I have a backp of my sd card data.
I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.
Is there any way I can unbrick my device and- (in decreasing order of preference)
1. Keep my stock rom and recovery?
2. Keep stock rom with twrp? (It should not be a problem)
3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.
Also, is SELinux involved anywhere with my phone getting bricked? I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good:
purplepizza said:
Any recommendations how to proceed?
Click to expand...
Click to collapse
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
acejavelin said:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
Click to expand...
Click to collapse
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.
Can you think of any reasons not to try fastboot again the re-flash TWRP?
Good day, its my first thread here, so I'm sorry for my english and terminology.
My Photon Q had CM-13-Nightly installed, bootloader unlocked and Clockwork recovery installed. Everything was working fine, till few days ago. Phone was left unused with drained battery, so I charged it and powerd on. After that, all app started to crash one after another. I was trying to do factory reset from recovery, erase everything from bootloader menu or using bootloader commands (bootloader erase data, bootloader -w) but nothing worked. I still have my system, with same apps, wallpaper etc and apps still crash. Are these all symptoms of damaged partition or internal storage? Will be thankful for any help
Erasing in bootloader/fastboot mode can be dangerous... be careful.
I would just factory reset and reinstall the ROM. Don't use ClockworkMod for recovery tho, use TWRP. CWM hasn't had updates in a long time (and frankly I'm surprised it was able to flash the latest CM).
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
greedo85 said:
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
Click to expand...
Click to collapse
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
HTML:
C:\fastboot>fastboot flash recovery twrp-2.3.0.0-asanti_c.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6702 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 1.786s]
finished. total time: 2.298s
arrrghhh said:
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
Click to expand...
Click to collapse
greedo85 said:
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
Click to expand...
Click to collapse
I think you can safely ignore the bootloader message.
As for flashing TWRP, did you boot TWRP immediately after flashing, or did you boot Android?
I believe you need to make sure you boot TWRP immediately after flashing, otherwise CM Recovery will blow it out.
After flashing TWRP hold power until the device shuts off, release, and now hold power + vol down to enter recovery. Please use the latest version of TWRP from kabaldan, or the latest official TWRP.
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
greedo85 said:
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
Click to expand...
Click to collapse
Sorry it's power + vol UP (according to my own guide...)
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
greedo85 said:
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
Click to expand...
Click to collapse
I'm not sure why people have issues with this... I always thought it was how they 'completed' the flashing process. I don't recall being able to reproduce the condition.
Perhaps boot Android then boot TWRP? Or try to reboot directly to recovery from the fastboot cli? Try something different... or just fastboot boot the TWRP image? There is a problem in the process, I'm just not sure 'where' since I don't have the phone in front of me.
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
greedo85 said:
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
Click to expand...
Click to collapse
IIRC this device will let you 'fastboot boot' images directly - I think I suggested this - have you tried it?
I'll dig around and see what else I can find from the TWRP thread. I was pretty sure it had to do with the process, but I could be mistaken.
Edit - I'll flash CM Recovery on my old Q and see if I can recreate this as well. It's always bothered me...
How would I boot images directly? From where?
greedo85 said:
How would I boot images directly? From where?
Click to expand...
Click to collapse
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
arrrghhh said:
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
Click to expand...
Click to collapse
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
greedo85 said:
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
Click to expand...
Click to collapse
I guess they only allow fastboot booting kernels... at least I used to do that on this device.
So I just flashed CM Recovery no problem. Going to flash back TWRP.
Is there anything I can do now to put this phone back to work?
greedo85 said:
Is there anything I can do now to put this phone back to work?
Click to expand...
Click to collapse
I'm... kind of at a loss. Make sure you have the latest TWRP. I just downloaded the latest CM Recovery, fastboot flash recovery <cmrecimg> and it rebooted to Android on its own. I reboot to recovery, CM Recovery is installed. All good.
I reboot to bootloader mode, grab the latest official TWRP, fastboot flash recovery <twrpimg>, this time when I unplugged it was still in fastboot mode. So I hit the power button, phone turns off. Then I hold power + vol up until I see the screen turn on. Continue to hold vol up, but release power. Then when the screen dims (or when recovery starts if you can't tell) release vol up.
Maybe that'll help you? Good luck.
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
greedo85 said:
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
Click to expand...
Click to collapse
Dunno why it would make any difference at this point, but have at it.
I would REALLY appreciate help if possible. I'm trying to recover my honeymoon pictures from a Pixel that freezes as soon as it boots.
It has the locked, original bootloader, but debugging is enabled. Sailfish Oreo 8.1.0/OPM1.171019.012/4470837 installed.
I thought after enabling debug that I could adb shell or adb pull files in recovery mode, but I can't figure out how (assuming it's possible). I can boot into "no command" recovery, and get into the Android Recovery menu with "Apply update from ADB", "Mount /system", etc. I've even upgraded the OS with adb sideload successfully...
But booting into Android, it freezes almost always on the "G" loading screen...but rarely, it will display the clock and notifications and immediately freeze. Even more rarely (like once in a thousand boots), it will give me maybe 10 seconds before it freezes. The last time it did this, I had just enough time to enable dev options, enable debugging, and "always enable with this computer"...then it froze.
What are my options or the most likely way to recover my files? Is there anything I can do from recovery, or if I get another 10 seconds in Android, is there anything I should try?
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
KittyRgnarok said:
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
Click to expand...
Click to collapse
Thanks for the suggestion! I'll try this tonight, but I worry it won't work since my bootloader is the original and locked. If I understand correctly:
- you need an unlocked bootloader to do "fastboot boot"
- you have to factory reset and wipe all your files to unlock the bootloader
Is that not true?
Yes, it looks like I can't "fastboot boot" because it's not unlocked. Everything I've found says unlocking should wipe my device.
Is there any way to boot an img or get to adb shell/pull without wiping it?
Code:
>>> fastboot boot twrp-3.2.1-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.868s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.967s
Oh yeah I forgot about that. Uhhhhh no I think ur boned sorry
are you sure you did not have google photos automatically backing up your photos?
mruno said:
are you sure you did not have google photos automatically backing up your photos?
Click to expand...
Click to collapse
Yes, I'm sure. I was away from any connection on my honeymoon and it crashed right before coming home.
If your phone is under warranty still you can likely RMA it to get a phone that isn't bootstuck but as far as the data I think it's pretty safe to say you can't access it unless you have already disabled forced full disk encryption prior(which I'm not even sure is safe to do on these devices).