Develop Bugs

[Q] Failed Sprint Note 2 Root Stuck in Loop, Dev not answering

I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.

doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already

vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?

doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!

I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.

Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.

Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!

---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.

garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY

[Q] [x-post from LG G3] D851 unroot / restore to stock

I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.

http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4

BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.

etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.

Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it

BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.

Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.

Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4

BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.

Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4

BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.

Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea

Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.

Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.

Thank you for answering

yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.

Good luck man let us know what tmobile says

Strange OPPO Find7 Soft Brick

Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?

Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
Do you have an OTG Usb drive. If so, you can use it with Nameless TWRP. Copy the Installation files into the USB drive and plug the usb drive into the phone. Now boot into Nameless recovery. It will show USBOTG. You can install the CM11 from USBOTG.
Flash Nameless recovery using Fastboot.
Download Nameless Recovery from HERE.

soft brick
This link explains how to restore our find 7 to factory settings:
oppoforums.com/threads/guida-riportare-il-find-7-7a-nello-stato-dacquisto-con-il-firmware-sahara.24561
if phone doesn't start try it i've use it several times and it works fine

I might just be reposting what dracula6mt was talking about, but there's an English post with full brick recovery here: http://www.oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/. I've used it before and it works perfectly. Just make sure you follow it exactly as written!

Bug
same bug report

for retrive your data just open the gummy twrp recovery, go on mount --> sd card and internal memory... in this way when you connect the phone to pc you will be able to see what's inside and try to rescue your data. in the same way you can send files to it.
I suggest you to get back your files, reboot the phone in fastboot mode (hold power and volume +) and just flash a recovery, it depends about what you want to install:
twrp for custom roms https://dl.twrp.me/find7/
colorOS stock recovery http://community.oppo.com/en/forum.php?mod=viewthread&tid=17397&extra=
you have to install fastboot on your pc and do from a command prompt:
fastboot devices
this will check if your phone is connected
fastboot flash recovery nameoftherecoveryfile.img
that will flash the recovery, only check the name of the .img file you want to install
be carreful, twrp has only a version for both find7s (QHD) and find7a while colorOS recovery 1.0 is different, unified for both models in 1.2 if i remember right...
after that you just have to put on your external storage the rom you want to use, wipe all except the external sd card, and flash...

