Hi,
I flashed successfully cyanogenmod for the HDX 7 and everything worked great. Than I updated cm over the air and within the update the device rebooted (battery was full). Since that I only see the kindle logo for about half a second and get an instant reboot. So the device doesn't show up if it's connected to my pc. Any ideas what I could do to get adb working?
Regards,
Alex
GM_Alex said:
Hi,
I flashed successfully cyanogenmod for the HDX 7 and everything worked great. Than I updated cm over the air and within the update the device rebooted (battery was full). Since that I only see the kindle logo for about half a second and get an instant reboot. So the device doesn't show up if it's connected to my pc. Any ideas what I could do to get adb working?
Regards,
Alex
Click to expand...
Click to collapse
Which CM version?
If bootloader is unlocked you should be able to access TWRP recovery via <power>+<vol-up> from a cold start. If running Safestrap then the device is likely bricked with no hope of recovery short of board replacement.
Davey126 said:
Which CM version?
If bootloader is unlocked you should be able to access TWRP recovery via <power>+<vol-up> from a cold start. If running Safestrap then the device is likely bricked with no hope of recovery short of board replacement.
Click to expand...
Click to collapse
Thanks for the quick reply. To be honest it was like 6 months ago and I hadn't any time to get my hands on it until now, so I don't remember the cm version, but the bootloader is unlocked. Also using <power>+<vol-up> results in the same behavior, seeing the logo for 1/2 second and than bootloop: ~15 seconds black, 1/2 second logo, repeat.
GM_Alex said:
Thanks for the quick reply. To be honest it was like 6 months ago and I hadn't any time to get my hands on it until now, so I don't remember the cm version, but the bootloader is unlocked. Also using <power>+<vol-up> results in the same behavior, seeing the logo for 1/2 second and than bootloop: ~15 seconds black, 1/2 second logo, repeat.
Click to expand...
Click to collapse
- <power>+<vol-up> must be initiated from a cold start; if needed long press <power> (up to 20 sec) to fully power down device
- if response is identicial you have lost your custom recovery (likely TWRP) which is not a good sign ...
- at full power off try <power>+<vol-down> to see if device will enter fastboot mode
- if fastboot works *AND* the device is truly unlocked it is possible to reflash TWRP and (later) the custom rom of your choosing
- if still no joy the filesystem may have become corrupt; unfortunately, fixing it is above my pay-grade ...
Davey126 said:
- <power>+<vol-up> must be initiated from a cold start; if needed long press <power> (up to 20 sec) to fully power down device
- if response is identicial you have lost your custom recovery (likely TWRP) which is not a good sign ...
- at full power off try <power>+<vol-down> to see if device will enter fastboot mode
- if fastboot works *AND* the device is truly unlocked it is possible to reflash TWRP and (later) the custom rom of your choosing
- if still no joy the filesystem may have become corrupt; unfortunately, fixing it is above my pay-grade ...
Click to expand...
Click to collapse
Ok doesn't worked. I have an other one with locked bootloader and broken screen, I will try to disassemble the one with the boot loop, because it isn't possible to turn it off, even if the battery is totally empty. Maybe if I can unplug it it will work. Otherwise I hope I'm able to exchange some parts to get one working one. Thanks again for your help.
GM_Alex said:
Ok doesn't worked. I have an other one with locked bootloader and broken screen, I will try to disassemble the one with the boot loop, because it isn't possible to turn it off, even if the battery is totally empty. Maybe if I can unplug it it will work. Otherwise I hope I'm able to exchange some parts to get one working one. Thanks again for your help.
Click to expand...
Click to collapse
FYI - full power down is not possible on HDX models when device is tethered to an active host. Disassembly will be a challenge (especially on 7" model) due to copious use of glue. Cracked screens are common. Good luck!
Related
I used a fastboot cable to attempt to load a factory ROM to a Kindle Fire model p48wvb4 in order to fix some flakiness I had with the device, and now I cannot boot, as the device goes to the fastboot screen whether the cable is connected or not. I got this device used, and was under the impression that it was a 2nd gen HD but maybe it is HDX.
Anyway, I used KF First Aide to attempt to load 10.2.3 on it, and everything appeared to operate fine. However it reboots directly to fastboot screen, and I cannot find a way around this. I've done the power switch reset thing, have redone the KFFA load several times, and nothing helps.
Please help!
Obarryon said:
I used a fastboot cable to attempt to load a factory ROM to a Kindle Fire model p48wvb4 in order to fix some flakiness I had with the device, and now I cannot boot, as the device goes to the fastboot screen whether the cable is connected or not. I got this device used, and was under the impression that it was a 2nd gen HD but maybe it is HDX.
Anyway, I used KF First Aide to attempt to load 10.2.3 on it, and everything appeared to operate fine. However it reboots directly to fastboot screen, and I cannot find a way around this. I've done the power switch reset thing, have redone the KFFA load several times, and nothing helps.
Please help!
Click to expand...
Click to collapse
I'm currently having the same issue. I've noted that the soldering on the fastboot cable I'm using is loose, so that may be the case, but regardless of if I'm using the cable or not, the device STILL boots to fastboot.
Bumping for interest!
avery.deloach said:
I'm currently having the same issue. I've noted that the soldering on the fastboot cable I'm using is loose, so that may be the case, but regardless of if I'm using the cable or not, the device STILL boots to fastboot.
Bumping for interest!
Click to expand...
Click to collapse
Same here. No matter how I try to reboot the device (long press, etc), it boots to fastboot after briefly flashing a red screen. Trying to reboot through software, as with KFFA, does nothing - no reboot at all.
Obarryon said:
I used a fastboot cable to attempt to load a factory ROM to a Kindle Fire model p48wvb4 in order to fix some flakiness I had with the device, and now I cannot boot, as the device goes to the fastboot screen whether the cable is connected or not. I got this device used, and was under the impression that it was a 2nd gen HD but maybe it is HDX.
Anyway, I used KF First Aide to attempt to load 10.2.3 on it, and everything appeared to operate fine. However it reboots directly to fastboot screen, and I cannot find a way around this. I've done the power switch reset thing, have redone the KFFA load several times, and nothing helps.
Please help!
Click to expand...
Click to collapse
if that is your model number you are in the wrong forum and need to go
here http://forum.xda-developers.com/kindle-fire-hd
hope this helps you
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
How to recover your device from almost any kind of brick
Requirements
Check the pinned sites
Flashtool
FTF of choice for your device
2 Rubber bands (I am serious but only if your device has no response)
Step1
unplug your device from anything
open flashtool on your pc
plug your cable into your PC
do not plug the cable into your device
Step2
Hold your power button and your volume up button at the same time
your device should buzz 3 times
(this should take a few secconds)
if it does not take a few seconds then you need to put a rubber band around your device holding your power button and your volume up button, DO NOT LEAVE MORE THAN IT NEEDS TO BE LEFT, wait patiently for your device to buzz 3 times
Step 3
once your device has buzzed 3 times you are free to flash a FTF as your device is powered off
step4
if you dont know how to flash a FTF but have gotten as far as installing flashtool,Z2 drivers and downloading a FTF FOR YOUR DEVICE... then folow this step
within your flashtool window click on the lightning icon at the top left
select flashmode
navigate to where you downloaded your FTF (OR put your FTF in your /flashtool/firmwares folder)
select your FTF
Flashtool should give you a prompt to plug in your device
hold volume down and plug in your device
step5
wait for it to finish flashing
step6
your device is now recovered, enjoy...
Sent from my D6503 using XDA Premium 4 mobile app
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
carloscarvalho said:
I bricked my phone doing this:
- root with eazyroot
- installed dual recovery
- full wipe
- install carbon + gapps
bum... bricked
i cant even see the Sony logo
Then i use the method mentioned by Envious_Data and my phone returned from hell
Good luck dude... hope u can fix that
Click to expand...
Click to collapse
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Unbalanced said:
Okay, I'm not sure exactly what you'll need to know to help, so I'll just tell you what I think is important....
Current situation:
- If I boot the phone normally it freezes at the SONY screen and goes no further.
- If I attempt to boot into recovery mode, it loads the CWM screen (logo in the middle with instructions at bottom), but no actual menu or options. After about 5 seconds, this screen disappears, the phone reboots and then gets stuck on the SONY screen.
- If I connect the phone to the computer in Flashmode Flashtool recognizes it as being connected, but regardless of what I do, after about 2mins the phone reboots, loses connection with the computer, and freezes on the SONY screen as before mentioned.
- If I connect the phone to the computer normally while stuck on the SONY screen, the PC recognizes it though doesn't allow me to do anything to it, and Flashtool says I need to install drivers (I have installed every driver that comes with Flashtool).
How I got here:
- I've rooted the phone
- I've flashed Z2_DooMLoRD_AdvStkKernel_FW-438-v05
- I've unlocked the bootloader (via Flashtool)
- I've installed [Rom][Unofficial]Slim Rom 4.4.4 based on CM11.0, ROM for the Sony Xperia Z2
The phone was okay up until this point, however I wasn't happy with the ROM so I tried to reboot into recovery mode to wipe and install Carbon. This is when the trouble began.
Now it seems I can't do anything :/
Please help. This phone is literally 3 days and it looks like I've completely screwed it >.<
Thanks!
Click to expand...
Click to collapse
Okay I used to get into this kind of situation when I used HTC One, and what I did is try to flash recovery and unlocked bootloader again "using command".
And problem has solved. I think it is pretty much same for Xperia Z2, (ftf flashing method is not useful in this situation.)
I hope you know how to flash custom recovery using command. If not I think there is some thread that explains how to flash recovery and unlock the bootloader using command, if you can't find it plz let me know. Hope you have recovered phone next time I check this thread. Good luck mate :good:
HussainQ said:
You didn't unlock your bootloader?
Isn't Carbon ROM AOSP?
If it is, it needs an unlocked bootloader or it will get bricked
Click to expand...
Click to collapse
Yeah... I know... A newbie mistake...
I Just follow the instruction available in the site. And there is just "root and recovery"
No bootloader mentioned
But u r right... Thats the reason
Sent from my awesome Xperia Z2 using XDA Premium
@Envious_Data: Bro, thank you so much for that. I my z2 have only 1 day, and i god damn it bricket, that even screen wasn't working. So for other people who had bad luck: first I rooted using Community Rootkit, then unlocked bootloader, and at the end I flashed via fastboot boot.img which one i extracted from zip file from this thread - http://forum.xda-developers.com/showthread.php?t=2702001. Command prompt showed that it works. I rebooted phone sony logo showed up, but then disappeared, and then was crying and sorrow. Three years of rooting,flashing without any problem, and now that. Thank you one more time, that's a great lesson
I do have some advice for people
1. Try to find help threads for your device, i have one for Z2 that gives some useful info, ill be adding more soon
2. Once you have got the jist of flashing then try to expand on that, i do recomend roms first because its harder to brick from a rom than a kernel or a non stock based rom such as CM11 or AOSP
3. Always keep a stock flashable rom (kernel too if you have a unlocked bootloader) on your device
Sent from my D6503 using XDA Premium 4 mobile app
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
discipuloosho said:
I too hard brick my Z2, only solution is the same as for Z1 http://forum.xda-developers.com/showthread.php?t=2646405
Sorry friend :`
Click to expand...
Click to collapse
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
ghostofcain said:
A hard brick is by definition not recoverable by the user, requiring either special equipment ie jtag or RMA to fix.
I am quite surprised, and intrigued, at people flashing cm or AOSP on a two day old phone, was Sony experience that awful? You'd maybe be better served with a nexus device.
Click to expand...
Click to collapse
True friend, but I had an Xperia MT11i (Neo V) and all (fastboot, flashtool, CM, etc) was always no problem.
I've taken today for service (with CM11 (and cm kernel)) and see what happens ...
@Unbalanced I don't think your Z2 Hardbricked, if it were not ignite. Luck
Hi all, if it helps I did the same thing last night. Flashed CM11 without a recovery and wanted to revert back to my nandroid backup. I flashed doomloards kernal via fastboot. CWM started with no menu and just bootlooped. I then thought it may be a CWM issue, maybe no file structure or something. I flashed XZDuelKernal via fastboot and booted into CWM again and experienced the same issue. As this is a duel recovery, I then booted into TWRP. Recovery started and I was able to flash another zip then recover my nandroid backup. If you get this menu issue with CWM,try and flash a TWRP recovery and boot into that.
Also, as mentioned before, this is not a hard brick. It's just incompatible software and is easily fixed if you know what you are doing and prepared (nandroid backup, knowledge about fastboot and flashmode, ftf, recovery, unlocked bootloader).
Sent from my D6503 using Tapatalk
Stuck
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
scoobard said:
Hi.
I believe (although I'm not sure) that I have bricked my Xperia Z2 in some way. When I press the 'power' button, the phone vibrates once and does nothing. I have tried to hold the 'power on' and 'volume up' buttons for a long time (half an hour with rubber bands), and nothing happens (as explained earlier in the thread).
I believe I am able to access the fastboot though, through 'Terminal' app on OSX. From there I can " ./fastboot devices " and get confirmation that they have loaded. I am also able to perform other tasks from here, such as flashing a recovery and " fastboot erase system -w " (which I believe may have got me to where I am now). I've been following things on this thread: http://forum.xda-developers.com/showthread.php?t=2277112
I have no experience in rooting or flashing, but attempted to flash a custom ROM because there were step by step instructions.
Anyway, I firstly used Sony's rooting procedure whereby an unlock code is generated etc. Eventually I gained access to the Recovery mode (via clockwork), and wiped the phone, installed the ROMAur zip and GApps zip. However, when I booted, it kept giving me warnings saying the apps were crashing. I've since gotten lost completely and need someone to help bail me out.
I'm hoping I can sort things out via the fastboot.
Thanks in advance for your help.
Click to expand...
Click to collapse
Download ftf file for your device and flash via flashtool.
mariosraptor said:
Download ftf file for your device and flash via flashtool.
Click to expand...
Click to collapse
Thanks for the quick reply Mario. I did just that (using Kuwait FFT for the D6503), and everything appears to be back to normal. Unfortunately I still have not got root access and can't remove the bloatware. As for the bricking issue however, it's solved. Thanks.
I am having an issue. Updated kindle fire 6 hd 4th gen to 5.0, downgraded to 4.5.3. Installed king root, rooted device, installed flashify, flashed openrecovery-twrp-2.8.6.0-ariel.img, rebooted. Now I am stuck rebooting . If plugged into a computer loads to the amazon logo, shuts down, loads to the logo repeat.
I have tried to fast boot by correcting drivers in device manager for the mtp whatever and constantly spamming the fast boot string.
I have used adb to see if a device ever loads and it doesn't.
Windows makes the sound that a new device is connected for about 15 seconds then will make the noise that a device has been disconnected as the fire reboots. I want to say it is a soft brick since it attempts to load and is communicating with windows to some degree. I have searched for two days and tried KFFA and an assortment of other tools. Any thoughts or assistance is greatly appreciated. It was only 60 bucks so not really worth sending it in to someone for repair. Also since it was brand new amazon is sending a replacement so this thing is now simply a toy to learn on.
When it can't get past the Amazon logo, there is no hope. OS 4.5.3 should be able to boot TWRP after OS 5.0. Where did you get the 5.0 file? Is it possible you got updated at some point?
ardorcalenture said:
I am having an issue. Updated kindle fire 6 hd 4th gen to 5.0, downgraded to 4.5.3. Installed king root, rooted device, installed flashify, flashed openrecovery-twrp-2.8.6.0-ariel.img, rebooted. Now I am stuck rebooting . If plugged into a computer loads to the amazon logo, shuts down, loads to the logo repeat.
I have tried to fast boot by correcting drivers in device manager for the mtp whatever and constantly spamming the fast boot string.
I have used adb to see if a device ever loads and it doesn't.
Windows makes the sound that a new device is connected for about 15 seconds then will make the noise that a device has been disconnected as the fire reboots. I want to say it is a soft brick since it attempts to load and is communicating with windows to some degree. I have searched for two days and tried KFFA and an assortment of other tools. Any thoughts or assistance is greatly appreciated. It was only 60 bucks so not really worth sending it in to someone for repair. Also since it was brand new amazon is sending a replacement so this thing is now simply a toy to learn on.
Click to expand...
Click to collapse
You probably Flashified TWRP into your boot partition (instead of recovery). Since TWRP not signed, it will not boot. You can probably get into 4.5.3 recovery by pressing Pwr + Vol+ during boot, but that's not going to do you much good. Anyway, if Amazon can get you a replacement, go for it!
DoLooper said:
When it can't get past the Amazon logo, there is no hope. OS 4.5.3 should be able to boot TWRP after OS 5.0. Where did you get the 5.0 file? Is it possible you got updated at some point?
Click to expand...
Click to collapse
When I say 5.0 I am talking generic. I updated it to that version in order to downgrade the OS.
bibikalka said:
You probably Flashified TWRP into your boot partition (instead of recovery). Since TWRP not signed, it will not boot. You can probably get into 4.5.3 recovery by pressing Pwr + Vol+ during boot, but that's not going to do you much good. Anyway, if Amazon can get you a replacement, go for it!
Click to expand...
Click to collapse
Yeah I tried that. I get reboot or erase everything and restart. Neither works.
Afternoon
I have a Lenovo 7" tablet which is sticking on boot...to describe:
tablet off, charge screen working fine (green battery)
can get into menu to select fastboot mode or recovery
fastboot works, at least screen appears!
recovery shows dead android/no command screen - how to access recovery?
booting up, get inital orange logo then a 'bing' and start of boot but then freezes on the second logo
tablet not visible on PC, even in fastboot mode (have installed drivers)
I'm looking to get this going but am a bit stumped. I tried reinstalling firmware but can't get SPF Tools to work with any available scatter files; I would like to install TWRP (I found a potential image file on XDA) but can't do this until the PC recognises it....and I'm going round in circles now....any suggestions gratefully received. :good:
Update
OK, post was maybe a bit premature - I've kinda fixed my issues.
Managed to get into recovery after watching many videos (most of which were wrong, but hey-ho, got me on the right path!). At dead android screen, press and hold in power + vol up + vol down together (there is a bit of knack, turn it on its side with buttons facing up seems to be easiest) - this fires up the recovery screen (android standard recovery).
I managed to get over my bootloop issue by performing a data wipe/factory reset and cache wipe, then restarted fine.
As this was a secondhand tablet (my usual purchases - good condition bootloops!) - once it booted up I got into the set-up screens only to discover a Google lock issue. I ran the FRP unlock from here: https://androidfilehost.com/?fid=11050483647474832839 using the instructions from here: http://forum.gsmhosting.com/vbb/f958/lenovo-tab-4-7-essential-tb4-7304f-frp-remove-2322527/ (Voltrans second post, not the original one which has a 404 error on the download site). This removed the FRP lock straight off and now I have a functioning tablet.
I'm probably going to try getting custom recovery on so will see how that goes - I'll post back
and...that's all folks....
OK, despite finding a TWRP recovery online https://twrpbuilder.github.io/downloads/twrp/#441 and downloading it, can I get the fastboot unlocked? no.
Apparently Lenovo locked them all up and threw away the key, so nothing more can be done here.
I tried various iterations of fastboot oem unlock and fastboot flashing unlock, and nothing works, just get an error - and yes, I did put developer options on, OEM unlocking ticked and USB debugging active.... :silly:
So, unless someone can point me in a direction on how to unlock it - I've reached the end of the road with this one
Hi Fols
completely stuck - have had pixel experience on Xiaomi Note 5 PRo for 6 monts no issues have just tried to OTA update - it seems it was doing it but stopped at the TWRP screen - there are NO BUTTONS or prompts available just the TWRP initial screen - NO interactive elements - it doesnt matter whether i Power off / Power OFF while hoding UP or Power off while Holding DOWN - it ALWAYS shows MI logo / bootloader unlocked and then Teamwin screen appears nothing happens - simply not good enough by the Pixel Experience team to advertise as capable of doing OTA updates without testing it works first - HELP !! Please if you can - as it stands ive lost all my Data
Anyone ?
Fastboot boot recovery.img
When the answer is to short then look here
✏ How to use TWRP without flashing it (e.g. for Backup)
I already posted it here, but I’m pretty sure many people aren’t aware of this 😉 I found a way to boot TWRP without flashing it, so you only boot it from your computer, do what you want and as soon as you shutdown your phone, it’s just as it was before. 🙂 TWRP is a great tool for many things...
forum.fairphone.com
Test the orangefox img
hi folks thank you - got it sorted with Orangefox - but not until i i ballsed up the first attempt by trying to set filesystems to that new f2fs one , but got it done and didnt lose my photos in the end - (thank heavens for the Google ecosystem and Android) - thanks @joke19 for posting
joke19 said:
Fastboot boot recovery.img
Click to expand...
Click to collapse
I have exactly the same issue on my Redmi note 5, after auto rebooted by the update, the system stucked at the TWRP inital screen;
I tried to force shut it down by holding power button, then holding volume down botton, fastboot screen appeared, but nothing changed or happened in windows device manager, so fastboot commands are not available.
I also tried to drained the battory by leaving it alone until the TWRP initial screen off, after charging it for a few minutes, it auto powered on, loaded into TWRP initial screen, stucked again, even I booted it into fastboot mode again, windows device manager had no any android device or unrecognised device appeared. I guess that the usb interface was disabled during the OTA update.
My cell phone now is an iron brick...plz help...
dumbledon said:
hi folks thank you - got it sorted with Orangefox - but not until i i ballsed up the first attempt by trying to set filesystems to that new f2fs one , but got it done and didnt lose my photos in the end - (thank heavens for the Google ecosystem and Android) - thanks @joke19 for posting
Click to expand...
Click to collapse
It's good for you.
The Orangefox didn't adapted it to Redmi note 5, my cell phone is going to be a brick 4ever...