Develop Bugs

[Trouble] Reboot... reboot... reboot

Hi guys,
I've receive yesterday my new Google Galaxy Nexus.
Everything was fine, the phone was working all day. Because it's the first day of the phone, i've decided to let him go untill the battery is down.
But, at 8%, the phone just shutdown, and start to reboot automatically all the time. I've put it on charge, and it continue.
Here are the step :
1. It reboot
2. There is the animation with those color who is coming
3. Main screen // lock SIM
4. 5 seconds after the main screen, it reboot
Go to step 1 again.
It won't stop.
Could you help me here ?
Btw, i'm in France, with Orange.
Thks.
C.

Remove your Sim and try again.
Sent from my LG-P999

It doesn't work.
The main screen came, and after 3sec, the screen is like freezing for 1 sec, and after that, baaaam, it reboot again.

Maevix said:
It doesn't work.
The main screen came, and after 3sec, the screen is like freezing for 1 sec, and after that, baaaam, it reboot again.
Click to expand...
Click to collapse
Do a factory restore is the only thing I can think of; if you have pulled the battery already
Use the factory images here: http://code.google.com/android/nexus/images.html
Or you could try flashing boot again, so just get the packages images from the factory package extract the boot.img and boot it from fastboot
Code:
fastboot boot boot.img
If that works then flash it:
Code:
fastboot flash boot.img
If that fails then just do a complete restore try use teh scrip in the package

I've Wipe the phone, and right now it's working (except that i have lost my configuration).
So, it's SOLVE.
Thx guys !

Try and remember what app you installed right before your phone went bonkers.
Don't install that app again.
Sent from my LG-P999

Yeah, sure.
But today, again, my phone just start to reboot, over and over.
I'd to swipe and format AGAIN my phone, wich is sad, because everytime i do that, i lose all my user data.
It's strange because it didn't freeze just after i'd installed some app, but hour after. I just don't understand, and i really don't want that to happen again.
Did someone else got the same problem then I ? I didn't find another topic about that problem.
Thx a lot guys!
Céd.

Maevix said:
Did someone else got the same problem then I ? I didn't find another topic about that problem.
Click to expand...
Click to collapse
I have basically the same problem, intermittently. The phone will just be sitting there and suddenly reboot. I will enter the SIM PIN and then it will continue, and then shortly afterwards reboot again. The only way I can stop the Insane Reboot Loop (IRL) is to pull the battery. Then, when it reboots, it stays booted - until the next IRL starts (I've only seen two so far - but then again I've only had the phone for a couple of days).

Again, hello all,
it's me and my [big] problem with my Samsung Galaxy Nexus.
I have my phone since more than one week right now. Every two days, my phone will restart, booting over and over, freezing each time at the reboot animation.
The only way to make it stop to reboot is to format/wipe the data and restore the factory configuration. Which is very very annoying, i'm loosing all my personal data.
It really drive me crazy. I don't know what to do.
My phone is not rooted, it's just a simple SGN with some apps.
Can you help me here please ?

Strange issue, need a little help.

I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
EDIT, as posted below:
I was getting ready to do the ODIN restore when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now. I even booted into recovery and it is functioning as normal.
Any ideas what happened?

Dakota0206 said:
I was on my phone, checking XDA, reading news and so forth. I put the phone down to grab some dinner. When I got back after eating I picked up my phone and it was unresponsive.
I held down the power button for a while and nothing.
I did a battery pull and I was able to boot to the Google splash screen with the unlock symbol. Unfortunately it just hung there.
I pulled the battery again, this time I booted in fastboot, then recovery. The clockworkmod recovery main menu came up in recovery, but when trying to do a restore or anything… The blue menu would disappear and not come back. I can get to recovery, but I am unable to do anything with it.
Last night I flashed to AOKP B26 from AOKP B25. I wiped cache and dalvik. I did not do a full wipe, but according to the dev you do not need to. This morning I flashed Morphic’s kernel TNP138-RD-FUV. I used this kernel on B25 with no issues for several days as well. I wiped cache and dalvik before flashing the kernel as well. CPU was set to the default 1190 and default voltages, with the on demand governor.
It is weird that I didn’t have any issues until hours later and the phone wasn’t even in use. It is as if it wiped itself. I am wondering how and why.
At this point I am going to do a full factory ODIN restore. I don’t think there are any other options.
Click to expand...
Click to collapse
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk

