Related
What do I do to avoid permanently bricking this?
Story: Had Cyanogen mod installed on my HDX 8.9"; everything was rosy. Cyanogen kept pestering me with new nightly updates; thought "why not? can't cause any harm now everything's sorted!" Lo and behold, it soft bricked the device. Managed to recover to TWRP. What are my steps from here to get back to the Cyanogen ROM I had before, where everything was perfect (yes, I'm an idiot)?
Just reflash the ZIP you downloaded from XDA.
EncryptedCurse said:
Just reflash the ZIP you downloaded from XDA.
Click to expand...
Click to collapse
I tried; it says failed. Any thoughts?
Edit: Also, if I reinstall the ROM I had, will I have to reconfigure blocking the autoupdates from Amazon? Or will that still all be configured?
BRPW said:
I tried; it says failed. Any thoughts?
Edit: Also, if I reinstall the ROM I had, will I have to reconfigure blocking the autoupdates from Amazon? Or will that still all be configured?
Click to expand...
Click to collapse
Looking through previous posts it appears you have native twrp recovery (not safestrap) with a locked bootloader. If accurate try a factory reset from within twrp (slider under wipe option). This will wipe cache, dalvik and data partitions. You will loose personal data; might want to backup first. Do not wipe system unless instructed.
OTA will remained blocked if you reinstall a previous version of FireOS that was backed up via twrp. If you opt for a fresh install you must use a custom variant that has components removed that could brick your device.
Nexus v4 is a better choice IMO if you can't get CM to work. Avoids the hassles/risks associated with FireOS.
Davey126 said:
Looking through previous posts it appears you have native twrp recovery (not safestrap) with a locked bootloader. If accurate try a factory reset from within twrp (slider under wipe option). This will wipe cache, dalvik and data partitions. You will loose personal data; might want to backup first. Do not wipe system unless instructed.
OTA will remained blocked if you reinstall a previous version of FireOS that was backed up via twrp. If you opt for a fresh install you must use a custom variant that has components removed that could brick your device.
Nexus v4 is a better choice IMO if you can't get CM to work. Avoids the hassles/risks associated with FireOS.
Click to expand...
Click to collapse
Davey, you helped me install this originally; thank you for that!
So just so I'm clear; perform a factory wipe (no personal data that I care about on here), avoiding the wipe of the system partition. I can from that point, install the file on there labelled something akin to 'cm-apollo-nightly05032015.zip" right? And that will bring me back to where I was before this happened.
Edit: If I wipe the data partition, won't that wipe the cm-nightly.zip and other .img's etc?
BRPW said:
Davey, you helped me install this originally; thank you for that!
So just so I'm clear; perform a factory wipe (no personal data that I care about on here), avoiding the wipe of the system partition. I can from that point, install the file on there labelled something akin to 'cm-apollo-nightly05032015.zip" right? And that will bring me back to where I was before this happened.
Click to expand...
Click to collapse
I can not speak to the nightly referenced above. The most recent variant that was prepared/tested for your device is located here. If you browse through the full tread some individuals had luck with more recent nighties while others encountered difficulties.
BRPW said:
Edit: If I wipe the data partition, won't that wipe the cm-nightly.zip and other .img's etc?
Click to expand...
Click to collapse
Likely not as those images should be located in 'Internal Storage' (sdcard) which is a separate partition. You can verify this by locating the images in twrp file manager (under advanced). Use caution while in File Manager and you can mess your system if you accidentally delete/move critical file and folders. Like you mum use to say ... look but don't touch
Comment: Keep in mind you have opted not to unlock your bootloader which leaves your device vulnerable should something go wrong. Also, the build of CM11 you are using is not regularly updated for HDX devices as other cm variants and roms have become available. However, those either require an unlocked bootloader or Safestrap v4. If your are considering the latter be aware there are mandatory steps required to prepare your device for Safestrap v4. In your shoes I would seriously consider unlocking once the current problem is resolved. Risks are negligible (a failed unlock attempt has no adverse consequences) but does involve a bit of work.
Davey126 said:
I can not speak to the nightly referenced above. The most recent variant that was prepared/tested for your device is located here. If you browse through the full tread some individuals had luck with more recent nighties while others encountered difficulties.
Likely not as those images should be located in 'Internal Storage' (sdcard) which is a separate partition. You can verify this by locating the images in twrp file manager (under advanced). Use caution while in File Manager and you can mess your system if you accidentally delete/move critical file and folders. Like you mum use to say ... look but don't touch
Comment: Keep in mind you have opted not to unlock your bootloader which leaves your device vulnerable should something go wrong. Also, the build of CM11 you are using is not regularly updated for HDX devices as other cm variants and roms have become available. However, those either require an unlocked bootloader or Safestrap v4. If your are considering the latter be aware there are mandatory steps required to prepare your device for Safestrap v4. In your shoes I would seriously consider unlocking once the current problem is resolved. Risks are negligible (a failed unlock attempt has no adverse consequences) but does involve a bit of work.
Click to expand...
Click to collapse
Davey,
thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
BRPW said:
Davey,
thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
Click to expand...
Click to collapse
You can access TWRP with the HDX powered off this way: press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen.
BRPW said:
Thanks again for the help so far; got back to CM11. Howevger, did so and realized I haven't installed the gapps.zip with it. Now, I think I'm being a total tool but I can't boot back into TWRP. Any idea how to do so? Sure I'm doing something wrong...
Click to expand...
Click to collapse
Just for clarification, you are not able to access TWRP recovery after powering down your device (full shutdown...not sleep), holding [power]+[vol-up] buttons together and then releasing after the grey logo appears? What happens?
Cl4ncy said:
You can access TWRP with the HDX powered off this way: press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen.
Click to expand...
Click to collapse
Davey126 said:
Just for clarification, you are not able to access TWRP recovery after powering down your device (full shutdown...not sleep), holding [power]+[vol-up] buttons together and then releasing after the grey logo appears? What happens?
Click to expand...
Click to collapse
I was just pressing buttons in the wrong way. I was getting frustrated because I knew I was doing it wrong, heh. Thanks guys! So regarding unlocking the bootloader, do you have some resources I can follow to fully unlock and perhaps find a Lollipop ROM, keep up with the times!
BRPW said:
I was just pressing buttons in the wrong way. I was getting frustrated because I knew I was doing it wrong, heh. Thanks guys! So regarding unlocking the bootloader, do you have some resources I can follow to fully unlock and perhaps find a Lollipop ROM, keep up with the times!
Click to expand...
Click to collapse
I assume you have Minimal ADB and Fastboot installed, so you should grab these drivers, download the software and follow the procedure mentioned here. Requires a little knowledge about the usage of command prompts. Any questions just ask.
Regarding Lollipop check this, or this ROM, note that both are in beta stage. Regarding the first one the 20150814 ROM seems to have issues regarding WLAN only (reboot required to re-enable it), the 20150815 ROM has some issues regarding sound and auto-rotation on some devices (rotation works perfect on my Thor).
Hey guys! Unfortunately I bricked my new HTC Desire 626s while fiddling around with xposed for lollipop after successfully rooting the phone and installing cyanogen recovery. I think if I flash the stock rom on the phone through either adb or cyanogen recovery I can unbrick it, but I have been unsuccessful in finding this file on the internet. Would anyone care to give me a link or upload the stock firmware/rom of this phone? It would really help me out, thank you!
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
es0tericcha0s said:
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
Click to expand...
Click to collapse
Umm.. Okay so I guess I'll give you my phone's info? WAIT DOES THIS MEAN YOU CAN PROVIDE A DOWNLOAD!? IM SO EXCITED, UH OK HERE
- HTC Desire 626s
- Metro PCS USA
- Current firmware version : 1.06.1550.7
ANYTHING ELSE?? IF YOU CAN GIVE ME THAT DOWNLOAD LINK, MY MOM WONT KILL ME:crying::crying::crying: (she's really pissed :laugh Thank you btw!
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
es0tericcha0s said:
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
Click to expand...
Click to collapse
I tried this before my phone got ****ed and it worked:good:! If you can help me dude that'd be great. After uninstalling or changing some stuff in priv-app on my HTC Desire 626s, when I rebooted, it would just stay in a boot loop with the optimizing app message. Any ideas?
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
es0tericcha0s said:
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
Click to expand...
Click to collapse
I believe I uninstalled the dialer and its service in an attempt to replace them with the stock lollipop ones. How do you install TWRP on this phone? My mom has the same phone and its also rooted but hers actually works so I was thinking since TWRP has a nandroid backup setting, I could simply do a nandroid backup on hers and flash it on to mine to see if it will boot up. What do you think? And for the optimizing apps thing, it would finish optimizing, say starting apps, reboot and then optimize again and repeat. Thanks for the help btw, I really hope we can fix this.
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
es0tericcha0s said:
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
Click to expand...
Click to collapse
Do you have the TWRP recovery file for me to download?
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
es0tericcha0s said:
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
Click to expand...
Click to collapse
I installed Cyanogen recovery before flashing Xposed and the uninstaller. I thought you had the TWRP recovery img for my phone which is why I asked. I believe some developers are working on a Clockworkmod recovery for this phone which is basically the same thing as TWRP recovery, right? Anyways I guess I just have to wait until that comes out, but I was wondering if anyone who somehow got a hold of the stock rom could upload it for us to use. It would be really helpful
ClockWorkMod is the recovery that Cyanogen uses. That is able to perform nandroid backups as well.
You have to unlock the bootloader, then if you messed up your stock rom and you've updated it to something newer than what Samsung gives for a stock recoverable rom, you must first use the tmobile vers, let it fail, and then use metropcs vers.
If you messed up recovery or anything it will all go back to stock after flash.
Next just copy superuser zip file to phone, go to download mode and adb flash cyanogen recovery img. Then reboot to recovery, choose to flash update, and find the superuser. zip and flash it, voila.
https://www.mediafire.com/?8o6qtn7hlsec0zj,yqbbzb7divlcvvc
Kitkat, anyone?
Does anybody have a stock KitKat ROM for this device? I'd like to try to bypass the FRP, but am stuck on what must be either a marshmallow or lollipop ROM.
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Issue is fixed
BigCountry907 said:
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Click to expand...
Click to collapse
I ended up fixing it using some ADB commands as noted in the "Well, I may have found..." thread. It'll be nice to have this phone out of my life. The day I had to spend with it was two days too many.
Since there seems to be no way of installing current (and future) patches from stock recovery when the device is rooted, it'd be good to know if someone has information about whether it's possible or not to develop a custom recovery. The old method using 5.02 droidboot won't work because the updates mess up the whole system if you use them. So since we have unlockable bootloaders in 5.1, could there be the possibility of compiling a permanent CWM?
since there seems no one to be working on it at the moment, i'll start a few tries myself and document the progress in this thread. Feel free to help or comment.
For now, i', stuck at unlocking the bootloader and still don't know why. "OEM unlock" was set in the developer options, rebooted to fastboot and tried "fastboot oem unlock". Results as attached. :\
I'll google a bit around and see if i can get it working....
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
He's asking about a recovery that can be installed to the recovery partition, not just tethered.
It's possible, but we'd need somebody to build one. I tried one a while back from the Zenfone 2, but it didn't want to boot.
jumpup said:
What's the question - how to load the tethered CWM when you're running Lollipop 5.1? Because I can do that and provide insructions.
Click to expand...
Click to collapse
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
toxic_garden said:
no, it's not about the tethered one. The method booting tethered CWM won't work anymore once you installed the stagefright update. We'd need a 5.1 post-stagefright boot.img and system.img for that. And as the bootloader can be unlocked now, i think it might be the better solution to build a untethered CWM for the future.
@xBIGREDDx: do you have any good step by step instructions for setting up a build environment for that? The most things i found we not that complete. E.g. where to find the "vendor-specific files" and what they even are.
Click to expand...
Click to collapse
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
@xBIGREDDx made some instructions on this. Let me find it.
http://forum.xda-developers.com/showpost.php?p=64391058&postcount=16
This is not straightforward, but you *can* get to tethered CWM and root your 5.1 system. I did exactly this.
jumpup said:
There is a means of booting to tethered CWM after the Stagefright update. You must first flash the old 5.02 droidboot firmware via Intel Flash Utility (while in bootloader mode). Afterward, you can run the tethered CWM.
Click to expand...
Click to collapse
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
toxic_garden said:
that'S exactly the problem: if you flash the 5.02 droidboot over a system that applied the stagefright fix, you'll completely mess up the system. The fix contains a new boot.img and patches to the system.img, so even rolling back after super su to the stock 5.1 boot and system.img will get your tablet in a messed up state. If there'd be a way to dump the actual system and boot img without root, we could still use this method, but i don't know of one.
Click to expand...
Click to collapse
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
jumpup said:
*OH*! Now I understand. Could you post a screenshot of the build version with the Stagefright patch applied? I want to compare to mine. See attached.
Sent from my Venue 8 7840 using Tapatalk
Click to expand...
Click to collapse
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
However, I have always used a multi-tiered backup system:
* Titanium Backup (FULL on Sunday, INCREMENTAL every other day)
* Online NAndroid Backup (One per week using CWM format)
Each app's backup data syncs to the home NAS and Dropbox once a week.
I thought I had the Stagefright fix already in place. That's why I wanted to compare build/version details with a device that has the fix installed.
jumpup said:
With my current Android installation, CWM does not seem to be able to back up the data partition which is unfortunate.
Click to expand...
Click to collapse
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
toxic_garden said:
Yeah, /data is encrypted, so CWM can't access it for backup.
And since the stagefright fix won't install when it recognizes the /system partition as "tempered" (which means e.g. having the superSU binaries installed), it's pretty hard to keep root. That's the trap we're in.
back to topic: i'm gonna boot my linux netbook today and see if i can get the "oem unlock" option working...
Click to expand...
Click to collapse
D'oh. I should have remembered about the data encryption. Need more caffeine
If you need anything tested or confirmed in the field, I'd be glad to help.
Sent from my Venue 8 7840 using Tapatalk
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
jumpup said:
The build number of a 5.1 install prior to Stagefright is different as well. Ends in 171200DEL instead of 173600DEL post-Stagefright patch.
Click to expand...
Click to collapse
oops you're right. Didn't even notice.
First steps forward: it seems like it's not possible to unlock the bootloader with installed sf-patch. No matter which version of fastboot i tried, i always got "FAILED: (some text i can't remember)". After downgrading to 5.1 stock firmware, unlock was possible. So as i now at least have the possibility to boot another recovery, i'll try setting up the build env. The Recovery Builder from CWM seems to be out of order at the moment.
toxic_garden said:
Here's mine. Software version doesn't seem to be changed, but the kernel is different...
Click to expand...
Click to collapse
I now have the Stagefright patch installed. Used the 5.02 droidboot temporarily to engage tethered CWM and install SuperSU. Reflashed 5.10 droidboot and firmware before proceeding. All is well. As you mentioned, it makes for a mixed 5.1 boot system, but I simply cannot live without root.
Here are the new build/version details:
After taking your advice and flashing the sg droidboot, my IWFI version is in line. I'll see if any system issues occur.
Is anyone still working on the 7840? Would be nice to have TWRP or CWM
I've been poking around on my 7840 on and off for a few weeks now. I seem to have verified that, after unlocking the bootloader, you can modify the boot and recovery partitions to your heart's content. However, any time I rebuild the kernel myself, I end up back at the "Dell" screen, frozen. Any other files are free game.
Assuming that the kernel needs to be signed using some tool I haven't figured out yet, I'm going to see if I can get a version of CWM working w/ the stock kernel. I tried dumping the version from the tethered recovery onto the recovery.img, but running it results in a black screen. I'll keep poking around though.
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
I am just getting back to messing around with phones after about 5 years. So many things have changed and I am trying to get answers here as well.
I used TWRP and Magisk to root my phone. Installing TWRP will not wipe your data as it is flashed to a different partition but to install TWRP you have to unlock the bootloader and that will wipe your userdata. And no, I don't believe there is any possibility of rooting without unlocking the bootloader. If you decide you want to go back to stock, there are stock roms available and you can re-lock the bootloader on the N10 so you should be able to set it back to just like it was when you first bought it. I say should because I have never done it, just read that it can be done when I unlocked and flashed mine.
I wish I could be of more help but so many things have changed in the years since I've been away from doing this stuff I feel like a total noob again.
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
No I do not believe there's a way to gain root without flashing anything. There's no need to backup anything you can always use the MSM download tool to restore your device. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ You should be able to find most of the stock imgs on here already if you'd really need to flash back. I'm no expert either, just my experience with this phone in particular has been pretty straightforward. I never backed up anything lol.
Twrp is iffy i made a backup I'll never use, check out the post about flashing international rom to tmo and metro devices, that's my backup. Also you can run 11.0.3/2 firmware and boot 11 gsi's the post about lir rom has the info. Flash the product_gsi.img referenced there, I have never deleted my product partition and I only leave oos ten installed long enough to take ota's. There are more roms in the source forge page referenced with lir rom post. Flash magisk via recovery, either side load or twrp, pay attention that it flashes partition sda14(super image) or wifi breaks.
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
draymond1987 said:
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
Click to expand...
Click to collapse
Why don't you use fastboot environment and flash the January factory image without wiping data and then restore root by flashing the new patched boot image from the January update?
phaino00 said:
Why don't you use fastboot environment and flash the January factory image without wiping data and then restore root by flashing the new patched boot image from the January update?
Click to expand...
Click to collapse
I don’t have a computer at all, at least for a little while. I’m away from home, and I don’t have access to somebody else’s PC, either :/
draymond1987 said:
I don’t have a computer at all, at least for a little while. I’m away from home, and I don’t have access to somebody else’s PC, either :/
Click to expand...
Click to collapse
That answers my question. Sorry, I don't have a copy of that build. Just realized you wrote 'nor do I even have a computer...'
phaino00 said:
That answers my question. Sorry, I don't have a copy of that build. Just realized you wrote 'nor do I even have a computer...'
Click to expand...
Click to collapse
I’ll have to edit that part then
draymond1987 said:
Long story short, I flashed my patched boot image without backing up, so I can’t restore via magisk. THEN I flashed a custom kernel. I have absolutely no way to OTA to January, nor do I even have a computer for awhile. I tried flashing the boot image via EX Kernel app but it doesn’t stick. Probably because of the modified files of the custom kernel.
So, does ANYBODY have A1 (global) kernel, that can be flashed via EX, or any other app?? I’m sure vbmeta might need to be included too. I’m desperate, and yes, it was a rookie mistake on my part. I always get Status error 1 when I try applying update via stock recovery (via sdcard option). OTA is completely broken and just refuses to do anything.
Thank you, in advance!!
Click to expand...
Click to collapse
Here you go this is from the December A1 Firmware image. enjoy
LeoD said:
Here you go this is from the December A1 Firmware image. enjoy
Click to expand...
Click to collapse
Is there a way I can make a zip, to flash via EX’s app?
You’re a live saver, so far!
Why don't you wait until you get a PC.
If you keep fooling around. You will have no PC and no P6.
Too risky!
vandyman said:
Why don't you wait until you get a PC.
If you keep fooling around. You will have no PC and no P6.
Too risky!
Click to expand...
Click to collapse
You make a really decent point. Guess I’m just antsy to have all the fixes and not be on a buggy firmware.
The tools in This thread may help.