Related
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
ClockworkMod Recovery v3.0.2.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
Thanks
-Kagen
notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
How did u get it bricked?
xudsa II USERT said:
How did u get it bricked?
Click to expand...
Click to collapse
A friend rooted it over a year ago.
Everything worked fine, so we flashed a ROM. (don't remember which one)
That worked fine, then few days later things on the phone started to fail. Slowly more and more things failed. Then I was forced to reboot the phone.
When I rebooted It stuck on boot screen. now I get those logs in recovered that I originally posted.
To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)
xudsa II USERT said:
To say the worse, it sounds like a corrupted file system acutally . You can get to HBOOT screen right? (Vol + Power On)
Click to expand...
Click to collapse
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
notKagen said:
Yes, I can get there very easily.
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse
EDITED: GAVE EXPLAINATION
notKagen said:
Yes, I can get there very easily.
Is a corrupt file system irreversible? That sounds like something where I could just replace the files with non-corrupt ones...maybe? haha as you can see I know nothing.
Click to expand...
Click to collapse
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/
xudsa II USERT said:
EDITED: GAVE EXPLAINATION
Erm.. I'm not too sure, it could be just maybe a small error fixable by 'replacing', but then again it could be a physical damage (bad sectors, but those are usually very very rare).
If your bootloader does function fine, it could be the former (though not being able to mount in recovery sounds like a bad sector). It is possible that you can load a rom through ur sd card and restore it through the bootloader. (I'm still learning that part). Be very very very careful! You can actually make your phone not work! Do a lot of research, and don't rush! Hopefully someone with much more experience can help from here on.
I'll explain here: if your phone does not boot, usually it could mean that some files cannot be read or are missing, so the phone will not boot android. The fact that the recovery states that it cannot mount the filesystem could mean that there is a possibility that your memory filesystem may be corrupted. But, since it can boot the bootloader without problems, there is a high possibility that the problem lies in the recovery files being problematic themselves. In that case, you can load a original rom (BE VERY CAREFUL BEFORE YOU DO SO, I ASKED HERE, so this could be a jumping board for you.). A mention, u must be careful, loading a full ROM includes loading the bootloader as well, so it may cause your phone to not even load the bootloader.
I really think someone with better experience should help from here on, i dont want to brick your phone :/
Click to expand...
Click to collapse
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.
notKagen said:
Alright man, I'll follow the link but I don't know if this will help you. Some things when I am in HBOOT and I hit them they do nothing. Just freeze the phone. I don't know if that changes things.
Click to expand...
Click to collapse
Okay, I tried what you said but no success. My ClockworkMod seems to not be mounting. Because of the Errors I posted previously in my first post. So this way I can't flash anything from recovery because it will just stay on that screen with the top hat and the orange circle with the arrow. Nothing happens. If I tap the power button, it just goes back to the menu.
Should I be updating clockwork somehow?
Is there another way to flash?
Could there be a problem with my SD's? (i've tried on 2 different ones)
Do you have any ideas?
This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
Firstly, don't select stuff with power button in clockwork, use the camera or trackpad.
Secondly, those errors may indicate a bad emmc, which is a hardware defect, and cannot be fixed. More info here
You can either go for a warranty replacement, or you can boot cm7.1 from your sdcard, using Catherall's instructions
-Nipqer
EdWaRdW818 said:
This is an educated guess, but you might want to try flashing the stock firmware back onto the phone and trying again, and ensure the MD5s match. You could even follow the instructions in the wiki to give CyanogenMod ROM a try; that's what I'm using now and is the more widely developed and recognizable ROM that I know of.
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
Click to expand...
Click to collapse
Sure, I can try that. Is there a step by step....don't really know what im doing.
Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium
demkantor said:
Almost 100% you have a bad emmc, there is no fix for this, nipqer sent you a guide to run an os off your sdcard and this may be your only 'fix'
You can try and flash a new recovery via fastboot and a rom as well. But my best guess is your sol, try to warranty it if possible, run os off sd, or sell it for parts and get a new one
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Alrighty! Thanks for your help!
reflash a new ROM
notKagen said:
My T-Mobile HTC G2 gets stuck on the HTC white & green boot screen..
I read some forums and apparently I'm not bricked. I can get the the HBOOT screen.
I want to make this phone useable again, so if anyone has any methods at all, help me out please. I am a noob with andriod.
I will need step-by-steps!
VISION PVT SHIP "S-OFF"
Thanks
-Kagen
Click to expand...
Click to collapse
Dude This happened to me too first if you downgraded to froyo and if you kept a nandroid backup of it restore to the froyo nandroid backup BE SURE THE NANDROID BAKUP OF THE FROYO VERSION IS A ROOTED ONE OR ELSE YOU'LL BRICK YOUR PHONE OR SCREW UP THE ROOT!! then after that flash another ROM using fastboot in bootloader mode
okay heres what to do
1.Open A CMD window in windows
2.Navigate to the folder where you have fastboot for example cd...
cd...
cd /
C:\Android SDK\Platform Tools
then you should also have ADB at the same folder together with Fastboot
then plug your phone while it fastboot mode in Bootloader
it should say "FASTBOOT USB"
3.Then verify that your computer recognizes your Phone by typing "fastboot devices" without (" ")
4.put the ROM.zip on the same folder where you have Fastboot and ADB
5. type in fastboot clear cache (I don't know the exact command but you need to clear cache)
6. AFTER CLEARING CACHE TYPE IN "fastboot flash zip ROM.zip (REPLACE "ROM" with the right ROM name it ahould be like ICS.zip or whatever your gonna flash
7. just let it do its job
8.Celebrate if it worked =))
PM me if you need more help
SOMEONE PLEASE CORRECT ME IF I DID SOMETHING WRONG
-goodluck
Hey all. I'm thinking I may have bricked my mother's Zenfone So I was trying to help her out by installing a custom rom on the phone as she complained about the bloatware that comes with the phone slowing things down. I couldn't get the bootloader unlocked (tried every procedure under the sun), so I tried entering recovery mode and flashing the boot.img and droidboot.img directly (saw a thread where someone did this, then tried unlocking and it worked).
The phone boots into up fine but now everytime I try entering recovery mode, I get the dreaded USB logo screen. It remains there for about a minute, reboots and comes back again. Does that about 3-4 times before turning off. Is there a way to just completely get the phone back to 100% factory settings? I'd rather just starting over from there. The problem I'm having is pretty much exactly the same as what the person in the video below is experiencing....
Can you get to bootloader mode?
Sent from my ASUS_Z00AD using Tapatalk
jimchee said:
Can you get to bootloader mode?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Sorry for the late reply. If u mean Fastboot mode, where I can see the Product name, Booloader version, etc, then no. That's where I see the USB icon.
You've screwed it up, there might be a way if you can flash a RAW image of the rom on there but you'd need to look around as I can't remember the thread name, something about recover hard brick (which is what you have)...
ultramag69 said:
You've screwed it up, there might be a way if you can flash a RAW image of the rom on there but you'd need to look around as I can't remember the thread name, something about recover hard brick (which is what you have)...
Click to expand...
Click to collapse
Hmmm. Well I came across this thread...
http://forum.xda-developers.com/zenfone2/general/unbricking-research-unbricking-method-t3162848
They seem to have procedures to help with my issue. But I came across another problem. Hopefully someone there could help with it. I post here if I succeed.
hi, I removed os from my Asus and now it is not entering fast boot mode any one can kindly help me pls.
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
w144mjb said:
Hello XDA!
I have a Verizon Pixel XL that is stuck in a boot-loop after the 7.1.2 firmware update. The boot-loop did not begin immediately after the update which confuses me. I have never attempted to unlock the bootloader, root, or flash the firmware. I have thousands of pictures I am attempting to recover (I did not have coverage to backup the pictures in Google Photos) before I work on the boot-loop issue (or warranty replacement). I can access fastboot & recovery but these modes do not provide a backup option or backup command from ADB. When I boot to safe-mode the phone will stay on for about 10 seconds which has allowed me to disable a LOT of apps and enable USB debug.
As I see it, there are only two options available to me...
1) Find a way to 'halt' the system after start-up or find the mysterious app causing the issue and disable it.
2) Forensic (physical) data recovery for $500-$900
I have tried to research as much as possible (please correct me if I'm wrong): unlocking Verizon bootloader is not currently possible, installing custom recovery is either not possible or will wipe the device, and pushing a firmware update will also wipe the device.
If anyone has any suggestions or would like more information please let me know.
I will keep an eye on this thread to provide timely responses.
Thank you,
Matthew
Click to expand...
Click to collapse
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Tulsadiver said:
Flashing updates do not wipe your data. Download firmware of choice. Unzip it, place latest fastboot drivers in where update zip is. Rename it to something easy. fastboot update update.zip
Edit: enclosed fastboot drivers
Click to expand...
Click to collapse
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
w144mjb said:
Thank you Tulsadiver!
Do you think the firmware update will also fix the boot loop?
Click to expand...
Click to collapse
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
w144mjb said:
Being the noob that I am, I have a few more questions.
Do I have to unlock the bootloader to update the firmware?
I'm currently on NHG470 firmware, should I choose NHG47N or NHG47K or a different one?
I'd like to keep the phone on a factory image unless you suggest otherwise.
Thank you for your time and patience,
Matthew
Click to expand...
Click to collapse
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Tulsadiver said:
Of that I do not know. You really should go ahead and flash the entire firmware. You need to open the flash-all.bat and remove the -w or it WILL wipe your data.
Click to expand...
Click to collapse
Tulsadiver said:
Yes, you must unlock the bootloader...you are on Verizon and I am unfamiliar with their procedure and even if the bootloader is unlockable. You had better talk to someone on a Verizon phone.
Click to expand...
Click to collapse
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
w144mjb said:
On Android source I am reading that unlocking the bootloader requires a full wipe.
https://source.android.com/source/running#unlocking-the-bootloader
Please advise.
Thank you,
Matthew
Click to expand...
Click to collapse
That is true.
If you take it to a Verizon store and explain the situation they might be able to help.
Tulsadiver said:
That is true.
Click to expand...
Click to collapse
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
w144mjb said:
Ok, good to know.
The only reason for this thread is to explore data recovery options, not to fix the boot loop.
Thank you,
Matthew
Click to expand...
Click to collapse
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Tulsadiver said:
I understand but my stepson has worked for every Carrier and they have access to software that might help. You already have a phone coming in so no skin off their nose.
Click to expand...
Click to collapse
I'll give Verizon technical support a call tonight (or a few, as necessary) and update you after.
Thank you,
Matthew
toknitup420 said:
I'm pretty sure you're SOL if you can't get it to boot to system. I don't think you can pull the data off the device without being in system. Even if you can it would be encrypted. So you wouldn't be able to do anything with it. Have you tried to boot in safe mode. If you get it to boot up in safe mode then you can pull the data off with no issues.
Click to expand...
Click to collapse
It will stay on for about 10 seconds in Safe mode.
w144mjb said:
It will stay on for about 10 seconds in Safe mode.
Click to expand...
Click to collapse
Safe mode only runs stock apps so if you are still boot looping in safe mode it's unlikely an app is causing your problem. I'm not sure what you mean when you say you didn't have coverage to back up your photos in Google Photos --i thought all Pixel phones came with unlimited original quality photo backup as long as the photos were uploaded from your phone. At this point I don't think you can recover your photos unless you find a way to fix the boot loop. Your boot loop where it didn't happen immediately after the update and it allows you into safe mode briefly sounds kind of unusual and might be the result of a hardware problem on your phone rather than a software issue. Have you tried booting the phone up while it is plugged into a wall outlet to see if that makes any difference? Some people with boot loop issues on the Pixels have reported that allowing the battery to completely run down until the phone is dead and then plugging the phone into a wall outlet allowed them to boot up normally. If you try that maybe you will get lucky but your options are very limited at this point.
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Psicovirus said:
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Click to expand...
Click to collapse
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Psicovirus said:
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Click to expand...
Click to collapse
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Nicktheprofessor said:
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Click to expand...
Click to collapse
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Psicovirus said:
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Click to expand...
Click to collapse
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Nicktheprofessor said:
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Click to expand...
Click to collapse
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Psicovirus said:
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Click to expand...
Click to collapse
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Nicktheprofessor said:
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Click to expand...
Click to collapse
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Psicovirus said:
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Click to expand...
Click to collapse
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Nicktheprofessor said:
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Click to expand...
Click to collapse
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Psicovirus said:
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Click to expand...
Click to collapse
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Nicktheprofessor said:
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Click to expand...
Click to collapse
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Edit2: Seems like i screwed up stalling stock recovery on top of twrp, sahme on me. How can i short the volume down button?
Psicovirus said:
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Click to expand...
Click to collapse
Reboot to recovery, use adb to sideload the OTA.
Reply to edit2: open it up, find the leads on the circuit board that go up to the vol down circuit breaker, use two needles and insert them into the solder where the breaker connects and while crossing the needles so they connect push power.
OR, fix the broken breaker, most of the time it's just a broken off brass dome that needs realigning, you'll need to fixate it which is just a needle's head worth of superglue on one side and a soldering on the other side (reflowing by heating the dome with a soldering iron usually works).
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Nicktheprofessor said:
Reboot to recovery, use adb to sideload the OTA.
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Click to expand...
Click to collapse
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Psicovirus said:
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Click to expand...
Click to collapse
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Nicktheprofessor said:
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Click to expand...
Click to collapse
Im trying to do that, i already have the phone open, sewing needles will do?
Psicovirus said:
Im trying to do that, i already have the phone open, sewing needles will do?
Click to expand...
Click to collapse
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Nicktheprofessor said:
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Click to expand...
Click to collapse
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Psicovirus said:
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Click to expand...
Click to collapse
You can use a q tip and some acetone to clear eventual lacquer from the solder points but the thing is, it's probably the emmc that is shot.
Your emmc obviously doesn't accept what the recovery the LGUP wrote to it. If it did, you'd be flashing the OTA right now. Why? I have no idea, I'd need to take the phone to the lab to examine what caused the degradation and even then I probably couldn't tell you much more about the actual cause.
And don't worry about it, your case is interesting and not easy to solve by simply doing a search, you weren't an arse about anything either and that is unusual and welcome.
Please help me, I’ve hardbricked my oneplus 7t. It’s stuck in fastboot mode and pressing the power button brings it back to that very same screen. How do I fix it?
I can’t find a file nor a guide on how to restore this phone. I’m in desperate need of help.
I’d be forever grateful if someone can help me. Thanks
What did you do to get bricked?
Sent from my ONEPLUS A6013 using Tapatalk
xRogerxC said:
What did you do to get bricked?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I’ve tried to install twrp which worked but for some reason I couldn’t root it as it said /system, /vendor and /package couldn’t be mounted. So I tried to restore and installed the stock recovery from https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961 But it didn’t work. This led to my phone being hard bricked. It’s stuck on the fast boot menu. I can’t find a mega unbrick guide like the other devices to fix it.
Please help!
Is there an msmtool like for the other oneplus devices to fix my oneplus 7T?
How2Kritin said:
Please help me, I’ve hardbricked my oneplus 7t. It’s stuck in fastboot mode and pressing the power button brings it back to that very same screen. How do I fix it?
I can’t find a file nor a guide on how to restore this phone. I’m in desperate need of help.
I’d be forever grateful if someone can help me. Thanks
Click to expand...
Click to collapse
Did you try connecting it to the PC and run the command in fastboot mode
Fastboot reboot
?
vicky2131 said:
Did you try connecting it to the PC and run the command in fastboot mode
Fastboot reboot
?
Click to expand...
Click to collapse
I did, it just brought me back to that same screen.
If you just got the phone in India there's a good chance Oneplus service might just replace it. Just tell them you got a software update and this happened.
Soul_reaper121 said:
If you just got the phone in India there's a good chance Oneplus service might just replace it. Just tell them you got a software update and this happened.
Click to expand...
Click to collapse
Oneplus service as in a physical store or the one online?
How2Kritin said:
Oneplus service as in a physical store or the one online?
Click to expand...
Click to collapse
A physical store might be much better https://www.oneplus.in/support/service-center you can check from this site depending on your location
Soul_reaper121 said:
A physical store might be much better https://www.oneplus.in/support/service-center you can check from this site depending on your location
Click to expand...
Click to collapse
Thanks for the advice but all I have in my hometown is one service centre which isn’t even a oneplus exclusive service centre according to that website. Do you think they would understand what happened to my device, let alone fix it?
Edit: I’ve bought this device off of amazon yesterday.
If you got it online, you can maybe ask for replacement
How2Kritin said:
Thanks for the advice but all I have in my hometown is one service centre which isn’t even a oneplus exclusive service centre according to that website. Do you think they would understand what happened to my device, let alone fix it?
Edit: I’ve bought this device off of amazon yesterday.
Click to expand...
Click to collapse
Ask for replacement on Amazon. Say it randomly turned off and wont start up. They might ask you to boot in recovery say nothing happens and they will send a replacement.
jesrani said:
If you got it online, you can maybe ask for replacement
Click to expand...
Click to collapse
What do I ask for a replacement for though? Item defective or doesn’t work? How do I make them believe me?
Soul_reaper121 said:
Ask for replacement on Amazon. Say it randomly turned off and wont start up. They might ask you to boot in recovery say nothing happens and they will send a replacement.
Click to expand...
Click to collapse
Do I have to call them up? Or is there another way?
Soul_reaper121 said:
Ask for replacement on Amazon. Say it randomly turned off and wont start up. They might ask you to boot in recovery say nothing happens and they will send a replacement.
Click to expand...
Click to collapse
Update, I’ve requested for an inspection service and it is going to happen after 24 hours from now. They’ve said that if the technician recommends to replace the device, a replacement will happen. However, if someone could provide me the msstool file for oneplus 7T, that would be GREATLY appreciated. Thanks a lot!
How2Kritin said:
Update, I’ve requested for an inspection service and it is going to happen after 24 hours from now. They’ve said that if the technician recommends to replace the device, a replacement will happen. However, if someone could provide me the msstool file for oneplus 7T, that would be GREATLY appreciated. Thanks a lot!
Click to expand...
Click to collapse
What do you mean for hardbricked? The bootloader is unlocked? You are able to enter in TWRP mode?
mauronofrio said:
What do you mean for hardbricked? The bootloader is unlocked? You are able to enter in TWRP mode?
Click to expand...
Click to collapse
Is not hardbricked
He is just stuck on fastboot...
He can flash a stock fastboot img
cultofluna said:
Is not hardbricked
He is just stuck on fastboot...
He can flash a stock fastboot img
Click to expand...
Click to collapse
actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this.
mauronofrio said:
actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this.
Click to expand...
Click to collapse
Super partition???
Is not an A/B partition device?
How2Kritin said:
I’ve tried to install twrp which worked but for some reason I couldn’t root it as it said /system, /vendor and /package couldn’t be mounted. So I tried to restore and installed the stock recovery from https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961 But it didn’t work. This led to my phone being hard bricked. It’s stuck on the fast boot menu. I can’t find a mega unbrick guide like the other devices to fix it.
Please help!
Click to expand...
Click to collapse
How2Kritin said:
Please help me, I’ve hardbricked my oneplus 7t. It’s stuck in fastboot mode and pressing the power button brings it back to that very same screen. How do I fix it?
I can’t find a file nor a guide on how to restore this phone. I’m in desperate need of help.
I’d be forever grateful if someone can help me. Thanks
Click to expand...
Click to collapse
Can you try this:
https://forum.xda-developers.com/oneplus-7t/how-to/stock-fastboot-flashable-images-oneplus-t3977623