I downloaded the new leaked pie version of android for the Galaxy s9+ and after realizing it was buggy, lacking some features i needed, i tried going back to oreo and messed up somewhere. I used odin do get oreo and that worked, then while starting back up, it said i had to factory reset it and after turning the phone back off, i keep getting stuck on the ss rdx screen where it asks to back up to sd card or computer and cant get off that no matter what i do. Ive tried backing up to sd card and nothing happens. Any help would be appreciated.
I had this same problem..... I'm on an s9+ on Xfinity service. I could boot the phone back up by pressing and holding a combo of power and volume down I believe but the phone would boot up and be locked up on the sign-on screen (it wouldn't pull up the keypad to let me enter the pin code). I also couldn't shut down the phone or boot it into download mode or into recovery. I ended up hooking it up to my computer via usb and sending an adb command to fastboot into download mode. Luckily that worked and I could then use Odin and reflash stock firmware. I already had developer mode and usb debugging mode enabled prior to the phone locking up on me.
---------- Post added at 01:21 PM ---------- Previous post was at 01:01 PM ----------
I also found this by digging through Google:
https://forum.xda-developers.com/galaxy-s8+/help/samsung-s8-sm-g955uzkatmb-boot-error-t3726832
Hope this helps.
Libdawg said:
I had this same problem..... I'm on an s9+ on Xfinity service. I could boot the phone back up by pressing and holding a combo of power and volume down I believe but the phone would boot up and be locked up on the sign-on screen (it wouldn't pull up the keypad to let me enter the pin code). I also couldn't shut down the phone or boot it into download mode or into recovery. I ended up hooking it up to my computer via usb and sending an adb command to fastboot into download mode. Luckily that worked and I could then use Odin and reflash stock firmware. I already had developer mode and usb debugging mode enabled prior to the phone locking up on me.
---------- Post added at 01:21 PM ---------- Previous post was at 01:01 PM ----------
I also found this by digging through Google:
https://forum.xda-developers.com/galaxy-s8+/help/samsung-s8-sm-g955uzkatmb-boot-error-t3726832
Hope this helps.
Click to expand...
Click to collapse
Samsung phones do not have "fastboot" mode. What you did is issue the adb command
adb reboot bootloader OR download OR recovery OR edl
If adb wasn't already pre-enabled then this would not have worked, however flashing a combination or eng boot would have enabled adb mode.
billa said:
Samsung phones do not have "fastboot" mode. What you did is issue the adb command
adb reboot bootloader OR download OR recovery OR edl
If adb wasn't already pre-enabled then this would not have worked, however flashing a combination or eng boot would have enabled adb mode.
Click to expand...
Click to collapse
Dude... Way to ressurect an old thread..
InsanePostman said:
Dude... Way to ressurect an old thread..
Click to expand...
Click to collapse
I replied to a message dated 10-04-2018 it's not from 1999 lol
thank you
billa said:
I replied to a message dated 10-04-2018 it's not from 1999 lol
Click to expand...
Click to collapse
and your reply is still relevant... even another year later. I'm in the same boat and was confused about the fastboot reference, but appreciate the info from everyone.
*side note*
"Way to ___" posts and comments rarely add any value and usually have the opposite effect intended... instead calling someone else out or pointing out a misconduct you end up looking like a condescending prick. And now I've got dirty hands as well and seem like a know it all for calling out this know it all. The high road is always a better path.
God bless relevant ressurectable threads. Unlike Pet Cemeteries... sometimes dead is NOT better : )
HT
HTidwell said:
and your reply is still relevant... even another year later. I'm in the same boat and was confused about the fastboot reference, but appreciate the info from everyone.
*side note*
"Way to ___" posts and comments rarely add any value and usually have the opposite effect intended... instead calling someone else out or pointing out a misconduct you end up looking like a condescending prick. And now I've got dirty hands as well and seem like a know it all for calling out this know it all. The high road is always a better path.
God bless relevant ressurectable threads. Unlike Pet Cemeteries... sometimes dead is NOT better : )
HT
Click to expand...
Click to collapse
I see, so anyone posting a relevant reply to a thread regardless if it's new or old, is now called a "know it all" by your name calling.
Interestingly I couldn't find in the xda rules anything that prohibits anyone from posting a reply if it's one year or older.
I'll just leave it at that, and let the moderators decide.
Related
I know there is threads about this, but I am having troubles, I will be willing to donate $20 to anyone who can help me. I am hoping it will be relatively easy............. I shouldn't have said that.
I loaded a bad framework-res.apk on my phone, and now it won't boot.
I have read DG's thread on recovering from the brick, but I can't figure out how to make it work.
In order to get the framework loaded I used root explorer to copy it over, because I couldn't get ADB to push the file. (I know, if I couldn't get ADB to work why would I muck with it....)
Now the first step in his guide is to boot into fastboot and wait for adb to work, then use superoneclick and hit 'shell root'
well, I can load into fastboot, but adb consistently says "error: device not found" or it doesn't list anything when I check devices. The troubles I was having before with adb were with pushing files, I could still see the device and pull files.
When I did the superoneclick step it ended up freezing the program, and I am not sure what is supposed to happen with fastboot but all it said was starting fastboot protocol support then did nothing.
I would be very grateful to anyone who can help me with this problem, I do have a backup framework on my computer and on the external sd card in the phone.
One thing I should note is that I did originally boot into the recovery mode, but all i did from there was reboot the phone (and go into fastboot mode).
Please help me! I have learned my lesson.
does the phone turn on
Do you have USB debugging enabled?
If you do, its possible to use adb by selecting Early USB Enumeration from boot menu. If not, you'll need to reflash using an SBF.
Come to my gtalk id texasdude11 and I'll help you out on chat.
Sent from my MB860 using Tapatalk
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Click to expand...
Click to collapse
I think debugging was on, but I was also in USB data mode (the one above none). And yes, I am the poor Bell SOL'er.
toughbax said:
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
Click to expand...
Click to collapse
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
lsxrx7 said:
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
blaque72 said:
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
Click to expand...
Click to collapse
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
raybond25 said:
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
Click to expand...
Click to collapse
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
blaque72 said:
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
Click to expand...
Click to collapse
yeah, i don't think he explicitly said that, but i just PM'ed him because i guessed that that was the case and it was, i'm on Bell and ima see what i can do
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
toughbax said:
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
Click to expand...
Click to collapse
What was the solution?
shawnbuck said:
What was the solution?
Click to expand...
Click to collapse
NO IDEA.
Kenneth made me a script that did it all for me all I did was hit the space bar a few times.
Basically the problem seemed to be on this side of the keyboard.....
Moved to Q&A
Please post this script so that we may use this in the future
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
erik10002 said:
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
Click to expand...
Click to collapse
The problem is that the script that ken wrote for the OP only restores the framework-res.apk file, and nothing else. If you really need this to recover from soft brick in the first place I'm not sure if you have the ability to edit it the way that is required.
Sent from my MB860 using XDA App
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
Click to expand...
Click to collapse
Freaking beautiful. Early USB enumeration was just what I needed to fix my f*ck up.
So I've finally decided to unlock and have managed to install clockworkmod to my Prime.
I am now trying to install nvflash because I hear it's supposed to prevent me from bricking my tablet. Booting into fastboot is not a problem for me, but the problem appears when I'm using the cmd prompt and trying to reach the device.
I've used all the correct commands as shown on the nvflash guide, but the tablet doesn't seem to acknowledge them. Using a command like fastboot reboot shows successful on my computer, but does not actually physically reboot the tablet.
Any help on this matter would be very appreciated. Seems like I keep going in circles and nothing will work
Post deleted by user.
Post deleted by user.
kenny98023 said:
This is exactly my problem as well. If I attempt to flash ebtblob.bin, fastboot says it works, but doesn't. If I reboot from fastboot before attempting the flash it will reboot the prime.
Sent from my Galaxy Nexus using xda premium
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
BTW... I've just unlocked since JB and have not rooted yet.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm guessing you discovered that if you are on JB you can't enable nvFlash anymore.
---------- Post added at 10:37 AM ---------- Previous post was at 10:34 AM ----------
Leinhart_6 said:
So I've finally decided to unlock and have managed to install clockworkmod to my Prime.
I am now trying to install nvflash because I hear it's supposed to prevent me from bricking my tablet. Booting into fastboot is not a problem for me, but the problem appears when I'm using the cmd prompt and trying to reach the device.
I've used all the correct commands as shown on the nvflash guide, but the tablet doesn't seem to acknowledge them. Using a command like fastboot reboot shows successful on my computer, but does not actually physically reboot the tablet.
Any help on this matter would be very appreciated. Seems like I keep going in circles and nothing will work
Click to expand...
Click to collapse
Did you try going through the entire recommended steps of uninstalling the Asus drivers and then installing the naked drivers? You can find them in the development area. Also some folks have had issues with cwm on the Prime so the generally accepted recovery to use is TWRP which you should have seen if you read thoroughly the threads in the development area. Are you certain the files weren't generated? Please, Please read up more before you do anything more or you could easily end up with a plastic, glass and metal paperweight.
Post deleted by user.
fastboot wont recognize tablet
fastboot wont recocnize my tablet, which is in fastboot mode. i have tried the standard asus drivers, the whole pc suite, the naked drivers, still doesnt work. adb recognizes it just fine when i boot android, but as soon as i get to "Fastboot USB protocol" its off the hook...weird think also is, that in device manager it is listed under "SAMSUNG android phone>ASUS fastboot interface"
i also tried to uninstall all my samsung drivers (i9100), still it wont be recognized...
anyone any ideas??
kenny98023 said:
Thanks for putting more salt in the wound. Going to not proceed any further until I can get a blob of my device made. Too much $ to F with.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not my intention to rub salt. sorry you are having issues but there is a lot of good information to be had if you read read read and you are right that it is too Mich money to fool around with.
Hey guys i have been using my dell tablet for more than a year. I also rooted it at the same time i bought the tab. Now a week ago when i was using my tab it was completly turned off. I have tried charging it for a day nothing happens. it dosent Show any Boot animation or charging animation nor does it even enter fastboot mode. It doesn't even turn on. It has just become like a paper weight. When i connect it to pc, it shows under the Device Manager CLOVERVIEW PLUS Device. I checked out some other posts and it shows reflashing it through xFTSK, but i searched everywhere but it doesn't have any firmware or software for Dell Venue 7 HSPA+ 3730. Pls Guys Help me out here, really appreciated. Thanks.
can you boot into the fastboot mode?
Huzaifa_Aziz said:
can you boot into the fastboot mode?
Click to expand...
Click to collapse
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
ssjdeepanshu said:
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
Click to expand...
Click to collapse
I'm really sorry for replying late, was stuck in an issue of my own with S6 Edge, okay so, when you put it on charge does it show up "charging" ?? like the Cell with charging animation shows up?
---------- Post added at 04:10 AM ---------- Previous post was at 03:56 AM ----------
ssjdeepanshu said:
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
Click to expand...
Click to collapse
if it is showing up a response in Device Manager then it means your boot is still alive. There is hope brother, so first of all we need to know if it has juice or not?
also please READ some stuff here http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
and download and extract this package http://https://www.androidfilehost.com/?fid=23622183712464837 from @social-design-concepts and please don't flash stuff just right away. I would suggest that you read first what they have to say, then cautiously proceed with the Toolkit.
do also thank @social-design-concepts on his thread by the way.. :good:
---------- Post added at 04:25 AM ---------- Previous post was at 04:10 AM ----------
ssjdeepanshu said:
No, I cannot. it doesn't give any response, only when conected to pc it shows CloverView Plus in Device Manager.
Click to expand...
Click to collapse
and then there is the good old METHOD number 2,
it's easier as far as I know,
make an easy ADB folder.
Just boot in FASTBOOT mode.
extract the ::Venue_7_3G_KK4.4.2v1.33_FLASHPKG.7z:: archive
and take out Venue_7_3G_KK4.4.2v1.33.system.img.gz (place it in same folder as adb.
after that in fastboot mode
write command
fastboot flash system Venue_7_3G_KK4.4.2v1.33.system.img.gz
Click to expand...
Click to collapse
wait for it to finish.
after that fastboot reboot
and profit!
Sorry for replying late, but as i said earlier it doesn't show any charging animation or enters the fastboot mode but when connected to pc it shows CloverView Plus in the device manager. i am just confused is it even alive or not.....
ssjdeepanshu said:
Sorry for replying late, but as i said earlier it doesn't show any charging animation or enters the fastboot mode but when connected to pc it shows CloverView Plus in the device manager. i am just confused is it even alive or not.....
Click to expand...
Click to collapse
It might be possible that the charging IC has been damaged, if after a continuous 2/3 hour connection with PC/charger the tablet does not turn on. Means it isn't getting enough charge to even boot up. It might be a good idea to get it checked by a technician but I am afraid parts/ replacements and finding an expert on Dell devices is quiet rare because of it's less popularity.
yeah even i am thinking it is a hardware problem, if i was a software problem, i might have been able to solve it on my own.
Anyway's thanks for help.
ssjdeepanshu said:
yeah even i am thinking it is a hardware problem, if i was a software problem, i might have been able to solve it on my own.
Anyway's thanks for help.
Click to expand...
Click to collapse
You are welcome!
I wonder what became of your tablet...
Huzaifa_Aziz said:
You are welcome!
I wonder what became of your tablet...
Click to expand...
Click to collapse
It's now just a useless paper weight :crying:
ssjdeepanshu said:
It's now just a useless paper weight :crying:
Click to expand...
Click to collapse
you know I found that tablet to be indestructible. up till now at least. still running even though I corrupted its recovery once.
So my Moto X (2014) which is around 20 months old just up and started giving this problem. When I try to boot it, it just goes to the fastboot screen and gives the error: "Fastboot reason: Failed to validate system image". The usual fastboot options like Normal Power up, factory, recovery, etc show up, but no matter what I select it gives the error: "Failed to validate system image. Boot up failed". I tried to attach some images, but being a new user was unable to link them.
Now the thing is, I am a complete noob at this stuff. So all I did was try to use adb sideload to try and re-flash the official ROM. But the adb command window doesn't seem to detect my device. Also, I'd just like to add, when I connect my phone to the PC, the standard windows sound of a USB being connected is heard, I don't know if that means anything, but I just thought I'd put it out there.
So obviously, the next thing I did was approach the service center. After a days inspection, they said, and I quote "There is an issue with the motherboard and/or PCB". I don't know what a PCB is. To fix the issue it's gonna cost me INR 12500, which is almost as much as a new phone. When I asked if they had tried re-flashing the ROM, they didn't seem to understand what I was saying, which made me a little skeptical. So, I came home and tried with the adb again, without any luck of course. Only this time when I connect my USB, I get a new error: "Fastboot reason: UTAG 'bootmode' configured as fastboot. USB connected".
Is there any way to fix this?
Or do I use it as a door stopper?
Thank you for any help in advance.
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
es0tericcha0s said:
You should find some helpful info over this way: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515. You must make sure to find the correct firmware for your model and the storage that it has.
Click to expand...
Click to collapse
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
souamguha said:
Hi, first of all, thanks for the reply, really appreciate that.
Okay, so I went through the post you referred me to, and I have a few questions regarding that, if you don't mind.
1) The phone in that post is the Moto X (2013), I have the 2014 model (the 2nd Gen). Does it make any difference? or is it the same procedure?
2) It says "Return to stock". I never left the stock ROM. Never rooted the phone, didn't even unlock the bootloader. I'm not even sure if my USB debugging was enabled.
4) Most of the download links on the post seem to be dead.
How should I proceed?
Again, thanks for any help in advance.
Click to expand...
Click to collapse
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
es0tericcha0s said:
I'm terribly sorry about the mix-up with the generation. I was half asleep looking through the forum.
This is the one you need: http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
I realize that you have not modified the phone, but this is how you reload the software+firmware back to the phone, or what you referred to as "flashing the stock rom" to the shop you took your phone to. If this fails, there's not much else that you would personally be able to do to fix the device.
USB Debugging on does not matter as you can boot directly to the bootloader by powering off, then press the power and volume down buttons simultaneously.
Good luck!
Click to expand...
Click to collapse
Okay, so I followed the thread exactly. But I can't get past the first step. When I type in "adb devices" on the adb command window, nothing shows up on the device list. (Note: My phone is already in the AP fastboot mode. I don't know if adb is supposed to detect it when it's in that mode).
But, Motorola device manager is able to detect my phone. When I run Motorola device manager with my phone connected, it searches for "repair software" for a while and then gives a pop-up saying "Your software is up to date" (and the name of the ROM installed).
Any further advice?
Thanks.
Use the fastboot method since you're in the bootloader. The adb is only mentioned there as an alternative way to get to the bootloader. Since you are there, skip that step.
Sorry for the late reply. But turns out the Boot IC of my motherboard was faulty. Whatever I did, it would always get stuck on the fast boot screen. Replaced my motherboard and now it's all good .
Thanks for all the help guys.
Hello. I have flashed my Lenovo Vibe K5, former build A6020a40_S004 to A6020a40_105, hoping for that VoLTE update. Following the proper steps and downloading the Stock ROM Firmware from trusted supplier, my phone won't boot into anything: recovery, or normal. Though the LED lights up when connected to a computer. However, it doesn't appear on my computer or hear that USB chime. I'm using a Windows 10 (which I've seen many have issues with Windows 10 and drivers) running on Bootcamp 6. I appreciate it if you guys could help me. Thank you very much.
By the way, I have no custom recovery installed. Just the basic Android System Recovery <3e> and I'm not that familiar with Android systems.
justinfinity09 said:
Hello. I have flashed my Lenovo Vibe K5, former build A6020a40_S004 to A6020a40_105, hoping for that VoLTE update. Following the proper steps and downloading the Stock ROM Firmware from trusted supplier, my phone won't boot into anything: recovery, or normal. Though the LED lights up when connected to a computer. However, it doesn't appear on my computer or hear that USB chime. I'm using a Windows 10 (which I've seen many have issues with Windows 10 and drivers) running on Bootcamp 6. I appreciate it if you guys could help me. Thank you very much.
By the way, I have no custom recovery installed. Just the basic Android System Recovery <3e> and I'm not that familiar with Android systems.[/Q
Click to expand...
Click to collapse
Well sorry to hear about that but I know very well how to recover from such situation. You'll need to flash the recovery IMG again so that it boots into recovery mode
Brawler leon said:
Well sorry to hear about that but I know very well how to recover from such situation. You'll need to flash the recovery IMG again so that it boots into recovery mode
Click to expand...
Click to collapse
Thanks! Can you tell me how? I've been researching about this as well for a long time now. Any help is appreciated.
Yes my bud. I will provide you the link shortly to some SDK tools so that you can flash your recovery IMG again and et access to recovery mode. I know that situation is chaotic and sucks but I am assuming that you aren't able to access twrp or anything.when you turn the phone on it gets stuck at lenovo and after few minutes it gets restarted on its own. And on connection g it to computer, it just doesn't get connected and nothing appears to be connected. I want you to take the battery out and place it again after few minutes and press the "vol down" button and "power button at the same time. You'll see the same lenovo icon but there will be something written in Chinese or something like that. Now connect your phone to your computer and I advise you to use a very good quality data sharing cable or original lenovo cable. Now your computer will recognise your phone as a hard drive or a storage device.i I'll try to upload a video on that too. Till then try these steps and lemme know if they work and your computer recognises your dead phone.if it does then there is still a hope left. BTW I was stuck in the same situation twice but thank god I saved myself and I am using my device. Note:- this method doesn't uses any software like " QFIL" or "QCOM" loader to flash stock firmware. Hope it works
---------- Post added at 05:30 PM ---------- Previous post was at 05:22 PM ----------
Just keep replying if it works and within a week you'll get your phone fully functional.
Here I have uploaded the platform tools needs d to flash recovery
Brawler leon said:
Here I have uploaded the platform tools needs d to flash recovery
Click to expand...
Click to collapse
Thanks a lot, man. Where the hell have you been all my life? Lol.
So my phone doesn't boot. It doesn't even show the Lenovo logo on it. Just mere darkness. :'(
I am going to Hong Kong later this week (this is where I bought the phone) and I don't know, maybe have someone fix it.
PS. Can you please DM me the links or if it isn't a loss for you you may just reply it here.
Thanks in advance and more power. The world needs more people like you.
Sincerely,
Justin
Sorry for responding late bud.but I am not able to post the link on this thread. If you have any e mail address then tell me so that I can mail you the links. And as you said your phone doesn't boot I want to ask you whether your phone charges when you connect it to the power and charging bar is shown or not. If yes then pls remove your phone battery and put it back and press the power button and the vol. down button hardly .if you see lenovo logo and something written in Chinese or something like that then you're on the way to get your phone back.just reply me the results soon bud
Brawler leon said:
Sorry for responding late bud.but I am not able to post the link on this thread. If you have any e mail address then tell me so that I can mail you the links. And as you said your phone doesn't boot I want to ask you whether your phone charges when you connect it to the power and charging bar is shown or not. If yes then pls remove your phone battery and put it back and press the power button and the vol. down button hardly .if you see lenovo logo and something written in Chinese or something like that then you're on the way to get your phone back.just reply me the results soon bud
Click to expand...
Click to collapse
Hey man. Justin here, again.
You may reach me through "[email protected]".
It doesn't show anything. Though, the LED light illuminates when connected to a power source or laptop. I'm starting to think it's absolutely hopeless. But please do message me anyway.
Fondly,
Justin
I think you have hard bricked your phone but still let's try
Brawler leon said:
I think you have hard bricked your phone but still let's try
Click to expand...
Click to collapse
Sure. I will wait for you in my e-mail. Thanks!
Brawler leon said:
Yes my bud. I will provide you the link shortly to some SDK tools so that you can flash your recovery IMG again and et access to recovery mode. I know that situation is chaotic and sucks but I am assuming that you aren't able to access twrp or anything.when you turn the phone on it gets stuck at lenovo and after few minutes it gets restarted on its own. And on connection g it to computer, it just doesn't get connected and nothing appears to be connected. I want you to take the battery out and place it again after few minutes and press the "vol down" button and "power button at the same time. You'll see the same lenovo icon but there will be something written in Chinese or something like that. Now connect your phone to your computer and I advise you to use a very good quality data sharing cable or original lenovo cable. Now your computer will recognise your phone as a hard drive or a storage device.i I'll try to upload a video on that too. Till then try these steps and lemme know if they work and your computer recognises your dead phone.if it does then there is still a hope left. BTW I was stuck in the same situation twice but thank god I saved myself and I am using my device. Note:- this method doesn't uses any software like " QFIL" or "QCOM" loader to flash stock firmware. Hope it works
Tried removing battery, its still in bootloop.
Click to expand...
Click to collapse