if you can get into cwm then try fastboot and flash the factory images from the boot screen

_Dennis_ said:
In cwm is there a 'go back' option at the bottom? If not scroll up and down a few times passing from bottom to top (looping) until it says like back button activated. If back is not active power button makes screen go off and on and does not select.
This is if you are not using touch enabled cwm.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am not using the touch enabled. I know that if you cycle through the menu too much it will disable the select button, but if you keep cycling it will enable it. This isn't that.
The screen is on, I can see the clockworkmod recovery & version in the middle of the screen. Just the ICS blue menu disappears completely. no go back or anything. just a black screen with the clockworkmod info in the middle. It is as if its thinking but it just hangs.

id suggest you try to use ADB from recovery to try and at least pull the sdcard files first of all
second id try to flash another recovery from fastboot then boot to recovery and flash a rom or restore backup
if the above doesnt work then factory image from fastboot is it

I was getting ready to do the ODIN recovery when for the heck of it I decided to let it boot normally one last time. What do I have to lose.
I booted to the Google splash screen and set it down. I got a drink and took out the trash. When I came back I noticed it was at the boot animation! It sat at the boot animation for another couple of minutes but 10 minutes after pressing the power button I was booted up.
I let it sit for another 10 before I played with it. But now its like nothing ever happened. And it boots regularly now.
Any ideas what happened?
Sent from my Samsung Galaxy Nexus - Verizon 4G LTE.

Did I just BRICK my G Nexus?

So, last night I was out and about - just having a good time. Noticed that the battery on my GSM Galaxy Nexus was getting low. Went "Meh, wasn't the first time it's died." It got to 1% battery power and shut-off, like it normally does. Me being who I am, I turned it back on to see just how much more juice I could get out of it.
Phone booted up alright. Finished the boot animation, and then a couple seconds later turned off.. not a big deal. I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
I'm not talking about the regular charge screen. After the battery gets 'filled' twice, it completely restarts. Black screen for 2 or so seconds, and then it goes through the charge animations as it would if you had just pluggied it in. I CAN get into bootloader, but that's about it. I'm just curious.. has anyone seen this before? Or know what my problem might be?
I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.

Try going into recovery and wiping cache and dalvik. If that doesn't work reflash your rom

My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..

i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).

