Related
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
albert_htc said:
Hi
Earlier I installed TWRP via Philz and that worked fine.
I then reset my phone and flashed Bigxie's Android L, again this worked fine.
I flashed the new radio for the same thread and that worked fine.
I then downloaded CF-Root from here:
http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Ran the Windows Batch file all seemed to go well. Bootloader was unlocked and the big red android appears on screen.
Phone booted back to TWRP, a script ran and then my phone started constantly booting the the TWRP screen.
All I'm getting is teamwin flashing up.
If I power off it goes back to this loop.
Any way I can get this working again ?
Not worried about any data.. I've got all I need backed up.
Thanks
Click to expand...
Click to collapse
dont use root toolkits.
flash the factory img via fastboot. then flash twrp again, flash a kernel that allows root, then flash the latest supersu.
Thanks for the reply.
Just want to claify to make sure I don't make it worse..
I've got the L image from Googles site, do I extract the factory.img from that ?
Then flash it using :
fastboot flash factory factory.img
Thanks
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
albert_htc said:
Think I may have made things worse..
I extracted the tgz file and while browsing double clicked the flash all batch file.
:silly: Not sure how the hell I clicked it twice.. but it's doing something.. .hopefully not killing my phone.
Any suggestions how I did myself out of this hole..
Click to expand...
Click to collapse
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
Found out how I've managed to double click.. The trackpad on my laptop is playing up.
I'll have to remember to use a USB mouse with it.
The phone has just rebooted and is coming back up.
Thanks for the advise.. looks like it's working.
I'll start a new thread with a couple of follow up questions.
Thanks
simms22 said:
i dont think hitting it twice will do anything. but you might have to flash the img files separate, as in the flash-all is giving some ppl issues.
Click to expand...
Click to collapse
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Jmurf said:
When doing this, is there any specific order to follow when flashing all the .img files separately? I am also getting errors stating recovery.sig and boot.sig are missing. Does installing separate also take care of this?
Click to expand...
Click to collapse
it appears that the flash-all is having issues and skipping. so by flashing them all individually, you will make sure to flash them all.
I recently tried a custom ColorOS Rom off here and then flashed a CM 44s backup through TWRP as I didn't like the custom ROM.
However I know have a few issues on 44s
1. Custom gestures no longer work
2. When I call anyone the screen turns off and I cant access the the dialpad, , etc
Does it sound like some settings are probably borked? I think I may need a stock 44s flash and possibly Kernel? I'm not sure.
Kildimo89 said:
I recently tried a custom ColorOS Rom off here and then flashed a CM 44s backup through TWRP as I didn't like the custom ROM.
However I know have a few issues on 44s
1. Custom gestures no longer work
2. When I call anyone the screen turns off and I cant access the the dialpad, , etc
Does it sound like some settings are probably borked? I think I may need a stock 44s flash and possibly Kernel? I'm not sure.
Click to expand...
Click to collapse
I'm shure you will find some people here with better knowledge than me on the matter.
But i would advice a full wipe before installing a different rom, just to avoid conflicts.
But first and as you have TWRP installed i would suggest using it to make a backup, save it to your PC and then a full wipe (everything but internal storage).
I would go for a fastboot install of stock cm11s 44s, just to ensure everything stays as stock again.
I suggest you get an full 38R rom and install this one clean. I do only read annoying stuff about 44S and I will not install it. My battery life is perfect for me with 38R and this should not be ruined
Sent from my O+O
I experienced this first hand ColorOS flashes the ColorOS partitions etc. You'll need to perform a full flash of the stock ROM via fastboot to flash all the CM11S partitions and such then it works a treat.
Kildimo89 said:
I recently tried a custom ColorOS Rom off here and then flashed a CM 44s backup through TWRP as I didn't like the custom ROM.
However I know have a few issues on 44s
1. Custom gestures no longer work
2. When I call anyone the screen turns off and I cant access the the dialpad, , etc
Does it sound like some settings are probably borked? I think I may need a stock 44s flash and possibly Kernel? I'm not sure.
Click to expand...
Click to collapse
"Backup" is not flashed, it gets Restored with TWRP
nikzDHD said:
I experienced this first hand ColorOS flashes the ColorOS partitions etc. You'll need to perform a full flash of the stock ROM via fastboot to flash all the CM11S partitions and such then it works a treat.
Click to expand...
Click to collapse
Ok I am getting an error.
I have downloaded 33r and extraced folder into the android-sdk on my desktop. Bootloader is unlocked and phone rooted.
I boot into fastboot and navigate to the Cm11 33r folder and try to run the flash-all.bat command and I get
"fastboot is not recognised as an internal or external command, operable program or batch file"
I first use this guide to start.
If i understand well, i think you extract your rom to the wrong folder it should be extract to /android-sdk-windows/platform-tools/ extract the rom zip content, not the entire folder, if you do it right you should have all your rom files on same place that fastboot.
You don't need to extract to the SDK folder, I usually extract the full image and just copy the adb.exe and dlls and fastboot into the folder, then control shift right click open a new command window here. I recommend you download the image from the cyngn site extract and flash each item separately.
hallow said:
I first use this guide to start.
If i understand well, i think you extract your rom to the wrong folder it should be extract to /android-sdk-windows/platform-tools/ extract the rom zip content, not the entire folder, if you do it right you should have all your rom files on same place that fastboot.
Click to expand...
Click to collapse
I just came here to post I figured it out not long after I posted, this was my error I was cd'ing android-sdk-windows/platform-tools/cm11-33r
I extracted all contents into platform tools and then it flashed perfect, thanks for all your help everyone
Lollipop
Rocco3 said:
I suggest you get an full 38R rom and install this one clean. I do only read annoying stuff about 44S and I will not install it. My battery life is perfect for me with 38R and this should not be ruined
Sent from my O+O
Click to expand...
Click to collapse
Battery life is even more perfect with Lollipop, its ludicrous how long it lasts forget 38R!
just my opinion. my phone lasts 3 days with my usage profile...never change a running system!
all other wannabe hackers crying here in the forums about battery after updating stuff etc....sorry, not my deal
Kildimo89 said:
I just came here to post I figured it out not long after I posted, this was my error I was cd'ing android-sdk-windows/platform-tools/cm11-33r
I extracted all contents into platform tools and then it flashed perfect, thanks for all your help everyone
Click to expand...
Click to collapse
Do yourself a favor and install this
http://forum.xda-developers.com/showthread.php?t=2588979
It installs the adb drivers computer wide so you don't have to worry about where you copy files, etc
Just go to the folder where the files are, shift+Ctrl+ right click then open command prompt there and flash away
ek69 said:
Do yourself a favor and install this
http://forum.xda-developers.com/showthread.php?t=2588979
It installs the adb drivers computer wide so you don't have to worry about where you copy files, etc
Just go to the folder where the files are, shift+Ctrl+ right click then open command prompt there and flash away
Click to expand...
Click to collapse
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
[/COLOR]
ek69 said:
Do yourself a favor and install this
http://forum.xda-developers.com/showthread.php?t=2588979
It installs the adb drivers computer wide so you don't have to worry about where you copy files, etc
Just go to the folder where the files are, shift+Ctrl+ right click then open command prompt there and flash away
Click to expand...
Click to collapse
:good: If your a windows user. A good bit easier with linux.
Alright guys I have a question. I am having issues returning to stock using the lg flash tool. Errors out everytime no matter what computer/what cable I used. I have the TOT file and I have extracted it and there is a recovery.bin. I was wondering if there was anyway to use this .bin file to restore the stock recovery? I can't find any info on this from my google searches.
Issue Resolved
tenebris said:
Alright guys I have a question. I am having issues returning to stock using the lg flash tool. Errors out everytime no matter what computer/what cable I used. I have the TOT file and I have extracted it and there is a recovery.bin. I was wondering if there was anyway to use this .bin file to restore the stock recovery? I can't find any info on this from my google searches.
Click to expand...
Click to collapse
I decided to do some more digging around and I found http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/10D by Team codefire. I downloaded the recovery.img for the D850. Flashed it using flashify. Once doing this, my phone reboot factory reset and now it is 100% stock. This was so much easier then actually setting up the lg flashtool
20f Recovery Name
tenebris said:
I decided to do some more digging around and I found http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/10D by Team codefire. I downloaded the recovery.img for the D850. Flashed it using flashify. Once doing this, my phone reboot factory reset and now it is 100% stock. This was so much easier then actually setting up the lg flashtool
Click to expand...
Click to collapse
You used the 10d recovery image. Were you able to get OTAs after that? Also, with 10d, the name of the file is simply recovery.img. What is the name of the 20f recovery image and where is it?
glenn4466 said:
You used the 10d recovery image. Were you able to get OTAs after that? Also, with 10d, the name of the file is simply recovery.img. What is the name of the 20f recovery image and where is it?
Click to expand...
Click to collapse
The recovery name should be still recovery.img even for the 20f update. To answer your question about OTAs, yes I was able to take them.
You can find the files for 20F here. http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/20F
The recovery might be in the Stock zip file, though I am not 100% sure.
Not There
tenebris said:
The recovery name should be still recovery.img even for the 20f update. To answer your question about OTAs, yes I was able to take them.
You can find the files for 20F here. http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/20F
The recovery might be in the Stock zip file, though I am not 100% sure.
Click to expand...
Click to collapse
Unfortunately, in the stock zip file there is only a system.img and a boot.img.
tenebris said:
I decided to do some more digging around and I found http://downloads.codefi.re/autoprime/LG/LG_G3/D850/stock_partitions/10D by Team codefire. I downloaded the recovery.img for the D850. Flashed it using flashify. Once doing this, my phone reboot factory reset and now it is 100% stock. This was so much easier then actually setting up the lg flashtool
Click to expand...
Click to collapse
i had twrp and installed bumpd stock 5.0 rom. so if i hardreset the phone from backup and reset, will i stuck in bootloop or twrp recovery menu?
I tried to flash CWM made with MTKdroidTools, directly through MTKdroidTools, and it came up (upside down). I then proceeded to select reboot. It just got stuck at a bootloop (also upside down). I did a battery pull after a few minutes, and booted into recovery, which came up with the stock one. I selected wipe emmc (written in chinese, but I have a different phone with the same recovery for reference). Did the wipe, still stuck in bootloop.
Device a is MT6572 Note 4 replica. I have a backup. ADB and Fastboot still work. I can boot into the stock recovery. What should I do?
Jesse72 said:
I tried to flash CWM made with MTKdroidTools, directly through MTKdroidTools, and it came up (upside down). I then proceeded to select reboot. It just got stuck at a bootloop (also upside down). I did a battery pull after a few minutes, and booted into recovery, which came up with the stock one. I selected wipe emmc (written in chinese, but I have a different phone with the same recovery for reference). Did the wipe, still stuck in bootloop.
Device a is MT6572 Note 4 replica. I have a backup. ADB and Fastboot still work. I can boot into the stock recovery. What should I do?
Click to expand...
Click to collapse
So you have a fake note 4 OK
Can you flash a kernel and can you get the boot.IMG
USBhost said:
So you have a fake note 4 OK
Can you flash a kernel and can you get the boot.IMG
Click to expand...
Click to collapse
I'm not sure what you mean about the kernel, can you be more specific?
I have a whole ROM backup, done minutes before I tried to flash the recovery, so I can get the boot.IMG from that
Jesse72 said:
I'm not sure what you mean about the kernel, can you be more specific?
I have a whole ROM backup, done minutes before I tried to flash the recovery, so I can get the boot.IMG from that
Click to expand...
Click to collapse
Then can you just restore that backup?
USBhost said:
Then can you just restore that backup?
Click to expand...
Click to collapse
How do I do that?
Jesse72 said:
How do I do that?
Click to expand...
Click to collapse
How did you even do a full ROM backup
Or you used that tool to do so?
USBhost said:
How did you even do a full ROM backup
Or you used that tool to do so?
Click to expand...
Click to collapse
Did the backup with MTKdroidTools. Its currently on my computer. How can I now restore it to the phone? ADB and fastboot work, but my recovery reverted back to stock?
Sorry for the dumb questions, but this is the first time I've ever created a brick.
Jesse72 said:
Did the backup with MTKdroidTools. Its currently on my computer. How can I now restore it to the phone? ADB and fastboot work, but my recovery reverted back to stock?
Sorry for the dumb questions, but this is the first time I've ever created a brick.
Click to expand...
Click to collapse
NP I was a noob too
What do you mean by adb working
In recovery and or booting up?
If you get adb while the bootloop
Can you do "adb shell mount"
And is your bootloader unlocked
Do you have download mod?
Edit nvm thanks @karandpr
This thread has instructions for backup & restore.
http://forum.xda-developers.com/showthread.php?t=2730031
karandpr said:
This thread has instructions for backup & restore.
http://forum.xda-developers.com/showthread.php?t=2730031
Click to expand...
Click to collapse
Stuck at step 3, won't accept scatter file.
Jesse72 said:
Stuck at step 3, won't accept scatter file.
Click to expand...
Click to collapse
In that case you will need stock firmware ....
I can tell you the procedure but not the solution...
You will need Google and lot of patience ...
First you will need to find phones with specs same(atleast 90% similar) to your phone....
Then you need to download firmwares with the help of Google (there will be a lot)...
Then you need to test them one by one using SP tool...
You will get weird results like touchscreen not working or something...
In case you find the perfect firmware...post in in this thread or make an FAQ ...It will help others ...
karandpr said:
In that case you will need stock firmware ....
I can tell you the procedure but not the solution...
You will need Google and lot of patience ...
First you will need to find phones with specs same(atleast 90% similar) to your phone....
Then you need to download firmwares with the help of Google (there will be a lot)...
Then you need to test them one by one using SP tool...
You will get weird results like touchscreen not working or something...
In case you find the perfect firmware...post in in this thread or make an FAQ ...It will help others ...
Click to expand...
Click to collapse
I have the backup ROM I made, can I just flash it somehow? Its in zip format.
Jesse72 said:
I have the backup ROM I made, can I just flash it somehow? Its in zip format.
Click to expand...
Click to collapse
Make a copy of zip
Open zip and check if there is updater-script ...
If there is then you can flash with recovery. ...
karandpr said:
Make a copy of zip
Open zip and check if there is updater-script ...
If there is then you can flash with recovery. ...
Click to expand...
Click to collapse
Just realised MTKdroidtools is working, so I re-flashed CWM. Putting ROM zip on blank SD card, and will try to flash with CWM.
Am I doing this right?
Jesse72 said:
Just realised MTKdroidtools is working, so I re-flashed CWM. Putting ROM zip on blank SD card, and will try to flash with CWM.
Am I doing this right?
Click to expand...
Click to collapse
I have no hands-on experience with MTK devices.
On normal devices with recoveries , there is a folder Meta-INF and there is updater script and update binary which allows a Zip file o flashed on Android Recoveries (Stock or CWM). Stock recoveries enforce manufacturers signature. Custom recoveries like CWM allow unsigned zips.
Long story short ,check for META-INF folder and check if updater script & updater-binary is present. If not then ,zip won't be flashed with CWM
karandpr said:
I have no hands-on experience with MTK devices.
On normal devices with recoveries , there is a folder Meta-INF and there is updater script and update binary which allows a Zip file o flashed on Android Recoveries (Stock or CWM). Stock recoveries enforce manufacturers signature. Custom recoveries like CWM allow unsigned zips.
Long story short ,check for META-INF folder and check if updater script & updater-binary is present. If not then ,zip won't be flashed with CWM
Click to expand...
Click to collapse
There is no folders in the backup, just individual files. No files called updater script or updater-binary either. And yeah, it didn't flash either. I have 2 backups, one stock ROM, one done today. Both were done with MTKdroidTools, so I expect both to be the same. Any way to get the required files and add them, or do something else to make it flashable?
Jesse72 said:
There is no folders in the backup, just individual files. No files called updater script or updater-binary either. And yeah, it didn't flash either. I have 2 backups, one stock ROM, one done today. Both were done with MTKdroidTools, so I expect both to be the same. Any way to get the required files and add them, or do something else to make it flashable?
Click to expand...
Click to collapse
Try SP tool or it's variant . ..Those backups can only be flashed in SP tool !!
:angel:
It might be possible to extract files if they are not encrypted but it will take a lot of time...
karandpr said:
Try SP tool or it's variant . ..Those backups can only be flashed in SP tool !!
:angel:
It might be possible to extract files if they are not encrypted but it will take a lot of time...
Click to expand...
Click to collapse
SP flashtools isn't working, but I found a guide, which shows how to create a flashable zip from a backup. However it says to get the META-INF folder from a custom ROM for your phone. How specific does this folder need to be? I cant be sure of what my device is completely because it is branded as a note 4, rather than a replica under a brand name.
I can find a MT6572 ROM, but I cant be sure everything would work flawlessly with my phone. Understand what I'm saying?
EDIT: link to article http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
Jesse72 said:
SP flashtools isn't working, but I found a guide, which shows how to create a flashable zip from a backup. However it says to get the META-INF folder from a custom ROM for your phone. How specific does this folder need to be? I cant be sure of what my device is completely because it is branded as a note 4, rather than a replica under a brand name.
I can find a MT6572 ROM, but I cant be sure everything would work flawlessly with my phone. Understand what I'm saying?
EDIT: link to article http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
Click to expand...
Click to collapse
The binary is generic .The updater script needs to be specific. Special permissions are assigned to files using the script which can make or break the device. You will need a ROM very close to your device for Meta INF.
The article you have listed is for CWM backup which is different from MTK tools backup.
You will need to get SP tools working to get your device working...or search for a working backup for your device.
karandpr said:
The binary is generic .The updater script needs to be specific. Special permissions are assigned to files using the script which can make or break the device. You will need a ROM very close to your device for Meta INF.
The article you have listed is for CWM backup which is different from MTK tools backup.
You will need to get SP tools working to get your device working...or search for a working backup for your device.
Click to expand...
Click to collapse
I'm confused with what you want me to do with SP flash tools. Can you please explain?
Hello,
I recently unlocked the bootloader and installed TWRP as custom recovery, but I'm now in need to return full-stock:
could anyone please tell me (or link me - I searched but I didn't found anything about it) a full procedure to restore the phone status?
I need a stock ROM, I guess, but then what? Flash it in TWRP? Does it also include stock recovery or is it a separate file instead?
Thank you very much!
shakathesaint said:
Hello,
I recently unlocked the bootloader and installed TWRP as custom recovery, but I'm now in need to return full-stock:
could anyone please tell me (or link me - I searched but I didn't found anything about it) a full procedure to restore the phone status?
I need a stock ROM, I guess, but then what? Flash it in TWRP? Does it also include stock recovery or is it a separate file instead?
Thank you very much!
Click to expand...
Click to collapse
so you do know that relocking the bootloader will cause a factory reset and all data will be wiped from device.
First, all you need to do is download a full rom update and flash in system local update. that will put stock software and stock recovery back.
second, Reboot phone to bootloader mode. Then you just type in cmd "fastboot oem lock"
MrSteelX said:
so you do know that relocking the bootloader will cause a factory reset and all data will be wiped from device.
First, all you need to do is download a full rom update and flash in system local update. that will put stock software and stock recovery back.
second, Reboot phone to bootloader mode. Then you just type in cmd "fastboot oem lock"
Click to expand...
Click to collapse
Thanks for your fast answer!
So is it better to flash stock ROM through local update than through TWRP? Or it's the same procedure both ways?
Thanks again!
They both will work.
Use the msmdownloadtool it's easiest, safest and fastest way.
Lownita said:
Use the msmdownloadtool it's easiest, safest and fastest way.
Click to expand...
Click to collapse
File name : 6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12
Hi, i have downloaded many times file above, why the said .rar file can not be extracted?
What is content the .rar file above?
Download Source : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
DancingFate said:
File name : 6T_MsmDownloadTool_v4.0.58_OOS_v9.0.12
Hi, i have downloaded many times file above, why the said .rar file can not be extracted?
What is content the .rar file above?
Download Source : https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Click to expand...
Click to collapse
This is for 6t. Is OP at 6t or 6?
Latest and greatest https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
These tools will return your phone to 100% stock.
I've use them multiple times.
I recommend using these qualcomm drivers.
https://drive.google.com/file/d/1k1cXnVaz5d2IRLqxFE9AiY8GFMmx3CDG/view?usp=sharing