Database Info

[Q] I am Bricked....i think

Ok, So i rooted my T-mobile G2x 2.3.3 and there were difficulties when i flashed the Cyanogen 7mod. The Rom worked but the only default was i didnt get data. Like i couldnt even get Edge. The only way to use internet and stuff was through wifi. SO then i reflashed it thinking it was a bad flash. But when i reflash through rom manager it gives me the option to downoad with google apps. so i clicked that option. It downloaded fine but on the reboot it stayed stuck on the 2nd LG screen. Am i bricked or if anyone can help id appreciate it alot.

U can't do it via rom manager. U have to flash recovery using nv flash, then u can try to flash custom rom. Remeber to wipe data and format system before flashing any rom.
U r not bricked yet
Check here to nv flash the cwm
http://forum.xda-developers.com/showthread.php?p=13330067
Sent from my LG-P999 using xda premium

Did you flash CWM via NV Flash. If not, do that. Then boot into recovery by holding down the power + volume down keys until you get the second boot logo. Then wipe the dalvik cache and the regular cache. That is usually why a phone refuses to boot.
Also, if your phone turns on it is not bricked. Bricked means when you press the power button nothing happens at all. You can be soft-bricked like you are, but it can be easily fixed. Nothing to panic about.

I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.

iSpooNz said:
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
Click to expand...
Click to collapse
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.

jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
Ok so from CWM do i wipe everything?

jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
@OP, this is is correct. Use tga gunmann's nvflash tool from the development section. The process is super easy. Just make sure to follow his instructions closely. Just fyi, most people get errors during the nvflash process because they don't install the apx drivers appropriately, so take your time and read the instructions carefully.

iSpooNz said:
Ok so from CWM do i wipe everything?
Click to expand...
Click to collapse
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.

phburks said:
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
Click to expand...
Click to collapse
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up

iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.

iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.

phburks said:
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
Click to expand...
Click to collapse
Ok ill try that.
jboxer said:
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
Click to expand...
Click to collapse
Yea i wiped Dalvik cahce and the same result came up. So i factory resetted and same result. So im going to try what phburks said and see what happens.

Im still stuck in the second LG screen :/

iSpooNz said:
Im still stuck in the second LG screen :/
Click to expand...
Click to collapse
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.

phburks said:
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
Click to expand...
Click to collapse
download the rom right?

iSpooNz said:
download the rom right?
Click to expand...
Click to collapse
Yea the rom. Is it cm7 that you're wanting to flash?

phburks said:
Yea the rom. Is it cm7 that you're wanting to flash?
Click to expand...
Click to collapse
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.

phburks said:
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
Click to expand...
Click to collapse
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?

iSpooNz said:
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
Click to expand...
Click to collapse
Not sure. I'd just play it safe, re-download both, wipe data, and reflash both. Sometimes its hard to determine which step went wrong and its best and quicker to just start with a clean slate and redo everything.

I wont be able to post for a while so good luck.

[Q] Bricked P5100? Help please!

My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!

dwl99 said:
My P5100 had CM10 nightly on it and was running fine until I upgraded to the latest version of CM10 after wiping the cache & Dalvik cache. After the upgrade I couldn't get Google Play to run even after wiping its data and fixing permissions so I tried to do a CWM restore. Unfortunately there was a fault restoring the Data partition and now my tablet is stuck at the animated bootscreen. If I long-press the power button it powers off but immediately restarts. There is no way to start in in recovery or flash mode. I've plugged it into my PC and the Samsung Android ADB interface is showing but the other references to the tablet all have a yellow triangle in Device Manager. I'm hoping some clever person can help me rescue the tablet with ADB. Thanks!
Click to expand...
Click to collapse
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM

DigitalMD said:
IF CWM is not working use Odin to flash CWM again then use CWM to flash CM10,
You may need to do a factory reset (full wipe) from CWM.
If all else fails use Odin to flash stock JB ROM
Click to expand...
Click to collapse
Thanks but Odin cannot see the tablet to re-flash the recovery.

Downlods mode
Then flash new firmware

sembre said:
Downlods mode
Then flash new firmware
Click to expand...
Click to collapse
That's the problem - I cannot access download mode
UPDATE - it just started in download mode! I can manage from here!!

Just for the record you can install adb on the pc and run the command 'adb reboot recovery'. This will force the tablet to reboot in recovery mode.
Sent from my GT-I9300 using xda app-developers app

Jeez, this has taken up most of the day to fix. I came across many problems I have not previously experienced:
1. When the tablet was stuck at the boot animation and I tried to turn it off by long-pressing the power button it immediately restarted. The only way I could get it to turn off was by long-pressing the power button whilst it was connected to my PC.
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
3. Flashing CWM with Odin caused the tablet to reboot into the stock ROM which would not load, in the end I had to untick the "reboot" button in Odin, power it off then manually restart with the Vol- & power buttons.
4. The only way I could get a bootable ROM was by flashing CM10 with CWM. I tried to restore 2 previous CWM backups but on each occasion there was an error restoring the Data partition and I got stuck at the scenario at (1). The backups were made to the external SD card with CWM Touch - is the Touch version unreliable?
I would be really interested if anyone could shed any light on any of this stuff!

