Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
So, i was trying to flash a ROM after i got my recovery and root going on, i wiped EVERYTHING INCLUDING THE recovery file i made and the installation file i got in the phone when i went to wipe the system files and attempt to install the ROM. So, i tried to put the ROM files into my phone via the ADB method. It worked but my ROM didn't and now my S6 is in a boot loop. i have tired Odin, smartwatch and kies. On kies and smart watch, they both said the attempt to install stock ROM failed and attempt a emergency recovery. HOWEVER, both software did not recognize my device in the emergency recovery devices list, nor did it recognize it as a compatible device in the 1st place, i tired to reinstall the drivers and the software themselves but nothing worked. For Odin, it keeps on saying fail to flash as well, it usually stuck on the 'nano write' process or 'setting up connection' process for a long time too! I did download the official Samsung firmware and extracted it, put it into the blank next to the 'AP' button in odin and i got 'Auto Reboot' and 'F. Reset Time' checked off. On the phone, i can boot in to download mode and download mode only, now it shows me a triangle and it says that stock firmware flash failed and use emergency recovery. i actually download a custom recovery and for some reason it wont boot into that.
Model number: SM-G920W8
carrier: fido
If any of you pros got any ideas please share with me, i've been trying to fix this problem for about a day and a night.
try "nand erase all" in odin while flashing the stock fido rom
noob924 said:
try "nand erase all" in odin while flashing the stock fido rom
Click to expand...
Click to collapse
well it either says fail or stuck in set up connection
Use smart switch
shahram Ali said:
Use smart switch
Click to expand...
Click to collapse
like i said man, both kies and smartwatch don't work.
BigBlackCook said:
like i said man, both kies and smartwatch don't work.
Click to expand...
Click to collapse
it should work !!
shahram Ali said:
it should work !!
Click to expand...
Click to collapse
On kies and smart swich, they both said the attempt to install stock ROM failed and attempt a emergency recovery. HOWEVER, both software did not recognize my device in the emergency recovery devices list, nor did it recognize it as a compatible device in the 1st place, i tired to reinstall the drivers and the software themselves but nothing worked. I even contacted Samsung and they said that it won't work because my device is rooted. i've seen videos of it working but not for me, did i do anything wrong or did i miss anything?
BigBlackCook said:
On kies and smart swich, they both said the attempt to install stock ROM failed and attempt a emergency recovery. HOWEVER, both software did not recognize my device in the emergency recovery devices list, nor did it recognize it as a compatible device in the 1st place, i tired to reinstall the drivers and the software themselves but nothing worked. I even contacted Samsung and they said that it won't work because my device is rooted. i've seen videos of it working but not for me, did i do anything wrong or did i miss anything?
Click to expand...
Click to collapse
dude dont use emergency recovery use device initialization
shahram Ali said:
dude dont use emergency recovery use device initialization
Click to expand...
Click to collapse
IT WORKED!!! idk why it didint work the 1st damn time but i guess it's the usb connection or what not. Now it workes, time to root again and re-uninstall the bloat ware.. prob wont install a rom tho btw.. since ur a pro, what else do ppl do afterthey root their phone? other then to uninstall bloatware
BigBlackCook said:
IT WORKED!!! idk why it didint work the 1st damn time but i guess it's the usb connection or what not. Now it workes, time to root again and re-uninstall the bloat ware.. prob wont install a rom tho btw.. since ur a pro, what else do ppl do afterthey root their phone? other then to uninstall bloatware
Click to expand...
Click to collapse
ahaha congratulations dude but take back up of your EFS cause bricking sometimes make it gone take a back up and keep it somewhere safe and add solved near thread title
shahram Ali said:
ahaha congratulations dude but take back up of your EFS cause bricking sometimes make it gone take a back up and keep it somewhere safe and add solved near thread title
Click to expand...
Click to collapse
what's EFS?
BigBlackCook said:
what's EFS?
Click to expand...
Click to collapse
it is youre imei wifi etc it is important thing to back up
shahram Ali said:
it is youre imei wifi etc it is important thing to back up
Click to expand...
Click to collapse
yeah cause with out the S/R, smart swich won't work D: good thing is that the sticker on the bak of my phone has all that info on it, it kinda saved my life.
BigBlackCook said:
yeah cause with out the S/R, smart swich won't work D: good thing is that the sticker on the bak of my phone has all that info on it, it kinda saved my life.
Click to expand...
Click to collapse
yeah it is
shahram Ali said:
yeah it is
Click to expand...
Click to collapse
about roms, i still got 5.1.1 so if i want to install a rom, does it matter? or is it just about finding the 1 for your model. i want to install XtreStoLite but some versions have android 6.0 in the title and some have 5.1.1, and why don't posts about roms have any comments?
BigBlackCook said:
about roms, i still got 5.1.1 so if i want to install a rom, does it matter? or is it just about finding the 1 for your model. i want to install XtreStoLite but some versions have android 6.0 in the title and some have 5.1.1, and why don't posts about roms have any comments?
Click to expand...
Click to collapse
If u want 6.0.1 and i recommend to use 6.0.1 u need 6.0.1 bootloader and modem and ur phone is canadian so find an w8 rom but flash 6.0.1 modem and bootloader
shahram Ali said:
If u want 6.0.1 and i recommend to use 6.0.1 u need 6.0.1 bootloader and modem and ur phone is canadian so find an w8 rom but flash 6.0.1 modem and bootloader
Click to expand...
Click to collapse
so u ned to flash boot loaders and modem? damn maybe dats why that rom bricked my phone LOL
BigBlackCook said:
so u ned to flash boot loaders and modem? damn maybe dats why that rom bricked my phone LOL
Click to expand...
Click to collapse
If you flashed 6.0.1 rom on 5.1.1 bootloader maybe
shahram Ali said:
If you flashed 6.0.1 rom on 5.1.1 bootloader maybe
Click to expand...
Click to collapse
LOL i got it bricked again after installing both the boot loader and a modem.. i did them 1 by 1 and for some reason it says success in odin but had to reinstall firmware again to make my s6 work.. how do people install rom these days..
BigBlackCook said:
LOL i got it bricked again after installing both the boot loader and a modem.. i did them 1 by 1 and for some reason it says success in odin but had to reinstall firmware again to make my s6 work.. how do people install rom these days..
Click to expand...
Click to collapse
dude install stock then flash twrp and use ur model number rom not others 6.0.1
Hey ! First of all excuse my english I'll do my best.
I flashed CM13 to test it. To do that I flashed the TWRP you can find in CM's thread and just after I wiped the data because without that you're unable to wipe cache/dalvik/system. After the flash everything was right except for some reasons in my opinion this rom wasn't smooth enough so I wanted to go back to EMUI (damn EMUI never thought i could want to go back to this again).
To do that I flashed The "normal" TWRP and tryed to wipe my data. It was impossible. Si I tryed to restore my nandroid, impossible too. Some errors messages.
So I flashed the CM's TWRP and was finally able to wipe my data and restore my EMUI nandroid. After that I tryed to flash again the "normal" TWRP and take a look at the wipe options to see if I was able to wipe data or dalvik or whatever but the same errors messages came to my face.
Is there a way to fix the wipe of my TWRP without rollback to stock and root again ?
I hope I was clear, my english really sucks.
Thank you guys.
Androhyp said:
Hey ! First of all excuse my english I'll do my best.
I flashed CM13 to test it. To do that I flashed the TWRP you can find in CM's thread and just after I wiped the data because without that you're unable to wipe cache/dalvik/system. After the flash everything was right except for some reasons in my opinion this rom wasn't smooth enough so I wanted to go back to EMUI (damn EMUI never thought i could want to go back to this again).
To do that I flashed The "normal" TWRP and tryed to wipe my data. It was impossible. Si I tryed to restore my nandroid, impossible too. Some errors messages.
So I flashed the CM's TWRP and was finally able to wipe my data and restore my EMUI nandroid. After that I tryed to flash again the "normal" TWRP and take a look at the wipe options to see if I was able to wipe data or dalvik or whatever but the same errors messages came to my face.
Is there a way to fix the wipe of my TWRP without rollback to stock and root again ?
I hope I was clear, my english really sucks.
Thank you guys.
Click to expand...
Click to collapse
If the cm twrp is working fine with emui for backup/restore then just keep using it tbh
You can read to the CM's thread :
Warning :
* recovery not compatible to stock Huawei Firmware !
Click to expand...
Click to collapse
I think there is a reason to that and I don't want to brick my MMC or anything for something like that..
Androhyp said:
You can read to the CM's thread :
I think there is a reason to that and I don't want to brick my MMC or anything for something like that..
Click to expand...
Click to collapse
Probably try fastboot erase recovery
Than fastboot flash twrp.img
Sent from my Mi 4i using Tapatalk
chongns said:
Probably try fastboot erase recovery
Than fastboot flash twrp.img
Sent from my Mi 4i using Tapatalk
Click to expand...
Click to collapse
seams he's not good enough to get that so I'll explain more !
for some reason or flashing roms u' might get some errors while flashing roms or trying to wipe data ! ..
restoring ur nandroid sometimes need to be restored throw the same recovery but for some binary errors while restoring or for some reason it wont !
I recommended to do the following :
Use the full restoration method to get back into stock fresh . ( to do that all u need is : download fresh rom from official EMUI website then send it to SD card , put it into ur phone , make sure its off , press volume Up+Down+Power for 3 seconds or 4 then will start getting back ur original Software ) if u got fail might be for some reason of a kernel so u'll need to do the ADB Method will be later if fail only .
now after getting back to stock install TWRP again and make nandroid restore only for data without system and cach and delvik
u must get all ur phone back as will but the restoration should be only above same rom version and custom number .
GD Luck ..
Thank you for the "not good enough" man I'm flashing roms since 2009, I had a lot of phones and a lot of way to flash roms. My english sucks, not me.
I know how to erase the recovery but I already try to flash different recovery, it's obvious for me that my problem is here because of the encryption missing of the DATA partition who have been erase by the CM's TWRP. I try to find a way to fix the encryption without get back to stock because it's a pain in my ass and if I can do another way I'll be happy. I hate come back to stock, it's a waste of time to come back to all tweaks I made on my actual rom.
But if I have to come back to stock I'll do it.
I'm use to work with phones more open than Honor so I'm a little disapointed about all the pain devs have with this phone.
Thanks for your help anyway. Oh and yes, I can be wrong about encryption but I don't think so.
Much love.
Androhyp said:
Thank you for the "not good enough" man I'm flashing roms since 2009, I had a lot of phones and a lot of way to flash roms. My english sucks, not me.
I know how to erase the recovery but I already try to flash different recovery, it's obvious for me that my problem is here because of the encryption missing of the DATA partition who have been erase by the CM's TWRP. I try to find a way to fix the encryption without get back to stock because it's a pain in my ass and if I can do another way I'll be happy. I hate come back to stock, it's a waste of time to come back to all tweaks I made on my actual rom.
But if I have to come back to stock I'll do it.
I'm use to work with phones more open than Honor so I'm a little disapointed about all the pain devs have with this phone.
Thanks for your help anyway. Oh and yes, I can be wrong about encryption but I don't think so.
Much love.
Click to expand...
Click to collapse
You r welcome. But you waste people time. Why u just can't post the actual problem like your last post so people not able to help wouldn't wasting their time trying to help here, so good luck and have a nice day.
Sent from my FRD-L09 using Tapatalk
Androhyp said:
Thank you for the "not good enough" man I'm flashing roms since 2009, I had a lot of phones and a lot of way to flash roms. My english sucks, not me.
I know how to erase the recovery but I already try to flash different recovery, it's obvious for me that my problem is here because of the encryption missing of the DATA partition who have been erase by the CM's TWRP. I try to find a way to fix the encryption without get back to stock because it's a pain in my ass and if I can do another way I'll be happy. I hate come back to stock, it's a waste of time to come back to all tweaks I made on my actual rom.
But if I have to come back to stock I'll do it.
I'm use to work with phones more open than Honor so I'm a little disapointed about all the pain devs have with this phone.
Thanks for your help anyway. Oh and yes, I can be wrong about encryption but I don't think so.
Much love.
Click to expand...
Click to collapse
It might actually be the problem with recovery too .. Can u send a screenshot or what sort of error u faced ?
The error code ? Or any log ?
Any of this could help u instead of saying just the problem
chongns said:
Why u just can't post the actual problem like your last post so people not able to help wouldn't wasting their time trying to help here
Click to expand...
Click to collapse
Because my english sucks man, I can understand, I can talk but it's hard for me to explain a problem from zero to the end. It seems my last message was more clear for you than my first, for me they are saying the same things.
I didn't try to be mean to anyone, every help is always welcome. We are more smart when we are two, three....
gopinaidu77 said:
It might actually be the problem with recovery too .. Can u send a screenshot or what sort of error u faced ?
The error code ? Or any log ?
Any of this could help u instead of saying just the problem
Click to expand...
Click to collapse
Thanks man but between I have an answer of surdu_petru in private message whose telling me to watch here : http://forum.xda-developers.com/showpost.php?p=70131271&postcount=350
So the problem seems to be with encryption, I'll have to come back to stock, this will encrypt the DATA partition and fix my problem. IMO it should be said somewhere in CM's thread.
Thank to all of you.
Androhyp said:
Because my english sucks man, I can understand, I can talk but it's hard for me to explain a problem from zero to the end. It seems my last message was more clear for you than my first, for me they are saying the same things.
I didn't try to be mean to anyone, every help is always welcome. We are more smart when we are two, three....
Thanks man but between I have an answer of surdu_petru in private message whose telling me to watch here : http://forum.xda-developers.com/showpost.php?p=70131271&postcount=350
So the problem seems to be with encryption, I'll have to come back to stock to encrypt the DATA partition and start to zero. IMO it should be said somewhere in CM's thread.
Thank to all of you. Kiss without the tong but I touch you ass
Click to expand...
Click to collapse
?alright. You figured it out yourself .. And the last lines are weird ..?
Sent from my KIW-L22 using Tapatalk
Androhyp said:
Thank you for the "not good enough" man I'm flashing roms since 2009, I had a lot of phones and a lot of way to flash roms. My english sucks, not me.
I know how to erase the recovery but I already try to flash different recovery, it's obvious for me that my problem is here because of the encryption missing of the DATA partition who have been erase by the CM's TWRP. I try to find a way to fix the encryption without get back to stock because it's a pain in my ass and if I can do another way I'll be happy. I hate come back to stock, it's a waste of time to come back to all tweaks I made on my actual rom.
But if I have to come back to stock I'll do it.
I'm use to work with phones more open than Honor so I'm a little disapointed about all the pain devs have with this phone.
Thanks for your help anyway. Oh and yes, I can be wrong about encryption but I don't think so.
Much love.
Click to expand...
Click to collapse
Sorry for my rode way , and glad that u got problem fixed !
Romiui said:
Sorry for my rode way , and glad that u got problem fixed !
Click to expand...
Click to collapse
Spread peace.
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
@PriPhaze is your device stock(bootloader locked) or modified in any way?
aaycce said:
The problem isn't the phone, the problem is you. Clearly you stuffed the phone up yourself by trying to mod/root it and now you have ruined it further by flashing incorrect images to the device.
You shouldn't be coming to XDA when the fault is entirely on you, I've seen it all before.
Click to expand...
Click to collapse
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
strongst said:
@PriPhaze is your device stock(bootloader locked) or modified in any way?
Click to expand...
Click to collapse
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
PriPhaze said:
Really? Lol it's that the best you could say? Trying to sound smart eh ? lmao
Clearly you don't know what you saying so you are not the person I'm looking for but "thanks" for such "helpful" respond.
Hi, the device is unlocked right now. I didn't install any other ROM other than OOS.
Click to expand...
Click to collapse
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
strongst said:
Thank you for the reply. Is the bootloader just unlocked or do you have installed anything like twrp, magisk or others?
Which version of OxygenOS do you have?
Click to expand...
Click to collapse
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
PriPhaze said:
Thanks to you
Ahh yes twrp was installed but now it's inaccessible .
After the phone freezed I can no longer use twrp.
Also yes magisk was installed to restore my apps using swift backup.
OOS version is the last one available.
Click to expand...
Click to collapse
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
strongst said:
It might be a good idea to use unbrick tool and clean flash the stock OxygenOS, recovery and remove root to see if it behaves better.
Click to expand...
Click to collapse
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
PriPhaze said:
I did, same behaivor ; in 2 days more less it will freeze and reboot and then system will be gone.
And so i need to use MSM tool again to get it back running. The only thing i have not tried is to use a custom ROM insetad of OOS
Click to expand...
Click to collapse
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
strongst said:
Maybe I did not understand correctly: Did you tried the stock rom without unlocking the bootloader and magisk? Or did you immediately unlock and install magisk immediately and then test?
The stock rom is stable and should work, otherwise a hardware issue can be the problem why you have those issues.
Click to expand...
Click to collapse
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
PriPhaze said:
Yea tried with locked bootloader and then unlocked .
So yea maybe i wasn't clear enough but what i meant with the first post is that im 90% sure that here is a hardware issue but i dont really know what could be and there is not repair service in my country.
Thats why the only option i have left is to figure out what is wrong and change that part.
Iwas hoping someone could guide me to figure out which part i need to change.
Click to expand...
Click to collapse
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
strongst said:
Hmm, I can't tell you which part to exchange cause it can be the processor, flash for example which you cannot exchange. Battery might be an option, but that's not really the culprit imo...
Click to expand...
Click to collapse
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
PriPhaze said:
Well in any case the cpu and internal memory are in the same board no? so that probably means i would need to change the whole board wich is 250US
Click to expand...
Click to collapse
Yes, everything is on board. It's the worst case for, sadly...
Or you buy a device with broken screen and exchange the board /display. Depends how much you have to spent for this at all.
PriPhaze said:
Ok so i will try to go straight to the point.
I got OnePlus 7 that i bought from Aliexpress (8gb and 256gb) the thing is that im almost 90% sure this phone is defective.
You can use teh phone correctly for about 2 days then all of a sudden it will freeze completely and then you CANT do absolutely anything else, not even turn it off by holding power button ..
So i just left it there until it ran out of battery.
Then i charge while inside the fastboot and when i try to boot it is in a boot loop , doesnt even go into the boot animation
and to make things even more interesting i tried to wipe data guess what? The phone screen suddendly started blinking until again it ran out of battery. (you could see for a split of a second every time the screen blinks the progress bar of the wipe but it never moved from initial point).
So yea at this point is pretty obvious that something is wrong so i bought a Mi9T Pro meanwhile but i dont want this phone to go to waste.
Anyone out there has a clue of what could be? I wanna attempt to fix it myself if possible.
Aliexpress just gave a bit of the money back and the company Hongkong Goldway didnt give a f and they even go as far as to pretend they don't know what i'm saying ( the language barrier when it beneficial for them ).
This was gonna be a short explanation but i guess it was neccesary to be this long to explain correctly whats going on.
BTW: the only way yo make the phone work again for 2 days mayebe 3 is by using the MSM tool , any other method doesnt work.
also when it was working i filled the whole 256gb to kinda check the internal memory for corruption but it actually filled up without any problem so idk .
Click to expand...
Click to collapse
Ah yes, the common misconception that power shuts it off. Nope, not this phone. You have to hold power and volume up together to power off the phone when it crashes. Make sure you're using the latest platform tools (adb/fasboot) to unlock your phone. Make sure oem unlocking is enabled in developer settings after you've unlocked, having it disabled for some reason does screwy things. Mine was disabled once when I downgraded to Android 9 using the all in one tool available on xda, I thought I bricked the phone because it wouldn't boot after a reboot. Flash the latest oos twice through the system local upgrade feature, this will put the current oos on all partitions. Use the correct twrp, the unified versions found on xda 3.3.1-75 and 3.3.1-76 work well for me. The installer zip for those can be used in magisk to flash twrp after an OTA update before reboot. So, local upgrade 100% -> magisk modules "+" twrp 3.3.1-75 unified installer zip -> reboot to recovery -> flash magisk 20.3 at least (20.4 is available now). Do this twice so that everything is the same version on all the partitions. Lastly restore apps with swift backup without data, I know it's not ideal but may be necessary because some app's data may be corrupt and causing this. Good luck. Of course at any time you have it running you can reboot in safe mode (touch and hold restart until the dialogue pops up) and see how long you can use it without any third party apps to confirm that it is an app you installed.
Man I had the exact same problem as you and I got it fixed this morning after nights of fastboot commands trial and error found this thread forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Tried a few times before it worked but saved my phone all I had was fastboot mode and no recovery make sure to manually flash all fastboot commands you will then get stock recovery back wipe using all 3 options go 1st 2nd 3rd and then 1st wipe again after reboot phone might hang just force reboot and fixed
I really appreciate all the replies really but hmm im guessing there's a misunderstanding on what im saying.
I do know how to flash and recover one plus devices using MSM tool if neccesary, also to flash the fastboot rom .
The thing here is that everytime i recover the phone and all seems stable and working good , after a2 days more less it will random freeze of death and you cant even reboot holding power button NOTHING! is completely freezed.
So yea, thats pretty much it, i have tried already all that you said so far :c.
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Passportpowell said:
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Click to expand...
Click to collapse
do you have usb debugging enabled, are your sdk tools up to date?
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Passportpowell said:
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Click to expand...
Click to collapse
then you need to update your htc drivers.
here you go.
Aldo101t said:
do you have usb debugging enabled, are your sdk tools up to date?
Click to expand...
Click to collapse
Aldo101t said:
here you go.
Click to expand...
Click to collapse
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
I've done a format data on twrp and it won't ask for a password anymore but I still can't sideload anything. Going to try to copy the rom to the storage and see what happens there
I've only could see a twrp folder on my phone when I connect it to my pc while still in twrp so I copied a rom there and went into install zip, data, media, twrp. My file was there.
Installing rom now I'll update if it worked.
Passportpowell said:
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
View attachment 5087597
View attachment 5087599
Click to expand...
Click to collapse
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
here is magisk
if you are on pie that viper rom is based on oreo. just so you know.
Aldo101t said:
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
Click to expand...
Click to collapse
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Aldo101t said:
if you are on pie that viper rom is based on oreo. just so you know.
Click to expand...
Click to collapse
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Passportpowell said:
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Click to expand...
Click to collapse
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Aldo101t said:
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Click to expand...
Click to collapse
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Passportpowell said:
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Click to expand...
Click to collapse
3.37.617.1 is for the us-unlocked
Hello to everyone...I just got from my older brother his HTC U11 4gb 64gb phone. And it has locked bootloader and does not have root. So please what should I have to do so I can install custom rom. Stock rom is old full of bloatrware. There is so many information that I am confused.
Thx so much !