I made the mistake of flashing a CM nightly on my tablet, because now everything's broke. I had it set up with CWM and SlimLP alphas which were running fine, but now everything's bunk.
I've tried turning off the tablet, but it just starts back up again without warning, even when unplugged. I've tried every power/volume combination at boot, but it only boots to Android.
I hopped into an root Android terminal session and typed
Code:
reboot download
and
Code:
reboot recovery
as well as
Code:
reboot bootloader
and
Code:
reboot fastboot
all of which send the tablet back to Android post-boot.
ADB recognizes it as an ADB device, but it will only show as offline, and revoking the UBS authorizations doesn't prompt them again later.
I've even tried Odin Mobile and UAMP, as well as ROM Manager, but they won't flash anything either. Rather, the things they flash don't stick after a reboot.
What do I do?
Fixed it! Had to do a battery pull, but download mode kicked in again just fine.
How you did it? Battery pull?
Beware of nightlies, only trust after getting positive feedback from other brave saps. Must have B/U before you go there.
Pp.
How did you do it!??!
what did you do to get your tab to boot to recovery mode? i've had to revert twice in the last 2 years back to 4.2.2. because anything higher causes the tab to never boot to recovery mode to apply any updates or flash anything. would really love any help here as I can almost never find anyone with the same problem so trouble-shooting has been next-to-impossible, thank you!!
DarkWolffe said:
I made the mistake of flashing a CM nightly on my tablet, because now everything's broke. I had it set up with CWM and SlimLP alphas which were running fine, but now everything's bunk.
I've tried turning off the tablet, but it just starts back up again without warning, even when unplugged. I've tried every power/volume combination at boot, but it only boots to Android.
I hopped into an root Android terminal session and typed
Code:
reboot download
and
Code:
reboot recovery
as well as
Code:
reboot bootloader
and
Code:
reboot fastboot
all of which send the tablet back to Android post-boot.
ADB recognizes it as an ADB device, but it will only show as offline, and revoking the UBS authorizations doesn't prompt them again later.
I've even tried Odin Mobile and UAMP, as well as ROM Manager, but they won't flash anything either. Rather, the things they flash don't stick after a reboot.
What do I do?
Click to expand...
Click to collapse
I have a P5113 and since new I did one factory update, a couple of months after getting it. After that have only ran Cyanogenmod roms,currently on CM12 5.0.2 and have never had any issues (no nightlies).
Pp.
johnf84 said:
what did you do to get your tab to boot to recovery mode? i've had to revert twice in the last 2 years back to 4.2.2. because anything higher causes the tab to never boot to recovery mode to apply any updates or flash anything. would really love any help here as I can almost never find anyone with the same problem so trouble-shooting has been next-to-impossible, thank you!!
Click to expand...
Click to collapse
shsagnik said:
How you did it? Battery pull?
Click to expand...
Click to collapse
I had to do a battery pull.
johnf84 said:
what did you do to get your tab to boot to recovery mode? i've had to revert twice in the last 2 years back to 4.2.2. because anything higher causes the tab to never boot to recovery mode to apply any updates or flash anything. would really love any help here as I can almost never find anyone with the same problem so trouble-shooting has been next-to-impossible, thank you!!
Click to expand...
Click to collapse
Never quote the OP
---------- Post added at 01:50 PM ---------- Previous post was at 01:44 PM ----------
DarkWolffe said:
I had to do a battery pull.
Click to expand...
Click to collapse
I think he was asking how u did the battery pull.
AndroidMaster1909 said:
Never quote the OP
---------- Post added at 01:50 PM ---------- Previous post was at 01:44 PM ----------
I think he was asking how u did the battery pull.
Click to expand...
Click to collapse
To pull the battery, you have to remove the front faceplate from the back. You can do this by very carefully separating the glass part of the screen from the plastic housing around it. (You need to remove the SD card, too, otherwise you'll risk bending or ripping out the port) Then, once you have that removed, there's a cable that runs out of the battery to the PCB and connects with a creamish-colored connector. Just pop it out.
I followed this video for visual aid. You can see him remove the battery cable at the three minute mark.
DarkWolffe said:
To pull the battery, you have to remove the front faceplate from the back. You can do this by very carefully separating the glass part of the screen from the plastic housing around it. (You need to remove the SD card, too, otherwise you'll risk bending or ripping out the port) Then, once you have that removed, there's a cable that runs out of the battery to the PCB and connects with a creamish-colored connector. Just pop it out.
I followed this video for visual aid. You can see him remove the battery cable at the three minute mark.
Click to expand...
Click to collapse
Thanks for posting the video here but i knew what u were saying. I just wanted to tell u what he was asking.
AndroidMaster1909 said:
Thanks for posting the video here but i knew what u were saying. I just wanted to tell u what he was asking.
Click to expand...
Click to collapse
I was mostly putting it here in case anyone else ever has this problem. They have a resource.
Related
Hi all,
My Samsung Galaxy phone is stuck on the Samsung boot up logo. I shut off the phone and it starts up again to the Samsung logo again. I am rooted but still had the stock rom and kernel.
I went to selections and wiped my cache and tried to format it like a new phone. The same thing still happens. I am not sure what else to do. Anyone know how to fix this?
Keep the instructions simple please, if you do know. (I'm a desperate noob)
Thanks for any help.
IF you ever did nandroid than just restore that otherwise.........
Hey first follow this steps to flash any rom. If you flash the rom properly than you can use any stock rom from dev section and use that.
OR
follow this step to go back to stock and it will unroot you.
Vman7765 said:
Hi all,
My Samsung Galaxy phone is stuck on the Samsung boot up logo. I shut off the phone and it starts up again to the Samsung logo again. I am rooted but still had the stock rom and kernel.
I went to selections and wiped my cache and tried to format it like a new phone. The same thing still happens. I am not sure what else to do. Anyone know how to fix this?
Keep the instructions simple please, if you do know. (I'm a desperate noob)
Thanks for any help.
Click to expand...
Click to collapse
Great, I'm downloading the drivers now. My phone was working perfectly. Do you know what may have caused this? Thanks.
I am not sure why it happened but it looks like u cleared cache so that might be the problem. IDK
Vman7765 said:
Great, I'm downloading the drivers now. My phone was working perfectly. Do you know what may have caused this? Thanks.
Click to expand...
Click to collapse
Rocketing on Sky Ics¡
I'm back up and running. If I want to change my rom and kernel, what do you recommend? I midas well do everything now, while I am on work mode. Thanks for your help.
first of all to show that you appreciate my help please hit that thnx button. I am running Sky Ice Rom which is deeply themed rom with faux123's kernel.
Vman7765 said:
I'm back up and running. If I want to change my rom and kernel, what do you recommend? I midas well do everything now, while I am on work mode. Thanks for your help.
Click to expand...
Click to collapse
NP thanks for your help. I spammed that button as much as I could lol.
Same Problem
My problem is that my Rogers SGSII LTE I727R, is stuck on the logo screen, which is flashing the boot screen. When I connect the USB (even after install of Kies and Odin), my PC does not see the device. I am really not sure what to do. I think I set the wrong phone ID when I installed recovery (I think I was supposed to use the T-Mobil SGSII setting), but I selected something else. I then tried to backup the existing ROM, and am now in this unending loop. Does anyone have any suggestions? Thanks.
Follow these steps it will help you go back to stock. ANd reroot your phone.
Barlaw604 said:
My problem is that my Rogers SGSII LTE I727R, is stuck on the logo screen, which is flashing the boot screen. When I connect the USB (even after install of Kies and Odin), my PC does not see the device. I am really not sure what to do. I think I set the wrong phone ID when I installed recovery (I think I was supposed to use the T-Mobil SGSII setting), but I selected something else. I then tried to backup the existing ROM, and am now in this unending loop. Does anyone have any suggestions? Thanks.
Click to expand...
Click to collapse
I did try the main process, but the problem seems to be that the my PC/Odin, don't see my phone. The USB drivers are installed, and I have the stock rom, but I can't seem to make the connection.
Barlaw604 said:
I did try the main process, but the problem seems to be that the my PC/Odin, don't see my phone. The USB drivers are installed, and I have the stock rom, but I can't seem to make the connection.
Click to expand...
Click to collapse
Try a different USB port. Avoid rear ports and hubs.
OK, i will try that on a different computer, as I have tried all of the available ports on my laptop. Any other thoughts?
Barlaw604 said:
I did try the main process, but the problem seems to be that the my PC/Odin, don't see my phone. The USB drivers are installed, and I have the stock rom, but I can't seem to make the connection.
Click to expand...
Click to collapse
Have you uninstalled kies? If not uninstall it from your PC. Put your phone in download mode and see if Odin can see the phone.
Sent from my SAMSUNG-SGH-I727 using xda premium
Barlaw604 said:
I did try the main process, but the problem seems to be that the my PC/Odin, don't see my phone. The USB drivers are installed, and I have the stock rom, but I can't seem to make the connection.
Click to expand...
Click to collapse
Try another USB port or another computer. If you can get the logo you are in a boot loop, the most common form of a soft brick. If you can get into download mode you should be able to fix it.
---------- Post added at 04:55 PM ---------- Previous post was at 04:46 PM ----------
Barlaw604 said:
OK, i will try that on a different computer, as I have tried all of the available ports on my laptop. Any other thoughts?
Click to expand...
Click to collapse
Just saw this. Have you tried to re-install the drivers?
Another thought is to try turning off firewall and antivirus when using Odin. I've never had my firewall or antivirus block Odin but I've heard it can happen...
Can you get into download mode? Hold the two volume buttons down, then plug the usb cable into your phone, then you should be in download mode.
I cannot get into download mode. I just keep getting the flashing boot screen, with the corresponding vibration.
mimart7 said:
Can you get into download mode? Hold the two volume buttons down, then plug the usb cable into your phone, then you should be in download mode.
Click to expand...
Click to collapse
What he said. Pull the battery and put it back in. Hold volume up/down and plug in USB. Continue holding volume buttons until you see download mode. Careful not to press the power button during this process.
Sent from my SAMSUNG-SGH-I727 using xda premium
I like how u guys are really trying to help him. Let u guys know that on my first responce I gave him all the steps on how to go back to stock. So if he followed that and nothing happened than he should try USB jig if that don't work than its hard brick!!
Rocketing on Sky Ics¡
Barlaw604 said:
I cannot get into download mode. I just keep getting the flashing boot screen, with the corresponding vibration.
Click to expand...
Click to collapse
Don't panic. If you're in a boot loop it's fixable. It's when you get nothing that you need to worry about a hard brick.
Try the button combo mentioned above to get into download mode. If that doesn't work, pull the battery again and try using just the volume down button button--I've heard people say this worked for them when they had a hard time.
If this doesn't get you into download mode, I guarantee you that a jig will work. You can buy one online or make one yourself for about 75 cents and a cut-up data cable (I had a car charger that I didn't need--car charges the phone through USB port, so I cut that one up). Always good to have a jig, at any rate...
skrambled said:
Don't panic. If you're in a boot loop it's fixable. It's when you get nothing that you need to worry about a hard brick.
Try the button combo mentioned above to get into download mode. If that doesn't work, pull the battery again and try using just the volume down button button--I've heard people say this worked for them when they had a hard time.
If this doesn't get you into download mode, I guarantee you that a jig will work. You can buy one online or make one yourself for about 75 cents and a cut-up data cable (I had a car charger that I didn't need--car charges the phone through USB port, so I cut that one up). Always good to have a jig, at any rate...
Click to expand...
Click to collapse
Yup, when I rooted my phone, the only way I could get it into download was volume DOWN & power.
Sent from my SGH-I727R using xda premium
Was trying to revert my phone to stock. I pick up my phone today after where I left it and now after holding down the volume down button and connecting USB it wont even go into download mode. Tried plugging it into the wall nothing happened. Phone wont turn on either. Help!
Mod edited
Battery dead?
The battery shouldn't have anything to do with not being able to enter download mode.
roboman342 said:
The battery shouldn't have anything to do with not being able to enter download mode.
Click to expand...
Click to collapse
Correct, but if the phone doesn't turn on at all, there's probably some other problem. You may not be accessing download mode because of a bad cable, bad usb port on phone, bad usb port on computer, etc.
If your phone is dead even when you try to charge it, you may have a bad usb port that is preventing it from charging or getting into download mode. So if you've been charging it but your battery is still dead, you can probably narrow down the issue to either cable or phone's usb port...
I'm going to guess that you weren't flashing the device with the battery in the phone, causing all of the failed flashes. Since it seems like you tried to flash several times, I'm also guessing that you never paid attention to where it stopped, or bothered to see what was going on until now, and it is very possible that you do have a brick if it failed during the flash of boot.bin and/or sbl.bin. If it did, then your only options are to try a jig to get into download mode, the unbrickable mod, insurance, or buy a new phone.
Cleaned up thread and edited op. Prob a good idea not to bash ur phone and the devs when asking for help
Papa Smurf151 said:
Cleaned up thread and edited op. Prob a good idea not to bash ur phone and the devs when asking for help
Click to expand...
Click to collapse
THANK YOU! Was wondering about the logic(or lack there of) behind that.
---------- Post added at 10:17 PM ---------- Previous post was at 10:13 PM ----------
imnuts said:
...If it did, then your only options are to try a jig to get into download mode, the unbrickable mod, insurance, or buy a new phone.
Click to expand...
Click to collapse
I've only successfully completed the jig once... Not easy stuff.
Hi Guys,
i am happy to annouce that the Xperia Z2 Tablet, recieves Unoffical CM11 weekly built's by The Free Xperia Project-Team, available on there Site www.fxpblog.co
I don't take any Credits, i just thought about posting the good News for everyone to see.
Things needed:
Root
Unlocked Bootloader
Recovery
Flashing Procedure for CWM:
1. Reboot to Recovery or at Start up press Volume-Up (CWM) till the Recovery shows up.
2. back a complete Backup of your actual Rom (optional)
3. go to Mounts and storage.
4. format: cache, system, data.
5. go in advanced in the Menu and wipe "Dalvik Cache"
6. Install zip from sdcard (Internal Storage) or sdcard1 (MicroSD)
7. Choose the downloaded zip-file named like example: "FXP327-CM11-20140706-UNOFFICAL-castor" and make sure you have the right build for your device. (there is castor, for LTE version and castor_windy for the Wifi Version) and install it
8. I recommend to use the Paranoid Android Google apps package also know as "PA-Gapps"
9. Install the Latest PA-Gapps for Kitkat reapeat Step 7 just with the PA-Gapps.
10. Reboot to System.
You should now have everthing installed and working.
For any Problems with the Installation or the ROM itself, Qoute me and i will try to help you
Credits:
Free Xperia Project-Team
Cyanogenmod-Team
Best Regard's
Alex1911
Thanks for posting this. Really looking forward to CM11 on my Castor Windy. The file size for castor windy is about 100 megs smaller than the lte castor. Do we know why? Ill take the plunge and test shortly. Will report back.
bacon612 said:
Thanks for posting this. Really looking forward to CM11 on my Castor Windy. The file size for castor windy is about 100 megs smaller than the lte castor. Do we know why? Ill take the plunge and test shortly. Will report back.
Click to expand...
Click to collapse
I'd assume because the LTE version has to support LTE antenna and software and schtuff.
It is still at least 64MB smaller than the pollux windy ROM-
which should be similar in size.
I have had no luck booting the kernel boot.img contained in the
castor_windy ROM zip file on a sgp51x.
Uclydde said:
I'd assume because the LTE version has to support LTE antenna and software and schtuff.
Click to expand...
Click to collapse
bacon612 said:
Thanks for posting this. Really looking forward to CM11 on my Castor Windy. The file size for castor windy is about 100 megs smaller than the lte castor. Do we know why? Ill take the plunge and test shortly. Will report back.
Click to expand...
Click to collapse
This is a Problem in the cm Device tree e.g System ui is missing or settings apk
I wrote a pm to alex1911 how to fix it
After He add this it will work (I have build the Rom by myself some days ago and i fix it there)
Well, I did exactly as advertised, but my device is now in a bootloop. No idea what's gone wrong.
Very curious what's gone wrong here. No idea right now.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
xbill9 said:
It is still at least 64MB smaller than the pollux windy ROM-
which should be similar in size.
I have had no luck booting the kernel boot.img contained in the
castor_windy ROM zip file on a sgp51x.
Click to expand...
Click to collapse
Ah so the ROM as uploaded currently is broken, and that's why my device (see post above) is in a bootloop.
Well, I feel stupid now.
thomholwerda said:
Well, I did exactly as advertised, but my device is now in a bootloop. No idea what's gone wrong.
Very curious what's gone wrong here. No idea right now.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
Ah so the ROM as uploaded currently is broken, and that's why my device (see post above) is in a bootloop.
Well, I feel stupid now.
Click to expand...
Click to collapse
Yeah my SGP512 will only get into bootloop if I flash the castor_windy. I felt stupid before as if I was doing something wrong, but now I know it's not user error :highfive:
Uclydde said:
Yeah my SGP512 will only get into bootloop if I flash the castor_windy. I felt stupid before as if I was doing something wrong, but now I know it's not user error :highfive:
Click to expand...
Click to collapse
Weird though, since I can't even get back into cwm - nor can I end the bootloop with the power button (I time holding volume-down to get into fastboot and end the bootloop like that).
EDIT: In fact, "fastboot devices" lists nothing when I do that. So, the way I have to end the bootloop is to connect it to my PC via USB, press volume-down when the devices powers down, and then I hear the device connected sound from Windows. If I then do nothing, the bootloop continues after a while. If I issue "fastboot devices", I get nothing. Yanking out the USB cable shuts the device down.
So strange.
Rom Castor_windy
Hi
If some one want a complet Rom for wifi-tablet send me a message
I will send you a mega link to download but i don't Support it because i'm New in building Roms but it is completly based on Cyanogenmod trees
Rcstar6696
thomholwerda said:
Weird though, since I can't even get back into cwm - nor can I end the bootloop with the power button (I time holding volume-down to get into fastboot and end the bootloop like that).
EDIT: In fact, "fastboot devices" lists nothing when I do that. So, the way I have to end the bootloop is to connect it to my PC via USB, press volume-down when the devices powers down, and then I hear the device connected sound from Windows. If I then do nothing, the bootloop continues after a while. If I issue "fastboot devices", I get nothing. Yanking out the USB cable shuts the device down.
So strange.
Click to expand...
Click to collapse
EXACT same thing happened to me. I had to hold down the little red button under the big top flap, then hold up volume while plugging into my pc. I couldn't get into recovery either without flashing a stock ftf and reinstalling recovery. Flashtool is a life saver.
rcstar6696 said:
Hi
If some one want a complet Rom for wifi-tablet send me a message
I will send you a mega link to download but i don't Support it because i'm New in building Roms but it is completly based on Cyanogenmod trees
Rcstar6696
Click to expand...
Click to collapse
ill try it. Is it for z2 wifi 511? Does it boot?
Uclydde said:
EXACT same thing happened to me. I had to hold down the little red button under the big top flap, then hold up volume while plugging into my pc. I couldn't get into recovery either without flashing a stock ftf and reinstalling recovery. Flashtool is a life saver.
Click to expand...
Click to collapse
So you pressed/held the red button while in the loop, then pressed/held volume-up while pluggin it in?
I'm downloading Flashtool right now, so that should be a decent starting point. What is the stock ftf (ROM I imagine?)?
Uclydde said:
EXACT same thing happened to me. I had to hold down the little red button under the big top flap, then hold up volume while plugging into my pc. I couldn't get into recovery either without flashing a stock ftf and reinstalling recovery. Flashtool is a life saver.
Click to expand...
Click to collapse
You don't need to Flash complete ftf in flashtool exculde all except Kernel (you don't need wipe Data)than Flash the Kernel and Boot into fastboot and Flash doomloards stock kernel
Did we mess up the windy tree? Can anybody point me to the problem an i'll push the fix asap.
Regards
Bin4ry said:
Did we mess up the windy tree? Can anybody point me to the problem an i'll push the fix asap.
Regards
Click to expand...
Click to collapse
I have fix i have send you a message
rcstar6696 said:
I have fix it can you clean your privat message space your is full and i can't write you
Click to expand...
Click to collapse
cleaned
rcstar6696 said:
You don't need to Flash complete ftf in flashtool exculde all except Kernel (you don't need wipe Data)than Flash the Kernel and Boot into fastboot and Flash doomloards stock kernel
Click to expand...
Click to collapse
I saw the bootloop as well.
I went back to doomlords rooted stock kernel with CWM.
Then reflashed one of my earlier stock ROM backups.
Out of habit one of the first things I do with new HW
is to take a few full backups from the recovery after
the device is rooted and has a custom recovery.
The unusual thing with the Sony devices is that the recovery
shares the kernel image - so you have to pay attention
to both the kernel version and the ROM version.
xbill9 said:
I saw the bootloop as well.
I went back to doomlords rooted stock kernel with CWM.
Then reflashed one of my earlier stock ROM backups.
Click to expand...
Click to collapse
So how did you get back into CWM? I can't seem to get back into CWM at all.
thomholwerda said:
So you pressed/held the red button while in the loop, then pressed/held volume-up while pluggin it in?
I'm downloading Flashtool right now, so that should be a decent starting point. What is the stock ftf (ROM I imagine?)?
Click to expand...
Click to collapse
Make sure to hold the tiny red button at least until it buzzes 3 times. Make sure you're not plugged in while doing this. This basically just turns the tablet off. Then I hold up volume while plugging in to my computer. Just look around on the forums/google for any SGP511 or SGP512 ftf file.
thomholwerda said:
So how did you get back into CWM? I can't seem to get back into CWM at all.
Click to expand...
Click to collapse
I couldn't either. I had to hard power-off with tiny red button under the bigger top flap. Then hold up volume while plugging into my computer, then flash new ftf in flashtool, then re-install CWM.
Bin4ry said:
cleaned
Click to expand...
Click to collapse
So the castor_windy rom will work now?
Uclydde said:
Make sure to hold the tiny red button at least until it buzzes 3 times. Make sure you're not plugged in while doing this. This basically just turns the tablet off. Then I hold up volume while plugging in to my computer. Just look around on the forums/google for any SGP511 or SGP512 ftf file.
I couldn't either. I had to hard power-off with tiny red button under the bigger top flap. Then hold up volume while plugging into my computer, then flash new ftf in flashtool, then re-install CWM.
Click to expand...
Click to collapse
Alright, thanks a million. I couldn't find a ftf specifically for the SGP512, but according to this comment a specific SGP511 ftf will work as well.
I'm guessing Flashtool is pretty self-explanatory (it looks pretty straightforward), but if not, I'll be back .
Thanks again!
---------- Post added at 09:19 PM ---------- Previous post was at 08:56 PM ----------
Uclydde said:
Make sure to hold the tiny red button at least until it buzzes 3 times. Make sure you're not plugged in while doing this. This basically just turns the tablet off. Then I hold up volume while plugging in to my computer. Just look around on the forums/google for any SGP511 or SGP512 ftf file.
I couldn't either. I had to hard power-off with tiny red button under the bigger top flap. Then hold up volume while plugging into my computer, then flash new ftf in flashtool, then re-install CWM.
Click to expand...
Click to collapse
Well, I must have done something wrong.
So, I got Flashtool to recognise the device exactly as you said. However, Flashtool didn't have an option for showing/opening ftf files, so I disconnected the device. I then Googled the exact procedure (and felt like an idiot), found it, and wanted to reconnect the device.
No luck. All I get now is a blue light when I press volume-up and connect it via USB. Flashtool recognises nothing. I also turned it back on into the bootloop, pressed the red button, and tried again - no luck. Any ideas?
So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..
I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.
Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..
when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).
I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.
There's not even a way I can communicate with the phone from the PC.
any suggestions, any ideas??
I can't believe that a device would be bricked from xposed module??
I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
THE_KINGDOM said:
So I was posting about this in the Purity thread already, but this has become a major unresolvable issue so far..
I just updated clean install/flash of Purity ROM to the newest version, with the included stock kernel.
I tried out xposed framework, and only 1 mod (Serajr Blurred System UI)
on dalvik of course.. working fine for over a day.
Suddenly today, phone turned off in the gym randomly and wouldn't boot, then after 30 minutes in the gym after repeatedly trying it eventually boot, then right when I got home, I decided to un-install the mod on xposed framework, and reboot and then boom, off again not turning on for several hours... phone is not detectable by adb or fastboot. when connected to a PC, absolutely nothing, completely dead..
when connected to pc... the only thing that happens when I do vol up + vol down + power is that it cycles through usb device connecting on the PC but (device cannot start).
I've tried charging it, leaving it, I've went through every trouble shooting option that I know of.
There's not even a way I can communicate with the phone from the PC.
any suggestions, any ideas??
I can't believe that a device would be bricked from xposed module??
I could do an RMA, as the device is relatively new,
but If I return this device I'm worried about warranty void due to unlocked bootloader and custom ROM etc??
Click to expand...
Click to collapse
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
Wakamatsu said:
I'm leaning towards this being a hardware issue. If you got the phone straight from Google, the unlocked bootloader and custom whatever shouldn't be an issue.
Click to expand...
Click to collapse
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
joecool666 said:
you could try nexus root toolkit, also you could try with power off hold vol-up insert USB it should install lg flash tool driver's.some time's it take's it time installing driver's so just give it a min or two regard's joe
Click to expand...
Click to collapse
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
THE_KINGDOM said:
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
Click to expand...
Click to collapse
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
THE_KINGDOM said:
ok as long as it shouldn't be a problem I'm prob going to do an RMA.
Ok I'm going to try holding vol-up and insert USB, but i assume for nexus root toolkit to work it phone would need to be visible as a "fastboot" device bare minimum, which I'm having problems even getting that right now.
Click to expand...
Click to collapse
how's it going any news?
joecool666 said:
hi, nexus toolkit has an op for soft-bricked/bootloop. it might detect your device.
---------- Post added at 01:38 AM ---------- Previous post was at 01:22 AM ----------
how's it going any news?
Click to expand...
Click to collapse
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
THE_KINGDOM said:
vol-up and power while connecting usb didn't do anything so far. I'm going to try nexus toolkit just for the hell of it, but I think this device is literally bricked beyond repair.
Click to expand...
Click to collapse
yeah sound's like it could be hard bricked, hope toolkit work's for you tho.
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
THE_KINGDOM said:
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
Click to expand...
Click to collapse
strange that, not getting detected by p.c, yeah look's like a trip to the service station.sorry i coulden't be of more help. hope you get it back to life.kind regard's joe
THE_KINGDOM said:
just doesn't make any sense of why it would be hard-bricked.. randomly just turns off.. so weird
Click to expand...
Click to collapse
All bricks are hard bricks. As much as people use the term "soft bricked", believe me - it isn't a thing. A brick is irreparable. If it was repairable, it isn't a brick.
If it is irreparable, its because its been affected beyond the software layer. Messing up the NAND partitions or NAND death are the most common. This can happen during a flash or even seemingly random - its not unusual for bricks to be random. Flash memory in my opinion, is still pretty unstable. Send it for repair /RMA.
Sent from my Nexus 5 using Tapatalk
Recently my screen's digitizer broke, so I ordered a new screen and just got it today.
I replaced it and I tested it, it turned on and that, but when I try to boot it just come with the onplus logo and powered by android stuff in the bottom and that's the only thing it's showing with it just turns off and on basically rebooting
So I tested, can it go into fastboot it could so I tried flashing twrp on but didn't work keeps doing the same cannot even enter recovery just fastboot.
Anyone tried this before or, what can I do to fix it if there is a possible fix for it.
Have you tried flashing official images from fastboot? hopefully not a hardware issues
I'm having the same problem, also since today. My phone just got in a bootloop while powered on and running completely fine. Trying to boot into recovery also gets me a bootloop. Fastboot works, and when i try to flash anything it tells me it succeeds. Then when i try to power on again, still the same bootloop.
I've tried the Oneplus Recovery Tool, same thing. Everything succeeds, but I still end up with a bootloop. The logo on the fastboot page had changed, though, so I'm guessing the flash was successful, but something else is broken.
I'm actually really worried about my phone right now.
morreion said:
I'm having the same problem, also since today. My phone just got in a bootloop while powered on and running completely fine. Trying to boot into recovery also gets me a bootloop. Fastboot works, and when i try to flash anything it tells me it succeeds. Then when i try to power on again, still the same bootloop.
I've tried the Oneplus Recovery Tool, same thing. Everything succeeds, but I still end up with a bootloop. The logo on the fastboot page had changed, though, so I'm guessing the flash was successful, but something else is broken.
I'm actually really worried about my phone right now.
Click to expand...
Click to collapse
You tried one plus recovery tool cm11s?
Mr.Ak said:
You tried one plus recovery tool cm11s?
Click to expand...
Click to collapse
Yep, that's the one. Everything seems to work fine, all the bars are loading, and the device turns green. Unplugged the device, booted up, still a bootloop.
I tried the ColorOS guide (https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732) too, same thing. The boot logo did turn red though.
morreion said:
Yep, that's the one. Everything seems to work fine, all the bars are loading, and the device turns green. Unplugged the device, booted up, still a bootloop.
I tried the ColorOS guide (https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732) too, same thing. The boot logo did turn red though.
Click to expand...
Click to collapse
If even that tool couldn't solve it then it's definitely a hardware issue.
Mr.Ak said:
If even that tool couldn't solve it then it's definitely a hardware issue.
Click to expand...
Click to collapse
Damn. Well, too bad. I'm going to try to fix my phone for a bit more, not that I think it's still fixable. Thanks!
I also think it is a hardware issue but I don't want it to be :/
It's just funny but I think I found it, its the power button because apparently the button itself got off the wire so maybe I can sort it on again.
Or maybe it could be something else but cannot seem to find it.
I maybe u try to get my friend to sort a new storage chip on if I can get I contact with him wish me luck
morreion said:
Damn. Well, too bad. I'm going to try to fix my phone for a bit more, not that I think it's still fixable. Thanks!
Click to expand...
Click to collapse
Just get your device checked from a local source and then replace the decayed part yourself.
AFAIK,it can be either battery or Motherboard/Logic board.
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
Melonendk said:
I also think it is a hardware issue but I don't want it to be :/
It's just funny but I think I found it, its the power button because apparently the button itself got off the wire so maybe I can sort it on again.
Or maybe it could be something else but cannot seem to find it.
I maybe u try to get my friend to sort a new storage chip on if I can get I contact with him wish me luck
Click to expand...
Click to collapse
Best of luck!
I am encountering the same problem. Out of nowhere my phone started rebooting. It reboots ok and after a minute it does it again...so it is working alright for a minute. However, my phone is completely stock Cyanogen OS...
I have tried this, but it did not work for me.
diosak said:
I am encountering the same problem. Out of nowhere my phone started rebooting. It reboots ok and after a minute it does it again...so it is working alright for a minute. However, my phone is completely stock Cyanogen OS...
I have tried this, but it did not work for me.
Click to expand...
Click to collapse
If it does work alright for a minute every time, I don't think you have the same problem as I have.