hey, i'll be brief...
today (maybe yesterday for you.. nevermind) i was rooting my nexus 4 after bootloader unlocking... during the procedure my computer has freezed, so i rebooted it and after few minutes i tried again and this time i have correctly rooted my phone... then i flashed a custom rom and finally few hours ago i went into fastboot mode, erased all the imgs (userdata, boot, system, etc... don't ask me why i've done that, i'm very stupid...) and flashed the 4.3 factory image on the google site... and just now i've realized that my internal storage has switched from 12,95 GB to 5,6 GB...... I purchased the 16 gb version, but now i litterally have a 8 gb one... so tell me, is it a software problem? is it easily solvable or I have to ship the phone in warranty? please, answer me asap, i'm hopeless at the moment!!!
p.s. 5,9 GB is the TOTAL ammount that the os takes over, not the available..
I've had the same experience once,
Go to official android page, download the JDQ39 version and reflash it. Then optional for the cwm installation and others.
I had it a couple of times, so chillax.
yeah, i was already trying it... my router is very low-power now, so it is taking a lot.. omg this reassure me! ahahahahhaa i was going out of mind, thanks bro!
Related
Hey XDA, just a long time stalker who has finally given up trying to find his solution on already posted items (I think 10 hours of trail and error means I'm not gonna catch what I'm failing to see...)
When I first got my galaxy s4 I downloaded KangaBean and it was on 4.2.2 I believe. Today I decided I should upgrade to 4.4.2 since I've only been hearing good things about it, and I wanted the slight updates that came with it.
Well, I have a AT&T s4, sgh-i337 that was on CWM 6 when I tried updating to another ROM, the first one I tried was GOOGLE EDITION 4.4.2 BY DANVDH. Did a wipe, cache, dalvik, format system, flashed it, flashed loki doki, said no to re-root/root fix prompt that followed, then I came to the yellow triangle, I thought that was odd, believed I missed something.
So, I downloaded TWRP 2.5.0.2 like the thread suggested, tried again, no luck. Then I tried Unoffical Carbon KitKat, which just caused the "Samsung Custom" logo to stay on indefinitely (I let it sit for 40 minutes before giving up.) After 2 failed ROMs, I tried KangaKat, updated version of KangaBean, so it should be just dandy right? Narp, same luck. This one boots, then reboots into recovery.
At this point I considered myself to be stupid in some way so obvious that I would die before I noticed it. So, then I just flashed the stock firmware thats like 2.5 gb through odin, re-rooted and installed CWM 6.0.4.4 LOKI'd and tried to flash KangaKat, being confident it would work this time, again I got boot to the logo and then reboot into recovery.
At this point I attempted the other 2 ROMs again, multiple times.
After some sobbing, I re-did the stock firmware, tried again, failed again.
My sadness turned into rage, I just destroyed one of my micro sd to usb-s because it was being annoying and I was annoyed, I took a picture and got over it.
I tried a 3rd time with the re-flashing stock firmware and tried with twrp again, no cigar.
Now, after MANY hours and MANY false hopes... I shall be using my blackberry and hoping to return to android soon, if somebody can help me figure out what I'm missing. Many thanks ahead!
Did you do lokidoki after?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Did you doa hard reboot clear the cache and davlik after it got stuck on the lock screen ? It seems odd that it would just not boot up at all. I was about to wonder if maybe it was the CM kernel bug that will keep it from booting past the initial screen but you tried aGE rom so...
So, I flashed back to stock to take the OTA using NRT, the process went off without a hitch. I realized once I got most of my stuff setup that I only have 6gb instead of the 13 or so I had previously. to be clear, I have the 16 gb tablet but now its showing 6 gb total. I wanted to see if anyone knows how to resize or re partition my device. Or if there's a way to roll back, I went back to my old custom rom and it still doesn't show the full space.
This has happened to me several times while flashing factory images. The only fix I know of is to do a factory data reset.
Bootloop following contact with water? Or recent update?
Hello,
Here is my story : end of last wwek, my phone fall in a small amount of water (1cm) on the top (jack side). I wiped it very fast and use it for the next 30 min, everything is good. and then i let it 2 hours (charging or not i don't remember, i don't know if it can matter). After that i find it bootlooping was there an update, end of last week? Anyway i let it in that state at least 30 min and even more and then tried to restart it not better. I also tried a wipe cache and after that a factory reset, nothing...
Yersterday back to home, i tried to flash the 5.0.1 factory image ( didn't want to take the 5.1, because i feared a possible bad update on the image maybe) nothing better, even worst because after after some time of bootlooping, i've got the red light flashing :/
Same goes for the 4.4 flash but small miracle, it's working 4.2.2... During all those tries, i did some oem lock and unlock before and after each flash.
So my phone is working with the first version of android available, which is not the best.... I also tried the OTA update to the 4.3 and i also got stuck to a bootloop
So after that long story (sorry), I defer to your expertise because i don't know what else to do.
Please help :/
I just installed the lastest version of cyanogen and it's working well...
Still no idea whats happening there?
Seems to be a real big question i ask you there, but i continue my thinking on my side.
I dont like the idea, but it light be a hardware problem... Maybe a failing memory slot, or an unused component until then.
So it brings me 2 questions : how and where could i find logs after a failed update?
And how could i efficiently test my hardware CPU, RAM, as we can do on a computer?
Thanks in advance, any idea, help, joke are welcome
Hello, I just want to share with you strangest problem I ever had with Android device.
I have old Nexus 7 nakasi with stock 5.1 rooted. Past few weeks tablet was unused, charging from USB port in Sony Bravia TV.
Yesterday I've tried to use again, but I realized that it was turned off. After switching on and connect to wifi, he rebooted after a few minutes.
I found that without wifi lasts about 10 minutes before it restarts.
Strangest thing:
After each reboot, he booted into absolutely identical state. No matter that I uninstalled application, app was back, deleted files was back. But also all the changes of the past were gone.
I tried boot to save mode – after while he rebooted too
I tried leave tabled few hours in TWRP recovery - he has not rebooted, so he’s not unstable
I tried delete cache – no change
So I tried factory restore – after reboot he booted without change, hmm…
So I download nexus image a start “flash-all.bat”. No error, but after reboot. Surprise – no change – my old rooted system.
Via TWRP recovery I tried format/wipe everything, no change I even change filesystem from ext4 to F2FS – after reboot data are back
If I make backup in TWRK into internal memory (boot for instance), backup completes ok, but after reboot backup is gone.
If I start big backup (3gb data) into internal memory, backup fail after few minutes. But backup via otg to usb flash disk completes OK. So I can create full system+data backup.
It’s like flash memory is damaged and allow write only a small amount of data. And after reboot is restored to identical state. That would explain why Android reboots after a while, and recovery not.
What do you think? Can it be anything else than damaged flash memory? And if so, is there anything i could try, or "Zed is dead"
And finally it’s possible that Sony TV cause this? Thank you and sorry for my bad English.
Exact same thing happened to me, Bought a new motherboard for around $20 online... ebay I think and fixed it good as new... plus i upgraded to the 32GB model! replacement was pretty easy, I have never done anything like this before but didn't encounter any problems. I think its due to the flash memory dying, and becoming read only. I even formatted the whole drive from my computer and when I rebooted, Exact same old system. Here's the iFixit guide I followed: https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
Happened to me too, and I also just replaced the motherboard. I have a feeling the equivalent of the boot sector fails, but on a ssd that puts the drive in read only mode. I seem to recall a fix using a non standard partitioning tool whose name escapes me, but our normal flash and recovery tools won't work. I wanted 32 meg upgrade anyway so decided it was best to replace rather than repair.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 12:48 AM ---------- Previous post was at 12:43 AM ----------
Ah, tool is called NVFlash, but been years since I used it so can't help with instructions.
Sent from my Nexus 7 using Tapatalk
Thank you all for reply. Unfortunately cheapest 32GB motherboards on ebay cost 45$. But but I'm afraid that 32 gigabytes version will not be much faster. Nexus 7 has a terribly slow storage. Recently i bought Onda tablet V891, for 140$ and it's and it's perfectly fast device
When I think about it, the problem was caused by Titanium backup backuping every day. Finally, a flash memory did not last.
Thank for NVFlash I'll try to write here how it went
I just bought a nexus 7 / 32g with a broken screen for about 25$. Used, but worked. And now have a few extra parts...
Sent from my Nexus 7 using Tapatalk
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
sevenvoldizm said:
Good day everyone, i am going to report my delicate and infuriating problem that has been haunting my head for two months
I'll describe my problem in extreme detail, hoping you guys able to identify this disaster.
My android phone is Lenovo A6000 Plus, i've bought it 2 years ago and it's running on latest Lollipop version 5.1.1 I never alter the system files, since i only use my phone for games and communications, and i'm not really into tinkering android's software. so i use my phone like a normal person, do the updates when the settings asked me, update the apps, etc. and this phone running smoothly in my service. i wanted to ask both WISDOM and HELP in this thread.
1. The Bootloop disaster symptoms started on april 2018, when the phone boot SLOWLY AS HELL, seriously.. it took about 1-2 hours to boot, and it also shows the (ANDROID IS UPGRADING 0/132 apps) like wtf? , i haven't update or install any new android apps before this symptom happened. So i leave my phone plugged in and wait it to complete the upgrade; then it worked normally as it should. Unfortunately, it happened EVERYTIME i turn my phone on, EVERY SINGLE TIME.. T_T. so i struggled to avoid my phone from running out from battery as i can. This symptom happened for 3 weeks and it got from bad to worse. I wonder what kind of problem is this?
2. The worse part came when my phone is running at high RAM usage, let's say, i game on my phone alot in my spare time, using the ram up to 1800mb everytime i play game or open chrome browser (Lenovo A6000 plus have 2GB ram). When i close/task manager the apps, my phone launcher wont appear normally as it should (long pressing bottom left button) and it FORCED me to restart the phone and suffer the 1-2 hour LONG BOOT. That's unusual, i cleaned my phone regularly (using cleanmaster) and preserve both of my internal and external storage with 3-4GB free space. I wonder what kind of curse is this?
3. So the bootloop disaster finally got me this May when i turn my phone off and tried to reboot. And... no Android is upgrading 0/132 showed up, i waited for 4 hours and reboot my phone again and again and again. And its finally STRANDED on BOOTLOOP :crying:
Im on panic mode when problem 3 happened, then i searched the almighty Google for help, and found that i can backup my data with TWRP recovery, so i do as it said, followed the guides and BACKED UP all of my data.
For once i felt relieved my data is now saved. Now onto the main problem.
I've had enough of this problem so i format the phone into factory reset, wipe the Dalvik ****s, cache, system and data. All of it. thus, making my phone virgin again.
4. Now im trying to resurrect my phone, and tried my effort by downloading Stock Lollipop 5.1.1 OS again along with its prerequisites. I tried to zip-install it using TWRP but it said that "has not switched carriers and cannot be upgraded" i scratched my head and searched almighty Google again then found that i need to do ####6430### thingy before doing that. umm.. so my phone domain need to be changed, how can i do that with a phone who can't boot? (I'm from Singapore btw). What did i do wrong?? did my phone just turned into useless BRICK? but i've read that bricked phone can't even start the recovery, yet my phone still able to start either with Lollipop stock recovery or TWRP (if i adb fastboot it with adb tools from .cmd), so it's not totally fuc.. uh., BRICKED and i got the chance to fix it.
TL;DR
So, Guys.. i desperately need help. i'm a peon both in work and college, and a dead phone will not make a great company for a person like me.
I searched for enlightments and breakthroughs but always ended up failed resurrecting my phone, can you guys PLEASE :crying: tell/give me a SAFE and WORKING walkthrough to re-install my Lenovo A6000 Plus with Lollipop 5.1.1? And does it running a custom OS like those Cynadrogen thingy is good and worthy enough to speed up my phone? is the chances of getting bricked is unavoidable when running custom OS? I thought its going to be easy like reinstalling Windows, but i was wrong.
FYI, my phone now is UNROOTED and running on TWRP 3.0.2 and i can easily revert it back to Lollipop stock recovery if needed (does it considered rooting if i install custom recovery?) I also need a valid info if my phone would never turn like this again if i resurrect it again.
PLEASE HELP ME PEOPLE
THANK YOU.. ! :highfive:
Click to expand...
Click to collapse
When 5.1.1 update arrived?
Okay lets get to the point. Just don't panic. You have the stock rom file, extract a file named 'system.zip'. Now go to TWRP, perform advance wipe (wipe dalvik, data, system and cache partitions) and flash that file from TWRP. You'll be on stock rom with a fresh new experience.
---------- Post added at 10:38 PM ---------- Previous post was at 10:33 PM ----------
Custom ROMs are amazing and far better than the stock lenovo rom. Believe me, no one here is using that crap stock rom. You just need some instructions to flash and your phone will get a new life. We are here to assist you.