Related
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
swampy67 said:
I was trying to re-install stock apps that i deleted in order to get the OTA update, but in the process i accidentally deleted some thing i shouldn't have(no idea what it was). I had previously been running the odex optimized apps and framework by dc13, and after copying the stock apps to the system/app folder i attempted to delete all of the .odex files. this is where i accidentally deleted some thing essential. i rebooted and was face to face with boot loop. been there ever since please help, i dont want to be stuck with an expensive brick!
Click to expand...
Click to collapse
Would someone (aka moderator) simply sticky a bold
DO NOT REMOVE ANY FACTORY FILES, u goty plenty of room.......
to prevent this kinda stuff
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
dr1337 said:
Reinstall your system by using this file -
http://www.filesonic.com/file/958397621/acer_a500_0.000.00_1.122.01_emea_gen5_update.zip.html
Click to expand...
Click to collapse
but how do i reinstall when im stuck in a boot loop? is there some way to execute adb?
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
anubis13 said:
Rename the file Update.Zip, put the file on the root folder of your SDcard. Power on the tablet with the volume down button held
Click to expand...
Click to collapse
Thanks I'll give it a shot
Sent from my PC36100 using XDA Premium App
thanks this worked like a charm. Gotta love the XDA community.
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Chaz36 said:
A strange thing happened to me, i was working with the tab, and layed it
aside for a while, suddenly it shutted down, and rebooted.
(Not sure where i went wrong, or why this happened,cant remember doin anything out of the ordinairy)
Then i got stuck in this bootloop.
Tried to update, wich goes okee i guess, but after the reboot, i got stuck in a
different boot loop.
Im sure i didnt mess with the standard files that came with the device,
however i have another bootanimation, than stock, could this be causing the "second"
bootloop?
Kinda out of options now, hope you guys can shed more light to this, but i think
i have to return it to Acer for repairs.
Btw: great device anyway!
Click to expand...
Click to collapse
Okay so this is what i did as directed by the guys above.
1. Download this file. have to warn you though this service is horribly slow http://api.viglink.com/api/click?fo...ww.filesonic.com/file/958397...pdate.zip.html
2. Put your external SD card into your computer, and copy over the file to the root of the card.
3. Rename the file update.zip(make sure it isn't named update.zip.zip)
4. Put the SD card back it the tab.
5. Make sure your tab is completely shut down.
6. Hold down the volume down button and press the power button.( dont let go of the volume down button till the screen turns on)
7. The recovery will boot and the update should hopefully restore your tab.
8.(optional but recommended) follow these steps in order to revert back to the latest OTA american version so that your able to upgrade to 3.1 when it comes out.http://forum.xda-developers.com/showthread.php?t=1101859
Hope this helps.
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Chaz36 said:
Thanks for quick reply, i did exactly those steps before, and it seems that the
update goes well, then after the update, the tablet reboots loads up a bit, and then
again runs into a bootloop.
That is what is different in comparison with the un brick methods come-out, i read all over this forum.
So im a little affraid something different is goin on, with or in my tablet after the update completes.
It just never really recovers from the boot loop with or without the update.
sadly.
Click to expand...
Click to collapse
Well sorry that didn't work, i am not to experienced with development for this tab, so im fresh out of ideas. It might help to start a new thread explaining that you tried to un-brick your tab via this method and that a boot loop still occurs. Maybe some super smart devs can help you.
Crsdr37 said:
Just want to let you know that was not the correct update.zip for our Country you make consider going back to the USA rom. Or you will not receive the Correct Updates. If any at all. These are the files and instructions you will need to get back to stock and be able to receive all updates.
http://forum.xda-developers.com/showthread.php?t=1101859
Give thanks and support if this helps.
Click to expand...
Click to collapse
yeah i did that right after i un-bricked it, but thanks for the heads up anyways.
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
SmittyRN said:
For anyone else who has bootloop problems and finds his/her way to this thread, there is another option. Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state. You will lose root and all of your info, but you have your tab working again. There really should be a way to do this without adding a keyboard, but it works fine.
Click to expand...
Click to collapse
Dude, you just made my day.
Thanks.!!!!!
I was having problems yesterday, I though my KF was bricked. I got some help and I got my phone to start again. But for some reason even after following this thread http://forum.xda-developers.com/showpost.php?p=19552626&postcount=1 my KF was still rooted when everything was over. I don't know why it was still rooted but when I tried to root it again, SuperOneClick said "Are you sure you want to root, you are all ready rooted".
Anyways I installed Root Explorer, it worked, so I guess I still had root. So now I wanted to install the Android Market. But first I wanted to switch Launcher because I have to anyways in the end.
I installed GoLauncher (GO_Launcher_EX_HDTest_V2.69Beta.apk) from their website. After installation, my KF seemed to lag, almost become unresponsive. Then a popup appear telling me to pick eithier the Amazon Launcher or GoLauncher. I picked GoLauncher and my KF wouldn't turn back on. I have to press the Power button a few times really fast to get back to the Lock Screen. Once I'm their I'll slide the lock arrow across and my screen just shuts off, my KF doesn't power off, just the screen. I turned my phone off for 20 seconds, restarted and back into bootloop with that Kindle Fire splash screen. I cant say for sure that it is GoLauncher but the first time my KF boot looped it was after I installed it and the 2nd time happened immediately after GoLauncher was installed.
I really don't know what I'm doing wrong or missing? Am I using the wrong version of GoLauncher or am I missing a step? Right now I'm following the "Unbricking" guide again to get my KF to work.
EDIT: I just followed steps 1-6 from the Unbricking guide and my KF is working again, but like I said for some reason I still have root. If I can't figure out what I'm having launcher trouble I'm just going to unroot I guess.
Try version 2.68
Droidanian said:
Try version 2.68
Click to expand...
Click to collapse
Does it need to be installed in any certain way? Once installed how do I switch from stock to GoLauncher?
Just install it the normal way and choose "Open" once the installation is complete.
Kinda sounds like HD test version of the launcher was too much. I think go launcher has a failsafe style thing where when it becomes too much for the device, the choose launcher option pops up but...you choose go launcher again anyway lol. You probably weren't bricked or anything like that, actually what it sounds like is the launcher was malfunctioning or eating up all the resources causing the device to become unresponsive. Did you restore your kindle already? If not, a few adb commands could probably get you out of the situation
foxdog66 said:
Kinda sounds like HD test version of the launcher was too much. I think go launcher has a failsafe style thing where when it becomes too much for the device, the choose launcher option pops up but...you choose go launcher again anyway lol. You probably weren't bricked or anything like that, actually what it sounds like is the launcher was malfunctioning or eating up all the resources causing the device to become unresponsive. Did you restore your kindle already? If not, a few adb commands could probably get you out of the situation
Click to expand...
Click to collapse
yeah i had to use fast boot and what not to get the kindle back on, but once i did i just installed golauncher 2.68 the latest stable one and everything works except sometimes widgets will say i dont have any space left but i have plenty.
i guess like you said that HD golauncher was just too much and was messing my KF up.
As mentioned to you already in the unbrick thread, you still have root after the fix because it doesn't remove the system partition. Why not just leave it stock until these types of things are more stable. You might get yourself into trouble where my guide will not help you anymore.
ubeezee said:
As mentioned to you already in the unbrick thread, you still have root after the fix because it doesn't remove the system partition. Why not just leave it stock until these types of things are more stable. You might get yourself into trouble where my guide will not help you anymore.
Click to expand...
Click to collapse
If he bricks it again, good luck getting help from anyone, period. It's obviously your choice what you do with your device, but it does not mean I or ubeezee (we work together to solve the questions) or anyone else will help you to undo it. However, Amazon seems to be willing to forgive him so I guess he can still go that route.
I told you why your device is still "rooted," do you not listen? Not listening/reading is probably why you ended up in the predicament you were in. You don't read and you don't listen to what people say when you ask questions.
Accidents are forgivable...blatantly doing something you know will probably screw your device up (after you already screwed it up once by doing so) is not so much.
I was happy that I rooted the phone and got Japanese fonts working.. but I wanted the ability to adjust the gain/volume of my mic headset and tried to install a rom to do that. I used the Nexus Root Toolkit to root the phone and do an entire backup. Then I flashed the rom. It didn't take and I really had no idea why (being noob). So I go on youtube and see what i can find for flashing a rom. I see that you have to delete your old OS in order to install the new one.. ok.. risky but I did a full backup right? Well when I tried using Nexus Root Toolkit to install said rom the phone ended up with a screen with a menu with some options including to delete the OS. So I did that. Then I tried to install the zip file which was now on the phone thanks to Nexus Root Toolkit.. but it still didn't take. Okay. I gave up. I rebooted.
But I have no OS. And my Win7 machine can't see the phone. I tried deleting and installing drivers again and it doesn't work. I can boot to the fastboot screen (the one with the Start at the top and cycle through options like recovery mode). But the computer can't see the phone. Nexus Root Toolkit seems to be of the opinion that I need to enable USB tether debugging mode on the phone.. but there's OS to do that.
Is it hopeless?
btw I think this phone is great. I would prefer maybe a slightly smaller phone but i can't believe how cheap it is, beautiful screen, fast, responsive. Amazing.
Flash the stock image, comprehend what you are doing while you flash the images, and never use a toolkit again.
Here's all the info you need. http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 10 using xda premium
Sorry i accidentally clicked your thanks button. If you have a recovery installed then just flash a rom.
windows 7 can't recognize the device now
Thanks very much for the reply. I still am thinking it's hopeless... I followed your link and I'm attempting to follow the directions...but here's where the problem is. And basically why the toolkit can't help me either.. (I agree it's better to understand all steps and yet I'm lazy..)
Attempting to install drivers for Nexus 4...
*** cut and pasted from OEM USB Drivers install guide **
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
***********
The phone doesn't exist in device manager. Perhaps its lack of an OS keeps windows from realizing what the heck it is?
Do you have a custom recovery installed?
no custom recovery
chromium96 said:
Do you have a custom recovery installed?
Click to expand...
Click to collapse
Not on purpose. So probably not. Actually I doubt it. I am looking at Nexus Root Toolkit and I see the checkbox for Custom Recovery and I know I did not check it when I rooted.
soft brick?
The computer does acknowledge the device to the extent that it installs Android ADB (if memory serves which who knows).. but otherwise it doesn't know it's a Nexus 4. It thinks it's an MTP USB Device.
I am playing with Nexus Root Toolkit a bit (it did do the backup of the phone afterall... ) and it apparently flashed the stock kernel.. that's the 1st thing I've been able to do to between the phone and the computer. Now Toolkit is telling me to wait 7 minutes before assuming soft brick.
I am thinking it is soft bricked? gonna wait a few more minutes.
well I ignored the lack of nexus 4 drivers...
and just followed all the directions anyway for the command line install. When you go to the LGE website to get drivers.. you don't find any. At least I couldn't. Just manuals to download. But I got success messages all along and it rebooted when I told it to and stuff.. but it's just sitting at google. It isn't going past the google screen. The computer calls it an MTP USB device with a big exclamation point next to it.
clockword recovery
I might have it. It might have been installed when I did my full backup perhaps. If it's the reclining robot with a red triangle and an exclamation point then yes. I can wipe cache, wipe data/factory reset, and apply update from ADB, or reboot. I've wiped the cache and done a factory reset... I'm gonna try:
Default [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Again.
And hope.
It's a new phone so I am still within the 14 days they give to return it.. of course if it's a brick when they get it back... heh. Okay it's a 100% brick it does turn on just not boot up...
it works omg
El Daddy said:
Flash the stock image, comprehend what you are doing while you flash the images, and never use a toolkit again.
Here's all the info you need. http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Well 2nd time through was the charm.. and not worrying about nexus drivers too much.
Thank you very much for the link. I can't say I really understand everything more but I am happy that I seemed to have killed the phone in the worst way and yet still got it working.
I was going to go back to the iPhone 5 (and lose a lot of money haha). I'm glad this one is working. I genuinely like it more than the iPhone and I save several hundred dollars.
If anyone's googling in a similar situation.. what I did the 2nd time through was use recovery mode on the phone to restore factory default and clear the cache. Then I did all the steps outlined in the above link again. I think that if it doesn't work the first time it's worth doing it again carefully.. and maybe a third time if needed. Wow. It works XD.
kraemder said:
Well 2nd time through was the charm.. and not worrying about nexus drivers too much.
Thank you very much for the link. I can't say I really understand everything more but I am happy that I seemed to have killed the phone in the worst way and yet still got it working.
I was going to go back to the iPhone 5 (and lose a lot of money haha). I'm glad this one is working. I genuinely like it more than the iPhone and I save several hundred dollars.
If anyone's googling in a similar situation.. what I did the 2nd time through was use recovery mode on the phone to restore factory default and clear the cache. Then I did all the steps outlined in the above link again. I think that if it doesn't work the first time it's worth doing it again carefully.. and maybe a third time if needed. Wow. It works XD.
Click to expand...
Click to collapse
Awesome! Glad you figured it out. Sorry I wasn't around to help you through it. I was out and about this evening.
Thanks for the beer, I appreciate it!
I found the solution.
Really pisses me off that it was this simple.
Turn on your phone into bootloader
Leave it on bootloader until the battery drains 100%
You can tell it is drained when the phone looks like it is bricked and when you plug it in a red light shows on the notification light
Let it charge for ten minutes
Boot the phone
It should boot. Yeah. Seriously.
It looks like a battery fault of some sort. Welcome
YFBanana said:
So two days ago my Nexus 4 died, and i charged it back up. When I tried to turn it on, it would go to my boot screen, but it would bootloop for 5 minutes, and then restart. This never happened before even the other two times my phone died. I have tried doing a lot of things including switching PA for CM11, and getting stock everything from google. Everything goes succesfully, but again, for every different boot logo, it does the same thing. It really pisses me off beacuse i cant find anyone else with a similar problem, so i dont know what to do.. Also, since the thing cant boot, i cant even turn it back in to tmobile, because it is unlocked and they don't help with anything unlocked... any help would be appreciated Also, if i need to proivide more info on the software i can
Click to expand...
Click to collapse
Did you try to wipe Dalvik Cache & Cache in recovery after flashing back to stock?
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google https://developers.google.com/android/nexus/images#occam
It's the best way.
Click to expand...
Click to collapse
+1. And if that doesn't work and you have a hardware issue, boot into fastboot and use
fastboot oem lock
That'll lock the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Konstantinos said:
If the above doesn't work then do this:
Boot into recovery(go to bootloader(vol. down+power) and select recovery). Use "adb pull /sdcard/the_folder_goes_here/and_so_on.jpg" to pull whatever you want to backup(pics, music etc) and flash stock ROM from Google
It's the best way.
Click to expand...
Click to collapse
Well yeah, but flashing the stock rom just left me with a bootloop, just with those 4 rings..
boot into recovery, see if your computer detect your phone as android device, try use minimal adb and fastboot, it happen to me once, and success to fix it. if it cant fix it, try use nexus root toolkit, the tools here on xda nexus 4 forum. choose back to stock, and dont forget to choose current status as soft-bricked/bootloop. let me know how it goes.. we'll figure it out
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Update. I somehow managed to get it up and running on factory version 4.3 but I flashed/ used an older radio.img "cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48.img" got it from here
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
and by using this method "[URL="http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312]http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312[/URL]
Many thanks to all the good ppl on here
Kdom81 said:
HELP ME PLEASE.
I have the same issue where no matter which factory ROM i install using soft bricked option, or fastboot my Google Nexus 4 will not get past the black screen with the four circular colours which come together to form a white circle then repeat.
I know the proximity sensor is defective since it is broken and I am wondering if this could be the problem?
What else can I try?
Could a custom ROM be a solution?
Click to expand...
Click to collapse
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
YFBanana said:
Seems like nothing at all is working, this is really dumb, im gonna try to install 4.2.2 instead of 4.4, but i think it is a hardware problem and i have to buy a new phone....
Click to expand...
Click to collapse
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
I fixed it, and had it fixed for maybe 4 months, but now it is back in a bootloop. What i did to fix it the first time beats me, i just randomly flashed 4.4 roms, and it booted once. I used adb sideload for some stuff, but i am gonna keep trying.
Kdom81 said:
Gday again, just curious as to how you went with going back to android 4.2.2. Is your phone back in action? I was stoked when mine worked again, even though it took me 12 hrs to make it happen lol.
This might be helpful, was for me. http://forum.xda-developers.com/nexus-4/help/nexus-4-bootloop-official-4-3-ota-t2595057
Click to expand...
Click to collapse
I cant even boot in 4.2.2...
I hate this so much.
Also, i just rebooted my phone and i got this loop again.
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
YFBanana said:
Does anyone know what to do? There has to be a way to get a phone out of a soft brick..
Click to expand...
Click to collapse
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
I am gonna try this now, i just hope it doesnt ruin my phone even more lol
22sl22 said:
If you guys have already tried a normal reset using the guides posted them maybe this will help :good:
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Sent from my Note 10.1 2014
Click to expand...
Click to collapse
There is a problem, seems like the lg drivers are not compatible with windows 8.1...
Found a fix, check the forum page
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Added video of issue:
https://www.youtube.com/watch?v=M_mncUueCJ8
Edit: Solved the issue through the most scientific methods; insanity and brute force! The phone would boot sometimes with the lock screen in the rotation, and those boots allowed me a brief window of touch interaction which I used to enable emergency mode, which fixed my immediate problem of being locked out and allowed me into an adb root shell. Hurrah.
Thanks all,
Overkill
OverkillSD said:
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Click to expand...
Click to collapse
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Chopstix9 said:
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
Already in progress But the stock tar also flashes over any user data, correct?
OverkillSD said:
Already in progress But the stock tar also flashes over any user data, correct?
Click to expand...
Click to collapse
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Chopstix9 said:
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Click to expand...
Click to collapse
Right The problem is, there are files I need to get from the device before I do that!
OverkillSD said:
does anybody have a suggestion that would allow me to get the data off the internal storage before wiping?
Click to expand...
Click to collapse
OverkillSD said:
Right The problem is, there are files I need to get from the device before I do that!
Click to expand...
Click to collapse
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Chopstix9 said:
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Click to expand...
Click to collapse
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
OverkillSD said:
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
Click to expand...
Click to collapse
I wasn't able to do this, presumably because com.android.systemui is responsible for this dialog and when it restarts, the problem restarts with it.
what's strange is that i can see my device on windows but the internal storage doesn't mount when the device shows up >.<
would i be able to flash just the systemui.apk and framwork.res files to stock using odin?
EDIT: Was able to get the device into emergency mode after much spamming of buttons and trial/error; this stops the problem I'm having, and I was able to get into ADB. The problem is most likely with Xposed, I'll be able to troubleshoot from here =) Basically, I had a brief window of laggy but responsive touchscreen interaction once out of every 10 boots which I used to get emergency mode enabled (lots of checkboxes) and this worked. It was either xposed or nova or a combination of the two, but it appears that I'm able to hack at it from here xD