Database Users

Stuck in BootLoop and Factory Wiping doesn't actually wipe anything

Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.

same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.

I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?

eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.

Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911

[Q] Jiayu S3 semi-hard brick (NOT BY FLASHING), help needed

Hi all,
Yesterday my Jiayu S3 crashed and rebooted, after setting an alarm clock and using the Spotify app. However, it did not reboot into the OS as usual. It did not even show the Jiayu logo, but the phone vibrated (sign that it's booting), screen turned on, phone turned off again, repeating this cycle over and over (not the traditional bootloop as I know it). I was running a rom based on the original rom, with some slight modifications. This rom was running stable for more than a week. I know my way around Android, and am used to switching roms, flashing etc.
Right away, I checked the following things:
- Battery removal didn't help (I did not forget to put it in again ofcourse )
- Phone doesn't go into it's charging cycle when charger is connected
- I do NOT have access to recovery
- I can, however, access the boot menu (Volume up + power key, options: Normal boot, recovery, fastboot)
- I can get into fastboot mode (haven't tested ADB yet), that's the only thing that's still working
I tried to flash the original firmware using SP flashtool, and I am still able to upload firmware on the phone! I am sure that I'm using the correct ROM, and tried different PC's and drivers. Got a few succesful flashes, but still bootlooping.
I also had the idea that my battery was empty (didn't charge it overnight), and measured the battery at 3.52 V. So it was pretty empty but not that empty that it doesn't boot. In an effort to charge the phone, I left it bootlooping for an hour or so, and later on it turned out that it only drained the battery further, 2.99 V.
I didn't want to kill this battery so I did use 2 other batteries from an old Jiayu G4, which appear to work if you turn them around and hold them against the pins (note: I knew what I was doing here ). After a lot of Googling, and seeing a lot of generic "how to fix any brick" stuff I was not able to revive my phone again.
I still believe (and hope) that the error is on the software side of the phone. All the partitions should be ok and in working order according to SP flashtool.
Now this is where my knowledge stops and where (hopefully) your help comes in. What can be corrupted that I haven't checked yet? Do you guys have any suggestions to revive this "high-end" phone again? Once again, it did not happen because of bad flashing or something like that, it happened randomly when I was using the phone normally. I tried to be as accurate as possible (long story), but if there are any questions I'm happy to answer them.
Any suggestion is welcome!
Thanks in advance.

Bump..
Anyone?

bump

Bricked MF3 4.2.2 rooted

Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.

DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.

DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Just reflash the rom you are on without wiping. That should fix it.

Is the phone an i337? If it is, you're in the wrong s4 forum.

GDReaper said:
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
Click to expand...
Click to collapse
Okay and suppose i could get adb working how would i copy the "usr" file back to the "/system"

audit13 said:
Is the phone an i337? If it is, you're in the wrong s4 forum.
Click to expand...
Click to collapse
Yea it is the i337 my bad i didnt noticed can it be moved?

Contact a moderator and ask him or her to move your thread.

Lennyz1988 said:
Just reflash the rom you are on without wiping. That should fix it.
Click to expand...
Click to collapse
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.

DaFrenchTaco said:
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
Click to expand...
Click to collapse
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.

Lennyz1988 said:
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Click to expand...
Click to collapse
I think AT&T and Verizon phones always had locked bootloaders, just that the earlier versions were easier to hack.

if its hard bricked, try jtag

thnx to everyone in this thread you were all of help my phone is now working even better then it did before much appreciated

If your Y2 is in a bootloop and you can't get to the recovery..

Had the same experience as some of you - my Yotaphone got bricked (not sure why, but soon after .136RU update) and ended up in a bootloop - "Powered by Android" logo, reboot every couple of minutes. Tried flashing different recoveries and systems but no change.
Recently I've ordered a set of screwdrivers and opened my phone, disconnected the epd screen and the battery (this one only for a couple of minutes) and tried fastboot again.
Power + vol up (recovery) didn't work before and now it does, so I'm in Twrp. That's all for now (had to go to work ), but will keep you posted afterwards.

Above I'm putting the YT video I was using to safely open Y2, you will need T3 screwdriver and some lever to lift the EPD back cover - be careful, use sth soft (wood/ABS), it looks like it's very easy to break the glass.
So, back to the story..
Was in TWRP and had the full funcionality, except for the OTG. ADB also didn't work (haven't switched debugging on when Y2 was alive..). So went back to the fastboot (Power + Vol Down).
Yotaflasher did crappy job so I had to flash everything manually, command after command:
fastboot flash aboot firmware/emmc_appsboot.mbn
fastboot flash boot firmware/boot.img
fastboot flash cache firmware/cache.img
fastboot flash modem firmware/radio/NON-HLOS.bin
fastboot flash sbl1 firmware/radio/sbl1.mbn
fastboot flash rpm firmware/radio/rpm.mbn
fastboot flash tz firmware/radio/tz.mbn
fastboot flash userdata firmware/userdata.img
fastboot flash -S 512M system firmware/system.img
fastboot reboot
Click to expand...
Click to collapse
(didn't include recovery - have it already)
Now Y2 went through the "Powered by Android" logo and stopped for a while (maybe even 10min..) at its own boot animation. After that I was welcomed by Language choice menu and quickly after had my phone working. Now it's downloading .136RU update again.
Mind it's also still disconeccted from EPD screen - it has some dead pixel lines and can't figure out where lies the problem, will play with that tomorrow.
PS. Don't forget to enable USB debugging when you have the chance!

I can 't see youtube video. It is not valid. Pkease reupload him.

Maristrat said:
I can 't see youtube video. It is not valid. Pkease reupload him.
Click to expand...
Click to collapse
visit the link

Thanks. I have the same problem. Yt 201 buyed under www.coolicool.com after a ota it rest in booploop. After i disconnect baterry and lcd. I shalluse twmp or it enough fastboost with all the commands?

Maristrat said:
Thanks. I have the same problem. Yt 201 buyed under www.coolicool.com after a ota it rest in booploop. After i disconnect baterry and lcd. I shalluse twmp or it enough fastboost with all the commands?
Click to expand...
Click to collapse
maybe first just disconnect battery and epd screen and try to boot, if no then flash twrp and do factory reset and try again, if still no change then erase data and flash new system image

keeeper said:
maybe first just disconnect battery and epd screen and try to boot, if no then flash twrp and do factory reset and try again, if still no change then erase data and flash new system image
Click to expand...
Click to collapse
I have tried all, disconnect flash twmp nothing happens. I have installed again the system but it rest in bootlooop.

wow, i am not alone with this problem. Why does the problem is coming at same time in december ? any bad updates? hm.
Anybody told with yotaphone support about this problem ?
im not realy a mobile crack, its not easy for me to understand this repair process. the only thing i have do is restore und wipe cache function in the bootloader.
Then i have uploaded the newest firmware with yotaflasher. it was successfull.
ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/5.0.0-EU1.1.87a.zip
But this was not the solution. i will try "5.0.0-EU1.1.124b.zip" this is from august 2016 newer then all.
keeeper you have make manually flash, it was success? I dont know how it works with command lines. And my english is not good.
I had debugging on mode when my yota was alive.

somehow yotaflasher does not do its job properly, at least on my PC - while flashing the system directory manually it takes me a large while to move about 1GB of data, YF does it much faster, what was really suspicious.

i have flashed the new 124b now, then it updated something. And then, ahhhhhhh i see the start screen where i can choose my language. but when i plug of the handy from PC, the screen is off. game over.
i think my phone have a damaged RAM.
Question,... why does yotaflasher needs only 10sec. to flashed a 1GB firmware ??? thats unreal.
maybe first just disconnect battery and epd screen and try to boot, if no then flash twrp and do factory reset and try again, if still no change then erase data and flash new system image
Click to expand...
Click to collapse
i want to try this, but it makes me worry

izanagi23 said:
And then, ahhhhhhh i see the start screen where i can choose my language. but when i plug of the handy from PC, the screen is off
Click to expand...
Click to collapse
Is the battery fully charged? QC doesn't work all the time - it needs CPU to help and for example in recovery mode CPU doesn't support quick charging.

i cant see if it full loaded. i only plug in to power suply. Today im come to the welcome screen !!! And then, i type the password for my wlan to start configuration. But it freezed und go down.
i send you my pictures from the state. i think,.... its damaged hardware
i dont understand that the phone is started alone after 15 minutes. then crashing 10 times on boot and then mute. after 10 - 20 minutes it started again. i do nothing, it is only plug in powersuply.

izanagi23 said:
i cant see if it full loaded. i only plug in to power suply. Today im come to the welcome screen !!! And then, i type the password for my wlan to start configuration. But it freezed und go down.
i send you my pictures from the state. i think,.... its damaged hardware
i dont understand that the phone is started alone after 15 minutes. then crashing 10 times on boot and then mute. after 10 - 20 minutes it started again. i do nothing, it is only plug in powersuply.
Click to expand...
Click to collapse
I would try to disconnect the EPD completely (like in this thread and try if there's any change.
I've also had problems with random reboots but after saying goodbye to the back screen Yotaphone works like a charm. I know that wasn't the point of buying this phone but even without the EPD it's still a great device.

but this can not be normal without EPD i can use my s5
Today i was longer time in the OS. i have configured the phone and the wlan. After 5min. its crash and reboot. The battery was 1% !!!
After complete one night charging it is on 50%. this is not normal. On the EPD i have a double screen ?! 25% size on left side and on right side clone.
My Yota is a new device, i will try to send it to the seller or manufacturer

this is unbelievable. after i loading the accu complete, i can start the phone. And all works. 5 days long the phone lay without used it. After this days the phone works. Then i have install whatsapp, activate yotaFit, and will configure the "keyboard". After i changed the Keyboard Layout, UI-system hold on and the phone crashed.
After this, the phone was reboot some times and crashed again. Now, i have the same problem. What is this F** S** ?
The phone only works fine, when i do nothing. when the phone lay one week without interaction. yeay!

izanagi23 said:
i have flashed the new 124b now, then it updated something. And then, ahhhhhhh i see the start screen where i can choose my language. But when i plug of the handy from pc, the screen is off. Game over.
i think my phone have a damaged ram.
Question,... Why does yotaflasher needs only 10sec. To flashed a 1gb firmware ??? Thats unreal.
I want to try this, but it makes me worry :d
Click to expand...
Click to collapse
good afternoons i have the problem that is drained in the android logo but i can not access the recovery in any way what can i do? Do i have to remove the battery to access recovery?

By the way I have a YotaPhone 1 with a bootloop problem. Could anyone help me with finding the stock rom so that I can revive my phone?

Turned this phone into a brick and I need to fix it!

Hi, so, I got this phone from a friend, and he told me that the phone was working prorperly, but after someone factory resetted it, he wasn't able to set it up. Constant force close pop-ups where showing up while setting it up, and you weren't able to accept terms and conditions (button grayed out). Also, one thing I noticed. The phone got into "Factory Mode". Idk what that is, but it wouldn't let me to enable wifi or bluetooth. That little Factory mode thingy got me really confused. Also, I wanted to boot into recovery mode, and I wasn't able to do so. After turning the phone off, and doing the key combo to boot into recovery, the phone rebooted itself (very showrtly after doing the startup vibration) and after that, it seemd to get into recovery, but it stayed at the android logo with an exclamation sign and after 3 seconds it rebooted itself to system.
After that I said, "well, last thing to try is flashing stock rom again". And I did so. Using the Frija software to download the latest version of android for this phone (and using the corect CSC for this phone (CTI)). I used odin 3.12.7 (wich I knew it works because of previously using it with other phones) to flash the stock rom again. I made sure that only Auto-reboot and F.reset time were checked, and started flashing. After it finished, it got to the samsung logo, but got stuck there. Nothing happened (I left the phone there for like 30 min). I decided to hard-reboot the phone and try to factory-reset it, but after shutting it down, it started to be really hard to make the phone turn on. I had to unplug the battery and wait like 10 mins to try again, and I still wasnt able to boot into recovery mode. It just got stuck at the "Galaxy Core 2" logo.
After that first boot, the phone never got passed the "Galaxy Core 2" logo. Just stuck there. After that, things just begun to get worse. It was also hard to get the phone to get into download mode, most of the time it just stayed at a blackscreen (im not shure if the phone ever turned on, but it never vibrated) and did nothing. I decided to try other versions of odin. Tried with 3.09 and 3.04. Nothing, and after every flash, it got harder and harder to make the phone boot.
At this point, I can hardly get the phone into download mode, and if I do so, sometimes I get the odin complete write operation failed error, wich the only way that I've found to solve it is to reboot again the phone into download mode.
I know that the battery is working, I have another core 2 (same exact model) and battery is ok. At this moment I don't know what else to do. Please, help me to get this brick of a phone back to working conditions, I dont want my friend to buy a new phone just to use it to recive calls and charge it.
Some extra notes:
As i've read, sometimes this can be caused by the replacement of the digitizer/screen. This phone seems to have one or both of them replaced, since I can see glue residues on the corners of the glass, where it touches with the plastic frame.
If there is anything hardware related thing to try, I can try to open the phone. I have some experience doing so.

EDIT: As I continued reading through this forum, I found out that some people had luck with Odin3_v3.13.1_3B_PatcheD, so I decided to try it out and see. Still, nothing changed. As today, I can only use this phone to charge the battery (it dosent actually show the percentage, only the battery icon with a loading icon inside) and boot into download mode
Although, I have to say that after flashing the stock rom with that version of odin made the phone not that hard to start in download mode. I think that it could be something that got corrupted on the eMMC module and it has to repartition it all again...? Does anyone know how to do so?
Regards

Well, tried almost everithing I know. Downloaded rom again with binary nature, tried with odin version 3.12.7, 3.13.1_3b patched and 3.13.3, but nothing. Extracted the PIT file from the CSC file, did repartition, NAND wipe, and nothing changed. I have to say that its certaily easier to get the phone in download mode, but thats almost it. One thing to note, when i select the NAND wipe, it dosent seems to do anything. I mean, in odin Log screen some things appear related to NAND wiping and such, but its really fast and there are only 2 or 3 lines dedicated to that. Is that OK?
Anyway, please, any recoomendation or thing to try would be great, since this phone is now trash, it dosent matters if it starts to get worse, or even unusable (more than it is rn).
Regards