i.vt3c.d0hc said:
[snip]
I get home, plug it in, and the charge screens cycle..... and then they cycle again. And again. And again. Basically just looping. I turn the phone ON, finishes the boot animation and... turns off again riight away? Goes back to the charge screen loop.
Click to expand...
Click to collapse
Turn it off. Leave it charging for a few hours before turning it on.
i.vt3c.d0hc said:
[snip] I'm unable to turn USB Debugging on in the system settings, so I'm at a loss as to how I can fix this issue WITHOUT bringing it into Bell.
Click to expand...
Click to collapse
You do not need to have USB debugging enabled to use fastboot.
i.vt3c.d0hc said:
My phone is completely stock (I reflashed it to to the stock yakju? I believe it was when I found out Samsung had screwed people off the google update path.. so I can't get into recovery mode. It just shows the broken android. It's all been re-locked, and since then, my laptop has died. So I no longer have the ABD/Samsung drivers setup. Which was a pain to get going the first time..
Click to expand...
Click to collapse
It doesn't take long at all to install the drivers. Look for a thread with "universal" in the title. I think it is in GN General. Once you do install the fastboot driver, download the fastboot.exe file and reflash the stock ROM.
Diger36 said:
The "Broken android" IS stock recovery. I believe that when you push Volume Up seeing that image it takes you to the stock recovery menu. But you can always reflash Yakju or any other ROM through fastboot mode (see the tutorials here on the forum).
Click to expand...
Click to collapse
It's volume up and the power button.
Sent from my Galaxy Nexus using Tapatalk

The problem I have is that the charge animation doesn't change... i.e. It'll constantly refill the battery and all, but it always starts from the bottom (While when a phone is say... half charged, the little battery is half filled and the animation continues.
I'm not sure it's even charging at all.

Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?

i.vt3c.d0hc said:
Update time!
Got it into the stock recovery. Wiped the cache and all of my data. Rebooted, and.... it turns on! No longer reboots on regular startup. That's the good news. So at least it's somewhat useable now..
Now for the BAD news.
-It still does that retarded charging bootloop that doesn't seem to get me anywhere
-....When it's on. Like, running, it doesn't charge. Nadda. Zip. Zilch. Computer, wall charger, android dock, nothing. It just won't charge when it's on. However when I got it to power on, it said I had 14% remaining - which means it was likely charging inside the Bootloader, as I had it on that for quite a bit.
I think this just went from a software to a hardware issue. Thoughts?
Click to expand...
Click to collapse
Power down phone, do a long battery pull, place it inside again, let it charge for a few hours without powering it on, when it is fully charged (or after a few hours) pull battery again and then take charger out the phone. After a few minutes, place battery inside phone again and start it up without the charger.
Hope that works.
Sent from my Galaxy Nexus using xda premium

And that might fix this charging bootloop? Because the LCD doesn't even turn off..

i.vt3c.d0hc said:
And that might fix this charging bootloop? Because the LCD doesn't even turn off..
Click to expand...
Click to collapse
You could always try a new battery
Sent from my Galaxy Nexus using xda premium

+1 for the new battery thought.

Battery test
I am having a similar problem, I get the boot loop.
Difference is that I had started with a new battery so that could be your problem or unrelated. I went to a mobile shop yesterday and they let me use a new battery to see if the loop would start. It did not so there seems to be at least one other failure path. I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
I posted to this thread #192
http://forum.xda-developers.com/showthread.php?t=1490815
My Galaxy Nexus phone from WIND went into a reboot loop yesterday. It had been charged to 98%, used to make a call and then put away. Wireless was enabled. Noticed vibration periodically and say it was rebooting every 6 - 7 seconds. Pulled battery to stop reboot. Saw references to fully charged battery via USB stops reboot loop so tried that. Battery voltage was 4.17V and still went into reboot loop.
Tried to boot into safe mode but still goes into a loop
I went into recovery mode and tried all options but factory reset because I am hoping to recover some pictures
reboot system now
apply update from cache (but did not have an update to install as only options were ../ lost+found/ recovery and when I selected these was in a loop as well)
wipe cache partition
Can't tell what version of Andorid I have as the phone never finishes booting.
Boot console gives the following information
Product Name – tuna
Variant – maguro
HW version – 9
Bootloader version – PRIMEKK14
Baseband version – I9250UGKL1
Have installed SMS backup because I was planning to do a backup after a trip. Also have two GPS tracker apps installed.

GNMO15 said:
[snip]
I have avoided a factory reset as I was hoping to pull some pictures but coming to the realization that I will have to try factory reset as a last resort
Click to expand...
Click to collapse
If you can boot into recovery, you may be able to get your pictures off your device.
1) Make sure you have the drivers for your device properly installed on your computer.
2) Download the attachment and unzip it to a directory on your computer.
3) Open a command prompt in the same directory.
4) Reboot your device into recovery and plug into your computer.
5) Make sure your computer sees your device by typing: adb devices
6) Pull the data off your device by typing: adb pull /data/media
Note: depending on how much data you had on /sdcard, this could take a while, so be patient.

[Q] Random Reboot Leads to Bootloop from...

