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:
Related
http://forum.xda-developers.com/showthread.php?t=2217296
i just buy a phone samsung note II few days ago and tried to unlock it but i make a miss galaxy note II ---------------SGH-I317M
1st i didnt made the backup
2nd maybe i install the wrong flash or firmware
so the phone is stuck on a black screen and just samsung logo
it can boot on downloud mode and the clock mode
i use the kies but still have the same problem .system cant mount <invalid argument >
efs cant mount system
cant mount data
cant mount sdcard
even .. i install the stuck rom from rogers
i found the kernel and used the Odin
no thing happens
and were lookig to ---------------PIT------File
to repartion might help
please guys and help
Hi. Ok so once your bootlooped yer pretty much borked.
So you can get into download mode?
I want to be sure you know how and what this is. Sorry if you take this the wrong way but your english is a bit scattered.
Ok dl mode: hold the home, power and volume down all at the same time.
There is no other way to achieve this other than a jig or possibly adb, that idk.
If you can get into dl mode your golden.
If kies isnt helping youre doing it wrong.
Odin is an option but lets try this first.
Please, dont get mad if you feel you tried this before.
First, re download thevusb drivers from samsung. "I already did that!"... trust me,
Do it again unless you are 1000000% sure they are current. Even then, uninstall and dl again to be safe.
Next get the current kies software.
Seems like you got this, but again make sure its the latest version.
So lets double check something.
Try again for ****s and giggles to get into recovery. Press the power, home and volume UP buttons all at the same time.
I know you know this has to be done when the phone is powered off.
We just want to see if your recovery is corrupted or not.
If you can get into recovery just do a factory reset.
This may or may not work.
Its ok.
Ok if it fails back to dl mode.
When you get to dl mode start kies.
Kies aint gonna do nothing but lag and hang if your phone and or recovery is fragged.
Youll need to go to the drop down menu in kies and choose:
"emergency firmware recovery"
its gonna ask you for phone model and such. Its then going to say
Plug your phone in or we it says
Put your phone in dl mode:
After you did the pwr, vol dwn, and home key, it brings you to a screen that says
Push up to cancel down to enter dl mode.
Again dont take offense if you know this.
Connectvyour phone to the pc and push the down button.
Give it time. This process can take upbto 20 min.
Once its done you shoyld now have a completly stock phone.
I highly recomend you remove your sd card for this.
Post back with results.
You can also try Odin.
Youll still need the latest samsung drivers.
Youll need the latest stock rom to flash.
Im sure others will chime in .
Good luck and post back
freakboy13 said:
Hi. Ok so once your bootlooped yer pretty much borked.
So you can get into download mode?
I want to be sure you know how and what this is. Sorry if you take this the wrong way but your english is a bit scattered.
Ok dl mode: hold the home, power and volume down all at the same time.
There is no other way to achieve this other than a jig or possibly adb, that idk.
If you can get into dl mode your golden.
If kies isnt helping youre doing it wrong.
Odin is an option but lets try this first.
Please, dont get mad if you feel you tried this before.
First, re download thevusb drivers from samsung. "I already did that!"... trust me,
Do it again unless you are 1000000% sure they are current. Even then, uninstall and dl again to be safe.
Next get the current kies software.
Seems like you got this, but again make sure its the latest version.
So lets double check something.
Try again for ****s and giggles to get into recovery. Press the power, home and volume UP buttons all at the same time.
I know you know this has to be done when the phone is powered off.
We just want to see if your recovery is corrupted or not.
If you can get into recovery just do a factory reset.
This may or may not work.
Its ok.
Ok if it fails back to dl mode.
When you get to dl mode start kies.
Kies aint gonna do nothing but lag and hang if your phone and or recovery is fragged.
Youll need to go to the drop down menu in kies and choose:
"emergency firmware recovery"
its gonna ask you for phone model and such. Its then going to say
Plug your phone in or we it says
Put your phone in dl mode:
After you did the pwr, vol dwn, and home key, it brings you to a screen that says
Push up to cancel down to enter dl mode.
Again dont take offense if you know this.
Connectvyour phone to the pc and push the down button.
Give it time. This process can take upbto 20 min.
Once its done you shoyld now have a completly stock phone.
I highly recomend you remove your sd card for this.
Post back with results.
You can also try Odin.
Youll still need the latest samsung drivers.
Youll need the latest stock rom to flash.
Im sure others will chime in .
Good luck and post back
Click to expand...
Click to collapse
+1
You told him everything that he needed to do bro.:thumbup::thumbup:
And yes his/her English is broken.. Lol
But this also may help him out:
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/
Note: phone is soft bricked when it's still coming on. When it's completely dead, blank, Chaput, NADA, it's confirmed hard bricked!!! :banghead:
Just my 2¢®
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
Hope you fix that phone.what an expensive paper weight that'll be.
Sent from my SAMSUNG-SGH-I317 using xda premium
read ur mesage and thanks for giving me time
i buy the phone from a friend who win from radio station
the phone was locked with roger and i was trying ODIN to downloud wind i guess cause i think that i could do it
i dont knw what i did just the phone suddely start on samsung
i have Kies program and i just made firm upgarde and initialization
the ask 4 phone model and serial number
i removed batery restart in download mode and e software installed into the phone
but the phone even didnt started
it say :
E: failed to mount system <invaled argument>
E; cant mount/ sys invalid argument
E : int main /system invalid argument
E failed to mout data
E failed to mount system ..
when i start at ODIN MODE
Poduct name SGH-I317M_NA_BMC #
coust bianery dwnloud (125)
current bianery (samsung official)
system status (custom)
when i start the phone now give me black screen with battery shade ??
am i doing good or bad so far
please help me tep by step
Hey I replied back but you didnt answer.
But thats ok its better to keep this in the thread so thers can chime in and if we find a solution others who have this exact prob will find a fix.
As I wrote to you please confirm:
Your native language (maybe others who speak your tounge will better help)
I asked you what was the first thing you did with phone. (Root , any mods and exactly which rom.There are to many roms to be vague.)
I asked you what model you said rogers but above I noticed something about wind mobile?
First lesson: if you dont root your phone, you can NOT intsall a new rom, meaning you can ONLY do a factory reset, or install exact OEM (stock) rom viaodin or kies.
By the way . IM not gonna keep repeating "Kies Emergency Firmware Recovery" From now on when I say kies, im only talking about that function of kies.
So Example: A Rogers mobile, rooted or not, CANNOT have a wind, att, verizon tmobile or what ever installed. This is exactly why your phone is s-bricked. Like Bajanman said and as I told you if it powers on your good. Your just stuck.
This is called a bootloop; aka soft brick.
Also to complicate things more I am suspecting that you may have
Installed a custom kernel. Ooooops
Locked phones will def brick if you do that.
rage.jpg
As I said sometimes mobile phones are picky you may have to uninstall and reinstall : usb drivers, microsoft drivers, use different computer etc. Thats another thing; what computer and Operating System are you using?
PC right? What OS?
I dont have and despise face book but here are two other options.
If you live in the usa mail me your phone and ill take care of it.
Right now all other xda'rs are lulzing and gonna say dont do that.
:silly:
Understandably if you say no if you wanna dl yahoo or msn messenger we can do it that way.
The best thing to do dude is find a friend who speaks and understands english better than you and get them to translate
Or help.
If odin fails and kies EFR fails you are doing it wrong.
Even if your recoveryis corruptedit doesnt matter. If you can get
Into Download mode (its a two step process explained above)
Your phone can be fixed.
The other option is adb push and im sorry my fingers would fall off typing that out :lol:
You will have to do some leg work and research using adb to basically "force" the firmware into your partition. This is, c9rrefte if im wrong guys, basically what kies emergency recovery does but "automagically"
Why do I feel like mr miyagi : turn on! Turn off! Put in download mode..again! Now wax my hard drive! !
Do you have a camera? Pics or maybe a youtube vid would help.
Its 3am here im crashin.
I feel for ya bud.
:thumbup:
Edit: I just thought of something. Pull out your sd card and sim.
Dont put them back in until this is fixed.
This may even solve your problem.
From now on evey time you restart your phone pull out your battery and hold pkwer for a few seconds. No this is not a magic trick it just ensures most of the power is drained.
freakboy13 said:
You will have to do some leg work and research using adb to basically "force" the firmware into your partition. This is, c9rrefte if im wrong guys, basically what kies emergency recovery does but "automagically"
Why do I feel like mr miyagi : turn on! Turn off! Put in download mode..again! Now wax my hard drive! !
Do you have a camera? Pics or maybe a youtube vid would help.
Its 3am here im crashin.
I feel for ya bud.
:thumbup:
Edit: I just thought of something. Pull out your sd card and sim.
Dont put them back in until this is fixed.
This may even solve your problem.
From now on evey time you restart your phone pull out your battery and hold pkwer for a few seconds. No this is not a magic trick it just ensures most of the power is drained.
Click to expand...
Click to collapse
+1 again freakboy
Everything your telling him is correct.:thumbup::thumbup:He should be happy he's getting into download mode.
And not hard bricked. But if he's not careful it will b hard bricked.
LMAO at the Mr. Miyagi, wax on wax off..
Classic :thumbup:
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
I could also try helping you out with TeamViewer later today.
Et je parle français si ça peut aider.
Send me a PM.
Goodbye,
Darkshado
Sent from my SGH-T889V using xda app-developers app
Hello . This post was originally a tutorial for samsung kies EFR.
Since so many people seem to not understand this great tool and to save bandwith
for xda (mods hit my thanks button! :victory: ...oh cmon im jk )
I removed this post and made it into an actual tutorial.
heres my new tutorial for Samsung's KIES Emergency Firmware Recovery Tool:
http://forum.xda-developers.com/showthread.php?p=40966346#post40966346
freakboy13 said:
I would hold off on flashing new roms until you read some more.
I hope this works out for ya!
Edit: its is recomended to unistall kies before using the galaxy note 2 toolkit
Click to expand...
Click to collapse
Very detail write up bro. :thumbup::thumbup: Very nice trying to help out!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
Just a silly obsevation here, but you tell them to pull the battery and then go into recovery with the proper key press sequence. You forgot to tell them to put the battery back in the step by step sequence. Picturing op sitting there and not getting it to power up because battery is sitting next to phone. like I said, silly but I have encountered sillier. I am confident op would put it back in, but......
{
"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"
}
By the way, great tutorial. Hope op gets it running.
Sent from the Millennium Falcon somewhere on the Kessel Run
ok guys .. sorry i was not here yesterday ..
just come back and i will do what u told me
thx for the help ..lets see what will happens ....
Mad383Max said:
Just a silly obsevation here, but you tell them to pull the battery and then go into recovery with the proper key press sequence. You forgot to tell them to put the battery back in the step by step sequence. ...... I am confident op would put it back in, but......View attachment 1884163
By the way, great tutorial. Hope op gets it running.
Sent from the Millennium Falcon somewhere on the Kessel Run
Click to expand...
Click to collapse
Dude thats hilarious.
Yes. OP, if you take the battery out....
Ya gotta put it back in for the phone to work!
:beer:
device not responding .
to solve the issue ,reboot the device ..
i did that 5 times and same issue bro
what i can do !!
What happens when you try to get into recovery? Describe the screen please.also describe exactly what happens when you the to the point if using the EFR.
You are doing the efr Right?
You are not doing the upgrade...correct?
You need to describe in more detail whats happening when its failing.
Just saying "its not working" makes it tough.
I still think youre doing something wrong.
Because the next step is to push the firmware and .....thats a bit more complicated.
Make sure you are NOT doing an upgrade, because before I made my pic guide you mentioned "I tried the upgrade".
You dont want to upgrade.
Keep trying dawg.
Please help me help you by explaining and describing the screen.
And so on.
Picsc would be better!
Describe the screen when you are in dl mode please. Remember dl mode is 2 parts.
Maybe some one else can chime in.
Theres gotta be someone in your area on these forums or others, who can maybe meet up and helpnyou in person?
Hello. I was using my phone and suddenly in the afternoon it started to restart automatically.. its never ending and it only stops when I take out the battery... When I put the battery again SAMSUNG Logo comes up followed by Samsung Galaxy W (CyanogenMod 9) screen then it restarts again and back to SAMSUNG logo... this process is never ending...
I also plugged in the charger and all i see is battery meter trying to calibrate but phone restarts and again i get to see the un-calibrated battery meter... this process also never ending...
I'm using ''CyanogenMod 9 Final Release (EOL)'' for past 3 weeks and there wasn't any problem... all this happened all of a sudden... I don't know what to do... So experts kindly help me out... Thanks a lot!!
hiitsme123 said:
Hello. I was using my phone and suddenly in the afternoon it started to restart automatically.. its never ending and it only stops when I take out the battery... When I put the battery again SAMSUNG Logo comes up followed by Samsung Galaxy W (CyanogenMod 9) screen then it restarts again and back to SAMSUNG logo... this process is never ending...
I also plugged in the charger and all i see is battery meter trying to calibrate but phone restarts and again i get to see the un-calibrated battery meter... this process also never ending...
I'm using ''CyanogenMod 9 Final Release (EOL)'' for past 3 weeks and there wasn't any problem... all this happened all of a sudden... I don't know what to do... So experts kindly help me out... Thanks a lot!!
Click to expand...
Click to collapse
I'm not an expert, but i would like to help Try to enter cwm recovery, reflash the rom and gapps. Hope it works
reply
thank you so much for your quick response... the problem is i cannot enter into CWM... i just googled and found the problem to be a SOft Brick/ Boot Loop issue... I hope someone has a solution for it...
geniusboy93 said:
I'm not an expert, but i would like to help Try to enter cwm recovery, reflash the rom and gapps. Hope it works
Click to expand...
Click to collapse
U have to flash stock rom via odin and start everything again
Sent from my GT-I8150 using xda premium
1) a bootloop won't stop you from getting into cwm.
2) cwm will usually stop a bootloop.
Something else is going on here. The symptoms you describe *could* indicate a damaged power button.
With a normally working W, if you press and hold the power button for long enough, the phone will switch off. If you continue to hold the power button, the phone will come back on....and then switch off again.....in a continual loop.....
It *could* be that the power button has failed by *maybe* being pressed into the phone (it can happen)...this would replicate the above scenario....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
regarding odin
yeah im trying to flash everything again through odin... but the problem is when i go into the download mode the phone restarts... i dont know how to flash the file if it keeps on restarting like this... can u help me on that?
gameboy20131 said:
U have to flash stock rom via odin and start everything again
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
regarding power button
i dont think so it is because of the power button...
you see the exact problem which i face on this video... http://www.youtube.com/watch?v=iWg0LifdXlQ
the sad thing is even the uploader hasnt found a solution yet...
let me know if you know anything... as i dont want to buy a new phone
keithross39 said:
1) a bootloop won't stop you from getting into cwm.
2) cwm will usually stop a bootloop.
Something else is going on here. The symptoms you describe *could* indicate a damaged power button.
With a normally working W, if you press and hold the power button for long enough, the phone will switch off. If you continue to hold the power button, the phone will come back on....and then switch off again.....in a continual loop.....
It *could* be that the power button has failed by *maybe* being pressed into the phone (it can happen)...this would replicate the above scenario....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
i had this problem recently , i did a cmw sd phone partition and kinda bricked my phone , samsung logo restarts rapidly
so at the time u can do 2 things
flash the galaxy via odin , if that didn't work then there is no other ways to fix it
or go to samsung and play dum cuz i went to samsung and replaced the motherboard under warranty , like a fresh phone!
Cheers..
Ok.....so watched that video....in his case, it ain't software related.....if it was, the phone would restart at the same point every time. You notice that the phone would restart after the galaxy w logo screen but when he started hitting the phone it fully booted. That's defo hardware related. I'm not suggesting you mistreat your phone the way he did, but if you did, I bet you'd notice a certain lack of regularity as to where the boot process fails.
My money's still on hardware as the cause of your phones problem.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
regarding odin
can you tell me how you fixed it using odin? because when i put my phone into download mode, the phone restart keeps continuing... all the youtube tutorials and posts say that you got to start off with download mode and then proceed... i can go to download mode for just like 5 seconds and my mobile restarts again....
help me!!
redshift9 said:
i had this problem recently , i did a cmw sd phone partition and kinda bricked my phone , samsung logo restarts rapidly
so at the time u can do 2 things
flash the galaxy via odin , if that didn't work then there is no other ways to fix it
or go to samsung and play dum cuz i went to samsung and replaced the motherboard under warranty , like a fresh phone!
Cheers..
Click to expand...
Click to collapse
regarding rebooting
it is definitely restarting at the same time for me... i just pasted the link just get an idea of it... when i see SAMSUNG logo and SAMSUNG Samsung Galaxy W screen it restarts at that point... as shown in the video i tried doing that and the phone proceeded to load till i stopped hitting it... but once it restarted it went back to the same rebooting sequence...
keithross39 said:
Ok.....so watched that video....in his case, it ain't software related.....if it was, the phone would restart at the same point every time. You notice that the phone would restart after the galaxy w logo screen but when he started hitting the phone it fully booted. That's defo hardware related. I'm not suggesting you mistreat your phone the way he did, but if you did, I bet you'd notice a certain lack of regularity as to where the boot process fails.
My money's still on hardware as the cause of your phones problem.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
Ok...going back to OS basics to try to explain this.....
As I'm sure you know, an operating system will load up files in a specific and pre defined order. The ONLY thing that will stop this process is an interruption of the power or a corrupted file that the OS is trying to load. The phone in the video is NOT suffering from a bootloop due to a corrupted file......hitting the phone will not suddenly make that file ok and allow the phone to fully boot. If there was a corrupted file, the boot process would fail at EXACTLY the SAME point EVERY time.....regardless of what was done to the phone.
You say you've managed to reproduce the results in the video and get your phone to boot past the startup screen?.......that being the case, it's NOT software related....simply because the boot process doesn't fail at the same point and gets further in.
You say you can't access recovery or download mode because the phone restarts......this is another indication that the OS has nothing to do with it as during these tasks, the OS isn't even being used.
EVERYTHING I've seen and read here is telling me that it's a hardware issue....specifically the power button......wouldn't hurt to get it checked
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
regarding rebooting
thank you for your reply... now it makes sense...
and what do you mean by get it checked? my phone is rooted and its using Cyanogen Mod 9 custom rom and its more than a year old (Out of Warranty period) So if I contact Samsung service center will they help me out? I mean with all the rooted stuff?
keithross39 said:
Ok...going back to OS basics to try to explain this.....
As I'm sure you know, an operating system will load up files in a specific and pre defined order. The ONLY thing that will stop this process is an interruption of the power or a corrupted file that the OS is trying to load. The phone in the video is NOT suffering from a bootloop due to a corrupted file......hitting the phone will not suddenly make that file ok and allow the phone to fully boot. If there was a corrupted file, the boot process would fail at EXACTLY the SAME point EVERY time.....regardless of what was done to the phone.
You say you've managed to reproduce the results in the video and get your phone to boot past the startup screen?.......that being the case, it's NOT software related....simply because the boot process doesn't fail at the same point and gets further in.
You say you can't access recovery or download mode because the phone restarts......this is another indication that the OS has nothing to do with it as during these tasks, the OS isn't even being used.
EVERYTHING I've seen and read here is telling me that it's a hardware issue....specifically the power button......wouldn't hurt to get it checked
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
If the phone is out of warranty, it shouldn't matter that you've rooted and gone custom as they'll charge you anyway....just got to tell them that you want to stay custom or they're likely to return you to stock and unroot the phone (and charge you for that too).......
You could always try an unauthorized repair shop and see what they say.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
{
"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"
}
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Power Button
Thank you for that quick search... i dont know what to do... i badly wish the mobile is stable in download mode so that i can flash the rom into it
keithross39 said:
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
View attachment 2132195
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
regarding odin
Just one more thing...
1.Can you tell me how to approach this problem if it is totally related to software? I mean like there is a mobile phone which is stuck with boot-loop and I want the mobile to snap out of it?
2. Kind of a general question... if the phone restarts even in download mode how to use ODIN? Because then the process might fail... any other way to flash?
keithross39 said:
Just done a little research.....
It turns out that the power button is soldered directly to the mainboard.
See image below....
View attachment 2132195
So unless the repairer is good at soldering, then replacing the mainboard (and the custom OS) is a very real (expensive) possibility......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
To answer both of your questions together....if it is software related and odin can't be used because download mode can't be relied on.....jtagging is the only option.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
jtagging
is there any forum which gives info about the jtag? because i couldnt find much info about it...
P.S. I just want to make sure to try out all options before taking it to service center... thanks
keithross39 said:
To answer both of your questions together....if it is software related and odin can't be used because download mode can't be relied on.....jtagging is the only option.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
In my opinion, I don't think jtagging will help in this case. I'm 99.999% certain that it's hardware related. Even if you did jtag, I still reckon you will have a phone that continually restarts. All you'd be doing is replacing one functioning OS with another. Jtag is primarily used for a phone that will not boot at all......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Hey everyone,
I just bricked my T805. I was following this guide:
[OFFICIAL] LOLLIPOP 5.0.2 /SM-T800/ SM-T805/ Firmwares T800XXU1BOCC / DOWNLOAD / ROOT
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
Installing Lollipop Firmware
Instructions:
1. Download the needed firmware from above.
2. Download Odin_3.10.0 from the attached file below
3. Open Odin, select AP and than select your firmware.
4. Make sure you have installed all samsung drivers
5. Shut down your Tab S.
6. Open download mode by holding volume down, home button and power button.
7. Connect it to your PC.
8. LEAVE EVERY THING AS IT IS IN ODIN, OTHERWISE THERE WILL BE A CATASTROPHE (If you select something wrong.)
9. When your tablet is connected, there will be a blue box in odin.
10. Hit start and wait
11. It will reboot and you will get the latest firmware from samsung.
Click to expand...
Click to collapse
So I was in Download mode, klicked on Start in ODIN.
After one minute, this is what followed:
{
"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"
}
The Tab hangs in the Download mode screen...
USB connection does not work, PC is not recognizing the tab anymore.
Power off does not work, no chance to power down or reset the device (have to wail 'til battery is empty?)
Anyone knows what to do?
Thanks!
sheng1337 said:
Hey everyone,
I just bricked my T805. I was following this guide:
[OFFICIAL] LOLLIPOP 5.0.2 /SM-T800/ SM-T805/ Firmwares T800XXU1BOCC / DOWNLOAD / ROOT
http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
So I was in Download mode, klicked on Start in ODIN.
After one minute, this is what followed:
The Tab hangs in the Download mode screen...
USB connection does not work, PC is not recognizing the tab anymore.
Power off does not work, no chance to power down or reset the device (have to wail 'til battery is empty?)
Anyone knows what to do?
Thanks!
Click to expand...
Click to collapse
You didn't read the WHOLE THREAD. If you had you wouldn't have had to make this unnecessary post.
Your image isn't showing.
californiarailroader said:
Your image isn't showing.
Click to expand...
Click to collapse
Use a browser.
Got ya, it must be a bug with Tapatalk. It looks like you did everything right, I followed those same instructions to flash my SM-T700 and I had no issues. I'm sorry about the brick, I've done it once and it's upsetting for sure.
Edit- Did you make sure you had all the drivers installed correctly and the PC detected and installed everything?
californiarailroader said:
Got ya, it must be a bug with Tapatalk. It looks like you did everything right, I followed those same instructions to flash my SM-T700 and I had no issues. I'm sorry about the brick, I've done it once and it's upsetting for sure.
Edit- Did you make sure you had all the drivers installed correctly and the PC detected and installed everything?
Click to expand...
Click to collapse
Hidden.img part of that file fails unless have a vodafone locked tablet. This was VERY well explained. Flash the latest T805 UAE firmware and it will be fine, no loss of data. READ BEFORE YOU FLASH!
lynxblaine said:
Hidden.img part of that file fails unless have a vodafone locked tablet. This was VERY well explained. Flash the latest T805 UAE firmware and it will be fine, no loss of data. READ BEFORE YOU FLASH!
Click to expand...
Click to collapse
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Restart with the download mode 3 button combo then flash the UAE firmware.
sheng1337 said:
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Click to expand...
Click to collapse
You're almost there, you have nothing more to do than boot to stock recovery then wipe the cache.
The tablet will then successfully boot to lollipop.
POWER +VOL DOWN + HOME to restart then immediately change to VOL UP whilst still holding POWER + HOME.
sheng1337 said:
Dang, I missed that part. Ok so, that is the deal, but how do I reboot the device? It's stuck in Download Mode since yesterday evening. Any Idea on this?
Click to expand...
Click to collapse
For reboot you can also press and hold a few seconds only 2 buttons HOME and VOL-
lynxblaine said:
Restart with the download mode 3 button combo then flash the UAE firmware.
Click to expand...
Click to collapse
Ok I finally managed to get into download mode again. So i'm in Odin Mode. But please, can you explain why I should flash the UAE version?
ashyx said:
You're almost there, you have nothing more to do than boot to stock recovery then wipe the cache.
The tablet will then successfully boot to lollipop.
POWER +VOL DOWN + HOME to restart then immediately change to VOL UP whilst still holding POWER + HOME.
Click to expand...
Click to collapse
I can't boot to stock recovery. I only managed to get into download mode. Recovery is not working.
UAE as it flashes nicely it's got the highest change list and it's clean - no bloat. I flashed it earlier today.
lynxblaine said:
UAE as it flashes nicely it's got the highest change list and it's clean - no bloat. I flashed it earlier today.
Click to expand...
Click to collapse
UAE is the country code for United Arabian Kingdoms, but I have a german device. Well it's not going to be worse than it is, so i will give it a try. Thanks, I will report back.
Sent from my Nexus 5 using XDA Free mobile app
sheng1337 said:
I can't boot to stock recovery. I only managed to get into download mode. Recovery is not working.
Click to expand...
Click to collapse
All you have to do is flash one.
I live in the UK, the firmware region makes little difference apart from that it can determine the bloatware you get. You will get offered the next OTA from the region you are in: but you can always manually flash any newer ROM.
Thank you very much all. I got it working, POWER+VOLDOWN to resrart, instantly HOME+VOLDOWN+POWER to switch to Download Mode. Connecting to PC, flashed UAE version with ODIN. TAB runs good now! Apps and Data were not cleared/wiped.
Thanks again!
Sent from my Nexus 5 using XDA Free mobile app
Hi im having a hard time figuring this out, this is a brand new 5t that bricked itself while ota updating
the device is in a boot loop (wont go any further than the oneplus logo)
if i enter to the recovery it says LOCKED, and the oem unlock option on android is not enabled
im in argentina so i cant send the phone to oneplus rma
{
"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"
}
is there any way to unlock the bootloader? then i would be able to flash it and save the phone
Ps: a level 2 OnePlus tech guy tried a remote fix with the official brand software and it did not work
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
es0tericcha0s said:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
Click to expand...
Click to collapse
Thanks a lot! i think that oneplus did use that file and did not work but i will try it again (at least 10 times)
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
if i boot to recovery and press the power button to select factory reset or any usefull option, the phone resets, i think that the problem is a corrupt recovery, thats why i want to unlock it, install TWRP and then try to flash android
CZ Eddie said:
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
Click to expand...
Click to collapse
maybe this is an anti thief security measure? (since android 6.0 )
es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
why would i have a problem putting the 5t on qhusb? i did not know that it could be done via testpoint
the phone works, the problem seems to be a faulty file on the bootloader or maybe an internal damage from factory (i hope this is not the case)
in a few hours i will try it all and post the result
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
I did the entire process and the result is the same as before doing it, the phone turns on and gets stuck on the oneplus logo, it does nothing else, the recovery works but doesnt do anything usefull
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
es0tericcha0s said:
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
Click to expand...
Click to collapse
It may well be a partition error, one+ is not being helpfull right now
I did comit an error saying that the recovery works, it doesnt work, the pone only goes into fastboot and qhusb mode, after that it will allways get stuck on the oneplus logo
On adb i get feedback if i try to flash the phone says "not allowed, locked device"
I think that the problem is a corrupt bootloader
The msmdownloader tool works, i dont know what It copies on to the terminal but i want to flash the recovery and bootloader using that tool, i dont know if it is possible
this the md5sum file that i found in a compilation for oneplusone (msmdownloader tool)
so i shoud be able to do the same with the 5t
es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
that is no true, u just have the phone powered off and then hold the volume + and plug the device in, if u saw the video in the unbrick post he was not bricked at all and everything was working good and still did a restore, not sure why it is not working for the OP but it should fix it.
Yes i can enter into qhusb, and i can flash the phone with msm downloader, but i used the origibal file that oneplus technicians use amd it didnt work, now i want to flash hydrogen os or the recovery file only into the terminal but i dont know how to modify the msm downloader (the unbrick tool)
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
sascha224 said:
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
Click to expand...
Click to collapse
I remember that the device wouldnt flash anything because it was locked, but I will try the sideload right away
It has been impossible to fix, this is the best i got doing fastboot boot recovery.img
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 : )