For how long did you let it install during the first reboot? It happened to me too, and it took about 10 minutes, maybe even more...
Also, did you try in the "Mount and storage" cwm menu the options "format system", "format data", "format cache" and "format preload" options, prior to re-flashing a ROM? I have read somewhere that for a clean install it's better to do this, as it really clears everything that could mess up the system between two different bases ROMs (like CM and stock).
What I do everytime is using in CWM these 4 "format" options, plus "wipe" system, cache and dalvik, then immediately after this I flash with cwm the new "zip" copied on the card. Then the first reboot is much longer than usual, as at this stage it installs the files, rebuild the dalvik cache etc.
Good luck
dwl99 said:
2. Flashing the stock ROM with Odin appeared to complete successfully but it would never fully boot, it always got stuck at the black & white Samsung screen. Same problems turning it off as above.
Click to expand...
Click to collapse

I think I gave it a good 20 mins to boot. When I got up this morning there was an error message saying that there was no room to install any more apps even though I had very few installed. Settings -> Storage would not calculate the space available so I figured that the partitions had become corrupted. I did the step by step format you described and reflashed & it all seems to be OK now.

Bootloop CWM ok+no format data+rom bootloop+no pc[SOLVED]

Hello,
First sorry for my English, i´m from Spain and i read-speak only a little.
I've been searching for a solution for my problem but i cannot find it.
On Friday when I had in my hands my TF101 (i just in chrome browser) just restarted, and restarted it again in a loop.
The first thing I did was go to Recovery ( CWM Recovery 3.2.0.1 -r1 Roach2010 ) to run a backup .
I try a cold boot, without results.
Then I try to restore to a previous backup and follows restarting.
Next i try was to install the stockrom I had previously installed, the last StockRom recovery from wipes and did the install , reboot the blue bar goes loading screen asus just restarts and restarts and restarts.
I think that the installation can't be completed because the restart.
Then, I do a wipe data/factory reset and I get an error.
I can not delete a file(/data/data/com.asus.reader/cache/files/media_external_file176Satellite.pdf ) and CWM cancel the formatting /data.
I try to make a format / data and I get the same error.
I´ve tried doing all wipes (data can't) installing all my previous buckups. Everything seems to be installed but reboot continue.
Otherwise I tried to connect to the PC ( 3 to be exact) OS: Vista x64, 7, 7 x64, Linux x64, Linux live cd.
I pressed Pwr + Vol + from 6-60 sg, after shutoff my tablet from CWM, connecting the usb cable before or after and no detects the TF101 .
I ordered a new cable, but mine seems to be good and i can charge the TF101 without problems.
I have read as Xda-topics as I can , I haven't seen in any solution to my problem ( CWM Recovery working + no format data + bootloop + pc no connection).
I´m afraid of brick my tablet. Only lives in recovery, no Android (reboot), no apx, no adb.
What can i do to format /data ?
Can I flash from my actual CWM another Recovery (maintaining the functionality of the microsd ) as TWRP? what happend if failed?
Thanks
PD. I really learn a lot with this problem reading yours posts.
Thanks

1.) Put this flashable zip on your Micro SDCard
http://nexfiles.kjonigsen.net/tf101/twrp/twrp2.6-tf101-unofficial.beta.zip
2.) Flash it from inside CWM Recovery
3.) Reboot tablet into recovery, check that TWRP is the new recovery
4.) Copy this ROM on to MicroSD Card
http://downloads.timduru.org/android/tf101/K.A.T/KatKiss/dev/KatKiss-4.2.2_226.zip
5.) Copy Gapps onto Micro SDCard
http://goo.im/devs/teameos/roms/eos4/gapps/gapps_4.2.2_TF101_20130323b.zip
6.) Boot into TWRP recovery
7.) Wipe SYSTEM, DATA, CACHE, DALVIK CACHE
8.) Flash ROM, Flash Gapps,
9.) Wipe CACHE and DALVIK CACHE one more time
10.) Reboot into working Jellybean ROM
The above will wipe everything clean and install a fresh JellyBean ROM to your tablet

First thank you very much Detection.
My new usb cable should arrive today and i'll try to apx mode recongnition.
In any case I downloading the files you provided me, but i have one question
*Detection* said:
1.) Put this flashable zip on your Micro SDCard.
Twrp Downloaded
2.) Flash it from inside CWM Recovery
Ok, i can.
3.) Reboot tablet into recovery, check that TWRP is the new recovery.
Click to expand...
Click to collapse
Here i must to reboot into new recovery from old recovery. Not need reboot tablet to OS (bootloop) ¿ok?
Thanks, thanks, thanks.
Edit:
I do it, i flashed TWRP, reboot and reboot into RCK. ok
Now copying camera data to microsd, and ready for wipes.
Thanks.

