Database Info

[Q] Is my Phone Bricked

I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help

Try reflashing Clockwork Mod Recovery.
Sent from my LG G2X using XDA Premium for Android

Do that, and if you have the means, try to check out the external sd on some other device to see what's going on. I'd start with pulling the battery for a bit and try flashing the backup again.
Also, correct me if I'm wrong but if you didn't flash anything because of misfiling xboarder's rom, there was no reason to use the backup in the first place.

dachinaman said:
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i realized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Click to expand...
Click to collapse
Where did you put your nandroid - internal or external SD? They would have been determined by the recovery option you chose - Internal or External SD. Your stock ROM would download the Xboarder ROM to internal in any case, but your nandroid location depends on the choice above.
Since you did a total wipe, you do not have a ROM installed, so you will not be able to boot up, but you DO NOT have a brick.
You could flash the Recovery again with the Oneclick Recovery tool and choose internal, and then you could flash the Xboarder ROM. After that, see if you can find your backup (in the clockworkmod folder).

gaww said:
Since you did a total wipe, you do not have a ROM installed, so you will not be able to boot up, but you DO NOT have a brick.
Click to expand...
Click to collapse
I didn't know that a wipe from cwm clears out the rom. I only ever wiped before flashing something else so I assumed it was more like a factory reset.

heysharon said:
I didn't know that a wipe from cwm clears out the rom. I only ever wiped before flashing something else so I assumed it was more like a factory reset.
Click to expand...
Click to collapse
As far as I know, the wipe data/factory reset is exactly that.
There's also a wipe system function, which wipes the entire ROM also. It seems he did that also.
As for fixing the phone, what gaww said haha. If xboarder's mod isn't there, then in recovery while the phone is plugged in, mount the sd card, and put a rom on there using windows explorer or whatever, then disconnect and you should be able to flash it.

dachinaman said:
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Click to expand...
Click to collapse
Boot into recovery, go down to mount, and mount usb. Then find the file on your internal sd and move it over to the external sdcard. I have had to do that a few times when I forgot to move the file.

Recovery verified failed ??

Hello A510 owners,
After playing with patching google store using lucky patcher, my tablet start to bootloop...I was on Piccolo Rom,so I just flashed the rom again (wiped everything that could be wiped), but didn't worked, still bootloop...So I said to myself, let's make a fresh and clean install and get back to stock. I've download a stock rom, put it on my external SD Card and flashed it in CWN. I got a warning like I won't have recovery anymore after flashing but accept anyway, and start to flash...Tablet reboot and this is what I get :
Code:
erasing cache before sd update
SD update cmd : recovery
--update_package=SDCARD : update.zip
booting recovery kernel image
[COLOR="Red"]Recovery verified failed[/COLOR]
Then, I tried many stock rom I could find on the internet, still same error. I even tried with removing first line of the updater-script, nothing work...and I can't use adb anymore to push cwn again.
Any idea ? I really need help here ! :crying:

I guess u might flash the stock n still kept the cwm, so u can't enter the cwm anymore 'coz the bootloader was locked back.
Maybe u can try to unlock first, or u can consider to rewrite the recovery partition.

Rename update.zip to something different, CMW may not accept "command line" flashing.
Anyway if you can boot CMW (rename update.zip first!)
a) wipe dalvik-cache (under Advanced) and try to boot
b)if this fails- wipe data/cache (factory reset)

THX guys, I don't know how but I just format everything and reinstall cwn+rom, and it worked... I just lose all my datas on sdcard:'(
Sent from my A510 using xda premium

wiped, bricked tf300 now installing c/roms but still booting to twrp?

hello, last week i bricked my tf300, this is what happened...
i installed the energy rom along with the 4.2.1 bootloader, i was already using twrp 2.4.3.0 and it seemed to work fine for a while but then i had problems with a double screen after trying a different rom (cant remember which) anyway i tried the usual resets and wipes to to fix it but no joy. I then used the wipe data in bootloader thinking a full clean wipe would sort it but it just booted straight into twrp.
in twrp nothing will mount apart from system, ive used fastboot to flash various stock blobs, proper twrp img etc but even tho fastboot said everything flashed ok, i still boot into the old twrp which wont mount anything apart from system.
i then got an old 8 gig sd card and put stock roms and energy rom on root of the sd card , in twrp i mounted system but cant mount cache, data or sd card but strangely, i was able to copy the above roms from the sd card and move them to the mounted system partition which i was then able to install the energy rom with aroma installer , happy days i thought until after installation it rebooted straight to twrp again asking for password?
when i try to install stock roms by the above method it fails because cache isnt mounted. i think the twrp is corrupted, how do i fix this?
could someone with the know how tell me what im doing wrong,? should i full wipe again? should i wipe the twrp and how do i do this?
i am sort of a newb to this and any advice would be great

[Q] Cannot reboot system from Clockworkmod Recovery(Samsung Galaxy Mini 2 GT-S6500D)

Cannot reboot system from Clockworkmod Recovery
Hello, my phone detected that there is an update then i click the update after that it told me to confirm for reboot my phone enter CWM recovery then I clicked on reboot system now. It showed the Samsung Logo and the Splashscreen, but then enters the CWM recovery. I also tried pulling out the battery and then pushing the power button, but it still boots into CWM recovery. Any help? It looks like my phone got messed up and I can only use it in CWM recovery. Help is much appreciated. for everyone information i did root my phone a year ago.

So no problem at all.Wipe the data there and enter into mobile.It should work..

well the thing is i already tried that. i dont remember how many time i wipe it clean. then tried to reboot but still comeback to CWM recovery.

If there are any roms for ur device then fladh it .Of restore the nandroid backup...:thumbup:

wipe dalvik cache

[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.