Develop Bugs

[SOLVED]USB BRICKED+SDCARDnot Recognize+Heavy Battery Drain

To all Who are experiencing the problem I faced...Illustrated HERE..
And this is What I've Triedhttp://forum.xda-developers.com/showpost.php?p=19562122&postcount=8 to solve until got a FIX
I am writing this because I am getting PMs for help..and For the future Problems..
A Big Thanks to ckpv5... He helped me through out the days...
The Phone must be S-OFF and must got ROOT access to use this
Here is the Solution .. ..
After this you will have SD-CARD RECOGNIZED+NO BATTERY DRAIN..EVEN BETTER BATTERY BACKUP See my screen Shots
STILL GOT PROBLEM UNSOLVED ..PM me I'll TRY TO SOLVE
SOLUTION
1. First of ALL..do install ADB in you PC and on your Device(If it is bricked.. don’t worry it has adb shel on this already) see help from here http://forum.xda-developers.com/showthread.php?t=690362
Note these commands carefully ..and save these as txt in PC for further help
adb devices
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot erase cache
2. Download these(http://www.multiupload.com/5ZAPJTFXMM) and put them into C drive after UNZIPING by 7ZIP...
3. Put a recovery.img named file of AMON RA recovery.. download from here(http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-desire-v2.0.0.img)
4. Reboot your phone in BOOTLOADER ...Power on by pressing FIRST BACK BUTTON and than POWER simultaneously..
5. Open Command Prompt in PC.. for Windows7 type cmd in search at START button... for XP type run at START search..
6. Go to the directory in cmd prompt....as...
“cd C:\android sdk\tools”
7. Type
“adb devices” Let it load
“adb shel” Let it load
“fastboot erase cache”
“fastboot reboot-bootloader”
“fastbooot oem enableqxdm 0”
“fastbooot oem eraseconfig”
“fastboot erase cache”
“fastboot reboot-bootloader”
NOTE: Do remember to do all above command together and by sequence only...
8. Now it is time to flash the recovery..
9. Rename the download recovery image as “recovery”
10. Put this img file in to “C\android sdk\tools” folder
11. Open command prompt again..
12. Type
“adb devices” Let it load
“adb shel” Let it load
“fastboot erase cache”
“fastboot reboot-bootloader”
“fastboot flash recovery recovery.img”
“fastboot erase cache”
“fastboot reboot-bootloader”
13. Now remove the SD card from the phone and connect it to PC via card reader or anything by which u can easily connect..
14. Put the ROM.zip in the SD card
15. Put the SD card back in the Phone..
16. PowerOn the phone in fastboot mode by pressing VOLUMEDOWN first and than POWER simultaneously..
17. Use volume keys to go up and down..and power to select
18. Go to recovey and press power button..
19. In recovery just go to the WIPE.. and do WIPE of cache..dalvik cache..boot..system...sd-ext...Battery Stats..
20. Now reboot recovery..
21. Now after coming back to recovery in Phone choose INSTALL ZIP FROM SD CARD..
22. Simply choose the ROM.zip file...
23. Let it Flash
24. Wait
25. And
26. ENJOY!!!!!
The PROBLEM IS NO MORE..
Your phone will RECOGNIZE the SD card..
The Battery Drain (Usually having 1% under a minute) Will be Gone
You can use FAstBoot Commander or Android Flasher also to Flash Recoveries or hboots and Bootloaders
SEE SCREENSHOTS HERE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hey, Think I have the battery drain problem with runnymede AIO Rom, was it flashing AMON RA recovery that solved it? or the whole process? I don't have an SD problem.

jacksonliam said:
Hey, Think I have the battery drain problem with runnymede AIO Rom, was it flashing AMON RA recovery that solved it? or the whole process? I don't have an SD problem.
Click to expand...
Click to collapse
for the battery Drain problem.. you can do following things..
1. Wipe Battery stats
2. Install snq kernel
3. If above two doesn't work than only... try the two "oem commands" as I writtten in the procedure..
Actually every time you flash a ROm or everytime deleting and using the phone.. a extra data related to everything as cache configuration is stored in the MEMORY which acually u can not see but it eats battery...
The oem commandsd erases that thing and after this..it is like a new memory having completely blank..
BUT AFTER DOING THIS YOU WILL NOT BE ABLE TO RECOVER ANY DATA ON PHONE MEMORY IF ACCIDENTLY DELETED..
you will need to flash a new Inatall of same ROM..or whichever you want...

YES! You saved my sanity AND my phone! many many thanks!

Matty Matt said:
YES! You saved my sanity AND my phone! many many thanks!
Click to expand...
Click to collapse
.. Happy to help

I am a bit lost...
ADB cannot be used when the phone is in bootloader. So after the instruction to put the phone in to bootloader the proceeding instructions which say:
type adb devices [enter]
type adb shel [enter]
won't achieve anything. In other words, adb devices (whilst the device is in bootloader) will not find any attached devices.
adb "shel" isn't a valid command. Do you mean adb "shell" ? If so, this too isn't going to work while the device is in bootloader, adb will simply reply with "error: device not found".
So I guess what I'm trying to ask is - what is the point of those typing those two commands? In this instance, they don't serve any purpose and can be omitted?

sachin.02 said:
The oem commandsd erases that thing and after this..it is like a new memory having completely blank..
BUT AFTER DOING THIS YOU WILL NOT BE ABLE TO RECOVER ANY DATA ON PHONE MEMORY IF ACCIDENTLY DELETED..
you will need to flash a new Inatall of same ROM..or whichever you want...
Click to expand...
Click to collapse
I just can't understand what do you mean....
How am i supposed to recover any accidently deleted files if i didn't run those commands??????

dlotters said:
I am a bit lost...
ADB cannot be used when the phone is in bootloader. So after the instruction to put the phone in to bootloader the proceeding instructions which say:
type adb devices [enter]
type adb shel [enter]
won't achieve anything. In other words, adb devices (whilst the device is in bootloader) will not find any attached devices.
adb "shel" isn't a valid command. Do you mean adb "shell" ? If so, this too isn't going to work while the device is in bootloader, adb will simply reply with "error: device not found".
So I guess what I'm trying to ask is - what is the point of those typing those two commands? In this instance, they don't serve any purpose and can be omitted?
Click to expand...
Click to collapse
everything is written clearly...
these two commands repairs the USB brick also improves battery life and gives exact information about battery uses.. you will see this after flashing a ROM..
adb shel is correct command..it open the list of commands and details of phone...
Tell me what you need.. than i may solve the problem..

spitjo said:
I just can't understand what do you mean....
How am i supposed to recover any accidently deleted files if i didn't run those commands??????
Click to expand...
Click to collapse
by saying not able to recover any data is just.. if you are using any recover data application from market to recover anything which have been lost by mistake.. than you won't be able to..
BTW this Problem rarely occurs...

I' ve done this as you said in your 1st post but still Display uses more than 60% of battery use (i set brightness to minimum, all is set up to minimum and power saving)
I'm running AIO 3.0.5. CM7r2 hboot, XD2SDX, desire is s-lcd version

kciko said:
I' ve done this as you said in your 1st post but still Display uses more than 60% of battery use (i set brightness to minimum, all is set up to minimum and power saving)
I'm running AIO 3.0.5. CM7r2 hboot, XD2SDX, desire is s-lcd version
Click to expand...
Click to collapse
Calibrate tour battery... It happens that the software doesn't shows exact informations...
The problem is also with guys at cynogen too...
It is normal...
The thing is..after doing this tutorial you must be getting 16 hours battery life as normal use....
Don't worry about display...
Sent from my HTC Runnymede using Tapatalk

is it just me? having problem make adb detect my phone.

napalm.potter said:
is it just me? having problem make adb detect my phone.
Click to expand...
Click to collapse
Have you Downloaded the Tools from the link I've provided

If you have 4ext recovery boot into it and go to tools - usb unbrick. It works for me fine.
Sent from my HTC Desire using XDA App

[HOW TO][UNBRICK][KF2][RED SCREEN] You have a red screen? Try this!

How to fix your bricked KF2/otter2 with a red screen​
Preparation:
Amazon recently fixed the secruity hole, that was used to flash second bootloader and TWRP recovery.
After you flashed TWRP recovery/second bootloader and rebooted the device you will see a red screen. You can do nothing at this point withoud a pc.
So to reopen the secruity hole you have to downgrade the bootloader via fastboot.
In order to enter Fastboot mode you have to have a fastboot/factory cable. The fastboot/factory cable is not the cable that came with your Kindle Fire!!! For more information about the factory cable visit this thread: http://forum.xda-developers.com/showthread.php?t=1392693
Also you should set up all drivers and the Android SDK.
You can find the right drivers here!
Your device is not turning on? No sign of life? Then check this thread for hard bricked KF2s': http://forum.xda-developers.com/showthread.php?t=2415870
Steps:
1.)Hold the power button for 20 sec. Your device will shut down
2.)Plug in your Fastboot cable and power on the device. Your Kindle should now be in fastboot mode (a green light should blinking)
3.)Download the Bootloader file: otter2-u-boot-prod-10.2.4.bin
md5sum: 5b03a7b428325de8d360ec201a745498
4.)Copy the file in to the same directory where the fastboot.exe is located
5.)Open a CMD window, navigate to your fastboot directory and type:
##############################################################
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
##############################################################
6.)Disconnect the device and hold the power button for 20 sec again.
7.)Your device should now be working fine.
Support Me:
If I helped you please press the thanks button and rate this thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
!
Thanks to @Hashcode for providing the bootloader file.

