Develop Bugs

[Q] Advanced Ace Hack Kit issue

Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks

anomander0108 said:
Earlier today, I ran the updated 15/10/11 version of the ace hack kit. Like it was suggested, I read through the manual then I re-read it and re-read it again. As suggested, I disabled / uninstalled all security software on my pc and the other superfluous services. Ran the executable drivers file then I set the phone to charge only and usb debugging was ticked.
I then ran the hack-ace.cmd file as administrator and let the program do it's thing.
It appeared to have completed without any glitches in the suggested 6 minutes.
However, on the phone, all was not well. Since running this, the screen remains blank. When I power on, I get the HTC logo and then it disappears / disintegrates into a blank screen and nothing happens.
The only reason I ran this was to get rid of the irritating apps that I never use but have to Kill every day.
Can anyone help to overcome this problem? This was a replacement handset that I had to fight with my insurance company to get only for this to happen.
I am literaly at my wits end.
Thanks
Click to expand...
Click to collapse
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..

avnr said:
i think you need to install custom rom and flash it in recovery follow the steps in instruction in ace hack kit because it happen to me also when I ran the ace hack kit..
Click to expand...
Click to collapse
Yes this is the best thing to do. Something must have corrupted your stock ROM. If AAHK completed properly, then you should have ClockworkMod recovery installed.
The first thing I did was install 4EXT recovery but thats not necessary, that was just a personal choice.
So these are the steps you should take:
1: Download a new ROM and put it on your SD card in a convenient place (I recommend the RCMIX32 Runny 3.1 ROM)
2: Remove the battery and reinsert the battery
3: Hold down the volume down button and then hold down the power button. You will get to a white screen with some green robots on the bottom. This is the bootloader screen. You will have to wait a bit for it to finish scanning the SD card. It will tell you when it is finished
4: Use the volume buttons to select recovery and press the power button to select it
5: After a few seconds the recovery environment will appear
6: Go to the wipe menu. Wipe data, cache and dalvik cache (and system if you have the option. I havent used Clockworkmod in a while so I cant really remember what options you have there)
7: Go a few menu's back and select Install zip from SD card
8: Select the zip file
9: Press yes on the confirmation screen
10: When it is finished, click reboot now. It might be on the menu back
This will install a new ROM and it should work properly. If you have any problems along the way just say and we will help to the best of our ability

Thanks for the responses.
I don't think ClockworkMod is installed as there are no options available when I select recovery. It just reboots the device back to the HTC splash screen which as mentioned then fades / deteriorates to a black screen. I had tried the Android HD Revolution rom but no difference.
One thing I did yesterday in my panic was to select 'Factory reset'. Will this have usb debugging setting?
Finally, when I connect to a pc, it doesn't see it. Is this because it's still set on charge only mode?
I'm probably my own worst enemy

If you finally press "Factory reset" you will reset USB debugging, then you can't root your phone using this tools kit. Try to reinstall the stock rom.
If you didn't root your DHD. Phone may still under warranty.

Hi Guys
I've managed to get this back up and running again.
After a lot of playing about with various file downloads last night, I finally managed to get my pc to see the phone. After that, I just downloaded a stock rom and installed it.
After this fright, I am reluctantly going to stick with this and not bother with rooting / custom roms.
Anyway, many thanks for all your responses, I really appreciate the time you took to helpo me out.
This forum absolutely rocks.

Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!

