Related
hi guys
I tried to install a custom rom on my HTC One X PLUS. I am new to this and it looks like i kinda screwed up. i used "HTC One X+ AIO Kit By Hasoon2000 v2.3". I have now this "CWM-based Recovery v6.0.2.7" on my phone. i can't boot the normal OS anymore. everytime i reboot, this cwm recovery shows up. when i try to install cyanogenmod (cm-11-20140705-NIGHTLY-enrc2b.zip) by "install zip from sdcard => choose zip from sdcard ==> ..." i just receive:
Code:
set_metadata_recursive: some changes failed
E:Error in /sdcard/0/cm-11-20140705-NIGHTLY-enrc2b.zip
(Status 7)
Installation aborted.
i have no idea what to do. can anyone pls help? is it still possible to reset everything to get my phone working again?
Flash the latest version, older ones can't flash kitkat ROMs
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-enrc2b.img
Sent from my One X+ using Tapatalk
Phoenix09 said:
Flash the latest version, older ones can't flash kitkat ROMs
Click to expand...
Click to collapse
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Hutschi93 said:
How can i do this? i can't put the file on my phone because my phone doesn't have a sd card.
Click to expand...
Click to collapse
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
leefear said:
check this out http://forum.xda-developers.com/showthread.php?t=2066390 read it all, the part you need is adb sideloading, again, read it all at least a few times
Click to expand...
Click to collapse
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Hutschi93 said:
i already tried that, but all i get is this error:
Code:
* failed to write data 'protocol fault (no status)' *
my phone is in this "sideload mode" and i changed the filename into one word (that's what i should do if i get an error)
Click to expand...
Click to collapse
did you flash the recovery that phoenix suggested?
leefear said:
did you flash the recovery that phoenix suggested?
Click to expand...
Click to collapse
how? i just can open this cwm based recovery mode or this strangely HBOOT mode. but my computer doesn't really recognize it. if i open the device manager i see it under "ADB Interface" as "HTC Bootloader" but if use "adb devices" in command prompt my phone does not get recognized. the toolkit doesn't recongize it either.
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Hutschi93 said:
OK guys i got my computer to recognize my phone in recovery mode. i can use adb push to transfer files to my phone. do i have to flash a new recovery or can a just put a new rom on my phone and try installing that?
EDIT:
OK GUYS! thanks to that i got my computer to recognize my phone i could flash the recovery phoenix suggested! and i finally could install my rom! thank you sooo much guys! you are my hero and made my day! i would give you a hug if i could but i guess nobody of you lives in switzerland
love you guys! (no homo)
Click to expand...
Click to collapse
glad u got it working bud!
M6E69X only for WI501Q
TWRP Backup & stockrecoveryM6E69X: uploaded by @Lrs121
【Version】
WI501Q _M6E69X
【Model Name】
ZenWatch 2
【Release Date】
???
【Release Note】
???
@RoyanArt
I won't be able to have access to adb till late tonight at the earliest, can you pull it using the following command?
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/
Those commands should copy the stock recovery IMG to your sdcard directory
Edit. Last command might be
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG
I think you have to specify the destination IMG file name
Sent from my ONEPLUS A3000 using Tapatalk
RoyanArt said:
MWD59 to M6E69N update.zip (adb sideload) : go to this thread
TWRP Backup : googledrive
Who can help to pull the stock recovery ? @Lrs121 , @slothdabski
【Version】
M6E69N
【Model Name】
ZenWatch 2
【Release Date】
2016/10/17
【Release Note】
1.Fix security vulnerabilities ( Update to Sep 2016 of Android Security Bulletins )
2.Fix issue "Watch could not pair with iPhone 7"
Click to expand...
Click to collapse
FYI: The stock recovery link is broken.
I can get to it in a couple hours. Out running errands and I've been meaning to make a backup
Here it is: Stock M6E69N recovery
slothdabski said:
@RoyanArt
I won't be able to have access to adb till late tonight at the earliest, can you pull it using the following command?
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/
Those commands should copy the stock recovery IMG to your sdcard directory
Edit. Last command might be
dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG
I think you have to specify the destination IMG file name
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
sorry, i cant do it, because i've flashed twrp recovery :good:
Lrs121 said:
I can get to it in a couple hours. Out running errands and I've been meaning to make a backup
Here it is: Stock M6E69N recovery
Click to expand...
Click to collapse
Thanks for the stock recovery, ill put your post to top :good::good:
Want to root/twrp Zenwatch 2 m6e69n - ANY HELP would be GREAT!!!
I got my Z2 m6e69n about a week ago (10/16/16) and it's great but I want root & twrp like I have on my other Android devices. Don't know that it matters, I'm using LS990 (Sprint LG G3 on KK 4.4.2). I've been searching XDA and YouTube for clear, detailed info on how to root and get TWRP on the watch but not having a lot of luck.
What I have found is:
- I have activated developer options
- How to get into recovery, how to access bootloader, how to unlock bootloader (http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623) THANKS to arbitercu
...but nothing detailed about installing TWRP. Maybe I'm blind or just not understanding but any help would be great. I simply don't want to BRICK my Zenwatch.
- ALSO, VERY LITTLE EXPERIENCE with ADB and side loading which I think might be important to mention.
- Last thing, basically want to get some of the BLOAT off the device and get the most out of it.
Almost forgot:
- Zenwatch 2 m6e69n Sparrow (1.63")
Thanks in advance!
dsabine said:
I got my Z2 m6e69n about a week ago (10/16/16) and it's great but I want root & twrp like I have on my other Android devices. Don't know that it matters, I'm using LS990 (Sprint LG G3 on KK 4.4.2). I've been searching XDA and YouTube for clear, detailed info on how to root and get TWRP on the watch but not having a lot of luck.
What I have found is:
- I have activated developer options
- How to get into recovery, how to access bootloader, how to unlock bootloader (http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623) THANKS to arbitercu
...but nothing detailed about installing TWRP. Maybe I'm blind or just not understanding but any help would be great. I simply don't want to BRICK my Zenwatch.
- ALSO, VERY LITTLE EXPERIENCE with ADB and side loading which I think might be important to mention.
- Last thing, basically want to get some of the BLOAT off the device and get the most out of it.
Almost forgot:
- Zenwatch 2 m6e69n Sparrow (1.63")
Thanks in advance!
Click to expand...
Click to collapse
How about a little more googling. http://forum.xda-developers.com/zenwatch-2/orig-development/wip-unofficial-twrp-v2-8-7-0-t3321199/
Be careful what you remove. The watch won't function properly without some apps.
edit : no issue quick for wear
Thanks for the thread. :laugh::laugh::laugh:
Could someone provide fastboot flashable .IMG files?
I've ****ed up my watch quite hard by grabbing the wrong system image while the watch was still locked, now I can't even boot it anymore or restore a TWRP backup because the file system seems to be corrupt. I can't save anything in /sdcard without it getting wiped again after a reboot.
EpicLPer said:
Could someone provide fastboot flashable .IMG files?
I've ****ed up my watch quite hard by grabbing the wrong system image while the watch was still locked, now I can't even boot it anymore or restore a TWRP backup because the file system seems to be corrupt. I can't save anything in /sdcard without it getting wiped again after a reboot.
Click to expand...
Click to collapse
What happens when you boot twrp using fastboot? If you can get into twrp, with the bootloader unlocked you might be able to reformat the partitions.
On a side note I think you can format the partitions from fastboot mode
Lrs121 said:
What happens when you boot twrp using fastboot? If you can get into twrp, with the bootloader unlocked you might be able to reformat the partitions.
On a side note I think you can format the partitions from fastboot mode
Click to expand...
Click to collapse
Yeah, I've managed to repair the partitions by erasing and formatting them via fastboot, for whatever reason only formatting them didn't help... I have no clue why. Except boot I've erased + formatted every partition, then booted TWRP via "fastboot boot TWRP" and then was able to push TWRP backup files onto /data/media (/sdcard was broken still for whatever reason). After the first boot it somehow fixed /sdcard too tho it was missing all of its files on there. I simply did a factory reset of the watch after this and now it seems to be back and working again, tho I'm not fully sure because TWRP seems to have some problems still but that could be due to the wonky and, sorry, "****ty" port of TWRP 3.0 someone else made.
EpicLPer said:
Yeah, I've managed to repair the partitions by erasing and formatting them via fastboot, for whatever reason only formatting them didn't help... I have no clue why. Except boot I've erased + formatted every partition, then booted TWRP via "fastboot boot TWRP" and then was able to push TWRP backup files onto /data/media (/sdcard was broken still for whatever reason). After the first boot it somehow fixed /sdcard too tho it was missing all of its files on there. I simply did a factory reset of the watch after this and now it seems to be back and working again, tho I'm not fully sure because TWRP seems to have some problems still but that could be due to the wonky and, sorry, "****ty" port of TWRP 3.0 someone else made.
Click to expand...
Click to collapse
That's good you got it working. As for twrp if I remember right there were some issues with 3.0.0 regarding Android wear that were fixed in later versions. Ever since my galaxy s3, I've taken to building my own for the devices I have or have had. I make them available on my website.
Can anybody provide this for a Zenwatch 2 Wren? It would be appreciated a lot.
Can you help to pull the M6E69S stock recovery ? @Lrs121 , @slothdabski
RoyanArt said:
Can you help to pull the M6E69S stock recovery ? @Lrs121 , @slothdabski
Click to expand...
Click to collapse
Sorry had it pulled the moment the ota went out. I just didnt have it pushed to my server. Sparrow Stock recoveries
OP EDITED & UPDATED
M6E69S
-Version-
WI501Q _M6E69S
-Model Name-
ZenWatch 2
-Release Date-
2016/12/07
-Release Note-
1.Fix security vulnerabilities ( Update to Nov 2016 of Android Security Bulletins
Hey bud, watch just got an update today dec 29th, im rooted with twrp. Ill install a stock recovery sometime but in the mean time it would be nice to get that up for people to side load!
Dont know what the build is called, but i was running M6E69S when i got it.
Can you help to pull the M6E69V stock recovery ? @Lrs121 , @slothdabski
RoyanArt said:
Can you help to pull the M6E69V stock recovery ? @Lrs121 , @slothdabski
Click to expand...
Click to collapse
@RoyanArt Could you please upload the TWRP backup of latest firmware? It would be so appreciated ???
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...
I unlocked the device bootloader thanks to Narender, and tried to flash Lineage OS 18.1. After flashing the ROM and vendor zip files, I switched the current slot and restarted to fastboot mode. Then I flashed the vbmeta image. Then I rebooted to recovery to check the current slot. Slot was as expected, so I rebooted the system.
Then, TWRP gave me an alert saying "No OS is installed" before rebooting. I was unsure what was the reason for it because the ROM was just installed, so I rebooted the system.
After that, device went straight into fastboot mode after "Android One" screen. No matter which option I choose from there, it keeps restarting the bootloader. I tried using "fastboot reboot recovery" but that did not work either. Then I tried to change the active slot of the device using fastboot commands. That did not help either.
Now I'm stuck with a Nokia 7.2 that can only be turned off or start in fastboot mode. Is it bricked beyond saving? I just want to install TWRP in any of the slots and install any usable ROM. Any help is deeply appreciated.
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Chevindu said:
Installed NFT and flashed the stock ROM using that. All good now. I still need to figure out how to install ROMs on A/B systems using TWRP.
Click to expand...
Click to collapse
Follow this and DM if you have doubts
Edit: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
Follow this and DM if you have doubts
Click to expand...
Click to collapse
I actually installed few ROMs after my previous reply. But none of them had working WiFi, which is a deal breaker. Went back to stock ROM.
If you are interested I could help you
Ujwal2000 said:
If you are interested I could help you
Click to expand...
Click to collapse
Hey, thanks. But I thought it's not possible due how the signatures in security patches work. So I gave up. Maybe I misunderstood. Linking to Raghu's reply below.
Post in thread '[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |'
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Ujwal2000 said:
No, wi-fi with twrp still doesn't work. But what I did was, I extracted the boot image of the ROM I was using, flashed twrp, flashed gapps and then flashed the boot file I extracted earlier. So, wi-fi does work in the end. But, you can't have twrp perpetually installed
Some tutorials I saw online used fastboot boot twrp.img
What this is supposed to do is boot into twrp temporarily and is gone after restart.
But, on this phone, instead of booting to recovery after the command, it boots to the OS. And when you restart the boot image is gone and you restart into the stock recovery. So, that method doesn't work
Click to expand...
Click to collapse
Yup, pretty much what I experienced too.
I haven't tried extracting boot image and flashing it manually. At this point to be honest, I'm reluctant to put my hands on it again without having a clear step-by-step guide about it.
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I realize I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Ujwal2000 said:
I did write a step by step guide. But i'll leave it to you to decide if it is clear. Ok I relaise I haven't linked the post.
Here it is: https://forum.xda-developers.com/t/...-magisk-on-custom-roms-for-nokia-7-2.4301145/
Click to expand...
Click to collapse
Thanks Ujwal, appreciate it. I'll have a look.