Database Users

[Q] hard bricked and SOL it seems

I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.

neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
Can you get into the bootloader?

DaanJordaan said:
Can you get into the bootloader?
Click to expand...
Click to collapse
No. it's really gone. Just spoke with google and getting a replacement. I really can't do jack....bleep...with it.
all this for changing a font with Rom toolbox.

Yeah, bricked, but I'll buy it for 30

So it's permanently stuck on the Google logo and you can't access recovery or bootloader? No boot animation?
I wonder why something so trivial as a font change caused this... I've had font changes cause bootloops but never a bricked device.
Sent from my Nexus 7 using XDA Premium HD app

neiander said:
I really think I am going to be out of luck but here is my problem.
I was simply changing fonts using Rom toolbox on my rooted N7.
Rebooted and it boot looped. I let it go for a while but nothing. So i tried to reboot into recovery and i am stuck on the google logo screen. Nothing. Happens.
I can't do anything.
Any suggestions?
S.O.L. i think.
Click to expand...
Click to collapse
You aren't alone.
That app is made by the ROM Toolbox dev, lotsa complaining in the reviews about it bricking. You did connect it to your PC via USB and tried pushing the needed bits and starting from scratch didn't you? I'd even try one of the toolkits available for rooting and recovery.

After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks

As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.

I'm glad I was able to fix it. My computer was not able to recognize the device while I was on the fastboot screen (android laying down.) THe only other screen I ever was able to get was the bootlooping screen. By chance I realized the computer was connected to the device only if it was on the bootloop screen. When I saw that, then I was cooking with fire.

Sounds like you should install your fast boot drivers
Sent from my Galaxy Nexus

I've only just got my nexus (first tablet) had it for two weeks, decided to root mainly because I hate adverts popping up everywhere, anyway I digress. I purchased toolbox pro for my hox ages ago and even though I haven't installed it, for the last few days I've been thinking of it so cheers buddy for bringing this to my attention
Sent from my Nexus 7 using xda premium

player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
Best. Idea. Ever.
Also, with a Nexus device at least that was a shot. Many others would keel over and die for good if that sort of stuff happened.

neiander said:
After several several hours, I was able to reboot into recovery. It was very tricky and I had a bit of luck on my side. I have since vowed not to use rim toolbox again. Thanks
Click to expand...
Click to collapse
Cool, and agreed with the above. If you can see stuff on the screen, it's technically not bricked.
Bricked an N7 once, it was stuck in APX mode, the lowest recovery mode for tegra chips I believe.
At the time there was no way recovering from it using NVFlash, maybe there is now though.
Mind telling us how you got yours back to life? Just curious
Cheers

all nowellel
Was really luck. I was working on trying to get the computer to sees the device. Trying to load drivers. Anything I could do. The computer kept saying no adb device plugged in. Finally after deleting drivers and reloading drivers, I plugged in the device while it was bootlooping and heard the correct "connected" sound and saw the device in device manager. Then with toolbox, was finally able to reboot into recovery and wipe and reinstall rom. Didn't lose anything in the process.

Oh, the thing that was really the biggest mind blower was that there were 2 screens I could get to, bootlooping screen and what appeared to be the correct fadtboot screen, the computer would not recognize the device when I was on the fastboot screen. That was why I thought I was SOL.

player911 said:
As long as you see something on the screen, it is not bricked.
I bricked my first N7 by drunk flashing an updated Galaxy Nexus bootloader on my N7. Needless-to-say the backlight wouldn't even light up. Even then it technically isn't bricked. I could use the NVedit tool if I had the right files and commands.
Click to expand...
Click to collapse
What is this NVedit tool? I cant seem to find that anywhere. I'm working on my buddy's N7 32GB Wifi, he tried to revert to stock from having CWR and CM10.1 using the Nexus Root Toolkit and now there is that problem happening you mentioned, backlight wont light up and computer doesnt recognize the device and I cant get into the bootloader either. Already checked the Screen itself and it works (disassemble and connected to my N7) and the battery has power, just no luck.

Need help, bootloop..

I installed LCD Density app from the market. Changed settings from 320 to 300 and it said to reboot phone. This put my phone into bootloop with LG logo and led flashing. My phone is Verizon, rooted with TWRP installed. I can get into TWRP but hadn't made a backup yet. Any ideas? I tried wiping will in TWRP and then rebooting but still got the bootloop. If it matters, I have a Mac. Thanks for any help...

Factory reset in twrp. Then install the rom again should work. Changing dpi can have adverse effects ☺
Sent from my LG-D800 using Tapatalk 4

