Related
Hi all,
On monday I was looking forward to download Froyo, and since then I live a nightmare. Everything starts cool, it downloaded, it installed itself, and when it restarted.... NIGHTMARE, it started to keep on restarting every two o three minutes after saying the system has a problem.
Since that moment I lost Wifi and mobile features, as well as SD-card reading posibilities.
What I found after some reboots is that I could get into the bootloader and select Recovery, and so I did... and I chose wipe data/factory reset. Everything got delete, and now I could see the screen when it loads (HTC Sense screen).
After this I have tried almost everything, a goldcard to copy a new update.zip file (but when I do it I got the following message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
And this had happen with any single update.zip file I found in these forums and others.
I have tried to use revoked3, and I got an error saying it can not keep on installed.
So... do i have a brick or does someone know how to fix this problem?
Thank you very much in advance for any piece of help.
Guillermo
did you update to the latest radio ?
hittori said:
After this I have tried almost everything, a goldcard to copy a new update.zip file (but when I do it I got the following message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
And this had happen with any single update.zip file I found in these forums and others.
I have tried to use revoked3, and I got an error saying it can not keep on installed.
Click to expand...
Click to collapse
I haven't used revoked recovery, but I know that ROM Manager recovery has an option to 'disable signature verification' (or similar wording) that should get rid of your verify option. As for the reboot loop, usually if you remove the SD card completely, and go into fastboot mode and wipe storage, you get booted up ok.
In my experience, its pretty near impossible to permanently brick an Android handset, so keep at it. You will get it working fully again in the end.
(I lost SD, BT and USB functionality in late July and had everything working again in 24 hours - after lots of panic and stress!).
Feel free to PM me if you get totally stuck.
When and how??
I think I did not, but I did not know I have to do it. I mean, my phone was working fine, I download FROYO, it crashs.... when should I put a new Radio????
Best regards
Solution at last
Thanks to dez_bordes, we found out that I have to use r6 method and it does works.
Thank you very much indeed.
Guillermo.
Welcome. hope you help me a job
I have HTC's Desire ROOT
The state of the machine is still up normally and works fine, but Andoid not get the memory card, no recovery
As children learn to bring the phenomenon known as USB-Brick, Brick SDCard. and on the forums have dealt with software Address. Today I read of your experience you should want to help
because no good at computer should not know
wish you a detailed step by step guide 1 is not?
bban hope this helps for me. tks you more
So I tried cyanogenmod6 and it wasn't my favorite. So now Im trying to restore my image that I made before installing cyanogenmod6, I can start the recovery and it finishes saying "E: error in CACHE: recovery/log (No space left on device)" I try rebooting and it stays on the HTC white screen. What do I need to do?
may be installing another rom might solve the problem..not sure though..just give it a try!!
Full wipe then flash another rom ... it might be a bad img file
Thanks for ur help guys. I figured out I had to uninstall cMTD.
Have a big problem: I want to install ZendroKat NAND to my Samsung Wave I. I did the install successfully exactly following the tutorial. With newest Kernel, dvmpatch is not needed any longer, it even causes problems making NovaLauncher crash all the time. Unfortunately, the tutorial did not point this out and so I have only known that when it has already been too late. How to get rid of this patch now??? Okay, I thought, again a full wipe, and then reinstalling without this patch. So far, so good. But reinstall does not work. When formatting the following error message is shown by cwm: E:format_volume failed to umount "/system" and when trying to restore the ZendroKat ROM, it stopped after formatting "/system" and shows "error while restoring /system" as output.
What to do now? Can anybody help? Bada has completely gone, /system is already reformatted - do not know to help myself now....
Try to unplug battery...
Then directly restart to recovery and try again...
Thank you very much! Left it without battery all night and have just succeeded to reflash! Now, all force closes of Nova Launcher have gone and I can try testing ZendroKat!
Help me find a solution with this error
E:format _volume :make_ext4fs failed
on dev/block/mmcblk1kp3
Error while formatting/system
Note: on kernal 4.5,while trying to clean the data
Turn device off by removing battery and boot directly to Recovery...
Format /system, format /data and then try to recover ROM...
Bought new OP5t
Update OOS 5.1.5 latest
Unlock bootloader
Flash TWRP recovery
Wipe everything except otg format
Install lingue os 15.1 gapps 8.1 pico
Boot normally
Then try to install red flare kenel, magisk zip boot to fatboot menu can't boot make nandroid backup twrp then try to restore also boot on bootloader menu try to download magisk apk download but it's blank can't install notification bar have strange one
Discover trust "get to know to assure how your device is safe"
I don't know what happened if someone could help me if I didn't something wrong please
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
Flash this solve your proplem
https://drive.google.com/file/d/14QnXJH9TWMZnYI9RItIPv8ivGUjz1q5S/view
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Tobias101 said:
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Click to expand...
Click to collapse
That's all I can help with I'm not professional sorry.
Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
brad:
It won't mount data for many reasons but just installing stock recovery and installing OOS would fix everything.
https://forum.xda-developers.com/on...-revert-to-oos-oreo-8-1-t3730952/post75096633
Hi, I'm new here. I did some searching and couldn't find any answers regarding my problem exactly. I'm using TWRP to update my Nexus 7 2013 (flo). I have been successful in the past - as recently as yesterday. Something happened along the way and now I only get an error when attempting to flash ROMs.
I have been trying Lineage 16 and 17.1. I did do the repartition, but I get the same error on both ROMs:
Installing zip file '/sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Checking fir Digest file...
Warning: No file_contexts
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file /sdcard/Download/lineage-17.1-20200803-UNOFFICIAL-flo.zip'
Updating partition details...
...done
I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!
ericdudeus said:
....I have tried to edit the text to eliminate the "asserts" - no help. I downgraded TWRP one version, no help. What else can I do. I'm pretty much a noob when it comes to this, and I'm willing to "hold hands" to get a solution if there is one. Thanks!
Click to expand...
Click to collapse
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Thank you! I actually started over - completely wiped the tablet, repartitioned it, flashed the ROM, and Gapps, and it's fully functioning again. It just didn't like something in the process before, I guess.
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
Hi,
i have too this problem.
I wipe everything, flashed the repartitioning zip and still havoc 3.3 cannot be flashed. What i have to do? thanks
The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!
ericdudeus said:
The solution for me was to just completely wipe the storage - everything, and start over. Once wiped, I repartitioned, flashed the ROM (I used Resurrection Remix), and then GApps. The tablet seems to be fully functional at this point, but it's showing its age.
Good luck!
Click to expand...
Click to collapse
It's tell me E: eroor creating fstab
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL
thrilway said:
I ran the logging zip. My log.tgz is here: https://abar.duckdns.org/s/aywJagDNJDxfiyL
Click to expand...
Click to collapse
OK, the relevant error is...
Code:
erasing 18342 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,223772,228864,229950,243200]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
It seems your eMMC hardware version is <4.4
But RESTOCK should work.
Thanks, but I'm running a linux desktop, so I can't really run RESTOCK. Is there a guide somewhere to run the commands in RESTOCK manually?
EDIT
I've reviewed your logs. For the custom ROM to work you need repartition. Install sysrepart-max.zip then reboot and now install the ROM. If gapps are needed, use pico.
It worked! Thanks
k23m said:
In TWRP go Advanced Wipe and wipe system/data/cache/dalvik before installing the ROM.
If it still does not work and you wish to investigate it, please 'install' this zip in twrp, find 'logs.tgz' in the root of internal storage and post it here.
If you just want this ROM installed ASAP then do:
RESTOCK (select repartition to original factory layout)
CROSS
:fingers-crossed:
Click to expand...
Click to collapse
Thank you so much! It worked perfectly. In the beginning it didn't work, I just reboot the device after wiping system/data/cache/dalvik, then tried again to install the ROM, Now my device has the new ROM working without problem.
Getting error 70 in twrp when installing Opengapps (pico) even BitGapps
Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!
BlackVoltage said:
Hi, I have the Error 7 Problem with my Nexus 10 Using newest TWRP Recovery and trying to install Lineage 17.1 unoffical. Generated the logs.tgz file - which you will find encllosed. Hope anyone could help.
Thanks a lot in advance!
Click to expand...
Click to collapse
This is a Nexus 7 forum, not Error 7 forum, lol.
The error indicates a too small 'system' partition and you need to enlarge it. You will find a solution on Nexus 10 'manta' forum.
Ok thanks - I did not see that at first. My fault. Do you know a special Error 7 Nexus 10 Forum? Or am I just right here?
[ROM][LineageOS][17.1][UNOFFICIAL][Nexus10]
LineageOS lineage-17.1-20230404-UNOFFICIAL-manta.zip Known issues: - Pls disable "Adaptive brightness" in display settings -> sensor service problems. - GPS is not working and has been disabled completely - NFC is not working and has been...
forum.xda-developers.com