Database Develop

Battery problem after 6.0.1 factory image

Hi all,
I just recently installed the Marshmallow 6.0.1 factory image via fastboot and all seemed well till I looked at the battery stats whilst plugged in.
I'm confused as to why or if its a bug or just my battery about to give up on me?
Whilst plugged in it states 4000% charge but why?
When unplugged it fluctuates and says 20 minutes remaining and keeps going up and down.
Any help would be appreciated.
FYI I'm not rooted or anything just an unlocked stock bootloader with no tampering as yet.

ignore it, its a bug.

simms22 said:
ignore it, its a bug.
Click to expand...
Click to collapse
Thank God! Now I can stop looking for replacement batteries..

MarkPH123 said:
Thank God! Now I can stop looking for replacement batteries..
Click to expand...
Click to collapse
ive read three threads today about people that flashed 6.0.1, and are having the same issue.

flashed 6.0.1 - stock - don't see that battery problem (yet)

jj14 said:
flashed 6.0.1 - stock - don't see that battery problem (yet)
Click to expand...
Click to collapse
Lucky for you ey

I had this issue with a dirty flash and running Despair R39. Doing a proper clean flash fixed the issue for me.

same issue here!

Another thread on this topic.. It was suggested that flashing the boot.img fixed the issue for another user.. Going to try that once I get home since I only flashed the system and radio images

I had the problem and flashed imgs in the following order: bootloader, radio, boot, system and cache.
It seems to have fixed the issue.

Started from scratch, but I can't get it to go away. Annoying bug.

N3V3RS3TTL3 said:
Started from scratch, but I can't get it to go away. Annoying bug.
Click to expand...
Click to collapse
Yeah, I started fresh too but I've fixed it.
If you still have the extracted image from Google, you'll want to flash the boot.img again via fastboot.
In case you don't know the commands, make sure you're in boooader/fastboot mode and then 'fastboot flash boot boot.img'. Then reboot.
That's what I had done and all is well now!

MarkPH123 said:
Yeah, I started fresh too but I've fixed it.
If you still have the extracted image from Google, you'll want to flash the boot.img again via fastboot.
In case you don't know the commands, make sure you're in boooader/fastboot mode and then 'fastboot flash boot boot.img'. Then reboot.
That's what I had done and all is well now!
Click to expand...
Click to collapse
I get the boot loader "you phone is not secure" message if I use MMB29K's boot.img
I also have a modified system image (DPI, removed apps, and UI audio changes)
Sticking with the MRA58K modified boot.img and MMB29K system image, I have 4000% battery bug

Flashing the boot.img worked for me as well. Seems like the fix for everyone I have seen. Here it is one more time.
'fastboot flash boot boot.img'.

Xperia V soft bricked, please help!

Hi guys. I am in desperate need of your help.
I have a Sony Xperia V LT25i which used to have a CyanogenMod Rom 12.1 up and running and TWRP 2.8.
I decided to update TWRP from the Bootloader, hoping I could update it to later on to CyanogenMod 13.0, and stupidly picked it to update on boot instead of recovery and now my phone is bricked. it does nothing but load the "Sony" logo, then dim.
I tried fastboot from the computer, it does not detect my phone. I tried Sony Mobile Flasher, it does not detect my phone, i.e. I managed to flash most of the files from a factory rom except system.sin.
I can't get into recovery(Volume up + power button). I am able to get into fastboot and bootloader mode over the phone (blue and green lights), however, my computer does not detect it at all (I tried all the drivers I found on the internet, but not success).
Any suggestions? Please?

mrainman said:
Hi guys. I am in desperate need of your help.
I have a Sony Xperia V LT25i which used to have a CyanogenMod Rom 12.1 up and running and TWRP 2.8.
I decided to update TWRP from the Bootloader, hoping I could update it to later on to CyanogenMod 13.0, and stupidly picked it to update on boot instead of recovery and now my phone is bricked. it does nothing but load the "Sony" logo, then dim.
I tried fastboot from the computer, it does not detect my phone. I tried Sony Mobile Flasher, it does not detect my phone, i.e. I managed to flash most of the files from a factory rom except system.sin.
I can't get into recovery(Volume up + power button). I am able to get into fastboot and bootloader mode over the phone (blue and green lights), however, my computer does not detect it at all (I tried all the drivers I found on the internet, but not success).
Any suggestions? Please?
Click to expand...
Click to collapse
Which operating system are you running on your PC? Did you currently update it to windows 10, or a newer windows 10 version? If so you'll have to disable driver signature and install the drivers again.

St.Jimmy90 said:
Which operating system are you running on your PC? Did you currently update it to windows 10, or a newer windows 10 version? If so you'll have to disable driver signature and install the drivers again.
Click to expand...
Click to collapse
I am running windows 10 with its latest updates, and had had it for a while. I did disable driver signature and reinstalled the drivers but that did not fix it.
I am currently able to identify my device in fastboot as
PSDN: CB5A1WUDZ0&ZLP fastboot
I tried to flash a recovery.img to it, but it says it fails with
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: "Partition not found" ).
finished. total time: 0.693s
Click to expand...
Click to collapse
any other advice, please?

