Database Info

help ! something isn't working :(

so today i went to unlock and flash CM 10.1 on my tablet.
unlocking went smoothly
installing clockwork recovery went fine
installing cm10.1 and gapps went fine
once i booted into cm successfully, i checked the internal storage to see if it was clear. it wasn't, so i went to settings, backup and reset, and done a factory reset. now i'm stuck on this one screen and i dont know what it is.
i've held the power button and volume down until the tablet restarts and that results in the same thing.
i've tried power and volume up. that seems to start the tablet but the screen stays blank. i connected it to the computer and my computer installed an APX or APTX or something like that driver.
i've tried holding power, volume up and down, and that does the same as the power and volume up.
i'm very new to installing custom recoveries and roms. can anyone give me an idea on whats happened

Once you have a custom recovery installed you should NEVER wipe from the system settings or the bootloader menu. You wipe from your recovery.
If you do that, the bootloader seems to write a command to the misc partition to reboot into recovery.
And that is the loop you seem to be stuck in.
You can try _that's method to clear the misc partition from here: http://forum.xda-developers.com/showthread.php?t=2528313
Read the whole thread, salvation may be found in post 7.
If that does not work, you could try this:
http://forum.xda-developers.com/showthread.php?t=2399698
buster99's method may be another way to enable you to boot into the bootloader and flash a working recovery.
Good luck!

Thanks for the tip. I'll remember to do that next time. As of now it is fixed. I found a post on the cyanogen forum of someone who done the same thing. And he said he had to wait a painful 6+ hours of that screen I posted. Lucky for me it was only a ~45 minute wait. So all is good. Cyanogen is running. Recovery is working. All the stress is gone.

Another TF300T brick ? need advice !

Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,

hardballer83 said:
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
Click to expand...
Click to collapse
I guess you've tried this, but power on by holding power+down vol. Should get you to bootloader. Keep holding it until bootloader screen appears. Holding power for 10-20 seconds should power down tablet.
Sent from my HTC One M8 using XDA Free mobile app