Hi juicyp
juicyp said:
Hi,
I've just downloaded, I read the 'effen' manual and then ran ace-hack, it seems to have worked except I can't see clockwork mod recovery?
I can see superuser and ROMmanager, is it still ok to try and download and flash a custom ROM?
---------- Post added at 09:46 PM ---------- Previous post was at 09:03 PM ----------
Well to confirm my noob status I have now found that clockwork mod recovery is indeed installed (I assume you're not meant to be able to see it as an app as it sits at a lower level).
I downloaded the CM7 ROM, so have booted up into recovery mode, have wiped/formatted as instructed but when I choose the zip file from SD card it appears to start then aborts installation...help!!!!
Click to expand...
Click to collapse
Did you check the MD5 Checksum of the .zip before you copied it to your SD Card? as it might is some way have got corrupted.
Here is a link to what I always use before I copy anything to my SD Card or install on my OS System:- MD5 Check 2.1.
Take Care
TheQuest

Thanks!
I'm all sorted (I think, fingers crossed).
It was principally because of the mac unzipping (Safari preferences not checked), this was the original and prime fault.
That caused me to doubt my partitions on the SD card (google is sometimes your enemy) which I altered.
So what then happened was CM7 installed but upon reboot looped continuously on the android skateboarding screen.
I finally resorted to formatting the SD Card, reapplying the CM7 zip and the google zips and so far it looks good.
Of course I (me and me alone) has stuffed up all the user data I had on the SD card. I might try to recover some photos but stuff like contacts I can regenerate no major loss there.
Thanks for replying!!

CM7 - the experience thus far
Well its 72 hours since I took the plunge!
Initially it looked odd and felt flakey, the Market refused to download 80% of the apps I tried. I resolved this (not sure if it was the right way) by going into recovery and clearing the cache 2-3 times and eventually downloaded all of my old apps.
Some apps cause frequent force-closes, I assume because they've not been updated for Gingerbread? Thats a very minor irritant, I can easily live without these apps anyway.
Battery life hasn't noticeably altered yet but I suppose I have been constantly been tinkering, playing with settings, trying wifi (seems a little less sensitive to signals) and gauging how the radio is working - I seem to get HSPDA a lot less and resort to 3G more than I previously did?
So, done it, like it despite some minor reservations - now what, is there anything else I can do to improve the experience?
I must add one thing this has shown me - I really really know very little about what goes on under the hood. Despite 20+ years experience in CIS this is a very different world and all credit to those who have developed CM7!!

Please help if you can.. please
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.

ravennyc said:
Hello!!
I am desperately seeking some guidance. Please.
So, I used to have a HTC Inspire 4G and in June I rooted it successfully.. then installed Cyanogenmod 7 etc.. everything worked great. I unfortunately lost the phone and because of insurance got a new one.
When I rooted the first time I used the old school method that was in the XDA forum.. ADB..etc.. but today... with the new replacement..
I downloaded Advance ace hack kit 29102011 (ahhk 29102011.zip) which after reading all the stuff I thought would be just a quicker way to get rooted. I used the same PC that I used before.
This time, unfortunately I am getting a black screen, right after the HTC splash screen shows up.. it fades to black.
I can get to the "Hboot" screen but removing the battery, then restarting by holding the power and the down vol button.
Tried Factory reset.. still fades to back
Tried Recovery .. still fades to back
The device will not be recognized on my laptop when connected to USB..
Am I stuck? Do I have any options?
I should have done what I did before.. but am at a loss right now.. will you please help me.
Please.
Thanks a million in advance for your responses.
Please help.
Click to expand...
Click to collapse
Try to run the latest RUU.

Similar Issue
Hi all,
Similar issue as the thread, during AAHK had a "file not found" issue and now, only get HTC screen fading to black. Getting into HBOOT works fine.
I do have S-OFF but;
Have tried recovery, nothing.
Any RUU nothing
ADB shows device is offline
running any other option in AAHK device offline
Any help would be greatly appreciated.
Cheers!

[Q] LG Optimus G Stuck On LG Screen Need Help.

I was making a TWRP Backup when all of the sudden my phone just randomly turns off. I grabed my phone and it was really hot. Tried turning it on, but nothing happened. Then I connected it to the ac adapter and it turned on, but it would go to the LG logo, the screen turns black then it restarts. This does not stop unless I unplug it. I had previously made two backups before and nothing like this happened, but this time I enabled conpression<-------- This must have been what caused this. All I want to know is if this can be fixed or not. If it could be fixed I would be so happy if somone could tell me how to fix this. THANK YOU. P.S. THIS PHONE IS A BEAST. D

cgtrr34 said:
I was making a TWRP Backup when all of the sudden my phone just randomly turns off. I grabed my phone and it was really hot. Tried turning it on, but nothing happened. Then I connected it to the ac adapter and it turned on, but it would go to the LG logo, the screen turns black then it restarts. This does not stop unless I unplug it. I had previously made two backups before and nothing like this happened, but this time I enabled conpression<-------- This must have been what caused this. All I want to know is if this can be fixed or not. If it could be fixed I would be so happy if somone could tell me how to fix this. THANK YOU. P.S. THIS PHONE IS A BEAST. D
Click to expand...
Click to collapse
Can you boot into recovery and restore a previous backup?
Sent from my LG-LS970 using Tapatalk 2

cowfodder said:
Can you boot into recovery and restore a previous backup?
Sent from my LG-LS970 using Tapatalk 2
Click to expand...
Click to collapse
It does not let me go into recovery, the screen goes black then restarts. All I can do is go into fastboot and Download mode.

cgtrr34 said:
It does not let me go into recovery, the screen goes black then restarts. All I can do is go into fastboot and Download mode.
Click to expand...
Click to collapse
Likely bricked. Do you have flashing notification and capacitive lights? Have you LGNPST'd? If yes to both of those questions, you're in the same predicament as I was and hopefully you have insurance, because your phone is fried.

xboxfanj said:
Likely bricked. Do you have flashing notification and capacitive lights? Have you LGNPST'd? If yes to both of those questions, you're in the same predicament as I was and hopefully you have insurance, because your phone is fried.
Click to expand...
Click to collapse
I do have flashing notification and capacitive lights. But I don't know what LGNPST is.(sorry I'm new to this) this is my first android phone