OK all I am sincerely reaching out as I am out of ideas. Here is the situation...
Issue : Last evening, running most recent Liquid Smooth 4.4 (Superb ROM, I don't feel this is really at fault just relevant and thorough), I had been doing some heavy tethering when I picked up my beast and stepped out for a smoke. As I am reading up on moto360's 2 1/2 hour sellout I get a random reboot. Eh, no biggy ... it does happen. (Not often, or at all to speak of in my case just stating.) Right after reboot I hit the power button to make a forced boot cycle and it rebooted again before I pressed anything on screen!
Now SOMETIMES I will boot past the initial "NOTE II" splash (NOT often at all ... usually get reboots, splash hangs, or the phone simply turns off on its own from here) If it does make it past Note II splash it will reboot, hang, or simply turn off from here as well.
Steps Taken: I firstly, attempted a restore... no dice. I attempted a fresh install (TW, SlimRom, and DU) ... no dice dos. OK hmmmm
Now to all mighty ODIN (L900VPUCNE2_L900SPTCNE2_1561791_REV04) .... NO FREAKING DICE!!! WTF?!?!? I additionally attempted MC2_STOCK_with_COUNT_RESET-20130511 ... no bueno!
I still have access to Recovery and Download soooooooo ... I lay down at the mercy of you the community!!!
Thanks in advance and if you need more info PLEASE don't be shy!

Same issue here!!!
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??

Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.

Exact same thing
I've been running the latest nightlies of OmniRom. And yesterday, out of the blue, random reset then bootloop. No luck with anything, recovery, odin, etc.
Did Sprint deliberately brick our phones?
I'll try the odin to stock to see if I get any luck there. But if anyone else figures it out, it'd be nice to know the fix. Thanks!

No luck going back to stock. It's dead Jim.

I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
If my case, my phone would boot loop around the splash screen. on the battery power only. I could go into recovery and download mode with no issues and stay on for hours. If I connected it to, say a PC, it would boot, but would random shut off within five minutes. But if I plugged into the wall charger, it would boot with no problems. Stay on for hours. If I plugged it from the charger, it would immediately shut off and try rebooting which it would just boot loop.
Luckily, the batteries are pretty cheap at $10 to $20 on Amazon. I went with the Anker for $15 to get me by till I get my next phone, which will probably be October; I'm heavily learning towards the Note 4

Replace the battery
I had the exact same issues. I ended up buying a $10 battery on amazon and it solved the problem. I did go through all the flashing, odin to stock, etc. All was pretty good when plugged in to a good power source. It took me about 4 hours of trial, error, reflashing, etc before I realized it was probably a battery issue. The new battery has solved the problem.

lovekeiiy said:
I had a very similar issue. Try booting your phone with it plugged into the wall changer; something given the full 2amps of power. It it'll boot, it's possible your battery is bad.
Click to expand...
Click to collapse
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?

crackrock360 said:
After a random reboot, I have the same type issue!
Running an almost stock NE2 rom, random reboot then hanging at the Note2 bootscreen.
Like you, I can access download and PhilZ recovery.
I CANNOT flash through recovery. Errors out.
Odin flashes succeed but on reboot I still hang at the Note2 bootscreen.
My recovery is showing multiple error related to accessing E:, E:/cache, etc.
Are you having that issue as well??
Click to expand...
Click to collapse
I couldn't flash any of counter reset rom through anything but TWP so i have to boot into download and update away from Philz. AFTER the recovery update I started making headway. but couldn't ever seem to make it past boot no matter how much batter is charged. I was beginning to think it was something that died on the inside (heh...heh)
After reading through some of these greatly appreciated replies I am going to plug her up to the wall and try the ne2 counter reset again(12:58 am). ... AND I may go throw some cash at a battery juuuuuust in case. (I do tether 100gigs daily sooooooo it does make sense that it could have burnted up lmao!)
UPDATE 1:25AM : I did as advised and it does seem battery has taken a dive! hmmm so weird! It still shows having power and charging. But after being plugged into wall I made it booted into a fresh ODIN install!!! (keep in mind that AS SOON AS odin gave me a pass I switched to Wall outlet!) I have even performed a power cycle to confirm it wasn't a fluke! I will indeed be out first thing in the morn to get a new battery!
AGAIN I can not thank you all enough ... I would have never thought of that. (you would think it would be one of the first things but eh you live and learn.)
I will update with any new progress!
cheers!

crackrock360 said:
When I try to power the phone on while plugged to the charger. I see the battery graphic with a circle on it but the phone won't boot at all.
When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.
Do the batteries go bad instantly?
Click to expand...
Click to collapse
'When the random reboot happened the phone WAS plugged into the charger and fully charged. Prior my problem, battery life had been excellent.' EXACT CIRCUMSTANCES AS I SIR!!!
Mine does the same and hangs .... right? HIt the power button and as soon as it lights up to start to boot then plug in the power cable. (the freezing while off and charging is a known bug in at least two roms i believe)

Congrats Rubledub!
As for me, I'm still screwed. Invested $40 in a battery (had to have it today, couldn't wait on shipping)
With the new battery fully charged I still have the same result!