Thanks for the info. Saw this in one of the HD forums an d assumed it would work for us (not that my device will ever see stock again lol)
Good to see some sharing here.
--
Sent from my mind to your screen.

flopower1996;42062477
4.)Copy the file in to your fastboot directory
[/QUOTE said:
This may be a dumb question, but where is the fastboot directory? I'm reading this as a directory as in filesystem, i.e Device/sys/fastboot, something like that, but from glancing around, I'm failing to find anything remotely similar. Am I missing something or just misunderstanding the instruction?
Click to expand...
Click to collapse

I believe he meant the directory in which the fastboot application is located on your PC, which is typically your Android SDK folder / platform-tools.
Sent from my Amazon Kindle Fire2 using xda premium

bjoswald said:
I believe he meant the directory in which the fastboot application is located on your PC, which is typically your Android SDK folder / platform-tools.
Sent from my Amazon Kindle Fire2 using xda premium
Click to expand...
Click to collapse
That's what I too assumed, but wasn't sure, thanks!

Thanks. I will try this when my fast boot cable is arrived . it got a red screen ad soon as I installed TWRP.
Sent from my Nexus 7 using Tapatalk 2

My kf2 is on 10.4.1 but its still rooted after i fixed the red screen the first time. used kffaid to recover it to 10.2.4. Its working as a normal kindle with root now. So if i flash twrp again. Get a red screen. And then do what the first thread says. TWRP will be installed and i can install a custom rom then ?

lost
flopower1996 said:
Amazon recently fixed the secruity hole, that was used to flash second bootloader and TWRP recovery.
After you flashed TWRP recovery and rebooted the device you will see a red screen. You can do nothing at this point withoud a pc.
So to reopen the secruity hole you have to downgrade the bootloader.
In order to enter Fastboot mode you have to have a fastboot/factory cable. Buy or build one.
Also you should set up all drivers and the Android SDK.
1.)Hold the power button for 20 sec. Your device will shut down
2.)Plug in your Fastboot cable and power on the device. Your Kindle shout now be in fastboot mode (a green light should blinking)
3.)Download the Bootloader file: otter2-u-boot-prod-10.2.4.bin
4.)Copy the file in to your fastboot directory
5.)Open a CMD window and type: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
6.)Disconnect the cable and hold the power button for 20 sec.
7.)Your device should now be working fine.
If i helped you please drop a like thank you!
Thanks to hashode for providing the bootloader file.
Click to expand...
Click to collapse
attempting to do this i have not gotten a blinking green light. the screen stays red and i can't get my computer to recognize it again to do the fastboot cmd. what else should i try or do?