mrainman said:
I am running windows 10 with its latest updates, and had had it for a while. I did disable driver signature and reinstalled the drivers but that did not fix it.
I am currently able to identify my device in fastboot as
PSDN: CB5A1WUDZ0&ZLP fastboot
I tried to flash a recovery.img to it, but it says it fails with
any other advice, please?
Click to expand...
Click to collapse
What happens if you extract to boot.img from your current 12.1 and try to flash it as boot.img?

St.Jimmy90 said:
What happens if you extract to boot.img from your current 12.1 and try to flash it as boot.img?
Click to expand...
Click to collapse
you are reading my thoughts. I just did that, and I have a bit of progress (I guess). I am in cyanogenmod recovery mode. however, I do not know how to proceed from here. I have the cyanogenmod 13.0 archive on my sdcard, however when I try to install it it says
install failed.
install /storage/540D-CA26/cm-13.0-20160920-nightly-tsubasa.zip finding update package.....
verifying update package....
installing update....
user data unifier tool
sdcard partition still contains files.
please copy your data from internal sdcard. do not format the partition yourself.
if you are sure you want to remove sdcard, and accept the losses, flash this zip again.
the device needs to be converted to unified userdata partition.
please read the information above.
failed to install /sideload/package.zip
please take note of all the above lines for report.
installation aborted.
Click to expand...
Click to collapse
I tried flashing it again, it kicks the same error.

mrainman said:
you are reading my thoughts. I just did that, and I have a bit of progress (I guess). I am in cyanogenmod recovery mode. however, I do not know how to proceed from here. I have the cyanogenmod 13.0 archive on my sdcard, however when I try to install it it says
I tried flashing it again, it kicks the same error.
Click to expand...
Click to collapse
Ok, your phone is recovered. I guess you're trying a CM13 nightly. It should work at the 2nd or 3rd time, though I'm not quite sure. Otherwise you could try to boot up to your Cm12.1 and install TWRP via a terminal emulator and the dd command. To me TWRP is way better than the CM recovery

St.Jimmy90 said:
Ok, your phone is recovered. I guess you're trying a CM13 nightly. It should work at the 2nd or 3rd time, though I'm not quite sure. Otherwise you could try to boot up to your Cm12.1 and install TWRP via a terminal emulator and the dd command. To me TWRP is way better than the CM recovery
Click to expand...
Click to collapse
It does not boot to my CM12.1. It simply freezes to "Sony" logo. however, if I hold volume up + power button it goes into recovery mode. should I keep on trying on installing 13.0? I tried about 4-5 times, still kicks the same error.

mrainman said:
It does not boot to my CM12.1. It simply freezes to "Sony" logo. however, if I hold volume up + power button it goes into recovery mode. should I keep on trying on installing 13.0? I tried about 4-5 times, still kicks the same error.
Click to expand...
Click to collapse
You could also try Cm14, it runs pretty good on my Xperia T. Unifying will wipe your internal storage though, so be aware. If you still got data on it you should try to flash CM12.1 again and safe your data

St.Jimmy90 said:
You could also try Cm14, it runs pretty good on my Xperia T. Unifying will wipe your internal storage though, so be aware. If you still got data on it you should try to flash CM12.1 again and safe your data
Click to expand...
Click to collapse
I was able to boot a TWRP from an unofficial CyanogenMod 12.1. I think I got it from here. I do not own an Xpire T, so my latest version of Cyanogen would be 13 ? (I Guess)
Thank you so much for your help!

mrainman said:
I was able to boot a TWRP from an unofficial CyanogenMod 12.1. I think I got it from here. I do not own an Xpire T, so my latest version of Cyanogen would be 13 ? (I Guess)
Thank you so much for your help!
Click to expand...
Click to collapse
Awesome!
Here you go for CM14:
http://forum.xda-developers.com/xperia-t-v/v-development/rom-cyanogenmod-14-0-xperia-t3461746

St.Jimmy90 said:
Awesome!
Here you go for CM14:
http://forum.xda-developers.com/xperia-t-v/v-development/rom-cyanogenmod-14-0-xperia-t3461746
Click to expand...
Click to collapse
Cheers! Your support means a lot!

mrainman said:
Cheers! Your support means a lot!
Click to expand...
Click to collapse
No worries mate, everyone runs into trouble once in a time and needs assistance I'm really glad it worked out

Oneplus 3T + ResurrectionRemix.