Outblaze713 said:
Hey guys.
I'm new to this forum... and am posting this as I no longer know what to do, and need some guidance.
First I'll say that I've looked ALL OVER this forum and others, but couldn't solve my problem.
...So I subscribed in the hopes that someone will be able to more properly guide me.
------------------------------------------
So, first thing's fisrt - the story from the beginning:::
My device is an OPPO Find7 (QHD Version)
I've been using Cyanogenmod 11 for many months and without any problems.
Few days ago I installed the first nightly update of CM12 - and phone went into boot loop.
I had to restore to the ColorOS backup that was saved on my phone... Reinstalled CM11 and all is good.
Later I again updated to CM12 - and again was forced to revert back to Backup and then to CM11 due to bugs (phone wouldn't wake up after being locked, etc)
Anyway, There were three nightly build of CM12 to that point,and the last one was working in a relatively stable manner,
exept two bugs.
1. Contact names didn't appear when mamkiing to receiving a call - even though they were saved on the phone.
But this bug can be overlooked.
2. This one was more cirtical - - For some reason the phone said that I have no more free
space (even though I had 20+GB), thus preventing me from installing or updating
anything.
I figured that, perhaps, becuase of all the re-installs that I've done - my system memory got clogged.
So I decided, with more haste than thought, to perform a full wipe...SDcard and all, which consequently also removed
my ColorOS backup and everything, basically.
-----------------------------------------
The currrent outcome of what I did:::
Phone has no OS installed on it, and PC doesn't llow my to put files in there.
I can currently boot in three different states:
1. Normal boot with power button - - - OPPO logo appears - followed by a black
screen PC recognizes that I've connected a device, tries to install MTP Device and
evetually fails.
2. Power Button + Vol Up - - - Fastboot screen.
3. Power button+Vol-Down - - - Boots into the Gummified Team Win Recovery 2.7.1.0
In here, several things need to be mentioned.
- In the "Mount" section, I can choose which Partitions to mount to unmount, but
don't actually have the "Mount" button inside... So I can't mount.
- ADB Sideload doesn't work. When activating - it says "Starting ADB Sideload
Feature and just goes on forever, until I cancel it - and it says that it failed.
--------------------------------------------------
What I tried doing:::
Tried to use the Recovery Installer for OPPO, which is the exe that is available on the internet, that comes with drivers and all - and open command line with various options.
Tried installing the stock Color OS recovery, but when booting into it I still get the teamwin recovery
I am unsure how to proceed.
Is there a way to fix my phone?
I have my CM11 working version and gapps ready - just need to place it in the phone somehow.
Any help?
Click to expand...
Click to collapse
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.

os_man said:
There is a much easier way :
http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
mail me to : [email protected], greetings.
Click to expand...
Click to collapse
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF

spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.

spoonymoon said:
I know you, you are every where in all sites when searching for brick solutions...and are just thinking of earring money....fuuuii you rotten bastard,I want you too get your greedy as out of here, right now
And reporting this too forum admin right away, so they lock your ip right away
Greedy bastard, seen hundreds of posts, where people begged for the password you locked the rar file with, and only giving it when they pay you....gonna say it again.....
**** OFF
Click to expand...
Click to collapse
Taken from my article ( for those who can read ) :
Please Stop asking for password without reading the article completely till the end, THIS TOOL WONT WORK UNLESS YOU HAVE THE NECESSARY SERVICE ROM ! Try sharing your phone model first and also try to share the service ( QPST ) Rom if you have it so more people can use it, THANK YOU.

os_man said:
Every human beeing who can communicate gets the password for free, especialy OPPO and OPO owners, every e-mail i get starting with "Pasword pleaseee pleaseee pleaseee" gets different behaviour of course. OH, and every CLEVER people already knows the tool in my article, i mentioned it a couple of times, for stupids like you its impossible to see of course. I helped hundreds of people for free and sometimes i request for donation, ITS MY VERY COMMON RIGHT + to help those i want and not to help to those that i dont want.
Greetings from TURKEY you silly Viking.
Click to expand...
Click to collapse
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
EDIT: believe me, this turk psyko, has NOTHING not known already, regarding unbricking devices, there´s hundreds of posts here and on oppo forum about people having storage issues etc, not one ever mentioned anything about any other tools than those oppo them selves gave us, there is NO other working ways not known as this cracy dude claims, he´s just running a scam and wants 20$ for nothing - OS_MAN is a fraud dude all over.
EDIT 2: Silence from sir os_man tells the truth....

spoonymoon said:
Hahaha,if so why, don't you post a link here, on mega or something, instead of all this " mail me" crap??? That would be a honest thing too do, instead....
And no, it's not common too sort in who and which, you want to help out, at least not here on XDA, we help every body, with no exceptions.
I say again, give us this file freely or I report you too forum admins.
My x9076 is bricked because of me making a lvm error, but I'd rather have it semi Working, with messed up partitions, like now, than pay our beg some guy like you for something that not working any way.
Last chance give this freely or get locked out from xda
Click to expand...
Click to collapse
Never threaten a Turk Do whatever you can !
If XDA will lock me becouse of you, let it be
And i dont think that you can help anybody with that brain of yours, you even cant rescue your unbrickable Oppo..

spoonymoon said:
I say again, give us this file freely or I report you too forum admins.
Click to expand...
Click to collapse
When asking for help in a free space and for free, sometimes some manners can really make a huge difference. I think you fail to understand that even though you have a problem and someone might have a solution, that someone has no obligation whatsoever to share their time and the fruit of their research with you, especially so when threatened.

Hmm, considering the files and how-to's for unbricking a Find7 are freely available from Oppo forums (and here, I believe), I'm pretty suspicious of anyone doing ANYTHING other than giving them away freely. The files I downloaded and have used, a few times now, were free and had no passwords on zip/rar archives.
As for 'fruits of research', this guy wasn't the guy who put up the how-to's or did the initial research on it so, in my books, he doesn't get the credit, be it kudos OR cash money.
Some folks seem to literally want something for nothing. No harm in asking for donations, sure, but don't be at all surprised if I tell you to go f*** yourself. That's not how this game works, we all stand on each other's shoulders.

Pixel 2 Bricked??! (Solved!)

I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
---Solution---
Chilipepprflea said:
I know this is probably too late for you guys, but maybe it will help someone else. Fastboot commands would result in "waiting on any device" and my Pixel 2 wouldn't boot out of the bootloader. I thought it was done for good based on this thread and others I've read...until I came across this Reddit https://www.reddit.com/r/GooglePixel/comments/b25nso/error_slot_unbootable_load_error/
I did what this guy did and held the power button (ended up being for a couple minutes in my case) and it vibrated and all is good again! adb recognized my phone and I was able to flash again.
Click to expand...
Click to collapse

You'll have to go back into bootloader and do a stock flash follow the steps on googles site. go back to 8.0 or whatever you were on before, make sure that boots up fine. You must not have had updated your sdk before trying to update to 9.0

I was going to just reflash everything but when I do fastboot devices its just blank as if the phone does not exist. Also the computer doesnt do its chime when I plug the USB in while its in bootloader. When the phone is off and I plug it in it shows the charging icon for a split second then boots into bootloader saying ERROR: Slot Unbootable: Load Error. If I try to do any commands in fastboot it just says "waiting for any device"

I was already on 9.0 and was just pushing the January security patch when it stopped near the end of the update. Now I can not get fastboot to even see the device.

Try removing all drivers and fastboot files on your pc. Sounds like you just flashed the wrong file. Were you rooted with magisk? or just on a stock rom. re download the full image and try and re flash. https://developers.google.com/android/images
Because of the slots (a and b) alot of people seem to have trouble flashing things. I have even messed things up as well. On the Pixel devices I havent been able to not go back into stock setups. Even if it took removing all files and starting over.
---------- Post added at 04:19 AM ---------- Previous post was at 04:18 AM ----------
I will keep checking back over here to see if you have any issues.

So I just tried what you had said. Deleted all the SDK files and uninstalled the drivers, rebooted computer and phone redownloaded everything and still can not find the phone via fastboot... magisk was installed but I was doing the full image install without the -w so it would not wipe. it was almost done with it and never actually booted into android it just stayed on the bootloader which I found strange. That is when I noticed that the phone could no longer be found via fastboot devices. I have tried different cords different ports and even a different computer and still have the same result. It did update the bootloader and radio portions of the update. I feel like if I can get fastboot to start working I can save this thing.

I got caught up with friends that came over. You have tried everything I would have tried. Which is good cause you seem to know what you are doing, but not good that it hasnt been resolved. Have you looked at this guide? https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Coolpente said:
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you *sure* it will not boot to recovery? If you're not used to the stock recovery it can fool you. Many ppl see the dead android and stop there. If you can get into the stock recovery you can try sideloading an OTA via adb (which only works in recovery). I would also be trying different computers and cables. If you cannot use fastboot -and- you have no working recovery you might be dead in the water.

OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])! And those who have seen me around this forum the last year know that I am very knowledgeable and don't make the simple and "noob" mistakes! I've literally have helped and recovered people in this/our position -- so it is doubtful there was a amateur or novice mistake made in the updating process or "stone un-turned" in the recovery process!
So here is what happened to me, particularly, and my observations on it...
- When "crap hit the fan", it was very peculiar that fastboot would identify the phone's serial number as "??????????" (when running the command "fastboot devices"). Only after rebooting and disconnecting/reconnecting the usb cable did it (fastboot) simply just stop detecting. To make sure that my computer, usb port, cable, and fastboot is working correctly and able to process properly, I would make sure the fastboot process/server was not running, then I would actually run the command "fastboot getvar all", and as it would "would for device", I would plug in the phone, nothing would happen, then plug in my phone [taimen] (not my gf's walleye), and it would detect it and display all the pertinent information and device details, I would then unplug it from my phone, run the same getvar command, and lastly replug it into the phone (broken gf's walleye) with no detection or success.
- What's also interesting and of note is that when loading straight into the bootloader (via button combination), it displays no error in the list of device details. But when booting into the recovery (note: I, like the OP, had the TWRP custom recovery already flashed and installed) and also the system and/or from a power-off state, it states in red colored font and yellow background, "ERROR: Slot Unbootable: Load Error". Even more than that is when attempting to boot into Download mode, it states a different error (but in the same font style), "ERROR: Operation Denied"!
- I also attempted to manually change the slot in attempts to address the "slot unbootable..." "...load[ing] error", but -- due to either fastboot not detecting or the device not connecting properly I imagine -- without fastboot properly detecting, the commands wouldn't work and execute properly anyway. I've even taken steps further and attempted to format and custom "re-size" partitions. But, for the aforementioned reasons (presumably), it and attempts at commands like it wouldn't likely work and execute, again as previously reasoned. Also, in attempt to tackle the "slot" aspect of the issue, I tried Deuce's script; but as Deuce's script is, simply put, based off of the flash-all.bat that ends up being an advanced batch (pun intended) of commands that manually and individually flashes the stock images/partitions to the partitions of the device -- so, in essence, uses fastboot and since fastboot can't work.... I even found and attempted to use the (hardly heard of; at least to me) tool Skipsoft Android Toolkit (which looks genuinely super dooper awesome btw...)... all for naught :crying: ...
You know, after a year with the Pixel 2 (XL), and after coming back from messing my phone up (15+ times), and actually purely bricking it once (had to get it replaced), I always thought that, as long as one could access the device via the bootloader, one would always have hope (at least in the Pixel's case). So, it's curious but agonizingly ironic being able to access the bootloader (which was not the case in my one and only instance of bricking my device and having a completely "lost cause") just for me not to be able to do anything about it and/or fastboot to not be able to properly connect and send commands to it...
But to me and Coolpente (and anyone else who this may have happened to) I ultimately can't think of anything else that can be done at this point. To re-iterate, I/we had the most up-to-date platform-tools (r28.0.1), it has been proven that the usb cord, port, computer, and drivers are all working as I was able to get the "getvar all" command to work on another pixel mere seconds before attempting the same on this (broken) device, and even attempted all tools available...
Unfortunately, @Coolpente, it does look as if our phones are irrevocably "bricked" and it's all rather doomed and attempting to get it repaired/replaced by the manufacturer ("The Big G") is the only recourse we may have :crying::crying::crying:
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...

simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
-- SNIP---
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
Click to expand...
Click to collapse
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.

Coolpente said:
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Click to expand...
Click to collapse
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....

simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])!
Click to expand...
Click to collapse
Find a new girlfriend, your problem will be easily solved.