snoogens79 said:
attempting to do this i have not gotten a blinking green light. the screen stays red and i can't get my computer to recognize it again to do the fastboot cmd. what else should i try or do?
Click to expand...
Click to collapse
That means you either don't have a factory cable or the factory cable you made doesn't work. BTW, a "factory cable" is not a standard USB cable.

soupmagnet said:
That means you either don't have a factory cable or the factory cable you made doesn't work. BTW, a "factory cable" is not a standard USB cable.
Click to expand...
Click to collapse
i have the cable that came with the kindle and a few other cables and it worked before this 10.4 update.

snoogens79 said:
i have the cable that came with the kindle and a few other cables and it worked before this 10.4 update.
Click to expand...
Click to collapse
Once again, a "factory cable" is not a standard USB cable. When people say "factory cable", they are referring to a factory programming cable. If you don't know what it is, you don't have one.

This has truly saved my tail. Thank you very much. You are a life saver.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta

Need some help!
I just got my fastboot cable in the mail, did all the steps up until the typing the command into the prompt. I put the .bin file into the exact folder where fastboot.exe is located and everytime I run the command, it says: "error: cannot load 'otter2-u-boot-prod-10.2.4.bin'".
Can anyone help me please?!

Sry guys, my server is atm down. I contacted my hoster so it should be up soon!
EDIT: Ok everthing is up now again

