Database Develop

[Updated 05/08] Sprint 2.2 Stock ROM Download.

Here it is, as asked for.
Updated 05/08/11
THESE IMAGES ARE CONFIRMED WORKING!!
http://openzio.rtrnetwork.com/openzio/sprint2.2_image_pack/

the system rom is no good, i have tried 6x all with the same result
C:\Program Files (x86)\Android\android-sdk\tools>fastboot flash system system.img
sending 'system' (121856 KB)...
OKAY [ 30.490s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 50.419s
C:\Program Files (x86)\Android\android-sdk\tools\zio\sprintsystem>unyaffs system
.img
2 [main] unyaffs 4456 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
657 [main] unyaffs 4456 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
238280 [main] unyaffs 4456 _cygtls::handle_exceptions: Exception: STATUS_ACCESS
_VIOLATION
263350 [main] unyaffs 4456 _cygtls::handle_exceptions: Error while dumping stat
e (probably corrupted stack)
Could you get another copy ?

I'll have to do some asking around. Could be awhile. The person I got the dump off of isn't online much anymore.
I think the system image must have been dumped using dump_image instead of mkfs.yaffs2, if thats any help.
I'll let you know as soon as I'm able to grab another copy
Sent from my Zio using XDA App

Go to the sprint forums for the zio, make a new thread and request a rom dump
Sent from my Zio using XDA Premium App

I have put up threads everywhere asking for this rom. Its very difficult to come by. All we can do is continue looking and hope someone posts up a working img

I dont see why you wouldnt be able to loop mount the system image, extract the system files then rebuild the image yaffs2?
Im saying that, cuz with my source, it could be a while. =\

well i could use some help, currently i have the sprint files in a zip and i tried to compile a img file using them without luck. When i flashed the device powercycled though recovery mode and back to boot screen. Have a messanger of some sort for a live chat?

hop on IRC
irc.freenode.net
#openzio
A little crunched for time, but I'll help with what I can.

After successfully restoring the Sprint Zio, I am now running into another issue. The phone is not getting service, and is not recognizing the MSL (may be due to the fact the phone is NOT recognizing the MEID).
{
"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"
}
Yet, from a PC diagnostic standpoint, the phone looks okay.
Any ideas??

Playa4Life352 said:
After successfully restoring the Sprint Zio, I am now running into another issue. The phone is not getting service, and is not recognizing the MSL (may be due to the fact the phone is NOT recognizing the MEID).
Yet, from a PC diagnostic standpoint, the phone looks okay.
Any ideas??
Click to expand...
Click to collapse
I will flash the Zio I have, and see if the same issue comes up.. If it does then its flash related, but it not then its a problem on your end

hakuchi18v said:
I will flash the Zio I have, and see if the same issue comes up.. If it does then its flash related, but it not then its a problem on your end
Click to expand...
Click to collapse
What steps did you do to get it flashed? I just flashed my zio and everything is recognzed.. esn msi and prl

fastboot -w
fastboot flash boot
fastboot flash system
fastboot flash recovery

What I did was
Fastboot erase system
Fastboot erase boot
Fastboot erase recovery
Fastboot erase userdata
Fastboot flash boot
Fastboot flash system
Fastboot flash recovery
Fastboot reboot
Maybe it was something that went wrong software wise.. Or its hardware related
Sent from my HD2 using XDA Windows Phone 7 App

hakuchi18v said:
What I did was
Fastboot erase system
Fastboot erase boot
Fastboot erase recovery
Fastboot erase userdata
Fastboot flash boot
Fastboot flash system
Fastboot flash recovery
Fastboot reboot
Maybe it was something that went wrong software wise.. Or its hardware related
Sent from my HD2 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Okay I just tried it, and it's still a no go...
There must be a way I can rebuild the NV items other than a ##RTN#.
Anyone know of a way in adb??

hakuchi18v said:
I will flash the Zio I have, and see if the same issue comes up.. If it does then its flash related, but it not then its a problem on your end
Click to expand...
Click to collapse
same problems here.. nv fail

I too have an NV fail.
I was able to fix corrupted NV items with an ENG rom on my evo. But until we get the nv.img I don't know if this is fixable
Or if there is an nv.img

Have you guys tried to factory reset _after_ flashing and booting up the phone?
The reason I ask, is that us cricket users had ran into an issue way back in the day after fastboot flashing images -- upon reboot we would be on the verizon network.
A factory reset fixed the issue.
What the problem was, was when the phone does a factory reset, it posts once - during this post is when all the MSL, PRL, APN, etc... settings get configured. Then the phone cycles and boots up, on the correct network.
A bit of added info: DO NOT delete ANY partitions other than the ones listed in the image pack provided in the first post. I say this for the simple fact that I do not know what other partitions sprint has put in this phone, nor do I know what they do (possibly something similar to our FLEX partition being responsible for for configuring network settings prior to first boot)
Good Luck

cutthroatamft said:
I too have an NV fail.
I was able to fix corrupted NV items with an ENG rom on my evo. But until we get the nv.img I don't know if this is fixable
Or if there is an nv.img
Click to expand...
Click to collapse
can you share how to fix this nv fail and the nv.item file?

OK I know this is an old thread but I need some help I made a really noob move and tried to flash cwm recovery through rom manager on a sprint zio someone gave me and am stuck in a bootloop.
I've tried flashing the recovery.img from fastboot but it starts and I get a failed error everything else flashed fine so IDK what's going on.
Is there any other recovery I could try to flash.
TIA for any help.
Edit: I fixed it.

Hi ALL! New to the Zio. Had a Nexus One, G1, and some windows phone made by HTC. (Can't remember the name of the phone). I have a Sprint Sanyo Zio that i just picked up. It's already rooted. I think it's running 2.2.1 (gotta check) but I read you need stock img that works. Try mines?

How to flash CWM Unoffical???

Hi,
I downloaded CWM unofficial 6.0.32 from this forum, but I'm new and I have no idea what to do with it. I did successfully root my phone that's all I've done to it.
Thanks!

You use fastboot commands. There's a tutorial skeevy just made in general.
Sent from my PACMAN MATRIX HD MAXX

I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.

Do you have the lastest motorola usb driver installed?

hungrymr2 said:
Do you have the lastest motorola usb driver installed?
Click to expand...
Click to collapse
Yes, Sir

Rick1488 said:
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Click to expand...
Click to collapse
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....

No idea, but here's what I did to install cwm. download safestrap apk, boot to safestrap recovery, hit fix permission, go back to cmd prompt, fastboot flash it,
edit: try enabling "usb developer/debugging mode" before booting it into fastboot?

skeevydude said:
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
Click to expand...
Click to collapse
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
{
"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"
}
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.

Rick1488 said:
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Click to expand...
Click to collapse
You might have a picky motherboard. Some front-side ubs ports won't work for some odd reason for some users. Use a usb port on the back of your pc.
Out of curiousity, did you try flashing a fastboot with rsd before you started doing this? And if yes, did it finish completely?
Also attached is a zip to flash CWM from SSR (maybe...SSR might block the command) and a fastboot modified to only flash CWM. Both are untested but worth a shot.
EDIT: Any one of you windows users care to chime in? Ya'll know I don't run it. I'm kinda runnin outta ideas here....gettin down to the just use linux reply...

unlocked bootloader
I saw that you rooted but did you unlock the boot loader?

frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
You're right...can't believe I missed that...never once is that mentioned...,

frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
Um, I kinda forgot that part.. my fault. I just unlocked the bootloader and I'm gonna give it another try.
UPDATE: Success!
I'm sorry guys thanks for all your help.

:victory::victory:

HTC One M7 brick got even worse!

I have posted a thread about bricking my HTC One a few days ago and actually , I got it finally fixed today with the help of SaHiLzZ!
First of all , thanks man for helping me.
Here's the first thread that I have opened if anyone is interested:
http://forum.xda-developers.com/showthread.php?p=52747826
I was finally able to get past the HTC boot logo and use the phone but I also wanted to update the ROM to KitKat 4.4.
I have changed my CID to HTC__001 from HTC__K18 with no effort , however , I failed to change my MID to PN0710000.
I followed this tutorial step by step (http://forum.xda-developers.com/showthread.php?t=2322820) , but when I applied the fastboot oem writemid command , there was an unknown error and when I rebooted the phone I got the exact same screen as this:
{
"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"
}
Now , I'm unable to access anything!!! I can't even get to the bootloader or recovery which was possible with the soft brick. The only 2 screens that I am able to get now is the gray screen as in the picture above , or a complete black screen (and the device still stays on).
I'm unable to use any adb commands , but fastboot commands still work. However , I'm unable to flash any RUU , rom , CWM , TWRP , boot...
Is there's anything I can do about it?
Here's an output of the fastboot getvar all:
Anyone have any idea what can I possibly do to fix this?

You are on eng hboot. And your device is responding in ruu mode. Run the ruu as long as your fastboot is working.

SaHiLzZ said:
You are on eng hboot. And your device is responding in ruu mode. Run the ruu as long as your fastboot is working.
Click to expand...
Click to collapse
I tried it , I used the RUU that fixed the soft brick but it didn't work this time.
It can't get past the bootloader stage because it tries to access the bootloader but with no success.

ciyomh said:
I tried it , I used the RUU that fixed the soft brick but it didn't work this time.
It can't get past the bootloader stage because it tries to access the bootloader but with no success.
Click to expand...
Click to collapse
I didn't understand, is this a continuation of the other thread, or did you get any further? a bit more details please.

nkk71 said:
I didn't understand, is this a continuation of the other thread, or did you get any further? a bit more details please.
Click to expand...
Click to collapse
It got worse but I was finally able to change my MID and fix it. After that I reinstalled RUU 1.29.401.2 (I tried to install anything newer but nothing worked , only this one).
I can use my device regullary now.
I have supercid , mid PN0710000 and JB 4.1.2 on my device.
But the problem now is that I'm unable to update the device using any newer RUU (that match the new mid of my device).
I also don't have superuser or working recovery , when I try to flash recovery , I get this error:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8758 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
I've tried to flash a few different recoveries but I get this same Unknown error everytime.
How is it possible for me to update from 4.1.2 to 4.4.2/4.4 if I get this same error every time and with no superuser access when every .exe RUU install fails too?

ciyomh said:
It got worse but I was finally able to change my MID and fix it. After that I reinstalled RUU 1.29.401.2 (I tried to install anything newer but nothing worked , only this one).
I can use my device regullary now.
I have supercid , mid PN0710000 and JB 4.1.2 on my device.
But the problem now is that I'm unable to update the device using any newer RUU (that match the new mid of my device).
I also don't have superuser or working recovery , when I try to flash recovery , I get this error:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8758 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
I've tried to flash a few different recoveries but I get this same Unknown error everytime.
How is it possible for me to update from 4.1.2 to 4.4.2/4.4 if I get this same error every time and with no superuser access when every .exe RUU install fails too?
Click to expand...
Click to collapse
Can you
1- post an updated "fastboot getvar all" (copy/paste would be better than screenshot),
2- a screenshot of your bootloader screen
3- what recovery are you flashing above? have you checked MD5, cause the filesize looks a bit small,
4- try using a different USB port / PC.

nkk71 said:
Can you
1- post an updated "fastboot getvar all" (copy/paste would be better than screenshot),
2- a screenshot of your bootloader screen
3- what recovery are you flashing above? have you checked MD5, cause the filesize looks a bit small,
4- try using a different USB port / PC.
Click to expand...
Click to collapse
Thank you mate! I tried using a different USB port and it actually worked!
Although I have no idea why should it work but haha it doesn't matter to me.
I have recovery and superuser as well now but I'm still stuck in JB 4.1.2.
I've tried flashing One_4.19.401.11_odexed.zip through recovery and it failed , then I got a mini brick and the phone didn't turn off no matter what I did for a few hours.
Then I see this craziest fix ever , I stuck it in front of a lightbub while holding power + Vol down for about 15 seconds and it worked! lol!
I'm now able to use it , but can't update it in any possible way.
I tried using an .exe RUU of KK4.4 but it didn't work as well (and it was compatible with my mid + cid).
Any idea what can I do to update my device to 4.4.2/4.4 from 4.1.2? I have access now to everything , the android , recovery , supersu , adb ,fastboot..
Thank you!

ciyomh said:
Thank you mate! I tried using a different USB port and it actually worked!
Although I have no idea why should it work but haha it doesn't matter to me.
I have recovery and superuser as well now but I'm still stuck in JB 4.1.2.
I've tried flashing One_4.19.401.11_odexed.zip through recovery and it failed , then I got a mini brick and the phone didn't turn off no matter what I did for a few hours.
Then I see this craziest fix ever , I stuck it in front of a lightbub while holding power + Vol down for about 15 seconds and it worked! lol!
I'm now able to use it , but can't update it in any possible way.
I tried using an .exe RUU of KK4.4 but it didn't work as well (and it was compatible with my mid + cid).
Any idea what can I do to update my device to 4.4.2/4.4 from 4.1.2? I have access now to everything , the android , recovery , supersu , adb ,fastboot..
Thank you!
Click to expand...
Click to collapse
Those 4.4 RUUs are very "sensitive", no idea why sometimes they work, and other times give people a hard time (could be anything OS, antivirus, bad download, USB port, etc)
Why didnt you just take the OTAs to 4.4, before installing custom recovery and root? just reflash the 1.28.401.7 ruu.zip, and take OTAs to 4.4.2 then install custom recovery and root
with S-Off, you can keep bootloader unlocked, no need to relock it or anything; as mentioned in the "Not so FAQ #2" here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

how to flash NEXUS 6 XT1103 ROM, BOOTLOADER LOCKED, CAN'T GET INTO PHONE, PLEASE HELP

PROBLEM -
I can not get into phone settings or ANYTHING ELSE because it keep SHOWING this error and LOADS NO OS or any icon THING AFTER BOOT
{
"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"
}
I tried from adb and it didn't work :-
<<< C:\adb>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
- I have downloaded rom from google for my phone model
- I can not ENABLE OEM unlock because I can not get into phone.
- I have tried wiping CACHE AND FACTORY RESET from recovery but it does not LOAD anything after boot and shows error I posted in image above.

lol!
first off, you posted in the wrong nexus 6 forums, as you arent developing anything(besides a headache). secondly, adb and fastboot are different. fastboot is not an adb command! fastboot is a different tool, like adb but different, and you can only use fastboot while you are in the bootloader. secondly, go back for a little and do a little more reading please, then try again.
edit.. good, this thread got moved to the right place.

"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?

Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/

dahawthorne said:
"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?
Click to expand...
Click to collapse
no, its not dead though I was dead for couple days.

Administr4tor said:
Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/
Click to expand...
Click to collapse
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.

thatkindaguy said:
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.
Click to expand...
Click to collapse
Thank you for reply,
- I have adb and fastboot drivers installed from xda when I connect the phone it shows connected, Please check the screenshot.
- I just want to flash stock rom, even if its possible to do it without unlocking bootloader, please let me know.
_ i have already tried NEXUS TOOLKIT and tried to unlock bootloader but it failed to unlock it.
Regards

You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?

geokhentix said:
You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?
Click to expand...
Click to collapse
oh, I didn't do anything, I wokeup and charged it after it went dead, and it all happened,
also sometimes I get this error too if I am not getting those "unfortunate error"

Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.

vicks1008 said:
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.
Click to expand...
Click to collapse
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example

Vivjen said:
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example
Click to expand...
Click to collapse
My Nexus 6 is stuck at LMY48M & I tried pushing the latest Marshmallow OTA build MMB29X.

You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?

Why is your Nexus reported in Device Manager as a Samsung device? As someone who owns a Galaxy S4 as well as a Nexus, you cannot use the Samsung driver in place of the Nexus USB driver.
Change your driver to the Google-provided version and try again.

Vivjen said:
You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?
Click to expand...
Click to collapse
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.

Nexus root toolkit
this toolkit will do all the work for you. from wugfresh development

vicks1008 said:
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.
Click to expand...
Click to collapse
No. Just download OTA from PC and push it to N6 via adb sideload

joseppa87 said:
this toolkit will do all the work for you. from wugfresh development
Click to expand...
Click to collapse
Absolutely. It washed my dishes, took the dog for a walk, and helped me with my homework.

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
sIR, How did you push STOCK OTA and where did you get it from, Can you please tell me steps you followed in details?
Thank you for reading.

The Bootloop of Death - Fix it Challenge

Hi Ppl,
I have a OP3T with unlocked bootloader and stock OTA updated OS. I unlocked the phone several months ago and didn't touch anything in that regard (CustomROM, TWRP, ....)
When I walked down the stairs (no fancy stuff, just moving as humans do who are hungry and go to lunch ) the phone entered bootlooping. My journey begins and up to now I am not able to fix it and need your help.
Things I tried:
Holding vol+ to go into fastboot. Fastboot screen appears, I cannot select anything and phone reboots after 2 secs
Holding vol- seems to stop the looping process but phone doesn't start even with pressing power additionally
Long press of power (the 40ish secs) to power off the phone doesn't work. Phone continues to loop
Followed several guides to get a USB connection (like 10secs holding vol+, connect via usb and inspect the device manager). The expected device is shown for a couple of secs and the phone loops thus the device disappears again.
I let the phone do its looping over night to empty the battery. Woke up in the morning, phone stopped looping (who would have thought that, battery is dead). Started to hold vol+ and tried the whole connect to usb thingie, same result. COM devices disappears after several secs.
Do you, honourable members of this community, can help me with the aforementioned issue? I can't figure out whats wrong and how to fix it.
Thanks in advance

Tried a different cable?
Tried different USB ports?
Tried flashing recovery via fastboot or booting the Recovery img via "fastboot boot twrp.img"?
Reinstalled your ADB, Fastboot and L2 Drivers?
Tried the Oreo Unbrick Tool?
Tried wiping internal storage via "Fastboot format userdata"?

thes3usa said:
Tried a different cable?
Tried different USB ports?
Tried flashing recovery via fastboot or booting the Recovery img via "fastboot boot twrp.img"?
Reinstalled your ADB, Fastboot and L2 Drivers?
Tried the Oreo Unbrick Tool?
Tried wiping internal storage via "Fastboot format userdata"?
Click to expand...
Click to collapse
Different Cable and Ports --> Yes
Fastboot or booting recovery --> see above, not possible since the phone loops every 2secs and the only thing that stopps it is a dead battery
Reinstall of computer resources (driver, ad, L2) --> same, connection is not stable and toggling from connected to disconnected after 2secs
Oreo Unbrick Tool --> same since I can't establish a stable connection
Wipe of internal storage --> same, connection

booyakasha12 said:
When I walked down the stairs [...], the phone entered bootlooping.
Click to expand...
Click to collapse
Have you tried to walk upstairs to make the issue go away?
:cyclops:

booyakasha12 said:
Different Cable and Ports --> Yes
Fastboot or booting recovery --> see above, not possible since the phone loops every 2secs and the only thing that stopps it is a dead battery
Reinstall of computer resources (driver, ad, L2) --> same, connection is not stable and toggling from connected to disconnected after 2secs
Oreo Unbrick Tool --> same since I can't establish a stable connection
Wipe of internal storage --> same, connection
Click to expand...
Click to collapse
Alright so try this. Kind of a janky thing, and it needs a lot of tries. So you have a few seconds before the phone reboots yeah?
On CMD/Powershell, type out the command "fastboot flash recovery twrp.img" before plugging in the device.
Then plug your device in, go to fastboot, and quickly hit enter on Powershell. The flashing takes 1.4S to complete. This should be enough time for TWRP to be flashed.

thes3usa said:
Alright so try this. Kind of a janky thing, and it needs a lot of tries. So you have a few seconds before the phone reboots yeah?
On CMD/Powershell, type out the command "fastboot flash recovery twrp.img" before plugging in the device.
Then plug your device in, go to fastboot, and quickly hit enter on Powershell. The flashing takes 1.4S to complete. This should be enough time for TWRP to be flashed.
Click to expand...
Click to collapse
Okay so I have an update:
target reported max download size of 435159040 bytes
sending 'recovery' (22680 KB)...
OKAY [ 0.557s]
writing 'recovery'...
OKAY [ 0.168s]
finished. total time: 0.729s
So recovery is written succesfully but still the device is bootlooping
Do you have further suggestions?

booyakasha12 said:
Okay so I have an update:
target reported max download size of 435159040 bytes
sending 'recovery' (22680 KB)...
OKAY [ 0.557s]
writing 'recovery'...
OKAY [ 0.168s]
finished. total time: 0.729s
So recovery is written succesfully but still the device is bootlooping
Do you have further suggestions?
Click to expand...
Click to collapse
Can you get into Recovery by holding Power and Vol +?

thes3usa said:
Can you get into Recovery by holding Power and Vol +?
Click to expand...
Click to collapse
Nope. Vol+ and power just shows the fastboot menu (where you usually select start, recovery, power off) but i can't select anything (you probably know from experience it takes some time, say a few secs, until you can select something.)
It shows this screen where it says bootloader unlocked and similar stuff for 2 secs and the loop continues.
The screen I see for 2-3 secs is the following. I can't select anything
{
"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"
}

Maybe power button got stuck somehow? Check ifixit how to open back cover only to be sure.
Edit: Remember something similar happened to my OPO years ago and that solved the issue.

TurboStrutsi said:
Maybe power button got stuck somehow? Check ifixit how to open back cover only to be sure.
Edit: Remember something similar happened to my OPO years ago and that solved the issue.
Click to expand...
Click to collapse
Thought about that also. I also tried to give the phone a hard knock, wiggled the power button and so on without effect.
I guess I have to order the ifixit kit
Further suggestions what to try are still welcome

in the 2(ish) seconds that you have to send an adb command over, are you able to reboot to recovery via that? (adb reboot-recovery or something like that....) and then from the format the internal storage maybe...
this is a complete shot in the dark cus I'm not necessarily sure how the boot partition works (maybe someone could help me out lol.) is it possible to flash a stock boot.img to the boot partition via adb in the brief moment you have connection? just to see if something changes??
good luck on this endeavor of yours