How can I get the Rom onto my phone? I have a Mac?

did you delete the rom from the sdcard? if it isnt there anymore then you will need to adb push it. I dont have a mac so cant be of help on that side of it.

I was running stock Rom. Only mod was black notification bar. I hadn't downloaded any roms yet. Don't think I can get adb to recognize my phone as I can't select Ethernet connection. Any ideas?

I don't have a Mac, so I cannot help you with that. And I really hope you get this rectified with the help of the community here. That being said, please know that this next comment is not being directed solely towards you, but to a whole lot of others as well.
Order of life in customizing your phone :
1. Root method applied
2. Install appropriate custom recovery
3. Boot to custom recovery
4. MAKE A BACKUP. PERIOD! Absolutely no reason not to do this step. It will save your butt or your phone in the future, when, not if, you find yourself in a bad situation.
5. Have fun with your phone, but only after you understand what you are doing, and accept the possibility of messing up your phone. $hit happens when it's least expected.
I didn't mean for this to sound harsh, but it is really important to understand.
Anyone with a Mac that can help this person out?
Sent from my Nexus 10 using XDA Premium HD app

Yeah I have always made a back up in the past. I'm so annoyed at myself for not doing it. Any suggestion on how I can either get a rom onto my phone or edit the build.prop back to stock?

Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.

black05x5 said:
Got it fixed! Was finally able to connect to my Mac. Then put a rom on the phone using ADB and flashed the rom.
Click to expand...
Click to collapse
Excellent.
Thanks Devs. From my VZW G2.

trickster2369 said:
I don't have a Mac, so I cannot help you with that. And I really hope you get this rectified with the help of the community here. That being said, please know that this next comment is not being directed solely towards you, but to a whole lot of others as well.
Order of life in customizing your phone :
1. Root method applied
2. Install appropriate custom recovery
3. Boot to custom recovery
4. MAKE A BACKUP. PERIOD! Absolutely no reason not to do this step. It will save your butt or your phone in the future, when, not if, you find yourself in a bad situation.
5. Have fun with your phone, but only after you understand what you are doing, and accept the possibility of messing up your phone. $hit happens when it's least expected.
I didn't mean for this to sound harsh, but it is really important to understand.
Anyone with a Mac that can help this person out?
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
It amazes me when people don't create a backup.

[Q] HELP!!! Nexus 4 stuck in what i think is "recovery mode"

Hello All,
About 2 days ago i tried to root my google nexus 4, I dont know what i did, but now when i turn it on it shows the google logo then goes to where it shows an android with a red exclamation mark, does anyone know how this can be fixed, any help would be much appreciated!!

Can you be a bit more specific on what you did? Or what guide you followed?
Rooting is quick and easy on a nexus
fastboot oem unlock
fastboot flash recovery nameofrecovery.img
Then flash ROM of choice in recovery
Reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app

Ok, i had successfully rooted my phone, i then went to put on a new rom so i could use OTG storage. That got me completely stuck, i tried toget back to my normal phone but didnt know how. I foolishly went into recovery mode, and wiped everything off it. and just now i cant even do anything it just has a red light flashing at the bottom, i hope this has helpt in some way.

Do you have a custom recovery? Use adb sideload to flash the ROM, or if you have a working otg cable this should be fine too
Sent from my Nexus 7 using XDA Premium 4 mobile app

UPDATE: The red light has gone (was just low on power) But the phone is still stuck in recovery mode. i have tried to "apply update from ADB" with my mac but it doesnt work and im not sure if i am doing it propperly.

I am pretty new to this kinda stuff, so i dont know what a custom recovery is, and i honestly have no idea what to do, im not really bothered about the root anymore i would rather just have my phone back to normal.

Please dont take this the wrong way and I mean no disrespect, but maybe we should just get your phone up and running and then maybe a few months from now after you've done a whole lot of reading you can consider rooting again. The n4 isn't the most expensive phone in the world but it would still be a shame to brick it, as much as I believe all androids are best to be rooted the user really needs to understand fully what s/he is doing, 95% of "help my device is bricked" threads come from lack of homework, which is easily 100s of threads a day across xda alone
OK, sorry for the lecture I've just ran into this a lot lately, and I'd be glad to help
I try not to use apple products as a whole so I can't say for sure why its not connecting with adb, is this for sure set up properly? As in has adb or fastboot worked fine in the past? Also is device currently unlocked? By a custom recovery I mean nonstock, not an oem, like twrp or clockwork.
If you want root let's download the latest twrp image for the n4, if you want factory than download latest from here
https://developers.google.com/android/nexus/images?hl=de
Let me know how you want to proceed
Sent from my Nexus 7 using XDA Premium 4 mobile app

