Develop Bugs

Having trouble with recovery and download mode

I got a hand me down S3 since my old phone (ancient infuse 4g) recently broke. It works fine at the moment, but I can't seem to get anything to work properly in terms of roms/odin/any customization.
Booting into download seems to work, as I can flash things in ODIN, but it shows a black screen. I've been using adb boot download to make sure I'm going into the right mode. ODIN shows success when flashing stuff, but I'm not so sure.
Booting into recovery just shows a black screen. Flashing to stock recovery, cwm, or twrp doesn't seem to change anything.
I can't get any of the root methods to work since I can't get into recovery. I found a rooted stock image that's current but it's in zip form, and since you can only install zip files from recovery, I can't use it. I tried a convert to tar utility but that also didn't work.
I've done a factory reset, and managed to wipe everything the one time I got into stock recovery (when I first got the phone). After that, any attempts to root, get back to stock, or do anything really but turn it on and use it, aren't working. I also tried towelroot, which worked once, then I reset the phone and towelroot no longer worked- probably due to a kernel upgrade.
A lot of the posts I found, including one about Kies, all dealt with older versions and possible bricking when downgrading bootloaders so I wanted to make sure before I did anything dumb.
Oh, and using rom manager to try to install cwm just freezes at 'flashing'. the twrp utility whose name I forget (replaced goo manager) just freezes as soon as I open it. I've also tried multiple usb ports, and made sure to only use ones directly connected to the mother board.
I'm running ucufnj1. Maybe if I had an odin flashable version of that?
What do?

Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.

audit13 said:
Did you try flashing a custom recovery in Odin? When it finishes flashing recovery, do not let it reboot. Just remove the battery and try booting into recovery.
I recommend using Philz Touch for the d2lte.
Click to expand...
Click to collapse
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.

Please help!

yoonietang said:
I tried that with cwm and twrp, removing the battery and all, but I got a black screen with both. Just an unresponsive black screen.
Click to expand...
Click to collapse
Are you checking auto-reboot in Odin?

audit13 said:
Are you checking auto-reboot in Odin?
Click to expand...
Click to collapse
I make sure auto reboot is unchecked, then I take the battery out and try to start into recovery. I'm also having trouble booting into download mode with the button combo (vol down, home, power) so I've been using adb reboot download to do it.

Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.

audit13 said:
Can you use adb commands to enter recovery?
Have you tried flashing the latest Philz Touch doe thr d2lte? I highly recommend it.
Click to expand...
Click to collapse
Doesn't work =( Still getting the same black screen when I try to get into recovery.

If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.

audit13 said:
If you can somehow manage to get into download mode, let me know what it says on the screen. The important thing is to make note of the model # and the presence of a warranty bit line.
If you can't get into download mode, try installing the Samsung Info App from the Play Store and use the app to find your bootloader and modem version.
Click to expand...
Click to collapse
I honestly can't tell if I'm getting into download mode or not. I *think* I'm getting into download mode except with a black screen for some reason, as ODIN claims success when flashing stuff. I also used adb reboot download to eliminate any doubt about holding the right buttons to access it, so that helps narrow down the possible source of the problem. I believe my dad (previous owner) had the screen replaced at some point. Could this be a wobbly connection?
Phone model is sgh-i747rwbatt.
Bootloader, Baseband, PDA, and CSC versions are all UCUFNJ1 (csc is i747attfnj1).
I can't seem to find modem version- is that baseband? Modem model is MSM8960.

Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
just had to go there. 1st three google search results for sgh i747rwbatt pulled up a white S3. (?). never knew or heard of.
"all i can really do , is stay out of my own way and let the will of heaven be done"

audit13 said:
Weird but the AT&T S3 is the sgh-i747. There should not be any letters or numbers after the second 7.
In download mode, are you seeing the Android guy? Are you sing the button combination or fastboot commands to get into download mode? USB debugging must be on to use fastboot commands.
Click to expand...
Click to collapse
usb debugging is on. Download mode just shows a black screen, nothing at all, whether I use adb reboot download or the button combo to get into. Odin reports that it sees the phone though.

would like to get @audit13 opinion on this , but you can use flashify and mobile odin to flash with. i have no experience with mobile odin and have only used flashify for .img and not .zips. he might be more knowledgeable about these apps performance records.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.

