so i bought this 1+1 with missing imei/baseband/sim. succeeded in restoring to stock 13 following this help :
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
but still no imei so followed this help page :
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Followed the part :
RUN THE flash-all.bat FILE FROM FASTBOOT AND YOU SHOULD BE CURED!!!
it this is when my phone never rebooted properly, it tried but seemed like it powered off the cmd window said waiting for phone for a long time and now will not power on.
did i not wait long enough?
i dont have a pix of the last thing i did but of the 2nd one is here
Related
Hey Guys,
I appreciate the time you're all taking to read this thread.
Earlier this year in March my OPO stopped working suddenly after a party which I thought was from water damage. The phone was working perfectly and after 30 minutes of using it the next day it stopped. Because of the lack of warranty options I dried my phone in a box of rice for a couple of weeks and the phone remained broken. The problem is that is does not stay on. When I turn the phone on in Safe Mode, it will continue to run as long as the Vol + / - buttons are pressed. Recently last month I tried to use the phone is it was working no problem at all. After maybe 2 weeks of constant usage (Charging, turning off, updating, etc...) the phone stopped working again!
TL;DR
- Phone constantly resets during "1+ Powered by android screen"
- Only stays on while Holding Both Volume buttons (Safe mode), turns off upon release.
- Stays on during Fastboot mode.
Tried many times to follow many different threads however can't seem to get it to work. I'm not sure if unlocking developer mode while running safe mode or not being able to boot outside of safemode is doing it.
Please lend me your aid!
Much appreciated
aykaylee said:
Hey Guys,
I appreciate the time you're all taking to read this thread.
Earlier this year in March my OPO stopped working suddenly after a party which I thought was from water damage. The phone was working perfectly and after 30 minutes of using it the next day it stopped. Because of the lack of warranty options I dried my phone in a box of rice for a couple of weeks and the phone remained broken. The problem is that is does not stay on. When I turn the phone on in Safe Mode, it will continue to run as long as the Vol + / - buttons are pressed. Recently last month I tried to use the phone is it was working no problem at all. After maybe 2 weeks of constant usage (Charging, turning off, updating, etc...) the phone stopped working again!
TL;DR
- Phone constantly resets during "1+ Powered by android screen"
- Only stays on while Holding Both Volume buttons (Safe mode), turns off upon release.
- Stays on during Fastboot mode.
Tried many times to follow many different threads however can't seem to get it to work. I'm not sure if unlocking developer mode while running safe mode or not being able to boot outside of safemode is doing it.
Please lend me your aid!
Much appreciated
Click to expand...
Click to collapse
Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img
Then flash the latest stock images with fastboot. Full instructions in section 8 of my guide thread.
Heisenberg said:
Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img
Then flash the latest stock images with fastboot. Full instructions in section 8 of my guide thread.
Click to expand...
Click to collapse
thanks for the post! trying it now.
many thanks Heisenberg for helping me out. The system.img isn't in the .zip file for the stock image. Following the step 8 in your tutorial, I can't get past the second last step when fastbooting the system.img
Any advice? I'm sure skipping one step would affect the overall solution.
Should I restart and download a new .zip or is there another solution.
Thanks
aykaylee said:
many thanks Heisenberg for helping me out. The system.img isn't in the .zip file for the stock image. Following the step 8 in your tutorial, I can't get past the second last step when fastbooting the system.img
Any advice? I'm sure skipping one step would affect the overall solution.
Should I restart and download a new .zip or is there another solution.
Thanks
Click to expand...
Click to collapse
The system.img should definitely be in the zip, download it again and check the md5 to make sure it didn't become corrupt during the download.
Heisenberg said:
Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then do this with fastboot:
Code:
fastboot erase persist
fastboot flash persist persist.img
Then flash the latest stock images with fastboot. Full instructions in section 8 of my guide thread.
Click to expand...
Click to collapse
Followed step by step hoping for a solution. Maybe i'm doing it wrong, but no errors come up when I'm doing these tutorials. The only thing is the same result of 1+ Powered by android screen.
If you have any other suggestions please keep them coming!
Thanks
aykaylee said:
Followed step by step hoping for a solution. Maybe i'm doing it wrong, but no errors come up when I'm doing these tutorials. The only thing is the same result of 1+ Powered by android screen.
If you have any other suggestions please keep them coming!
Thanks
Click to expand...
Click to collapse
And you erased and flashed the persist?
Hello, so recently I tried to fix my bootlooped Moto G 3rd gen(dual-sim, India) and made a mistake that has somewhat fixed my phone but the wifi doesn't work, there might be some undiscovered errors still, the whole story..
-The phone became bootlooped like I said above
-So I decided to flash stock rom for it, and looked up several guides on how to do it.
-Downloaded the correct rom, and connected the phone in recovery mode as I could still hold down power button while phone loops(switch on to logo-pause-black screen repeat...)
-After setting correct path for fastboot, I got the [FAILED ] REMOTE ERROR while flashing partition - the "gpt.bin file"
-So I decided to skip that and went on with rest of the given commands including all 6(number 0 to number 5) sparsechunks
-I received signed error for sparsechunks
-I continued upto reboot
After this the phone booted fine but wouldn't get past selecting wifi network phase of start setup screen
Somehow a repair guy I gave phone to fix got up to that with login details of account, and now the phone is functional but I can't manage to turn on the wifi, if I hit on it automatically slides back to off instantly.
Notes: After fastboot and the start phase issue I tried mfastboot with same rom files and went over all commands many times, with same error
: After the phone became functional I tried flashing process again with mfastboot and usb debugging enabled but received REMOTE ERROR at partition again and stopped there.
That's all so far, any advice or suggestion you could give is highly appreciated. Thanks for your time.
Same problem.
zarama12 said:
Hello, so recently I tried to fix my bootlooped Moto G 3rd gen(dual-sim, India) and made a mistake that has somewhat fixed my phone but the wifi doesn't work, there might be some undiscovered errors still, the whole story..
-The phone became bootlooped like I said above
-So I decided to flash stock rom for it, and looked up several guides on how to do it.
-Downloaded the correct rom, and connected the phone in recovery mode as I could still hold down power button while phone loops(switch on to logo-pause-black screen repeat...)
-After setting correct path for fastboot, I got the [FAILED ] REMOTE ERROR while flashing partition - the "gpt.bin file"
-So I decided to skip that and went on with rest of the given commands including all 6(number 0 to number 5) sparsechunks
-I received signed error for sparsechunks
-I continued upto reboot
After this the phone booted fine but wouldn't get past selecting wifi network phase of start setup screen
Somehow a repair guy I gave phone to fix got up to that with login details of account, and now the phone is functional but I can't manage to turn on the wifi, if I hit on it automatically slides back to off instantly.
Notes: After fastboot and the start phase issue I tried mfastboot with same rom files and went over all commands many times, with same error
: After the phone became functional I tried flashing process again with mfastboot and usb debugging enabled but received REMOTE ERROR at partition again and stopped there.
That's all so far, any advice or suggestion you could give is highly appreciated. Thanks for your time.
Click to expand...
Click to collapse
I have same problem. I can't use WiFi or Internet on other custom/Stock ROM. Not problem on nandroid backup.
Make sure you have the correct firmware files downloaded
Avinash Mali said:
I have same problem. I can't use WiFi or Internet on other custom/Stock ROM. Not problem on nandroid backup.
Click to expand...
Click to collapse
I was going to post how I fixed it but it slipped from my mind.
The flashing problem(Remote error) seems to be caused by the locked bootloader, which I only discovered after needing to root my phone following a guide to fix the wifi.
The thing is, a lot of people who have this problem seem to miss a file in the 'persist' folder of their root directory, see: http://forum.xda-developers.com/showthread.php?t=2619553
However for me it didn't fix the issue, mostly since the file isn't available for 3rd gen moto G, but with unlocked bootloader (see: http://theunlockr.com/2015/09/09/how-to-root-the-motorola-moto-g-3rd-gen/) I could flash other parts just fine (except gpt.bin still giving the same error) and it pretty much fixed my issue.
Hi all,
So my I decided to bring my old Oneplus One back to life by following some 'Unbrick Tutorials'. I've tried a couple but nothing seems to work.
So I followed this tutorial as last resort:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
Everything went like it's supposed to happen I guess. My cmd window gave me positive info (Things like: flashing recovery.img - okay... Sending packages etc. etc.) So I wanted to perform the final step -> reboot to recovery and all of a sudden my phone vibrates! yay!
But then it showed some nasty vertical stripes and it didn't boot in recovery at all. I don't see anything exept those lines. But my PC seems the recognize my OPO. When I launch fastboot my pc can find it.
But what do I do now!? How do I boot it normally and get rid of those vertical lines!? PLEASE HELP!!
Thank you for your time and effort in helping me! I'll donate a beer for the guy that helps me fix this issue!
Thread on OnePlus Forums: here
Are you sure it's not hardware damaged? "Bring to life" from what? What happened to it in the first place?
use wugfresh tool kit and go back to stock and start again and see if it fixes the issue may just been a bad flash of the recovery
Hi,
I just followed the steps on these two web pages to get my device modded:
https://android.gadgethacks.com/how-to/root-your-google-pixel-pixel-xl-0174670/
https://android.gadgethacks.com/how-to/install-twrp-custom-recovery-your-pixel-pixel-xl-0175163/
On step 10 of the second link I followed the steps to root my Pixel phone but at the end I saw an option on my TWRP that said you can install TWRP app as a system app to get latest updates. I said okay and done that. Then my device started restarting approximately 2 times followed by this message: "Your device software can't be checked for corruption. Please lock the bootloader. Press power to continue." I can't turn off the phone because it will lock the bootloader.
What should I do to fix this problem?
Here's a Google's response to this issue: https://support.google.com/nexus/answer/6185381?hl=en-GB
Update: I decided to hold power button to turn off the phone. The phone restarted automatically and this time I get "pause boot" then "continue". Then it goes in a boot loop.
Update 2: I managed to get to the bootloader mode via power + vol down.
That screen is standard during boot up when your device is not locked and it is nothing to worry about. If your device is boot looping and you can't get it sorted out you can download stock images from google and run the flash-all command to flash everything again.
ohioa6driver said:
That screen is standard during boot up when your device is not locked and it is nothing to worry about. If your device is boot looping and you can't get it sorted out you can download stock images from google and run the flash-all command to flash everything again.
Click to expand...
Click to collapse
Hi and thanks for the response. You mean something like this or exactly this: https://www.youtube.com/watch?v=5Ewo1ou_53o
Yep just like that video. Be aware that it will wipe all of your user data too unless you remove the -w flag from inside flash-all.bat.
ohioa6driver said:
Yep just like that video. Be aware that it will wipe all of your user data too unless you remove the -w flag from inside flash-all.bat.
Click to expand...
Click to collapse
I just tried that tutorial but it didn't work. :/
Should I follow the steps @death2all110 gave on here: https://forum.xda-developers.com/pixel-xl/help/bootloop-t3498140
Power and Vol Up got me to recover mode and I managed to wipe data and factory reset but my phone is still in a loop + that orange message.
My phone is fixed now. I downloaded 7.1.2 (N2G47O) from the official Google website and followed the steps of @death2all110 . Then I followed the tutorials again and this time I didn't install TWRP as a system app and my phone is successfully rooted.
Hello guys,
i am exhausted.
today i used my pixel like everyday, from one second to the other i turned off and immediately it turned on again.
i couldn´t get it started so i tried to install lineage os.
What i have done is: i took the device and pressed the vol down + power button. at my pc i (allready adb installed) fastboot devices, the phone answered. good, so far. i flashed the lineage recovery and started it. i wiped all the data and send the os .zip via usb to the phone. the shell said all worked good. i had to aplly the update in the recovery but after that the bootloop is still there.
What happens if i turn on the phone: google logo appears for one seconds, black screen. thats it. it´not a typical bootloop.
The next step was to download the OEM package from google and to install that by the included "flash-all.bat" file. that doesn´t worked too.
What information can i provide to you guys that you can help me finding a soloution?
You can find the result of "fastboot getvar all" in the attachment
Very big thanks in advance.
Best regards
morph163 said:
Hello guys,
i am exhausted.
today i used my pixel like everyday, from one second to the other i turned off and immediately it turned on again.
i couldn´t get it started so i tried to install lineage os.
What i have done is: i took the device and pressed the vol down + power button. at my pc i (allready adb installed) fastboot devices, the phone answered. good, so far. i flashed the lineage recovery and started it. i wiped all the data and send the os .zip via usb to the phone. the shell said all worked good. i had to aplly the update in the recovery but after that the bootloop is still there.
What happens if i turn on the phone: google logo appears for one seconds, black screen. thats it. it´not a typical bootloop.
The next step was to download the OEM package from google and to install that by the included "flash-all.bat" file. that doesn´t worked too.
What information can i provide to you guys that you can help me finding a soloution?
You can find the result of "fastboot getvar all" in the attachment
Very big thanks in advance.
Best regards
Click to expand...
Click to collapse
happened to me too. fix it?