so it all started on trying to root with kingroot and as expected i got stuck in bootloop
and after that i was able to flash philz
but on flashing cm11 (changed updater script to kis3 and then i flashed) it didnt work and the contentiously booted into recovery (phliz)
then i went through xda and found it philz dont work
so
I flash twrp
and this time (the unedited script) its said status 7
i flashed Stock ROM still wont boot
basically im stuck with twrp installed
I tried restoring cwm backup as well
and I cant get nokia care suite to work
kotic said:
so it all started on trying to root with kingroot and as expected i got stuck in bootloop
and after that i was able to flash philz
but on flashing cm11 (changed updater script to kis3 and then i flashed) it didnt work and the contentiously booted into recovery (phliz)
then i went through xda and found it philz dont work
so
I flash twrp
and this time (the unedited script) its said status 7
i flashed Stock ROM still wont boot
basically im stuck with twrp installed
I tried restoring cwm backup as well
and I cant get nokia care suite to work
Click to expand...
Click to collapse
If you have TWRP recovery 2.8.1.0 you can install Cyanogenmod 11 ...
i gotta say..
DON'T TRY TO EDIT USERSCRIPTS....YOU MIGHT END UP GETTING YOUR PHONE HARD BRICKED
DinethIrusha said:
If you have TWRP recovery 2.8.1.0 you can install Cyanogenmod 11 ...
i gotta say..
DON'T TRY TO EDIT USERSCRIPTS....YOU MIGHT END UP GETTING YOUR PHONE HARD BRICKED
Click to expand...
Click to collapse
I did try, but I'm getting status 7 error,everytime i try
i think I found the problem is that i cant mount system(cant check the box in options)
so I gotta find the solution now tought
and since I have no OS installed I'm pretty much hard bricked
kotic said:
I did try, but I'm getting status 7 error,everytime i try
i think I found the problem is that i cant mount system(cant check the box in options)
so I gotta find the solution now tought
and since I have no OS installed I'm pretty much hard bricked
Click to expand...
Click to collapse
Try this..
1. Download this Recovery to your sdcard and flash this using your current Recovery
TWRP Recovery
2. Reboot your recovery (Reboot>Recovery)
3. Download this Cm11 Last build and flash it
CM11 Latest Last Build
4. Reboot your phone (It'll take like 5-10mins to boot up so be patient)
TIP :
Hard-Brick - Hardware Bricked..which means you can't even turn on the phone and you can't recover your phone (dead phone)
Soft-Brick - Software Bricked....Which means you can turn on the phone and do whatever to recover your phone
Okay so I found out whats wrong with the phone,it seems twrp cant mount "system" and "data"
even in the mount>the two checkbox cant be checked
and idea to fix?
kotic said:
Okay so I found out whats wrong with the phone,it seems twrp cant mount "system" and "data"
even in the mount>the two checkbox cant be checked
and idea to fix?
Click to expand...
Click to collapse
try rooting your phone using nokia-x2-tools v.1.2..
help
i tried flashing CM13 in mhy NOKIA X2 DS RM-1013 with TWRP but forgot to make a backup of my data. The rom flashed but then it says no OS installed are u sure to reboot.. i don't understand what's wrong, please help me recover my phone
Flash new any stable rom
j€nish said:
Flash new any stable rom
Click to expand...
Click to collapse
please provide link to any stable ROM for NOKIA X2 RM-1013 product code 059V782
hard bricked
DinethIrusha said:
Try this..
1. Download this Recovery to your sdcard and flash this using your current Recovery
TWRP Recovery
2. Reboot your recovery (Reboot>Recovery)
3. Download this Cm11 Last build and flash it
CM11 Latest Last Build
4. Reboot your phone (It'll take like 5-10mins to boot up so be patient)
TIP :
Hard-Brick - Hardware Bricked..which means you can't even turn on the phone and you can't recover your phone (dead phone)
Soft-Brick - Software Bricked....Which means you can turn on the phone and do whatever to recover your phone
Click to expand...
Click to collapse
can we repair hard bricked phone
kotic said:
so it all started on trying to root with kingroot and as expected i got stuck in bootloop
and after that i was able to flash philz
but on flashing cm11 (changed updater script to kis3 and then i flashed) it didnt work and the contentiously booted into recovery (phliz)
then i went through xda and found it philz dont work
so
I flash twrp
and this time (the unedited script) its said status 7
i flashed Stock ROM still wont boot
basically im stuck with twrp installed
I tried restoring cwm backup as well
and I cant get nokia care suite to work
Click to expand...
Click to collapse
i hope not corupted emmc, i have this but with samsung ace 2.
it can bootup to recovery and bootloader but it wont install any ROM
Related
Hey folks,
after hours of reading around I have almost no idea left how to update my CM13 (13.0-20151213_nightly-titan) currently installed to a newer version. I tried with TWRP 2.8.6.0 and even 2.8.7.0, but it's all the same: I choose the zip file to install, the filesystem is detected correctly - but the installation just won't continue (usually the detection is followed by "patching the system unconditionally"). TWRP doesn't freeze, but just nothing happens . When I brake up after some time (usually an installation is done very quickly) with pressing the power button, my phone boots in the old version normally.
I tried another TWRP, wiped cache and dalvik, fixed permissions, set root in phone options, tried several CM13 builds... But I'm afraid of wiping data and system as it's a lot of work to get everything right again afterwards :crying:. Do you have any idea why TWRP doesn't want to install the new build?
Thanks a lot!
First always take a nandroid backup before you make any changes.
Even thought TWRP 2.8.7.0 is released, For Moto G 2014(titan)
only 2.8.6.0 is official https://dl.twrp.me/titan/
Try doing a clean installation(Wipe the data & System). That should do the trick.
just for the record the recovery is stopping you from installing a new build
Seems to be an issue with TWRP. You could give a try using CWM PhilZ Touch recovery. I have flashed using this recovery numerous times without any problem.
Thank you two for your replies !
Maddy, I know that 2.8.7.0 is unofficial for titan, but nevertheless it's working (for others). I want to avoid a complete reset, but in the end this could be a solution. But as I reflashed twrp (and tried another version also) I'm really wondering why twrp could be the problem ...
pank, I will take a look on CWM PhilZ, but until now I was really happy with twrp (and of course with its backup function). I hope it's possible to flash CWM using twrp and vice versa .
Unfortunately CWM PhilZ Touch Recovery shows the same behaviour than twrp - installation of new zip file just doesn't work (without any error) . If someone has an idea (except of a full wipe) please give me input !
Update the bootloader to the latest version. Had a similar problem a few months back that resulted in lots of hair tearing This solved it.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
Great hint - just checked your link already this morning and everything seemed to make sense... But I figured out that bootloader 4883 (newest version) was installed at my phone . Downgrade to 4882 should not be possible, and I'm also afraid of that .
I think I have something to do around Christmas - full wipe and a clean install! Damn...
Try installing this app called "CyanDelta" from playstore. What it does is it downloads the necessary files to upgrade from cm latest build (not the hole file) it's could be around 30 mb only. Totally legit!!... And it would dirty flash after download....
Do let us know how it turns out ?
I already tried CyanDelta, great tool! But as it's just creating a script for TWRP it has the same behavior . Oh, and I discovered that the nightly I'm using is no more available on cyanogenmod's official website ^^.
By now I think I've spend more time on searching for a solution than a full wipe including everything would need :laugh: ...
For me TWRP gives this behaviour only when Downloaded zip has some problem in it.
when it's not downloaded correctly it stuck at patching System
Have you tried latest zip?
also check SHA1 after download, doing that will confirm zip is downloaded correctly
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
No_Future said:
Yes, I've tried the newest zip (several days respectively the newest) and I've checked the SHA value every time . The zip verification of twrp itself also doesn't report an error.
Maybe the reason is that I've used CM 12.1 before and made a "dirty" flash. Full wipe is getting closer to me...
Click to expand...
Click to collapse
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
mwalma said:
Just to say that I am having the same problem. Does the problem exist with Cyanogen Recovery? Can I replace TWRP with Cyanogen Recovery without touching everything else?
Thanks in advance.
Click to expand...
Click to collapse
Yes, you can try Cyanogen Recovery
download it and from fastboot
you can either just boot once and try it or flash the recovery replacing TWRP
Code:
fastboot boot recovery.img
Code:
fastboot flash recovery recovery.img
Great, I didn't know that it's possible just to boot once with a special recovery image. I'll try cyanogenmod recovery today !
Great news: With use of Cyanogenmod Recovery I was able to flash the newest build :victory:! I'm looking forward to try one day with TWRP, but for now I'm totally up to date . Thank you all again and have some nice days !
Edit: A full wipe and clean install solved this problem completely . Now the flashing with TWRP works again.
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
kitsunezero said:
Hello, i have a bricked asus memo pad 7 (me176cx), when i try to install the factory firmware (UL-K013-WW-12.10.1.33-user.zip) the cwm and the twrp2 give me a error "unable to mount /factory" and i can't install the rom.
How can i fix that?
Thanks
PD: sorry for my caveman english (?)
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A inorder to get expertise help
-Vatsal
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
paulgiro said:
I never had to mount those partitions when installing that ROM when I bricked mine. I just wiped all caches and installed from zip. Are you doing this?
Click to expand...
Click to collapse
I'm a idiot http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814,
I didn't read this "This package is for "K013" devices; this is a "K013_1"." I was bricked for a week because of a random device "name change?" Well here are the steps I took to make a flashable lollipop that wouldnt brick me. What you are doing here is telling the script that does the update that it does not need to verify your tablet model since it is wrong anyways.
Now i follow the steps and my tablet is boot, i'm waiting.
EDIT: Still bricked, now i can enter in fastboot mode but when i power on the tablet, after the logo, the screen is black
I have the same problem and can't find any solution yet :crying::crying:
sidane12 said:
I have the same problem and can't find any solution yet :crying::crying:
Click to expand...
Click to collapse
i can install the original firmware, but now still bricked with the same error
kitsunezero said:
i can install the original firmware, but now still bricked with the same error
Click to expand...
Click to collapse
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Ruben Craveiro said:
try to format all partitions and shutdown, then boot into bootloader and load temp recovery and reflash .33 then boot android normally if still doesnt work, then reinstall once more but without wiping any partitions, if it decides to boot to bootanimation but its stuck there you need to simply make a reboot and then it should boot.
Click to expand...
Click to collapse
how can i do that? can you make a tutorial please ><?
kitsunezero said:
how can i do that? can you make a tutorial please ><?
Click to expand...
Click to collapse
Load temp recovery select wipe, advanced wipe, format all, reboot to bootloader, load temp recovery, install, reboot normally, if it boots but its on bootloop just make another rebokt and itshould boot
Hello lovely XDA-members,
this morning a new OTA update/patch came out for my OnePlus 3T, so I downloaded and tryed to install it right away. My phone is rooted on android 7.0 and I have TWRP 3.0.3-0 installed as my recovery. Normally (when I updated to nougat) after downloading a new update the phone reboots itself into TWRP and installs the update by itself, but not this time. I had to seqrch through my phone and had to install thw update manually. After that I rebooted the phone and it started booting the TWRP recovery again, I tried it again and again and again, nothint changed. So I tried to restore my backup with everything functioning, but this wouldnt help either. :/ I read the few existing threads with this problem and heard of a recovery flag that isnt cleared and the bootloader being the problem. One solution that I found was only for an LG phone and I'm afraid that I'll brick my brand new phone I have absolutely no idea what to do now, I would be so happy if someone could help me with this :$
I thank you in advance <3
Encoutered the same problem. Either you reflash the official or twrp recovery (neither did the trick to me) or use this "emergency tool" (which helped me):
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
Btw: TWRP 3.0.3-0 is not working well, switch to 3.0.3-1 beta
Good luck to you
I had the same problem.
How you can ''unbrick it'':
1. Flash a any rom available for the oneplus 3t via twrp
a. after this you will be still in twrp bootloop, to solve this go to step 2
2. Flash back stock recovery via twrp
Now your system will boot again
Optional: Flash back twrp
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Isus <3 said:
Just flash stock recovery via adb and you're done. It will fix the problem, you won't lose any data
Click to expand...
Click to collapse
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
EYT said:
@Isus <3 and @koentdm Do you have a download for the stock recovery, cause the oneplus download-site isnt working and I cant find any other downloads for it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0pr-ZA5b-1pNVlxV3ljMUFaUHc/view
Thank you so much, it worked
EYT said:
Thank you so much, it worked
Click to expand...
Click to collapse
No problemos my friendos
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Ifuckinghatemyselfandall said:
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Click to expand...
Click to collapse
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
flairepathos.info said:
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
Click to expand...
Click to collapse
I am going to try the mtk bypass tool, is that going to work? if not i am going to try your instructions, however it did not boot into the recovery even after reflashing , i have tried that before with the twrp app
It cannot detect the device, it isnt in device manager either, i am getting scared
edit: actually it gets detected in device manager as "usb serial device (com4)" when i hold the power button, volume up and volume down at the same time, when i do that, the device stays with a black screen
SP flash tool still does not detect it
it seems to be disconnecting while in this state
Please help, i cant turn the device off
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Ifuckinghatemyselfandall said:
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Click to expand...
Click to collapse
You need to flash the SAME miui version present on the device first.
VD171 said:
You need to flash the SAME miui version present on the device first.
Click to expand...
Click to collapse
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
It is now giving me "error status error" please help
Ifuckinghatemyselfandall said:
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
Click to expand...
Click to collapse
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
VD171 said:
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
Click to expand...
Click to collapse
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Ifuckinghatemyselfandall said:
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Click to expand...
Click to collapse
Custom recovery will never brick a device.
VD171 said:
Custom recovery will never brick a device.
Click to expand...
Click to collapse
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Ilovethewholeworldbutme said:
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Click to expand...
Click to collapse
Just flash the full stock miui again.
Hello,
As the title suggests, I've flashed a custom rom (EvolutionX to be exact), upon booting it up, mediatek Ims stops working, but that appears only on boot so it's not that big of a deal.
However, Upon rebooting into recovery (through system or via vol up+power) i get greeted by the SHRP logo but it powers off and on.
Fastboot mode works just fine, ROM works too, the recovery doesnt want to work though. I had the phone modded for 2 weeks and this is the first time this happened.
Any idea on i can fix it? I've already tried flashing the same recovery via fastboot but to no avail, i get an error saying:
fastboot: error: cannot load 'SHRP_v3.1_stable-Official_CD6-1630047089': Permission denied
That's weird, because my phone has an unlocked bootloader.
Any help would be greatly appreciated!
Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned
HaroldTech312 said:
Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned
Click to expand...
Click to collapse
i will try flashing stock xiaomi and then install a custom rom again
NewtonPL said:
i will try flashing stock xiaomi and then install a custom rom again
Click to expand...
Click to collapse
try it I can't guarantee you anything but if it comes back and the same thing happens it means that the rom is not compatible with your mobile and you will have to look for another one
If you still have doubts tell me that I can try to help you
the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now
NewtonPL said:
the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now
Click to expand...
Click to collapse
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.
Mineplayerminer said:
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.
Click to expand...
Click to collapse
what zip? this isnt about magisk mate.
NewtonPL said:
what zip? this isnt about magisk mate.
Click to expand...
Click to collapse
I mean the MIUI ROM in zip. But I figured it out, I unbricked mine by installing the MIUI from the SHRP.