simplepinoi177 said:
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
Click to expand...
Click to collapse
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...

Coolpente said:
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Click to expand...
Click to collapse
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**

simplepinoi177 said:
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
Click to expand...
Click to collapse
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.

Coolpente said:
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Click to expand...
Click to collapse
Yeah, I see what you're saying and in the exact same boat (2 pixels, gf's is a walleye, mine's a taimen, both have been updated monthly with no issues or def bricking issues, so 14 of 14 and 13 of 14...)...
But I guess that's definitely one of the "safest" methods, just that support for ROMs come and go (hell, even one of the original custom kernels [Flash] is EOL)...but Pixel 2 is only a year "in" and Google will continue to support it for the foreseeable future so it may look like regular support for walleye/taimen-related mods will continue to get regular updates and support as well...
But still, as I enjoy our conversations, it also serves to "bump" this thread as well...
Anyone have any idea on how to reinstall bootloaders, switch slots, enter custom recovery, flash anything all without -- and this is key -- fastboot (because fastboot will not detect and connect with the device)?!?!

I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?

James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.

simplepinoi177 said:
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
Click to expand...
Click to collapse
I just contacted Google for an RMA. Hope it doesn't occur on the phone that will be shipped to me. Now I am without a phone for a couple weeks...

James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Did you also ran the flash all without - w?
Sent from my Pixel 2 XL using Tapatalk