Hi guys!
Hopefully you can assist with my issue. It's the first time i'm having these complications with a device.
So i flashed TWRP (Which worked fine) And then flashed RR from within TWRP (The first install.)
If i have to enter TWRP after a full setup it's going to end up differently.
When i try going into TWRP the next time (Mainly for updates.) My device kinda softbricks?
I just get a black screen with nothing on it after the TWRP splash screen.
*shrugs* i think, and reboot my device, BUT! My rom will now start to setup again, but with a lot of com.android. errors.
This leads me to the only solution of reflashing TWRP + Getting the new RR Update = And starting the process all over again.
At this point i'm pretty frustrated with having to set it all back up every time i glance an update.
What could be wrong? Did i do this correctly?
THANKS!

U must reflash diffrent twrp ithink blue sparks is without issues

psychemisha said:
U must reflash diffrent twrp ithink blue sparks is without issues
Click to expand...
Click to collapse
Do you mean different kernel? It seems noone is having issues with RR and nothing is stated in the "Whats not working" section.

https://forum.xda-developers.com/devdb/project/dl/?id=22806
Flash this

which RR version you installed?
which twrp are you on?

dogmatism said:
which RR version you installed?
which twrp are you on?
Click to expand...
Click to collapse
3.0.3-1 from the TWRP Website. Should i try the above mentioned?
Thank you for the answers so far.

psychemisha said:
https://forum.xda-developers.com/devdb/project/dl/?id=22806
Flash this
Click to expand...
Click to collapse
This did the trick, or atleast for now! Thank you so much. Must have missed something, but wasn't showing.

Bootloop with no recovery or fastboot options

Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks

Did you flash anything?

Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.

VD171 said:
Because you compromissed the boot process.
When your device try to boot, it make some checks first.
You need to flash the stock MIUI rom again.
Click to expand...
Click to collapse
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?

jeromeof said:
Yes, thanks, I imagine that is what happened but how can I flash when I can't get into recovery or get to into fastboot?
Click to expand...
Click to collapse
You need to flash the stock MIUI rom again using SPFLASHTOOL.
[GUIDE] How to properly solve the errors of the SP FLASH TOOL for MERLIN ? (Redmi Note 9 / Redmi 10X 4G)
WARNINGS: Keep your backup files safe and secure ! If you can, encrypt them. If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again ! Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and...
forum.xda-developers.com

jeromeof said:
Not sure what I did but I am now stuck in a bootloop where it reboots every 10 seconds or so but I can't get into recovery or get to fastboot no matter how I press and hold the Power and up or down volume buttons? Is there any way out of this? I left the phone overnight and the battery wasted but as soon as I plugged it into the USB on my laptop again it went back to the bootloop.
So, just wondering is there a special sequence of buttons to press on the device, that I don't know of, when this happens?
Thanks
Click to expand...
Click to collapse
If you have have adb drivers installed in your pc, try connecting your phone and open power shell. Then try this command.
Code:
adb devices
If it shows the device, then simply command
Code:
adb reboot fastboot
and flash the fastboot rom.
If not works, then follow VD171.
Also you should read threads carefully before flashing anything. Like there a tread about pixelplus UI. And they recommend to force reboot when you see the boot logo. To avoid boot loop.
Good luck

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Don't flash pixel experience. It's unofficial and it's and old version. I recommend you to flash pixel extended after solving and flashing latest fastboot rom. It's official and provide update every month. This rom is also a pure aosp based Stock rom.
Always read new treads before deciding
Redmi Note 9 ROMs, Kernels, Recoveries, & Other De
Improve your Redmi Note 9's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com

jeromeof said:
Yes, I had switched from MIUI to PixelExperience (and I had unlocked the bootloader etc to do this) but I believe I did something wrong in the process and both my IMEI (which were still reported correctly) were not working - I thought this might be some firmware issue so I had flashed an update firmware but that did not help. So I went and flashed the Engineering ROM to see would that help resetting the device.
But that didn't help and I had lost TWRP so I refreshed TWRP and at that point it went into the bootloop. What I don't understand is why I can't get back to fastboot - I can understand maybe something went wrong with the version of TWRP I flashed (though I am pretty sure it was the same one I flashed originally when playing around with the PixelExperience ROM.
Anyway, just wondering if there was some other mechanism to trigger either the fast boot or some recovery as its like the boot loader fail to find anything appropriate to boot up from.
Click to expand...
Click to collapse
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.

Mobarok_ said:
Also, before doing any customization, you have to flash the Indonesian fastboot rom. Because almost every development is based on Indonesian rom.
Click to expand...
Click to collapse
Indonesia V12.0.1.0 precisely (V12.0.1.0.QJOIDXM).
Here, you can find and download the rom: https://xiaomifirmwareupdater.com/miui/merlin/stable/V12.0.1.0.QJOIDXM/

I think I messed up royally

Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?

Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH

Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?

newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com

Hmm, it didn't work. I get bootloops...

Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH

For Multidisabler just do a google search one for samsung devices will appear

Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.

Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH

Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!

newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.