Database Users

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

Stuck in boot loop after flashing twrp recovery/installing supersu

So I flashed the latest firmware, after being unlocked, then rent back to bootloader, flashed recovery, went to recovery and installed file. Then restarted...now stuck in boot loop. It booted before I went to flash recovery in the new firmware just fine.
Do you need to flash something else when you flash recovery?
it says device is corrupt when I restart, but I was under the impression that screen comes up when bootloader is unlocked, so not sure if it means anything

Make sure your using the correct commands!
I did this, and i was accidentally flashing recovery to boot!

Before flashing your phone with new firmware your phone previously rooted in older firmware?

premchandar777 said:
Before flashing your phone with new firmware your phone previously rooted in older firmware?
Click to expand...
Click to collapse
yea, I unlocked it in old firmware, didnt realize my mistake and then downloaded image of newest from google, installed everything, booted fine, then went to send recovery and that causes the corruption/boot loopp

xamius said:
yea, I unlocked it in old firmware, didnt realize my mistake and then downloaded image of newest from google, installed everything, booted fine, then went to send recovery and that causes the corruption/boot loopp
Click to expand...
Click to collapse
The biggest problem in Samsung is that when we flash phone with new firmware it won't delete the entire /system instead it rewrites the /system(sub folders),if you rooted your phone previously which means /su will be made in previous /system folder,now when you flash with new firmware without wiping the previous /system completely,then new firmware will be just rewrites other folder leaving /su since original firmware won't contain /su,since your old /su now corrupted because of misleading binaries that's the reason for you problem
Its possible for you go to recovery now?

premchandar777 said:
The biggest problem in Samsung is that when we flash phone with new firmware it won't delete the entire /system instead it rewrites the /system(sub folders),if you rooted your phone previously which means /su will be made in previous /system folder,now when you flash with new firmware without wiping the previous /system completely,then new firmware will be just rewrites other folder leaving /su since original firmware won't contain /su,since your old /su now corrupted because of misleading binaries that's the reason for you problem
Its possible for you go to recovery now?
Click to expand...
Click to collapse
Samsung? I think you are in the wrong forum mate!

xamius said:
So I flashed the latest firmware, after being unlocked, then rent back to bootloader, flashed recovery, went to recovery and installed file. Then restarted...now stuck in boot loop. It booted before I went to flash recovery in the new firmware just fine.
Do you need to flash something else when you flash recovery?
it says device is corrupt when I restart, but I was under the impression that screen comes up when bootloader is unlocked, so not sure if it means anything
Click to expand...
Click to collapse
We had this problem with the n6 with marshmallow. The fix was to reboot system after flashing the recovery. Then reboot recovery flash SuperSU and a custom kernel before rebooting. Something in the kernel needed to be fixed to allow su. For the n6 there was a stock with fixes boot image available for this if you didn't want a custom kernel. I would suggest reflashing the factory image & reading the forums some more for a kernel that offers the fix you're after.

If you flashed everything from the new image then wouldn't that reset your phone? When you reset the phone it turns off usb debugging in the developer options. I don't know if this makes a difference when flashing in fastboot but after I unlocked the bootloader I booted the phone up, re-enabled developer settings and turned usb debugging back on. I then booted into fastboot and flashed the recovery and it worked fine.

Won't be druv said:
Samsung? I think you are in the wrong forum mate!
Click to expand...
Click to collapse
Sorry I have posted wrong forum but the solution to that problem is correct I feel.

Not sure if you flashed correctly. Follow the unlock root thread. If using SuperSU in addition to flashing to at least factory K you need to flash modified modified boot.img found on correct SuperSU thread.

premchandar777 said:
The biggest problem in Samsung is that when we flash phone with new firmware it won't delete the entire /system instead it rewrites the /system(sub folders),if you rooted your phone previously which means /su will be made in previous /system folder,now when you flash with new firmware without wiping the previous /system completely,then new firmware will be just rewrites other folder leaving /su since original firmware won't contain /su,since your old /su now corrupted because of misleading binaries that's the reason for you problem
Its possible for you go to recovery now?
Click to expand...
Click to collapse
yes I am able to reset everything after rebooting to OS using fastboot continue
what's the solution for this now, to root my phone again?

I have almost the same problem. My device is the sm-t110. I flashed twrp, thinking their android app can flash through zip files. which i dont think it can. I let the battery die to see if it would fix it. but it didnt. Now its not charging because of bootloop. Can't go into recovery mode. And i forced into recovery using flashible and now it tries to boot into recovery, even when charging. And the computer won't pick it up. So Odin won't work. I think of fixing by removing battery or see if samsung can fix it.

Soft Brick/possible full brick in need of help

I was trying to root and unlock boot loader. I was on the latest update B29 and tried following the guide but used the B27 files. I flashed the files got into TWRP but for some reason my system got wiped. I can get into fastboot, recovery, and EDL but when i try to boot my phone regular it boots ZTE boot screen real quick and then goes into a BLACK screen and stays there? Any Suggestions on what I can do? If I try to unlock the bootloader it says failed cannot do remotely probably because my phone system get erased and so the option isnt clicked in phone to allow oem unlock.
I was going to try flashing;
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
There is some kind of problems with android file host does anyone have a copy of these two files hosted somewhere else?
Thanks

