Related
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
pgoelz said:
I've had a similar issue a couple times after doing something stupid (ADB or FASTBOOT could not detect the phone). The fix was to look in Windows Device Manager and make sure the phone really was detected and a driver installed. Windows would say that it could not find a driver but telling it to install manually did the trick..... as I recall there were a couple driver choices, so it might be trieal and error. Might not be the issue in your case since it does sound like the hardware has a problem, but worth looking into?
Paul
Click to expand...
Click to collapse
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
ItsMason said:
I've re-installed the drivers a couple of times now, and it doesn't seem to be fixing the problem.
I don't think it's a hardware problem, because I don't see what making a backup would do to the hardware of the phone (of course, I don't really know much about the hardware, so I might be wrong.) Thanks for the help, though!
Click to expand...
Click to collapse
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
exige34 said:
Hi, since you're communicating with the device via ADB and can boot to recovery, I'm pretty sure you can still do something about it. I've had this issue and I can recommend starting to read up on Ubuntu or some type of Linux with a decent user interface. It's easier for starters.
You see, if you don't detect the device via the 'fastboot devices' command, then you have one of two big problems:
a) drivers are messed up - it implies you uninstall everything from Device Manager related to ADB / Bootloader interface. After that, shut off the phone, connect your type-c usb cable, boot up the phone into bootloader and let it install the drivers again (I didn't have much success with this but I read others have. Worth a try)
b) something messed up deeper, as in device permissions. When I had the issue, I used Mint (a Debian distribution) and installed all the drivers via the command line there. After that, when I ran fastboot devices, I got something. It was my lost N5x showing with 'no permissions' and no serial ID. I ran 'sudo fastboot devices' and lo' and behold, I saw the device. After that, I just used sudo fastboot flash recovery/system/etc with it and that was it.
Click to expand...
Click to collapse
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
ItsMason said:
I think I've done goofed my nexus.
Yesterday, I made a backup of my phone, and then booted it up. Everything was working fine prior to the backup, but as soon as I booted it after making the backup, it got stuck on the google logo. I tried restarting it several times, but it's just been stuck in a bootloop ever since. I've tried numerous things, like formatting it, flashing factory images, and so on, but it turns out fastboot won't detect my device. ADB detects my device fine, but only in recovery. As far as I know, I don't have usb debugging enabled (since I formatted it). It currently has no OS since I formatted it. I've tried installing stock android since formatting it but it still gets stuck in a bootloop.
All my drivers are correct (I've re-installed them probably 10 times by now), and the images aren't corrupted (as far as I know).
I've run out of ideas, as I've been trying to figure this out for the past 2 days with no success. Any help would be appreciated.
Click to expand...
Click to collapse
Do you use 3.02.1. Twrp
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Code:
adb push "/path/to/rom.zip" /data/media
ItsMason said:
I made some progress: my device is now detected in fastboot. I have literally absolutely no clue what happened. I guess it was a bit of randomness or luck or something (maybe wacky and goofy). I've done some flashing - I've flashed system, boot, recovery, cache, data, and radio, but it's still stuck in a bootloop. I don't know what's going on it with it now, but it seems like I haven't made any progress with fastboot.
Click to expand...
Click to collapse
Good. I see you mention flashing system, boot, recovery, cache(?), data(?) and radio. What do you mean by flash cache&data? You mean you've cleaned it? Formatting data is not usually a thing you have to do to recover from a bootloop.
What ROM have you flashed? Are you flashing stock? It's important you give more details so I can help you.
Have you flashed vendor.img? If you have been on a ROM that had it's own vendor.img and you went back to stock, then the vendor.imgs are different enough to cause a bootloop.
If all and all fails, we just want to see your system running so I'd recommend drop everything you are doing and follow these steps:
1. Access recovery (make sure you're using v 3.0.2.2)
2. Tap Wipe - > Advanced Wipe - > And check:
Dalvik / ART Cache
System
Internal Storage
Cache
3. Go to -> Pixel ROM (7.1.1) Get V 3.0 which was just uploaded recently. Please note it comes preconfigured with Gapps so no need to get that
4. You have to unzip the archive and you will see all the necessary img files (includes boot/vendor which are critical for boot). I strongly recommend manually flashing them. You can open the flash-all.bat file with a .txt editor and just follow the steps there.
After you have finished these steps, you should be free of a bootloop. From there, it is your decision where you. Either stay on a stock ROM or flash safely and always remember that you can make a backup and flash that backup in case you bootloop.
Good luck.
EDIT
Decay3 said:
Since you mention ADB works fine from recovery, have you tried to adb push a rom zip, and then flash it from your recovery?
Click to expand...
Click to collapse
I think his problem is deeper than a /system error. I'm guessing the wrong boot/vendor is flashed for the ROM he is trying to install and trying to guess which ROM would work on his current config would take more time than just starting from a clean flash.
Thanks for the help guys, but I gave up. I contacted Google and they sent me a replacement. Sorry for kind of wasting time.
Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..
Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
premedicated said:
Hey all. Hopefully someone can provide a little assistance with this..
TLDR; Phone was fine, this morning it went into a bootloop. Tried restore which didn't work, tried wiping which didn't work, wipe everything and installed a new factory image and now it still won't boot and recovery is giving "no command" but I can still see everything with fastboot.
So a few months ago I rooted my Pixel Xl and flashed a "official" 8.1.0 ROM on it along with TWRP and Magisk. Everything was going fine and then about a week ago my phone shut off and wouldn't turn back on. I had to hold the power button about thirty seconds for it to come back. That was the only issue until this morning. This morning the same thing happened, the phone had shut off at some point last night while it was plugged in and this morning it was a black screen. Again, I held the power button down for about thirty seconds until it booted up, but this time a couple minutes after it booted, it shut back off again. Rinse and repeat and every time the time on was shorter and shorter until it just got to the Google boot screen and would freeze up and shut off.
After playing with it for a little while trying to figure out what was going on, I tried to do a factory wipe/reset. That didn't resolve anything. I booted back into TWRP and tried to do a restore, but about 80% of the way through it froze up. I restarted the device and tried restore again, but it froze up towards the end once more. So I tried doing a wipe, then a restore but only the first two boxes checked, system and something else.. It completed successfully, but was still boot looping just like before.
Then I thought maybe it was something internal and did a full wipe of everything.. Still no luck. Then I figured since there wasn't much to lose, I pushed the newest factory image to the phone using platform tools/fastboot.
Now what I get is when I try to start the phone it'll go to the Google logo, then restart, then do that once more and then it will go to a little screen with the Android on his back and an exclamation saying "No command", which I'm assuming is recovery mode since it does the same thing when I try to go there.
I can access fastboot still and all the system menus, I don't care about losing my data obviously and I just need my phone to work. Is there anything I can do?
In the bootloader my information is..
BL: 8996-012001-1808030001
Baseband: 8996-130181-1806061856
Product/Variant: marlin-US-PVT
Serial Number: HT68Hxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 32GB Samsung
DRAM: 4096MB Samsung LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is UNLOCKED
Click to expand...
Click to collapse
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB. Hook up your phone to the PC and boot into the bootloader on the phone by powering on while holding in Volume Down + power. In the folder where you have fastboot on your PC, hold down shift and right click the mouse and select open command prompt (or powershell, depending on Windows version). Type fastboot devices to make sure your phone is being seen by your PC. If it is, type fastboot erase system, after that runs type fastboot erase userdata, once that runs type fastboot erase system, and finally fastboot erase boot. Then type fastboot --set-active=b , and run the same commands on that slot. Then type fastboot reboot bootloader, and when it reboots to bootloader type in flash-all.bat . That should wipe everything properly on both slots and install the latest factory image. If that doesn't work then I would say there's definitely a hardware defect. Also if it doesn't work I would try a different port on your PC.
Phalanx7621 said:
Ok, so I'm assuming you have the latest factory image currently downloaded on your PC and extracted all the files to the same folder as fastboot/ADB.
Click to expand...
Click to collapse
Inside of the factory image file, once unzipped there is another zip file contained in there with the same name. Do I need to extract that as well since it has options such as boot.img, keymaster.img and several other .img files in it, or do you just extract the main files containing bootloader-marlin-8996-012001-1808030001.img, flash-all.bat, etc.?
Phalanx7621 said:
Then type fastboot --set-active=b , and run the same commands on that slot.
Click to expand...
Click to collapse
Awesome, thanks for the reply. Question though since i'm not entirely sure about the slots. Since it's already reading it as slot B, will I change the active to slot A at some point or will running those commands in slot B erase slot A, as I understand that it basically works in whatever slot is not active.
It should detect slot A by defualt, but as long as you run those commands for both slots you'll be wiping it clean. Keep in mind we aren't talking about TWRP, we're in fastboot. And no, once you extract the files from the zip you don't need to extract the other file inside of it. The flash-all command will read it and do the proper magic. Just make sure the extracted files are in the folder with fastboot/ADB.
Well, I followed it to a T with your first post and I made it further than before. I got it all the way to where it asked if I wanted to copy files and then it froze. Restarted and it made it to finding my sim before it restarted and then it makes it to a different point before restarting, which is further than I made it before, however it still hasn't made it all the way into the software, so I guess I'm pretty well screwed unless it's something with Slot A. But I'm pretty doubtful at this point.
Update: Now it won't make it past the Google logo anymore again...
Ok, so it still isn't working. I'm going to try flashing the 8.1.0 image in a bit and see if maybe that some how resolves it. Doubtful, but it's my last step before I go spend a thousand dollars buying a new phone..
A couple questions though, when I flash-all I'm getting a lot of "Archive does not contain 'xxxxx.xxx'" errors. Archive does not contain boot.sig, boot_other.img, dtbo.img, dt.img, odm.img, product.img, product-services.img, recovery.img (this one seems important..), super.img, system.sig, vbmeta.sig and vendor.sig are all missing from the archive. This normal?
Also, I can play around in bootloader and I could in TWRP before it was erased for hours with no reboot or anything, but once the OS starts to load or loads, that's when it freezes up and fails. If it was a hardware issue shouldn't it be restarting regardless of what I'm running under?
Just trying to expend all my options before spending more ludicrous amounts of time for a piece of hardware that can just die without reason.
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.
tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.
Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse
What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.
@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.