Related
Ok im not usually this stupid but for some unknown reason my brain went on holiday this morning and I deleted the framework-res.apk from the system/framework folder on the phone when performing a mod. As expected now my nice new phone is stuck in the animation screen and I dont know how to get the file back on the phone.
* The bootloader is unlocked and I have rooted it.
* Adb is setup on my pc but if I boot the phone into the fastboot screen I get no device found when I type adb devices.
* I have tryed the same thing in the Recovery screen.
* Fastboot works and I can lock and unlock the bootloader.
I have installed the samsung usb driver pack which and used the samsung android adb interface as my Adb Interface driver.
I need to somehow push the framework-res.apk (which I have on my pc) back to the /system/framework folder on my phone so it will boot back up or im going to have to send it back ;[
I know there is a dump in the Development forum so I dont know if I can use part of that to flash the system image using fastboot?
Im not too big to ask for help when I need it and thisd isnt my speciality. I have been googling this all night to no avail so now I pass it over to you.
Im not going to bed I hope someone will be able to help when I wake up or its off to phones4u with my broken phone lol.
Mark.
EDIT: Fix can be found *HERE*
As long as that dump is correct, and it seems to be judging from the other replies in the thread, you should be able to simply flash it using 'fastboot flash system system.img' (or whatever he called the file).
If you don't want to do that for some reason you could check if ADB is enabled in recovery as it is in custom roms. If so, you could mount the system partition (mount /system) and then push it from there. Might not be enabled in stock recovery though.
EDIT: I saw you mention adb devices. That only works when adbd is running which it naturally isn't in fastboot mode as that is a much lower level than that. The command 'fastboot devices' exists though.
I'm not familiar with fastboot at all but have you tried adb kill-server and then adb devices?
I had an issue before with finding a device and it fixed it
altimax98 said:
I'm not familiar with fastboot at all but have you tried adb kill-server and then adb devices?
I had an issue before with finding a device and it fixed it
Click to expand...
Click to collapse
ADB is handled by the daemon adbd which starts during boot and is an Android/linux binary. The bootloader most certainly isn't something that high-level though so it makes no sense to try to interface with it using ADB in that mode.
Recovery is a very slimmed down Android though so it would work if it's enabled in stock recovery.
blunden said:
As long as that dump is correct, and it seems to be judging from the other replies in the thread, you should be able to simply flash it using 'fastboot flash system system.img' (or whatever he called the file).
Click to expand...
Click to collapse
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
mskip said:
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
Click to expand...
Click to collapse
http://www.hard-reset.com/samsung-galaxy-nexus-hard-reset.html
?
winwiz said:
http://www.hard-reset.com/samsung-galaxy-nexus-hard-reset.html
?
Click to expand...
Click to collapse
Doesnt do anything I have tryed going through the recovery selection in the fastboot screen. Also that page is inacurate as you need to hold Volume Up + Volume Down while powering up. Volume Up + Power just boots up as normal..
My only bet before taking it back is via fastboot which works fine. I still have the bootloader unlocked but that system image wouldnt flash .
Mark.
Well theoretically you can try to use fastboot and
fastboot flash system system.img
All you need to do is to make system.img
mskip said:
I just tryed to flash the system image using fastboot flash system gnsys.img from *THIS* thread and got the following:
sending 'system' (669696 KB)... FAILED (remote: Exceed Buffer Size (0x16400000))
Kinda getting lost here. Any experts around?
Mark.
Click to expand...
Click to collapse
The system image is probably not a sparse image -- that is, the image exceeds the RAM size for fastboot. Same issue with the Nexus S.
mike1986. said:
Well theoretically you can try to use fastboot and
fastboot flash system system.img
All you need to do is to make system.img
Click to expand...
Click to collapse
How do I make a system image from the system dump *HERE*?
Mark.
ydaraishy said:
The system image is probably not a sparse image -- that is, the image exceeds the RAM size for fastboot. Same issue with the Nexus S.
Click to expand...
Click to collapse
Yes thats exactly what I read about in the Nexus S thread when I was researching this. Is there any way to make it smaller so its flashable?
Mark.
Post here your framework-res.apk
mike1986. said:
Post here your framework-res.apk
Click to expand...
Click to collapse
Here you go
Mark.
In the meantime - have you tried this? http://forum.xda-developers.com/showthread.php?t=1193915
It has "Flash multiple files in one click by using custom folders and tags."
Worth to give a shot. Let me know if it works.
Ok I think I know how to solve your problem What is your stock ROM? ITL41D?
mike1986. said:
Ok I think I know how to solve your problem What is your stock ROM? ITL41D?
Click to expand...
Click to collapse
Yes its the retail build which is ITL41D
Mark.
So here is what I have done:
I included framework-res.apk in ramdisk inside boot.img. This way it should fix your problem but now keep in mind that you can't replace framework-res.apk because it will be reloaded from ramdisk on every boot. So if your device will boot with boot.img from me then adb push framework-res.apk /system/framework and reboot in fastboot and fastboot flash boot boot.img BUT stock boot.img this time so it wont replace your framework-res.apk. So:
1. Modified ITL41D boot.img - flash in fastboot using fastboot flash boot boot_mod.img
2. If system boots (I'm not sure if will) then adb push framework-res.apk /system/framework
3. Boot in fastboot and flash Stock ITL41D boot.img - flash in fastboot using fastboot flash boot boot_stock.img
mike1986. said:
So here is what I have done:
I included framework-res.apk in ramdisk inside boot.img. This way it should fix your problem but now keep in mind that you can't replace framework-res.apk because it will be reloaded from ramdisk on every boot. So if your device will boot with boot.img from me then adb push framework-res.apk /system/framework and reboot in fastboot and fastboot flash boot boot.img BUT stock boot.img this time so it wont replace your framework-res.apk. So:
1. Modified ITL41D boot.img - flash in fastboot using fastboot flash boot boot_mod.img
2. If system boots (I'm not sure if will) then adb push framework-res.apk /system/framework
3. Boot in fastboot and flash Stock ITL41D boot.img - flash in fastboot using fastboot flash boot boot_stock.img
Click to expand...
Click to collapse
WOW. nice if it works!
Doesnt work im afraid..
I get the following information in the command screen:
fastboot flash boot boot_mod.img (my input)
> sending 'boot' (8752 KB)... OKAY
> writing 'boot'... FAILED (remote: Write Fail)
On the phone is displays:
FASTBOOT STATUS - FAILWrite Fail
Mark.
mskip said:
Doesnt work im afraid..
I get the following information in the command screen:
fastboot flash boot boot_mod.img (my input)
> sending 'boot' (8752 KB)... OKAY
> writing 'boot'... FAILED (remote: Write Fail)
On the phone is displays:
FASTBOOT STATUS - FAILWrite Fail
Mark.
Click to expand...
Click to collapse
rename it to boot.img and try again.
Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?
How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?
I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?
the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?
BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.
BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.
IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.
Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Airwolf79 said:
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Click to expand...
Click to collapse
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Also having that issue on the NA varient. So f-ing annoying.
djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Go into recovery and factory reset. That happen to me once when flashing in fastboot from bootloader.
djsubterrain said:
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
Click to expand...
Click to collapse
Yeah, I know. I'm on a Mac, so, same boat. Yes, I flashed with "fastboot flash boot boot.img", specifically renaming the patched img to boot.img. This used to be the standard way of doing it, although I realize it's safer to boot the img.
My mistake, you are trying to get root, correct?
TheGhost1951 said:
My mistake, you are trying to get root, correct?
Click to expand...
Click to collapse
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
TheGhost1951 said:
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
Click to expand...
Click to collapse
Being on a MAC, I really don't have a clue bud..
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
djsubterrain said:
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
Click to expand...
Click to collapse
Did root work?
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
You did actually read my post, right?
mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
I'm still getting a bootloop
LuckyTheCoder said:
I'm still getting a bootloop
Click to expand...
Click to collapse
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
mustangtim49 said:
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
Click to expand...
Click to collapse
I did, yes. MSN tool? Like fully reset?
LuckyTheCoder said:
I did, yes. MSN tool? Like fully reset?
Click to expand...
Click to collapse
It will!
TheGhost1951 said:
It will!
Click to expand...
Click to collapse
:/
LuckyTheCoder said:
:/
Click to expand...
Click to collapse
I can't count the number of times I have started from scratch just from trying different things and crashing!
TheGhost1951 said:
I can't count the number of times I have started from scratch just from trying different things and crashing!
Click to expand...
Click to collapse
How in the world am I supposed to back it up?
I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.
whats wrong with fastboot?
Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed
more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom
Partition table doesn't exist?? you must have done something stupid...
aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow
Did you try flash by mi flash the rom that you used to downgrade?
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it
pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.
pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.