Did you make the backups shown in both the twrp flashing guide and the unlock bootloader guide?
Could you provide a little more detail on what you did so far?
neo4uo said:
I was trying to root and unlock boot loader. I was on the latest update B29 and tried following the guide but used the B27 files. I flashed the files got into TWRP but for some reason my system got wiped. I can get into fastboot, recovery, and EDL but when i try to boot my phone regular it boots ZTE boot screen real quick and then goes into a BLACK screen and stays there? Any Suggestions on what I can do? If I try to unlock the bootloader it says failed cannot do remotely probably because my phone system get erased and so the option isnt clicked in phone to allow oem unlock.
I was going to try flashing;
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
There is some kind of problems with android file host does anyone have a copy of these two files hosted somewhere else?
Thanks
Click to expand...
Click to collapse

lafester said:
Did you make the backups shown in both the twrp flashing guide and the unlock bootloader guide?
Could you provide a little more detail on what you did so far?
Click to expand...
Click to collapse
I ended up going to ZTE site and getting there B20 image and flashed back my backed up recovery and boot and flashed the update zip with there recovery and I am back in business now. I was trying to unlock and root but somewhere or how my system got deleted so it would not boot. What is the easiest way to unlock the BL and then root? Is DrakenFX the most up to date way? Anyways thanks for the reply, I was going to download DrakenFX files for stock recovery, but Android File Host is having some problems and you can not download anything from them right now

neo4uo said:
I ended up going to ZTE site and getting there B20 image and flashed back my backed up recovery and boot and flashed the update zip with there recovery and I am back in business now. I was trying to unlock and root but somewhere or how my system got deleted so it would not boot. What is the easiest way to unlock the BL and then root? Is DrakenFX the most up to date way? Anyways thanks for the reply, I was going to download DrakenFX files for stock recovery, but Android File Host is having some problems and you can not download anything from them right now
Click to expand...
Click to collapse
Yes, flash twrp and flash drakenfx unlockbootloader file. Look for the newbie guide to unlocking and follow. Read the thread first as always.

Phone booting back to TWRP

Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.

ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.

PapaMag said:
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.
Click to expand...
Click to collapse
So you had to wipe everything?

ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.

ledvedder said:
So you had to wipe everything?
Click to expand...
Click to collapse
When I flashed 9.0.11 again it wiped the device yes.

_Masked_ said:
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.
Click to expand...
Click to collapse
Obviously you are smarter than me. Thanks for the tip

PapaMag said:
Obviously you are smarter than me. Thanks for the tip
Click to expand...
Click to collapse
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.

_Masked_ said:
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.
Click to expand...
Click to collapse
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk

ledvedder said:
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.

_Masked_ said:
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.
Click to expand...
Click to collapse
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk

Use this if you're on OOS 9.0.5/9.0.6/9.0.7, but if you are on a higher OOS then you need to grab your stock boot.img for 9.0.10 from here and 9.0.11 from here, and patch it yourself using the instructions below.
Connect your phone to your PC using the OnePlus Cable
Reboot to Bootloader using "adb reboot bootloader" on PC while your phone is in TWRP
Rename stock boot .img file to boot.img on PC
Use "fastboot boot boot.img" on PC while your phone is in Fastboot Mode / Bootloader
Follow this guide once you are done with the above steps to root your phone with Magisk and actually boot.

I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.

h8Aramex said:
I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.
Click to expand...
Click to collapse
Try this.

ledvedder said:
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Plug your phone into your PC
Use this command in TWRP's Terminal and type this:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Copy it from your phone to your PC (in the directory your command prompt is in) and use the command:
Code:
fastboot boot boot.img

TWRP doesn't work
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.

dgdeepak000 said:
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.
Click to expand...
Click to collapse
Flash the CORRECT one, for the OnePlus 6T. Not for the OnePlus 6.

Messed up and my phone now cannot boot!

I tried to remove root.
First, I used supersu and used the full unroot setting. However, after rebooting back to android, it is still showing root.
Therefore, I used magisk uninstall. After that my phone is in boot loop with dm-verity error.
Tried to go into TWRP (still works) to install no-verity 6.0 zip but it says boot cannot be found.
So, I am now trying to install recovery.img and boot.img. However, I am unable to find recovery file for WW_15.0410.1807.75 (Android O).
Can anyone help shed some light? How can I restore back the phone without losing data?
If all else fail, what are my last resort to get the phone back to working?
Appreciate any input. Thanks!

Ok, I tried a few things and all failed. Now the phone keep looping into fastboot when I plug in the usb.
I would like to just flash to latest firmware will do. Data recovery is secondary now.
I tried AFT 1.0.0.45 but it only allow zip files. I cannot select the raw file. I tried renaming the raw to zip but it still refuse to flash. I get error saying unable to unzip. However, before that I can see the app is trying to connect to somewhere for verification. I think something about FRP. Don't know what is that.
Appreciate any input on this. Thanks.

abubin said:
So, I am now trying to install recovery.img and boot.img. However, I am unable to find recovery file for WW_15.0410.1807.75 (Android O).
Click to expand...
Click to collapse
if you flash stock ROM, recovery is restored automatically.
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1807.75-user.zip
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1807.75-user.zip

aIecxs said:
if you flash stock ROM, recovery is restored automatically.
View attachment 5825195
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1807.75-user.zip
View attachment 5825209
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1807.75-user.zip
Click to expand...
Click to collapse
Thanks! I manage to flash the stock ROM and it is able to boot into the OS again.
However, I am still seeing this "DM-verity in EID" screen whenever I boot up. Is this okay? Cause I remember this screen wasn't shown previously. It supposed to show a screen saying bootloader is unlocked and some security thing. Now it's showing this EID screen. Anyway to fix it?

if there is something like vbmeta partition, flash vbmeta.img otherwise I don't know. the screen ask for locking bootloader, but I do not recommend this. usually locking bootloader only works if every partition is stock, I doubt the locking process will fix anything.