audit13 said:
Since the LCD remains black when you boot into download mode, I assume you obtained the phone information using the Samsung Phone Info App.
Are you able to issue fastboot commands in download mode? In download mode, does fastboot devices return your phone?
Unfortunately, I know nothing about mobile Odin or Flashify. I have never used these tools and don't have an s3 anymore.
Click to expand...
Click to collapse
Fastboot commands don't work. I tried installing the fastboot drivers, but I still get nothing returned when I try 'fastboot devices', so I couldn't try any of the other fastboot commands. I'm not 100% sure if it's the drivers on my PC or the phone that's the issue, since a lot of the samsung/google drivers seem a bit finicky, but I did install minimal adb and fastboot from this forum.
Yes, I used the samsung phone info app (it's not official, right? It's made by vndnguyen?).
In regards to odin mobile and flashify, when I googled flashify (someone else mentioned it on reddit when I asked there) it said it required root. Unfortunately, I still can't get root due to the recovery issues, or I'd be able to use any number of methods.

When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?

audit13 said:
When you try to enter download mode, do you see the warning screen where you press the volume key to continue to download mode?
Since you can't issue fastboot commands, this leads me to believe that the phone may not be entering fastboot mode. In fastboot mode, you may be able to push a recovery image to the phone.
Could you post a screen shot of your Odin screen with the phone connected?
Click to expand...
Click to collapse
When I boot into download or recovery, there is nothing but a black screen, nothing else at any point at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again, nothing but a black screen when I boot to recovery or download. I do get the vibration to confirm the device turning on though.
Also a screenshot showing fastboot

When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.

audit13 said:
When using the button combination for download mode, I believe the first screen you see is a warning screen, then you need to press the volume + key to enter download mode. Are you pressing the volume up key?
Open Odin, flash recovery, and then take a screen shot of the Odin screen after it finishes flashing recovery. This may provide more clues as to what's happening.
Click to expand...
Click to collapse
Same when I try twrp of philz touch. However, when I flashed philz and then booted into recovery, I get a vibration when I touch the screen. This leads me to believe that the recovery is active, but the screen is off for some reason. Maybe if someone could walk me through flashing an image from recovery, step by step, I could do it blind?
Also, it seems that booting into download via key press requires you to press the volume up button to active download mode but using adb reboot download does not (based on when odin/my PC detected the phone entering download mode). Regardless, I tried both ways.
Edit: I copied and pasted the OP from another forum, and didn't realize it cut something off- I believe that my dad at some point had the screen replaced. Could it be a loose connection? It seems unlikely since I managed to get into recovery once when I first received the phone.

Nokia N1, wiped system, stuck on splash screen (Powered by Android) (Update!)

Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.

Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.

do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it

2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.

It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk

do you have full ROM for N1 tw or cn, if you have this can you share for me plêas

i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke

2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you

Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.

srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?

defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/

same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2

Question [SOLVED] Brick after beta

Hi guys,
So I have a pixel 6 pro, decided to join beta, but since all apps kept crashing afterwards (even after a reboot and reinstalling some apps) I decided to go back to stock. This is all just google-supported.
I got opted out from beta, got a rollback on my phone, that's where the terror began...
During download (in my phone) of the ota, it said: something went wrong, and it rebooted. It was 100% not in the process of installing, just downloading. Now I'm stuck at bootloader and if I do a wipe data/factory restore, I get multiple errors:
Unable to enable ext4 verify on /block/dev/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing
open failed: /metadata/ota: no such file or directory.
If I try to use the webbased flash tool, it says:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device.
However I am 100% sure it was enable before. Maybe the beta unset this?
In addition, if I do "fastboot flashing unlock" I get a 'flashing unlock not allowed'
no matter what I try, it I to 'reboot system now', I just end up back in the bootloader.
I haven't done anything, I wanted to consult you guys first.
Many thanks!
v0id

Sorry to hear about the nightmare. IF OEM unlocking truly isn't enabled, then this won't work, but it's worth a try: Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Was your bootloader actually unlocked? If it was already unlocked, then nothing can reverse that other than the command to relock the bootloader. I think I recall hearing of some people who disabled OEM unlocking after they unlocked the bootloader, and that might've caused problems, but if you didn't take any action to re-lock the bootloader then it should still be locked. Do you still get the warning when you boot that the bootloader is unlocked?

