Related
Hey guys,
i did stupid things witch my razr i and now i'm completely lost…maybe someone can help?
I've been impatient enough to try to flash the leaked jb rom 3 days ago. That did'nt work
No, whenever i power up the phone it shows the red M logo and nothing happens.
I can power it down by holding vol+down and power for more than 4 seconds.
If i release the keys, it goes back to te red M,
If i keep holding vol+down it boot s into AP fastboot flash mode (secure boot) 20.0f
i can choose recovery and that'll work, but i don't have an update for external storage. rebooting from there leads to red M.
Normal Powerup, Factory and BP Tools are choosable, log says Booting into… but nothing happens after that, i'll stay in fastboot.
Power off works.
I tried to flash various images via »fastboot flash boot/recovery/system«, but nothing worked out.
I flashed the files from Razri_Root_Linux, two files (retail central europe) from here sbf.droid-developers, but nothing helped, every reboot leads to the red M.
I read about RSD-Lite, tried to install it under Win7, got it, but was lost after the Program always complained about an invalid xml.
Since i don't own that machine i went back to my linuxbox where i found sbf_flash, but i don't get it how to put the pieces together (which file/s to use)
Any hints on how to go from here?
[EDIT:] I downloaded 91.2.26001.Retail.en.EU.zip and did all the steps from flashandboot.bat, read
fastboot flash boot
fastboot flash system
fastboot flash recovery
next step ist to select recovery, did this an cwm comes up, sideloaded RAZRiRoot2.zip everything is pisitively quited, no errors are shown.
reboot leads to red M
wiped data/factory reset, reboot
red Logo.
I'm completely lost, please help
[\EDIT]
greetings, D.
I had same problem
Hello.
I had same problem because I did very stupid thing. I flashed homemade JB and because some apps don´t work I tried downgrade my i to ICS back....
My i stucked at the red M then I tried same thing as you and phone still booted into red M.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools, then my i booted and started to flash JB what I can see in command window. Phone was still connected to PC. After next reboot my phone has work normally with JB.
I hope to help you. Let me know.
Lucki
Hi Lucki
thanks for jumping by.
Lucki_X said:
Hello.
So I tried in windows cmd and FlashAndRoot.bat from this .zip "91.2.26001.Retail.en.EU - 4.1.2" it did nothing, but I tried to choose in fastboot mode BP Tools,
Click to expand...
Click to collapse
I tried this, and display on razr i says »Booting into BP Tools mode…«
and nothing more happens, display stays on…
and after some time pc automounts a "cd-rom drive" with some motorola files (Autorun.inf MDMSetup.xml MotorolaDeviceManagerSetup.exe MDMSetup.ini MotorolaDeviceManager_2.2.28)
but it still won't reboot…
i don't know.
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Lucki_X said:
Hi.
I had opened command window, "FlashAndRoot.bat" was running (I pressed any key) process was running (it means freezing ) and at this time I chose in fastboot booting into BP tools mode. My phone did restart and after it "FlashAndRoot.bat" process started to flash JB. After flashing my phone is going normally with JB. But some apps don´t work in JB.
Lucki
Click to expand...
Click to collapse
Doesn't work. :crying:
since i use linux i opened FlashAndRoot.bat in texteditor and executed the comands from there in terminal
only chance for the script to stop and wait is IMHO(correct-me-if-i'm-wrong) "adb wait-for-device push RAZRiRoot2.zip /sdcard/RAZRiRoot2.zip & adb reboot bootloader"
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
dogo77 said:
but that message "Booting into BP Tools mode…" just stays there forever, or does it take longer than 5minutes?
Click to expand...
Click to collapse
In my case it booted within 10 second and ran.
I am noob, I am writing just my experience. I couldn´t give you another advice, sorry.
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
okaban said:
I'm not sure how far the real installation went, but i would find Windows computer, get RSD (6.0-6.14) and try to flash ICS first. If failed due to impossibility of downgrading, then try JB. While you are able to boot to Recovery - don't loose hope yet
Click to expand...
Click to collapse
Yeah. I'm still stuck at the red logo, or indeed, at a blueish "Bootloader unlocked warnig" message since i was able to install parts of an image from sbf.droid-developers. But flashing always fails while trying to flash system.img_signed.
After reading and trying a lot these last days i think i have to install windows somewhere just to get rsd-lite to run.
sbf_flash for linux didn't work for me and fastboot gives stange warnings about "Invalid sparse file format at header magi"…
so i'll give rsd a try before i give up. As i read in posts by HSDPilot, this is the only tool that works
thanks for your help!
flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
Mud3 said:
flashed twrp the other night, didn't realize it was the wrong version... apparently sprint needs a special one.
flashed the right one. somehow have no os now.
ran ruu which failed. now it's stuck on black htc screen with exclamations in all four corners.
tried to run ruu again, just says usb error.... don't know what to do next.
Click to expand...
Click to collapse
I recently had the same issue, you should be able to fix this by following these steps, keep in mind, continuing this process will unroot your device. Thus, you will loose all of your data on your phone.
first begin by booting into bootloader, then plugging in your device via usb cable to your computer, it should now say "fastbootusb" on the device's screen.
if you don't already have the the fastbooot files required for your computer, you can download them here: ftp.qbking77.(com)/Files/OneDrivers_Fastboot.zip
after that, extract the zip file somewhere on your computer, and open the fastboot folder. Now hold down shift and click on an empty space in the folder and choose open new command window here, or something along those lines.
Now that you've done this, type fastboot oem lock and press enter, this will relock your phones bootloader.
Now, unplug your phone from usb, and reboot back into fastboot, and once again, plug the device into the computer. Just as before, your phones screen should now say fastboot usb. You can now flash this file via fastboot by following the instructions below.
androidfilehost.(com)/?fid=23329332407568410
rename the file downlaoded to firmware.zip and copy it to the folder containing your fastboot.exe file
now in the command prompt window, type in Fastboot oem rebootRUU
you should now see a black screen with the HTC logo, type Fastboot flash zip firmware.zip,
once that is complete, type fastboot reboot and once more, reboot into fastboot
you can now download this RUU file from the following link: androidfilehost.(com)/?fid=23329332407573774
extract the zip folder somewhere on your computer
boot into bootloader, and once again choose fastboot,
plug in your usb cable to your phone and computer, and the phone should once again say fastboot usb.
now open the folder you extracted and run ARUWizard.exe, this will unroot your device and return you to stock.
now, if you wish, you may re root your device.
Hope this works, if none of this makes sense, mention it. I typed this up in a bit of a rush.
also, you will have to copy and paste the links, as I have not made 10 general posts, so I can't add direct links to my post. Sorry mate.
have issue with the first step there... can't boot into bootloader, i'm stuck on the black screen with silver htc letters in the middle, exclamation on all four corners. i'm able to turn off the phone using the flashlight trick, but when i boot back up it's to that screen every time. it's stuck there from a failed ruu, just don't know how to get un stuck...
okay, some more info here. I was running hboot 1.57 ( i did relock) trying to run ruu 5_03_651_3 i'm not even positive this is the ruu i should be trying to use. now when I try to run the ruu it starts going but every time eventually fails wtih windows bringing up an error that says htc_fastboot.exe has topped working. i hit close program and the rom update utility gives me error [171]: usb connection error
edit: and now after the sixth time of that failing i am able to boot into bootloader again! weird... and it says i have an os now... still wont boot up all the way, but it's no longer blank on the bootloader screen.
second edit: after getting the usb error again and again i remembered glossing over something about flashing roms not liking usb 3.0 or something... switched to a usb 2.0 port and ruu worked perfectly. now to try and get this thing rooted again.
I am new to the forums and I need your help. The display on my LGWR went black after update even on cradle. It cannot even connect to my mobile via BT. The only thing it does is vibrate when the button is pushed and the heart sensor blinks a single time (when it turns on I guess.) as the vibration is a small one. When connected to PC running Windows 7, it is detected as Android Bootloader Interface, but ADB does not show any attached devices. Fastboot does show some alphanumerical device when (fastboot devices command is run). I have disassembled to remove the battery and tried to run it without the battery on cradle to no avail. Your help is needed as to what to do.
So it seems to hang in fastboot mode?
Try some fastboot commands then:
Code:
fastboot getvar all
fastboot reboot
Dear Ranf.
Many thanks for your reply. I ran fastboot getvar all and this is what I got. Screenshot is attached. Please guide me further.
Thanks.
Looks like you already downloaded the firmware? Right?
If so start with wiping cache and userdata:
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
I have downloaded the M1D63X boot, recovery and system (Disc Image Files) saved in my PC. They are not present in the SD card of LGWR. Shall I execute the commands or can I use fastboot and install this M1D63X on the LGWR. Thanks for your support.
The 2 format commands are basically the same as a factory reset. Please try them and then reboot.
Where did you download the file (URL please)?
Boot and recovery usually aren't trouble makers. system.img will if it's not a sparse image file.
The download like is as under Ranf:
http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Dear Ranf,
I tried to run Fastboot flash cache, and this is what the result was. Please guide.
Oh I see: you first need to unlock the bootloader with:
Code:
fastboot oem unlock
How can I dod that, as the screen is blank on the watch. I have tried it, fastboot says OKAY on my PC screen, but the watch does not reboot on its own and I have to manually restart it to get recognized in PC at Android ABD Interface. What can I do.
After running "fastboot oem unlock" you somehow need to acknowledge your decision (I'm a Sony SW3 user)
Either swipe the screen from tp left to bottom right or
press the power button.
Do you see anything on the watch screen when in fastboot mode?
Dear Ranf,
I finally able to unlock bootloader and formatted cache and userdata and then rebooted it, but the problem still exists i.e. black screen and only vibration.
Is there any way I can install stock Rom via fastboot and if so please guide me how and from which url should I download the files.
Thanks.
Screenshot of the fastboot format cache and userdata is attached for your perusal.
At 1st look the download you have is fine.
You need to flash 3 partitions:
Code:
fastboot flash boot M1D63X_boot.img
fastboot flash recovery M1D63X_recovery.img
fastboot flash system M1D63X_system.img
When you see errors at any of these steps post them here.
Thankfully all things well without any errors, but the watch is still the same, no display whatsoever. I am really devastated now. If there is anything else that can be done, please guide.
Screenshot of the processes is attached.
Sorry I must admit I'm a bit lost now. Best you ask @vt0r in the thread where you got the firmware from.
Thanks a lot Ranf. God Bless You.
You have done all steps that you can do, probably your display is broken...
I'm sorry...
When your watch starts, you see the lg logo?
Is there a way to check if the display is broken as when I disassembled the watch everything looked fine with no signs of wear or moisture. The battery also is not holding charge as when you put the watch on cradle it vibrates but off of it, vibration stops. How can I charge the battery manually.
Hey,
my watch had exactly the same problem.
I had to repair it. They had to replace the mainboard.
Luckily the warranty paid for this.
Lucas
Lucky for you that you had warranty left. For me there are two problems. First no warranty left and secondly replacement parts are not available here in Pakistan, so if there is any online store from I can manage the parts, do let me know Lucas.
I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.