[Q] Can't boot into CWM! - Motorola Atrix HD

I am rooted and also have an unlock bootloader!
here's what i get when i try to boot into CWM!
An android icon with a red triangle!
google: android red triangle.

Probably lost your recovery
Did you just wipe your data, cache and/or dalvik from your recovery and not flash a new rom? More than likely you did something that got your recovery erased. You should just reload your recovery from the bootloader. I know I've had to do it a couple of times when I wasn't paying attention to what I was doing in my recovery.
bylithium said:
I am rooted and also have an unlock bootloader!
here's what i get when i try to boot into CWM!
An android icon with a red triangle!
google: android red triangle.
Click to expand...
Click to collapse

penser
bylithium said:
I am rooted and also have an unlock bootloader!
here's what i get when i try to boot into CWM!
An android icon with a red triangle!
google: android red triangle.
Click to expand...
Click to collapse
Open a root browser and find the "installrecovery.sh" file (I don't remember the location) and put ".bak" at the end of the filename. Reboot to fastboot and flash recovery, then you can successfully boot into it.

penser said:
Open a root browser and find the "installrecovery.sh" file (I don't remember the location) and put ".bak" at the end of the filename. Reboot to fastboot and flash recovery, then you can successfully boot into it.
Click to expand...
Click to collapse
Thank you so much, that has solved my problem much love to you brotha!

Related

[Q] i think i messed up

I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please
new problem
re edited to top post
Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.
Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!
Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread
bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?
No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip
Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2
Good catch!
Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope
You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img
Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img

Doesn't go into recovery

I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618
I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.
Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123
Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?
The stock recovery says it's not available anymore.
If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.
I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.
This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?
aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?
tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Would ADB be any better?
Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.
I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol
aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.
There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.

[Q] I done screwed up big time - the mystery of the unflashable recovery

Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.
PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?
gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?
nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Sorry, meant 4.4.2.
gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.

Boot loop after update

Hi. Last night I've updated to las OTA. After reboot and installation it make a reboot and never start again, it stopped in gear live initial logo and stay there until batteries end.
Now, when I plug the watch it show battery logo forever and if I press the bottom enough time it goes to startup infinite loop.
Some help?
Thanks!
Sent from my SM-N910F using XDA Free mobile app
Things that I've try:
Go into bootloader Ok.
Go into recovery fail: Do nothing and start to warmup.
Download twrp version 2.7.1.2-sp.img and twrp 2.8.6.0 and fastboot boot twrp.img: Nothing fastboot say ok and after that just nothing, watch start to warm
Download SamsungGearLive-sprat-ddPull-AdamOutlerDevice-24July2014.tar.gz ... inside lots of img's files, I've try to boot with recovery.img and.... nothing.
I'm soooo lost.
Mquinteiro said:
Things that I've try:
Go into bootloader Ok.
Go into recovery fail: Do nothing and start to warmup.
Download twrp version 2.7.1.2-sp.img and twrp 2.8.6.0 and fastboot boot twrp.img: Nothing fastboot say ok and after that just nothing, watch start to warm
Download SamsungGearLive-sprat-ddPull-AdamOutlerDevice-24July2014.tar.gz ... inside lots of img's files, I've try to boot with recovery.img and.... nothing.
I'm soooo lost.
Click to expand...
Click to collapse
Ok first things first: is your bootloader unlocked? if not then you can't flash/boot anything that is not signed by the Samsung/Google for our specific watch. So you can't boot into TWRP unless you unlock it. fastboot oem unlock will unlock it, but for security purposes, it will also reset your watch to factory.
Thanks Aligatror, it is not unlocked, i wish to restore to stock and I've tried to boot from external google//samsung recovery with out look.
Regarding the stock firmware i can't find anywhere instructions about how to flash everything and were to find factory images.
Thanks!
Sent from my SM-N910F using XDA Free mobile app
Did you try the Gear Live restore tool? It's in the gear live android development forum
Brendo said:
Did you try the Gear Live restore tool? It's in the gear live android development forum
Click to expand...
Click to collapse
Yes, it is a great tool, but there appears to be a broken bluetooth file in the v3 image which makes it impossible to pair watch to a phone. So, use V2 instead.
Brendo said:
Did you try the Gear Live restore tool? It's in the gear live android development forum
Click to expand...
Click to collapse
I do it and .... worst! now it still in boot loop but everithime show de lable "Recovery booting" Even in batery charge!
The only thing that works is bootloader.
Note I've unlocked and locked
Mquinteiro said:
I do it and .... worst! now it still in boot loop but everithime show de lable "Recovery booting" Even in batery charge!
The only thing that works is bootloader.
Note I've unlocked and locked
Click to expand...
Click to collapse
Which version did you download and what option did you select? Recovery boot message is normal when you do unlock since it erases the user partition. Select option to restore to stock or something like that in that program you downloaded. Just make you that you have version 2 and not 3.
I did with version 2 and 3 I do it by hand because linux script does not work.
I've flash boot recovery and system partitions included in the tool zip file.
And. ... nothing
Sent from my SM-N910F using XDA Free mobile app
Mquinteiro said:
I did with version 2 and 3 I do it by hand because linux script does not work.
I've flash boot recovery and system partitions included in the tool zip file.
And. ... nothing
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Is it still stuck in bootloop? Can you boot into recovery from bootloader?
I can't boot into recovery. Only bootloader works.
Every time that I press recovery from bootloader I get an "recovering boot " forever
Sent from my SM-N910F using XDA Free mobile app
Mquinteiro said:
I can't boot into recovery. Only bootloader works.
Every time that I press recovery from bootloader I get an "recovering boot " forever
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
Lets try something more radical.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
And then flash boot, recovery and system.
No, I can't go into recovery, just Bootloader. recovery hangs and normal boot hangs too.
I have take a look to update script and it have a new img for partitions associated with it.. I have flashed all of them and.... nothing.
Mquinteiro said:
No, I can't go into recovery, just Bootloader. recovery hangs and normal boot hangs too.
I have take a look to update script and it have a new img for partitions associated with it.. I have flashed all of them and.... nothing.
Click to expand...
Click to collapse
Try reflashing the bootloader itself. Download latest OTA update
sprat-LDZ22J-from-LWX49K.1e8de7cf.zip
Extract it and you'll see bunch of files "bootloader.xxxx.img". Flash all of the .img files.
fastboot flash apnhlos bootloader.apnhlos.img
fastboot flash aboot bootloader.aboot.img
.... and so on with all bootloader files.
Reboot bootloader and try booting into recovery or system.
aligatro2010 said:
Try reflashing the bootloader itself. Download latest OTA update
sprat-LDZ22J-from-LWX49K.1e8de7cf.zip
Extract it and you'll see bunch of files "bootloader.xxxx.img". Flash all of the .img files.
fastboot flash apnhlos bootloader.apnhlos.img
fastboot flash aboot bootloader.aboot.img
.... and so on with all bootloader files.
Reboot bootloader and try booting into recovery or system.
Click to expand...
Click to collapse
It is exactly what I did yesterday and no luck!
The only thing that I coulden't did was flash 5.1.1 recovery, and other partitions because it come like .p files (dif images)
But thanks
Mquinteiro said:
It is exactly what I did yesterday and no luck!
The only thing that I coulden't did was flash 5.1.1 recovery, and other partitions because it come like .p files (dif images)
But thanks
Click to expand...
Click to collapse
Well I guess your only option is to flash to 4.4, flash older bootloader and request repair service from Samsung.
aligatro2010 said:
Yes, it is a great tool, but there appears to be a broken bluetooth file in the v3 image which makes it impossible to pair watch to a phone. So, use V2 instead.
Click to expand...
Click to collapse
Is the watch effectively bricked once that image is flashed? I've come across your post too late after reading about the tool. Used v3, told the tool to restore to stock, the watch boots its image fine but the bluetooth is definitely broken now (phone won't connect to it). I can get to settings to enable ADB on wear but I can't authorize my PC it seems, never get the notification on the watch screen to allow the PC. It's just stuck at the initialization telling me to Install Android Wear on my phone.
naaaaail said:
Is the watch effectively bricked once that image is flashed? I've come across your post too late after reading about the tool. Used v3, told the tool to restore to stock, the watch boots its image fine but the bluetooth is definitely broken now (phone won't connect to it). I can get to settings to enable ADB on wear but I can't authorize my PC it seems, never get the notification on the watch screen to allow the PC. It's just stuck at the initialization telling me to Install Android Wear on my phone.
Click to expand...
Click to collapse
Its not bricked, but the bluetooth is not working due to corrupted file. You can flash v2 no problem. Just make sure to do reset after flashing.