v0id said:
Hi guys,
So I have a pixel 6 pro, decided to join beta, but since all apps kept crashing afterwards (even after a reboot and reinstalling some apps) I decided to go back to stock. This is all just google-supported.
I got opted out from beta, got a rollback on my phone, that's where the terror began...
During download (in my phone) of the ota, it said: something went wrong, and it rebooted. It was 100% not in the process of installing, just downloading. Now I'm stuck at bootloader and if I do a wipe data/factory restore, I get multiple errors:
Unable to enable ext4 verify on /block/dev/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing
open failed: /metadata/ota: no such file or directory.
If I try to use the webbased flash tool, it says:
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device.
However I am 100% sure it was enable before. Maybe the beta unset this?
In addition, if I do "fastboot flashing unlock" I get a 'flashing unlock not allowed'
no matter what I try, it I to 'reboot system now', I just end up back in the bootloader.
I haven't done anything, I wanted to consult you guys first.
Many thanks!
v0id
Click to expand...
Click to collapse
did you try flashing a FULL OTA zip?
try to get to recovery mode and follow the instructions:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

Which directions are you following?
The command is "fastboot oem unlock".

LLStarks said:
Which directions are you following?
The command is "fastboot oem unlock".
Click to expand...
Click to collapse
Not for newer devices, according to Google

Freak07 said:
did you try flashing a FULL OTA zip?
try to get to recovery mode and follow the instructions:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
Hi,
So after a restless night, I found this to be the actual solution. I couldn't ADB into the device just like that, nor would the phone start recovery mode if I chose it. I had to go into rescue mode > press power + vol up, to get recovery, then do adb sideloading, THEN I was able to ADB into the device from my laptop. Since the device was android 13 beta, I wasn't able to sideload just any image, it kept saying it wouldn't do a downgrade. Fortunately, the June update that was just released (also as OTA) got succesfully sideloaded onto my phone and afterwards the phone booted into the OS. I immediately turned on OEM unlock and USB debug in dev options, because one never knows what might happen to the pixel :/
None of the unlock commands worked, adb nor fastboot. Hence android flash tool NOR the android pixel repair & update site worked because the phone was still considered OEM locked.
So I closed the Google device-support case I had opened in the meantime. Funny thing, after explaining everything in a document, with screenshots, they advised to use flash.android.com to reset my phone... well..... if it only were that easy I wouldn't have opened the case in the first place huh
Anyway, thanks for your replies all!
PEACE

v0id said:
Hi,
So after a restless night, I found this to be the actual solution. I couldn't ADB into the device just like that, nor would the phone start recovery mode if I chose it. I had to go into rescue mode > press power + vol up, to get recovery, then do adb sideloading, THEN I was able to ADB into the device from my laptop. Since the device was android 13 beta, I wasn't able to sideload just any image, it kept saying it wouldn't do a downgrade. Fortunately, the June update that was just released (also as OTA) got succesfully sideloaded onto my phone and afterwards the phone booted into the OS. I immediately turned on OEM unlock and USB debug in dev options, because one never knows what might happen to the pixel :/
None of the unlock commands worked, adb nor fastboot. Hence android flash tool NOR the android pixel repair & update site worked because the phone was still considered OEM locked.
So I closed the Google device-support case I had opened in the meantime. Funny thing, after explaining everything in a document, with screenshots, they advised to use flash.android.com to reset my phone... well..... if it only were that easy I wouldn't have opened the case in the first place huh
Anyway, thanks for your replies all!
PEACE
Click to expand...
Click to collapse
Just one question, were you complete stock before enrolling in A13 beta program? By stock i mean locked bootloader and not activating unlock button in developer options.
Thanks

Just got in this today and I'm not able to do it. How did you do the adb sideload?
I can't do it in fastboot or in rescue mode
v0id said:
Hi,
So after a restless night, I found this to be the actual solution. I couldn't ADB into the device just like that, nor would the phone start recovery mode if I chose it. I had to go into rescue mode > press power + vol up, to get recovery, then do adb sideloading, THEN I was able to ADB into the device from my laptop. Since the device was android 13 beta, I wasn't able to sideload just any image, it kept saying it wouldn't do a downgrade. Fortunately, the June update that was just released (also as OTA) got succesfully sideloaded onto my phone and afterwards the phone booted into the OS. I immediately turned on OEM unlock and USB debug in dev options, because one never knows what might happen to the pixel :/
None of the unlock commands worked, adb nor fastboot. Hence android flash tool NOR the android pixel repair & update site worked because the phone was still considered OEM locked.
So I closed the Google device-support case I had opened in the meantime. Funny thing, after explaining everything in a document, with screenshots, they advised to use flash.android.com to reset my phone... well..... if it only were that easy I wouldn't have opened the case in the first place huh
Anyway, thanks for your replies all!
PEACE
Click to expand...
Click to collapse