Pandasaurus12 said:
I just got my fastboot cable in the mail, did all the steps up until the typing the command into the prompt. I put the .bin file into the exact folder where fastboot.exe is located and everytime I run the command, it says: "error: cannot load 'otter2-u-boot-prod-10.2.4.bin'".
Can anyone help me please?!
Click to expand...
Click to collapse
Umm...did you check the md5 sum of that file before trying to flash it in fastboot?

Hello, sorry for the English, but I am an Italian boy.
I have red screen on my Kindle second generation.
I just got the factory and I CLABE fastboot with green light.
Unfortunately in my Windows 7 Ultimate, is recognized as the Kindle I otter2 - prod - 04.
Can you tell me where to download the drivers to be able to run my Kindle?
Thank you.

I know i will sound stupid for asking this, but i need your help. Which drivers do i set up because i am not sure if i have the right one (Device manager says Kindle fire: android adb interface) also i have a android sdk with fastboot and they on the same page but when i type it in on the cmd it says it does not recognize fastboot. Is your version of fastboot the same as mine? And how will i know when it is done or when to disconnect. thank you!
:good::highfive:

controguerra said:
Hello, sorry for the English, but I am an Italian boy.
I have red screen on my Kindle second generation.
I just got the factory and I CLABE fastboot with green light.
Unfortunately in my Windows 7 Ultimate, is recognized as the Kindle I otter2 - prod - 04.
Can you tell me where to download the drivers to be able to run my Kindle?
Thank you.
Click to expand...
Click to collapse
Davis6050 said:
I know i will sound stupid for asking this, but i need your help. Which drivers do i set up because i am not sure if i have the right one (Device manager says Kindle fire: android adb interface) also i have a android sdk with fastboot and they on the same page but when i type it in on the cmd it says it does not recognize fastboot. Is your version of fastboot the same as mine? And how will i know when it is done or when to disconnect. thank you!
:good::highfive:
Click to expand...
Click to collapse
Use this driver: http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
It's for the Kindle Fire HD 7'' but works fine for our Kindle Fire 2 as well.

flopower1996 said:
Use this driver: http://forum.xda-developers.com/attachment.php?attachmentid=1337103&d=1348009415
It's for the Kindle Fire HD 7'' but works fine for our Kindle Fire 2 as well.
Click to expand...
Click to collapse
Thank you, now my kindle in Fastboot is recognized by the PC as a Kindle fire.
I inserted the file otter2-u-boot-prod-10.2.4.bin in the directory where there is' fastboot.exe (in the platform-tools). I typed CMD and then fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin but I received an answer: fastboot-i not recognized as an internal or external command, operable program or batch file
I do not understand where I'm wrong ....

