I just bricked and recovered my brand new s2 and of course because I was careless , just thought if I post it , it might help people who brick their phones and go in into "panic mode".
The whole story is simple , while trying to reboot the phone instead of plain reboot , gave reboot into recovery , and in a sense of hurry , removed the battery and put it back in , now to my luck the phone started with all my settings except that it messed up the phone modem , luckily I HAD BACKED UP EFS AND THE WHOLE PHONE WITH CWM
I had a custom rom on the phone with titanium backup as well , I just restored the /efs and got the phone back up from the recovery mode , flashed the ROM again , restored the apps from titanium backup
Next time if you are trying something new PLEASE backup anything and everything, because accidents happen.
Hope this will help somebody someday !!!
thanks for the heads-up bro
Excellent advice Dreamchaser
Unfortunately, these forums of full of people who don't listen and are in too much of a hurry to do things to their phone they don't understand even a little
Run your eye over SGS2 general & QA forums today & you'll see a couple of examples.
+10 MistahBungle .
jje
oh I use to silently visit all the threads before buying my s2 , and I did that for a month so that I wont brick and void warranty on a 600$ gadget .The general problem is a lot of people are enthusiastic to do stuff but they DONT READ
dreamchaser_161 said:
The whole story is simple , while trying to reboot the phone instead of plain reboot , gave reboot into recovery , and in a sense of hurry , removed the battery and put it back in
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"
}
Well then you didn't brick it then.
Sent from my GT-I9100 using XDA App
Ya I came close to bricking mine a couple times too because like the other people have stated I was in such a hurry to get the custom rom on there I thought it would be ok to skip steps. Just yesterday I ran into big problems because I put a new rom on and didnt do a full wipe and I got random reboots, forced closes and all kinds of crap. Thank god for the good old nandroid backup! Has saved me more than a couple times!
oops my bad
Thats actually download mode and not recovery , sorry my bad and yes I know I didnt completely brick it, but still I thought sharing this will help
True that!
I almost messed up my friend's Samsung i9000B because I flashed the wrong kernel!
Luckily I was able to go into download mode and flash the right kernel.
argh-like all things in life (ok, most of them) things cant be rushed or done without some knowledge.
when im flashing something i check 5 times am i doing the right thing. no issues so far. cool story eh?
dreamchaser_161 said:
Thats actually download mode and not recovery , sorry my bad and yes I know I didnt completely brick it, but still I thought sharing this will help
Click to expand...
Click to collapse
when u accidently move to download mode, just hold the power button for few seconds it ll reboot... entering the download mode screwed up modem??
Related
I got the root, took 5 minutes but anything after that, not so good.
I spent all day trying to root, nand, flash and am left with nothing but frustration. I had problems with htc sync, still do. Clockwork recovery won't flash and I can't flash a rom from the sd card or usb cable.
I like to tinker but it just doesn't seem worth it. jailbreaking my iphone was a cinch compared to this. I'm very frustrated because I was looking forward to what a custom rom could provide and to getting froyo early.
Thinking of going back to stock and trying the unrevoked method (can I just apply the unrevoked method or do I have to revert back to stock and then try it?) and if that doesn't work just stick with the root.
What method are you using? What errors or problems are you running into? You need to provide more details in order for anyone to be able to help you. Rooting the Evo and nand unlocking has never been easier (unless you are running the latest OTA).
Edit: You don't need to post multiple threads for the same issue. If you're not get any replies, it's most likely because you didn't provide enough info.
yeah i been trying to get that clockwork to install too i cant find a zip for it or anything. I am rooted but still dont have any idea how to enable su to use the rom manager app. i tried that idiot proof which is missing the link for clockwork. I also tried the the simple root but when i hit the exe i get a error. i had almost no issues with the hero i been trying for all day too. I am amazed no one else had another link for that clockwork recovery.zip i woulda been done hours ago. very very frustrating but i am sure its my own fault for being a nubbbbb lol. sucks too cause i work all weekend and i wanted to get this done on my day offf.. which was today
you don't flash recovery using a zip. You need to flash the img. I just checked the clockwork thread, the links do appear to be down. Use Amon_RA
Doesn't get any easier than this: http://forum.xda-developers.com/showthread.php?t=706411
lgevo said:
yeah i been trying to get that clockwork to install too i cant find a zip for it or anything. I am rooted but still dont have any idea how to enable su to use the rom manager app. i tried that idiot proof which is missing the link for clockwork. I also tried the the simple root but when i hit the exe i get a error. i had almost no issues with the hero i been trying for all day too. I am amazed no one else had another link for that clockwork recovery.zip i woulda been done hours ago. very very frustrating but i am sure its my own fault for being a nubbbbb lol. sucks too cause i work all weekend and i wanted to get this done on my day offf.. which was today
Click to expand...
Click to collapse
Go here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
About half way down the page you'll see a list of phones, click the EVO. Clockwork recovery will begin downloading.
imo don't use clockwork, people have been reporting problems with wiping with it.
Where does the recovery clockwork img go?
jgarozzo said:
Where does the recovery clockwork img go?
Click to expand...
Click to collapse
Have you read any guides or tutorials?
http://forum.xda-developers.com/showpost.php?p=6806125&postcount=1
mrono said:
imo don't use clockwork, people have been reporting problems with wiping with it.
Click to expand...
Click to collapse
He can use clockwork, i dont think he will need to wipe the SD, i mean, is not really necesary
,is it?
mikevillarroel said:
He can use clockwork, i dont think he will need to wipe the SD, i mean, is not really necesary
,is it?
Click to expand...
Click to collapse
It is if you had apps2sd stuff on it from another rom. That's where I ran into problems. I've seen other threads where people reported it not wiping cache correctly. I never saw that personally though.
Here...maybe this will help
{
"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"
}
redrazr7791 said:
Here...maybe this will help
Click to expand...
Click to collapse
Hahahahaha
{
"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
Well, I think I need some help with this one.
So, I have been using Resurrection Remix as my daily driver for a while now (to be able to run lollipop). As I noticed the G2 now has an official lollipop build, so I wanted to install that(cam sucks on most ROMs and overall stability isn't always great). Since I figured the best way would be to go back to stock, and then run the OTA updates.
I made a backup of my current rom, found this, and tried the TOT method. Everything ran fine, but when the 85% reboot thing happened, it booted straight into TWRP. Decided to reboot to system via TWRP, but after showing the LG logo for about 5-10s, it goed straight back into recovery. Since i figured the install failed or something I decided to factory reset, and restore from my backup. TWRP says the restore is succesful, but it still won't boot into my ROM. Reinstalling any ROM doesn't work either
Already tried this, no result(, and I'm afraid of trying the above guide again, but let me know if i should just try again)!
I do have access to my recovery and download, and ADB still works. The only thing I see is that instead of this:
{
"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"
}
Mine says this:
(My PC is in Dutch )
(The LG Driver on the guide was an older version than the one on my pc still, but I don't think that will cause a problem).
Hope my phone isn't gone forever, and thanks for helping in advance!!
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
You should edit the title to include the word (solved) or (fixed).
Sent from my LG-LS980 using XDA Free mobile app
Scrytal said:
Well, I think I need some help with this one.
-Scrytal
EDIT:
Tried the above TOT method again, apparatly it skips a lot of things, and is done in like 30s, so it's not doing its job. I have no idea what's causing that though!
EDIT2:
IF ANYONE STILL FINDS THIS, this was the solution for me. I didn't know LG had a 'official' tool for fixing our sh*t . Hope it still helps you!
Click to expand...
Click to collapse
Hi, i can't boot any rom too,
I can access my download mode and recovery mode (twrp),
But i can't boot any custom rom,
And ADB can't recognize my phone,
I tried to back to stock using LG Flash Tool 2014 (the kdz ones), but nothing works,
And the official lg tool link is broken
i get the error "Recording Failed" when i pressed the record button.... my sd card and phone memory still have like 10gb empty... and im using Phronesis Rom v3.0. Any solution?
what do logs say
what logs do you mean?
the logs that tell you what the error is
DSA said:
the logs that tell you what the error is
Click to expand...
Click to collapse
im not sure where to find it...i just saw the pop out error when i press the record camera icon..
aronron33 said:
im not sure where to find it...i just saw the pop out error when i press the record camera icon..
Click to expand...
Click to collapse
XDA is a developers forum/site. Not an end-user forum/site.
People are expected to search for the info the need first.
So google your issue, if that not works google howto get the right logs.
If that also doesn't succeed, write down what you have done to avoid the error.
Don't forget to put in all the needed specs, software versions and so on.
And do that in a proper post, preferably with good spelling, grammar and punctuation.
If done all that, help will be more helpful, plentiful and faster.
{
"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 cant switch to the video camera mode...
I'm out
@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!
HanZie82 said:
@aronron33 Yeah you dug your own grave on this one.
You will get NO HELP, if you dont read others comments and at least try.
So bubye and goodluck finding out the problem yourself!!!
Click to expand...
Click to collapse
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?
aronron33 said:
wow you are so helpful........i google -ed and i cant find anything about extract the logs... so i have no idea what the problem is and i cant even switch to the video camera mode so how could i get an error logs?
Click to expand...
Click to collapse
I have the same problem on my N900W8, probably you can fix it installing a 5.0 bootloader.
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol
Maybe the rom is incorrect have you checked the region and model number etc?
Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked
Could you provide ODIN logs?
{
"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"
}
it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one
TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.
Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?
It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.
no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox
Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin