I tried searching but im still having trouble....
I have the Mytouch 3G and ive been running Cyanogen since 4.1. I did the upgrade to 4.2.1 with no problems. Today the browser randomly started force closing so I rebooted and now its stuck in a loop. The mytouch splash screen comes up for about 10 seconds and then reboots. It won't let me get into recovery mode but I can get into fastboot mode.
I downloaded the SDK and installed the driver so that I could use fastboot but when I click the fastboot.exe it comes up for a split second and then disappears.
Any help would be appreciated, or any other solutions than what im trying to do.thanks
EDIT: I'm dumb. im using command prompt and trying to boot the cm recovery image now. I used "fastboot boot cm-recovery-1.4.img" and it seems to be stuck on "downloading 'boot.img'"
anyone? please?
Fastboot isn't working at all, maybe because I didn't having debugging enabled before? I tried following the steps at http://forum.xda-developers.com/showthread.php?t=547133 but i can't make a gold card following that tutorial and it didnt work with just a regular SD card
Can someone please help? Am I posting in the wrong section?
what happens if you turn it off and then boot into recovery?
Do you have apps2sd? swap?
BTW: to use fastboot you dont click it you use it as a line command... eg. fastboot boot amon1.2.2.img
I forgot to mention that I'm not able to boot into recovery, but I am able to boot into fastboot mode. When I use fastboot to try and load something to the phone, I get a "remote: failed" message.
I don't have any special partitions on my sd, and I hadn't changed anything on the phone besides upgrading to 4.2.1 the day before.
Bump. Anyone else?
Hello everyone,
As a new member I would like to extend my sincere thanks to everyone who posts here and that makes working with my Atrix possible. Please forgive any misuse of terms etc. As I said I am new and I truly would like to learn to flash roms and recover easily etc, but I am overwhelmed right now and just want my phone to work again - with any rom!
Last night I unlocked my phone (rooted ATT 4.5.140 - 2.3.6 OTA) using unlock v4.2 and everything went smoothly. I downloaded CWM manager and Superuser and then thought I was creating a backup. I then tried to flash to CM7 and began having what I assume are boot loop issues: The CM7 splash screen with the circling arrow would repeat several times and then I would see the skateboard guy move across the screen several times and then the phone would just shut down. From here I tried to go to Android Restore and restore from the back up but that wouldn't work. I next downloaded Blue 5.0.2.7-atrix5 (because the writing on my screen is blue), moved it to my external SD card via PC, booted phone to Android Restore, then ran the zip. Same issue. Lastly I tried to restore to an older stock ROM (ATT 4.5.140 - 2.3.6). Now I am stuck in a "boot loop" that gets to the dual core screen to appear for a second or two, then repeats itself. I also tried to flash using moto-fastboot with the same results. I can still get to the restore screens and fastboot so I don't think I am dealing with a brick situation.
I am hoping someone can help me get around this. I have read so many 85+ page threads that my head is spinning and I am really no closer to resolving on my own.
Thanks in advance for everyone's patience and any assistance rendered!
Cheers!
Chris
Did you do proper wipes? Try fastboot erase system, fastboot erase cache etc etc. You can search the forums for the various fastboot erase commands. You definitely aren't hardbricked yet
Sent from my MB860 using xda app-developers app
Hey Aaron
I know I did wipes from the Android Recovery screens - I'll try from fastboot and post back. Thanks for answering!
Chris
bert26 said:
Hey Aaron
I know I did wipes from the Android Recovery screens - I'll try from fastboot and post back. Thanks for answering!
Chris
Click to expand...
Click to collapse
What version of cwm recovery are you using? Make sure you have it up-to-date. Older versions don't wipe properly.
Sent from my MB860 using xda premium
I've executed the following:
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
flash ROM in recovery
wipe Dalvik
wipe cache
reboot
The device has been on the dual core screen (steady - not just for a couple of seconds at a time) for over 5 minutes. I will give it a few more and then pop the battery.
As far as I know I am running CWM 5.0.0.8 although I don't know how to be certain. It was the first one that came up in the play store.
but it's not giving you any errors on the logo/bios screen? like Fail to boot 0x00010 something?
i'm out of ideas beyond trying a different rom. you could try the wipe process again and test a different rom like nottachtrix. i'd wait for someone else to post who might have more ideas
No errors at all, just stuck on the dual core screen, even after battery removal. I am searching other threads for this specific issue now. Feels like I'm making progress since it's at least not looping. Thanks again!
Wow! Looks like I just caught a break. Out of desperation I tried to re-flash CM7 and whaddya know! The thing booted right up! I can only assume it was due to the full on wiping that was suggested.
Thanks so much for pointing me in the right direction and for taking the time to help a n00b.
Cheers!
I would have posted this to the thread it is in but I do not have enough post to be able to post in the Development forums yet.
I was very glad when I found the thread [RECOVERY][mojo] TWRP 2.8.2.0 recovery Mad Catz M.O.J.O. in the MOJO Development forum. I was hoping I would be able to find a custom recovery solution. I was able to install the image and root my MOJO. Unfortunately though I am unable to boot the image using
Code:
fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
When doing this from cmd prompt I get the TeamWin splash screen but then it goes back to the Key driver not found.. Booting OS screen.
Can someone please explain how I get into recovery mode?
Sir Jaxxy said:
I would have posted this to the thread it is in but I do not have enough post to be able to post in the Development forums yet.
I was very glad when I found the thread [RECOVERY][mojo] TWRP 2.8.2.0 recovery Mad Catz M.O.J.O. in the MOJO Development forum. I was hoping I would be able to find a custom recovery solution. I was able to install the image and root my MOJO. Unfortunately though I am unable to boot the image using
Code:
fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
When doing this from cmd prompt I get the TeamWin splash screen but then it goes back to the Key driver not found.. Booting OS screen.
Can someone please explain how I get into recovery mode?
Click to expand...
Click to collapse
I am releasing a new build now please give it a go. I had a custom theme applied and therefore I didn't get the error everyone else faces.
While trying to root my OPT I have done something terrible here.
Able to :
Boot into fastboot mode.
Not able to :
- Boot into phone
- Boot into recovery
- When trying to normal booting, phone just keeps into booting in loop.
Cannot flash recovery because fastboot device info says , device unlocked : false
When I try to unlock oem it just puts the phone into booting loop.
Please help out guys.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Hi Thanks for the reply Heisenberg.
My device is not hard bricked .. I am still getting a response ( fastboot working ),
Should I go ahead and follow the process mentioned in this thread for Hard Bricked device ??
Heisenberg said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
arescool said:
Hi Thanks for the reply Heisenberg.
My device is not hard bricked .. I am still getting a response ( fastboot working ),
Should I go ahead and follow the process mentioned in this thread for Hard Bricked device ??
Click to expand...
Click to collapse
Yeah I know it isn't hard bricked. If you have no access to recovery it's going to be your only option though.
shall i know what you have done with your phone before end up here?
Sent from my ONE A2003 using Tapatalk
You could also boot to recovery through the following command:
Code:
fastboot boot "path to the recovery image.img"
markus1540 said:
You could also boot to recovery through the following command:
Code:
fastboot boot "path to the recovery image.img"
Click to expand...
Click to collapse
That's an excellent idea, I didn't think of that. @arescool, this would allow you to flash a ROM zip.
UnBricked
Thanks you so much Heisenberg
The thread you provided really helped, and the method suggested by Lord Boeffla worked for me finally !!!
Please mark this thread as solved and closed
Thanks,
Raj
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
This is from the twrp website https://twrp.me/xiaomi/xiaomimi9t.html
Note many devices will replace your custom recovery automatically during first boot.
Click to expand...
Click to collapse
After flashing the recovery :
Code:
fastboot flash recovery twrp.img
enter the code to reboot in recovery :
Code:
fastboot oem reboot-recovery
DELLINSPIRON1958 said:
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
Click to expand...
Click to collapse
U have to flash the modified vbmeta.img in order to keep a custom recovery..
Hello ,
There is no other solution ?
DELLINSPIRON1958 said:
Hello ,
There is no other solution ?
Click to expand...
Click to collapse
Have you tried by forcing reboot to Recovery/TWRP right after flashing TWRP (answer from another user, post #2):
>>fastboot oem reboot-recovery
Are you using e.g. the official TWRP 3.4.0, and did you enter in TWRP your Android screen unlock code, for TWRP to be able to properly work with File Systems on Data and Internal memory?
I am a neophyte, can you give me precise details of the method, thanking you
DELLINSPIRON1958 said:
I am a neophyte, can you give me precise details of the method, thanking you
Click to expand...
Click to collapse
Read post #2 - if you are not familiar with Fastboot, please search by Google and read - but how else did you flash TWRP than from Fastboot.
After flashing TWRP from Fastboot (1st command), use 2nd command to force direct rebooting to TWRP - without pinpointing with Vol+&Pow buttons, etc.
But really, nothing else, just that
Search here for thread about Official TWRP 3.4.0, download and flash that TWRP for davinci
When you enter to TWRP, it will ask you for your Android screen unlock pin/password (you should know your own one you use when booting to Android and when you are unlocking the locked screen in Android), enter that one when TWRP prompts you and wait few seconds (it should report success)
There is no rocket science here to teach more about ?, you just need to follow and try
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
DELLINSPIRON1958 said:
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
Click to expand...
Click to collapse
Try as described above:
- download official TWRP for davinci
- flash from Fastboot and reboot to TWRP with the given command
- in TWRP, enter your Android screen unlock code and check does TWRP correctly read your files on Internal memory (e.g. seeing proper file names in Download, not some garbage names)
- try to reboot to recovery (by TWRP command or by using Vol+) and check if it reboots to TWRP, not to stock Recovery
Please don't waste time by further endless questions, until you first try and have concrete questions/results (can't expect that people will pay attention to answer if you at least don't even try - why should then anybody waste the time)
I can't guarantee you 100% but I always have bootable TWRP, properly reading Storage (I also have boot.img patched by Magisk, hence not 100% same environment like you)
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
thank you for your reply. while searching on the net, I noticed that there are several answers to this problem, but which one is the right one?
without the phone being out
DELLINSPIRON1958 said:
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
Click to expand...
Click to collapse
For each member you can simply judge the credibility of his posts by his 'degree' on XDA forum, for which devices and topics he mostly diiscusses about and how many people thanked his posts
E.g. if I ask how to flash Xiaomi, Mi 9T and receive a suspicious 'guide' from somebody who only participated in discussions about Nokia phones, and who even did not get Thanks there for his participation, I will probably fully ignore and not risk to brick my phone
But if I get an answer from somebody who maybe participated for a year or two in topics on Poco and Redmi Note but who got hundreds of Thanks for his posts there, I will consider that he likely very well knows about flashing Xiaomi phones, although maybe never had Mi 9T in his hands.
Moreover, if I see that two or more people guide me in the same direction.
So I would at least google myself for more info (and then ask if still something not clear), and try - specially if that what was suggested does not sound as something to potentially brick my phone
After all, this is hackers forum and everybody is responsible himself for his phone. But on the other side, nobody was born with the knowledge but learnt by searching, reading and trying things herself
Also, everybody helps for free and by his good will, and sooner or later finds useless to waste time to answer for something that was already answered by his best (what else/new to answer), but the other one did not even want to try
Of course (as also in my previous post), things work for me as you wanted but yes, I always immediately flash together the boot image patched by Magisk.
So you can try would it work with the fully stock Boot - if yes, good for you.
If not, you can consider going to root by Magisk (although, being so cautious, it would probably take much more time and many, many more new questions before ?)
Kaiwalya said:
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
Click to expand...
Click to collapse
So just tested the following on my MIUI 12.0.2 QFJEUXM, with (unofficial) TWRP 3.4.0.2 from brigudav and Canary Magisk 20424
- Booted to TWRP and flashed stock 12.0.2 eea Boot.img
- Immediately rebooted back to Recovery - that is to TWRP and (that step is also important!) entered my Android screen unlock pin to assure that TWRP 'touched' the Data
- Rebooted to Android (System), where ofc, Magisk Manager showed that Magisk was no more installed
Then rebooted to Recovery (by keeping pressed Vol+) and phone booted to TWRP, not to the stock Recovery!!!
Hence the stock Boot image did not overwrite my TWRP with stock Recovery (although without having Magisk flashed at the time), because of properly doing each and every step as above!
(At the end, flashed back my patched Boot.img from TWRP, rebooted to Android and continued to use Magisk with all previously installed modules, etc)
Btw, I have never flashed any VBMeta, decrypted storage or so
PS:
And believe me, I lost myself TWRP many times (having to reflash it from Fastboot again and again when I was uninstalling Magisk, updating MIUI from TWRP and so), before learning that every step counts?.