Database Info

[Q] is my desire s dead ?

i just wanted reset my phone
the in Phone Button "Reset ..." hasnt work
so i did it at the recovery boot
but after that, the phone dont wona start
it hangs after " HTC..."
after:
Code:
adb reload boatloader
it said:
NO Device coudnt be found
is my phone dead ?

Boot into recovery and flash a new rom?

What did you chose in the recovery?
My first guess is that you wiped your system partition. (That WOULD mean you don't have a ROM installed) Try flashing a new one.
Power down your phone
Press the volume down and the power button together until you are in the bootloader
Choose recovery (use the volume buttons to navigate and the power button to confirm)
Now flash a new ROM or restore a backup. Don't forget to flash the boot.img, if you are HTC Dev unlocked.

does yor recovery show errors like "E:Cant mount cache" ?

Thanks !
I realy wiped the phone, and there was no rom
c:\Android>fastboot flash boot boot.img
sending 'boot' (5624 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
???

[Q] N5 Stuck on welcome screen - only 128mb internal storage

hi all.
have had a search through the internet but not found anyone with the exact same problem
woke up to find my N5 on the welcome screen asking me to choose language, continued through set up to see there is only 128mb storage and no phone or 3g signal. whenever i try to start an app it fails.
tried to factory reset from the options but the final button just does not respond
loaded up bootloader to do a full wipe/ recovery but have the usual failed to mount partition
unlocked bootloader to flash facotry image but also not working...bootloader reverts to locked state automaticly
cannot see anyway out of this one...the phone is stock and never been rooted
hardware failure?
thanks in advance

Definitely sounds like a hardware failure I would send it back
sent from my T-Mobile LG-VS980

Try and fastboot flash everything via the backup bootkoader. Thats volume up + volume down + power.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Try and fastboot flash everything via the backup bootkoader. Thats volume up + volume down + power.
Click to expand...
Click to collapse
i have done that already, it just tells me failed to mount partition and relocks the bootloader after, none of the recovery options do anything and it wont let me flash the stock 4.4.4 image

samsamba said:
i have done that already, it just tells me failed to mount partition and relocks the bootloader after, none of the recovery options do anything and it wont let me flash the stock 4.4.4 image
Click to expand...
Click to collapse
So to be clear you have tried this on both the primary AND backup bootloader?
If so, yeah its screwed.
Sent from my Nexus 5 using Tapatalk

rootSU said:
So to be clear you have tried this on both the primary AND backup bootloader?
Click to expand...
Click to collapse
thanks for the reply,methods i have tried so far are:
factory reset from settings menu in android - button not responding
factory reset from bootloader menu (power + volume on start up) - failed to mount partition
unlocking the bootloader and flashing the stock image from google - failed to mount partition
am i missing something?

samsamba said:
thanks for the reply,methods i have tried so far are:
factory reset from settings menu in android - button not responding
factory reset from bootloader menu (power + volume on start up) - failed to mount partition
unlocking the bootloader and flashing the stock image from google - failed to mount partition
am i missing something?
Click to expand...
Click to collapse
There are 2 bootloaders. There is a primary one (volume down + power) and a backup one (volume up AND volume down + power).
Please boot into the alternative bootloader and repeat your last 2 steps.
Sent from my Nexus 5 using Tapatalk

rootSU said:
There are 2 bootloaders. There is a primary one (volume down + power) and a backup one (volume up AND volume down + power).
Please boot into the alternative bootloader and repeat your last 2 steps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
have loaded into alternative bootloader as suggested, results are as follows
E:failed to mount /cache (invalid arguement)
E:cant mount /cache/recovery/log
E:cant open /cache/recovery/log
after unlocking the bootloader and attempting to flash i have this from the command prompt window and the bootloader goes back to being locked. i am using the method from this guide to unlock the bootloader: http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
< waiting for device >
sending 'bootloader' (2508 KB)...
OKAY [ 0.196s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.396s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45409 KB)...
OKAY [ 1.790s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.876s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s

Sounds like your NAND is fried. Send it for repair
Sent from my Nexus 5 using Tapatalk

Error during 702 to 703, corrupted system, unable bootloader, bricked? Am i screwed?

Hi All,
I was following this guide: http://forum.xda-developers.com/mediapad-x2/general/how-to-flash-rom-x2-gem-703l-gem-702l-t3228915
Downloaded the document and following the step.
Here's what i had:
- bootloader unlocked
- twrp installed
- flashed x2_Kang_b015
Where it failed:
- fastboot flash system system.img
- had this:
Code:
c:\Users\user\Downloads\GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (447016 KB)...
FAILED (command write failed (Too many links))
finished. total time: 1.044s
c:\Users\user\Downloads\GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.015s
c:\Users\user\Downloads\GEM-703L_EMUI3.0.5_Android5.0_V100R001C233B015>fastboot devices
???????????? fastboot
Where i am now:
- twrp gone, fastboot flash recovery recovery.img worked, so twrp gone
- Power + Vol Down, unable to get me to bootloader mode (WTF)
- Power + Vol Up, simple recovery with WIPE option only
- Power + Vol Up + Vol Down, EMUI updater
What i tried:
- placed original B015 GEM-703L update.app in "dload", got *Version check failed*
Is there anything i can do? Any suggestion would be great?
I can't even power off the device now, it hangs at load screen, and holding power, will restart the device.
Thanks and Regards,
Kevin

It seems like i managed to save my own a**. Downloaded the stock B003 for GEM 702L and did Power + Vol Up + Vol Down. It works.
Seems like theres always a way to recover from a screw up, don't give up guys, there's always a way, or maybe i just got lucky =P
Thanks

If you get this error on flashing system, your adb version it's not up to date.
Install Huawei hisuite and use a different USB port.
If you bought your device with message 'bootloader unlocked' then forget this: it might be a fake unlock message. You must unlock bootloader yourself, if you still are not able to flash system.
First flash the 4 files for 015
and then install universal cust b112
and then install b015
My device: 701->703 Kang VIP B209

Problem with oopof1 phone

Problem with oopof1 phone
I have made Rom for the wrong phone oppof1f and the phone has stopped on this logo
I do not move I have stood on this and I can not enter the recovery permanently, what is the solution?
And sorry if the subject is not in place​

Picture of the problem
store6.up-00.com/2017-05/149603505807811.png

So it looks like its trying to install the rom.
if you cant enter recovery.
extract the recovery.img for the stock rom in the link below
boot into fastboot (power and volume up) then,
fastboot flash recovery recovery.img
if you can enter recovery do this.
Turn off the phone and put this rom for the f1f on the micro sd card.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46153
then hold the power button and volume down and it should come up with a langauge to pick.
then press install from sd card.
select the rom.
if it fails keep trying. u can also try wiping data and cache

Jamie_oppo said:
So it looks like its trying to install the rom.
if you cant enter recovery.
extract the recovery.img for the stock rom in the link below
boot into fastboot (power and volume up) then,
fastboot flash recovery recovery.img
if you can enter recovery do this.
Turn off the phone and put this rom for the f1f on the micro sd card.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=46153
then hold the power button and volume down and it should come up with a langauge to pick.
then press install from sd card.
select the rom.
if it fails keep trying. u can also try wiping data and cache
Click to expand...
Click to collapse
When you press the power button and the volume down, this message appears
Store6.up-00.com/2017-05/149603505807811.png
And unable to enter into recovery
Unable to access your phone

up up up up

If fastboot mode is working, you can try to boot another recovery (twrp, with fastboot boot twrp.img) and wipe the cache partition (that might have update information on it).
If it's not enough, I'd try to wipe data. But before that, try to backup things while TWRP is working.

tarek.eid said:
up up up up
Click to expand...
Click to collapse
Can you boot unto fast boot using power and volume up?

kdd998 said:
If fastboot mode is working, you can try to boot another recovery (twrp, with fastboot boot twrp.img) and wipe the cache partition (that might have update information on it).
If it's not enough, I'd try to wipe data. But before that, try to backup things while TWRP is working.
Click to expand...
Click to collapse
Yes FastBoot mode works
And when working twrp.img recovery
Of this site
Https://twrp.me/devices/oppof1.html
But there is a problem with the message
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
Can you explain
Clear the cache section

Jamie_oppo said:
Can you boot unto fast boot using power and volume up?
Click to expand...
Click to collapse
Yes I know how to login to FastBoot mode
But this message appears after the steps are executed
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s

tarek.eid said:
Yes I know how to login to FastBoot mode
But this message appears after the steps are executed
Target reported max download size of 268435456 bytes
Sending 'recovery' (25858 KB) ...
OKAY [1.142s]
Writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
Finished. Total time: 1.157s
Click to expand...
Click to collapse
Type fastboot oem unlock then repeat

Jamie_oppo said:
Type fastboot oem unlock then repeat
Click to expand...
Click to collapse
This message has not been opened
FAILED (remote: oem unlock is not allowed)
Finished. Total time: 0.009s

tarek.eid said:
This message has not been opened
FAILED (remote: oem unlock is not allowed)
Finished. Total time: 0.009s
Click to expand...
Click to collapse
Looks like you have a locked bootloader with unlocking disabled via developer options. With bootloader locked,no recovery and cant boot to rom to enable bootloader unlocking you only real option is to follow instuctions in this post to flash back to original stock firmware using low level QDloader to flash entire phone in factory mode.
PS This is only for f1f not f1s. You do have a f1f, right?

MiniBlu said:
Looks like you have a locked bootloader with unlocking disabled via developer options. With bootloader locked,no recovery and cant boot to rom to enable bootloader unlocking you only real option is to follow instuctions in this post to flash back to original stock firmware using low level QDloader to flash entire phone in factory mode.
PS This is only for f1f not f1s. You do have a f1f, right?
Click to expand...
Click to collapse
Yes my phone is f1f
I will carry
Https://drive.google.com/file/d/0B3vGskcdFbBcVThPS3FIb2dkdGs/view?usp=drivesdk
I will try
Take you

There is a problem with these definitions
Qualcomm HS-USB QDLoader 9008 (COM5
A triangle sign appears that needs to be defined
Does this affect
Even if it has a possible impact on its definition

tarek.eid said:
There is a problem with these definitions
Qualcomm HS-USB QDLoader 9008 (COM5
A triangle sign appears that needs to be defined
Does this affect
Even if it has a possible impact on its definition
Click to expand...
Click to collapse
You need to follow the instruction in the post I linked and "Install the QDLoader driver found in the DRIVER directory of the extracted archive". If its using the correct drivers the triangle should not be there. (you mean in contol panel?)
If you have problems PM the quy who posted the link. He said he would help.

Sony Xperia XZ1 Compact stucked after booting TWRP

Hey guys.
I'm having trouble to come forward booting my device with TWRP on my Sony Xperia XZ1 Compact (G8441) using a MacOSX.
Additional info to the phone:
version-baseband:1307-7511_47.2.A.11.228
version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
Steps I did:
Unlocking the bootloader (worked)
Flashing with TWRP from Androidfilehost (here) with:
Code:
./fastboot flash recovery TWRP.img
I've used Android 9.0 twrp-3.3.1-0-lilac-pie-5.img as TWRP.img
It gives me:
Code:
./fastboot flash recovery TWRP.imgSending 'recovery' (34548 KB) OKAY [ 0.750s]
Writing 'recovery' OKAY [ 0.262s]
Finished. Total time: 1.016s
Booting with TWRP:
Code:
./fastboot boot TWRP.img
Sending 'boot.img' (34548 KB) OKAY [ 0.749s]
Booting OKAY [ 5.742s]
After step #3 the phone gets stuck on the Splash screen showing "SONY" (blue LED light on)
Rebooting into normal mode using Volume-Up + Power also gives me a similar outcome leaving the phone stuck on the "XPERIA" screen.
I've read somewhere in this forum that a possible solution could be to format the cache and user data which gives me:
Code:
./fastboot format cache
/Applications/Android/./mke2fs failed with status 1
fastboot: error: Cannot generate image for cache
And a similar one for user data.
Does anyone of you have a clue what I did wrong and what I need to do next to solve it? Every constructive comment is much appreciated.
Best
EDIT:
I could get it running and were able to install lineage-17.1-20201217-UNOFFICIAL-v1.7-lilac from here (androidfilehost.com - modpunk).
It was working to get into TWRP through unplugging the USB cable. Restarting the phone and directly after it restarts pressing volume up and plugging in the USB again.

Wondering why you try to boot into TWRP when it has already been successfully installed?
Code:
fastboot boot <TWRP.IMG>
is used if TWRP isn't already installed yet.
You should run
Code:
adb devices
adb reboot recovery
instead.