cgtrr34 said:
I do have flashing notification and capacitive lights. But I don't know what LGNPST is.(sorry I'm new to this) this is my first android phone
Click to expand...
Click to collapse
Sounds like you are toast. Take it to Sprint and have em swap it out for ya. Hopefully you either have insurance or are within your 14-days to return it.

xboxfanj said:
Sounds like you are toast. Take it to Sprint and have em swap it out for ya. Hopefully you either have insurance or are within your 14-days to return it.
Click to expand...
Click to collapse
Will they swap a rooted and unlocked phone?

cgtrr34 said:
Will they swap a rooted and unlocked phone?
Click to expand...
Click to collapse
Sprint's policy on root is to document it but not do anything about it, so they would swap it. If you're worried, I can help you restore stock firmware.

xboxfanj said:
Sprint's policy on root is to document it but not do anything about it, so they would swap it. If you're worried, I can help you restore stock firmware.
Click to expand...
Click to collapse
How could I restore it to stock firmware. And also thank you for replying back and helping me out

cgtrr34 said:
How could I restore it to stock firmware. And also thank you for replying back and helping me out
Click to expand...
Click to collapse
I will PM you about that since it is against forum rules and perhaps laws to post copyrighted stuff here.

xboxfanj said:
I will PM you about that since it is against forum rules and perhaps laws to post copyrighted stuff here.
Click to expand...
Click to collapse
OK thank You so much!

cgtrr34 said:
I was making a TWRP Backup when all of the sudden my phone just randomly turns off. I grabed my phone and it was really hot. Tried turning it on, but nothing happened. Then I connected it to the ac adapter and it turned on, but it would go to the LG logo, the screen turns black then it restarts. This does not stop unless I unplug it. I had previously made two backups before and nothing like this happened, but this time I enabled conpression<-------- This must have been what caused this. All I want to know is if this can be fixed or not. If it could be fixed I would be so happy if somone could tell me how to fix this. THANK YOU. P.S. THIS PHONE IS A BEAST. D
Click to expand...
Click to collapse
WTF!!!!! I just bricked my phone in less then 24 hours of owning it. I just rooted and unlocked it and right after making a TWRP Backup and rebooting my phone wouldn't turn on and it was HOT AS HELL!!
I got it exchanged at Best Buy but now im scared to do anything with it.

shook187 said:
WTF!!!!! I just bricked my phone in less then 24 hours of owning it. I just rooted and unlocked it and right after making a TWRP Backup and rebooting my phone wouldn't turn on and it was HOT AS HELL!!
I got it exchanged at Best Buy but now im scared to do anything with it.
Click to expand...
Click to collapse
Same happened to me. The phone overheats in recovery, so do what you need to do and then get out of it.

