Friends and android geeks,could someone tell me the solution for my problem?
I have a htc one m8whl device and its unlocked and rooted now. I have a twrp 3.0.2 recovery installed on my device.
problem:
I face problem when flashing a cyanogenmod13-nightly os through twrp.
everytime i flash it , it shows "failed".
sanjeevikrishna said:
everytime i flash it , it shows "failed".
Click to expand...
Click to collapse
It doesn't just say "failed", it should give you an error code, like code 7 or something. Get back with the error code please.
thank you for replying
RAZERZDAHACKER said:
It doesn't just say "failed", it should give you an error code, like code 7 or something. Get back with the error code please.
Click to expand...
Click to collapse
Now the problem is actually solved. The error(sry did not notice the code) occurred only when i flashed the rom from usb-otg.
It was solved when i tried flashing from sd-card.
And i would be happy to know some good custom Roms for my htc one m8whl.
Thank you.
sanjeevikrishna said:
Now the problem is actually solved. The error(sry did not notice the code) occurred only when i flashed the rom from usb-otg.
It was solved when i tried flashing from sd-card.
And i would be happy to know some good custom Roms for my htc one m8whl.
Thank you.
Click to expand...
Click to collapse
CyanogenMod is if you like near stock android with some features on top.
ERROR 7;
RAZERZDAHACKER said:
CyanogenMod is if you like near stock android with some features on top.
Click to expand...
Click to collapse
Thank you dear friend.
I tried to find out the error code that occurred in previous sessions and it was ERROR:7 as you suggested. It happened with me when i tried to install NusenSeven for sprint m8 as well.
Additionally, I tried installing a couple of ROMS
1) BadBoys for m8 and
2) Wolla for m8.'
Both were installed successfully but unfortunately the Radio was not working. Plus both these Rom's kept on restarting multiple times in an hour for the whole day. Even-though it had many cool customisation's i couldn't use it.
Finally, i returned back to cm-13.0 nightly but Still it has two major problem
1) the Radio is down .
2) problem with the Gapps. ( I flashed the Gapps properly after the rom , but when i start my device i cannot find any apps from Gapps package. NOTE: There was a flash successful message on flashing gapps ).
kindly help me.
thank you in advance.
Related
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Have you tried deleting the telephone system app?
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
graphdarnell said:
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
Click to expand...
Click to collapse
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
hardslog said:
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
Click to expand...
Click to collapse
I upgraded to the latest TWRP 2.7.0.1, deleted everything and started from scratch. Everything works great now and using new kernel that clocks to 1.8 is flying.
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
joehouin said:
Having the same issue except it doesn't boot. I've had it unlocked for a while. Just flashed M v2 yesterday. Wanted to root just now. Ran "sh root-mac.sh" and started getting this error.
Click to expand...
Click to collapse
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
pricedpizza said:
same problem here.... only on my nexus 6. Anybody have a solution?
i found a solution download Nexus root toolkit v2.0.5.
download the preview v.2
Use Flash stock+ Unroot
Flash it again and you fine..
to enable fastboot, but you mobile in bootloader!!
Click to expand...
Click to collapse
Hello, do you mind sharing the link to preview 2, i googled it but didn't see an exact mention of "preview v.2"
Is it one of the ones found on this link?
https://developers.google.com/android/nexus/images#shamu
Thanks in advance,
Julian
I have this same message on my Nexsus 6. Neither Google, Motorola or Sprint can help me get my phone to turn on again. It's past the one year warranty, so no one will replace it. Can anyone help me?
cam30era said:
Nexus 9.
Running M preview 2, clean flashed a few days ago. Rooted, TWRP installed, ElementalX kernel. I just started getting this message on the splash screen during boot.
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co/ABH"
It boots fine and works fine. No other symptoms, at all.
Does anyone know what this is?
I searched XDA and did a more general Google search and found nothing.
Thanks, in advance.
Click to expand...
Click to collapse
I hit the same message loading CM13 on a Nexus 9. Google explains here - support.google.com nexus answer 6185381? I wiped all partitions and loaded stock Marshmallow - the error disappeared. After re-flashing TWRP 3.0.2 the "corrupt" error came back. I then rooted with BETA-SuperSU-v2.66 which got rid of the error. Have since added Google account, updated apps etc. Still booting without error.
So would you say twrp is the reason it gives that error? I rooted my phone today, but when I went to my recovery to check to see if I indeed had a nandroid back up, I didn't... I made one using titanium backup, but didn't show in twrp. Anyhow, about that error message... I didn't know what to do after I had the pop up error message so many times... so i just unrooted my Nexus 6p. I really would like to keep my phone rooted, but I didn't like seeing that concerning error message. Any ideas of what I can do. I would be starting from scratch again. Any links would help! Thank you in advance.
Hi
Im new here and actually i have a very very big problem with my Samsung S3 I9300. Days ago i installed Cm13 on my S3 but i got back to stock mistakelly, but now i want to instal Cm 13 again but when i try to flash it it says "cant open, abort" . Does anyone has any idea whats the problem ? i have tried to redownload the rom again form differet servers but nothing. Also used CWM, TWRP but still same thing. i can install S5 sensation, not blekota, not Cm13, why ?? does anyone has any idea whats the problem ?
Thank you
What do you mean by mistakingly?? Anyway since you can flash roms other than CM13 I suggest you try resurrection remix which is based on cm13 and has the same features (and even more ) frequent updates and a good support so you won't miss anything from CM.
You can try it here http://forum.xda-developers.com/galaxy-s3/development/rom-ressurrection-remix-m-t3270121
Don't be a leech, press the thanks button ?.
when i try to flash any rom, it says : Installation aborted (bad).. cant falsh anything
realdlalaj said:
when i try to flash any rom, it says : Installation aborted (bad).. cant falsh anything
Click to expand...
Click to collapse
Read this, I hope it solves your problem http://forum.xda-developers.com/showthread.php?t=1319857 good luck
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Odysseus1962 said:
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Click to expand...
Click to collapse
Hi, i dont know what happened before because the Phone is not mine, is of the gf of a friend. I can reach fastboot and recovery and I also changed the recovery to twrp and installing a new rom, but bootloop still is running. What can i do else?
BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Kevin1705 said:
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Click to expand...
Click to collapse
I dont have a backup, so i also tried yet everything you said. I dont have to save datas, so i flashed everything new, but still dont work. I also tried to flash everything from oneplusrecoverytool that in any difficult situations helped me, but in this case it did not worked. Is there any radical solution to get this Phone working? (i can install twrp and reach fastboot, but after installing something, it's always in bootloop. ?
i have the same problem , don't know what to do , i even used the tool to return to stock
maybe an overheat problem? i don't know
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Odysseus1962 said:
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Click to expand...
Click to collapse
i tried your solution but nothing changed i also tried this procedure http://forum.xda-developers.com/one...lusrecovery-tool-v1-0-restore-t2991851/page23 , the process is success but at the reboot the phone is always in bootloop
still same problem here =/
Download the latest fastboot image from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 follow step #8
Hello,
since today I flashed definitly more than 100 times a custom rom to several Smartphones. So I know the procedure und what to note.
But now the Redmi Note 6 Pro makes me crazy since two days.
Waited 15 days to unlock bootloader, then flashed the first TWRP, Error 7, tried another TWRP for the phone from here - passwort error encryption etc. etc. I think I have seen all the possible error-messages.
I tried everything incl. back to stock rom via Xiaomi Mi flash several time an than the same from the beginning, always errors, some new like "zip-file corrupt" "can't map file". Thought about a hardware error already.
Has anybody been in the same situation? What should I try? Is there a workaround where I can check the reason for these problems?
Regards
Robert
robert_b said:
Hello,
since today I flashed definitly more than 100 times a custom rom to several Smartphones. So I know the procedure und what to note.
But now the Redmi Note 6 Pro makes me crazy since two days.
Waited 15 days to unlock bootloader, then flashed the first TWRP, Error 7, tried another TWRP for the phone from here - passwort error encryption etc. etc. I think I have seen all the possible error-messages.
I tried everything incl. back to stock rom via Xiaomi Mi flash several time an than the same from the beginning, always errors, some new like "zip-file corrupt" "can't map file". Thought about a hardware error already.
Has anybody been in the same situation? What should I try? Is there a workaround where I can check the reason for these problems?
Regards
Robert
Click to expand...
Click to collapse
Same problem here ? I can't solve ? plz help
Never fear, Google is here!
I had this exact same problem, but this post fixed it:
https://forum.xda-developers.com/showthread.php?t=2522762
I still haven't figured out what caused it in the first place though...
I don't think this programming-issue is the only reason for error 7. I have been trying 5 different roms, always error 7. Is it possible that there comes a wrong model-information from the phone?
Another problem is the passwort for decrypting in TWRP. In some threads is said, this password is the screen protecting password. I tried this - nothing - I changed it - nothing, allways wrong password.
This phone makes me crazy.... All the things working allways and xtimes without any problems - here not.
Same Problem
Had the same problem turned out that you need to flash pie firmware first befor flashing any pie-roms.
See the post here: https://forum.xda-developers.com/showpost.php?p=79136824&postcount=2
This was the solution
matthewultraboy said:
Had the same problem turned out that you need to flash pie firmware first befor flashing any pie-roms.
See the post here: https://forum.xda-developers.com/showpost.php?p=79136824&postcount=2
Click to expand...
Click to collapse
Thank you very much. Sorry for the delay....