paquiro said:
Just got in this today and I'm not able to do it. How did you do the adb sideload?
I can't do it in fastboot or in rescue mode
Click to expand...
Click to collapse
Hi @paquiro. Welcome to XDA. It's possible that one of the existing how-to guides would help you. At the top of the list of threads in this section, just click the yellow How To Guide quick filter, and there are several threads that may give you what you need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

roirraW edor ehT said:
Hi @paquiro. Welcome to XDA. It's possible that one of the existing how-to guides would help you. At the top of the list of threads in this section, just click the yellow How To Guide quick filter, and there are several threads that may give you what you need.
View attachment 5636799
Click to expand...
Click to collapse
Hey! Thanks, I tried to see them but the problem is that my device is not unlocked and I'm not able to do nothing...

paquiro said:
Hey! Thanks, I tried to see them but the problem is that my device is not unlocked and I'm not able to do nothing...
Click to expand...
Click to collapse
At least one or two of those How-To Guides detail the OTA method, which doesn't require unlocking the bootloader - like others in this section who are experienced with OTAs have explained. I am not experienced with the OTA methods, although I understand them.
If you don't have USB Debugging enabled, then that is a different issue.

Heya,
paquiro said:
Just got in this today and I'm not able to do it. How did you do the adb sideload?
I can't do it in fastboot or in rescue mode
Click to expand...
Click to collapse
I literally did: "go into rescue mode > press power + vol up, to get recovery, then do adb sideloading". < Meaning, if you're in recovery, go to "apply update from ADB", then your phone will say something like "waiting for sideloading". Then on your laptop/pc you should be able to do adb devices. It will say something like <ID> sideload. Then do the adb sideloading. If your phone is OEM locked (like mine was, apparently), the only update that will succeed is the full OTA, like Freak07 stated.

v0id said:
Heya,
I literally did: "go into rescue mode > press power + vol up, to get recovery, then do adb sideloading". < Meaning, if you're in recovery, go to "apply update from ADB", then your phone will say something like "waiting for sideloading". Then on your laptop/pc you should be able to do adb devices. It will say something like <ID> sideload. Then do the adb sideloading. If your phone is OEM locked (like mine was, apparently), the only update that will succeed is the full OTA, like Freak07 stated.
Click to expand...
Click to collapse
Oh! Can you send me a link with the full OTA? I tried with the last version of redfin for Pixel 5: https://developers.google.com/android/images here
Edit>
Ok, ok. I think I will be able to fix it. I've tried with the last one of here: https://developers.google.com/android/ota
12.1.0 (SQ3A.220605.009.A1, Jun 2022)
That was the version I had on my phone and I receive a message saying:
The update package is older than the current build, expected a build newer than timestamp 1654230298 but the package has timestamp 16535171705
So the 12.1.0 SQ3A I sent is from Wednesday, May 25, 2022 10:18:25 PM
and the package I had installed the last is from Friday, June 3, 2022 4:24:58 AM
So, if I wait until another version is released, I will be able to recover it until another error happens... Will maintain you informed, thanks!

paquiro said:
Oh! Can you send me a link with the full OTA? I tried with the last version of redfin for Pixel 5: https://developers.google.com/android/images here
Edit>
Ok, ok. I think I will be able to fix it. I've tried with the last one of here: https://developers.google.com/android/ota
12.1.0 (SQ3A.220605.009.A1, Jun 2022)
That was the version I had on my phone and I receive a message saying:
The update package is older than the current build, expected a build newer than timestamp 1654230298 but the package has timestamp 16535171705
So the 12.1.0 SQ3A I sent is from Wednesday, May 25, 2022 10:18:25 PM
and the package I had installed the last is from Friday, June 3, 2022 4:24:58 AM
So, if I wait until another version is released, I will be able to recover it until another error happens... Will maintain you informed, thanks!
Click to expand...
Click to collapse
Well, I did the upgrade (through android beta program) and tried to downgrade by 'un-enrolling' from the program, leading to a failed downgrade and softbrick. To me, it seems I never actually downgraded from the beta, until I did the OTA sideloading manually. However, I never had a problem using the latest OTA to do the downgrade. Are you sure you're using the latest OTA at this moment? I believe there are beta OTA's as well, perhaps you can use them?