xboxfanj said:
Same happened to me. The phone overheats in recovery, so do what you need to do and then get out of it.
Click to expand...
Click to collapse
Im on the new phone and Im using clockwork and all is fine so far. I definitely suggest guys stop using twrp.
Sent from my LG-LS970 using XDA Premium HD app

Restore to stock when stuck at LG logo screen
xboxfanj said:
I will PM you about that since it is against forum rules and perhaps laws to post copyrighted stuff here.
Click to expand...
Click to collapse
Would you please help me out to restore to stock from a stuck LG logo screen? I can't even boot into fastboot or recovery. I tried LGNPST number of tries with different .bin files with no luck. I also tried a lot of diff things, too. Please email me at [email protected]. Thank you very much!

phatjulie said:
Would you please help me out to restore to stock from a stuck LG logo screen? I can't even boot into fastboot or recovery. I tried LGNPST number of tries with different .bin files with no luck. I also tried a lot of diff things, too. Please email me at [email protected]. Thank you very much!
Click to expand...
Click to collapse
I suggest you TEP it.
Sent from my LG-LS970 using xda premium

phatjulie said:
Would you please help me out to restore to stock from a stuck LG logo screen? I can't even boot into fastboot or recovery. I tried LGNPST number of tries with different .bin files with no luck. I also tried a lot of diff things, too. Please email me at [email protected]. Thank you very much!
Click to expand...
Click to collapse
Pull battery using a torx t5 screwdriver and phillips #00 if you don't have insurance.

xboxfanj said:
Pull battery using a torx t5 screwdriver and phillips #00 if you don't have insurance.
Click to expand...
Click to collapse
What's the purpose of pulling battery out? Just a try? I'm gonna have to get it from Fry's tomorrow and try that first.

phatjulie said:
What's the purpose of pulling battery out? Just a try? I'm gonna have to get it from Fry's tomorrow and try that first.
Click to expand...
Click to collapse
Because your phone doesn't know if it needs to be in charging mode or booting. Pulling battery will fix it.
Sent from my LG-LS970 using xda app-developers app