There must be a space between fastboot and -i
So the comand is:
Fastboot -i
Gesendet von meinem Optimus 2X mit Tapatalk 2

PhilZ Touch 6.59.0-CWM 6.0.5.1 Xperia T3[D5103]

PhilZ Touch 6.59.0-CWM 6.0.5.1 Xperia T3[D5103] for Unlocked Bootloader Only
Head to the Main thread for full feature list
PhilzRecovery
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something.
I have tested maximum stuff and it works fine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Additional FEATURES :
Stock based kernel with RIC disabled
init.d support
THIS RECOVERY IS FOR DEVICE D5103 WITH UNLOCKED BOOTLOADER ONLY and Firmware version 18.1.A.2.25
How to Unlock bootloader
1. Unlock Bootloader (will void warranty)
2. Download Fast-Boot package & install adb & fasstboot drivers
3. Download the kernel package (d5103_philz.zip) extract & open command prompt here & run “fastboot devices”
4. fastboot mode
5. Power off device & Hold volume up button, connect your device.
6. Use this fastboot command to flash boot.img: fastboot flash boot boot_d5103.img
7. Now reboot using this command: fastboot reboot
8. Now enjoy one of the best custom recovery on Xperia T3
Now fixed "ro.product.device" is set to "D5103"
Fixed-D5103 Download
FAQ
Code:
How to enter in recovery mode ?
Answer : As soon as you see Sony logo on your Xperia T3 ,
repeatedly press volume down(vol -) button.
Credits :
Code:
[user=5722563]@Siddhesh.K15[/user]
[user=5722563]@Santosh M[/user]
Tested by
[user=1199111]@AMIGAnTOMEK[/user]

Very thanks, il tried this in the evening

Thank you Xenon1978 for this good job

How to reboot in recovery please ?

snouki said:
How to reboot in recovery please ?
Click to expand...
Click to collapse
when on booting with sony logo, press volume down repeatly

Bro anyone have some flashable good which will root my T3 D5102

Hi
Can someone help me?
I already tryed to flash this and when reboot phone stuck at SONY logo only.
Im rooted and unlocked. My phone is D5103? What do i do wrong?
Ok i see now something that is not as screenshoot. My phone is 4.4.2 not 4.4.4 but i did not get any update? I live in SWEDEN.
BTW i will download 4.4.4 and flash manually

recovery for 5.1.1
Hello,
as we are able now to boot on 5.1.1, how to have a working recovery ?
is it possible to have only TRWP in a recovery.img in order to flash the d5103 ?

Thank you for this nice stuff!

