Requesting urgent help - Lenovo ZUK Z2 (Plus) Questions & Answers

Hello everyone
I was trying to do an OTA update for AOSP Extended custom rom on a Lenovo ZUK Z2 Plus phone from its then v6.2 to v6.6 and along the way encountered many problems and now my phone is now in an unusable state.
I'll state the issues I encountered in order:
-Do above mentioned OTA update for AOSP Extended. It downloads and shows it installed successfully but upon restart it refuses to boot the OS
-Stuck on that black screen with options for recovery. I think it is called fastboot screen? or perhaps bootloader screen. The one where you use volume keys to navigate.
-I chose Recovery option and it opened up TWRP. I clicked Install and selected my ROM manually but then was unable to install a newly downloaded AOSP due to an error #7
-I figure maybe updating TWRP to the latest version will help. I flash TWRP img and reboot.
-Upon reboot I find myself unable to even get back into recovery!.. the option to enter recovery exists but whenever I pick it it just restarts and throws me back to the fastload/bootloader black screen.
-I was stuck here for several hours before deciding to flash stock firmware via QFIL since fastboot was still working fine.
-I successfully flash stock firmware through QFIL using my computer. I reboot the phone and now a new issue:
I press the power button to turn my phone on but my phone screen briefly flashes a dimly lit black screen and then goes off, again flashes the black screen and goes off again. It keeps repeating this in a continuous unending loop.
I am literally out of ideas. I don't even want to get the stock rom anymore just want a usable phone again : (
I would greatly appreciate any help please.
Thank you for your time.

I wanted to post an update.
I was able to get out of this strange loop by holding power button and pressing volume up as soon as the led lit once and before the ZUK logo popped up.
Afterwards I did the Power+ Volume UP + Plug USB cable to get the qualcomm port thing and re-try flashing Stock firmware. Unfortunately the same problem after flashing, no errors in log, with the black screen being lit and then off again in loop. Could anyone tell me how to get to custom rom or even stock firmware from this position please.

The only thing you can do is QFIL stock rom. That should solve the problem. Try doing it correctly one more time and report with any type of errors.
Don't worry it'll be fine. Any type of software related problems can be solved just have to keep trying, who knows what solution may work!

the_harsh said:
The only thing you can do is QFIL stock rom. That should solve the problem. Try doing it correctly one more time and report with any type of errors.
Don't worry it'll be fine. Any type of software related problems can be solved just have to keep trying, who knows what solution may work!
Click to expand...
Click to collapse
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
{
"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"
}

Maky-313 said:
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
Click to expand...
Click to collapse
Flashing this ROM should solve the issue however flash again to confirm. I was in the same situation before but I don't remember exactly what I did.
Try pressing all three buttons (+- and power).

Maky-313 said:
Could you guide me to a specific stock rom I can use with QFIL method please?
I used a ' Lenovo_Zuk_Z2_Z2132_EN_OPEN_USER_Q01080.2_N_ZUI_2.5.104_ST_170418_QPST ' however now whenever I power my phone it takes me to this screen always:
Click to expand...
Click to collapse
okay this is strange....never encountered this screen before. Can you put your phone to EDL mode? If yes then try doing a QFIL any 3.5+ ZUI. It should solve the problem!
Although I've once successfully flashed ZUI 4.0.199, you can follow this guide for 3.5:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/oreo-zuio3-5-099dev-z2-t3719682

the_harsh said:
okay this is strange....never encountered this screen before. Can you put your phone to EDL mode? If yes then try doing a QFIL any 3.5+ ZUI. It should solve the problem!
Although I've once successfully flashed ZUI 4.0.199, you can follow this guide for 3.5:
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/oreo-zuio3-5-099dev-z2-t3719682
Click to expand...
Click to collapse
I am currently downloading a Z2131_CN_OPEN_USER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip for another thread. Is this the same as one of the ones in the thread linked by you? If not I'll abort.
Also, I previously had AOSP 6.2 which iirc was based on Android 9.0, do you feel perhaps me trying to flash older stock roms such as the earlier oreo(I think) based ones are causing issues? or is that not a problem flashing older android version based firmware/roms.

Maky-313 said:
I am currently downloading a Z2131_CN_OPEN_USER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip for another thread. Is this the same as one of the ones in the thread linked by you? If not I'll abort.
Also, I previously had AOSP 6.2 which iirc was based on Android 9.0, do you feel perhaps me trying to flash older stock roms such as the earlier oreo(I think) based ones are causing issues? or is that not a problem flashing older android version based firmware/roms.
Click to expand...
Click to collapse
well, i guess you've downloaded and tried it as it's been more than an hour now. also if you had AEX (not AOSP I presume) 6.2 then you must have flashed 3.5 to update the firmware, so flashing older one can be a problem. Is the new one working?