Observation On Infinix Hot 2 [X510-D5110-Androidone-20151208] on Root

So today I embarked on what seemed to be a fruitless journey as I tried to root the Infinix Hot 2 on the latest build (December Security Patch of course) and I observed the following:
1. Flashing TWRP Recovery that was previously made for this device doesn't Flash. SP/Infinix Flash Tool flashes the recovery quite alright but booting to recovery with ADB afterwards gives a "No command" screen.
2. Kingroot (PC & Mobile) can't root this device as of yet :'(
3. I think the bootloader can be unlocked using the Android One Toolkit that was created for 1st Gen Android One devices. Reason being the fact it booted to fastboot and prompted me with the option to accept bootloader unlock or not.
Should you come come successful with flashing recovery or rooting this latest build, please comment your method. Thank you...
Link to Android One Toolkit:
http://forum.xda-developers.com/crossdevice-dev/android-one-general/toolbox-android-one-toolkit-one-click-t3030165
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
sabcpj said:
recovery partition is protected, it will get back to stock recovery if you boot the system. so you really need to boot recovery as the first thing you do after flashing.
which because of the similar bug we can't unlock our bootloader, is impossible to do with default setting. flash your lk partition with this:
http://www80.zippyshare.com/v/X4etwppD/file.html
taken from: http://forum.xda-developers.com/hot-2/development/android-one-rom-recovery-twrp-root-sp-t3227682
Click to expand...
Click to collapse
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
iAmWiz said:
Thanks I will try this in the morning...
One more question... Does this mean after flashing recovery I can boot directly into TWRP using key combo?
Click to expand...
Click to collapse
yes, you should be. and you need to
Alright then
sabcpj said:
yes, you should be. and you need to
Click to expand...
Click to collapse
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
iAmWiz said:
there is no scatter file for the lk-recovery.. I do not think I can flash it directly with Flash Tool without the scatter file
Click to expand...
Click to collapse
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
sabcpj said:
why do you think you need another scatter file. you already tried flashing twrp right? use that one. then change the location of partition named "lk" to point this file. that's all.
Click to expand...
Click to collapse
Alright. If I cannot get a workaround on this, I'll just Flash Infinix 5.1 ROM and wait till M
Try using towel root
https://towelroot.com/
Mysteryagr said:
Try using towel root
https://towelroot.com/
Click to expand...
Click to collapse
Thanks but towelroot didn't work out.
Root achieved... More at
http://forum.xda-developers.com/hot-2/development/root-recovery-xposed-successfully-t3276420
please can you help me sp flashtool stuck at 0 and nothing happens

Categories

Resources