Related
A couple of days ago my Huawei p7 started to shut itself down and after that it keeps rebooting.
It starts itself up and I get into the choose your language screen and then it shuts down.
When i try to get into the system recovery (using volume & power) I get the following screen:
Android system recovery <3e>
Huawei software installed failed.
Please retry!
Shutdown system now
There is no UPDATE.APP
.............................................
FAIL
And even in system recovery it keeps rebooting.
Im kinda helpless at the moment not knowing what to do.
Did this occur to anyone ? Is there a solution for this problem ?
Thanks in advance.
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
wekii said:
You should download firmware update file from Huawei Official web site. Extract dload folder from downloaded archive and put it on your SD card. After that you should try to trigger firmware update with factory reset (method which is usually called "force update") by holding all three buttons when the phone is turned off.
But maybe your phone have some hardware problem if it restarts even in recovery mode.
UPDATE:
Does phone restarts itself when it's in fastboot mode (you can get into that mode by holding VOLUME DOWN and POWER button while phone is turned off and connected into USB port of computer just before pressing that button combination) ??
Click to expand...
Click to collapse
I've downloaded the update file and proceeded with your steps. I continued to trigger the firmware update with the factory reset.
At first it seemed to work, the phone started updating but after a couple of seconds it started to reboot itself again
I got the phone in fastboot mode and at this moment it does not restart itself !
I went on downloading Hisuite and at this moment it keeps searching for drivers on the network.
The searching for drivers is taking quite some time is this normal ?
Thank you very much for your help so far !
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked. If it's not you need to enter the next command "fastboot oem unlock 1234567812345678", where "1234567812345678" should be replaced with unlock code that is unique for your device. Instructions which explain how to obtain unlock code for your device can be found here,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
Hi,
I've got the same issue.
When I start to "force install" method, my phone doesn't boot.
It just stay in a state of "charging" but nothing append.
I flashed boot and recovery with Fastboot.
But now, when I start the phone in Fastboot&Rescue Mode, the device doesn't appear in the liste when I run adb devices.
But when I start in the "force install" mode, adb devices returns the serial of the phone (but it doesn't respond to fastboot command).
Are there other files to flash on the phone than juste recovery and boot ?
Thank's for those steps, i'll continue to try to flash again.
Edit :
Ok phone is back !
The problem came from my SD Card, I had not only the dload folder, but an other file.
Format SD Card -> dload folder -> "force install" method -> ENJOY !
Thank's a lot !
wekii said:
OK, maybe these are good news if you say that your phone doesn't restart when it's in fastboot mode.
I would recommend you to try to reflash your phone's stock recovery and boot images with those extracted from firmware that you are trying to install.
Follow these steps:
Download Huawei Extractor tool from here,
Open update.app with Huawei Extractor and extract next two images: RECOVERY and BOOT (you can do that by selecting those two images while holding CTRL button, then right click > Extract Selected),
When extracted, rename those two images into "recovery.img" and "boot.img",
Copy those two images into "platform-tools" folder of Android SDK,
Run command prompt and go to "platform-tools" folder by using "cd" command,
Start your phone into fastboot mode,
Enter following command into command prompt: "fastboot devices" (without quotes), you should get your phone's serial number listed, if that's right, go to the next step,
Enter: "fastboot oem get-bootinfo", it needs to say that your bootloader is unlocked, if it's not read this,
Flash your phone's recovery with "fastboot flash recovery recovery.img",
Flash your phone's boot image with: "fastboot flash boot boot.img",
After successful flashing of both images, turn your phone off by holding POWER button for a several seconds,
Prepare SD card on your PC by formatting SD card and copying "dload" folder of phone's firmware onto SD card,
After you insert SD card into phone, start your phone with "forced install" method by holding all three buttons on your phone.
After that your phone should process firmware install successfully if there is no some hardware issues. Good luck and inform us about your progress.
Click to expand...
Click to collapse
I followed all your steps but i get stuck at step 7. When I give the command fastboot devices it doesn't show my phone's serial number. Instead it shows a ? (question mark).
Did I do something wrong or is there a solution for this?
Thanks in advance!
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
wekii said:
Maybe you should try other version of platform tools. I would recommend you to download adt-bundle-windows-x86_64-20140702.zip (x64) or adt-bundle-windows-x86-20140702.zip (x32) from "Android SDK" official web pages (I assume that your are using Windows OS). After download extract only "platform-tools" directory to the root of Windows C:\ partition and try described procedure again.
However if you are still getting question marks instead of phone's serial number, you should ignore that step and go onto the next one. I had the same problem in the past and flash commands were successful even serial number wasn't been displayed.
Keep us informed about your progress. Good luck zbnd !!
Click to expand...
Click to collapse
Thanks for your response !
So I followed through like you said. Gave the fastboot oem get-bootinfo command and then I got (bootloader) locked. So I followed the bootloader's unlock code (official way), entered my product SN and product IMEI, used the Huawei Product ID generator followed the procedure and all I get is : Please input the correct Product ID
What did I do wrong this time ? I'm not sure if it's even possible to do this wrong. Is there another way around ?
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Pboguet said:
You can unlock with Vroot, like I did. I didn't try to get a serial from Huawei.
For the Fastboot command 'Fastboot device's I had a ? too, but with 'adb devices' command, I got my serial number.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
I've downloaded Vroot (english version) but when i connect my phone it says not support mode
I tried to connect while in fastboot&rescue mode, because this is the only way the phone stays on without restarting.
I then tried to connect without fastboot&rescue mode. But my phone keeps rebooting. I did get a message that USB debugging is disabled. However I can't enable usb debugging because my phone won't boot up normally.
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
wekii said:
@Pboguet
You should read carefully because your answer has no sense for the phone which is in state like zbnd's phone is.
@zbnd
Maybe you are doing something wrong. You can send me your's phone serial number and IMEI in PM inbox, I will try to generate unlock code for you.
Click to expand...
Click to collapse
Thank you very much for all your help!
Despite following all your steps my phone keeps rebooting
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
wekii said:
Sorry to hear that. Did you manage to make all steps that I described to you? Can you share more informations about your current efforts please.
Click to expand...
Click to collapse
Ik
After unlocking my phone I got the message unlocked in CMD.
I then flashed recovery and boot. Both times it said that the flash was succesfull, this only took a few seconds I don't know if thats normal? I then followed your last steps ( dload folder etc) and put the SD card in my phone.
It start installing but after approximetaly 25 seconds the phone shuts itself down and then reboots.
The procedure then starts again and it starts installing followed by shutting down and rebooting.
I'm sorry to hear that. Seems like it's some hardware issue.
However I still have one more idea that you can try in fastboot mode. I would recommend you to install entire firmware manually with fastboot commands.
By following previously described procedure try to extract with "Huawei Extractor" tool next images also: SYSTEM, USERDATA, CUST and CACHE.
After step number 10, try to use next commands also:
"fastboot flash system system.img"
"fastboot flash cust cust.img"
"fastboot flash userdata userdata.img"
"fastboot flash cache cache.img"
When you are finished with flashing of all images, use "fastboot reboot" command to restart your phone. Steps 11, 12 and 13 should be ignored this time.
Let me know the result
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
mbert said:
Hey,
Only TWRP 2.7.1.0 does not reboot.
Thanks in advance...
Click to expand...
Click to collapse
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Ziółek said:
If this recovery works than try:
1. Save this Se7en or this HRT or this custom MIUI ROM on SD card
2 .Wipe in TWRP everything (dalvik, system,data,cust, internal) except external (SD card). Internal only if You have a backup or not important data there.
4. Install zipp ROM from external memory. Sometimes try more than one time in fail case. For HRT ROM especially.
Let me know if helped.
Click to expand...
Click to collapse
failed
I tried se7en and miui.
I wiped dalvik,system,data,internal,cache and custom, which only lasted about 2 seconds, but said succesful (Is that enough to delete all partitions?).
Installation of both custom roms completed succesfully and lastet several seconds (max 1 min I think).
Se7en: reboot -> huawei logo -> reboot -> language selection (in the style of stock rom?) -> reboot ...
Miui: reboot -> miui logo -> reboot -> language selection (miui style) -> reboot -> wifi selection (I skipped) -> searching for sim card -> reboot
mbert said:
Hey, I'm glad I found this forum, because I have exactly the same problem! Since zbnd did not reply I wanted to let you know that flashing boot.img, recovery.img, cache.img, userdata.img, cust.img and system.img via fastboot did not work
The commandline for each file said "OKAY" and "finished" therefore I assume the process(es) completed succesfully.
Maybe I should tell you some information and the steps I did with my P7:
- my device is a branded german telekom version with firmware P7-L10-V100R001C150B122- because of crappy pink telekom bootlogo und bloatware I wanted to flash the original huawei firmware so I downloaded the B126 from the official website and updated via force update method- at the end of the update process i got the messages "huawei cust fail" and "update_post_process fail" but when I rebootet the B126 was installed and showed a message "Defect report reminders - This is an internal test version. Please report defects to Yangyexiao 00143718" - can't be correct, I thought- after googling a lot and reading through several forums I rooted my device with RootGenius, installed HiSuite and Android-SDK (driver were installed correctly, adb devices showed a device with serial) and deleted the "cust" directory on my phone - at that point everything still worked- next step: I installed TWRP 2.7.1.0, made an updateable zip file with huawei update extractor (including system.img, userdata.img, cust.img and boot.img) and flashed it via TWRP. The process completed succesfully, but needed only a few seconds. After that I got this bootloop at the language selection- then I wanted to return to the last functioning state, so I flashed the stock recovery via fastboot and started with force update method. But after a few seconds the device rebooted during the update process which led to another (maybe the same) bootloop. I had to remove the sd card, but the device continued to reboot in recovery mode. So i installed TWRP 2.7.1.0 again- Then I tried to restore a B133 backup I got from another forum, but it obviously did not work (see attached image)
Now I just don't know what to do ... I get a bootloop in stock recovery and I get a bootloop in TWRP 2.8.0.0.
Only TWRP 2.7.1.0 does not reboot. What is about the other files inside the UPDATE.APP (modemimage.img, efi.img, etc)? Is it possible that some of these files are needed?
Thanks in advance...
Click to expand...
Click to collapse
To use fastboot you need to unlock bootloader first. And before flash, you need to erase partition first, for a proper job. Please read well about the fastboot procedure is a dangerous procedure
My bootloader is unlocked, but fastboot sais I don't have permission to erase partitions ...
Gesendet von meinem HUAWEI P6-U06 mit Tapatalk
Just thought I'd share, might help someone. This is for Nexus 7 previously bootloader unlocked and rooted (and whatever else, like xposed) going from 4.4.4 to 5. If you're not on 4.4.4 and bootloader unlocked get there first. Obviously you need usb debugging on.
You also need some form of adb and fastboot. I used Minimal ADB from here:
http://forum.xda-developers.com/showthread.php?t=2317790
What I Did:
- Got the Lollipop OTA from the links posted everywhere by now, including the second sticky here in General.
Put a copy in the adb/fasboot folder in Windows, and renamed the file to updatelollipop.zip to make it easier to handle.
Tried old style of updating: Uninstall Xposed, flash Xposed Disabler, flash OTA zip from custom recovery. Failed. Tried again, failed again.
But this was expected, as I'd read that the way lollipop updates is different from all previous updates and will fail at the slightest discrepancy in system partition.
So, need clean system.
- Got the Stock 4.4.4 firmware from Google: https://developers.google.com/android/nexus/images
Inside the firmware file found the system.img and recovery.img images.
Put these two files in the same folder as minimal adb and fastboot.
- Got into bootloader.
if powered off hold power and volume down keys. if booted up in Minimal ADB command prompt window type:
adb reboot bootloader
- flashed stock system and recovery
fastboot flash system system.img
fastboot flash recovery recovery.img
- Got into stock recovery
In bootloader, scrolled to select recovery, then with "No Command" showing held power and clicked volume up.
Select apply update from adb. Screen says to type adb sideload update from computer.
Ran into a hiccup. ADB would not recognize my N7. typing "adb devices" returned empty result. Booted up into Android, computer and adb recognized device fine. typed adb reboot bootloader, and in bootloader adb no go.
So while connected to computer in bootloader mode, went into Device Manager in Windows. Sure enough there was unknown device called grouper. Promptly update the driver. I used driver files from the Wugfresh toolkit I had installed. The device was recognized as Google Galaxy Nexus ADB device. Didn't matter to me as long as it was recognized as ADB. If you want official drivers you can get them from Asus here: http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2
- Back into ADB sideload screen in N7 stock recovery.
typed adb sideload updatelollipop.zip
Let the ADB push the file, then stock recovery did the update. no issues. back in recovery might as well erase cache partition.
Root then. Could use Wugfresh NRT but decided to go manual.
UPDATE: As of SuperSU 2.27 Beta, flashing SuperSU from custom recovery is enough to gain root on Lollipop 5.0. Root kernel is no longer needed!
Old fashioned root failed works now: get the latest twrp recovery (copied it into adb folder, renamed it to twrprecovery.img), get the latest superSU (put it anywhere in N7 internal storage), flash the latter with the former:
In command prompt, typed fastboot boot twrprecovery.img
this temp booted twrp. promptly went to install, found superSU zip, flashed it.
Booted into Android, Lollipop looks nice, but No Root.
Again, not surprised, had already read lollipop needs modified kernel for root. Looked in the Wugfresh NRT files, had two candidates, modified boot img and root kernel img. not sure the difference, but the two files had different file sizes, and I had read somewhere that modified kernel would keep most of the security features of stock kernel, only modifying permissions needed for root, so decided to go with the kernel img file. Copied it over to adb fastboot folder, renamed it rootboot.img
- got back into bootloader. in command prompt typed
fastboot flash boot rootboot.img
Rebooted into Android, had root! Great. Notice didn't need to flash superSU a second time.
To check if root works fine, just open superSU app. If it opens fine then you're good. Root apps will ask for root, and granting will work fine, but that doesn't mean the apps will be able to use root for the simple reason that they might need to be updated. for example, es file manager asked for root, was granted, but root directories showed empty. clearly needs an update. Tried Total Commander, gave root, worked fine. So apps ability to use root in lollipop will vary based on their need to be updated to work.
thanks as always to Wugfresh and Chainfire.
"Unknown Device" when USB Debugging On
Speaking of root apps needing update, one app that needed updating if you use it, is Adbd Insecure. Why am I singling it out? Because it had me running around in circles trying to figure out why Windows was claiming my N7 was an Unknown Device.
Thing is, I installed adbd insecure long ago set on auto start, and it's useful for when it's needed, but I had completely forgotten about it now when trying to figure out the driver issue. Turning off USB debugging Windows happily recognized MTP, but who wants debugging off, it's a bad idea.
After twirling in circles finally decided to check if Windows would recognize bootloader and recovery mode. Sure enough, everything was good there. Rebooted into Android and noticed ADB was recognized briefly upon startup before it went away. That got me suspicious which led me to the culprit. So, yeah, save yourself some trouble and update that app, if you have it running.
Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
mclovin9091 said:
Decided to OTA (not sure why) my Moto G LTE that was and was running stock but with an unlocked bootloader but have ran into issues and think i am now just digging a bigger hole for myself so I am asking for some help please.
I after the attempted update i started having issues with some apps not working and/or uninstalling themselves. Play store was the worst (tired wiping cache and data but no joy) then the camera decided it would uninstall and then any other camera apps in added wouldn't save pictures. Managed to get a fresh stock rom install.
So i though i'd update to CM13, downloaded the file, twrp and Gapps and set about booting into recovery to install twrp but initially i was unable to enter recovery and it stayed on the fastboot screen. Now i am getting the dead android and the red triangle but have a working stock rom.
I can now no longer use fastboot, all it does is start the rom as if i had just powered on normally.
Any help appreciated.
Click to expand...
Click to collapse
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
stonedpsycho said:
You say you have working stock rom, so can you boot your phone to home screen? If so in ADB try using this command in CMD "mfastboot reboot bootloader" without the speech marks.
Click to expand...
Click to collapse
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
mclovin9091 said:
Yes can get onto the home screen and use the phone (so far) without issue, get as far as the fastboot screen but then states 'fastboot' is not recognized as an internal or external command, operable program or batch file. That is given for any command including "reboot"
Click to expand...
Click to collapse
Have you enabled "usb debugging"? in developer settings (tap the build number 7 times) Do you have ADB installed? If so did you open CMD in the ADB folder?
FCorvin said:
Stock ROMs do things like that to unlocked phones.
Check if you still have root access - I'm guessing you lost it, so you'll need to root again - Root Checker
Flash again the last and the proper TWRP tool (make sure you download for THEA) using the Rashr Flash Tool app if you can't access the fastboot screen.
Put your ROM on a SD card, erase everything and reinstall the system and the proper gapps (use at least MINI, so you could recover your old settings from your google account at first launch).
But think about ditching the stock - give Temasek a try. You will have to modify a couple of files to make the TITAN release work on your THEA, but it's worth aplenty.
Keep us posted.
Click to expand...
Click to collapse
Cheers, any info on what files need modding?
Was rooted, managed to get adb to work last night and managed to reinstall twrp but now i can't get the rom to load and can't flash any CROM.
So used the all in one tool to re install stock 5.0.2.
Going to grab a brew and chill for a bit.
Aiight, once you downloaded the zip on your PC, go to:
1. ...titan.zip\META-INF\com\android
Drag the "metadata" file on a notepad page and replace 0x4882 with 0x4821 (your phone's bootloader code) and save.
2. ...titan.zip\META-INF\com\google\android
Drag the "updater-script" file on a notepad page, hit "Search and replace" for any of the XT's in there with yours, XT1072.
You will have 3 hits.
Example: Search and replace XT1069 with XT1072 ->
getprop("ro.product.device") == "XT1069"
getprop("ro.build.product") == "XT1069"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069
will become:
getprop("ro.product.device") == "XT1072"
getprop("ro.build.product") == "XT1072"
titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1072.
(3 - while still here)
Search and replace the initial 0x4882 bootloader with yours, 0x4821.
Save the changes.
And... you're good to go.
Some native Moto apps won't show up in PlayStore because of this, but you can get all the Moto stuff from here (if you really love them).
Once installed, enjoy the full power of your brand new Android 6 phone.
Don't forget to do all the things you did as a kid once: activate the developer options as mentioned above, set the SuperSu permissions and so on.
However: screw-ups occur mainly because of conflicts between the new and the old, so you will have to perform a clean install as advised here, which means wiping everything you had - so you won't be able to return to your Lollipop Stock through any recovery.
So chill some more and consider everything thoroughly.
Cheers.
bloody phones, dunno ewhat happened but seems like reinstalling the SROM for the 2nd time allowed me to boot into recovery, twrp and load the CROM. Only issue this time was that apparently stock gapps was too big for the phone so had to download and install the mini version.
Will see how CM13 goes and download the Temasek for install later once im happy everythings working.
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.