v0id said:
Well, I did the upgrade (through android beta program) and tried to downgrade by 'un-enrolling' from the program, leading to a failed downgrade and softbrick. To me, it seems I never actually downgraded from the beta, until I did the OTA sideloading manually. However, I never had a problem using the latest OTA to do the downgrade. Are you sure you're using the latest OTA at this moment? I believe there are beta OTA's as well, perhaps you can use them?
Click to expand...
Click to collapse
Finally I got it with this: https://developer.android.com/about/versions/13/download-ota

paquiro said:
Finally I got it with this: https://developer.android.com/about/versions/13/download-ota
Click to expand...
Click to collapse
Awesome!

Hi all. I just want to seek help on the same error when wiping/factory resetting the phone:
"Unable to enable ext4 verify on /block/dev/platform/14700000.ufs/by-name/metadata because /system/bin/tune2fs is missing"
I'm able to boot up to the setup screen but I get stuck at the "Copy Apps & Data" stage. Tried every option but it either just goes back to the first screen or would get an error that "Settings has stopped working" error.
So far I've tried sideloading the latest OTA from this site https://developers.google.com/android/ota#bluejay
13.0.0 (TQ2A.230505.002, May 2023)
It completes without error but even after the install, when wiping/factory resetting the phone, I still get the same error and same situation at the start screen
I'm using a Pixel 6a

Found my old note 10.1 and did something stupid... need help...

I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Why don't you try flashing stock firmware?
Check for drivers issue.

mvikrant97 said:
Why don't you try flashing stock firmware?
Check for drivers issue.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
Your device should show up like this in device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing like this

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
It is P605. And from this post looks like you are not the only one https://forum.xda-developers.com/t/q-galaxy-note-10-1-2014-not-recognized-in-download-mode.2494886/

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Also watch this video

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Please try to get into download mode for odin to recognize your tablet

Ok, so using another PC and yet another cable, I was finally able to see this pop up on the device manager when in the "update with adb" option:
Unfortunately, I cannot get the tablet to stay in download mode. As soon as I confirm to go to download with the vol+ button, it immediately starts to boot loop.
On the other hand, when in the adb mode, the PC does recognize the device when it's attached and I can see it with "adb devices" command.
But unless there's a way to get it to go to download mode, I'm screwed, right?

mvikrant97 said:
Also watch this video
Click to expand...
Click to collapse
Yes, but that is my problem. I cannot get to the download screen. I can press up to select it, but then poof, it goes to cycle again. Unlike the guy in the video:

OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!

erkme73 said:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
Click to expand...
Click to collapse
Now you are good to go. Odin will detect and you can flash it.

Thanks... doing it now. I'll let you know how great you are as soon as it starts working! Thanks...

Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
That's great to see your device is working now.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
If you really wanna stay on stock you can use Chainfires Autoroot for this device.
Anyway, my P605 is on LOS17.1 running stable.

Question Pixel 6 Pro (no root) stuck in bootloop after official Android update

Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards

Thiiibs said:
Hello,
I usually come here to root my phone and choose the best ROM, but this time I'm here because of a problem with the official ROM. I did a simple OTA android update this weekend, and the phone never restarted. There was enough battery so nothing to report during the install. I'm stuck on an infinite bootloop and the recovery commands take me to a no command.
Beyond having lost all my data, I'm worried because no command is working. I have already followed all the tutorials on youtube (including the most improbable techniques of hitting the back of the smartphone or putting it in the freezer for 10min, I know it's stupid, but when you're desperate you try everything).
So I'm coming here to ask for your help, hoping that someone will give me a solution to at least flash a basic image and start over.
Regards
Click to expand...
Click to collapse
Since you can get into bootloader and it's locked, go to platform tools and unlock the bootloader. Then you can flash the factory image and proceed from there. This will wipe data.
The other image is the screen prior to entering recovery via pressing power button and vol up.

I would recommend turning on USB debugging first thing when getting any phone.
Android Flash Tool
flash.android.com

The No Command Screen is normal. You just need to press and hold the Power Button and while doing, so press and release the Volume Up key (after about 5 seconds) and then release the Power key as well. This will take you to stock recovery. From there, you could sideload the OTA package [works on a locked bootloader as well] but as already told in a post just above mine, you need to have enabled USB Debugging beforehand.

The bootloader is locked but you can access it, so go to platform tools and unlock it. After that, you can flash the factory image and carry on. It will erase all data.

To sideload an OTA in stock recovery you shouldn't need to have USB Debugging enabled. Being in sideload mode enables a very limited set of ADB commands on Pixels, including adb sideload <imagename>.zip. I'm not aware that this has changed.
To unlock your bootloader you will need to have OEM Unlocking enabled in Developer Options beforehand.