the_harsh said:
well, i guess you've downloaded and tried it as it's been more than an hour now. also if you had AEX (not AOSP I presume) 6.2 then you must have flashed 3.5 to update the firmware, so flashing older one can be a problem. Is the new one working?
Click to expand...
Click to collapse
I went ahead and downloaded the Zui.3.5.389.qpst from your earlier linked thread. I used QFIL just now to flash it, unfortunately the phone still won't boot.
When I press the power button the white LED turns on for a second and then goes off after which is just a Solid black screen throughout. Doesn't make difference if I press the power button and let go or hold the power button down the same behaviour each time.
This was also the behaviour on earlier flashes of 1_M_ZUI_2.0.093_ST_160811_qpst & 2_N_ZUI_2.5.104_ST_170418_QPST : (

Maky-313 said:
I went ahead and downloaded the Zui.3.5.389.qpst from your earlier linked thread. I used QFIL just now to flash it, unfortunately the phone still won't boot.
When I press the power button the white LED turns on for a second and then goes off after which is just a Solid black screen throughout. Doesn't make difference if I press the power button and let go or hold the power button down the same behaviour each time.
This was also the behaviour on earlier flashes of 1_M_ZUI_2.0.093_ST_160811_qpst & 2_N_ZUI_2.5.104_ST_170418_QPST : (
Click to expand...
Click to collapse
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?

the_harsh said:
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
Click to expand...
Click to collapse
I think its recognised as the correct qualcomm device under ports in device manager but I will take a screenshot for you so you can have a look.
and later today I'll reflash and save a log this time for the same 3.5 ROM and share that as well.

Samirmathakiya said:
Flashing this ROM should solve the issue however flash again to confirm. I was in the same situation before but I don't remember exactly what I did.
Try pressing all three buttons (+- and power).
Click to expand...
Click to collapse
the_harsh said:
are you sure your phone is being recognized in PC correctly and the flashing stock ROM don't endup in any error?
Click to expand...
Click to collapse
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.

Maky-313 said:
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Click to expand...
Click to collapse
Stick with official lineage os now
https://download.lineageos.org/z2_plus

Maky-313 said:
guys it worked! I just decided to leave it plugged into the charger for a while and left.
After coming back I long-pressed the power button to make sure it was powered off before attempting to use the key combination to put it in EDL mode and I guess I pressed it too short or let go of the power perhaps but it booted right into the OS : )
I feel now that earlier perhaps the phone didn't have enough charge to go past the initial zuk booting logo perhaps? I did not charge it since yesterday and would only be plugged into the usb for edl attempts, perhaps that was just enough to get flashing but not enough to boot the phone. I now wonder if previous flashing attempts were indeed successful and I just didn't have the battery to get it past the initial boot logo screen : S...
One last request please : )
I would like you guys to advise a custom rom for me please. I am looking for a stock android experience wherein the UI is very smooth and slick, I would also like to have a long battery life please if possible. I don't play games etc. so 3d performance or processing power is not a priority.
Thank you.
Click to expand...
Click to collapse
Derp caf pie is also very good..
On it for 3 days now and quite stable rom.. definitely recommend

congratulations on getting it done! as a thankyou gesture you can give me party in Starbucks ? (JK).
For Custom ROM
If you want something with customizations I'd say go with AOSiP pie. The best and latest I've used.
But if you want to stick more to the stock Android side you should go with Lineage pie. It's the best in business.

the_harsh said:
congratulations on getting it done! as a thankyou gesture you can give me party in Starbucks (JK).
For Custom ROM
If you want something with customizations I'd say go with AOSiP pie. The best and latest I've used.
But if you want to stick more to the stock Android side you should go with Lineage pie. It's the best in business.
Click to expand...
Click to collapse
yup yup I went ahead with the Lineage OS 16 as it seemed to be very popular. So far so good.
Thank you and everyone else for your help. God bless : )

Related

[GUIDE]How to unbrick your Defy and solve other bugs