http://forum.xda-developers.com/showthread.php?t=2010312
This will get u up and running.
Next time make sure u know what u are doing.
Credits: efrant
Sent from my Nexus 4 using Tapatalk

Sprint LS980 up ****s creek without a rom

Hey guys rookie mistake went to flash a new seemingly successful rom and forgot to make a back up first. Now my phone is on but black screen. I can get into recovery but I have no backup. Also when I connect my phone to the computer it no longer recognizes it. I have all up to date drivers. They worked yesterday. Ive been reading about bricked g2 on boot loop and other variances and trying different things all day with no success. Any help or advice would be greatly appreciated. Thank you in advance.

bump
This may have been discussed before. Ive searched here and google. Plenty of horror stories and the only one ive seen with the same problem never got a fix or least didnt reply on the boards about being fixed. My phone will not turn off no matter what I do. The screen is slightly lite up and will only boot to recovery(where I have no backups) and download mode where it basically does nothing and will not connect to my computer reguardless of it having the right drivers. So I have no way to my knowledge to flash a new/stock rom. I even got desperate and did a hard reset. Changed nothing but deleted the original rom I was attempting to flash.

Install pda net driver or koush drivers.
Sent from my LG-D800 using Tapatalk

Ok I'll try that. Ty
Sent from my SM-T217S using xda app-developers app

So confused now... Bricked? Not bricked? Please help?

OK, so here is the current situation. I've been searching, reading, and following different recovery procedures, but nothing seems to be working as it should, so now I'm posting here to get some guidance as to how to proceed.
I have a Verizon VS980. I had Malladus ROM 1.2.4 with furnace 0.1.0 kernel installed. I have Philz Touch recovery. I wanted to try out Sliding Lockscreen, but when I got installed and tried to reboot, my phone went into a boot loop. I booted to recovery and tried to restore a backup, but it said it couldn't find any backups... although I did have backups. This is when I started getting confused. I tried wiping cache and dalvik, no effect. I read through a bunch of threads here, tried a bunch of things that worked for other people, etc. Finally said screw it and did a factory reset through Philz. No joy. Tried several different methods to revert to stock. No joy. Oy vey.
So now the bottom line is it only gets to the LG screen with the LED doing its color changing thing, and thats it. Stops there. I CAN boot to Philz Touch recovery by power+vol. down, go through the factory hard reset menu, then it gets to Philz. Now, there has got to be a way to regain my phone from here. Like I said, I tried the 2 different methods to revert to stock... I can get all the way to the point it supposed to start flashing the stock ROM with the tot file method, but it just doesn't start flashing the ROM when its supposed to. Is there a way I can get a ROM from my computer to the phone? When I enter download mode (vol. up while plugging in USB), it says updating firmware, warns not to unplug while its updating, but its not doing anything at all, and at the bottom of the screen in a box it says something like "b100" in the top left corner of the box, and "ROOTED" in red letters at the bottom.
So, what in sam hell is going on with my phone, and how do I fix it? Is there a way to get either the stock ROM or Malladus from my computer to the phone so I can re-flash? I'm thinking thats all I need to do to get out of this.
Please... someone help a totally confused and now smartphone deprived guy? Please?

Dude, are u running the flash tool on pc while trying to flash stock rom? Just booting into download mode won't help. Or u can transfer a rom to a USB drive, connect it to ur mobile via OTG cable and then flash the rom via recovery
Sent from my LG-D802 using XDA Premium 4 mobile app

jaidev.s said:
Dude, are u running the flash tool on pc while trying to flash stock rom? Just booting into download mode won't help. Or u can transfer a rom to a USB drive, connect it to ur mobile via OTG cable and then flash the rom via recovery
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to revert to stock. After stepping away from the computer and phone, taking a cig break and a few deep breaths, I reread the tot revert instructions for 127th time. Found my mistake... I kept forgetting to change the com port to 41. Did that, revert worked just like it was supposed to for people who are not blind idiots who miss crucial little tidbits like that. I can't believe I kept missing that. COM Port 41 is ingrained in my memory forever. I may have to get a tattoo of it now.
I went so crazy trying to find the solution (yeah, didn't think of a flash drive either) because I was so determined not to have to resort to posting in the forum. The moment I give up... boom, I figure it out. Live and learn.....
Well, on to re-rooting the phone, re-flashing Malladus, and re-downloading all my crap...

Lol, happy to know that ur phone is back working, cheers mate
Sent from my LG-D802 using XDA Premium 4 mobile app