Hi
Thanks for your answer.
Yup I tried it, I tried all the ways I found on the internet (there's a post somewhere in this forum where 7 or 8 different methods are explained) none of it worked.

So, did you have TWRP loaded on the regular flash partition vs. the Recovery partition?
Is it possible you were running TWRP as the Operating System, and when you wiped the partition, you destroyed the OS?

TF300T bricked?
Hi,​
hardballer83 said:
Hello all,
I think my TF300T is definitely bricked, but I'd rather have your opinion before trying to switch motherboards....
What are the symptoms :
When I power on the tablet, I have for a few seconds the Asus screen (with "tablet unlocked" on the top), then this Asus screen blinks and the tablet launches twrp automatically (without showing the bootloader (recovery,android,wipe) screen, it goes directly to twrp).
But TWRP won't launch properly, it is stuck in twrp start screen for 30 seconds, then the tablets restarts automatically and the loop I described starts from the beginning.
I cannot event switch off the tablet holding the power button, can only restart it.
I started many combinations described in several posts here to obtain the bootloader screen (I've seen a post with a least seven methods, the only one I did not try yet is to open the tablet and unplug the battery ), none succeeded !
I previously (before the problems) had good adb/fastboot connection with my computer, none of it is working now ! (I've seen a post of someone saying that he had a proper connection for only a few seconds during boot, I tried the steps he described but it did not work either, If I constantly launch "adb devices" or "fastboot devices" commands , I never obtain a response from the tablet. ( I also did the drivers replacements )
How did I get there :
I wanted to install katkiss , before that I installed twrp and formatted /data in f2fs.
After installing twrp I saw that it could not launch properly (it could launch only after flashing it , the next boot it was not working anymore, stuck in launch screen), and that the filesystem was not accessible in twrp any more .
That's where I guess I did the biggest mistake, I used the wipe option in the bootloader (I know now that it was A VERY BAD IDEA ... ) .
I seemed to me that , to perform this wipe, the tablet launched twrp and freezed , but I can be wrong.
I suspect that the tablet saved somewhere that is has to launch twrp on boot to perform the wipe, but as twrp is not launching correctly, the tablets restarts, sees that it has to launch twrp... , then loop again ...
Am I right ? could it be possible that the tablets stored somewhere to automatically start twrp on boot ?
and now ?
Every ways to fix it I read implies having adb or fastboot (I read about nvflash but never used it before, so it seems too late), butI can't use it at the moment !
Any Suggestions / advice ?
Thanks in advance,
Click to expand...
Click to collapse
Hi, Had the same thing happen to mine. Hold own power to force shutdown then hold volume down and recovery screen should come up. Worked for me.!

@hardballer83
Unfortunately a bad situation caused by yourself!
If you don't have any fastboot or ADB-access to your tablet now, only a new MB can bring your device back to life again.

Point me in the right direction

Hi,
I just bought a second hand Nexus 5 and when I turned it on it was in "FastBoot Mode" with the product name Hammerhead and bootloader HHz12k showing as the bootloader version.
Anyway, I set the phone up and started a system software update and now it's stuck in a loop where it states "Installing System Update" with the progress bar 1/5th of the way up, restarting and repeating that process, Statement, Progress Bar, Restart.
Has this phone been tampered with and is there any way I (a layman) can get it running.
I've searched the forum but must admit the volume of threads is confusing. Can anyone help?

You can just flash the latest stock from from Google.
ROM images are here: https://developers.google.com/android/nexus/images#hammerhead
Good info here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

CHEWBAZZA said:
Hi,
I just bought a second hand Nexus 5 and when I turned it on it was in "FastBoot Mode" with the product name Hammerhead and bootloader HHz12k showing as the bootloader version.
Anyway, I set the phone up and started a system software update and now it's stuck in a loop where it states "Installing System Update" with the progress bar 1/5th of the way up, restarting and repeating that process, Statement, Progress Bar, Restart.
Has this phone been tampered with and is there any way I (a layman) can get it running.
I've searched the forum but must admit the volume of threads is confusing. Can anyone help?
Click to expand...
Click to collapse
You first need to find out what state the bootloader is in. Is it locked, unlocked? If unlocked, is there a custom recovery installed, such as TWRP? First of all, turn the phone completely off ... and then boot into recovery, by holding the volume down button and the start button simultaneously. Toggle the volume button to show recovery, and select with the power button. If it boots into TWRP, do a wipe (cache, dalvik cache, reset), and then reboot the system. You should be at the welcome screen of what software is currently on the phone. Set up enough so that you can get back to XDA, and download a stock custom rom, such as xTraFactory and the updated bootloader/radio zip that was released a couple of weeks ago. Back into recovery ... wipe, then flash the rom zip and the bl/radio zip. Reboot and setup.

Galaxy S7 G930U Unlocked stuck in boot loop - already flashed successfully but no fix

I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.

gabeblack said:
I'm really hoping you guys can help me out here. This is an S7 I bought from a Best Buy when I visited the US in 2017, and I got the Unlocked version so I would be able to use it back in my home country. Unfortunately, this is the second time I've had trouble with it in a span of 4 months and the first time it was a hardware problem and ended up quite expensive to get fixed.
Today I was using my phone normally when I decided to use the Google instant translation to translate something on my computer screen. That caused my phone to freeze, restart, and then tell me I was using an unauthorized flash and it was going to be locked, or something like that. Even after restarting a few more times, the phone would never get past that screen. I proceeded to factory reset/cache reset and from then on the phone just got stuck in a boot loop.
I learned that the fix would be to flash the phone. After a lot of work I found the G930UUESACSI1-20190930144640 firmware (the XAA version, for Unlocked) and successfully used Odin 3.13 at the Download Mode screen to flash my phone. It then restarted, went back to the blue screen, started installing some updates, when it was 100% it restarted again. Unfortunately, the loop remained. Galaxy S7 logo first, then the Samsung logo, then it just repeats.
I have also tried turning the phone off with the Recovery screen shut down option (since I can't seem to be able to turn it off with the power button right now), wait a few minutes, then turn it back on. Nothing changed.
Please, does anyone have any insight into this? What else could I possibly try, or what could I be doing wrong? I really don't want to send it to repair yet again in such a short time.
Many thanks in advance.
Click to expand...
Click to collapse
You need to clear the cache after flashing to get out of the boot loop.
Use the download key combo to restart. As soon as the screen goes black move to Volume up+home+power.
In the recovery menu choose clear/ Wipe cache, then choose reboot.

I apologize for not updating this thread before when it was still recent. The fact is that I didn't manage to fix my phone; clearing the cache after flashing did nothing to stop the loop.
I ended up taking the phone to the people who have fixed it in the past and after more than one month, they gave up. So I got my phone back and I want to try to give it another go before I just sell it for parts.
Unfortunately, my phone has come back even worse. Now it has no Recovery Menu to speak of, at least none that I can access; after a few seconds of the blue text on the top saying that it's entering recovery mode, it then proceeds to a blue screen saying: "Security Error: This phone has been flashed with unauthorized software and is locked.". I can still access Download Mode.
I have attempted flashing a few firmwares that I believe should have worked with my SM-G930U. Odin listed the attempts as "pass" and, after restarting and going back to the Download screen, it says the binary is Official. However, after trying to restart the phone normally, it starts displaying the blue screen again, and then, after going to Download mode, the binary is reverted to "Custom".
I believe right now the order of the day is to get the recovery menu to work again so I can do all the cache cleaning that seems to be required after flashing firmware. Any ideas at all on how I should proceed? Is there something specific I should download to fix the recovery menu?

How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?

Drunkpilot said:
How many files are you flashing in Odin, is it just 1 file in the AP slot, or 4 files: AP, BL, etc.? Also, is your phone rooted?
Click to expand...
Click to collapse
Never rooted, was using the phone legit before it froze and entered boot loop. I flashed all 4 files, multiple times.
Someone tried fixing my phone a few days after I replied to this thread and some progress seems to have been made, but now the phone cannot get past a black screen with a "SBL Error! rdx_init!" in red text, and "upload mode" in yellow text. Still cannot access Recovery Mode, but Download Mode still works.
I did a little Googling on rdx_init errors and it seems I need a firmware dump from another G930U or something like that...any ideas on how I can proceed?

Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy

STA1NL3SS said:
Flash it with Eng Boot in all slots using patched Odin. Reboot to recovery and wipe it. Reboot system. Then root it with advanced adb root. Links for all of this are here in xda. Enjoy
Click to expand...
Click to collapse
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed

gabeblack said:
Sorry, I'm not an expert at this by any means, I'm not sure what files to get. So far I've found and downloaded the following:
S7_Oreo_Nougat_Adb_Advanced_Root_V10
S7_Oreo_Nougat_Adb_Advanced_Root_V12
S7_Oreo_Su_Binary_Only_ADB_Root
But I had no luck flashing any of these cause my binary is 10. Is there any more help you can provide me? I really don't know how to proceed
Click to expand...
Click to collapse
I thought I had one in my phone, but I don't. If you look at the thread where you downloaded the Root_V12, you will see it. It's near the end of the thread somewhere.

My Google Pixel seems bricked - Could someone confirm there is nothing I can do ?

Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do

rraphrr said:
Hi, here's a description of what happened, what I did to solve my problem, and where I am now...
I left my Google Pixel and 2 hours later found it stuck into a booting loop (Google logo displayed > black screen > Google logo displayed > blackscreen...).
I first entered fastboot and tried to power off, restart, etc a few times, but it stayed stuck into the booting loop.
So I downloaded latest OTA from Google for my phone (my phone was already updated to the latest version via the phone update manager, which goes back to december 2019 I think).
I first verified that my linux pc could correctly see the devices, and then from fastboot I entered recovery mode and chose "Apply update from ADB".
I used the adb command to load the OTA I had downloaded.
The update progressed until it finished with the following error message :
Code:
install from ADB completed with status 1
Installation aborted
E:Failed to clear BCB messages: failed to write /dev/block/platform/soc/62400.ufshc/by-name/misc: I/O error
I was back on the recovery menu screen, and this is where I think I did something stupid : I selected "Reboot system now".
The phone did not reboot, the screen just went black and stays black. The phone is cold so I guess not running anything. And it does not respond to any button, so not starting up, no fastboot, etc. No more when I connect it to a PC or plug it in a power plug.
I don't really care about the phone, I was just trying to get back my picture/videos from the last 6 months.
I don't have much hope but I will appreciate any help, even if its just to confirm that there is nothing to do
Click to expand...
Click to collapse
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way

muhammad42620 said:
Well you could try and see if the phone is in deep flash mode, if it is flash system, boot and other sensitive partitions but make sure that the versions are the same. If you don't have the firmware you can pull user data partition from phone and get your data back that way
Click to expand...
Click to collapse
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...

rraphrr said:
Thanks for your help. This is probably beyond my capabilities. I don't know how to check if it's in deep flash mode. Pulling the data out is what I'm interested in most.
Maybe this is something that a phone repair shop is able to do...
Click to expand...
Click to collapse
These phones get emmc errors. Common issue with this device