I had a similar problem as you. Upon getting the phone I rooted and used the FreeGee app from the Google Play store to unlock the bootloader. Everything seemed fine and dandy, until one day when I let my phone's battery drain completely. Pluggin it in to a wall charger resulted in the failed boot where the LG logo flashes before going to a blank, but backlit screen. Luckily, the first few times this happened, through a combination of quickly plugging and unplugging the usb cord and holding the volume up+power button, I could get it into recovery (TWRP). Then a simple cache & dalvik cache wipe, and the phone would boot up as if nothing ever happened. Very strange.
Well yesterday this happened again, however, this time there was no getting the phone into recovery. My previous methods of button mashing and plugging and unplugging weren't working. So, I decided to bite the bullet and use LGNPST to get back to ZV7. Now, like you mentioned, this failed boot would automatically happen, without pressing the power button to turn it on. So it was difficult to get the phone to stay off. I found that with the phone unplugged, if you continue to press the power button until the blank backlit screen turns off, AND continue to hold the power button for an additional five seconds, the phone would stay off and not auto power on into the failed boot.
Once I was able to get the phone to stay off, I pressed the middle of the volume key to depress both volume up and down, and then plugged a usb cord that was attached to my computer. This powered on the phone into download mode. Following the LGNPST guide I was able to get to around 67% complete before my phone turned off and an error message flashed on the computer screen telling me to power cycle the phone and reconnect. Well, the whole 67%/85% LGNPST failure is apparently common and not indicative of an actual failure; HOWEVER, my phone became completely unresponsive. It wouldn't power on at all. It didn't matter if the usb was unplugged or connected to the computer or wall charger. So, I was forced to unplug the battery. I followed this tutorial and successfully disconnected and reconnected the battery cord, and the phone shot back to life. It even booted up into the factory stock ZV7 rom. I guess that LGNPST was successful. It looked like I was on my way to returning my phone to breezy's deodexed ZV9 stock rom that I was previously running.
I went ahead and re-rooted, ran the FreeGee app again, and rebooted into recovery. Then I made a backup and attempted to flash my new rom. Now, I think this is where I royally screwed up. I was pleasantly surprised to see my screen layout and all of my settings still intact after LGNPST back to ZV7 and thought I could just wipe the caches and ignore the factory reset and system wipe before flashing. Perhaps it was this, but part of me also thinks there might be something wrong with my battery draining extremely fast in recovery.
I proceeded to flash and all seemed good, but rebooting resulted in the LG logo failed boot that we have already discussed. So, I went ahead and repeated the LGNPST-re-root process numerous times (switching to the freegee 0.5 batch file instead of the app). Everytime after the first initial restore, I could never get my phone to enter recovery. As soon as I rebooted after using freegee, the phone would be soft bricked again. Sometimes I would get the LG logo thing, other times I would get the dreaded alternating flashing red notification light and soft keys. A battery pull was usually required in these circumstances before I could get back into download mode to start all over.
I was about ready to give up when I took to the LGOG irc channel. That's when Xboxfanj stepped in and helped me out IMMENSELY. Over the course of several hours, he walked me through flashing some partitions in ADB. At times it seemed like there was no hope and that I should have just returned the phone, but he failed to acquiesce, we pushed forth trying a couple of other bootloader options. The new bootloader appeared to have fixed the phones erratic behavior with powering on and off, but I had no rom to boot into and no recovery. Xboxfanj recommended using fastboot to flash over a recovery. Once in the new bootloader screen my Windows XP machine detected new hardware and wanted some drivers. I attempted to use the [ADB/FB/APX Driver] Universal Naked Driver 0.72, but XP indicated that I was missing 'winusbcoinstaller2.dll'.
I grabbed winusbcoinstaller2.dll from here and all was good. Fastboot recognized the phone, I was able to flash recovery and subsequently boot into recovery. From there I reformatted the system, wiped data/factory restore, wiped cache, wiped dalvik cache, and flashed breezy's ZV9 deodexed rom.
Fortunately, after around 7 hours, I am happy to say my phone is back to being rooted, unlocked, and running ZV9. It powers on and off properly and can get into recovery without a hitch. I'm still curious what will happen if I let my battery drain completely. Perhaps I'll try it some time this week. I'll be sure to post back here if/when I do that. All in all, it was a harrowing, but educational experience.
Anyway, just wanted to give a big THANK YOU to Xboxfanj! You really are the man :good:. Thanks for your patience and determination.

[Q] Screen flickering / Bootloop -> Is my Nexus dead? Data recovery possible?

Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.

Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery

Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?

BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?

Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.

you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.

Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?

BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app

beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.

BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.

beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems

BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link

How do you hard shut down and then get into recovery?

I got stuck at the boot screen with no OS installed.
Google is finding me ways to reboot but can't find anything on how to do a hard shutdown from here.
EDIT:
Okay one suggestion was to plug the phone into charge, then force a reboot (power + both volume buttons held down 10+ seconds).
Then when it shuts off, you disconnect the power cable after seeing a "battery" on the screen and the tab will remain turned off.
That did not work for me with computer data charging cable.
But it did work with the stock charger. :good:
This helped me get into download using the download mode button shortcuts. But I can't figure out how to get into recovery mode from here? The recovery mode buttons don't work (volume up + power + home).

It looks like this thread has the answer on how to get into recovery mode again.
Too bad I didn't find it before I did an ODIN back to stock.
http://forum.xda-developers.com/galaxy-tab-s/help/to-event-soft-brick-disaster-t2838473

Actually its even easier than that and have done it countless times.
Next time just hold POWER +VOL DOWN + HOME. As soon as the screen goes blank change to VOL UP whilst still holding POWER +HOME.
Works every time to get into recovery.