Sounds like you are making good progress
No need to reboot into OS, just into new TWRP recovery, then wipe and flash new ROMs etc

*Detection* said:
Sounds like you are making good progress
No need to reboot into OS, just into new TWRP recovery, then wipe and flash new ROMs etc
Click to expand...
Click to collapse
Yes, thanks.
I plugged my tf 101 with my new cable and now is detected in windows 7 x64. Naked drivers installed.
But before that, i flash TWRP recovery and it's fantastic. I can copy all my photos to microsd. I need to have this out TF101.
Now i installing the rom and gapps, but seems to be freeze on the four colour circles screen.
More than 20 minutes.
I'm thinking on reflash all an try again.
Thanks Detection.

Make sure you wiped everything before flashing the ROM & Gapps
The animation should not freeze during boot

I do all wipe data, cache, system, dalvik.
flash rom
flash gapps
wipe cache and dalvik
reboot.
and, not freeze but keeps moving and now + 30 minutes.
Something's bad.
I'm thinking on trying apx mode to solve.
Maybe

EDIT - See if it boots without Gapps first (Wipe everything again but only flash ROM)
1.) EDIT - Try this
http://www.putlocker.com/file/42672030BC26BD2F
Use Easyflasher to flash TWRP again, then try wiping and flashing ROM and Gapps again
IF THE ABOVE FAILS DO THIS:
2.) Ok, try this to rebuild the Partitions, this will flash the stock ROM to your tablet, if you have SBK1 (Serial number B6O or before, some B7Os)
http://www.xdafileserver.nl/index.php?dir=Asus%2FAsus+Transformer+%28TF101%29%2FSTOCK+ROMS%2FICS+.27
Choose US or WW
Connect TF to PC > Power Off TF > Put TF into APX mode (Vol Up & Power)
PC will recognise TF but nothing on TF screen will show
Extract the ROM above > Run download.bat as Admin (Right click > Run as Administrator)
Let it flash the ROM, this takes a while, maybe 10+ minutes
If that works, and you can boot, we can use Easyflasher to root and install TWRP again, and then flash Jellybean ROM again

I tried flashing rom and gapps again. No works, keeps on 4 turning circles screen. I leave it all night connected to AC Power. This morning was in the same screen.
I tried flashing rom, wipes, reboot. No works keeps on 4 turning circles screen. After 1 hour i restarted.
I'm going to try easyFlasher metod. I'll update progress.
My tf101 is B80 that's Sbk2. ok? Then, how can i rebuilt the partitions?
Thanks.
UPDATE 1.
easyFlasher WORKED¡¡¡¡¡¡
Now I'm on Stock.
I flash recovery and also WORKED¡¡¡¡¡
Next work:
Fisrt root
Afteri ready to KatKiss.
UPDATE 2.
Flashed superuser.
Reboot
Flash KatKiss 226 and gapps.
Then not reboot. But coldboot done.
¡¡¡SOLVED!!!
Thanks Detection.

Ok, you can't use NVFlash with SBK2, but you can use Easyflasher
Try using Easyflasher I posted here in SBK2 mode and flash TWRP
http://www.putlocker.com/file/42672030BC26BD2F
Then try wiping everything and flashing ROM and Gapps again
If it still won't work, wipe again and try a different ROM
ROM
http://downloads.timduru.org/android/tf101/K.A.T/KatKiss/4.3.1/dev/KatKiss-4.3.1_028.zip
Gapps (Only for this ROM)
http://downloads.timduru.org/android/tf101/gapps/gapps-KatKiss-4.3_20130914.zip

[Recovery][Boot] Recovery mode has highest boot priority?

So I unlocked, rooted and installed Euphoria ROM on my Moto G today, and now I'm perplexed to find that when I select the "Reboot" option either in Android or TWRP, I immediately get shoved back into TWRP. Rebooting to Bootloader works as expected, rebooting to Recovery works as expected, but the normal reboot doesn't.
Also, when my phone is offline and I plug it in, it immediately lights up and boots directly into TWRP. I don't know why this is, but I'd like to fix it since it's hit and miss trying to boot into the ROM normally.
Can anyone help me pin point the problem? In all my years with Android I've never seen an issue with boot priority such as this.
Things I have done:
-I tried to decide on a recovery so I flashed PhilZ, CWM, and TWRP in that order from the fastboot commandline
-wiped system, data, cache, dalvik cache, and flashed Euphoria ROM
Thanks!

One thing I would suggest is to flash the stock recovery and try rebooting, even i had encountered this problem. Later you can flash twrp again and everything will work fine.

Are you getting any errors while wiping partitions

sjandroiddeveloper said:
Are you getting any errors while wiping partitions
Click to expand...
Click to collapse
I'm having the same problem here. Wiping works alright, no errors at all. Although the built-in TWRP file manager is unable to see any files in the system folder.

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please

First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?

leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.

Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.