Related
closed
Read this whole thread. THE WHOLE THING. Preferably thoroughly.
edited
AJThePwnapple said:
Even though I have a factory cable, do you want me to go into fastboot using your method?
I tried flashing the images but my computer doesn't recognize the device (can't install otter2-prod-04) and stays at <waiting for device>. Will it be different using your method?
Sorry if I come off a bit noobish, I'm brand new to this.
Click to expand...
Click to collapse
you need the drivers (should have been mentioned on that thread.)
If you have a fbcable, use it. on windows, device manager, uninstall the current driver if there is any, and use KFU to install the fastboot driver. (only use kfu for the driver, don't do anything else.)
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
AJThePwnapple said:
Nevermind, I resolved the problem. It was much easier than I thought, after hours of pulling my hair out.
I now have cm10.1 on my kindle.
Thanks so much anyway.
Click to expand...
Click to collapse
No problem, i'm happy to help
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Same here...
obsolete1 said:
I had a similar problem when I did mine. (forgot to transfer the rom before wiping)
I could boot into TWRP so i just changed the permissions of the download folder and pushed the rom over from my PC
Click to expand...
Click to collapse
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
yudanjah said:
I did the same. I wiped the rom when I was prepping for flash... I forgot I didn't have an SD card for the rom... Took me a few days to get ADB working on a Linux PC, then I sideloaded the rom.
Patience was key...
Click to expand...
Click to collapse
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
melvsmis ster said:
I deleted my data and so I can't install my ROM, my device read as Amazon Kindle Fire2 (I already installed CM10 and I'm just trying to update)and I can't sideload via TWRP since my device is not detected in adb, I can boot in fastboot, can I push the zip file from there? or any steps on how adb can recognize my device? I tried installing driver from KFU and updated my android SDK tools but still no devices found. I also tried to kill and restart adb and even amazon driver in extras via Android SDK.
Thanks for your help.
Click to expand...
Click to collapse
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
gnandez said:
I deleted my os with no backup and wiped all files but i could boot into twrp. I couldn't see my kindle or files when plugged into my computer. I booted into twrp and hit advanced then adb side load, I downloaded cm10 ROM into a new file named kindle on my computer renamed the ROM file cm, opened a command prompt in the file " kindle" and typed adb sideload cm.zip then enter and it pushed the file over rebooted and it was fixed. Not sure if anyone else recommended this, I did it about a month ago hope i didnt forget anything, good luck
Click to expand...
Click to collapse
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr then plug device to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
melvsmeister said:
My main problem with adb is it didnt recognize my device even i tried the ff:
-install driver from kfu
-install driver from amazon in extra via android sdk
-remove driver in device mngr tn plug devicle to auto install driver
My fastboot is working but i didnt know the syntax to flash. Im thinking can i flash zip to system partition then just copy it to sd card via twrp file mngr? Or extract rom from zip then flash boot.img but im worried that twrp might be overwrtten?
Click to expand...
Click to collapse
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
gnandez said:
Sorry, I posted that because I'm just learning fast boot and adb and I looked for another way.. So I used the cmd prompt on windows to push my ROM onto my kindle sorry if I gave the impression I could help with fastboot. our problems seemed the same so I thought another way could help
Click to expand...
Click to collapse
I guess I'm missing some steps here or maybe I need to do something to make it work since my adb is not detected in TWRP but I can have it if I let it boot to blue kindle logo. I'm still having a hard time in pushing ROM due to "No space left on device" error and even though I can push gapps I can't find it in TWRP. I'll just wait for someone who might had the same issue and have other solution to resolve this problem. Thanks for your help!:good:
Hi there,
First I have installed CWM with the method I had to use the codes "adb reboot bootloader"... and so on and It worked perfectly.
I wanted to install the Envi ROM and on the tutorial there was said I first should install the Base ROM and then after restarting I should install the Envi ROM. After installing the Base ROM my CWM was gone. Now I can't install it anymore. I tried the following install methods:
-The one I've mentioned already <- Doesnt work because my PC says it does not know the command abd
-The install.bat method <- Does not work because my phone does not get recognized, despite I have all the drivers installed.
-The RecoverX method <- Does not work because my phone does not get recognized, despite I have all the drivers installed.
-The RecoverX app <- The says that installing CWM worked normally, but still I have no CWM
-The install.bat method directly on my phone <- SManager does not run the .bat even I ran it with the proper rights and adjustments
domiankrey said:
Hi there,
First I have installed CWM with the method I had to use the codes "adb reboot bootloader"... and so on and It worked perfectly.
.....
-The one I've mentioned already <- Doesnt work because my PC says it does not know the command abd
...
Click to expand...
Click to collapse
Did You try flashing a kernel with pre installed recovery? You can flash it using fastboot directly or flashtool.
Also, the command is adb, not "abd". Plus if windows doesn't recognize adb command, then the adb.exe is not in the folder from where You are running the command prompt from.
Mirhawk said:
Did You try flashing a kernel with pre installed recovery? You can flash it using fastboot directly or flashtool.
Also, the command is adb, not "abd". Plus if windows doesn't recognize adb command, then the adb.exe is not in the folder from where You are running the command prompt from.
Click to expand...
Click to collapse
How can I flash a Kernel with a pre Installed Recovery
Where do I get the adb.exe?
domiankrey said:
How can I flash a Kernel with a pre Installed Recovery
Where do I get the adb.exe?
Click to expand...
Click to collapse
You can install the DoomKernel, it has pre installed recovery. You can flash it via flashtool fastboot. But do note, You have to be on stock ROM.
adb.exe is usually in the flashing files.
Mirhawk said:
You can install the DoomKernel, it has pre installed recovery. You can flash it via flashtool fastboot. But do note, You have to be on stock ROM.
adb.exe is usually in the flashing files.
Click to expand...
Click to collapse
I have my phone connected in fastboot mode and the fastboot.exe and the kernel are in the same directory.
When I type: fastboot flash boot kernel.elf it only says "waiting for device"...
domiankrey said:
I have my phone connected in fastboot mode and the fastboot.exe and the kernel are in the same directory.
When I type: fastboot flash boot kernel.elf it only says "waiting for device"...
Click to expand...
Click to collapse
To connect Your phone in fastboot, You have to switch off Your phone. Then press & hold volume up and then connect the phone to Your PC.
Mirhawk said:
To connect Your phone in fastboot, You have to switch off Your phone. Then press & hold volume up and then connect the phone to Your PC.
Click to expand...
Click to collapse
I know that and I did that, but still my device cannot be detected.
I started Ubuntu (Live CD) installed adb und fastboot and tried it there... same result?
Is something wrong is my phone?
I don't think the drivers have been installed properly. Install fastboot and flash mode drivers from flashtool, it has drivers in it's folder. Else if even that doesn't work, install "Sony Update Service", and it will install required drivers.
Edit: I'm giving You instructions for Windows, are You using Ubuntu or was that just a trial?
Mirhawk said:
I don't think the drivers have been installed properly. Install fastboot and flash mode drivers from flashtool, it has drivers in it's folder. Else if even that doesn't work, install "Sony Update Service", and it will install required drivers.
Edit: I'm giving You instructions for Windows, are You using Ubuntu or was that just a trial?
Click to expand...
Click to collapse
I am using Windows. I installed from flashtool and I did not work, I am gonna try Sony Update Service now.
I tried Ubuntu because somebody said me that Ubuntu will detect all the drivers automaticly and there would be no detection problem...
Edit: After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?
Why did it not work on my phone with smanager?
domiankrey said:
I am using Windows. I installed from flash tool and I did not work, I am gonna try Sony Update Service now.
I tried Ubuntu because somebody said me that Ubuntu will detect all the drivers automatically and there would be no detection problem...
Edit: After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?
Why did it not work on my phone with s manager?
Click to expand...
Click to collapse
I suppose your phone is Xperia S.
If you have unlocked the boot loader , then Sony Official Softwares wont work. If your boot loader is still locked and this error is occurring then its mistake from your side.
I guess by Base ROM you meant official ROM. So if you were on official ROM, did you check for Root Privileges, Busy Box is installed etc ??
Im using Xperia Ion so the steps might be different but results all are same.
Try different methods, it will work.
Captain Droid said:
I suppose your phone is Xperia S.
If you have unlocked the boot loader , then Sony Official Softwares wont work. If your boot loader is still locked and this error is occurring then its mistake from your side.
I guess by Base ROM you meant official ROM. So if you were on official ROM, did you check for Root Privileges, Busy Box is installed etc ??
Im using Xperia Ion so the steps might be different but results all are same.
Try different methods, it will work.
Click to expand...
Click to collapse
By Base Rom I mean the following; I wanted to use the Envi Rom and for this Rom a Base Rom should be installed first.
I have unlocked Bootloader. Busybox is installed and Root Priviliges are given. Before installing the Base ROM I used the APP "Smanager" and I ran the install.sh with the app and then the CWM was there. But now that doesnt work anymore and DeliverX does also not work.
And all methods which require connection to PC won't work because those methods say my device is not detected or connected. I installed CWM on my phone and on other phones several times and never I had thode problems...
domiankrey said:
... After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?...
Click to expand...
Click to collapse
Do one thing, check Your Device Manager. Disconnect Your phone, Open Device Manager, then connect Your phone again. See if the Device Manager gets refreshed. If it does, Your device is being connected to the PC. Then check for Xperia S or anything related to Sony under "Other Devices" or other similar areas. Then right click on it to install drivers.
Mirhawk said:
Do one thing, check Your Device Manager. Disconnect Your phone, Open Device Manager, then connect Your phone again. See if the Device Manager gets refreshed. If it does, Your device is being connected to the PC. Then check for Xperia S or anything related to Sony under "Other Devices" or other similar areas. Then right click on it to install drivers.
Click to expand...
Click to collapse
I just did that.
My phone is getting showed under "Tragbare Geräte" which means portable devices. When I right click on it says:
-Update drivers
-Deactivate
-Uninstall
-Looking for changed hardware
-Properties
If I click on Update drivers the message shows, that the best driver is already installed.
domiankrey said:
I just did that.
My phone is getting showed under "Tragbare Geräte" which means portable devices. When I right click on it says:
-Update drivers
-Deactivate
-Uninstall
-Looking for changed hardware
-Properties
If I click on Update drivers the message shows, that the best driver is already installed.
Click to expand...
Click to collapse
There should be a device like the highlighted one in attachment.
Mirhawk said:
There should be a device like the highlighted one in attachment.
Click to expand...
Click to collapse
This is how it looks on my PC.
Since (I was told in an other Android Forum it is like this) that on Ubuntu, Ubuntu recognizes my phone automaticly and still I installed the drivers there and it didnt not work and since neither RecoverX on my phone nor smanager on my phone dit install CWM I think the problem is my phone not the PC...
domiankrey said:
This is how it looks on my PC.
Since (I was told in an other Android Forum it is like this) that on Ubuntu, Ubuntu recognizes my phone automaticly and still I installed the drivers there and it didnt not work and since neither RecoverX on my phone nor smanager on my phone dit install CWM I think the problem is my phone not the PC...
Click to expand...
Click to collapse
Could You translate what the yellow mark text is? I think the device is recognized wrongly or wrong drivers were installed for it. Unfortunately, I don't know much about Ubuntu.
Mirhawk said:
Could You translate what the yellow mark text is? I think the device is recognized wrongly or wrong drivers were installed for it. Unfortunately, I don't know much about Ubuntu.
Click to expand...
Click to collapse
What do you mean with yellowk mark text? I see no yellow text...
If you mean the 3 devices which have a yellow sign:
- Ethernet Controller should be clear.
- Teredo Tunneling Pseudo-inferface - I do not know what that is.
- Basissystemgerät - means somehting like basic system device
With other ROMS I was able to install a CWM from my phone (with the deliverx app or a script manager app), but for this rom this doesnt work anymore.
So is there a way to install an other ROM without CWM (and when I have this ROM I would try if installing CWM directly with an app works again)?
domiankrey said:
With other ROMS I was able to install a CWM from my phone (with the deliverx app or a script manager app), but for this rom this doesnt work anymore.
So is there a way to install an other ROM without CWM (and when I have this ROM I would try if installing CWM directly with an app works again)?
Click to expand...
Click to collapse
Unfortunately Your device is not being detected as an adb device. The problem would be solved if somehow it is detected in adb or if You are able to install recovery from cell. I will try to check out more. Say, did You try the goo manager app, twrp manager or rom maanager to install recovery?
Mirhawk said:
Unfortunately Your device is not being detected as an adb device. The problem would be solved if somehow it is detected in adb or if You are able to install recovery from cell. I will try to check out more. Say, did You try the goo manager app, twrp manager or rom maanager to install recovery?
Click to expand...
Click to collapse
I will Try Goo and TWRPG Manager. Rom Manager does not work with Xperia S I already tried it.
EDIT:
1. Goo Manager does not work. I installed the Open Recovery.img and then I tried to install the ROM (eXistenZ V2 Black) but it only restarts my phone <- Does not work
2. TWRPG Manager does not even the TWRPG Recovery.
3. Previously I used this App to install CWM and it worked. Now I used the App and the App said installed CWM worked but There is no CWM on my phone (or it can't get started neither manually by pressing up nor automatically with an App which reboots me into CWM). <-Does no work.
4. On other time I used this App to run the cwm-install.ch on my phone. It worked and CWM was on my phone. Now the script does not run and therefore CWM also cannot be installed with this method. <- Does not work.
5. After all that, today I tried to install an official Rom with Sony PC Companion (and then starting from 0 with an other ROM, to try all the other stuff again) but It says I cannot install the official ROM Update. because, I do not have the official ROM installed, <- Does not work
I dont know what to do anymore.
hello,
after i failed to root my phone
everytime i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
can you please help me !!
if someone would like to help me .. i can open teamviewer and he can do it for me ..
thx
zsnorow said:
hello,
after i failed to root my phone
everytime i try to put it in recovery mode it goes back to fastboot mode ..
even if i tried to flash a recovery on it , it would boot to fastboot mode
even when trying to install a official htc software update it just boots into fastboot ..
now i want to get it back to stock..
can you please help me !!
if someone would like to help me .. i can open teamviewer and he can do it for me ..
thx
Click to expand...
Click to collapse
If you are able to boot into fastboot, search the latest TWRP and flash it via adb. Connect your device while in fastboot mode and see if it recognize it.
If it does put the recovery file you have downloaded on your desktop and open a command window, press shift and right click at the same time and click on Open command window here.
Type adb devices, if you see a serial number go on and type adb reboot bootloader, then type fastboot flash recovery [ the name of the recovery file you have just downloaded ]
You can do this just by powering on your phone, no need to be already in fastboot mode, just follow the commands.
Press shift and right click : open command window here : adb devices : adb reboot bootloader : fastboot flash recovery [ the name of the recovery file you have just downloaded, do not forget the .img extension ]
fastboot reboot
Once you have a working TWRP you can flash your corresponding backup and go back to stock. The backup will be flashed from TWRP, search for instructions.
XSL-FO said:
If you are able to boot into fastboot, search the latest TWRP and flash it via adb. Connect your device while in fastboot mode and see if it recognize it.
If it does put the recovery file you have downloaded on your desktop and open a command window, press shift and right click at the same time and click on Open command window here.
Type adb devices, if you see a serial number go on and type adb reboot bootloader, then type fastboot flash recovery [ the name of the recovery file you have just downloaded ]
You can do this just by powering on your phone, no need to be already in fastboot mode, just follow the commands.
Press shift and right click : open command window here : adb devices : adb reboot bootloader : fastboot flash recovery [ the name of the recovery file you have just downloaded, do not forget the .img extension ]
fastboot reboot
Once you have a working TWRP you can flash your corresponding backup and go back to stock. The backup will be flashed from TWRP, search for instructions.
Click to expand...
Click to collapse
can you sir please give me a link for the TWRP and teach em how to flash it ? it would be much appreciated..
zsnorow said:
can you sir please give me a link for the TWRP and teach em how to flash it ? it would be much appreciated..
Click to expand...
Click to collapse
http://teamw.in/project/twrp2 and click on the upper right Get TWRP for your device.
Choose your device recovery and download the adb version. That is the .img
Once you have downloaded TWRP put it on your desktop.
Connect your device with your laptop/pc with the unknown sources checked also the usb debugging checked.
Move your mouse over a free space on your desktop, click once just to be sure there is no app or file clicked.
Then press shift and keep it pressed while you right click your mouse.
Press open command window here
in that command window type : adb devices
if you see a serial number type : adb reboot bootloader
then type : fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot reboot
openrecovery-twrp-2.8.1.0-m8 : This is an example, you will write the name of your recovery but it should be pretty much the same.
Good luck.
Are you familiar with
adb/fastboot commands?
It's a bad idea to mess with your phone if you don't know how to repair it if something goes wrong
spinninbsod said:
It's a bad idea to mess with your phone if you don't know how to repair it if something goes wrong
Click to expand...
Click to collapse
I agree with you but maybe he has done some reading and has fixed it sense he hasn't given us an update
ive tried everything
jball said:
I agree with you but maybe he has done some reading and has fixed it sense he hasn't given us an update
Click to expand...
Click to collapse
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
zsnorow said:
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
Click to expand...
Click to collapse
What guides/tutorials have you followed to get to the point you are at now.I'm sure someone wouldn't mind teamviewing the whole process but what would you learn by having that done .
From start to finish what have you used?
i honestly cant remember everything i did
jball said:
What guides/tutorials have you followed to get to the point you are at now.I'm sure someone wouldn't mind teamviewing the whole process but what would you learn by having that done .
From start to finish what have you used?
Click to expand...
Click to collapse
i cant remember everything i did but im sure that i followed the tutorials that are on youtube/XDA/android forums correctly
zsnorow said:
i tried everything to fix my phone like sideloading (my phone doesent get recognised when in sideload mode) , pushing a ROM and the flashing it with TWRP (it says that its completed but it doesent work)..
what else can i do .. cant someone do it for me via teamviewer ..
Click to expand...
Click to collapse
You say "pushing a ROM" with what?
You don't push a ROM with TWRP you just flash it.
Or are you talking about pushing the ROM with fastboot?
If you have TWRP than download a stock backup and flash it.
Take a long look at my profile man and if you look just right you will see I've done and asked some stupid things in my travels here on XDA.I can tell you I remember every phone and ridiculous thing I've done to each of them,I still feel crunchy when I think of the mistakes.
We really need more info about the full process.please I'm not trying to offend you and I'm trying to help
zsnorow said:
i cant remember everything i did but im sure that i followed the tutorials that are on youtube/XDA/android forums correctly
Click to expand...
Click to collapse
If you can't remember what you did, or at least even try to list in detail the steps you did as best you can remember; it makes it very hard for anyone to help.
Saying you followed some tutorials on an entire website (3 websites actually) doesn't tell us jack, and isn't any better than telling us nothing.
Its not even clear the current condition of the phone. Your OP says TWRP doesn't work, then a later post says you are trying things with TWRP, so presumably you have TWRP. But since you never stated that, we can only guess.
What happens when you try to adb push or sideload? What error messages, does it make the phone reboot, stuck on boot screen, etc?
TWRP working? Bootloader is unlocked? If yes to both of those, you should be able to just adb push a ROM, or put one on removable SD with a card reader attached to your computer. Than flash the ROM in TWRP.
same thing happened with me but i remember what i did
redpoint73 said:
If you can't remember what you did, or at least even try to list in detail the steps you did as best you can remember; it makes it very hard for anyone to help.
Saying you followed some tutorials on an entire website (3 websites actually) doesn't tell us jack, and isn't any better than telling us nothing.
Its not even clear the current condition of the phone. Your OP says TWRP doesn't work, then a later post says you are trying things with TWRP, so presumably you have TWRP. But since you never stated that, we can only guess.
What happens when you try to adb push or sideload? What error messages, does it make the phone reboot, stuck on boot screen, etc?
TWRP working? Bootloader is unlocked? If yes to both of those, you should be able to just adb push a ROM, or put one on removable SD with a card reader attached to your computer. Than flash the ROM in TWRP.
Click to expand...
Click to collapse
firstly i unlocked my bootloader via htcdev website then i installed twrp recovery successfully and then when i tried to root my phone by installing two zip files (mm-su-boot. & beta super su) i installed these two files and then tried to reboot my phone it opened in fastboot mode only . then i read here about the revolution hd rom installed it successfully but it does not reboot . help needed
farhanakhtar39 said:
firstly i unlocked my bootloader via htcdev website then i installed twrp recovery successfully and then when i tried to root my phone by installing two zip files (mm-su-boot. & beta super su) i installed these two files and then tried to reboot my phone it opened in fastboot mode only . then i read here about the revolution hd rom installed it successfully but it does not reboot . help needed
Click to expand...
Click to collapse
Your device is M8 dual SIM .. mm-su-boot is for M8 single SIM, won't work on your device.
Install custom ROM with support for Dual SIM or restore your stock ROM backup
please can you provide any link of the rom for dual sim addition
farhanakhtar39 said:
please can you provide any link of the rom for dual sim addition
Click to expand...
Click to collapse
Not so sure,
if Sense ROM - https://forum.xda-developers.com/htc-one-m8/development/rom-sense-6-12-401-4-mra58k-stock-t3296066
maybe S.ROM too has dual SIM support, you need to ask in their thread
https://forum.xda-developers.com/ht...the-worlds-first100-m9-port-m8upload-t3064838
if non-Sense ROM
CM13 ROM - https://forum.xda-developers.com/htc-one-m8/development/rom-cyanogenmod-13-0-experimental-t3259068
Nougat ROM -
https://forum.xda-developers.com/showthread.php?t=2753248
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
https://forum.xda-developers.com/ht...cyanogenmod-14-1-htc-one-m8-dual-sim-t3507192
There are a few more that support Dual SIM but you have to check & ask in their development thread as I'm not familiar with most of the available custom ROMs .. I don't try most of them
Thnks
Thanks buddy it worked
cm 13 worked for me !
God bless you
If I may jump in on this post and ask some advise my m8s is only booting to fastboot screen it has never been flashed, have tried recovery: nothing just goes back to fastboot, also wiped cache and factory reset: same result..... It has done this 2 times previous but only after restarting phone, usually repeatedly doing reboot it loads but it's been 2 days now and still only getting fastboot screen...plez help
My phone is having similar issues
Stanna16 said:
If I may jump in on this post and ask some advise my m8s is only booting to fastboot screen it has never been flashed, have tried recovery: nothing just goes back to fastboot, also wiped cache and factory reset: same result..... It has done this 2 times previous but only after restarting phone, usually repeatedly doing reboot it loads but it's been 2 days now and still only getting fastboot screen...plez help
Click to expand...
Click to collapse
I recently decided to root and install a custom rom on my old stock sprint HTC one m8. I unlocked the boot loader via HTC Dev website. I then flashed the TWRP recovery. Since doing the latter step, it's been booting into fast boot all the time! Did you ever figure out what was wrong with your phone?
pancho2009 said:
I recently decided to root and install a custom rom on my old stock sprint HTC one m8. I unlocked the boot loader via HTC Dev website. I then flashed the TWRP recovery. Since doing the latter step, it's been booting into fast boot all the time! Did you ever figure out what was wrong with your phone?
Click to expand...
Click to collapse
You only flashed TWRP onto the phone? Or did you root also?
Not nearly enough info to provide the proper help.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
What version TWRP?
What version SuperSU did you flash (if you got that far)?
Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!
Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.