Related
[Solved]Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
[emoji736] Solution:
Use flashall.bat which comes with the stock recovery and give it a good deal of time to parse system.img and transfer it to the phone.
You have to wait longer.
sure thet you have flashed img files one by one? i've had the same problem flashing factory image by flashall.bat...flashing img file one by one, no prob.
but if you have this problem with manual flash, try to flash twrp and install a rom zip by twrp
hamedunix said:
Dear friends,
I tried to upgrade my Nexus 5x via factory image files and adb commands. FYI I have done it before on my Nexus 4 so I thought it would be straightforward.
Downloaded the image files and did as the routine procedure is. However when I was flashing individual files, it was system.img turn to be flashed, I got this error "target reported max download size of 536870912 bytes"
and it won't flash system.img file.
The phone can go into bootloader, but fails to start up or whatever.
Any solution is much appreciated. :crying:
Click to expand...
Click to collapse
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.
ikyeye said:
It isn't an error I think.
it's because the filesize of system.img is too big for flashed in one go, so system.img need to be parsed (in Nougat, it become 5 parts) and send one by one to phone (the fastboot command will handle this, so no need to manual parsing).
I had this problem, I just canceled the command and tried again, and success.
if it still not working, try clear cache and reset from recovery (twrp is recommended)
as long as your phone can boot to bootloader and detected by fastboot, I think your phone is far from bricked.
Click to expand...
Click to collapse
I am on stock recovery.
I managed to solve the problem by using "flash all" command instead of flashing each file separately.
Thanks for the reply though.
There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.
hamedunix said:
There might have been a problem with the version of fastboot I was using since it was unable to parse the package automatically and I had to use flashall.bat and give it a good deal of time to be parsed, transfered and written.
Click to expand...
Click to collapse
Glad that you figured it out. Make sure to update your fastboot of course. For me, flashing system.img took quite awhile longer than I recall it taking on Marshmallow but it did eventually flash for me.
Sent from my Nexus 5X using Tapatalk
It's confirmed, need updating fastboot to latest version to get it work.
Wuzimu said:
You have to wait longer.
Click to expand...
Click to collapse
Thanks. I figured it out accidentally by leaving the phone connected for a while and saw it booted up and all done with flashing.
Sent from my Nexus 5X using Tapatalk
So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
TheOnlyPaulV said:
So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
Click to expand...
Click to collapse
First of all, I'm not sure whether flashing the official Huawei partition images will work if they are flashed from TWRP (I've never tried it). However, I do know that it works without problems when flashed in fastboot mode. Secondly, if TWRP was flashed as the recovery and you chose the TWRP inbuilt root option, it would have replaced your BOOT partition as well. So to repair this, you'd have to flash the official Huawei BOOT partition as well. BTW, I was in a similar state (bootloop/no boot) a couple of times (see my post here) and both times was able to recover by flashing the official Huawei BOOT.img and RECOVERY.img partitions to my device.
So, to get your device back into a decent shape, try flashing the BOOT.img as well as the RECOVERY.img from the official Huawei ROM for your device, performing the flashing in fastboot mode. I have written a guide which details extracting and flashing official Huawei partitions. Best of luck
It is obvious that I am missing something very simle here and I'm very interested in finding out what it is I'm doing wrong
So I have a TWRP booting tablet.
I downloaded the latest image from the roms thread on this forum which gives me a zip file called "M2-801LC100B205.zip".
I extract this and open it in Huawei extracter tool.
I extract the BOOT, RECOVERY, SYSTEM and CUST to separate .img files.
I flash all 4, one after the other using the commands listed in your guide:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
They all flash okay (it seems), an exmaple of the flash is:
C:\platform-tools>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (454239 KB)...
OKAY [ 17.471s]
writing 'system' 1/6...
OKAY [ 5.909s]
sending sparse 'system' 2/6 (449072 KB)...
OKAY [ 16.927s]
writing 'system' 2/6...
OKAY [ 5.788s]
sending sparse 'system' 3/6 (459356 KB)...
OKAY [ 17.035s]
writing 'system' 3/6...
OKAY [ 5.894s]
sending sparse 'system' 4/6 (442527 KB)...
OKAY [ 17.781s]
writing 'system' 4/6...
OKAY [ 5.713s]
sending sparse 'system' 5/6 (447342 KB)...
OKAY [ 20.828s]
writing 'system' 5/6...
OKAY [ 5.736s]
sending sparse 'system' 6/6 (67700 KB)...
OKAY [ 2.524s]
writing 'system' 6/6...
OKAY [ 0.864s]
finished. total time: 122.498s
C:\platform-tools>
But still I have a tablet that is stuck on the boot screen. I can still get back to the fastboot recovery so I can still flash but I seem to be missing WHAT to flash?
Surely there must be a complete .img file some where I can flash in flash boot which will just get the thing back and working?
It seems like I'm flashing lots of small simple things when I just want a complete image from some where to flash?
I cant flash the downloaded zip files via fast boot it seems?
Does one exist of have I missed some thing?
Update:
I downloaded a ZIP file of a full rom as detailed above, installed TWRP and tried to flash the zip: it fails stating it could not mount the system partition and radio firmware does not exist. I assume this is because the file downloaded is an update and not a complete rom?
I used TWRP to format and resize the system partition and it reports 0mb in size and fails.
I really think I just need a plain original simple complete rom to flash, in a ZIP format for TWRP: the updates all seem to assume its being flashed onto a working system as an update and I don't have a full base install.
Surely this base simple rom must exist some where?
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
TheOnlyPaulV said:
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
Click to expand...
Click to collapse
Hmmm... I expected you to only flash the boot and recovery images as mentioned in my previous reply (and not other partition images, the example text in my guide was just that - an example) from your original ROM version, not from a downloaded ROM version. If your original ROM was a lollipop ROM and not marshmallow, B205 is a mm ROM and would require a full ROM flash, and in this case a bits-and-pieces flash would not work, and cause a non-booting device. A bits-and-pieces flash especially of any device partition other than BOOT and RECOVERY should ideally be done only with the ROM version which is currently installed and (previously known to be) working.
If you can connect the phone to your computer long enough to transfer over the full ROM image to the device, you should be able to flash that using the original Huawei recovery. The instructions are present on the forum thread where you found the ROM. Alternatively, if you know what version the original ROM was on your device, you can flash its SYSTEM and CUST over.
Yes, that's what I would like to do and I can do that, fast boot still works, but it's where do I get a FULL ROM from? Everything on this forum I have found is an update and relies on another working ROM to be present.
Where do I get the full ROM from, do we know the name of one which is not an upgrade ROM?
It's this full ROM I've been looking for to no avail
Please confirm your device model and I'll try to find a full ROM image download (Marshmallow) for you.
EDIT: by full I mean a ROM which is a complete image (about 2-3GB) instead of a partial OTA update. Also, I'm not certain that you can flash a full Huawei official ROM image from fastboot; it requires booting into the recovery. AFAIK Booting into the recovery does not need a working ROM system partition.
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Sorry to bug but have you, or any one else, had any luck in finding a full rom?
Any one have a twrp backup of a basic fulll booting rom I could try?
I do appreciate all the help!
TheOnlyPaulV said:
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Click to expand...
Click to collapse
Sorry for the delayed reply, I've been pretty ill for the last few days.
Here are links to what I'm pretty certain are the OEM Lollipop full ROMs for the 801L. All those links are 1.4GB zipped, which means that they should unzip to about 2.5-3GB, which indicates that it is a full ROM:
801L B006 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=57706&version=181649&siteCode=my
801L B007 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=71503&version=254039&siteCode=my
801L B003 on Huawei Russian support site (): http://download-c.huawei.com/download/downloadCenter?downloadId=71523&version=254048&siteCode=ru
You'll need to get the unzipped ROM folder onto your external SD card somehow, to be able to flash it with the Huawei recovery.
Here are some steps you can follow:
Part 1: Download ROM, extract it and then copy extracted ROM directory to sdcard on phone
In this part, we will download the ROM, extract it, and transfer the extracted ROM to your M2 using TWRP and ADB. Make sure that you have the Mediapad drivers installed, and adb and fastboot installed and available.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
On Linux, just install the Android Command Line tools from Google.
For the phone drivers, just install HiSuite from Huawei - this will install the Mediapad device drivers. You can then uninstall HiSuite - the drivers will still continue to remain installed even if HiSuite is uninstalled, and this way you won't clutter up your computer with the useless HiSuite.
Now download one of the ROMs listed above (I suggest starting with B007. If that doesn't work, try B003 and then B006).
Unzip the downloaded ROM onto some location on your computer's hard drive. Let's say that on Windows, you unzip it to D:\MYROM
In D:\MYROM, you should find a directory called dload
Make sure that you have TWRP as the recovery on the phone. Flash TWRP onto the phone if you need to (since you already know how to do this, I won't go into more detail).
Boot into the TWRP recovery on the phone (since you already know how to do this, I won't go into more detail).
In TWRP, make sure that MTP mode is off. To do this, in the TWRP main menu, press "Mount". In the "Mount" screen, check whether the second (right-hand-side) button on the bottom reads "Enable MTP". If it says "Enable MTP", then you do not need to do anything else here, go back to the main TWRP screen. If the button says "Disable MTP", press it so that the button now reads as "Enable MTP". Setting MTP mode off will ensure that you can connect via ADB to your phone.
Now open a terminal/command-prompt window on your computer (Run->"cmd" or search for "cmd" on Windows).
In the terminal window, navigate to the directory where the unzipped ROM is present. On Windows, using the above example ROM unzip location, you would type
Code:
d:
cd D:\MYROM
Type the following ADB command to make sure that your phone is recognized by ADB:
Code:
adb devices
If it works, you should see something like
Code:
List of devices attached
ABCD1234567890 recovery
where "ABCD1234567890" will actually be your device ID string, and not literally "ABCD1234567890"
If you see a string like the above, good news, it means that your phone is recognized by ADB, and we can now transfer the unzipped ROM to your SD card. If you do not see anything after the "List of devices attached" string, make sure that you have turned off MTP mode in TWRP as detailed above. If you still don't get anything, you will have to transfer the unzipped ROM to your sdcard by some other means - perhaps by putting the SD card in another phone. Skip the rest of the steps here and see Part 1.5 below.
Now type the following command in your computer's terminal window (command below is for Windows; on Linux, replace "D:\dload" with the appropriate path to the dload directory):
Code:
adb push D:\MYROM\dload /sdcard
This will copy the extracted ROM's "dload" directory to the root of your internal SD card. To copy it to the root of your external SD card, replace "/sdcard" in the above command with "/external_sd".
If all went well with the above command, then at this point your extracted ROM's "dload" directory should have been copied over from your computer to your phone (either on the root of the internal SD if you used "/sdcard" in the "adb push" command, or on the root of the external SD if you used "/external_sd" in the "adb push" command. Go to Part 2 below.
Part 1.5: Copy extracted ROM directory to external sdcard on phone using another phone.
SKIP THIS PART IF YOU SUCCESSFULLY COMPLETED ALL STEPS IN PART 1 ABOVE, AND GO TO PART 2 BELOW!
Remove the external SD card from your M2.
Insert the external SD from the M2 into some other phone/device.
Connect that phone to your computer via USB.
Transfer the unzipped ROM's "dload" folder to the root of the SD card.
Remove the SD card from the other phone and put it back into your M2.
Part 2: Flash official Huawei BOOT.img and RECOVERY.img and installed extracted ROM using official Huawei Recovery
In this part, we will replace TWRP with the official Huawei recovery and boot partitions, and use the official Huawei recovery to flash the ROM on the phone.
From the ROM you downloaded in Part 1 above, extract BOOT.img and RECOVERY.img using the Huawei Update Extractor. Since you already know how to do this, no further details will be given.
Flash the official Huawei BOOT.img and RECOVERY.img partitions (for safety, do not flash any other partitions) onto your M2. to refresh your memory on how to do this, see my guide.
After successfully flashing the official Huawei BOOT.img and RECOVERY.img partitions to your M2, you can flash the downloaded ROM as an update by booting into the Huawei recovery which you just flashed onto your M2. After booting into the Huawei recovery, it should automatically detect and start installing the downloaded ROM.
Hope this helps. Good luck!
TheOnlyPaulV said:
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Click to expand...
Click to collapse
That won't be necessary, but thanks for the offer I'm just trying to help out people wherever I can; I don't want anything in return
Hello, "different customer" here
I came into the same situation, a while ago I wiped a lot of things (through TWRP) making my tablet unbootable, I was trying to recover from a bootloop.
I followed this well written guide but the stock recovery won't detect the new ROM (I have a dload folder with META-INF directory inside and UPDATE.APP).
I flashed the BOOT.img and the SYSTEM.img while at fastboot mode. At the sdcard there is a folder dload with the rest.
Booting up with pressed + and - is starting to "Installing update" but hangs at 5%
What should I do
Well finally I managed to fix it, twice! here is the story.
After I left it for half an hour saying "Installing update 5%" I decided to reboot.
Tablet booted ok but there was problem with WiFi, couldn't switch to On.
I decided to reflash http://update.hicloud.com:8180/TDS/d...1LC100B206.zip once again but still nothing, I tried B002, B005 but no success with the WiFi (this wifi problem is something I did when I was fing around at the bootloader with fastboot).
Then I decided to flash the SimplyGoogle, that got me in a bootloop.
Ok I said now I will fix it once and for all.
Then I entered TWRP, wiped EVERYTHING and I got this http://update.hicloud.com:8180/TDS/d...1LC100B206.zip uploaded to the /sdcard/dload.
Next step was fastboot mode, flashed BOOT.img, System.img and recovery.img from the extracted UPDATE.APP of the M2-802L once again (keep in mind I have the M2-801L).
Now it was time to poweron with + and - pressed so the recovery to understand I need a system update/flash.
Again it was stuck at 5% but now I knew just left it hanging for an hour and rebooted.
And it worked.
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
lepidas said:
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
Click to expand...
Click to collapse
You're welcome, glad I could be of assistance
Your posting of your experiences may help someone else who runs into a similar issue, so thank you for taking the trouble to post in detail :good:
Im afraid I am not quite as advanced as your self, I dont know what a 'META-INF directory inside and UPDATE.APP' is so please bear with me, especially if im preaching to the converted.
My problem was that I had a, basically, blank device.
The only thing that remained was the boot and recovery.
The first thing I got wrong is that the device is partitioned into multiple parts, its not one rom image for it all thus flashing a update rom wont write over all the partitions to recover the device, it will only flash the ones its updating thus you need an image that has alll the partitions to recover from a wiped device.
Second problem I has was that the TWRP recovery will not allow flashing of complete roms and I didnt have a backup of a complete rom.
Third problem I had was getting a hold of a 'complete image'.
So the link above allow you to download a complete image. part1 done.
then extract the boot partition from the complete image as the complete rom will only install/boot from its own boot partition: you cant install a complte from from a TWRP partition.
flash the bootimage from the complete rom.
copy it to the SD card, install it from there.
Then, once you have your system up and running, install your updates ot get the unit back.
Hope that makes sense and ive not just repeated things you already know, but thats as far as my knowledge goes
I got my phone a few days ago and rooted it, installed most stuff etc.. So far I have TWRP and Magisk 14.0 Root active on it, not much else I can think of. The phone is running Android 7.0.
I left the Camera for last to check and when I did I noticed neither the camera nor its flash are responding. ("camera busy" error, other full-fledged cam apps showing black) I went through the initial steps of disabling OK Google's camera settings, disabling a bunch of apps that had cam access, checking safe mode etc. and none of them worked.
Finally I went into Device Helper's hardware list and noticed under "Imaging" there isn't even a camera listed. I don't know how the app works but even with cam busy it would at least be listed. I went through a few other hardware spec listing apps and all of them showed absolutely no camera hardware. Interesting enough, I know the phone has 2 cameras, I'm not sure if they're a single unified piece of hardware or not but there was no such thing as back or front camera even, there was quite simply nothing listed under camera.
At this point I'm left to wonder if the problem is either a setting or something to do with rooting, or actual hardware fault. Unfortunately having rooted the device, I also have no warranty for it.
I welcome any ideas, advices, anything about trying to detect or diagnose camera issues. If there were a TWRP way of checking the camera hardware, I'd be glad to try it out since it would rule out anything having related to the Android OS, or other versions of Magisk. 11.6 was recommended but it never worked for me. This is all before I open up the phone. I can't much afford much to do a factory reset at this point and would like to leave it as the last resort.
In the event of a camera issue, I'm of course hoping it's as simple as a loose connector, but I'd like to know of any known G5 hardware issues with the camera and if there's documented fixes.
Also in the event I DO have to do a hard reset - do I have a reliable way of backing up absolutely everything about the phone's current state(apps settings documents etc.) and restoring it all back?
I just spent good money on this phone, thank you for all advice!
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
TheFixItMan said:
Are you using stock rom or a custom rom?
You can use magisk uninstaller to remove magisk to see if that caused an issue (see magisk v14.0 thread)
In some custom roms some people did report camera stopped working - Iv never had this issue
I'm using LineageOS with the built in superuser via the su add on zip
In terms of the camera itself hardware wise & on unmodified stock there are no reported issues
Click to expand...
Click to collapse
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
SearinoxNavras said:
Not using a custom ROM.
I went to the Magisk page where I got the install, got "latest uninstaller", ran it. It reported success but warned that no boot image backup was found. On restart it hanged indefinetly at the 5-second untrusted device warning. Did a hard poweroff and on, same result. I ended up installing the 14.0 back and the device again boots. I also did a dump of the boot logs.
In dmesg.log I see this:
Code:
<3>[ 5.684036,2] msm_camera_pinctrl_init:1277 Getting pinctrl handle failed
Code:
<3>[ 5.676660,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676664,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676667,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676710,2] msm_flash_get_pmic_source_info:895 alternate current: read failed
<3>[ 5.676714,2] msm_flash_get_pmic_source_info:915 alternate max-current: read failed
<3>[ 5.676717,2] msm_flash_get_pmic_source_info:935 alternate duration: read failed
<3>[ 5.676760,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676763,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
<3>[ 5.676806,2] msm_flash_get_pmic_source_info:1005 alternate current: read failed
<3>[ 5.676810,2] msm_flash_get_pmic_source_info:1025 alternate current: read failed
and respectively this:
Code:
<3>[ 5.664800,0] msm_camera_get_dt_vreg_data:1115 number of entries is 0 or not present in dts
I'm no expert reading these logs, is this signalling my issue?
Also this is from the non-working boot, near the end of the log:
Code:
>[ 33.292450,5] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Click to expand...
Click to collapse
Here is the original stock boot.img if you need to flash it after removing magisk
Stock boot image
You need to put your phone in bootloader mode & connect to pc via usb
Open a command/terminal prompt at your fastboot location
Code:
fastboot flash boot boot.img
Substitute boot.img for the name of your boot.img if different but I think I named it boot.img
You may have to flash the entire stock firmware & start again or try flashing Linageos
You can also try erasing user data by typing
Code:
fastboot erase userdata
But note this will erase all data from phone including anything in internal storage like photos music downloads etc (only data partition not system so phone will boot as if new)
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
If I were to try a stock reflash or another fw, do I have a way to image absolutely everything and if I want, to restore it back as if it never changed?
I forgot to mention that when I installed TWRP I also installed no-verity-opt-encrypt-5.1.zip. Does this have anything to do with it?
SearinoxNavras said:
The boot.img you sent me and the one I have both have the same hashes. So I was at least doing that right.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.518s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.739s]
finished. total time: 1.258s
Is "bad key" normal? Now the 5-second untlocked untrusted warning says ID: bad key instead of N/A. Sadly, the device behaves the same. It hangs indefinetly at that one screen. Maybe something's off with the uninstaller; if I wanted to manually -disable- magisk by renaming say one file or folder that is an entry point, how would I do that?
I checked the boot logs again, and I'm still seeing the same camera stuff mentioned there, so I don't know if it fixed anything since I can't boot but it doesn't look different.
I uploaded the files here: https://drive.google.com/file/d/0B5_lN_xRgoTVTUZZX0ZaWmZGNkE/view
Please tell me if there's anything there shouldn't be about the camera in them.
Once I reinstall Magisk, the ID at the boot splash warning goes back to N/A. Funny enough it -does- say it's found a stock boot image and it's backing it up when you install, but on uninstall it never finds it.
Click to expand...
Click to collapse
it always says image signed with bad key for me
you can try going into twrp
click advanced
file manager
data
select magisk.img (or something like that)
then delete it
Other than reflashing the entire firmware via fastboot theres not alot else I can suggest
I would erase userdata though if you are trying the uninstall magisk as it does modify the data partition and its best to erase it if you no longer use magisk - but as I mentioned before anything on internal storage will be lost so move it to sd card
But I dont know of anyone else who has used magisk and the camera stops working so I dont even know if thats the problem
Without testing it on a fresh stock rom you wont know
I flashed LineageOS and it's seeing my camera! I haven't yet flashed the google apps, mainly to see if the camera works in as minimal a clean slate as possible. Now with that out of the way, whatever other issues I may encounter I will solve or possibly ask in another thread, but at least this fixed the cam. Now off to the long road of installing stuff.
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
woozie.2007 said:
for me is the same, flashing stock again, update all to august patch, and the camera stop working, if i uninstall magisk the phone not starts, is stuck in the boot logo, after install magisk 14 again, the phone boting but no camera works
Click to expand...
Click to collapse
After uninstalling magisk try flashing the kernel for your rom via fastboot
i tried but the phone won't boot
---------- Post added at 05:13 PM ---------- Previous post was at 05:12 PM ----------
the phone started only if i flash system sparsechunk0, 1, 2, 3 and 4, without these flashed the phone not starting
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
woozie.2007 said:
i flashed again the stock firmware, initial is with patch from january, i made ota update to march(the camera still works with magisk 14), and then i updated ota to august....now camera works, but i installed magisk and patched the boot....bang, the camera stops. So i decided is problem with magisk after the august update, i haven't twrp, only flash it via fastboot. I dont know what can i tried to works camera with magisk ((
Click to expand...
Click to collapse
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
TheFixItMan said:
Why do you want to use magisk - it doesn't work fully on this device - eg magisk hide & modules do not work
Much better using supersu (either via twrp zip or CF-Auto-Root) or the lineageos root addon
Click to expand...
Click to collapse
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
woozie.2007 said:
because i want to update via ota, cf auto root i tried but not works, i want to use stock firmware not lineageos, i have 7.0. Can you tell me how to root moto g5 without modify system, to be able to update ota? Thanks
Click to expand...
Click to collapse
Then use supersu and flashfire app
https://play.google.com/store/apps/details?id=eu.chainfire.flash
I'm working on CF-Auto-Root - server is down at the moment - once Iv created a working package I'll post it
how? i am on stock now, not twrp, i have full stock
woozie.2007 said:
how? i am on stock now, not twrp, i have full stock
Click to expand...
Click to collapse
Flash twrp root then flash stock recovery
Obviously I presume you have unlocked the bootloader
yes, of course i have
woozie.2007 said:
yes, of course i have
Click to expand...
Click to collapse
hello
he
lp me please i have the same problem: camerera falled
Marie74 said:
hello
he
lp me please i have the same problem: camerera falled
Click to expand...
Click to collapse
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
camera
woozie.2007 said:
i fixed the problem with clean flash stock rom, then update ota then flash twrp and root again with latest version of magisk
Click to expand...
Click to collapse
thank you for awser give me the link please please please! god bless you!
I have a blackview A20 which is a low spec phone running android oreo go.
I would like to use this phone for experimentation with android development and learning about android on a cheap device without risk of breaking my main phone. To do this I would like it rooted and as a bonus with a custom recovery so I can test custom ROMs.
State of device:
Unlocked bootloader
Unchanged ROM
Unchanged Recovery
OEM unlocking enabled
USB debugging enabled
What I have tried:
Flashing recovery images with fastboot
Using fastboot flash recovery recovery.img with some TWRP and CWM recovery images all yield:
target reported max download size of 134217728 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.169s]
writing 'recovery'...
OKAY [ 0.276s]
Click to expand...
Click to collapse
finished. total time: 0.448s
or similar. Then I restart phone and select boot into recovery mode. The phone hangs for a small while before restarting and booting into the normal OS. On restart into recovery the unchanged recovery is there still.
Various 'one-tap' methods
All of which were unsuccessful. If needed I can give details.
Installing SuperSU zip from recovery
In a futile attempt I tried to use the android recovery to push a SuperSU zip with its update from zip option. I knew this wouldn't work but I found something interesting. On the Apply update from SD card option I get an error saying couldn't mount /sdcard
Booting recovery images with fastboot
I have tried the fastboot boot recovery.img command to try to boot directly into the images. I get this
downloading 'boot.img'...
OKAY [ 0.211s]
booting...
OKAY [ 0.047s]
finished. total time: 0.261s
Click to expand...
Click to collapse
output but the device just restarts and boots normally into the normal OS.
What I would like from this question (In order of importance):
A way to root the device
A way to access a custom recovery (even if temporary)
Ability to install custom ROMs
A permanent custom recovery
mejakep said:
I have a blackview A20 which is a low spec phone running android oreo go...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads helpful because they, apparently, are compatible with your specific device. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3709659
https://forum.xda-developers.com/showthread.php?t=3767690
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hello,
I'm also trying to root the Blackview A20 with no success. Where you able to find a way?
Thanks!!
I'm afraid I still haven't found a way. Other than TWRP or something making a custom recovery specifically for this phone I don't see a way to root it at all. Sorry
I have a Blackview A20 Pro (note this is probably different in specification to the A20) - Here is how I rooted it by using Magisk on a boot image read and written using SPFlash tools. I had previously unlocked the bootloader on the phone by using the Developer option for OEM unlock and then fastboot unlocking as standard.
- Obtain the MT6739_Android_Scatter file from an archive of the a20 stock rom available by googling
- Install Magisk manager apk on the phone
- Run the latest version of SP Flash tools on the PC with the associated drivers. Load the scatter file in to it.
- Work out the size of the boot partition by subtracting the start value of the next partition (Logo) from the start position of (Boot)
- I did using Windows calculator in programmer mode - set to hex, subtract the two values. Note the start position of the boot partition
- Go to the Read Back page, add an item to read back, enter a filename to save it like a20-stock-boot-image.img and then enter the start position of the boot partition and the size you calculated. Make sure to get them exactly correct and avoid changing the number of digits in the entry box as I don't know how fussy sp-flash tools is.
- Unplug the phone from PC if it is plugged in and remove the battery.
- Tell SP Flash tools to start the read-back
- Plug the phone in, within a few seconds it should read and save the boot partition from the phone. Keep this backed up. File should be something between 8-25mb I would expect.
- Put the battery in the phone and power it up and unplug/plug it in to the PC via usb and then in the notification area on the phone select "Transfer Files" from the very bottom so it appears to your PC as a drive.
- Drag over the stock boot image from your PC somewhere on the phone - like the Downloads folder.
- On the phone open magisk and select install - when prompted select to use local boot image, select the stock boot image file you transferred
- Magisk should now patch this file - make sure the text it outputs looks like it recognized the boot image and is working.
- Now unplug and replug the phone to PC as I found PC doesn't seem to see new files on the phone. Pull over the patched boot image Magisk has made. Don't worry if this is smaller than the original file. The extra bytes were likely just zeros.
- Using SP Flash tool, go back to the Download screen and select the patched boot image for the boot partition. This will write the new boot image to your phone.
- Power down the phone and remove the battery.
- Tell SP flash tool to start and then plug the phone in with no battery. It should then flash the patched boot image.
- Put the battery back in and boot the phone. When you open magisk app on the phone now it should say you are rooted.
Enjoy!
If it doesn't work, repeat the download process with the stock boot image you saved and that should restore things to how they were before. I assume if it doesn't work it will just be because you need to unlock the bootloader or because your phone is different to the scatter file, but in that case I would expect Magisk to fail to patch it before you get to that stage.
How do you remove the battery? Have I missed something?
Sorry, wrong phone!!
Hello guys, last night bought a redmi 7. But this i check this cell phone and the MIUI LOCK is unlocked.
I had a brilliant idea to block using adb. And i destroy the system.
I tryed MI PC Suite, I Tryed mi flash is faild(remoite: Update sparse crc list failed), I Tryed in adb fastboot oem unlock, i tryed mi flash unlock and I was unsuccessful.
Did i throw my money in the trash?:crying:
You mean MIUI (System ROM) is gone?
Yes.
The message in Main Menu is ""this miui version can't be installed on this device !
I think you have to flash TWRP in ADB Mode (Volume - and Power button). And in TWRP, connect USB to "computer" then copy MIUI stock rom to SD Card or Internal. Hope it helps.
H3XUS said:
I think you have to flash TWRP in ADB Mode (Volume - and Power button). And in TWRP, connect USB to "computer" then copy MIUI stock rom to SD Card or Internal. Hope it helps.
Click to expand...
Click to collapse
Thank you guy, but i don't have any idea how to install TWRP in my cell phone. I tryed but have a error:
fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
erasing 'recovery'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.006s
Can you help me ?
Please, Help !!!
Mr.Nexus said:
Yes.
The message in Main Menu is ""this miui version can't be installed on this device !
Click to expand...
Click to collapse
Maybe the rom is not for redmi 7, check this and try search a rom for the phone.
I buy a redmi 7 root and later i unroot..... the phone had acount of miui and block my new phone, i erase all operative system and installed Twrp (not all Twrp work on this device)
If your phone doesnt work whith miui, try another rom like a Pixel and ¿Aoex?
ericklawliet said:
Maybe the rom is not for redmi 7, check this and try search a rom for the phone.
I buy a redmi 7 root and later i unroot..... the phone had acount of miui and block my new phone, i erase all operative system and installed Twrp (not all Twrp work on this device)
If your phone doesnt work whith miui, try another rom like a Pixel and ¿Aoex?
Click to expand...
Click to collapse
Guy, I tried to use multiple versions of MIUI. But to no avail.
As I understand it, I need an authorized xiaomi account.
I particularly lost the money. In the past, changing the rom on xiaomi devices was an easy thing, today if there is some kind of problem in the most serious system, you practically lose the device.