Actually , my friend tried to upgrade from 5.0.2 to latest stock version.
He downloaded 133 Mb update via WiFi, and proceeded to install.
But after the phone turned off , the phone strucked on Motorola Logo, no restart, nothing.
Later he told me situation then we came to know that he is having only 232 MB left in internal memory, thus he was unable to install the update.
Even I tried to flash the ROM, but the phone isnt going in Recovery mode,
Tried many things, but none helped.
Any suggestions , to free up space and make the device usable again ?
I can't seem to understand what you have said, but from what I can tell the phone has little internal storage
The only thing I can suggest is to go into the bootloader and start flashing a new recovery. By holding the power button and volume down button will get you to the bootloader and from there it is simply Googling a tutorial.
Once you've done that, start transferring the internal files he needs to the SD card by using the recovery then wipe the phone and flash the stock or a custom rom
Related
hi there , last time i used this forum i had forced android onto a htc diamond and you guys helped me a great deal with the problems i encountered .. this time i have a problem with my milestone .
i updated to root and 2.1 with no problems a few months ago , i was going to attempt to flash froyo onto my handset in the near future but for now i just fancied clearing everything off it .
i tried to boot into recovery menu (camera and power button) and all that came up was a bootloader that looked like normal except for an extra line of :
Err:A5,69,35,00,2F
under the bootloader version .
i also tried to boot into the bootloader and flash using rsdlite after reading about that method , ( D-pad up and power ) , this bootloader doesnt have that error line . Although my device is being recognised by rsd i am unable to flash it .
The wierdest thing about all of this is that it isnt bricked completely in that it will still boot up and allow me to make calls etc , anyhelp you guys casn offer will be appreciated .
thankyou in advance
Sean
have you tried to hold 'x' on the hardware keyboard instead of camera-button to get into recovervy?
with rsdlite try to hold the up-dpad to avoid booting before flashing the vulnerable recovery is finished.
thankyou for your fast response . holding the x button did nothing phone just booted as normal .
rsd still wouldnt flash after i held up -dpad device in rsd looks like ..
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x009074
DRM Version: N / A
AP Die ID: 04200117737b0304000000000400
which i assume isnt right :S
plug the phone into rsd while booted and rsd will recognise it so you can flash as normal. this happened to me before. no biggie.
well that worked ... kinda .. it recognised the device and after several 0x7100 errors by moving the sbf file around my computer i managed to get it to flash ... only to find although it said pass it had done nothing to my phone at all and i was still unable to enter a recovery menu :S
And i can no longer access memory card :S
Ok. That is weird.
try complete uninstall and reinstall of motorola drivers and rsd. Also reseat your sd card. Redownload a fresh copy of the sbf and try again.
Sounds like something somewhere is corrupt so clean clean clean.
well ive tried about six times now and all it seems to do each time i flash it is update the bootloader and seeing as i cant get into the menu where i have the update from sd card option i cant change anything else ..
I think for now i will just be happy to use it as a phone i get to upgrade in a couple of months anyway .
Thankyou so much for your help guys .
Well one thing is clear your recovery partition is damaged/not formated properly.
But as a recovery is able to restore the bootloader, bootloader togehter with ROM is able to restore the recovery, so if one is not working phone is still not bricked at least this is how it is intended.
But with flash .sfb you got errors, that could imply bootloader also has some problems..
There is posibility that recovery part of phone is hardware damaged, so even working bootloader cant restore it, or damaged in some other way that bootloader cant repair it, maybe that were the errors for.
Than you say flashing sfb did nothing? What exactly did you mean, even phone ROM didnt get changed, or just recovery didnt? Couse maybe you can still flash sfb to change ROM. This way you will just have to stick to stock ROMs that are provided as .sfb files.
Try flashing sfb again and check if firmware is changed.
I have had a ATT captivate for almost 2 years now. It falls in the IMEI range specified by ATT. But it wasn't really a problem until very recently.
It got much worse about 3 weeks ago when the phone kept constantly rebooting. It would load the OS, begin media scanning, once that concluded, it would immediately reboot (almost every 20 seconds). Only way to stop the reboot cycle is to take out the battery. No new apps were installed, no system changes were made when this happened.
I am able to get the phone's menu which allows me to wipe and I am able to get the phone into download mode.
I have read (4) of this article regarding sleepdeath and all corresponding articles referenced.
This is what I did...
1) Performed hard reset, cleared storage. This eliminated all third party apps, returned the phone to stock (I think), but the phone is still rebooting.
2) Attempted to install a brand new rom (CM) via CWM = Problem got much worse. Still rebooting but this time, after the ATT logo appears, the screen changes to static (noise) and reboots. Followed instructions and diles from here.
3) Since the phone became useless, I hunted around to return it to stock again and used this. The phone now boots up into the OS, but now it's back to rebooting.
I repeated steps 2 and 3 just to make sure I didn't miss a step, but same problem.
I have 2 goals:
1) Get the phone working, if at all possible!
2) If that's not possible, recover the 300 pictures that are on the device.
My challenge is that since the phone keeps rebooting every 20 seconds, by the time it connects to my PC via USB as external storage, it reboots! This ofcourse is also preventing me from loading a ROM directly on to the SD card.
So if anyone can help me to do the following:
1) Point me in the right direction to how I can keep the phone in a certain mode or setting (download mode doesn't work) where I can transfer files, recover my pics, and perhaps load a custom ROM?
2) Next steps?? Am I even on the right track? Since the stock rom keeps the phone rebooting, will a custom ROM solve the problem (have not been able to get a conclusive answer on this on the threads referring to sleep death (which this is an exaggerated version of) or is the phone a lost cause?
I know I can call ATT and try to haggle a replacement (since the phone is out of warranty), the only benefit being they don't renew my contract, and I don't have to upgrade.
Any help or guidance is much appreciated.
Wow, bummer
Well i don't know if you can mount the sd card in stock recovery (never used it) but if you can't then you could flash one of the stock one click roms with cwm recovery from this thread.... http://forum.xda-developers.com/showthread.php?t=1300843
In cwm recovery there is an option to mount sd while connected to pc so you can backup your stuff.
For the reboots, could it be your power button? Mine is acting up, and often seems to cause reboots. There are threads about fixing that. Idk just a thought.
Hope that helped a bit
Sent from phone with app
Like the previous post says, maybe try a custom recovery, go to mounts and storage, and mount USB storage. While you're at it, try flashing a compatible ROM through that recovery i.e. GB rom if its a GB kernel with CWM recovery or ICS rom if its an ICS recovery.
Did you try to do a dump of SD card data with adb?
Sent from my GT-I9000 using xda premium
The static issue is because you flashed a gingerbread kernel but you don't have gingerbread bootloaders. You can fix this by flashing an AT&T stock one click with bootloaders.
Once there, you can flash corn kernel and use recovery to mount the sd card.
Or I guess you could flash a froyo kernel.. there's a number of ways to do this.
Sent from a jelly bean
So i wanted a new rom for the awesome features so after i had rooted and installed twrp custom recovery i downloaded cm12 then created a nandroid. I put my phone into recovery wiped everything except internal storage and installed cm12 and gapps. This is where my problems started, as much as i liked the new rom it wasnt connecting to my cellular network so i thought ok ill just recover my nandroid so i wiped everything except the internal storage and then started the recovery when it finished i rebooted and it goes to the warning bootloader unlocked screen and sits for about 15 seconds the goes black and repeats. My phone is a motorola moto x 2014 victara, any help is much appreciated.
Please give us more details:
1) can you access recovery? Try holding the "power" button for like 20 seconds and trying to reboot into recovery when the phone boots.
2) can you access fastboot mode on the phone? maybe you lost your custom recovery but can access the bootloader and that makes things easier.
3) what is your device number? (xt1097, xt1095, xt1092, etc)
You are going to want to factory reset. Most times coming from a customer rom to another or even back to stock you will need to do a factory reset in order to wipe out anything that may have been left over that could cause issues.
I can't boot into recovery, i have wiped all data through TWRP, and my phone won't get past the lg logo.
What Happened:
I rooted my LG-G4 H811 and installed TWRP too, yesterday, and i thought of trying out a custom rom.
I chose the CM 13 Rom, i downloaded the files.
i put them in the internal memory of the device, (since my phone has an sd card problem, a hardware one) i could've done that using OTG too but i didn't think of it that time.
I go to TWRP using my pc using adb, Because there's no direct method of doing it, not even with the volume buttons. tried them all.
Here's when i messed up
i went to wipe the phone data instead of flashing the rom and gapps first. I ticked all the boxes, and it did clean everything. including the rom files i was about to flash ( genius)
I went back to the main screen and i rebooted my phone and now it's stuck on the LG logo.
I can get into download mode by pressing the volume up button while plugging in a cable
i CANNOT get to TWRP. idk why.
Please help me :crying:
download kdz file with the firmware that you were running before on your phone get yourself into upgrade firmware mode by pressing volume up and connecting USB cable when your phone is turned off and run lgup application to upgrade the firmware and you should be ok unless you experienced bootloop phenomena on you lg4.
Hallo, yesterday my phone kinda got laggy so i thought to my self hmm why not flash a new firmware. Aftewards i said to my self, why not go even further and flash lingeageos 16 and thats when it starts going down. The phone would crash or black screen (volume and power key still work and show their UI on the screen) while the rest of the screen was black. I panicked and quickly wiped everything system,internal storage and all that via TWRP recovery. Now i face a even bigger problem. I cant flash anything onto my phone. The Flashtool requires some drives which i installed as the program instructed but with no great result. I put the device in flash mode by holding volume up key and putting the usb cable into the phone and still nothing i can do. I tried various tools to convert the FTF firmware into zip so i can flash it with TWRP that luckily still works. If i try to flash anything i get the error: 7 or bootloop/stock on loading screen. What should i do?
UPDATE: I flashed a stock rom via newflasher, so for anyone in situation like me, where they phone is a very essential part of they everyday life and everyday responsibilties. Then i recoomend this guid for you, it says everything you need to know when you are in a situation where nothing works: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/