Related
hey friends,
i've purchased huawei mts sp101/c8511 and wanted to unlock the boot loader. i tried using fast boot by using command "fastboot oem unlock" but it returns the message failed with "invalid command". can anynody please tell me what i'm doing wrong. usb drivers are okay and running.
sam87matte said:
hey friends,
i've purchased huawei mts sp101/c8511 and wanted to unlock the boot loader. i tried using fast boot by using command "fastboot oem unlock" but it returns the message failed with "invalid command". can anynody please tell me what i'm doing wrong. usb drivers are okay and running.
Click to expand...
Click to collapse
Only Nexus Devices can be unlocked this way.
What should you do?
Download Super One Click(Google is your friend)
Get your devices drivers and root your phone with Super One Click
Remember: Only Nexus's can be unlocked via fastboot...
<<<<<<<<<<<<<Hit Thanks /Danke/ Merci
Thnx for the soltn bt there's more
Thanks for the solution. But actual problem is that i wanted to flash custom rom that is bricking my phone. Tried gb 2.3 on my froyo but it kept crashing on next immidiate boot. Isn't bootloader denying to flash that rom, is it? That's my reason for unlocking my bootloader.also, is it the locked carrier that prohibiting the rom to operate or my phone that isn't upgradable. I can't figure that out. Plz give me another way to flash custom rom on my rooted phone. Thanx for info!waiting for the solution
Too complicated...
sam87matte said:
Thanks for the solution. But actual problem is that i wanted to flash custom rom that is bricking my phone. Tried gb 2.3 on my froyo but it kept crashing on next immidiate boot. Isn't bootloader denying to flash that rom, is it? That's my reason for unlocking my bootloader.also, is it the locked carrier that prohibiting the rom to operate or my phone that isn't upgradable. I can't figure that out. Plz give me another way to flash custom rom on my rooted phone. Thanx for info!waiting for the solution
Click to expand...
Click to collapse
The million dollar question is where are you going wrong?
Do you have a custom recovery e.g Clockworkmod for your phone?
If not follow instructions here
Is the ROM specifically for your device?
Try CM 7
Is you bootloader really unlocked?
Try Z4root for the job
Try flashing the new rom via custom recovery and make sure you have this prerequisites. You are a big boy, you know what to do!
PS: If you want to unlock your phone(Locked Carrier) try this
nice work
:cyclops:Yes i'm impressed. nice work with the contact details. sorry it took me so long, i followed your advice and downloaded the cm7. only problem i faced with it that, my recovery flashed a message that the rom was made for m860. i tried to edit that rom in kitchen by using my boot.img. but still no success.can you please suggest what should i be modifying to convert that rom into mine.:good:
Port CM7 to your device
sam87matte said:
:cyclops:Yes i'm impressed. nice work with the contact details. sorry it took me so long, i followed your advice and downloaded the cm7. only problem i faced with it that, my recovery flashed a message that the rom was made for m860. i tried to edit that rom in kitchen by using my boot.img. but still no success.can you please suggest what should i be modifying to convert that rom into mine.:good:
Click to expand...
Click to collapse
This way you will learn more about developing and also solve your problem
Click here for the info
Usefull
Help with clockwork/TWRP recovery?
trapinha said:
Usefull
Click to expand...
Click to collapse
Does anyone here know how to fix the clockwork or TWRP recovery? My tablet will not load recovery, it hangs at "loading recovery image"
its worth trying
This way you will learn more about developing and also solve your problem
Click to expand...
Click to collapse
porting seems bit complex procedure but still its not impossible. probably a better option for me rather than stay stuck with my froyo. i'll give it a try. thanks a lot.:highfive:
reflash the recovery
Does anyone here know how to fix the clockwork or TWRP recovery? My tablet will not load recovery, it hangs at "loading recovery image"
Click to expand...
Click to collapse
recovery problem occurs if flashed recovery doesn't belong to the desired device. find suitable cwm/twrp recovery for the tab and flash it in your device. for latest twrp:- HERE
Well i used to have a hox+ with Android Revolution custom rom and a custom kernel. I tried to power it up but it stucks at htc logo,then reboots and goes straight to twrp recovery. I tried to flash again the rom via adb but i can't see my device in cmd. I found and dowloaed htc drivers my htc,plus adk and htc sync manager but still no luck..any ideas what is going on here?
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
i360droid said:
do a full system reset in cwm recovery
now install the rom
reboot into fastboot
fastboot flash boot boot.img for the rom
Click to expand...
Click to collapse
fastboot is not recognised etc...........any ideas?
smavr said:
fastboot is not recognised etc...........any ideas?
Click to expand...
Click to collapse
ok, add me on skype, i360faceplant, i will walk you through it step by step
i360droid said:
ok, add me on skype, i360faceplant, i will walk you through it step by step
Click to expand...
Click to collapse
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
smavr said:
Well i actually found what happened..my old hox+ works perfectly now..thanks for your help anyway
Click to expand...
Click to collapse
what was up with it?
i360droid said:
what was up with it?
Click to expand...
Click to collapse
Well, i just made a mistake at adb sideload...
smavr said:
Well, i just made a mistake at adb sideload...
Click to expand...
Click to collapse
lol
i360droid said:
lol
Click to expand...
Click to collapse
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
ahighfield said:
Somewhat similar situation. I previously rooted my HTC One X+ (Intl) with Viper X+ rom. I thought I would experiment with it as it is no longer my daily phone, and since I liked the Cyanogen experience on OnePlus One, thought i would try to install it on the HOX+.
I followed these official (?) instructions http://wiki.cyanogenmod.org/w/Install_CM_for_enrc2b#Installing_recovery_using_fastboot, however, after getting CWM recovery on and then flashing via sideload command the ROM, I am now stuck in the CM bootloop animation and computer no longer recognises the device, and can't find anyway to get back to bootloader, recovery etc.
I did read about bootloop issues after this and some people said that the boot.imhg file should have been flashed separately (thanks CM for not including that instruction!), and somehow my computer recognised it one more time after the bootlooping started and I managed to get into fastboot to flash boot.img, but, then rebooted and bootloop again. Since then I have had no way to get back into recovery or bootloader, so it just runs until battery dies.
Should it go into the bin? Or anything else I should try?
Thanks so much for any
EDIT: Solved...I was able to get recovery back, then did full reset and followed instructions above re boot.img flash and now am back into my phone with a new lease on life and CM ROM!!
Click to expand...
Click to collapse
to get into bootloader, hold down the vol down and power, the home lights will flash (atleast they do when its booting), it will reboot, when you get the htc logo, let go of power button. and now try a stable er version of the rom.
---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------
ahighfield said:
Two more noob questions if I may, now that I have my HOX+ back...
I am now running CM 10.2.1-enrc2b.
I have 3 updates available and being offered to me (upgrade to CM11 from CM10):
- cm-11-20140308-SNAPSHOT-M4
- cm-11-20140916-SNAPSHOT-M10
- cm-11-20140916-SNAPSHOT-M12
1. I downloaded and installed the latest M12, but upon rebooting it went into a bootloop for 15mins+. I then followed your instructions again to get back. So, it seems I at least need to install them in order starting from the earliest (ie M4), but before doing so I wanted to check if anyone knows if these are even compatible with my HOX+ (Intl)?
2. Which would be the best place to get the right gapps package and installation instructions (if CM can get it wrong, am now wary of someone else leaving out the critical boot.img flash step eg)?
Thanks!
Sent from my Nexus 7 using XDA Free mobile app
EDIT: Nothing like some self-help. I am good now.
Click to expand...
Click to collapse
ok, dont do an ota update in cm, you need s-off, which you cant get on the hox+
flash the rom, flash the boot image, boot, reboot into recovery, SIDELOAD gapps and that should work. use cm10 for the moment, as cm11 has an annoying system ui crash loop bug.
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
ahighfield said:
Thanks again for your clear and helpful pointers that got me out of a mess, I seem to have figured it out, downloaded the latest CM11 update and extracted boot.img for separate flashing and it all worked, then added gapps and seems working good now (except for dead touch zone from kids dropping it too many times probably!). The OTAs clearly don't work as is and CM probably should update their instructions and how they push major updates that need a new boot.img. Now to work out what to do with my spare phone...!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The phone will boot loop, as the kernal is different to the rom
Hello....i rooted my sm-g360az samsung phone and when i restarted the phone, it didn't boot up to the home screen. It shows the samsung logo and then becomes blank....i later on came to know on the internet that i hadnt enabled 'oem unlock' on 'developer options' before rooting. I sent the phone to samsung for repair and they sent it back to me today saying that the phone is beyond repair because it was rooted, though i hadnt mentioned to them that i had rooted the phone. How do i get my phone to work again? I need it very badly for work purposes. Can somebody help me with this....
You need to flash stock rom for your device via odin.
røbin said:
you need to flash stock rom for your device via odin.
Click to expand...
Click to collapse
hello robin....thanks for the reply my brother.....can you help me with links of the firmware files for sm-g360az brother? I searched on the iternet, but im unable to find them for free....
alvcross said:
hello robin....thanks for the reply my brother.....can you help me with links of the firmware files for sm-g360az brother? I searched on the iternet, but im unable to find them for free....
Click to expand...
Click to collapse
It is hard to find stock firmware for your device but check this linkhttp://www.easy-firmware.com/index.php?a=browse&b=category&id=3228 Did you visited this page?
røbin said:
it is hard to find stock firmware for your device but check this linkhttp://www.easy-firmware.com/index.php?a=browse&b=category&id=3228 did you visited this page?
Click to expand...
Click to collapse
yes my brother....i did visit that page before.....but it says that downloads are available only to paid users....
alvcross said:
yes my brother....i did visit that page before.....but it says that downloads are available only to paid users....
Click to expand...
Click to collapse
https://samsung-firmware.org/model/SM-G361F/ both device have same spec.So you can try this version.
røbin said:
https://samsung-firmware.org/model/sm-g361f/ both device have same spec.so you can try this version.
Click to expand...
Click to collapse
ohhh wooowww....thank you soo soo soo very much my brother.....but will this cause any problems to the sm-g360az phone?
alvcross said:
ohhh wooowww....thank you soo soo soo very much my brother.....but will this cause any problems to the sm-g360az phone?
Click to expand...
Click to collapse
Can't 100% guarantee you that it will work or not.Both device have same spec so it should work but one have 2mp font camera and other have 1.9mp camera. It shouldn't be a big problem I think.
And can you also tell me weather you were taking about sm-g361f or sm-g360f brother? Can you mention the exact model number I should try flashing with? THERE ARE MANY MODELS IN SM-G360....WHICH ONE WOULD SUIT THE BEST BROTHER?
alvcross said:
And can you also tell me weather you were taking about sm-g361f or sm-g360f brother? Can you mention the exact model number I should try flashing with? THERE ARE MANY MODELS IN SM-G360....WHICH ONE WOULD SUIT THE BEST BROTHER?
Click to expand...
Click to collapse
All the version are same.Those files are from different region. So you can choose any region.but download lte version only.
røbin said:
all the version are same.those files are from different region. So you can choose any region.but download lte version only.
Click to expand...
Click to collapse
ohhh....wowwww....okay my brother....ill download the firmware...flash the files and let you know....thank you so very much for the help my brother....god bless you....
alvcross said:
ohhh....wowwww....okay my brother....ill download the firmware...flash the files and let you know....thank you so very much for the help my brother....god bless you....
Click to expand...
Click to collapse
Don't just say thanks.Hit the thanks button If you thik I helped you
røbin said:
don't just say thanks.hit the thanks button if you thik i helped you
Click to expand...
Click to collapse
yes my brother....i did just that....i downloaded the firmware files and tried to flash with odin....but the flash doesnt proceed....it gets stuck in initialization cause of the locked bootloader....i hadnt enabled 'oem unlock' when the phone was working....and also in the download mode it shows 'secureboot - enabled'.....so the locked bootloader is not allowing odin to flash.....the phone is being recognized by adb and it shows up with a serial number as recovery in the adb console....is there any way i could enable oem unlock and unlock the bootloader through adb commands?
alvcross said:
yes my brother....i did just that....i downloaded the firmware files and tried to flash with odin....but the flash doesnt proceed....it gets stuck in initialization cause of the locked bootloader....i hadnt enabled 'oem unlock' when the phone was working....and also in the download mode it shows 'secureboot - enabled'.....so the locked bootloader is not allowing odin to flash.....the phone is being recognized by adb and it shows up with a serial number as recovery in the adb console....is there any way i could enable oem unlock and unlock the bootloader through adb commands?
Click to expand...
Click to collapse
You need to install twrp via odin and from twrp you need to do a full factory reset(data,cache,delvik,phone memory).after that try again to flash stock rom via odin.Here is the twrp link for your device http://teamw.in/devices/samsunggalaxycoreprimequalcomm.html
Røbin said:
You need to install twrp via odin and from twrp you need to do a full factory reset(data,cache,delvik,phone memory).after that try again to flash stock rom via odin.Here is the twrp link for your device http://teamw.in/devices/samsunggalaxycoreprimequalcomm.html
Click to expand...
Click to collapse
Oh my god.....wonder of wonders my brother.....i downloaded TWRP from the link you gave me and flashed it with odin and to my surprise the phone booted up to the home screen after flashing was done.....the phone is back and working now.....wooowwwww.....thank you soooo soooo soooo very much my brother.....this forum needs many good hearted and wonderful people like you....Words cant express how happy I am.....thank you....thank you....thank you my brother....:victory:
alvcross said:
Oh my god.....wonder of wonders my brother.....i downloaded TWRP from the link you gave me and flashed it with odin and to my surprise the phone booted up to the home screen after flashing was done.....the phone is back and working now.....wooowwwww.....thank you soooo soooo soooo very much my brother.....this forum needs many good hearted and wonderful people like you....Words cant express how happy I am.....thank you....thank you....thank you my brother....:victory:
Click to expand...
Click to collapse
I'm also very happy that I helped you and Now you get your bricked phone back to normal.
Røbin said:
I'm also very happy that I helped you and Now you get your bricked phone back to normal.
Click to expand...
Click to collapse
but there is still some problem brother.....after flashing twrp 3 with odin the phone booted up to the home screen anad all my apps and settings were intact....but when i restarted the phone again....it showed the boot screen and then went blank.....i reflashed the twrp with odin again and it booted up to the home screen.....this time I MADE A FACTORY RESET AND AGAIN THERE WAS THE SAME PROBLEM.....PHONE WAS NOT BOOTING UP TO THE HOME SCREEN.....I REFLASHED TWRP AGAIN....BOOTED UP TO HOME SCREEN AND TRIED SOFTWARE UPDATES....BUT I GOT A MESSAGE SAYING THAT THE PHONE WAS MODIFIED IN AN UNAUTHORIZED WAY AND THAT I COULD TRY USING KIES FOR UPDATES.....
THE BOOTLOADER SEEMS TO BE DAMAGED.....CAN YOU TELL ME HOW TO UNLOCK THE BOOTLOADER WITH ADB BROTHER? WHEN I TYPE REBOOT RECOVERY THROUGH ADB, THE PHONE REBOOTS AND WHEN IT COMES TO THE TWRP RECOVERY SCREEN, IT TURNS BLANK....SO IM UNABLE TO GO INTO TWRP TO WIPE SOME STUFF AS YOU HAD SUGGESTED EARLIER....SHOULD I TRY CWM?
alvcross said:
but there is still some problem brother.....after flashing twrp 3 with odin the phone booted up to the home screen anad all my apps and settings were intact....but when i restarted the phone again....it showed the boot screen and then went blank.....i reflashed the twrp with odin again and it booted up to the home screen.....this time I MADE A FACTORY RESET AND AGAIN THERE WAS THE SAME PROBLEM.....PHONE WAS NOT BOOTING UP TO THE HOME SCREEN.....I REFLASHED TWRP AGAIN....BOOTED UP TO HOME SCREEN AND TRIED SOFTWARE UPDATES....BUT I GOT A MESSAGE SAYING THAT THE PHONE WAS MODIFIED IN AN UNAUTHORIZED WAY AND THAT I COULD TRY USING KIES FOR UPDATES.....
THE BOOTLOADER SEEMS TO BE DAMAGED.....CAN YOU TELL ME HOW TO UNLOCK THE BOOTLOADER WITH ADB BROTHER? WHEN I TYPE REBOOT RECOVERY THROUGH ADB, THE PHONE REBOOTS AND WHEN IT COMES TO THE TWRP RECOVERY SCREEN, IT TURNS BLANK....SO IM UNABLE TO GO INTO TWRP TO WIPE SOME STUFF AS YOU HAD SUGGESTED EARLIER....SHOULD I TRY CWM?
Click to expand...
Click to collapse
If locked bootloader causing this problem than you might want to try this http://unlock-bootloader.net/how-to/unlock-bootloader-samsung-galaxy-core-prime/ Follow the guide and unlock bootloader to see if this problem solve for good.
There is Android Marshmallow custom rom for your device too
Røbin said:
If locked bootloader causing this problem than you might want to try this http://unlock-bootloader.net/how-to/unlock-bootloader-samsung-galaxy-core-prime/ Follow the guide and unlock bootloader to see if this problem solve for good.
There is Android Marshmallow custom rom for your device too
Click to expand...
Click to collapse
thanks for the link brother.....but that website is a fake website with fake android 6 custom rom links....
brother....do you have a SM-G360AZ MOBILE? CAN YOU INSTALL FLASHIFY ON YOUR PHONE AND TAKE A BACKUP IMAGE OF THE STOCK RECOVERY AND UPLOAD A LINK HERE....
TWRP IS NOT WORKING....THE PHONE REACHES RECOVERY AND THEN TURNS BLANK....
alvcross said:
thanks for the link brother.....but that website is a fake website with fake android 6 custom rom links....
brother....do you have a SM-G360AZ MOBILE? CAN YOU INSTALL FLASHIFY ON YOUR PHONE AND TAKE A BACKUP IMAGE OF THE STOCK RECOVERY AND UPLOAD A LINK HERE....
TWRP IS NOT WORKING....THE PHONE REACHES RECOVERY AND THEN TURNS BLANK....
Click to expand...
Click to collapse
Why do you need stock recovery?There's no stock recovery available for your device.Try to instell different twrp version for your phone.
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
Hello Folks!
I recently updated the BL of my OPX which was running Ressuerection Remix 5.1.1,and TWRP from blu_spark.Im pretty sure i had unlocked the bootloader but after I updated the BL using this method https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917.
But now its stuck at One Plus logo and when ever i try to turn it off,it vibrates and turns back on.I cant access the recovery either please help.BTW i can access the fastboot.
Please help
**EDIT**Just followed the Mega-umbrik guide and now its all perfect
Because you didn't update your TWRP I believe. Also the mega unbrick guide was overkill if you have fastboot but at least your up and running again.
Exodusche said:
Because you didn't update your TWRP I believe. Also the mega unbrick guide was overkill if you have fastboot but at least your up and running again.
Click to expand...
Click to collapse
I also had the same problem as OP yesterday.
I had to do the mega unbrick guide, because fastboot can't do anything in that state either. Flashing was not possible (error message: device not unlocked, cannot flash or erase), = bricked
For everyone who can't do anything than entering fastboot (e.g. no recovery, restarting every second) the mega unbrick is necessary. (At least it was in my case.)
Installing the drivers for the unbrick guide was also a pain, because my OS didn't recognized my device in the first place. I had to play with the hardware keys to get it recognized.
Noneatme said:
I also had the same problem as OP yesterday.
I had to do the mega unbrick guide, because fastboot can't do anything in that state either. Flashing was not possible (error message: device not unlocked, cannot flash or erase), = bricked
.
Click to expand...
Click to collapse
My apologies didn't read guess yeah bootloader locked nothing would work except mega unbrick guide. One trick I've read maybe help someone is rolling back the driver think for Windows 10.
Exodusche said:
My apologies didn't read guess yeah bootloader locked nothing would work except mega unbrick guide. One trick I've read maybe help someone is rolling back the driver think for Windows 10.
Click to expand...
Click to collapse
Yeah I learned to be very careful with what to flash and what not. I hope I will never get my devices bricked again, lol.