ashyx said:
Actually its even easier than that and have done it countless times.
Next time just hold POWER +VOL DOWN + HOME. As soon as the screen goes blank change to VOL UP whilst still holding POWER +HOME.
Works every time to get into recovery.
Click to expand...
Click to collapse
Confirmed - this worked for me. Thanks!

I'm in the same situation where all of a sudden my tablet went into reboot and got stuck on the logo screen. I tried the combinations suggested such as : Power butto +Volume down then Volume up when screen is black to get to reboot mode but it just brings me back to the logo screen. Is there some other way I can access the safe mode or recovery mode to try and get this thing working again? I wasn't running any apps for it to cause this either, just checking email. Any help would be much appreciated

casual167 said:
I'm in the same situation where all of a sudden my tablet went into reboot and got stuck on the logo screen. I tried the combinations suggested such as : Power butto +Volume down then Volume up when screen is black to get to reboot mode but it just brings me back to the logo screen. Is there some other way I can access the safe mode or recovery mode to try and get this thing working again? I wasn't running any apps for it to cause this either, just checking email. Any help would be much appreciated
Click to expand...
Click to collapse
You're not following the instructions properly. Read post 3 again and hold ALL 3 buttons until recovery boots.
Do not let go of any of the buttons until you see the recovery screen.

ashyx said:
You're not following the instructions properly. Read post 3 again and hold ALL 3 buttons until recovery boots.
Do not let go of any of the buttons until you see the recovery screen.
Click to expand...
Click to collapse
Nevermind, I actually got it to work. What do I do after it says "downloading" to fix this issue of it not getting past the boot screen? Please help, I'm not too good with this kind of stuff

casual167 said:
Nevermind, I actually got it to work. What do I do after it says "downloading" to fix this issue of it not getting past the boot screen? Please help, I'm not too good with this kind of stuff
Click to expand...
Click to collapse
Well, downloading is not the recovery.
In download mode you would use ODIN to re-flash the firmware from a computer.
In recovery, you would do a factory reset to reset back to defaults to see if that helps boot back into the existing firmware. You'll probably lose everything.

CZ Eddie said:
Well, downloading is not the recovery.
In download mode you would use ODIN to re-flash the firmware from a computer.
In recovery, you would do a factory reset to reset back to defaults to see if that helps boot back into the existing firmware. You'll probably lose everything.
Click to expand...
Click to collapse
Yeah I just figured out I was in the wrong mode. I couldn't get it to the recovery mode for some reason but eventually it worked. So I have to go into wipe data/factory reset option? There's nothing else I can do on that screen to fix this without losing everything? I see other opions to Wipe Cache, reboot to bootloader, reboot system now etc..

casual167 said:
Yeah I just figured out I was in the wrong mode. I couldn't get it to the recovery mode for some reason but eventually it worked. So I have to go into wipe data/factory reset option? There's nothing else I can do on that screen to fix this without losing everything? I see other opions to Wipe Cache, reboot to bootloader, reboot system now etc..
Click to expand...
Click to collapse
Well, you're not really giving enough info for us to properly help you.
If you have stock recovery then you can try clearing cache but it probably won't fix a no-boot situation.
If you have TWRP recovery then you can try clearing cache and dalvik and fix permissions which probably won't help but gives you a better chance.
Also, if you had TWRP then you could simply re-flash your ROM zip and not lose a whole lot.

CZ Eddie said:
Well, you're not really giving enough info for us to properly help you.
If you have stock recovery then you can try clearing cache but it probably won't fix a no-boot situation.
If you have TWRP recovery then you can try clearing cache and dalvik and fix permissions which probably won't help but gives you a better chance.
Also, if you had TWRP then you could simply re-flash your ROM zip and not lose a whole lot.
Click to expand...
Click to collapse
Sorry about that. It's like I said, I'm not too inclined on this type of stuff. Here's what I got and hopefully it helps you more. The tab is completely stocked, never rooted because I wouldn't even know how to do that really. I was on it fine last night and all I did was put it down for literally 30 sec to get something to drink and when I came back it was stuck on the Samsung logo screen. Only apps I had open was gmail, chrome and a word document. There was nothing dowloading, system wise or apps. It's already had Lollipop on it for a week or two and I didn't get any update notices or anything. So I'm guessing the problem is it's somehow stuck in a "boot loop" from what I found searching on google and I don't understand why or what could be causing it so that's the issue I'm trying to fix. I can't get past that screen no matter how many times I restart it. Does that help some?

