Help please. Last two months, my phone keeps resetting time to Jan 1 1970 after restarting. I flashed rom many times but it's not working. I deleted all partitions and flashed stock rom as well, it's not working. Please help.
Fastboot erase tz
Fastboot flash tz tz.mbn
Type these two command your error might get fixed
Related
So i was running AOKP nighty and did a backup. I wanted to install the stock firmware so i could try to network unlock. So i flash the original recovery and flashed a general channel ICS. This resulted in a constant huawei logo. So i fastboot and reflash the twrp recovery and restore my backup. This results in a constant black screen on reboot. It seems any rom (stockish or cm10) results in just the hauwei logo, and my backup wont restore.
Is there any hope since i can flash recoveries all day long?
Flash all paritions via fastboot manualy from stock firmware
fastboot flash modem non-hlos.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash ext oeminfo
fastboot flash rpm rpm.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash logo logo.img
fastboot flash modem_st1 modem_st1.mbn
fastboot flash modem_st2 modem_st2.mbn
fastboot flash cust cust.img.ext4
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
fastboot flash boot boot.img
fastboot flash system system.img.ext4
fastboot flash persist persist.img.ext4
fastboot flash cache cache.img.ext4
fastboot flash userdata userdata.img.ext4
fastboot flash tombstones tombstones.img.ext4
Click to expand...
Click to collapse
Also try wiping everything a few times, cache d-cache, factory reset, system, not doing so can mix up ROMs on partition,
Wipe all then restore/ flash new rom
Clear EVERYTHING and restore backup got me working (though a few errors in the log, like dev/media turned into devmedia unknown directory). Not sure if i want to attempt a stock reflash yet.
nightanole said:
Clear EVERYTHING and restore backup got me working (though a few errors in the log, like dev/media turned into devmedia unknown directory). Not sure if i want to attempt a stock reflash yet.
Click to expand...
Click to collapse
Should be fine, again just wipe everything, and delete any logs on SD card when flashing your stock rom, make sure its the correct rom
well, ive soft bricked my mediapad many times, but this time nothing will get it booting again, ive wiped everything, used my backups to recover via twrp, ive wiped and tried starting with a fresh rom, and nothing, gets stuck into a the logo bootloop. anyone got any suggestions?
the bootloop occurred when i was using a bluetooth headset and they hung up, which cause the tablet to turn off (known bug its no problem) annnnnd i couldnt get any logs because i modded the rom not to log and not to report errors that cause fc, so no logs no hope. idk what to do someone help =(
Bleh!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
thanks for the help guys..not, tried flashing back to stock ics, nothing, i presume it dead just beacause ive fucl<ed with it long enough to piss me off
Try to flash all partitions manualy from stock fw via fastboot.
fastboot flash modem non-hlos.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash ext oeminfo
fastboot flash rpm rpm.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash logo logo.img
fastboot flash modem_st1 modem_st1.mbn
fastboot flash modem_st2 modem_st2.mbn
fastboot flash cust cust.img.ext4
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery.img
fastboot flash boot boot.img
fastboot flash system system.img.ext4
fastboot flash persist persist.img.ext4
fastboot flash cache cache.img.ext4
fastboot flash userdata userdata.img.ext4
fastboot flash tombstones tombstones.img.ext4
Click to expand...
Click to collapse
Corn Flake said:
Try to flash all partitions manualy from stock fw via fastboot.
Click to expand...
Click to collapse
Thanks, I figured it out, there's a problem sometimes with twrp with formatting the data partition, it was the problem all along because I use and older version of twrp, for my own reasons, I sometimes run into permissions problems when I flash with the most recent twrp, so I just flashed the updated recovery, wiped the data, installed my ROM and everything booted fine, then I flashed my old recovery, everything's all good now =)
Can anyone help me!!
I am new to the forum, my Huawei MediaPad 7 Slim has been bricked and the company logo on shows and then a black screen occurs. Can anyone help me please I am pleading for help
Phone is a Moto G7 1962-1 (river), unlocked and rooted with Magisk 20.0. TWRP 3.3.1-0 is installed.
Everything was fine for several months, but I temporarily uninstalled Magisk, and something apparently went wrong and I was unable to use mobile data. The mobile connection fluctuates on and off, every ~10 seconds or so.
Someone suggested doing a fastboot erase modemst1 and fastboot erase modemst2, and sure enough, that works - until I reboot. Then it has to be done again.
I tried going back to unrooted stock, and even relocked the bootloader - mobile data will work until I reboot once, then it remains dead until I issue those two erase commands, and it will work for one boot.
I have not tried erasing fsg and am afraid to without hearing from someone.
The phone is usable, given that it doesn't require rebooting often, but it is a frustrating to worry about. Does anyone know a more permanent solution? I could maybe write a script that would do the erase on reboot, but that would be more of a workaround than a fix.
Any thoughts would be gratefully welcomed.
Here to confirm this strange problem on my moto g7 also.
The fastboot erase modemst1 and fastboot erase modemst2 does fix the problem until reboot.
Need help in writing and installing a script to perform these functions that will run when the phone boots.
I thought about doing that, and will try, but only as a last resort. It seems like it would be patching the symptom rather than fixing the problem.
But yeah, it beats having to tether to a PC every time it needs a reboot.
Hi kenerly,
Try this:
Open your terminal and do
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
then reboot. I betcha the problem is resolved...
Some kind folks on the Telegram group were on the ball about it, and there was a recent thread here in the G6 area about it also. Apparently it is related to a bug in TWRP.
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t39948270
Thanks bro, seems to of fixed the problem.
Disregard
I used a payload extraction tool to open up the OTA file and then flashed each partition via fastboot manually (saw it in a oneplus thread) phone is currently at the boot screen which is much further than it was any time before this, going to give it a little more time before trying anything further as I did a factory reset before upgrading so it could just be first booting.
thoughtlesskyle said:
I messed up while trying to install the android 10 update, I have backups of my stock boot images but not my system paritionwas on MP2) my system partition is now wiped
I can only get to the bootloader but accessing anything else just results in a bootloop so I can't install the OTA updates, I do however still have a working fastboot.
does anyone have a backup of their paritions that I can flash via fastboot?
I also can't seem to boot twrp from fastboot anymore either
any help is appreciated
Click to expand...
Click to collapse
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
KM7 said:
First you didn't state your device model or version.
Android 10 update will lock your bootloader, and till now the unlocking code is no where to be found, and so it can't be rooted unless it is unlocked.
So what you could do is swapping your current partition slot to the one with Android 9 if you want to have root, flash your phone, or booting TWRP.
Code:
fastboot set_active other
Then reboot your phone to bootloader, and you will see that it is unlocked, and do 'Factory Reset' if needed.
Warning do not try to flash anything while the bootloader is locked.
If you have BS 2 Pro global and want to flash MP2 back, check my thread.
Goodluck
Click to expand...
Click to collapse
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
Good to know that you managed to boot it. Hope things are working well for you.
thoughtlesskyle said:
Okay further update, I am using a SKW-H01, I flashed all the partitions from the 10 update manually and hung at a bootloop rebooted to recovery after waiting a little while and factory reset now I am fully booted. I didn't read enough or else I would have been smarter about trying an android 10 build to recover the phone because of it locking the bootloader. Either way we are all good to go. Thanks for your help. I was just stupid and went into it unprepared. I have messed around with a lot of devices over the years but never one that had a payload.bin instead of a factory image.
WE'RE ALL GOOD NOW THOUGH!
Click to expand...
Click to collapse
22 sections.
Yes, all the partitions had to be flashed to run it.
Code:
fastboot flash xbl_config_a rom/xbl_config.img
fastboot flash xbl_a rom/xbl.img
fastboot flash vendor_a rom/vendor.img
fastboot flash vbmeta_a rom/vbmeta.img
fastboot flash uefisecapp_a rom/uefisecapp.img
fastboot flash tz_a rom/tz.img
fastboot flash system_a rom/system.img
fastboot flash qupfw_a rom/qupfw.img
fastboot flash modem_a rom/modem.img
fastboot flash keymaster_a rom/keymaster.img
fastboot flash imagefv_a rom/imagefv.img
fastboot flash hyp_a rom/hyp.img
fastboot flash dtbo_a rom/dtbo.img
fastboot flash dsp_a rom/dsp.img
fastboot flash devcfg_a rom/devcfg.img
fastboot flash custom_a rom/custom.img
fastboot flash cmnlib64_a rom/cmnlib64.img
fastboot flash cmnlib_a rom/cmnlib.img
fastboot flash boot_a rom/boot.img
fastboot flash bluetooth_a rom/bluetooth.img
fastboot flash aop_a rom/aop.img
fastboot flash abl_a rom/abl.img
All writing* [OK].
But having root on board this operation passes with the format userdata error.
In the flash writing* [FAILED].
Only by deleting hidden folders and files via the /data/directory... in internal storage, writing* [OK].
Hello,
I have a problem with the Teclast p20hd N6H7. The tablet had a problem with turning on. After unplugging the battery, it went into flash mode. When flashing the original software by ResearchDownload R25.20.3901, an error occurred while flashing UserData. After skip UserData, flash went to the end and the tablet started up but stuck in a bootloop on teclast logo. I tried other firmware from Tescals website, same problem. I can't upload via fastboot because the bootloader is locked. Anyone have an idea how to solve the problem?
enter recovery mode from Volume key and select factory reset (= format userdata + cache)
Its didn't help
did it work? you have flashed stock ROM and formatted userdata + cache successfully?
userdata partition is encrypted on first boot, for some devices initial boot takes up to 30 min. how long did you wait?
aIecxs said:
did it work? you have flashed stock ROM and formatted userdata + cache successfully?
userdata partition is encrypted on first boot, for some devices initial boot takes up to 30 min. how long did you wait?
Click to expand...
Click to collapse
Didn't work. I flashed four different stock ROMs formatted userdata + cache successfully. I waited 4 hours.