Question A22 4g (a225fxxu3cvk3) Bootloop

Greetings
I got a notification that there is an update to one ui 5 _ android 13 available. i connected the phone to the charger, started update and went to sleep (since the internet speed is slow here and takes a long time to download the data). after i woke up, i faced a bootloop on my phone.
i cleared the cache and repaired apps in recovery menu (based on a guide on some website), but it didn't help. what should i do?
* my phone doesn't have a warranty anymore.

First wait for an hour if it boots up if not wipe all the data

Oh my, I just faced the exact same problem WITH the exact same phone! :')
Don't bother with technicians, tried with two and they both said wiping data was the only way. I was thinking of trying with the Samsung Support Center but eh, they're closed tomorrow (italian holiday lmao)
Anyways, I believe doing a hard reset would resolve everything, but I'm assuming you don't want to..
I got a whole lot of help in here, if you want to check!
https://forum.xda-developers.com/t/...p-after-device-is-stuck-on-boot-loop.4536965/
Let me know if you're able to do something!

Alslamalikom (Peace be upon you) .. I hope you are well.... I had the same problem, in samsung a22 4g after updating Android 13, it only turned on the Samsung logo, then it restart.. Bootloop
I just subscribed.. to warn you so that no one will make same mistake .. My storage size is 128 GB and it is full of family personal and for me, and it was not possible to format it so as not to lose it.. Also, the mobile was under warranty, and I did not want to go to the agency, because they would say format or they would be able to open it, and it contains special family things
So I used Odin and the ROM version a225fxxu3cvk3 and another object such as bootloader and others, and the download began, and all my hope is to open The device does not delete anything
Thank Allah , in any case, the device was opened, but an automatic format was made for the device and everything was lost as if it was new... So I liked that no one did and lost his data as me🥹
And as kind member here called (nanawa) said, try when an update comes out, not the same ROM or Older than on the mobile phone
But everyone who installs the ROM is at her/his own risk
I will put it here and 2 another topics related to the problem and i will leave
Best wishes,, alslamalikom

Muslim for Allah said:
Alslamalikom (Peace be upon you) .. I hope you are well.... I had the same problem, in samsung a22 4g after updating Android 13, it only turned on the Samsung logo, then it restart.. Bootloop
I just subscribed.. to warn you so that no one will make same mistake .. My storage size is 128 GB and it is full of family personal and for me, and it was not possible to format it so as not to lose it.. Also, the mobile was under warranty, and I did not want to go to the agency, because they would say format or they would be able to open it, and it contains special family things
So I used Odin and the ROM version a225fxxu3cvk3 and another object such as bootloader and others, and the download began, and all my hope is to open The device does not delete anything
Thank Allah , in any case, the device was opened, but an automatic format was made for the device and everything was lost as if it was new... So I liked that no one did and lost his data as me🥹
And as kind member here called (nanawa) said, try when an update comes out, not the same ROM or Older than on the mobile phone
But everyone who installs the ROM is at her/his own risk
I will put it here and 2 another topics related to the problem and i will leave
Best wishes,, alslamalikom
Click to expand...
Click to collapse
Wa ʿalaykumu s-salam, i want to ask a question, was the device bootloader unlocked with the important data or was it locked?