Database Users

Fixed 6P bootlooping, now i want to update to Oreo

Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.

johnnyphive said:
Hi all, I posted this in the 6P bootloop thread, but didn't get a response. As that is a pretty LONG thread, i'm thinking my question may have gotten lost in the jumble.
Quick run down.
A few months back my 6P started the BLOD. I found the fix listed on these pages, applied it, and have been happily using my phone ever since. Phone is bone stock 7.1.2 other than the TWRP recovery and the modified EX kernel for 4 cores.
Since the fix, my phone FINALLY got the OTA update to go to Android 8.0 and i obviously want to get it done. My concern is HOW to do this without causing more headache.
Can anyone point me in the right direction? Should i use the OTA update or download the factory image from Google?
I've got some knowledge as i used to be into the "rooting" scene back in the day, but haven't for a while, so i feel a little lost.
Thanks for any help.
Click to expand...
Click to collapse
Well, for starters do NOT take the OTA. It will either fail or boot loop your phone. Due to the fact you have a modified boot.img you will need to update manually using fastboot with the full image. Re-apply the modified kernel after you finish updating the partitions, but BEFORE booting the first time. You can follow most guides on how to manually update a full image using fastboot, just add the step of flashing the modified kernel before booting.

Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.

johnnyphive said:
Thanks for the reply and the help. If i could ask for a little more help, as this is my only phone.
Can you explain the difference between the modified boot.img and the modified kernel?
If i download the factory image from here (https://developers.google.com/android/images) is it ok to the get the latested one (Nov 2017) or do i need to get the original one (Sep 2017 as i'm on Fi)
Once i flash the factory image, is it going to replace the modified boot image as well as the modified kernel?
Follow the OP on this thread (https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279) in the downloads section there appear to be 2 files i would need, the "Boot.img from stock 6.17, 8.0 firmware" and "EX kernel version 5.03". Am i understanding that correctly?
Like i said, this is my only phone, and i'm probably just being overly paranoid about bricking it, but any clarification would be greatly appreciated.
Click to expand...
Click to collapse
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:

v12xke said:
Use the latest November image. The boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted. When you flash the new boot.img contained in the Google image, it will overwrite the patched kernel. You then need to re-patch it by installing EX kernel before booting. EX writes to (modifies) the stock boot.img. There are also pre-modifed boot.img files floating around. You will probably get more detailed help in the dedicated thread. Learning to flash manually (or remember how) is not really a big deal and a necessary skill for modding (and for getting yourself out of trouble). Good luck. :good:
Click to expand...
Click to collapse
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?

johnnyphive said:
Ok, so 1 last time (sorry)
1 - Downloaded the latest 8.0.0 factory image from google (this contains the bootloader, radio, and partitions (.zip).
2 - Get phone to fastboot and apply the above 3 new images
3- before rebooting, flash oreo4core (new, modified boot.img), TWRP recovery.img
4- reboot to recovery (TWRP) and apply the modified EX kernel
5 - reboot and (hopefully) profit
Am i missing anything, or doing anything that isn't needed?
Click to expand...
Click to collapse
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.

v12xke said:
<<Disclaimer: I don't use the 4 core kernel, so I don't know if it comes with installer script or someone has just modified the latest boot.img>> Unzip the "partitions" zip you refer to and extract those image files to the same folder as bootloader and modem. For example, you can keep TWRP recovery if you don't flash the recovery.img. That is how you preserve your custom recovery. So in other words you'll now have a folder (your ADB folder?) with 5 image files.... bootloader, radio, boot, system, and vendor all in one folder. <<Note: it is my understanding you just substitute the latest oreo4core file (should be boot.img?) If this is true, copy that file into your ADB folder and let it overwrite the stock boot.img. Stop. Copy over flash-all.bat, change the *.bat extension to *.txt and open in notepad. You will see (and can copy/paste) the fastboot commands to get you started with bootloader and radio. Then flash the last 3 (boot, system, vendor). At this point you can reboot into the OS. Since you substituted the oreo4core boot.img file for the stock boot.img there is no need to use TWRP to flash anything. That and since you skipped flashing the recovery.img, TWRP is still there.
Click to expand...
Click to collapse
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied?
Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup

johnnyphive said:
Thank for the help! Everything seems to be up and running. I know you said you don't use the "4 cores" (can only assume your either on a different phone or yours isn't affected by the BLOD), but do you know if i still need to apply the EX kernel update, or know of a way to tell if it's already been applied? Thanks again for all the help. I was pretty much in the right direction, but being as how i'd been away from it for a while, i wanted some backup
Click to expand...
Click to collapse
I don't think you can flash EX kernel from now on. I think you have to use a modded boot.img that will contain his kernel/ramdisk. This is my guess. You really should be getting your information in the dedicated thread where everyone is actually installing and using it. Google "oreo 4 core" and you will find the XDA thread is the first hit. Good luck. :good:

Need backup img for tb-x304f

Hi I have tb-x304f.
I installed TWRP to get root access and by mistake I deleted my backup and now I can't update to 8.1.
So can someone give me backup img?
Thanks :good:

AlmogEd said:
Hi I have tb-x304f.
I installed TWRP to get root access and by mistake I deleted my backup and now I can't update to 8.1.
So can someone give me backup img?
Thanks :good:
Click to expand...
Click to collapse
They don't have images like Google devices, but flashable firmwares.
http://lenovo-forums.ru/files/category/287-lenovo-tab4-a10-tb4-x304l/ has it, second from the bottom, underneath all the OTAs. Double check that you got the 4F and not the 4L one.
I don't have this device so I cannot help you with it if you have issues, nor can I say this will work for you. I also really don't profess to be any kind of an expert so do ask in one of the other Tab 4 threads if needed... but I do have the TB-8704F & have restored it to stock several times and I would assume the devices to be identical in process so I can give you a guide if needed! The general path is:
Download the zip and extract it
Download and install Xiaomi Mi Flash (some say to use QFIL but it often throws up errors and sometimes requires flashing in multiple passes, when Mi Flash doesn't)
Plug your device into your PC
Put your device into Emergency Download Mode, easiest way for you is probably to first reboot to TWRP which you luckily already have installed
In TWRP go to Advanced>Terminal>type Reboot EDL
Open Mi Flash and it should see your device. Click Select, open the images directory in your extracted firmware and it should detect the flashing process XML
Click Flash, then leave everything to complete
I will warn you that you will lose everything on your device. There's no way around this that I know of, nor would I suggest it anyway. Just back up everything before doing the restore.
+ Good luck! But honestly I'd first weigh up whether you really want to update to 8.1 since you're already on a perfectly-working device. They already pushed the OTA once and had to retract it because of the amount of serious errors it had - but that's your call entirely.

AlmogEd said:
Hi I have tb-x304f.
I installed TWRP to get root access and by mistake I deleted my backup and now I can't update to 8.1.
So can someone give me backup img?
Thanks :good:
Click to expand...
Click to collapse
bro help me unlocked the bootloader yesterday and flashed recovery but then decided to downgrade the system with system sparse image in fastboot mode provided by o.p. of rooting thread, but now it is not booting up just showing lenovo logo and in fastboot mode again

Help needed! Qualcomm Crash dump after trying to reinstall magisk upon upgrade to Android 11

Hi,
Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error.
After searching, managed to boot into bootloader, however wondering how do I now boot my phone - I have downloaded and installed latest recovery (3.5.2_9.0-fajita.img) and am able to boot into recovery as well as bootloader/ fastboot.
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Any help woud be massively appreciated!

The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc

Extracted boot.img and used fastboot command : fastboot boot boot.img, but this doesn't seem to have worked as well. Just thinking aloud what else can be done?
Edit - It now tries to boot, but then seems to go into OnePlus Recovery (from the chinese characters displayed along with an option to choose English language)
sam_htc_touch said:
Have also downloaded the zip file for Android 11 stable version - OnePlus6TOxygen_34.J.60_OTA_0600_all_2108052232_8c516d0cce8795.zip
Question - What do I need to flash this? adb commands don't seem to be working, only fastboot commands seem to. Can I just "push" this zip file in fastboot or is that only for img files?
Click to expand...
Click to collapse

Masamune3210 said:
The update to 11 does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to 11 is finished though, so you can still have root.
In your case manually upgrading to 11, letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc
Click to expand...
Click to collapse
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?

sam_htc_touch said:
Hi, thanks for responding. I am not even concerned about root right now, just want my phone to boot up first Any suggestions on what can I try?
Click to expand...
Click to collapse
For the benefit of others, all sorted finally y'day evening. Plenty of helpful tips in this thread
(Well I was able to boot into Android 11.1.1.1 - no root as yet, but I will perhaps look into that later, can't stand those annoying ads :-D )

How To Guide Development for the Cricket Dream 5G

For starters, there's no thread for this device and I wasn't sure where to put it.
Secondly, me and a friend have been tinkering around with the Cricket Dream 5G and have successfully unlocked the bootloader and obtained root access. Unlocking the bootloader was the easy part. Anyways we've made a full device backup before rooting. I have a magisk patched boot.img. Just unlock the bootloader, flash the patchedboot.img and install magisk. There you go, you have root
WARNING
DO NOT FLASH A MODIFIED SUPER.IMG IT WILL BRICK YOUR DEVICE You can, however modify your system, like removing or adding apps.
I bricked mine because I flashed a modified super img. It's stuck in preloader. Still learning this dynamic partition scheme, it's weird
Full backup on Google drive currently, gonna be moving to mega=>
https://mega.nz/folder/UARQCD6I#8CSNy43GWo6XjEKk_mlldw
Links below, all links are thru mega
Original boot=> https://mega.nz/file/JBAhHSTQ#Aw-GQQ6-StdNAhLsu0vdonNDXcBo4wXI8xEalQ99X2Y
Original boot is in bin format but magisk recognized it and patched it.
Patched boot.img=> https://mega.nz/file/hEJjlaxI#e2DdzvNkq1421uESaSQR4ZP_-CHvt6I_IDCEpyYDZqA
And an app for the magisk modules, not my work, only sharing=> https://mega.nz/file/VAQR0ARI#IUT42ycW5bbb8xVSDhDthREJzr1GEd5WHW0xZbkE8Ts
Also, relocking the bootloader after flashing the patched boot img, it will say there's no OS installed. It's still there. Just unlock it and it'll boot. Not sure why. I believe it's the secure boot being on
Just send a message on here if links are broken
If enough people are on this maybe we can get a working twrp
Update: twrp available here => https://forum.xda-developers.com/t/development-for-the-cricket-dream-5g.4414603/
If anyone uses gpay, unlocking the bootloader will break it. But I know a workaround if anyone wants it.
@Welkwo is behind the twrp process.
My post is just a guide, really.

Thank God! I have numerous phones but for some reason, I have my main number through a sim card thast's unfortunately tied into this phone.. I have been searching online for the stock firmware for this p;hone for a long time with no conclusive results, so upon my search for it this morning, I came acrfoss your post and I almost craped my pants. Thank God.. noot for the almost crapped pants, but for the efforts of you and your friend.. Thank you so much.

We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g

Is it not completely slow as **** to you?! It's nowhere near what my OnePlus 5T , Redmi Note 8 nor Motorola Ace One can do nor did I expect it to be but God damn it's just super slow to me..
By the way should I flash boot_a and boot_b in fastboot because when I did the first time when I booted back up it kept making Google framework stop responding

Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
Nevermind.. I retract m yprevious statement.. I just got root and I'm blown away at the sactual speed of this phone. It's such a night and day fgucking difference betweeen having root and not.

Sorry I've been absent. My work has me drained and I've bricked my dream 5g. I messed with my super partition and it is stuck in preloader.
Also I only flashed the boot for the current slot via fastboot

We need to create a scatter file, not quite sure how. Any help is appreciated

yooo... are you guys just needling the scatter to make a twrp recovery?

DrScrad said:
yooo... are you guys just needling the scatter to make a twrp recovery?
Click to expand...
Click to collapse
Honestly I'm not sure. My friend is behind the twrp process. We got one to boot but it don't recognize the partitions so it won't even boot to the os.
Do you have a scatter file? If so please share and I'll also attach it to the op if I have permission, lol

I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did

Josephdbrewer25 said:
I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did
Click to expand...
Click to collapse
Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com

lopestom said:
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah. Your point? That's the friend working on twrp

No TWRP file?

DragonPitbull said:
No TWRP file?
Click to expand...
Click to collapse
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com

Josephdbrewer25 said:
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com
Click to expand...
Click to collapse
I not need that. but anyone need permission access.
Josephdbrewer25 said:
Yeah. Your point? That's the friend working on twrp
Click to expand...
Click to collapse
Okay. But the DT in the github is your.
I need access of DT for help and if you or users need help about TWRP improvements. Looking my post about collaborator.....
UPD: I donwloaded your bot_a.bin (I need time for donwload super...img file) and I'm working with that to process informations & simple DT. I prefer collaborator than creating new DT in the github. But if I not receive any answer here so i go create new DT in the github and compiled TWRP file for anyone test.
The question now is: Who is the tester?
UPD1: super_backup_2022-03-10_02-34-47.img from MEGA is not good. 3 times trying donwloading file..... Can you put that as zip file in the GDrive?
UPD2: The super.img file was downloaded.
I need some informations from device. But at this point I'll write in the TWRP Cricket Dream 5G thread. .
If someone can put informations so answer in that thread.

Not sure if I should post here or at the TWRP thread but I think I've fixed the problem with being stuck at preloader after flashing modified super img. I got it to work by flashing the modified super img, locking bootloader and unlocking bootloader.
Can someone else also verify that this works?
Edit: Nvm I've been flashing the wrong super img

UPDATE: TWRP IS NOW AVAILABLE FOR THIS DEVICE.
See this post: https://forum.xda-developers.com/t/twrp-for-cricket-dream-5g.4418963/post-86858605

Kinda new to this, but I have a problem I am hoping someone knows about...I unlocked bootloader then i entered the fastboot flash command ...my phone died, as in shut off, power button does nothing, plugging it in to the computer does nothing, and charging does nothing. Thoughts? I'm assuming its dead? Thnx for listening lol
correction, i entered fastboot reboot fastboot

You know what? IT'S ALWAYS SOMETHIN'! I just got a Cricket Dream 5G for free (promo) and the bloody thing won't read a Micro SD card unless it's formatted to Fat32. Which means the largest card it'll use is a 32gb card. I mean WTH? I've never seen anything like this. If I put in a card formatted to exFat or NTFS it says it's corrupted. A Fat32 card is fine. Anyone else run across this? Just another X-File conspiracy against me.

so...no one knows anything??? anyway to fix this??? i noticed when plugged into computer it makes the connecting noise followed by disconnect noise a few minutes later, and button combos seem to change the timing of said noises but nothing shows up under adb or fastboot devices....help!!!!!

[Dump][Hoki] System.img needed for Fossil Gen 6

Hey, I just bricked my watch and dont have a system.img backup to restore the watch. Can anyone dump the system.img via TWRP or any other means ?
Thanks

If you get a hold of one, I could also use it. I didn't expect the OTA to verify the system partition with an unlocked bootloader.

@cheger32 if you can share your partition dumps except the user-data, I'll be grateful. I managed to installed system from an old OTA, but sadly, I have now lost the functionality to update my watch. It cannot even pass the basic verification from the update app. I am stuck at wearOS 2.30 and minor update is to go for 2.32. One user did contacted me for help, but he was on WearOS 3 and I don't want to do something, that may permanently brick my watch. Not in a mood for a costly stone at the moment.

Bumping to say that we weren't able to source a proper system image for this device. Anyone with this device and a few moments of time that would be willing to do a quick system dump would be greatly appreciated. Step by step instructions can definitely be provided.

Malvik said:
Hey, I just bricked my watch and dont have a system.img backup to restore the watch. Can anyone dump the system.img via TWRP or any other means ?
Thanks
Click to expand...
Click to collapse
Do you still need the backup?

ricardollreis said:
Do you still need the backup?
Click to expand...
Click to collapse
It would definitely still be useful, if it's still available.

I'm damn stuck in fastboot mode after trying to downgrade to Wear OS 2.30 using the image file provided by Malvik (i converted the system vendor to .img files but it didnt work haha)
@Malvik is it possible to convert boot.img.p from your WearOS 3 OTA file to boot.img and flash it ? renaming the file dosent work