Hi,
Problem: my desire s is not Booting up!! {not even in recovery mode} it is S-off and rooted
Symptoms: if i try to boot up it just vibrates for 2-3 times and the Red Charge indicator light, turns on. if i try to hold down the volume key & press the on key then it vibrates for 2-3 times & the Green indicator light turn on. That's it!! it is stuck there... doesn't boot up or anything.
What might have happened last night!!:
1. i downloaded some games apk from different websites and installed those.
2. tried to update ROM manager but failed
3. suddenly the volume increase indication came up in my screen (without even touching the volume keys!!) this kept coming...then i decided to give it a restart...after restarting everything came back to normal
4. but again it started to show up this morning...so decided to restart it again...and thats it....it wont boot up again!!!
Guys please DO help me out!!
Thanx in advance
Hello
Attempt to put charge into the phone by plugging it into the main charger.
Does the charge light come on when the phone is being charged?
Now download and Install the adb & fastboot onto your PC which you'll see in a link in my signature. Ensure that you have HTC drivers on you PC if not also download and install the link in my signature.
Plug phone into PC by USB cable.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb devices[/COLOR][/B]
?
whats the response?
thanx for the reply bro...
if i enter "adb devices" it shows:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
list of devices attached
C:\android-win-tools>
Now what shall i do???...please help me out...i m very novice in this matter <to be mentioned that... i had a given factory reset before this!!>
After startup and the two vibrates, what's on the screen?
were you forced to pull the battery at any point?
Sent from my HTC Desire S using xda premium
after the vibration the screen doesn't show anything!! its just pitch dark...
yeah last night i had to pull the battery out as the Red light wont turn off!!
this isnt sounding good!
check out the link in bens signature regarding emmc chips...
The most unexpected happen right now!!!!
i installed the adb tools then plugged in my device to the pc..suddenly it booted up...everything seemed to work perfectly {though the volume increase notification was still bugging me!!!}.
So, i decided to give it a Factory default reset. i went to the settings & clicked the factory default button....it gave me a couple of warnings and wiped all the installed apps. then it started to restart again...!!! AND Here you go ....its stuck again!!!! Back to that old black screen & the red light!!!!!
Please tell me WHAT to do????? plz i m waiting...should i plug it out???
<if i try to boot into recovery mode...it vibrates 4 times the green lights turns on!!>
shariaphobia said:
The most unexpected happen right now!!!!
i installed the adb tools then plugged in my device to the pc..suddenly it booted up...everything seemed to work perfectly {though the volume increase notification was still bugging me!!!}.
So, i decided to give it a Factory default reset. i went to the settings & clicked the factory default button....it gave me a couple of warnings and wiped all the installed apps. then it started to restart again...!!! AND Here you go ....its stuck again!!!! Back to that old black screen & the red light!!!!!
Please tell me WHAT to do????? plz i m waiting...should i plug it out???
<if i try to boot into recovery mode...it vibrates 4 times the green lights turns on!!>
Click to expand...
Click to collapse
Very strange indeed, can you recall any part of the warnings?
Unless the phone semi-boots or can at least be recognised by adb (which yours doesn't) then you can use the HTC ROM utility to re-flash your phone)
Does sounds frightening like a hardware related issue, although it's difficult to tell as it appears to intermittently boot!?
The good thing is if it won't boot then hopefully the service centre won't be able to tell that you S-off'd so may well replace unit or motherboard for you under warranty.
bro ...i m really getting hopeless here!!!!
1. Can u plz tell me the steps if the adb recognizes my set or give me some links so that i can follow....
2. Or tell me the steps to use RUU to flash my set
Anyways thanx a lot for yr time
---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------
bro...
i've tried the adb devices command again...now it shows this message:
List of devices attached
HT15JTJ05547 recovery
Does it mean anything???
shariaphobia said:
bro ...i m really getting hopeless here!!!!
1. Can u plz tell me the steps if the adb recognizes my set or give me some links so that i can follow....
2. Or tell me the steps to use RUU to flash my set
Anyways thanx a lot for yr time
---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------
bro...
i've tried the adb devices command again...now it shows this message:
List of devices attached
HT15JTJ05547 recovery
Does it mean anything???
Click to expand...
Click to collapse
Yes that's good news.....Although I'm at work now so bit busy...
Try
Code:
adb reboot recovery
from the PC if it loads into recovery Good!
From recovery try to format the CACHE partition, write what happens?
I'd then say download a wipe script and a safe custom ROM and then load them onto your SD card, ie like LBC Mod v0.6.0
If no errors, then first flash the wipe ZIP file and then the LBC ROM ZIP file using the "install from sdcard/zip file options from your recovery....
Report back any errors...if you're not quite sure of any of the steps then ask questions....I'll check back later...
Nope...if i enter the command adb reboot recovery...its just vibrates twice and nothing comes on the screen (with the red light on).........!!
i guess i have go for RUU process
---------- Post added at 05:52 PM ---------- Previous post was at 05:37 PM ----------
i just remembered one thing....couple of days ago i installed the FOTA updates...has that changed something in my S-OFF or Root????
shariaphobia said:
Nope...if i enter the command adb reboot recovery...its just vibrates twice and nothing comes on the screen (with the red light on).........!!
i guess i have go for RUU process
---------- Post added at 05:52 PM ---------- Previous post was at 05:37 PM ----------
i just remembered one thing....couple of days ago i installed the FOTA updates...has that changed something in my S-OFF or Root????
Click to expand...
Click to collapse
I'm getting out of my depth here....As we don't know what version of ROm you're now running especially if you ran the OTA. There is a possibility that the OTA has removed your custom recovery, S-OFF and root. As as you can't see the HBOOT screen you can't confirm that you're even still S-OFF..
You could try to start to run an RUU as this might tell you want you current ROM version is......
But I'd wait for someone else to provide some more advice...as I don't know what the "recovery" next to your device serial number from adb devices quite means ( I assume it means that your device is in recovery)...
---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------
google adb yourself and see what safe options and commands of it you can use that will provide you with further information about your phone
hi...
Thanx to ALLAH...may b at last i have found the problem area.
it is the volume rocker!!! somehow the "+" side of the volume rocker is jammed so, whenever i try to boot the device it goes in a recovery mode!!!
But strangely though when I played with the volume buttons and they don't feel jammed at all, the vol. down button is clicking fine, doesn't feel stuck or anything. And if that wasn't bad enough, I tried turning my phone off and on, but when turning it on, it still thinks it's held down so it will only boot into recovery!!!
is there any solutions for it???
shariaphobia said:
hi...
Thanx to ALLAH...may b at last i have found the problem area.
it is the volume rocker!!! somehow the "+" side of the volume rocker is jammed so, whenever i try to boot the device it goes in a recovery mode!!!
But strangely though when I played with the volume buttons and they don't feel jammed at all, the vol. down button is clicking fine, doesn't feel stuck or anything. And if that wasn't bad enough, I tried turning my phone off and on, but when turning it on, it still thinks it's held down so it will only boot into recovery!!!
is there any solutions for it???
Click to expand...
Click to collapse
Well done in discovering the fault
But, I'm afraid that I don't know of any way to disable the buttons, without obviously dis-mantling the case from the unit (which is way over my head) ...
this maybe a daft question but have you tried the command
Code:
adb reboot
(not adb reboot recovery)?
if this does not work you may have to take your device to HTC
Related
Guys, i flashed the GoApk ROM 2.3.5 with Sense 3.0 and everything was fine. Today, i flashed the new Unity v9 kernel after wiping Dalvik cache and rebooted, but now my phone has been stuck at the wite HTC screen for the past 1 hour. The three button reset is not working, neither is the adbreboot recovery command as adb does not detect my device. Please help... I do not want to pull the battery and fry my eMMC.
EDIT: Got into the recovery and restored nandroid backup. Back up and running now. Thanks everybody for their contribution.
enigmaamit said:
Guys, i flashed the GoApk ROM 2.3.5 with Sense 3.0 and everything was fine. Today, i flashed the new Unity v9 kernel after wiping Dalvik cache and rebooted, but now my phone has been stuck at the wite HTC screen for the past 1 hour. The three button reset is not working, neither is the adbreboot recovery command as adb does not detect my device. Please help... I do not want to pull the battery and fry my eMMC.
Click to expand...
Click to collapse
Look in my signature for various links...
Download and extract the adb & fastboot into a directory on your PC. Ensure that you have HTC drivers installed on you PC if not also download and install the link in my signature.
Then fire up a CMD on your PC, go to directory where adb is and issue the command
Code:
[B][COLOR="Blue"]adb reboot recovery[/COLOR][/B]
which should take you into recovery, where you'll be able to reflash or restore a nandroid backup from.
What's your hboot.
It's a most recent 2.00.2002
or the older ?
I think it got updated to the most recent one when i flashed the ROM. I tried everything you have suggested. Nothing works...
---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------
I'm just waiting for the battery to run out so it powers off and then i'll try to boot into recovery again. I thought Unity kernels were compatible with sense roms. Please can anybody help me out here?
No, the newest hboot must be flashed alone.
It's not included in the rom.
You can find it on this thread: GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5
it's a solution maybe
Maybe you have new .2 hboot and kernel is not compatible ?
philos64 said:
No, the newest hboot must be flashed alone.
It's not included in the rom.
You can find it on this thread: GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5
Click to expand...
Click to collapse
Will it help solving the problem ?
So then what should i do now? Will i ever be able to boot into recovery? I have ClockWorkMod recovery.
i dont think that install kernel kill your phone. if you can't access adb or anything you have no other chance as pull the battery.
if something like this me happen,
- i pull battery
- go to recovery
- go to 4EXT menu and wipe system,data and cache as EXT4
- then go to factory reset and install your rom
- restart
@ proxuser: But i do not have EXT4, i have CWM recovery. Can you guide me as to how to do what you sais in your last post please?
---------- Post added at 08:31 PM ---------- Previous post was at 08:27 PM ----------
Also, wont pulling the battery fry my eMMC? i'm scared of that...
enigmaamit said:
@ proxuser: But i do not have EXT4, i have CWM recovery. Can you guide me as to how to do what you sais in your last post please?
Click to expand...
Click to collapse
Have you attempted the suggestions in my earlier post #2?
After following what I suggested, although I'm not the only person to suggest that you attempt to use adb ....you seem to be missing the point or perhaps not understanding?
Follow step in post #2
Then fire up a PC CMD window, go to the directory where adb is extracted to and type the command
Code:
adb devices
tell us what the response is?
---------- Post added at 04:05 PM ---------- Previous post was at 04:02 PM ----------
enigmaamit said:
wont pulling the battery fry my eMMC? i'm scared of that...
Click to expand...
Click to collapse
It doesn't matter whether you have CWM or 4EXT they both are similar and perform the same functions.
If you have to pull the battery, READ the first post of this thread
ben_pyett said:
Have you attempted the suggestions in my earlier post #2?
After following what I suggested, although I'm not the only person to suggest that you attempt to use adb ....you seem to be missing the point or perhaps not understanding?
Follow step in post #2
Then fire up a PC CMD window, go to the directory where adb is extracted to and type the command
Code:
adb devices
tell us what the response is?
Click to expand...
Click to collapse
@ben - I tried what you said and your instructions very very clear. But when i type adb devices it just says "List of devices" Thats all... and Typing adb reboot recovery just gives an error with no device connected...
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
@ben : Yours was the first help post that i read and i have tried everything you suggested and i'm down to the last point where i may have to pull the battery. even if i reinsert it after a minute, there are chances of killing mu eMMC, right. That is where i'm stuck currently...
The same issue happened to me last week while trying to flash EXT4Recovery over CWM.. I have pulled the battery and reinserted after few seconds.. And then I was able to boot into the ROM..
http://forum.xda-developers.com/showthread.php?t=1264527
@Nirubhai, can you tell me exactly how you got past the white screen into recovery?
Hey bro, if you do pull the battery, do not instantly re insert it. Re insert about a minute later. Try ADB commands.
You don't need to worry, relax. You're in no trouble at all. A kernel flash is usually harmless.
Sent from my HTC Desire S using Tapatalk
How much was your phone charged?
Around 52%
That'll take a while to run out. Is adb detecting your phone? ADB is probably your best bet.
You'll get into recovery eventually, it's not a question of IF , but WHEN.
I am going to wait the entire night if it takes that... Adb is not detecting my device. Have run out of all options but to wait till it switches off, then connect to charger and try recovery. WHEN i get into recovery, should i do a nand restore or flash another kernel, ext4 or what? Any suggestions willl be a big help...
enigmaamit said:
@ben - I tried what you said and your instructions very very clear. But when i type adb devices it just says "List of devices" Thats all... and Typing adb reboot recovery just gives an error with no device connected...
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
@ben : Yours was the first help post that i read and i have tried everything you suggested and i'm down to the last point where i may have to pull the battery. even if i reinsert it after a minute, there are chances of killing mu eMMC, right. That is where i'm stuck currently...
Click to expand...
Click to collapse
Sorry to hear that, just needed feedback to know what to suggest next.
when you plug charger in does LED light ?
The way I see it you have two options
1)
If LED was lighting when you tried charging phone?
Then you could wait until the battery runs completely flat and the phone turns itself off. Then plug in charger and fully charge the phone before turning phone ON and trying to enter bootloader by pressing VOLUME DOWN + POWER button.
2)
Just go for it and pull it, pull it out quickly leave out for about 30seconds and replace it and try to enter bootloader by pressing VOLUME DOWN + POWER button.
Anyone agree?
Do you have a nandroid backup? If you do, restore that. No need for Ext4 or anything right now.
Yeah ben, thats probably what i would do. I've been stuck on this screen many times, and thats what i did. Pull the battery, and re insert a minute later.
I have multiple problems so read on.
A couple weeks ago the computer stopped recognizing my verizon gnex that was rooted, unlocked and running jbsourcery 5.1 that it previously had no problems seeing. It still charges via wall and usb with original m-usb cable. I've tried numerous times to re-install the samsung driver on the computer with wug's toolkit with no luck. I've tried another samsung m-usb cable...no luck. My computer is new so no problems with usb ports (I've tried all of them) and have tried the ver 2.0 port. USB debugging is on and fastcharge is off.
My second and worst problem:
Yesterday in a fit of stupidity I restored one of my original backups ( I believe made with CWM recovery ) that turned out to be a stock. img and after restoring it OTA updated to stock JB. All my other backups were done with TWRP and it's no longer present on the phone. I tried installing BootUnlocker from play store but it says I have no root access and the phone won't flash either recovery so I'm stuck with only Fastboot ver. 9 that only wants to flash something from adb. I've exhausted my knowledge and eyes are crossed from reading forums.
I want to get back to full rooted or back to full stock.
It is still unlocked
I don't know if I can use something like Terminal Emulator for this or even how to use it.
If you know enough to see that I'm totally screwed...Please tell me! (I'm a big boy)
If you think you have a solution...You are a god!
If you need more info...I can provide it
Whoa...really big problem
---------- Post added at 08:54 PM ---------- Previous post was at 08:47 PM ----------
Why can't you enter recovery mode?
And what's ur age...
Streetryders_2000 said:
Whoa...really big problem
---------- Post added at 08:54 PM ---------- Previous post was at 08:47 PM ----------
Why can't you enter recovery mode?
And what's ur age...
Click to expand...
Click to collapse
Rom manager is on the phone but each time i try to reboot into recovery it does nothing. If I try to enter recovery through VOL up/dwn-Pwr it just goes to minimal fastboot that only gives me the option of installing from adb.
50 yrs young
earbuster said:
Rom manager is on the phone but each time i try to reboot into recovery it does nothing. If I try to enter recovery through VOL up/dwn-Pwr it just goes to minimal fastboot that only gives me the option of installing from adb.
50 yrs young
Click to expand...
Click to collapse
It wont flash recovery while in Rom manager but it says CWM and Twrp are both installed on phone.
First thing, I was serious about ur age,
Second to go into recovery mode see here.
www.youtube.com/watch?v=1vXCyI-BpZw
Yes...but when I try to enter recovery all I get is the dead android icon with a red triangle on his chest. If i press vol/up and pwr button at this point it goes to the install from adb options in fastboot ver.9
And I'm being honest...I'm 50
First thing, see the second thing
Second thing go here,
www.youtube.com/watch?v=OMBwrdWqpnA
Pls press thnx if helped.
Sorry, I tried reloading the drivers into computer so I could use Wugs toolkit but they won't load because the computer doesn't recognize the phone. I keep getting an error 10 when trying to update the drivers. I truly appreciate your help and thank you but I'm stuck.
Any other ideas?
Ur welcome and sorry I couldn't help much...
I'll try help ASAP...
Sorry again..
You may have already tried it, but have you tried to plug the phone into a different computer ?
Yes, I have a win xp laptop I tried connecting to also. No luck
Lets make a long story short, i just got my OPO, as an advanced android user i desided to put
ParanoidAndroid 4.6, but before I installed custom bootloader (TWRP) and rooted it. Since i am installing new ROM i did a backup and then i needed to wipe my device, by accident i wiped everything from my phone, including backup and new ROM. I was left with TWRP (It is my 1st android phone without sdcard so i started to panick), then i started it in fastboot mode, to check if I can copy ROM again from my pc, but it didnt work. Then i went to restart options in TWRP and choose restart in recovery mode, then my phone turned off. Apperently it did restart but now my screen is just black and I cant do anything with it. I was holding power button, then with volume up, then with volume down, no result. When i connect it to my PC i hear sound that phone is connected but still nothing is happening. Please help me what should I do. My guess is when i pressed to restart in recovery mode, it wasn't meant to be the custom one, so it tried to open one that dosen't exist. My phone was charged 40% when i was doing that.
Note1: Unknown USB Device (Device Descriptor Request Failed), this is what i get when I check Device Manager.
Many suggestions were made so far none of them help. Hope someone will help me here!
First, TWRP isn't a custom bootloader, it's a custom recovery. The phone can't 'open a recovery that doesn't exist', it opens whatever recovery you have installed at the time. Make sure the phone is powered off (hold power for about 10-15 seconds), then try booting into recovery again (hold power + volume down).
Transmitted via Bacon
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
There is another problem
bigballa said:
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
Click to expand...
Click to collapse
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Only 1 thing
I just need to fix how to find device in adb and then it will be very easy.
Mod Edit: quoted post removed.
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]
Gapkobob said:
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Click to expand...
Click to collapse
Gapkobob said:
I just need to fix how to find device in adb and then it will be very easy.
Click to expand...
Click to collapse
My friend you're in a bit more trouble than I think you realise you're in. Your device is showing up as QHSUSB_BULK in Windows, which means it's technically bricked. I believed you can save it though, have a look in this thread, you're gonna need to read through it all to find the solution you need. Let me know how you go.
Transmitted via Bacon
Simple driver issue.
The following steps will solve your problem: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
Solved !!!
Solved thx to everybody. http://forum.xda-developers.com/one...een-fastboot-adb-t2835696/page16#post55129486 this helped
Great news.
Transmitted via Bacon
So I have OnePlus One screen problems. First I dropped it and the screen cracked, so I had it replaced. After it got replaced I now have it back, but before screen worked and touch didn't, and now touch works and screen doesn't. The screen doesn't turn on at all, but when it is plugged in I know it is turned on and I can browse through the filesystem of the OnePlus One via my computer and also when I swipe I can hear the unlocking sound. However, data, WiFi and ADB is disabled so I can't get into there. However, saying Ok Google I can hear the response it gives me so I tried calling a friend but the call never went through. It's running CyanogenMod 12S with TWRP and Xposed flashed if that helps any. I did try following the guide using ColorOS to restore it as if it's hard bricked, but since it never seems to boot into fastboot (spamming fastboot devices in cmd never shows anything) I can't seem to do anything. I tried this on both of my computers running Windows 7, and it never shows up in fastboot, so I don't know which COM port it is to finish the guide, because it wouldn't show up abnormally. Can anyone help me figure out how to get the phone into fastboot? Thank you all so much! Also I don't really have any pictures or videos because I don't have another phone/camera to take them with. Sorry!
Update: I was able to get it into fastboot by getting it into recovery and then typing adb reboot bootloader, but that's about the extent of it. I have Bacon Root Toolkit and stuff and I'm willing to wipe my phone (because there isn't anything that I don't have a backup of) but all I really want is a solution to fix it. It did show up a few times as QHSUSB_BULK (twice, actually) but it also seems to be working, because if I take a screenshot, then reboot to recovery, I can pull the screenshot from the memory to my computer. For some reason the phone isn't showing up at all except in fastboot and recovery now.
I had the same issue with my OPO on Exodus, what I did was I pressed the power button to open the screen then unlocked the screen like usual and then brought the notification bar down and change the brightness by pressing on auto brightness button multiple times and in this whole process my screen was black then I successfully turned on my phone's screen. It also work if you just reboot the phone.
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
Also this issue was in the ROM itself and it was fixed in an update.
So i bougth an used S8+ (g955u) which seems to be from verizon. the thing is that right on the first boot i put in my simcard(AT&T) and microSD card, the phone booted whit a verizon screen then on the first settings screen a windows pop-up told me to reset it, cant remember why, but i tap on yes, after that the phone reboot again but now with an AT&T screen, i was unable to pass the fist settings due to playstore stopping everytime after the wifi setup, so i took out the sim card and skip the wifi setup and finally get to the home screen. but the problems dont end there cuz some apps were forceclosing when i tried to open it (internet browser, playstore even i was able to log in with my account tho) and some times when i reboot the phone it get stuck bootlooping until i force a shutdown and turn it on again... now here start the part where i need help i tried to flash another software version whit odin, but no matter what uptdated or outdated the phone says: Secure chek fail:system even whit the version it supposedly came, im on bootloader 5 i think and now im stuck on download mode. is there a way to flash a stock or custom firmware or should i let it die?
builderkage said:
So i bougth an used S8+ (g955u) which seems to be from verizon. the thing is that right on the first boot i put in my simcard(AT&T) and microSD card, the phone booted whit a verizon screen then on the first settings screen a windows pop-up told me to reset it, cant remember why, but i tap on yes, after that the phone reboot again but now with an AT&T screen, i was unable to pass the fist settings due to playstore stopping everytime after the wifi setup, so i took out the sim card and skip the wifi setup and finally get to the home screen. but the problems dont end there cuz some apps were forceclosing when i tried to open it (internet browser, playstore even i was able to log in with my account tho) and some times when i reboot the phone it get stuck bootlooping until i force a shutdown and turn it on again... now here start the part where i need help i tried to flash another software version whit odin, but no matter what uptdated or outdated the phone says: Secure chek fail:system even whit the version it supposedly came, im on bootloader 5 i think and now im stuck on download mode. is there a way to flash a stock or custom firmware or should i let it die?
Click to expand...
Click to collapse
Hmmm i would start with the latest firmware. If that fails maybe flash the latest combination file then firmware.
As for verizon att. These device normally now are multi csc selects system based on sim inserted which is awesome when it works right. But oreo and up i think checks system integrity so i would start with the combination files bit 5 then firmware
TheMadScientist said:
Hmmm i would start with the latest firmware. If that fails maybe flash the latest combination file then firmware.
As for verizon att. These device normally now are multi csc selects system based on sim inserted which is awesome when it works right. But oreo and up i think checks system integrity so i would start with the combination files bit 5 then firmware
Click to expand...
Click to collapse
Thanks, I've tried that already. Android 9 version, the B5 combination files. Even flashing every file one by one the problem is with system. Idk why but fails at the last second, I'm thinking in use the repartition option in Odin but I'm afraid it could get worse
builderkage said:
Thanks, I've tried that already. Android 9 version, the B5 combination files. Even flashing every file one by one the problem is with system. Idk why but fails at the last second, I'm thinking in use the repartition option in Odin but I'm afraid it could get worse
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s8+/development/root-t3909782
Might try his root and safe strap method this uses edl to push a system
doesn't work, i cant flash nothing that has to do to system. is there a way to reboot it into bootloader and use the fastboot commands? like fastboot flash xxxxxxx.img system?
TheMadScientist said:
https://forum.xda-developers.com/galaxy-s8+/development/root-t3909782
Might try his root and safe strap method this uses edl to push a system
Click to expand...
Click to collapse
builderkage said:
doesn't work, i cant flash nothing that has to do to system. is there a way to reboot it into bootloader and use the fastboot commands? like fastboot flash xxxxxxx.img system?
Click to expand...
Click to collapse
Nope locked bootloader
---------- Post added at 02:25 PM ---------- Previous post was at 02:24 PM ----------
If you can push a system using edl them something really wrong
TheMadScientist said:
Nope locked bootloader
---------- Post added at 02:25 PM ---------- Previous post was at 02:24 PM ----------
If you can push a system using edl them something really wrong
Click to expand...
Click to collapse
The thing is that to reboot into edl seems that first I have to be able to boot into system or a composition rom, Wich I'm unable to cuz the phone doesn't let me flash the system partition
Hello Mr. Mad Scientist I had a question, I bought a Samsung Galaxy s8 + like 3 weeks ago and it dropped at work it was fully dead when it fell,so I finally bought all the pieces necessary for the operation?know the devise is together yet it's on a black screen of death.i tried the volume down and power at the same time.and nothing. Can it be the battery ? Or what can it be all ribbons everywhere are snapped on correctly. Pls help it's an expensive device
vtech7634 said:
Hello Mr. Mad Scientist I had a question, I bought a Samsung Galaxy s8 + like 3 weeks ago and it dropped at work it was fully dead when it fell,so I finally bought all the pieces necessary for the operation?know the devise is together yet it's on a black screen of death.i tried the volume down and power at the same time.and nothing. Can it be the battery ? Or what can it be all ribbons everywhere are snapped on correctly. Pls help it's an expensive device
Click to expand...
Click to collapse
Lol i just responded in the other thread. If you dropped it take a bright flash light on the screen and inspect for any cracks under the gorilla glass. Sometimes the oled can crack without the outer glass breaking. If not. Try bixby vol down and power for upto 20 sec
---------- Post added at 07:42 AM ---------- Previous post was at 07:42 AM ----------
builderkage said:
The thing is that to reboot into edl seems that first I have to be able to boot into system or a composition rom, Wich I'm unable to cuz the phone doesn't let me flash the system partition
Click to expand...
Click to collapse
Its hard to say then not having the device in hand to try loads of things my self
TheMadScientist said:
Lol i just responded in the other thread. If you dropped it take a bright flash light on the screen and inspect for any cracks under the gorilla glass. Sometimes the oled can crack without the outer glass breaking. If not. Try bixby vol down and power for upto 20 sec
---------- Post added at 07:42 AM ---------- Previous post was at 07:42 AM ----------
Its hard to say then not having the device in hand to try loads of things my self
Click to expand...
Click to collapse
I also read that these phone just like the htc1+ and many others when the battery is under 5% like mines was I might need a jumpstart I tried the 20 sec method and nothing also the screen is a new one but I will try the flashlight thing since it came through mail it could've easily fell and broke the world may never know ?? thank you my friend for answering I will get a new battery and keep u posted