I have been having problems with my phone for weeks, to the point where I thought I would need a new phone (and many people commented this same belief). I managed to find ways to work around the problems. But now, I have a serious problem that I did not foresee: my phone will not reboot, even after a factory reset and clearing the cache partition. It all started because I installed an app called "Boot Animations" by JRummy Apps Inc. on the Play Store. I wanted a new boot animation. I installed the animation I wanted, then granted the app root permission to change my boot animation. I checked "yes" to creating a backup of my original animation, thinking that would be my safety net in case anything went wrong...
I rebooted my phone to see my fancy new Nexus inspired boot animation, and all I get is a black screen...for an hour. I figured a factory reset would fix things, but it didn't. My phone is still stuck at the black screen. After a few minutes of black screen, it turns white, and stays like that. But it doesn't go any farther than that white screen. I'm not even getting a carrier logo.
I'm hesitant to say my phone is ruined, since that's what I, and several other people, said about my previous phone issues, but those problems ended up being fixable. I would like to think that there is also some work-around for this new issue. I have an Alcatel One Touch Sonic A851L, running android 4.1.2. It's rooted. There is no stock firmware available for me to re-flash (I have looked for it everywhere and asked my service provider for it, and they could not provide the firmware). When I plug my phone into my computer, it says "CD Drive (H: )Alcatel_USB_auto", and the folders are "autorun", "driverinstaller', and "setup". No file access.
Does anyone have any solutions or ideas?
Also, when my phone is plugged into a computer via USB, it loops. It goes from the 'Alcatel' screen, to black, to off, then repeats about 10 times before finally stopping. Then it's recognized by my computer as a CD drive. When it's plugged into a wall, it just goes to the battery screen, but doesn't loop.
If debugging mode is on in developer option ,you can try this.
Download a bootanimation according to your phones screen resolution from here :- http://androidbootanimation.com/category/android-boot-animations/Try to access your system file by your computer using android commander.Delete bootanimation.zip file from system/media.Place the downloaded bootanimation file in system/media.Then reboot your phone.
raymond_bqg said:
If debugging mode is on in developer option ,you can try this.
Download a bootanimation according to your phones screen resolution from here :- http://androidbootanimation.com/category/android-boot-animations/Try to access your system file by your computer using android commander.Delete bootanimation.zip file from system/media.Place the downloaded bootanimation file in system/media.Then reboot your phone.
Click to expand...
Click to collapse
Will the android commander work if my phone isn't booting at all? I can't access anything, all I'm getting is a black screen. I think the stock boot animation itself got damaged by the app I used to change it.
fullscore21 said:
Will the android commander work if my phone isn't booting at all? I can't access anything, all I'm getting is a black screen. I think the stock boot animation itself got damaged by the app I used to change it.
Click to expand...
Click to collapse
Well...u should give it a chance.
I also think ur stock bootanimation is replaced ,that's why I gave you a link of alternate bootanimation.
raymond_bqg said:
Well...u should give it a chance.
I also think ur stock bootanimation is replaced ,that's why I gave you a link of alternate bootanimation.
Click to expand...
Click to collapse
I tried your solution. Installed android commander and...I can see my files!!! However, I have an issue. When I try to alter my system files in any way, I get a message "You need root access to do this operation". My phone is rooted, but I'm still getting that message. Any workaround that you know of?
fullscore21 said:
I tried your solution. Installed android commander and...I can see my files!!! However, I have an issue. When I try to alter my system files in any way, I get a message "You need root access to do this operation". My phone is rooted, but I'm still getting that message. Any workaround that you know of?
Click to expand...
Click to collapse
Do you have a custom recovery installed? If yes, which one?
Freewander10 said:
Do you have a custom recovery installed? If yes, which one?
Click to expand...
Click to collapse
Unfortunately, no. What's more frustrating is, in the days leading up to this, I had a nagging feeling out of nowhere that I should make a backup. But I said "nah, nothing will ever go so horribly wrong that I need to recover all of my stock files"
Is there a custom recovery available for your phone?
Also, check this post and see if its something you can pull off:
http://forum.xda-developers.com/showpost.php?p=56949443&postcount=2
And this thread (if you haven't already)
http://forum.xda-developers.com/showthread.php?t=2426426&page=1
fullscore21 said:
I tried your solution. Installed android commander and...I can see my files!!! However, I have an issue. When I try to alter my system files in any way, I get a message "You need root access to do this operation". My phone is rooted, but I'm still getting that message. Any workaround that you know of?
Click to expand...
Click to collapse
OK...connect your phone by PC and exucte :- "adb shell su"
raymond_bqg said:
OK...connect your phone by PC and exucte :- "adb shell su"
Click to expand...
Click to collapse
Just tried that. Got this message:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Users\Leigh.HOME>adb shell su
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ #
C:\Users\Leigh.HOME>
Thanks to everyone who tried to help. I pretty much gave up and am getting a new phone (no problem, the phone was only $19.99). I'm definitely going to install a custom recovery on my new phone.
fullscore21 said:
Thanks to everyone who tried to help. I pretty much gave up and am getting a new phone (no problem, the phone was only $19.99). I'm definitely going to install a custom recovery on my new phone.
Click to expand...
Click to collapse
Did you already give up fixing your device? Hey if you are still interested you could try twrp easy maker. It will create twrp for your phone and install for you. Just google for it or look for it in xda. From twrp recovery mount system and go to file explorer and delete boot animation.zip After that the phone should reboot without boot animation.
Related
[SOLVED]
MESSAGE TO DEVELOPERS/ANYONE WHO CAN HELP
Long story short, i edited my build.prop incorrectly and reset (yes i know very stupid) now my motorola cliq opens up to the motoblur screen but repeated messages saying "Sorry! the process X has shut down" show up.
Literaly, nearly nothing can open up but i am able to enter usb mode if i fight with the endless popups. i can also enter recovery mode because my phone was rooted before this. The problem is that my recovery image doesnt have any options that could help me
(reboot, apply sd card:update.zip, and wipe data/factory reset)
i've tried putting an official motorola update.zip onto my sd card then running the apply.. but like i told you before my build.prop is messed up a little so an error shows up saying:
Installing update...
E/:Failure at line 1: assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=motorola/morrison_two_us/morrison/morrison:1.5/CUPCAKE/1.4.8:user/rel-keys" == "true" || file_contains("SYSTEM:build.prop", "ro.build.prop", "ro.build.fingerprint=MOTO/morrison_two_us/moInstallation aborted
Press Menu+Back to reboot
All i need to do is fix the line of code i messed up but i cant reach my systems files,...i attached my original build.prop and a copy of my corrupted one to show you.. I also cannot use the phone service or network service (even wifi) because like i said, nearly ALL the services are unable to stay on, they immediately shut off at startup.
Ways to fix this would be to REACH/EDIT THE SYSTEMS FILES
1. I cant use an app like root explorer since i cant access any apps on my phone even things like my settings
2. Turn on usb debugging somehow (I cant access my settings app so im lost on this one)
1. ingenious DESKTOP program that can somehow access my phone's system files without adb (if it can access the sd there has to be a way..)
3. Ive looked around to maybe find a custom image recovery that had options like editing system files (shouldn't be hard to make..) but ive found none with that option and im not sure how i would install it without adb...
What i CAN do
1. ENTER USB MODE (that has to count for something so Developers Please help me)
2. I can play with the motoblur intro screen to some degree to make it go away, then a blank black home menu appears. If i wait a while for the popups to stop at the motoblur screen, i follow the instructions but it gets stuck at registering a new account or existing one since you need network access.
3. ENTER REVOVERY MODE (but the only option that looks helpful is the sdcard update which gave me an error...) I havent tried the wipe data/factory reset because the factory reset doesnt touch the build.prop so its pointless
WHat should I do? WHoever sees this please give me advice or direct me somewhere to get it... THANK YOU
[EDIT]
BTW what i was trying to do on the build.prop was replace this line (ro.build.fingerprint=generic/sdk/generic:3.2/HTJ85B/140714:eng/test-keys)
with (ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys)
but i messd up and put
(ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/rel)
youll see this in the attachments...what this does is unlock my 1.5 firmware market to ALL the apps (updating to the official 2.1 using recovery wouldve handled this but i didnt even know of this update till after my mistake)
I just thought id mention...
if you have adb abilities you can push the old build.prop. If you do not know a out this then post back and I will help you.You said you can enter recovery, but that is stock original recovery that anyone can get access to. If you ever bootstrapped your phone you can try pull the battery out, wait about 10 seconds, then plug your phone charger in without the battery in. If your bootstrappped this will pull you into a more advanced recovery mode. The last option is to use rsd lite to flash an sbf to your phone if nothing else works. If you have never done this just look up sbfing motor cliq to stock.
Good luck, and remember to thank me if this helped
SOLVED!!
I fixed my phone on my own but THANKS to rootfan for being the first to answer.
HERES HOW:
I was able to access recovery mode and from there i discovered the sd update option.
It took hours of research and work but i learned alot about adb,motorola, cliq, etc.
Anyway, i originally found the Blur_Version.2.1.5.MB200.T-Mobile.en.US.zip and i tried to put that in my sd card (i could get into it from the phone) but when i tried to update using recovery it gave me an error so i decided to try the "latest 1.5 with Blur 1.6.1" which was actually very hard to find... you can get it here
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/downgrade-to-cupcake .html
Lastly, i put that on my sd as update.zip, went into recover, and the update was SUCCESSFUL! MY PHONE REBOOTED AND NOW IS ACTING NORMAL AGAIN. Now, im trying to update to the Android™ 2.1 (Eclair):
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/2-1_index. html
but im still getting that error whether i update using recovery or the settings/about phone/system update option... Thats strange but my phone is still working normally and ill find a way to update to 2.1...
ONCE AGAIN THANKS TO ROOTFAN AND HOPEFULLY THIS POST WILL WORK FOR SOMEONE ELSE WHO MAY BE HALF-BRICKED (no adb, no usb debug, no root explorer) THERS STILL HOPE IN RECOVERY+USB DRIVE+BLUR VERSION SOFTWARES
Thanks man, now this is probabaly a redicilous reply, since im sure you would have already tried this, but you can try going into settings, about phone, and click on update and see if the 2.1 eclair ota update will work on your phone.
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
stepph said:
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
Click to expand...
Click to collapse
You can reflash a stock rom back if you wanna get it done easily - or even a updated gingerbread one from samfirmware.com
Search for S5570 in these fora for some guides
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video
parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it
parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Tonymhoffman said:
Ok, I'm an idiot. A big one.
I was looking to flash back to stock after using some lollipop roms. I was using TK's toolbox which was an extremely handy utility but in the peak of my madness, I hit lock bootloader with TWRP still installed.
Since hitting lock bootloader i'm not stuck with TWRP and it's crippled my phone since the current ROM no longer seems to be fully functional...I can't seem to download anything else from the web. Everything seems to fail.
I've tried fastboot oem unlock and it goes through the process that appears to be successful but it just boots back into TWRP and it's not unlocked. Does anyone have any suggestions or do I have a $300 paper weight. haha
Click to expand...
Click to collapse
Believe it or not, I have the same problem since yesterday. Its driving me mad since I'm no expert on rooting/unlocking
Phone gets detected by PC and by the toolbox but I can not unlock my phone again.
I am now stuck with TWRP and the only rom I can flash is Slimkat, all the others fail. If I hit unlock bootloader in the toolbox it goes through the process (fast) and it gives no error, boots back up to TWRP and thats it, but it is still locked
I just want it back locked and stocl CM11
Firstly, don't use toolkits. They are often the cause of issues.
Follow this thread to solve your problem: http://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
PewLaserBeam said:
Fixed it!
Solution: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Click to expand...
Click to collapse
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Tonymhoffman said:
Damn you're lucky!
I'm having more issues because my phone won't let me download anything. It's like there is no SD card detected. I can't get that file onto my phone to flash it. Any ideas how I can do it?
I have ADB enabled and it shows up in my devices but it won't respond to adb sideload oneplusone-bootunlocker.zip
It responds to fastboot commands.. it just won't let me download anything off the net onto the device. IT will however update phone apps.. It's so damn frustrating.
Click to expand...
Click to collapse
I had this yesterday + I kept getting the message 'No OS installed'. Since it was already half 'broken', out of frustration I clicked everything and used all sorts of commands I could find (not the best idea I know :angel untill my PC detected the internal memory and then I downloaded 6-7 roms just to be sure. Slimkat was the only one without a fail.
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Adb sideload did the fix for me after a while.
But it looks loke you have another problem.
Tonymhoffman said:
How did you get the files over to your phone then if it wouldn't let you send them to it?
I finally got my internal memory to show up by mounting the system in the TWRP recovery.. But still getting an error that the device stopped responding or is disconnected.. However, it will let me open and view any file on the system, it just won't let me write to it.
Click to expand...
Click to collapse
Instead of trying to sideload the unlocker zip have you tried using the adb push command?
Timma
Thanks for the reply. The solution for me was to mount the phone in TWRP. This allowed my SD card to be explored in Windows. However, it still would not allow me to copy files to the main directory and just out of frustration I quickly drag and dropped a PDF file that landed on a folder in the SD directory and it worked. Haha. So I then tried to copy the file inside another folder instead of the main directory. Success. What a headache and big ass mistake I'll never make again.
Note to self. Do not lock the bootloader with a custom recovery still installed. Ever.