casual167 said:
Does that help some?
Click to expand...
Click to collapse
Yeah, so unfortunately your options are very limited and you're kinda stuck with losing everything.
Try clearing cache first but I doubt it will help.
Then reset to factory defaults. That should work and you probably lose everything.
If not, then search this forum for "ODIN" and "firmware" or let me know and I'll guide you when I get back to my computer in a couple hours.

CZ Eddie said:
Yeah, so unfortunately your options are very limited and you're kinda stuck with losing everything.
Try clearing cache first but I doubt it will help.
Then reset to factory defaults. That should work and you probably lose everything.
If not, then search this forum for "ODIN" and "firmware" or let me know and I'll guide you when I get back to my computer in a couple hours.
Click to expand...
Click to collapse
Ok I'll give that a try, thanks. Should I take out my SD card before I reset everything
---------- Post added at 04:52 PM ---------- Previous post was at 04:15 PM ----------
casual167 said:
Ok I'll give that a try, thanks. Should I take out my SD card before I reset everything
Click to expand...
Click to collapse
So I did the factory reset, it started up now and it's as if I just took it out of the box. Unfortunately I'm at work though so I can't connect to a wifi to complete the set up process so I'll have to wait until tonight when I get home but thanks again for your help. If you could still help me later though with the Odin and firmware stuff I would appreciate it.

casual167 said:
So I did the factory reset, it started up now and it's as if I just took it out of the box. Unfortunately I'm at work though so I can't connect to a wifi to complete the set up process so I'll have to wait until tonight when I get home but thanks again for your help. If you could still help me later though with the Odin and firmware stuff I would appreciate it.
Click to expand...
Click to collapse
The factory reset should not touch the external SD card at all. So no worries about leaving it in during that process.
Yeah, starting over.
As long as you're doing that, this is a great time to flash a rooted ROM so you can install Titanium Backup and do regular backups of your apps in case you ever need to reset to factory again.
What model tab do you have? Like, mine is a T705.
If it's an LTE tab, who is your carrier?
The ODIN process depends on this info.

CZ Eddie said:
The factory reset should not touch the external SD card at all. So no worries about leaving it in during that process.
Yeah, starting over.
As long as you're doing that, this is a great time to flash a rooted ROM so you can install Titanium Backup and do regular backups of your apps in case you ever need to reset to factory again.
What model tab do you have? Like, mine is a T705.
If it's an LTE tab, who is your carrier?
The ODIN process depends on this info.
Click to expand...
Click to collapse
So I left for lunch and tablet was functional and in the set up process and when I came back, it's back at that damn Samsung logo screen and haven't been able to get back to the recover page. Any idea or suggestions on what to do now? How could that same problem still be here if I did the factory reset?
---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------
casual167 said:
So I left for lunch and tablet was functional and in the set up process and when I came back, it's back at that damn Samsung logo screen and haven't been able to get back to the recover page. Any idea or suggestions on what to do now? How could that same problem still be here if I did the factory reset?
Click to expand...
Click to collapse
Actually, I just got into the recovery page now
---------- Post added at 07:02 PM ---------- Previous post was at 07:00 PM ----------
What should I do ?

CZ Eddie said:
What model tab do you have? Like, mine is a T705.
If it's an LTE tab, who is your carrier?
The ODIN process depends on this info.
Click to expand...
Click to collapse
casual167 said:
How could that same problem still be here if I did the factory reset?
Click to expand...
Click to collapse
Who knows, something is not happy though.
You could try another reset.
Is your battery greater than 50%?
Under a certain percentage, the battery savings feature could possible do weird things.

CZ Eddie said:
Who knows, something is not happy though.
You could try another reset.
Is your battery greater than 50%?
Under a certain percentage, the battery savings feature could possible do weird things.
Click to expand...
Click to collapse
Lol yea no kidding. The battery has been plugged in the whole time. I'm actually at 100% now. I was really trying to avoid having to bring it to Geek squad. If I do the reset and it does it again, will going to the download mode and doing the custom OS help at all?