So your Defy is bricked. It's really hard to brick a Defy or a Defy+ due to locked bootloader, so you can't really brick it but you can get it in state of not booting. In this simple guide i will show you how to unbrick Defy and fix some common errors!
Lets get started!
How to unbrick your Defy
What do you need!
You need the following:
Motorola Defy
RSD Lite (download here: http://goo.gl/KRSRp
SBF (i reccomend 2.2 CEE Froyo) (download here: http://goo.gl/Jhz84) (for other SBFs use this link: http://goo.gl/dYQTl )
USB Cable
Charged battery (at least 50%)
Motorola USB Drivers (download here: http://goo.gl/bWg1M )
Download and install USB Drivers
Download and install RSD Lite
Turn off your phone
Go into bootloader by pressing Power button and Vol+ button
Connect your phone to your PC via USB cable
Make sure everything is OK
Locate downloaded SBF. In popup dialog press Uncompress and start flashing
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
That's it, you unbricked your Defy!
How to repair damaged Dalvik or cache
Use the same method for unbricking your Defy. If you still have problems...do the same procedure again.
How to fix empty battery
If your battery is so empty that you can't even charge it, there are 2 options
Option 1. (McGyver method)
Get a USB cable, cut the off the B plug (the one that plugs into the device) and strip away the shielding, revealing the 4 individual wires inside: White, Green, Red and Black. Red is +5V DC and Black is ground. strip a few (1-2) mm's off each and gently push them into the + and - slots on the battery. Apply some tape to keep them in place, but don't cover the other connectors. Now plug the battery back in, a tight fit, but possible if you've peeled back the shielding and the white and green wires so that only Black and Red are actually being crammed in there with the battery
It should look like 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"
}
Red goes to the + terminal,Black goes to the - terminal
Plug the business end of the newly modded usb cable into your computer.
That's it, your Defy should be alive now
McGyver method found at this thread:http://forum.xda-developers.com/showthread.php?t=892026
I was lazy to write the method by my words...so i just copied from that thread....because he wrote it so well
If original author has problems with copyrights, he can PM me and we will sort it out.
Option 2.
Connect Defy to PC via USB cable. Make sure that your PC is powered on. LED in the top left-hand corner should be white coloured. Leave the Defy overnight to charge. In the morning it should be charged a little bit to charge it via normal method
I have not tested McGyver method, but option 2 worked for me (happened to me once)
This is the end of this tutorial. I hope i helped!
Froyo nandroid backup here
Guys I created a prerooted and with cwm installed froyo nandroid backup. Make full restore
Link: http://d-h.st/RxH
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE DURING THE PROCESS I AM NOT RESPONSIBLE!
is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.
prax31 said:
is cee froyo recommended for india defy with stock froyo 2.2.2 and green lens?
my stock was retail taiwanese JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf.gz
reply please.
Click to expand...
Click to collapse
Well try it...you can always go back by flashing another SBF
IF YOU DO MAKE ANY DAMAGE TO YOUR PHONE , I AM NOT RESPONSIBLE!
bricked/not booting defy
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(
melowed said:
basically downloaded & flashed a wrong sbf file after i rooted it from rsd lite. now its stuck at M screen, will not connect to rsd lite and i have searched relentlessly to figure out another way to flash to it, even in recovery mode will not unzip any files. is there a way to fix it? i have wiped cache and data and rebooted. nothing works...pls help :'(
Click to expand...
Click to collapse
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!
bricked/not booting defy
ppero196 said:
Pull battery out and wait 5 minutes and reinsert it.
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
tried that, still not working
melowed said:
tried that, still not working
Click to expand...
Click to collapse
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!
bricked/not booting defy
ppero196 said:
Go manually to bootmenu (stock) and then connect phone with RSD Lite and flash another SBF
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
i can get it to go to boot menu but it wont connect to rsd lite for me to flash another sbf. is there some other way im not aware of?
I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!
bricked/not booting defy
ppero196 said:
I can send you my froyo nandroid backup. You can restore it via CWM
No apps installed...it comes pre rooted. OK?
Sent from my house via interwebs to You!
Click to expand...
Click to collapse
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!
i need help asap
melowed said:
Awesome thx see if that works
FINALLY got it back to stock after upgrading to the the 5.9v of rsd lite and reinstalling the drivers but i had to flash the same sbf file about 4 times...lol i knew i had the right one but thanks for trying to help me anyway!
Click to expand...
Click to collapse
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?
drakefrancis said:
Can you send me also the froyo back up? this is what happened to me:
i cleared the cache in the bootloader menu
then i restore factory settings
then i had a zip file of a rom , i changed its name to update so that the bootloader can detect the update.. the update installed completely but when i started rebooting its just stuck at the "Motorola" logo.. what can i do to fix this sir?
Click to expand...
Click to collapse
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app
ppero196 said:
OK..I'll send you...
It comes with 2ndinit and prerooted
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Hey ppero, Thanks for the guide.
Some random Chinese build finally worked for my phone, phone was bough used: http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Froyo nandroid backup
Extract in the root of SD card and restore using cwm
Make full restore
http://d-h.st/RxH
Sent from my iPhone 5 using Tapatalk 2
bricked MB526 BL7 no recovery available
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance
butcherr said:
Hello, I try to give as much information as possible so please bear with me.
MB526 with BL7 was working perfectly with the quarx nightly 20121018+update v3 but of course I installed the v4 update. What a friend and I figured is that there is a problem when flashing the 2ndboot updates with your power plug still plugged in, this is what I totally forgot about on the v4 update. I wiped the cache and dalvik before AND after the update but was stuck the bootloop. Now I had just made a CWM backup two weeks ago but when restoring I got an error message concerning the system folder. Still in bootloop on the splah M logo. I remember there was something about an older custom ROM and the recovery I used that didnt work so I figured I should start from the SBF.
Using RSDlite 5.7 on a winXP machine, I tried to flash the way I am used to flash brand new MB526 with BL7: (did that for a few friends and the girl)
1. DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
2. DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
but the plan was overthrown by my phone. It flashed through the whole process but was stuck at the the "please manually power up this phone"-screen in RSDlite, the phone was connected but at the splash screen. Battery out, the PASS would only appear in RSD if I boot directly into bootloader again. Otherwise this splash screen makes my mad. It doesnt boot.
I tried to flash the alternative, chinese, root ROM for BL7; samesame, but different.
Downloaded RSDlite 6.14, Mdriver 5.9 on a win7 machine, used about all the BL7 ROMs I could find on the site: sbf.droid-developers.org/umts_jordanplus/ The last one being the [Retail British] sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_BLUR_SIGN_USADEFYEMARAB1B8RTGB005.0R_PDS03C_USAJRDNGIBRRTGB_P023_A025_M002_Service1FF.sbf.gz
samesame
:crying:
Now I cannot boot into the motorola recovery. Theres just the background picture but no menu. As far as I know, flashing an SBF is all that I can do. Anyone has got an idea, which ROM to try or what else to do ?
Thanks in advance
Click to expand...
Click to collapse
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere
ppero196 said:
Flash the sbf again.
If you encounter please manually power up the phone unplug the device from PC, reboot into stock recovery and wipe data/factory reset. After that reboot
Trolls, trolls everywhere
Click to expand...
Click to collapse
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?
butcherr said:
thank you. stock recovery. there is no stock recovery. MB526. BL7. Just the droid and a triangle with the "!" inside the triangle if I try to boot into stock recovery. I remember having this problem with my hannspad and there was a flashable ROM with just the stock recovery. Is there something comparable for the defy? only the recovery or is the BL7 the problem here?
Click to expand...
Click to collapse
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.
_ossie_ said:
That is Stock recovery (droid and yellow triangle) .Try pressing Vol Up and Vol Down simultaneously to get the menu. If that doesn't work TAP in the lower right hand corner of the screen to get the menu. Tap around a bit to get the right spot.
The newer stock recovery works off touch screen instead of the rocker buttons.
Click to expand...
Click to collapse
Thank you VERY much. I spent too much time with CWM it appears. I dont remember having used the stock recovery once. I thought BL7 was my enemy with that screen. My phone must feel like its been gangbangraped now with all the different ROMS I have flash upon it. Thanks again, quarx build 20121018+v4 running. Am creating a backup right now.
When I connect to pc (battery empty) it charges white led then boots up hangs on motorola logo for sometime then shutsdown to white led again, is that normal?

Save My Note 4

Would someone mind helping me out, I cant use my phone any more. The last thing I did was install Emotion OS and then I installed the Emotion Kernel, upon reboot the phone was stuck on the emotion boot screen after restarting the phone Im not sure how it happened however the phone went from TWRP to some recovery that looks like the lineageos logo, I cant install any updates from this recovery and my phone via USB in download mode or ADB is not detected by any computer I have tried 3 computers in my house. I have never seen this recovery screen and I do not know what to do. I downloaded a stock MM firmware and converted it to a zip file from a tutorial on here however I keep getting an error message from this recovery. I really need my phone back up and running Im not sure what the heck happened.
Continued from other posts
Quote:
Originally Posted by shadeau
Do you have any options in recovery? Even if you could perform a "factory reset" with lineage OS you'd at least be able to enable ADB and reinstall TWRP. Also, when you say that the phone isn't recognized by the computer does that mean ADB, ODIN, and your OS don't recognize the phone?
So I do have options in this Lineage Recover but I cant get anything to work, Here are my options Reboot System Now, Apply Update, Factory Reset, Advanced. I have already tried factory reset however I may have deleted the OS all together with the Wipe Data Option. When I reboot the phone it stays on the the Samsung Galaxy Note 4 Screen with the little padlock that shows my bootloader is unlocked. I was messing around with flashing betwen several roms, I went from CM 14.1 to Lineage to Emotion OS, I then flashed the emotion kernel. If I select Apply update it gives me these several options, Apply from ADB choose from emulated (no typo) choose from sdcard1. I have tried to sideload via adb shell and my pc ( have tried multiple computers) does not detect the device. I even went to the extent of reinstalling windows and all Samsung USB and ADB drivers. Selecting choose from sdcard1 I can see the various zip files on my sd card however when it goes to install any roms it fails and just says error. There is a error log however it will not let me view these. My phone before this stopped connecting to any pc's I could plug the phone in via usb and it would charge but I would not get any notifications from windows! I will seriously send money to who ever can hlep me out I do not want to shell out for a new phone. Placing the phone in download mode still works however odin will not detect the phone either lol what the heck is going on here. I do have a micro sd card reader for the mc so i can place files on the phones card but I dont know what kind of file this recovery is looking for. I do not know how this recovery even got on here as I have been using TWRP from the very beginning. Please help me
I have never seen this recovery it has the lineage os logo and just says RECOVERY. I wish I could take a picture of the screen.
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
ziggsta2 said:
I have also tried renaming files on my sd card as update.zip and this does not help. It comes back with an error every time.
Click to expand...
Click to collapse
Are you using the Samsung OEM USB cord?
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
good questions will try another usb cable all I have is 1 for right now
quinciebee said:
Are you using the Samsung OEM USB cord?
Click to expand...
Click to collapse
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
quinciebee said:
It sounds likes it's the default factory recovery, you probably lost TWRP when you flashed the rom. When Odin recognizes your phone again, just Odin TWRP in there through download mode and you should be good to go.
Click to expand...
Click to collapse
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
ziggsta2 said:
When I plug my phone into a USB port I get a grey battery icon however it doesn't appear that its doing anything, is it possible I have a bad usb port on my phone? Odin wont recognize it, I have yet to find a single computer to see my phone, and I have now tried multiple USB cables.
Click to expand...
Click to collapse
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
quinciebee said:
Try unplugging your phone completely, pull the battery, boot into download mode, then plug it into your computer using the Samsung USB cord.
Click to expand...
Click to collapse
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
ziggsta2 said:
I wish that was the fix, I have tried everything at this point, for the life of me i cannot get any pc to recognize this phone. If I could get odin to detect the phone I would be all set
Click to expand...
Click to collapse
CHECK THIS OUT People are having the same issues
https://forum.xda-developers.com/android/help/phone-stuck-bootloop-t3510266
{
"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"
}
ziggsta2 said:
Click to expand...
Click to collapse
In the advanced menu is there an option to "mount system" or something? Also see if there's a setting in there for chmod
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
ziggsta2 said:
I actually ordered a new note 4 I believe my device is dead I will have to charge it as when I try to boot into recovery the words no command flash very quickly on the bottom of the screen, I do know I saw mount system I remember trying it and it didn't do anything but I will charge it tonight and try it. I have read about the nexus 6p and how 7.1.1 has bricked alot of devices, do you think upgrading to Emotion Os 7.1 was the culprit?
Click to expand...
Click to collapse
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
shadeau said:
I just tried EmotionOS over the weekend and had no issues so I'm not sure that's the culprit. I think you accidentally flashed something into the recovery partition that broke it. Another possibility is that the latest EmotionOS build is specifically designed for the custom TWRP that @hsbadr made. I used that to flash EmotionOS then returned to stock TWRP to flash a different ROM.
Click to expand...
Click to collapse
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
ziggsta2 said:
You know what you might be right I don't remember ever changing TWRP, what is weird is that I lost all usb connectivity too a point that could be due to a damaged usb port, too many unknowns at this point. It was a little embarrassing in the household when I had to admit that I bricked my phone. I was asked if I was going to mess with my new phone......I will have it rooted and unlocked TONIGHT lol
Click to expand...
Click to collapse
Well, good luck! Send me a PM if you have trouble finding the links to unlocking and rooting.
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
mojoswagger1980 said:
Ha I got there too man . pretty cool recovery wish I wouldn't have fixed it so fast might try duplicate your accident. OK its an easy fix just flash twrp in Odin for our device then boot back into twrp and do a complete wipe (might not be possible if u can't see sdcard if that is case wipe data system cache art/cache then install then wipe the internal after ROM flash . at this point I would factory reset and backup but hey that's me . anyway should be fine from here. BTW did you select the DL recovery option in dev options? I was wondering if that's how I got there the (lineage recovery) the first time. Lol your post made me want to check it out. Omg bud i almost forgot and this is crucial. Aosp ROMs like emotion take a long long time to boot the first time(damn near 15 mins) ! The last thing you want to do is mistake this for a bootloop
Click to expand...
Click to collapse
Ouch ! I kinda failed to take into account the very real possibility the ROM you wished to flash might not be on your device and you may have no means to get it there.....in which case flash twrp then you need (if you don't want relock bootloader) to flash a system only image . vague I know I'm thinking .....bottom line is whatever you flash cannot contain aboot image or you will relock boot loader. If on 6.0.1 boot loader there is a safeupgrade to the most recent firmware that won't relock if on 5.1.1 (bpa1 ) idk if there is one . I think there is . in fact I'm sure there is hsbrad made Odin flashable IMG for all Verizon note 4 firmware broth dev and retail . look under his profile on XDA should link you to it
ziggsta2 said:
Do you know what recovery this is? It has the lineage symbol! I cant find a picture of it any where if someone knew what recovery it was maybe then I could research info from the name
Click to expand...
Click to collapse
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
weard1212 said:
That is the lineage os recovery it comes in every build, you must have hit update recovery in the developer options of the settings menu. You just need to reflash twrp like you did when you unlocked your bootloader.
Click to expand...
Click to collapse
Yeah ty I went ahead and tried last night cause I was bored ....meh lack luster . oh and I did it intentionally and just restored recovery with flashify and I just realized this probably wasn't directed at me but yep lineage

Note 10+ SM-N975F/DS very very HARD BRICK --- Advice?

After years of flashing roms (and lurking here, especially DrKetan´s thread), I hard bricked my brand new SM-N975F. When I power it on, it goes to the screen that tells me the bootloader is unlocked, then to a welcome screen, and that is where it stays. (see pics).
I have tried the following:
1) All possible hardware combinations. (I tried at least 100 times all combinations between the keys): always the same.
2) Odin3 does not detect the phone in either screen.
3) Samsung Tool 300K does not detect the phone.
4) ADB does not detect the phone. (adb devices comes empty)
I am about to get a hammer and wreck the little guy, but I decided to ask you first.
Any ideas?
{
"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 think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Sent from my SM-N975F using Tapatalk
carlitobahsoun said:
i think if u post what firmware u was and what did u flashed or what u did ,,, its better that maybe someone can help
Click to expand...
Click to collapse
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
dk1965 said:
Thank you! I was on stock ROM (Q), with an unlocked bootloader. I was flashing TWRP for Android Q with Odin. It "Pass"ed, and when I rebooted it bricked. Tried every key combination, I can´t get into download mode and the phone is not recognized when connected to the laptop. Tried several cables, too.
Click to expand...
Click to collapse
i think ur fault was when u let it reboot / u must after odin twrp forced to reboot to custom twrp recovery and do as i think format data , well never root my samsung mobiles 3 years ago , i advice u to be cool + send private msg to dr ketan to get help OR if u have telegrams u can join many group and i know u will get help.
iam out of telegram 1 years ago too so i dont know any groups for n10+ .
try first dr ketan by pm him and wait till anyone read here and help
Sent from my SM-N975F using Tapatalk
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
ziotom2 said:
you should put the phone in download mode and reflash stock from odin.
reboot [down+pwr] when the screen shut down immediately put the usb cable in the phone usb port (the other already in the port of the pc) keeping the vol down till enters in download mode.
you cannot flash just the twrp partition, you have to flash the disable verity check as well. otherwise the bootloader dont't allow the bootstrap as the integrity check fails.
follow the dr.ketan instructions (carefully).
Inviato dal mio SM-N975F utilizzando Tapatalk
Click to expand...
Click to collapse
Thank you! I tried Dr Ketan´s instructions, but no matter how hard I try, I can´t get to the download mode. I followed your instructions but the phone does not go to download mode, it just shows the "bootloader modified" screen, then the other one. Odin (nor Samsung Tool 300K) do not recognize the phone at any time, not even for a second, so I can´t flash anything to it.
Sm-n975f hard brick - solved
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
dk1965 said:
I hard bricked my SMN975F by uploading the wrong TWRP. The bootloader was already unlocked, but the new TWRP for Q bricked it.
I solved it by sending the phone to a Samsung repair shop. It took them 24 hours (and about 70 dollars), but they were able to flash the bootloader, and the stock Q rom.
Moral of the story: if your Note 10+ is hard bricked, there is a solution. You can try the advice given to me above by these useful members, but if that fails do not toss the phone. Go to a Samsung service store, and they will be able to fix it. Thank you all for their help!
Click to expand...
Click to collapse
happy they solve it but let me be honest with u , in my country LEBANON middle east i KNOW and more knowledge than SAMSUNG'S guys inside , some small questions they wasent able to answer....so u are lucky guys that in ur country they are good knowledge to fix....
happy new year and keep enjoy ur n10+
Sent from my SM-N975F using Tapatalk
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
I know you said you tried 100 times, different combinations, by any chance was this - Press and hold the Volume Up + Bixby / Power buttons. - one of them? It should boot into recovery mode not download mode. I had a similar issue, I had to try and try until I was able to get into recovery, from there did wipe data/factory reset several time, and then select reboot to bootloader, then flash the latest firmware(since you probably wont know which booltloader you have on it). Also remember to used the recommended Odin by the XDA team.
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Note 10+ SM-N975F/DS very very HARD BRICK --- Advice?
Andrewtst said:
Try following alternate way.
- Turn Off Phone, if unable to turn off, wait till battery drain and off itself.
- Press and hold the Volume up and the Power keys at the same time for 3-4 seconds.
- This will bring you to Recovery Screen.
- Use Volume Up and Down Button to Navigate and choose Reboot to bootloader by pressing the power button.
- You are now at Download Mode.
Click to expand...
Click to collapse
Thank you for your feedback. I had tried that, but the recovery screen did not come up. The method you suggest will work for most cases, but in my case I had screwed up the recovery itself by flashing the wrong TWRP.
Moral of the story: do not flash the wrong TWRP, because it may corrupt your recovery, and then getting to download mode is a lot more complicated.
exocetdj said:
You f##ked it real good but not a hard brick as far as I'm aware. (I may be wrong)
Hard brick is only fixable with a new motherboard.
Well done on getting it sorted and that's great service from sammy
Click to expand...
Click to collapse
I agree with you, real good. It may not be a complete hard brick, as the repair guys did not open the phone nor changed the motherboard. Still, it was as bad as a soft brick can get....
ust buy a z3 and fix it lol
Samsung Smart Switch
As far as I know, Samsung Smart Switch is the only method to recover your phone. Download it on your pc. Launch the app and connect your phone. Choose to recover bricked phone.
I bricked about 8 different phones with the new A/B thing before I learned TWRP doesn't work and the fix was to flash the stock boot.img to both partitions with:
./fastboot flash boot --slot all <nameofboot.img>
Download the modded version of Odin. Here's a link to it in my Google Drive: https://drive.google.com/folderview?id=10F5bh4YmD0vAduSMfuqF7jQl4ho1s83a
Sent from my [device_name] using XDA-Developers Legacy app
Did it work buddy?
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issue
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Plz delete
---------- Post added at 06:20 PM ---------- Previous post was at 06:03 PM ----------
vs|porkchop said:
Sm-n975f hard brick - solved
Guys I solved it. I pressed Volume down + Power, as soon as the screen turned off I quickly pressed Volume up +Volume down as I inserted the cable and voila! Download mode. Now I can reflash stock firmware
That was a very close call.
Click to expand...
Click to collapse
YEAH you saved my ass!!!
Thank you wherever your are :victory:
God bless you :angel:

G960F/DS not booting system nor recovery

I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Jogius said:
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Click to expand...
Click to collapse
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
SubwayChamp said:
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
Click to expand...
Click to collapse
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Jogius said:
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Click to expand...
Click to collapse
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
SubwayChamp said:
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
Click to expand...
Click to collapse
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around 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"
}
Jogius said:
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
View attachment 5478243View attachment 5478245
Click to expand...
Click to collapse
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
SubwayChamp said:
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
Click to expand...
Click to collapse
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
frp still allows you to boot, it just will ask for your google account when setting the phone up
Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
FRP works mainly in two ways, when you didn't enable OEM unlock and of course USB debugging then FRP detects an unofficial attempt to inject some custom binary rejecting to boot to system, (What would be the purpose of FRP if you could flash a custom binary, rooting it and then pulling all the data you want?) sometimes this is bypassed by formatting data either booting to recovery (that you say you can't do at this time) or flashing the CSC different from the CSC_HOME, this will wipe/format all your data. And the second instance where FRP can be trigger is when the device was black listed (plus the Samsung account if the last owner didn't log out). The first thing you have to do when buying a Samsung device is logging into the two accounts, then formatting data, and from there you can do what you want.

Question Poco f3 battery stuck

{
"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"
}
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Zinnz said:
There can be bugs on the weekly builds. Use the stable builds if you don't want to deal with potential bugs
Click to expand...
Click to collapse
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
fireclouu said:
i even rollback to global stock rom , same results, maybe ill bring my phone to service center, it may be an isolated case
Click to expand...
Click to collapse
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Zinnz said:
I wouldn't go to a service center unless it's a hardware issue. You should be able to fix it, it just may take awhile of trial and error. you already have more knowledge than the average service center tech when it comes to flashing roms and whatnot, they're just wanna send it away most likely.
Also, could you summarize the issue you're having? It will increase your chances of someone replying with a potential fix
Click to expand...
Click to collapse
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
There are Deep Flash Cables, I don't know if those work on Poco F3..
fireclouu said:
i thought so too about flashing and stuff yeah xda rules!
but this one im not sure but it was not the usual software issue. I tried jumping from every roms i know, eu, lineage, arrow and still stuck at 100%
I also tried reverting it back to fastboot global stock roms, even the old ones and still facing the same issue
im now looking at flashing my device on edl mode. I remember my old phone I have redmi 5a, I got broken sensors due to jumping from xiaomi.eu to stock rom, even fastboot roms wont help, and the only thing fixes the sensors back to normal was edl mode flashing.
but edl mode is a pain when it comes to pocof3 , it needs to short some test points and to have authorize mi accounts just to get it done
Click to expand...
Click to collapse
Just wanna ask a few questions to exclude them
Have you tried using a different USB cable /different USB port on your pc?
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
If you do think it's a hardware issue, it couldn't hurt to flash to stock and see what service center / xiaomi can do. I just wouldn't mention anything about the whole flashing business lol. But yeah, they might swap it out for ya best case scenario. But might be without a phone for awhile :/
fireclouu said:
View attachment 5686001
steady 100% overnight while playing for 5 hours, thats not good i think
My story before I got into this mess:
I received my phone as a christmas gift to myself on January 2022
I really want to remove those bloatwares so obviously I'll unlock its bootloader and flash custom roms. I tested every roms available on a whole month of february and stayed for xiaomi.eu since I want the feels of miui but not the global one.
So far so good and im happy with eu rom until 22.8.10 update.
August 12, lunchbreak at work I decided to push some updates on my device. After flashing I still have almost 70-60% , I used it until 10%, after charging it my phne constantly loops at fast-charging animation and low power warning. I thought my cables were faulty or the charger plug itself. I didnt do anything and after a while it was okay.
about an hour later it just reboots itself, constantly powering on and off, unable to start itself, and after a while, i think 4-6 unsuccessful reboots and it fixes itself.
I just slept for a day not noticing anything. The morning I woke up, this is where i notice omething strange happen with my battery stuck at 100% even using some battery intensive apps before going to bed, looked up at battery stats and saw it stays constant for 16 hours.
I thought might be a bad update then I factory reset the phone. Still sitting at 100. I flashed previous version. No changes. This is the point I worried. I downloaded that 5 gigabyte fastboot rom of poco f3 global and still no signs of luck, I even choose to lock bootloader , still the same issue.
After collecting some infos, someone on TG said it might be related to PMIC breaking things up, ahardware-related issue.
Anyone having this? Thanks
Click to expand...
Click to collapse
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Have you tried using a different USB cable /different USB port on your pc?
Click to expand...
Click to collapse
yup i thought my cables are faulty so i borrow other cable thats also come from xiaomi
Have you tried entering recovery and factory reseting the phone before a new Rom flash?
Click to expand...
Click to collapse
done that too, I formatted the device before flashing it again, only dirty flash on eu update, after my issue arises ive done clean flash, does also too before reflashing stock rom on fastboot
Have you tried factory reseting the phone via settings after a new Rom flash, and after the phone boots up?
Click to expand...
Click to collapse
done as well, even on stock rom, i also lock my bootloader just to be sure, but still at 100%
one thing I also did was manually flashing persist but it wouldnt let me in, I tried also on recovery terminal, via orangefox, and twrp.
tried flashing persist manually too using
Code:
dd
, output says it pushed successfully but I dont think so. fastboot disabled flashing persist, needs edl mode.
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
oh this is new to me, okay ill try bootloader, wish me luck flash it rn
Rstment ^m^ said:
How did you flash new firmware? Via PC? If yes reflash it again then proceed with stepa below ( When flashing select clean all , you don't need to lock bootloader just yet so don't select lock )
You need to enter bootloader mode ( Power on phone while holding volume down , then type fastboot reboot bootloader. You must do it like this! Just holding volume down doesn't enter bootloader , instead it enters a stripped down version of it... Don't know what it's called... )
Reboot phone after doing this , if battery still isn't fixed flash back to stock , lock bootloader and go to service center. Don't even bother with anything else , pmic is supposed to reset when you enter bootloader ( Maybe it even resets in stripped bootloader but just to be safe do enter true boatloader like described above ) . If it isn't fixed it's likely a hardware issue
Click to expand...
Click to collapse
didnt fixed too, i even booted to fastbootd tried flashing there but boot_ab inaccessible, only in normal fastboot
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
cyanGalaxy said:
I had to flash a ROM through EDL Mode once (I hardbricked my phone). I had to pay someone on Telegram with an Authorised Xiaomi Service Center Account 25€ and it did work.
So... it seems to be locked by Xiaomi. Apparently to stop people from importing phones from China and flashing Global ROM on them.
Click to expand...
Click to collapse
xiaomi fked up the system now blackmarket abuse this kind of restrictions
fireclouu said:
i want to do edl mode flashing but some encryption needed, even at qfil cant flash the thing, needs to modify prog files and crack it
Click to expand...
Click to collapse
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Rstment ^m^ said:
What are we even talking about anymore?
You'll pay 20$ for edl that likely won't do anything, you're just delaying inevitable. If pmic is not reset via bootloader ( fastboot reboot bootloader ) that's where you start thinking it's hardware issue.
What do u even wanna flash? Open stock ROM folder and enter folder called images on pc - look what's inside, persist, cust, boot everything is in there and was flashed already...
Just take your phone to service center while you still can , if under warranty keep requesting new motherboard . They'll likely try battery replacement first.
If it's not under warranty then ok play around as much you feel the need to , it just makes no sense to beating your head with all of this when warranty covers it
Click to expand...
Click to collapse
its true , im just trying to figure this out myself if possible or not, accessing service center here is much more troublesome rather fixing it in such way i think possible
but yeah ill update soon enough, tomorrow will be my only day off for a week, will definitely take a visit, wish me luck!
update: i sent my phone to mi authorized drop points yesterday. expected to get it repaired within 2 weeks and to pick it up next month.
update: today Ill pickup my device, will ask what could be the cause of the issue
fireclouu said:
update: today Ill pickup my device, will ask what could be the cause of the issue
Click to expand...
Click to collapse
Good luck! Let us know
so I got the device, support told me about the issue: battery only replugged, no other service, no replacements needed, seems some wirings got loose.
Ive read similar incident here, s/he only did replug the cable, got it fixed. Same issue on my end

Categories

Resources