crackrock360 said:
,,, Do the batteries go bad instantly?
Click to expand...
Click to collapse
There were probably signs of the battery going bad, but misread. But in my experience, it went to total crap instantly.
The signs of going bad were shorter battery life, getting stuck/freezing when trying to charge the phone when off (there's that battery graphic that shows up). Unfortunately, I did all kids of other stuff before I really figured it out, and looks like a messed up my modem and now cannot connect to 3G. Kind of irritating, but luckily, I spend 75% of my time in LTE areas. Just got to ride this out till the Note 4 is released.
Here is thread of when I was having trouble: linky/URL]. It's a lot of me trying slightly different things with no changes in results. Plus, I was a buddy's house who was in a 3G only area. The worse part, my phone did this the day before I left to spend the weekend five hundred miles away from home at a friend's house to visit.

sloanmeister said:
Try this go to samsung-updates.com
search device l900 scroll to the very bottom of the list
download the L900VPUCNE2 zip (this is a pure sprint rom)
flash using ODIN3 v3.09
I have flashed this file many times and it works every time.
Hope this Helps.
Click to expand...
Click to collapse
Just chiming in to say this worked for me! Thanks!

Joelski144 said:
Just chiming in to say this worked for me! Thanks!
Click to expand...
Click to collapse
Oh i agree! Thats is what had me so baffled ... Not even the odin installs were breathing life, and Odin ALWAYS works for me. If Odin isnt getting it done and neither is a battery then your problem may be far more serious???

Weird Recovery Lag and bootlooping after CM12 update
Hey guys,
I came across this thread and the issues I'm having sound so what similar, so I thought you might be able to help.
I have two Samsung Note 2(l900) and running on cm12 as of yesterday morning. I installed the new nightly manually on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
I'm back on stock rom and the device is working great but takes forever to get into manual recovery which I believe is why it is having issues booting Cm 12

Useful advice for scenario: Blank TWRP + Bootloop After Rom Flash.

I had almost given up on my phone and was coming here to get some help.
As I was writing up this thread I had left my phone on the blank screen I'm about to describe.
then i noticed out of the corner of my eye the screen light up.
So my advice is, if you ever have this scenario happen it may take over 20 minutes for TWRP to even load.
This may not be something that can be duplicated, but hopefully it can be useful for someone who would panic about this like myself and keep trying things.
(I have a sneaky suspicion about my SD card now, I believe it may have become corrupted during the install.. breaking the rom.. and then making the phone hang while loading twrp.)
Mate - mt1-u06
(Ab)using TWRP v2.8.1.0
Thanks
So today I wanted to try out this:
http://forum.xda-developers.com/ascend-p6/ascend-mate/rom-omnirom-t3092487
and when I flashed it through twrp I did the install it was all successful but I forgot to wipe before rebooting (woops) So i thought hmm maybe it didn't need it,
so left it for a few minutes, realized this is a bootloop and needed to be done again.
So I was like okay I'll just shut it off and go back into recovery.
Did it like I normally would (power and the volume) and my heart kinda sank when I got a black screen (back-lit so you could tell it was still on).
weird usually it loads...
powered it off and let it load normally again to see if it was just taking a while to setup maybe to just get into the OS.
Nope 1 hour later nothing.
Have tried getting into recovery a million times but its still blank.
and to get the nooby stuff out of the way:
Fully charged before I did it and It wouldn't even turn on if it wasn't so that's kind obvious.
Mate - mt1-u06
using TWRP v2.8.1.0
Click to expand...
Click to collapse