casual167 said:
If I do the reset and it does it again, will going to the download mode and doing the custom OS help at all?
Click to expand...
Click to collapse
Unless it's a hardware issue, then re-flashing the firmware via ODIN could definitely help!
You can ODIN the stock, unrooted firmware or you can ODIN a TWRP recovery and flash any ROM you want for your phone.
Would still need to know the model # I asked for a couple times above.

CZ Eddie said:
Unless it's a hardware issue, then re-flashing the firmware via ODIN could definitely help!
You can ODIN the stock, unrooted firmware or you can ODIN a TWRP recovery and flash any ROM you want for your phone.
Would still need to know the model # I asked for a couple times above.
Click to expand...
Click to collapse
My bad, its SM-T800
---------- Post added at 08:02 PM ---------- Previous post was at 07:46 PM ----------
Leaving now but I'll be back in a couple hrs

casual167 said:
My bad, its SM-T800
Click to expand...
Click to collapse
Okay great, so you can ODIN a TWRP recovery and then flash a nice ROM. Same ROM I use on my phone. It's stock Touch Wiz that has been rooted and some small things have been improved. Very stable. IronROM.
Or you can download the stock firmware from sammobile.com and ODIN back to stock.

Oneplus 5T VERY Hard Bricked

Hey guys,
So this is very stupid but I think my phone is ultra hard bricked.
Long story short: I updated to 5.1.1 and wiped cache afterward and boom nothing works now.
Before people are coming with solutions I'll tell you guys what I did and tried.
First of all the phones bootloader is locked and fastboot tells me I can't flash in a locked state.
I tried the Unbricking tool.
I tried Power reset
I tried reflashing all I could in fastboot but won't let me because of the locked state.
I can only access Fastboot (sometimes) and it can get to the start up screen where it says powered by android and then it shuts off again.
Maybe its worth mentioning - the LED notification is blue all the time.
I don't know what to do.... I can't send it in for RMA since I'm going on vacation in a few days and it would be impossible to go without it.
So if anyone got something in their sleeves please let me know. :crying:
Best regards
Christoffer

Contact 1+ support, a technician may make a remote session to rescue your device
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
but did the unbricking tool say successul after a few minutes, or it failed?

You should be able to flash a stock image without OEM unlock or ADB enabled on the phone in fastboot using the stock recovery. If you can't access the recovery on the phone I would boot the stock recovery on your PC and attempt to flash a stock image from it.

As long as you can get to fastboot, you should be able to recover. From there you should be able to boot into recovery. If your on stock you can just factory reset, or try sideloading OTA- all.zip. A hard-brick is when your device doesn't power on, and you could still recover from that also.
Sent from my ONEPLUS A5010 using XDA Labs

A hard brick or even a brick by what u state means u have no life in the phone. U even stated your phone responds at times. Which means it's not bricked.

ChrisBG said:
Hey guys,
So this is very stupid but I think my phone is ultra hard bricked.
Long story short: I updated to 5.1.1 and wiped cache afterward and boom nothing works now.
Before people are coming with solutions I'll tell you guys what I did and tried.
First of all the phones bootloader is locked and fastboot tells me I can't flash in a locked state.
I tried the Unbricking tool.
I tried Power reset
I tried reflashing all I could in fastboot but won't let me because of the locked state.
I can only access Fastboot (sometimes) and it can get to the start up screen where it says powered by android and then it shuts off again.
Maybe its worth mentioning - the LED notification is blue all the time.
I don't know what to do.... I can't send it in for RMA since I'm going on vacation in a few days and it would be impossible to go without it.
So if anyone got something in their sleeves please let me know. :crying:
Best regards
Christoffer
Click to expand...
Click to collapse
When you get to fastboot try to boot TWRP, not install and then flash stock firmware first (there is some compiled one's here on xda without the whole rom).
If that doesnt work, try to flash a stock boot image.