Database Users

I think I bricked my NS

I was flashing CM7. This is what I did:
Rooted, ClockworkMod v3.0.0.5 from Rom Manager.
From recovery did a BackUp (seems useless because it doesn't do anything.)
Wipe data/factory reset
Wipe Cache partition
Install zip from sdcard - selected cm7 - got a Status Error 7
Now the phone won't boot, stays on the Google screen, I can get into the recovery though.
Any ideas? I am downloading the Stock 2.3.3 image.
Thanks!

restore your backup.

irishrally said:
restore your backup.
Click to expand...
Click to collapse
I tried doing that from ClockworkMod, gave me an error, it was a ridiculously small file, doesn't seem like a backup.
Even the stock gives me a Status Error 7.
Any ideas?

you didnt brick, just download a a new rom, sounds like it was a bad download.. if the phone shows a screen it isnt bricked...

shabbypenguin said:
you didnt brick, just download a a new rom, sounds like it was a bad download.. if the phone shows a screen it isnt bricked...
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get. For both Stock 2.3.3 and CM7. I've tried multiple times.

right did you re download it and copy it back to the phone or just going off the rom you downloaded already? if so worst case shouldnt odin work?

shabbypenguin said:
right did you re download it and copy it back to the phone or just going off the rom you downloaded already? if so worst case shouldnt odin work?
Click to expand...
Click to collapse
I'm downloading it again. Should I rename it to update.zip? Odin, that's the software right?

I think your problem is because you are using the clockwork mod for I9020, where as for rogers you should be using clockwork for i9023 -- at least this was my case, I have i9020a rogers
you can get it from this link 2nd file.
after using this one you shouldn't be getting "E: can't mount cache" and you shall be able to repeat rooting/flashing steps.

crypticsorr0w said:
I think your problem is because you are using the clockwork mod for I9020, where as for rogers you should be using clockwork for i9023 -- at least this was my case, I have i9020a rogers
you can get it from this link 2nd file.
after using this one you shouldn't be getting "E: can't mount cache" and you shall be able to repeat rooting/flashing steps.
Click to expand...
Click to collapse
I was feeling so, either the ROM or the recovery. I'm just flashing the recovery, thanks for your help.
Also, how do I manually install ClockworkMod?

What is your computer OS? do you have android sdk?
In general everything you need is in this post
http://forum.xda-developers.com/showthread.php?t=955719

crypticsorr0w said:
What is your computer OS? do you have android sdk?
In general everything you need is in this post
http://forum.xda-developers.com/showthread.php?t=955719
Click to expand...
Click to collapse
It worked, I used fastoot and Terminal. Worked like a charm. Thanks again.

[Q] Is my phone completely bricked? Pixelated screen when I boot my rooted Defy XT

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Motorola Defy XT: So what does it mean when this is the only screen your rooted Defy XT can make??? Once i turn it on this the first and only thing that appears on the screen but after a few min. my phone starts being a phone and everything, well at least making all the sounds it used to and receiving messages still, but the screen is kaput. Is my phone Bricked for good? or is there anything I can do? Please someone help!!! :crying:

Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app

arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks for the response!
I've actually only just rooted my phone. I haven't put any rom on it. It is still running the factory gb on it. Only rooted it so that I could run a screen shot app on it, and was probably eventually going to rom it once I became a little more knowledgeable about doing so. But everything was working fine with the phone after rooting it, for about 2 weeks even, but yesterday I just pulled out my pocket after coming out of the grocery store, clicked it to unlock it and there was that screen. Tried everything to get rid of it, took the battery out, plugged it in the wall, my computer. Nothing. Weird thing is though, after 5 min of being on, it will continue being the phone that it is, making all its regular sounds and receiving messages and notifications, just with that pixelated screen, which leads me to believe that it might be a hardware/bios problem, or if phones even have bios. This is my first smart phone so I'm just really starting to get to know it. Again, appreciate all help given! Just bummed this phone I've had for a month has already crashed on me.

arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Also forgot to mention I tried a factory reset by memory but with no visual it's hard to see if I'm even doing anything.

Search for your stock from and flash it
You can also use the custom from like miui v5 for defy/defy+ http://forum.xda-developers.com/showthread.php?t=2232947
Do you have a cwm recovery? Or you have to use the fastboot method
Sent from my A11 using xda app-developers app

[Q] Recovery data?

Ok so im running twrp 2.6 on beanstalk 4.3 and i went to make a back up and its showing me that wanting to back up system,data, and boot but whats got me is the data is 6266646mb what is that all about?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danebryan18 said:
Ok so im running twrp 2.6 on beanstalk 4.3 and i went to make a back up and its showing me that wanting to back up system,data, and boot but whats got me is the data is 6266646mb what is that all about?View attachment 2207641
Click to expand...
Click to collapse
i think that is all of your system data information (downloaded apps, passwords, pics, settings, etc). doing a factory reset/data wipe clear all of that.

jco23 said:
i think that is all of your system data information (downloaded apps, passwords, pics, settings, etc). doing a factory reset/data wipe clear all of that.
Click to expand...
Click to collapse
Ive tried everything full wipe,change recovery,flash differnt roms, even did a full format of internal memory and nothing chages I cant make any back ups now. Ive been up all night trying to fix it

danebryan18 said:
Ive tried everything full wipe,change recovery,flash differnt roms, even did a full format of internal memory and nothing chages I cant make any back ups now. Ive been up all night trying to fix it
Click to expand...
Click to collapse
i think I recall seeing some folks claim that they were having similar troubles with backing up 4.3 ROMs.

jco23 said:
i think I recall seeing some folks claim that they were having similar troubles with backing up 4.3 ROMs.
Click to expand...
Click to collapse
Well Im going to flash a 4.2 rom try that and see what happens. thanks for your imput

Well that didnt work.

danebryan18 said:
Well that didnt work.
Click to expand...
Click to collapse
hmmm... I was able to make several successful backups of 4.2.2 ROMs.
did you completely uninstall 4.3 and start from fresh? again, I read that some folks had trouble even getting back to stock or 4.2.2 from 4.3.
while I don't think there is an issue with TWRP, I would certainly post your question on that thread.

jco23 said:
hmmm... I was able to make several successful backups of 4.2.2 ROMs.
did you completely uninstall 4.3 and start from fresh? again, I read that some folks had trouble even getting back to stock or 4.2.2 from 4.3.
while I don't think there is an issue with TWRP, I would certainly post your question on that thread.
Click to expand...
Click to collapse
I just used matts tool and flashed back to stock and it fixed it all!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

danebryan18 said:
I just used matts tool and flashed back to stock and it fixed it all!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
great.
I would advise to create some nandroids of your fav 4.1.2 and 4.2.2 ROMs.

Ive flashed just about every rom for my M as it is just a play phone(no service lol) even unlocked it for other carriers and ive never had a problem like this. Well now that its fixed time to flash somemore 4.3's

Stuck at 4.2.2, bootloop on higher versions

Whenever I try to update 4.2.2 to a newer version via about -> phone, I get bootloop at Google logo. I've already tried to follow "official" guide for rooting but flashing any ROM in CWM newer than 4.2.2 resulted in the same error. I've been desperately looking for solutions for a while and finally came across this blog http://fixandoridproblems.blogspot.co.il/ . I actually managed to get working 4.3 with those steps, but again, as soon as I update it, I get bootloop.
In addition I got weird error while flashing ParanoidAdroid + GAppps, so that obviously didn't help as well. Of course I always wipe data, cache and dalvik cache before flashing anything whatsoever:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I really don't know what else to do, so some help would be greatly appreciated. Thanks in advance.

this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

hp420 said:
this guide is for nexus 5, but the steps are identical for nexus 4. just be sure you get a nexus 4 factory image, not a nexus 5 one Also, you're going to end up wiping your storage partition...be sure you back up all your pictures, music, etc. stored on your Nexus 4 prior to starting.
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I don't think the issue is how to flash, I've seen others who can't flash anything higher than 4.2.2. I'm not sure why or what the fix is other than warranty.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Flash the factory image from developers.google.com for Nexus4 4.4 then reflash the latest versions of custom recovery and SuperSU

I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.

krneki10 said:
I've tried all of these ROMs from https://developers.google.com/android/nexus/images, but the only one which works is 4.2.2, which I can also update to 4.3 (newer version via about -> phone, but ONLY if I downgrade radio - http://fixandoridproblems.blogspot.co.il/). However when I try to update it to 4.4, error occurs (failed android logo) and then it reverts back to 4.3.
Click to expand...
Click to collapse
Dude, we've told you repeatedly....FLASH A FACTORY IMAGE WITH FASTBOOT! STOP USING RECOVERY, BECAUSE THAT IS YOUR PROBLEM!!
Read the guide on how to flash with fastboot.

Jd is right, there are devices out there that after a certain amount of time will refuse to boot any OS above 4.2.2, regardless of how the OS is flashed to the device. No idea why this happens, and the only solution is to get another device.
Sent from my Nexus 4 using XDA Free mobile app

I have the exact same problem on my nexus 4, have you found a fix?

I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
Take a look: http://forum.xda-developers.com/nexus-4/help/help-please-bootloop-4-4-4-imei-t2882868
I'm tired of trying different solutions whit the same result, its exhausting

conquesoextra said:
I have the same annoying issue, but worse.. My phone only accept 4.2.2 or lower, but whitout imei, baseband or WiFi
I'm tired of trying different solutions whit the same result, its exhausting
Click to expand...
Click to collapse
I think this has happened to a few people recently. It happened to me too. For now I have ogt 4.2.2 running, I managed to fix the baseband and IMEI but if i update to a new version it gets broken again.
This is what I did to fix IMEI, hope it works for you
http://forum.xda-developers.com/nexus-4/help/fix-nexus-4-bad-imei-t2882694

Can't Re-Unlock the Bootloader

I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!

deleted

So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app

have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems

I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.

I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!

scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)