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
Will there be any custom Rom for Alcatel One Touch Fierce? Just curious...planning to buy that
How did you get recovery for the phone??? I've been looking everywhere for one!!
Sent from my rooted ALCATEL ONE TOUCH Fierce running stock Kernel and ROM. Android version 2.2.2.
Step 1: Turn off your Android phone, and boot it into bootloader or fastboot mode.
Step 2: when in bootloader or fastboot mode, scrolling down to "Recovery" option using volume keys, trackball or optical sensor. Done. Your device will enter Clockwork recovery mode then.
help?
Im actually wondering that myself. i want to install a custom rom, i recently bought the phone and i dont like the default one
pretty sure he's referring to the stock recovery. I am working on hijacking the init and booting to a 2nd init recovery. Keep holding out guys, we'll be running all kinds of sweetness on this phone soon enough.
edit - Aaaand, there's my third "brick"
fixed my brick
Even tho it says not to remove the battery i did. I had no other choice, i tried just about everything. only way i was able to get a sign of life from the phone was by plugging it into a usb. then the led at the top left of the screen would turn on and nothing more. i bricked mine by using motochopper somehow, first it would say the root failed then i tried changing some things and eventually i got a device not found error. i gave up on that method of rooting but the phone was still working. then i found framaroot. i think i used the first exploit and it bricked. i took out the battery VERY carefully, waited 10 seconds(cant be too safe), reinserted the battery, and it rebooted and was rooted. now im just worried it might have not fully rooted. going to do some tinkering and if it bricks ill let you all know.
goodluck
Yeah the battery is super easy to take out without it looking like you messed with it. I have used both bohomir and faramir with no problems. If you're worried about partial root; do a full unroot with superSu, reboot, unroot with framaroot using the original exploit you chose, reboot then reroot.
Sent from my ALCATEL ONE TOUCH Fierce using xda app-developers app
If your not afraid of the rumors..
Kingo rooted my device inside of 2 minutes.. No Problem recognizing the Quad-Core Mediatek chip.
bad post
Bad post, sorry.
Any word on what ROMs this phone is capable of running? Or can it only be rooted?
my alcatel fierce 7024N is giving an error message that says, 'unfortunately fingerprint unlock has stopped' and because of it, I can't get into my phone. And yes I have tried, hard resetting it but the problem persists. Someone plz help. contact me on my email, [email protected]
I have a way to flash a backup rom.
I have the rom and a recovery to flash it.
If you want to try let me know.
BigCountry907 said:
I have a way to flash a backup rom.
I have the rom and a recovery to flash it.
If you want to try let me know.
Click to expand...
Click to collapse
What do u have to do?
backup please!
BigCountry907 said:
I have a way to flash a backup rom.
I have the rom and a recovery to flash it.
If you want to try let me know.
Click to expand...
Click to collapse
Hello, could you send me backup for alcatel 7024W ?, my cell has the problem that makes any change in the system, not save anything, and when I do a hard reset, not make any changes, as if the system were frozen...
BigCountry907 said:
I have a way to flash a backup rom.
I have the rom and a recovery to flash it.
If you want to try let me know.
Click to expand...
Click to collapse
Could you please me offer me the rom and recovery.
Thank you very much!
can someone please share or upload Alcatel fierce 2 OT-7040T firmware or a custom rom. Please i bricked my phone.
BigCountry907 said:
I have a way to flash a backup rom.
I have the rom and a recovery to flash it.
If you want to try let me know.
Click to expand...
Click to collapse
I would, if that is acceptable. How do I get it..? Thanks
This is only a factory rom.
But the recovery I made would let you recovery from a brick.
You will need to read through at least the last 5 pages to figure out what you need.
http://androidforums.com/threads/roms-for-the-fierce-2.918921/page-11
Hey guys, i have big issue with my device. I am new to this "world". Tried to install a costume rom but seems to me i've bricked my device. I unlocked my bootloader with official guide on htc.com. Then i wanted to instal mySense DX RC 4.0. Flash that bootloader and problem appeared. I can't boot my device anymore. I tried to do factory reset but nothing happened. Went into recovery mode but it showed me an error. Is there a way to unbrick my device ? If so please help me. I tried to find a guide for it for almost a 2 hours but i didn't find anything "understandable" for me.
marko96desire said:
Hey guys, i have big issue with my device. I am new to this "world". Tried to install a costume rom but seems to me i've bricked my device. I unlocked my bootloader with official guide on htc.com. Then i wanted to instal mySense DX RC 4.0. Flash that bootloader and problem appeared. I can't boot my device anymore. I tried to do factory reset but nothing happened. Went into recovery mode but it showed me an error. Is there a way to unbrick my device ? If so please help me. I tried to find a guide for it for almost a 2 hours but i didn't find anything "understandable" for me.
Click to expand...
Click to collapse
Which hboot version do you have and which recovery did you install?
dansou901 said:
Which hboot version do you have and which recovery did you install?
Click to expand...
Click to collapse
Hey, thanks for your reply. I got it all working. Seems that i haven't fastboot flashed boot for new costum rom...and that screwed my process
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
Hard bricked after instaling Zapdos Kernel
Ok, big problem.
I had OTA update 5.1 working well, also rooted.
When i installed Zapdos kernel, my phone got stucked on that Warning Bootloader Un... probably bricked
Cant turn on my phone now, and cant do anything cuz USB debugging is off.
I can access bootloader tho, and twrp, is there any way i can fix this?
What can i do now?
Please help, and thanks in advance.
You could download a custom rom and sideload it form your pc. or restore a backup.
magnetboard said:
You could download a custom rom and sideload it form your pc. or restore a backup.
Click to expand...
Click to collapse
Dont have an backup, that with custom rom could work, but im having another problem, my adb doesnt see any device, tryed everything, uninstaled drivers..
Maybe i got wrong ones?
taparan said:
Ok, big problem.
I had OTA update 5.1 working well, also rooted.
When i installed Zapdos kernel, my phone got stucked on that Warning Bootloader Un... probably bricked
Cant turn on my phone now, and cant do anything cuz USB debugging is off.
I can access bootloader tho, and twrp, is there any way i can fix this?
What can i do now?
Please help, and thanks in advance.
Click to expand...
Click to collapse
Download any custom rom and flash with TWRP...!!
taparan said:
Ok, big problem.
I had OTA update 5.1 working well, also rooted.
When i installed Zapdos kernel, my phone got stucked on that Warning Bootloader Un... probably bricked
Cant turn on my phone now, and cant do anything cuz USB debugging is off.
I can access bootloader tho, and twrp, is there any way i can fix this?
What can i do now?
Please help, and thanks in advance.
Click to expand...
Click to collapse
Same Problem here. In an attempt to unbrick it, I tried to flash the stock firmware by entering into fastboot and using mfastboot. Guess what? Two of the system files gave back an error when i tried to flash them and that was it. Now my phone's battery is really low (almost dead) and bootloader won't let me flash unless "Battery is OK" and i can't charge when i'm in bootloader =_=:crying:
taparan said:
Ok, big problem.
I had OTA update 5.1 working well, also rooted.
When i installed Zapdos kernel, my phone got stucked on that Warning Bootloader Un... probably bricked
Cant turn on my phone now, and cant do anything cuz USB debugging is off.
I can access bootloader tho, and twrp, is there any way i can fix this?
What can i do now?
Please help, and thanks in advance.
Click to expand...
Click to collapse
The Kernel Zapdos is not compatible with stock roms. I saw on a website that can even brick your machine (as you said) settle on a stock rom.
The site you downloaded did not warn you about this risk ???
{{{ Sorry for my bad English". I am a Brazilian and I am using Google translator (which is horrible). }}}