Can't Flash.
I start flashing, and thenn an error-Message.
C:\platform-tools>fastboot flash boot boot_d5103.img
sending 'boot' (16390 KB)...
OKAY [ 0.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.702s

i do it
but cmd write
<waiting for device>

dan15 said:
Hello,
as we are able now to boot on 5.1.1, how to have a working recovery ?
is it possible to have only TRWP in a recovery.img in order to flash the d5103 ?
Click to expand...
Click to collapse
How have you booted 5.1.1?
dolor.sy said:
i do it
but cmd write
<waiting for device>
Click to expand...
Click to collapse
you need to have ADB, fastboot and drivers updated.
Try this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118

Maybe I don't understand this for well yet.. I can't find a direct link to the recovery for my experia T3

Fixing the <waiting for device> in fastboot.
dolor.sy said:
i do it
but cmd write
<waiting for device>
Click to expand...
Click to collapse
[This is for the XPERIA D5103 T3]
First of all download the USB drivers for your phone:
I cannot post here the link because XDA does not allow me to do that. Anyway it's in the attachment. In the case this file is somehow deleted due to expiration and you still need the drivers go to Google and search with xperia t3 usb drivers and you'll find a website that starts with developer.sonymobile something and its title is as follow: Xperia T3 driver – Developer World. Extract the file.
[Method 1] Go to Device Manager and select the warning triangle and select Update Driver Software. Choose the folder that you extracted and after a bit of time the computer should now detect that your phone is connected.
[Method 2] This method assumes that you have the driver already installed but the computer does not link it to your phone. Go to Device Manager and select the warning triangle and select Update Driver Software. Then click in the Browse my computer for driver software. Now click the one that says Let me pick from a list of device drivers on my computer and choose the one that says Sony so0108.
Don't forget to power off device, hold volume up button and then connect your device. Then try to execute whatever you need with the fastboot command.
Kind regards
Luis Rocha

OllerLoewe said:
Can't Flash.
I start flashing, and thenn an error-Message.
C:\platform-tools>fastboot flash boot boot_d5103.img
sending 'boot' (16390 KB)...
OKAY [ 0.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.702s
Click to expand...
Click to collapse
Have similar problem.
Did You, or anyone else, found a solution?
Bootloader unlocked, drivers installed...

I have a problem
I flashed it and everything was successfull but I can't go into recovery. can you help me?
btw. my device is rooted and has bootloader unlocked.

DownloaderXD said:
I flashed it and everything was successfull but I can't go into recovery. can you help me?
btw. my device is rooted and has bootloader unlocked.
Click to expand...
Click to collapse
had the same problem at 1st but realize (in a upper post) that to enter recovery you have to power on your phone and just after the vibration, press quickly at multiple time the vol down button (not a single long press but a lot of quick short presses).... until you see the recovery screen...

I feel so blond moment.. I coud not find a recovery in you mega list for my T3 d5103. Am I wrong or there is no one in the list between all those names at the left side.

FP4 stucks after unlock the bootloader

Hello together,
today i tried to install /e/ OS on my new FP4.
I did everything like in the official description:
> ## Unlocking the bootloader
>
> 1. Boot the device
> 2. Enable and connect Wifi
> 3. Enable Developer options
> 4. From developer options, enable OEM unlock
> * Get the unlock code from [this site](https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone-3/) and enter it
> 5. Reboot on fastboot by running the command in the PC console `adb reboot bootloader`
>
> 6.*Tip:** All the console commands are run on an adb enabled PC and in the `adb` console.
>
> 7. Ask for unlock with `fastboot flashing unlock`
> 8. Approve with <kbd>volume +</kbd> then <kbd>power</kbd>
> * The device proceed with a factory reset, and automatically reboots
At 8 i maybe made a mistake, when you are in the fastboot mode, you can choose different options, i choosed something like FFBM or something like this. Then the device restarted and since that it always shows the "blue dots" like in the beginning but nothing more happens, since hours.
I turned it off and on again, without success.
I can not load the fastboot again via ADB, because the device is not recognized.
If i try to use the volumeUP or VolumeDOWN at the startup, nothing happens and it restarts again after a few seconds.
So there is no way for me to enter the fastboot mode again.
So I have two questions to you, lovely community.
One is, can anybody help me?
Second, can somebody tell me how the different options are called in the fastboot mode, so i can google it and do more research.
THANKS a lot and sorry for my english :slight_sm

Hi,
Are you able to launch the stock rom or are u stuck on bootloop or bootloader page ?
If you can launch the stock rom, enable oem, debugging and unlock bootloader in developper options.
Then connect phone to pc with the cable and type adb devices
see if the phone is recopgnized.
Then adb reboot bootloader and do all steps of the official guide.
If you use Windows I suggest you to put all file to your adb folder, type CD /path/to/folder/
And copy paste all commands at once, this will avoid error of mishandling during fastboot operations.
If you stuck on a "waiting for phone" when you are in fastboot mode, check you driver, or test with a linux machine or see Hulk's solution here
If you stuck on a bootloop just use the key combo to enter bootloader. check on the bootloader is everything is ok (unlock) if not redone steps to unlock bootloader, then flash recovery from /e/ os folder fastboot flash recovery recovery.img
Then enter in recovery use the combo key to have the menu choice between bootloader, recovery... then enter recovery and wipe data...
Then restart the official guide of /e/ os.
You may ask on /e/ os forum too many much more Fairphone user are there and can help you (link i gave you above).

A944684 said:
Hi,
Are you able to launch the stock rom or are u stuck on bootloop or bootloader page ?
If you can launch the stock rom, enable oem, debugging and unlock bootloader in developper options.
Then connect phone to pc with the cable and type adb devices
see if the phone is recopgnized.
Then adb reboot bootloader and do all steps of the official guide.
If you use Windows I suggest you to put all file to your adb folder, type CD /path/to/folder/
And copy paste all commands at once, this will avoid error of mishandling during fastboot operations.
If you stuck on a "waiting for phone" when you are in fastboot mode, check you driver, or test with a linux machine or see Hulk's solution here
If you stuck on a bootloop just use the key combo to enter bootloader. check on the bootloader is everything is ok (unlock) if not redone steps to unlock bootloader, then flash recovery from /e/ os folder fastboot flash recovery recovery.img
Then enter in recovery use the combo key to have the menu choice between bootloader, recovery... then enter recovery and wipe data...
Then restart the official guide of /e/ os.
You may ask on /e/ os forum too many much more Fairphone user are there and can help you (link i gave you above).
Click to expand...
Click to collapse
Hello,
thanks for your reply.
I posted the same comment at the /E/ OS Forum as well.
I Can not load the stock rom, there are only this blue dots circling around for hours:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can not enter anything else, using ADB is not possible because the device is not recognized and the combination of volumeUP and power or volumeDOWN and power only restarts the device.
Do you have a FP4 and you maybe can tell me which options in the top of the fastboot menu you can choose?
Something like reboot and so on.
I will try the solution in your link in a few hours when i have more time.
Thanks a lot and BR

Bootloader menu options are "start / restart bootloader / recovery mode / power off / boot in ffbm / boot to qmmi"
I don't understand your problem if your bootloader is unlock you must have accesss to bootloader.
Are you sure you didn't relock bootloader before checking the rom is correctly installed ?
Contact /e/ support to have the precise combo key to enter bootloader. sometimes it change from phone to phone.
Does your computer works well with adb and fastboot before ? did you already flash rom ? Maybe a driver is missing or adb/fastboot is not on the last version. You may try with a linux pc to aovid those problem.

From /e/ Os website : https://doc.e.foundation/devices/FP4/install
How to Boot into bootloader mode
This section will be relevant later throughout the guide, when you need to reboot into bootloader mode.
Remove any USB-C cable and turn off your Fairphone 4
Tip: If you cannot turn your device off, remove the battery for about 5 seconds, then put it back in.
Press and hold the Volume Down button.
Insert a USB-C cable connected to the power (can either be a power outlet or a computer).
Release the Volume Down button as soon you boot into bootloader mode
For more details on how to erase the data on your FP4 refer this guide
I just try this and works great : power off the phone (if you can't just remove battery as said), press vol down and plug the usb cable
My phone has the bootloader locked and flashing locked and it works. try this

You are my hero.
I dont know how many times i read that but i was to stupid to do that correctly.
Now i tried it again and it worked well!
Thanks a lot!
Problem solved.
Just for other idiots like me, i choosed the option boot into ffbm into the bootloader menu, this was my mistake.

Question Can not boot any more

Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz

Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler

Moritz_pro said:
Hello comunity,
I installed TWRP on my Galaxy A72 to install Magisk but now I cant Boot any more. Please help my.
I hope you can help me. Moritz
Click to expand...
Click to collapse
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot

hey Idk Who can help me for SPOOF(Change by random TEXT) Any android 5.1 to Android8's BASEBRAND Version and KERNEL Version ? How I can change it ? Phone ROOTED and XPosed module ready(not Virtual xposed) ? Please find it or Create new Xposed APK or SUPERuser(ROOT right) APK for Change BASEBRAND and Kernel Version,You know it writes under settings/about phone,Everything changing exclude these.Please Helpme,or if i can do this manually from which file /system or where ?

ineedstoplaggerwatchers said:
Probably you flashed TWRP image at "fastboot boot TWRPLOL.img" this happens it . now do this,fastboot flash recovery YourTWRP.img then type fastboot reboot then Get your orginal boot.IMG from your Phone version's firmare folder by 7zip or winrar. then do fastboot flash boot boot.img then type fastboot reboot
Click to expand...
Click to collapse
I'm not sure if I am understanding all what you are saying right, so please tell me more detailed so I dont't make it worse.

turn of ur phone by holding power button 15 second then wait and be sure phone will not try reboot,then
Press and hold the Power, Volume Down and Home buttons for seconds;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the device will be the fastboot mode.
get this file then open it (Try open it by 7zip or winrar then extract it there),then click startCMD then type fastboot commands that i talked about it. but first type "fastboot devices" for be sure if it see your fastboot mode phone....... download this https://dl.twrp.me/a72q/twrp-3.6.2_11-1-a72q.img then rename it recovery(Right click on file then click properties and be sure if it says type of file: img file , so fullfile name must be recovery.img then put it into Adb&FastbootCommnderPrayForMe folder then enter this command "fastboot flash recovery recovery.img" then type fastboot reboot then remove cable quick,try power on ur phone, if it still stuck on boot then Poweroff by holding power button 15 second then 2 second later press power button by Volume Up Button together after 3 second later unpress power then continue holding volume up button,If twrp menu opened,swipe right adn go Wipe menu and ONLY chose Clear Cache , then restart phone . if still stuck then go Adb&FastbootCommnderPrayForMe folder and copy recovery.img file to same place and rename it boot(full file name must be boot.img), then go open command then type "fastboot flash boot boot.img" after enter it,Then type fastboot reboot and enter it. if still do same . then Find ur firmware's actual boot.img from your phone device model's firmare version File(firmware versions around 2GB to 10GB)'s boot.img . u can find it in internet too.Hope all works and i will be happy for u too

when I type Fastboot devices my Phone is not regionized what should I do?

Normally PC does not find your device as MTP device while you Hold POWER+home+volumeDown button(I mean fastboot mode without phone bootup).Coz it Shows device as MTP device after Phone bootedup(online).Maybe you tried install its driver as MTP by chosing manual install ? first download and install real usb driver(Adb&fastboot driver) of your samsung phone. https://developer.samsung.com/android-usb-driver then install it. then replug ur phone. Then go Device Manager of your PC,then replug your usb cable,and if you see New Device found like "unknow device or fastboot" then click them then click Properties on it, then click Update driver then click browse for Driver then click Let me pick from list then UNCHECK(unclick) "Show compatible hardware" then find your SAMSUNG ADB driver(if u cant see then click PORTS maybe it installed under Ports drivers) then click next to update it as Fastboot driver . but You can change your PC language to English for See same words in your Pc menus for I help you better coz im not German . but if already your secreen opens ? then you need go phone Settings / about phone/ Tap your phone Firm version 10 times and enable developer menu then enable USB ADB debug for install adb driver easily.if your phone screen not showing anything on screen . then you must just do fastboot mode by fastboot mode keys for install fastboot(samsung android usb driver or ADB driver another name)

When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.

Moritz_pro said:
When I am in the recovery mode then I see the MTP Window. When I am in the Download Mode I see the other window. I don't now waht the fastboot mode is.
Click to expand...
Click to collapse
Ignore what the other guy said above, fastboot is not a thing on Samsung phones. You can make it work with some patches however, but by default there is no fastboot.

ok can you tell me in detail so what do you think is the problem and wehre can I find these patches

Simon1511 said:
Did you follow all the steps on the XDA thread?
If yes, it could be possible that you additionally need to flash services disabler
Click to expand...
Click to collapse
There should be no issues if properly following the XDA thread's instructions.
Moritz_pro said:
ok can you tell me in detail so what do you think is the problem and wehre can I find these patches
Click to expand...
Click to collapse

Thank you for remaining me this option I forgot about it, but I installed a custom Rom, but I'd like to run again on the original software can I install it again. If not, it doesn't matter, but it would be better.

The Rom won't start, the start sign appears but doesn't finish loading.
[ROM][12.1][ENCRYPTION][EOL] LineageOS 19.1 for A52 4G and A72
LineageOS is a free, community built, aftermarket firmware distribution of Android 12.1/12L, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with...
forum.xda-developers.com