i have tried to install ICS OTA but was having an error so i saw a post asking to delete some files from system after that when i restarted my device it keeps stuck on the splash screen i tried to wipe data but my device isnt starting. Can anyone have me a rom that i can flash from the original phone recovery i really need to turn on my phone :S
hi_john said:
i have tried to install ICS OTA but was having an error so i saw a post asking to delete some files from system after that when i restarted my device it keeps stuck on the splash screen i tried to wipe data but my device isnt starting. Can anyone have me a rom that i can flash from the original phone recovery i really need to turn on my phone :S
Click to expand...
Click to collapse
Dude, you've got to be more specific. What 'files' did you delete, and did you wipe data via stock recovery or via CWM? Since you wiped data/factory reset your phone, and didn't flash a ROM or install the OTA, you have no system image, so of course it won't boot. What error message were you given when trying to update to ICS via the OTA?
Sent from my rooted Mayan Calendar
i was running 2.3.6 and want to upgrade to OTA ics but it was showing an error while updating so i factory reset my device i was running stock rom and my device was rooted today i read in a thread to delete Delete file /system/bin/logwrapper would make ics work but it didnt work and now my device is stuck at splash screen :S i tried to wipe data but still it is not working
Apex_Strider said:
Dude, you've got to be more specific. What 'files' did you delete, and did you wipe data via stock recovery or via CWM? Since you wiped data/factory reset your phone, and didn't flash a ROM or install the OTA, you have no system image, so of course it won't boot. What error message were you given when trying to update to ICS via the OTA?
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
I have to ask, why are there two posts from you on this same issue, both in the General Section and the Q&A? Please refrain from making duplicate posts, as it clutter up the forum. At any rate, you followed this thread: (?) http://forum.xda-developers.com/showthread.php?p=32632730
OTA ICS update "The software update failed"
Sent from my rooted Mayan Calendar
hi_john said:
i was running 2.3.6 and want to upgrade to OTA ics but it was showing an error while updating so i factory reset my device i was running stock rom and my device was rooted today i read in a thread to delete Delete file /system/bin/logwrapper would make ics work but it didnt work and now my device is stuck at splash screen :S i tried to wipe data but still it is not working
Click to expand...
Click to collapse
Reading for comprehension is key. The posts concerning the logwrapper was for a specific problem pertaining to custom recoveries. Now you need to check out Apex_strider's noob thread and learn how to properly flash a fxz. Read read read then when you've done that read some more. And I mean all of it! do not take pieces of it like the logwrapper out of the context of the discussion. Understand the whole of how to do something before you attempt it.
i have tried doing fxz but its showing an error or step 6 and my battery is low now i put my phone on charge its not even charging seems like i have lost my phone
Here's your options
1 mcgyver method : http://forum.xda-developers.com/showthread.php?t=892026
2 factory cable: http://forum.xda-developers.com/showthread.php?t=1392693
Edit: you could also purchase a standalone battery charger or find another A2 or a bionic will work to charge it in.
Another thing the OP could try is CFB's method using the DNA technique... :thumbup:
Sent from my rooted Mayan Calendar
Thank you so much i was like fed up :S but i did it because of you guys thanks alot
hi_john said:
Thank you so much i was like fed up :S but i am on 2.3.5 now i have bought a stand alone charger. But can you please help me to be on 2.3.6 i will never try to do anything on it again so please help me which rom should i flash
Click to expand...
Click to collapse
If you don't know how to read the posts (which there are several) as to how to go about this, and aren't possessing the initiative to search the forums for this, you probably shouldn't even be messing around with your phone. Just sayin'. This is a developer Site, not tech support...
Sent from my rooted Mayan Calendar
Stuck on M dual core screen
Hi all, I was trying to install the avatar v2.13 rom on my atrix 2, I went into recovery with the atrix 2 bootstrap recovery, backed up my current rom wiped everything and proceeded to install the rom. After it was installed, all I got was the M dual core screen folloed by a black screen and the M screen again. I'm running linux Zorin in my computer and i've looked allover the place for a solution to this. Can anyone please give me some guidance on to what to do to solve this dilema? Your help will be apreciated guys.
Related
hi, i have a samsung intercept from vm. I used a SuperOneClick to delete some stock apps and somethings wrong my on-screen keyboard is completely gone and i keep getting this message saying something about the android process has unexpectedly ended please try again and some times it wont stop coming up and wont let me do anything. i deleted stock email app, some of the virgin mobile stuff I'm new to this as you can tell. please help and thank you
"the process com.google.process.gapps has stopped unexpectedly. please try again."
Rom and Recovery
I am assuming your phone is rooted so can you please tell me what ROM and recovery you are running?
its not rooted any more i used a temporary root i believe its on the stock rom i tried factory reset but it still the same without the apps and the missing keyboard, thanks for your reply
Adb?
jefe1026 said:
"the process com.google.process.gapps has stopped unexpectedly. please try again."
Click to expand...
Click to collapse
This tells me you basically deleted some system applications that support the Google applications like Gmail, Calendar, etc. Not a good thing lol. Next time when you are deleting "bloatware," don't delete anything that starts with com.google or com.system. These are the packages that help run android and google applications.
Incidently, Do you know what adb is? If so, have you ever used it?
ive seen adb when i ran superoneclick im tryin to learn all this i use to have an iphone and hackin that is pie compared to this cause there is so many android phones
Try Factory Reset
jefe1026 said:
ive seen adb when i ran superoneclick im tryin to learn all this i use to have an iphone and hackin that is pie compared to this cause there is so many android phones
Click to expand...
Click to collapse
Don't worry, the initial rooting process is the hardest part. After that, it only gets easier. Then you can put on whatever custom ROM you want and trust me, its awesome!
Anyway, I don't think you need to use adb juuust yet. Did you try to get to recovery mode yet and try to factory reset the phone?
To get to recovery mode on your Samsung Intercept, you hold, all these buttons at the same time, for a few seconds:
Volume Down, Call, and End buttons.
This will either bring you to recovery mode or have an option for recovery mode. Once there, there will be a setting to factory reset your phone. It will say something along the lines of "Wipe Data/Factory Reset" It won't delete anything on your SD card but wipes out all your apps and restores it to when you first used it.
yea i did that and the stuffs still missing : / im tryng to use the sw update to re install stock 2.1 but i keep getting "cannot open .bin file"
I had that problem too. What i did is connect my phone with samsung kies and that restored evrything back for me.
May that not help, try to flash it back with original firmware using odin
just search on this forum
This is the site that contains evry firmware of evry samsung phone:
samfirmware.com
you only have to register
i dont see my phone in the android section
I'm not having any luck with this... nothing seems to work
Don't Give Up!
jefe1026 said:
I'm not having any luck with this... nothing seems to work
Click to expand...
Click to collapse
Don't fret. You haven't bricked your phone yet.
Ok. I checked to see if any forum or site was hosting the original signed zip of the OS that came with your phone and I couldn't find any.
I have an idea though. Not sure if it might work but theoretically it should. Although your phone WAS rooted (aka. temporary root), its not anymore which means you don't have any custom firmware and are running stock.
IF you updated your phone to 2.2 froyo with the official update, then it should completely replace the OS and not only reverse the damage but upgrade it as well.
So you take the phone, put it into "Recovery Mode," and then use adb to push this zip (link below) on to the ROOT OF THE SDCARD. not anywhere else!
then in the recovery, select the "flash/update zip" option and select the new zip.
In theory, this should work. Cannot be sure so tread with caution!
Here is the link:
http://02ee24b.netsolhost.com/downloads/crowder/update.zip
This is the full article that explains how to root your phone after:
http://www.crawfordium.com/blog/?p=22
Best of Luck!!
Thanks I'll try it out
I got this "E:Error in /sdcard/update.zip (Status 7) Installation aborted. I tried formatting the sdcard and redoing it but i got same message again I also tried going into superoneclick and hitting unroot and it says its unrooted but i still get the (status 7) message :/
and the sw upgrade says cannont open .bin file
This might work!
I was reading through some Samsung Intercept forums for you and this looks promising:
http://forum.sdx-developers.com/int...e-to-froyo-2-2-with-no-baseband-modification/
Go through the first three steps and flash the stock 2.1 on to your phone and it should be restored to basic regular Android 2.1. It IS sprint's stock 2.1 for intercept not Virgin Mobile's but its ok because it doesn't replace Virgin Mobile's Baseband so its fine. Instead of seeing the Virgin Mobile boot up screen, it will show you a sprint boot up screen. No biggie.
Try it and tell me how it goes. remember to follow instructions carefully and to the tee.
OK NOW IM ON SPRINT 2.1 and my number works and now im going to try upgrading to 2.2 show i try doing it over the air or just do it manually?
i just did it manually now im going to try to root it
now how do i get superuser and all that good stuff with the roms i dont like the slapstick 1.4
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
It depends what device you have. Different things can cause different devices to brick. Usually a "bricked" device is caused by a bad kernel (more so by over clocking or overvolting), (If you have an HTC device) a bad HBoot, flashing a leak that is incomplete or flashing an update (RUU, Odin, whatever) for the wrong device, or flashing a package for the wrong device or one that is improperly coded.
You CANNOT brick your device by flashing custom roms and recoveries or anything like that, and permanent, unfixable, hard bricks are VERY rare and are usually because someone did something stupid.
If you're worried about installing a custom ROM or something, don't worry, it won't brick you.
TwinHeadedEagle said:
Hello,
I was wondering if someone could explain me, how BRICK happens or what to do to stay away from brick.
I searched for this question, but cannot find proper answers...
Thx in adv
Click to expand...
Click to collapse
Bricks happen when you try something not meant for your phone.
Sent from my U8150 using XDA
Thank you so much for clarifying this to me...
I am not total beginner, i possess Galaxy GT-I9001, for 4 months and i installed CWM last week, with complications, i used Odin 4.03 what one guy instructed to me, beside 4.43. First 4.03 failed and my phone failed to boot, I was worrying i could lose the phone. Then i used 4.43 from the Wiki tutorial what fixed the things...
Now i want to Root the phone, so this previous experience scared me, now i am not confident about it so I used to ask here...
So to clarify:
- rooting
-CWM
-flashing - installing custom ROMS
in proper way and following instructions won't brick my phone?
Is it possible that the dev/alpha/beta ROM versions could brick my phone?
How hard brick happens I am interested?
Is soft brick always fixable?
Sorry for bothering with this stupid questions, I am just not too confident, and i don't wanna destroy the phone, i've got no money for another
Thanks again and sorry if bad English
bricked= corrupted bootloader
a really bricked phone is like "dead' and the only way to solve this problem is to flash a new-and-happy bootloader by hardware tools like Medusa jtag jig also you can't solve bricked phone by PC software if yo do so then your phone is not really bricked
I don't know anything about hard/soft bricked what's that ??
you can't brick a phone by flashing a beta rom if you don't touch bootloader but you can destroy or cause hardware damage by flashing a rom/kernel not made for your phone so that's very important to know !
to prevent bricking your phone:
1. never use a flashing tool not made for your phone
2.when flashing bootloader made for your phone only use a stable PC connection/cable and is better to use a laptop on battery
3.about ROM Manager :if you don't see your phone in list never use it to flash recovery/rom
rooting means to get root access this is like your Administrator account in Windows OS well, it happens because by default phones come out from manufacturer with root disabled to protect the phone and their business
CWM is a custom recovery in fact this is a little OS that works like Safe Mode in Windows it can help you to flash a rom/update/theme etc
CWM recovery is different compared to stock recovery because it gives you the chance to flash custom things to your phone I mean you have to give a package a digital signature in order to flash it to your phone and stock recovery is restrictive it allows you to flash only signed-by-manufacturer things like roms/updates/themes and here is the place where CWM comes it allows to flash self-signed packages
Follow tutorials and you won't brick your phone. Stick to your device forum. E.g ,Just because something worked on the galaxy ace doesn't mean you can use that tutorial on a galaxy mini.
Soft bricks can be fixed,those are just installation errors.
Sent from my U8150 using XDA
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
Why would you want to remove cwm? Its a custom recovery, without it you can't go custom. Use cwm to create a nand backup. To go back to stock recovery, you are correct, but make sure you have correct files etc in Odin. Pulling out your USB cable in Odin without completed will brick your phone, I know cuz I did it. The wrong files can do the same. CWM doesn't change the ROM, just the recovery. I have also heard of bricks from Samsung kies mini. Yes you need to wipe/ factory data reset when flashing a new ROM. If you are only updating a custom ROM, going from (ROM name) v 1.2 to (ROM name) v 1.3 it is not always necessary to do factory data reset but follow the instructions per developer of ROM/thread. Get root, put custom ROM on sd, in recovery make a nand backup, wipe cache, wipe dalvik cache, factory data reset, install zip from sd, reboot.
Also sometimes when flashing a ROM it might not boot first time. Don't panic, pull battery out/in 3 button to recovery, install zip again, reboot and enjoy.
Hope this helps....if so hit thanks button!
sent courtesy of the pony express
TwinHeadedEagle said:
I was wondering how to remove CWM and to restore original recovery...
I suppose i have to flash my stock ROM, am i right?
Do i need to wipe all data before flashing my custom ROM, just to add i have 2.3.3 i only did CWM nothing else is changed.
One thing isn't clear, when I flash CWM is my stock ROM changed?
Click to expand...
Click to collapse
No,your stock rom is not changed,just your recovery. You'll need clockworkmod do install custom roms since stock recovery lacks the features needed to install non-manufacturer roms.
If you are concerned about altering your current rom,you can make a backup using clockworkmod recovery, and store it somewhere like your PC.
Yes,just to be safe, it is better to wipe data. Unless it's an update of the same rom which again, isn't always guaranteed. Just to be sure your safe,backup your apps and clear everything.
Clockworkmod is removed in the bootloader by swapping it out with something else(like amon-ra).
Sent from my U8150 using XDA
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
TwinHeadedEagle said:
Ok, thanks
I am planning to use custom roms, but it's not important at this time, I am satissfied with current...
I only need to know how to restore stock recovery, if the phone is somehow damaged and needs to be taken to the service warranty is lost with CWM installed?
Thank you and Sorry again if i am too noob, and asking stupid questions, i just need detailed explanations from people that experienced this, and apparently I've got it
Click to expand...
Click to collapse
It is possible to reset the phone fully to stock. This removes clockworkmod recovery and your custom rom and allows you to claim warranty. So far only Sony is the one I'm aware void your warranty permanently if you unlock your bootloader using their 'official' method. They keep you on record,so even if you relock it you're outside warranty.
Sent from my U8150 using XDA
How To Unbrick my Kindle Fire?
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
lcharrisej said:
Hello, I'm a Noobie,
I think I bricked my Kindle Fire. “kindle fire” stays on the screen when I turn it on. I can see the device on my computer as ‘Removable Disk (G’ however I am unable to access the drive. Am I BRICKED for good? Kindle running 6.3.1.; PC running Window 7. Please help…..
Click to expand...
Click to collapse
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
@ Allanitomwesh
You didn't tell me how to reset phone fully to stock
I am assuming you haven't started playing with your phone.
Dial *#1234# and write down the three ID Strings PDA, CSC & PHONE ID
They'll be useful later. Just for paranoia, use adb to save your IMEI details (adb is for windows PC's don't worry)
Install Samsung Keis in same PC. Make sure it recognises your phone. Always check this before running Odin.
Always do a full backup (apps, data,settings) before resetting to stock or just any flashing.
Odin will install custom roms on your phone,and it will also take you back to stock if need arises. This is done by 'flashing' stock rom into your phone.
You can follow this tutorial
http://forum.xda-developers.com/showthread.php?t=1345671
Where the rom is the stock one. You can get the right one here http://www.sammobile.com/firmware/?page=1&t=2 Clockworkmod and root access will be lost.(those come with custom roms,don't worry)
When using Odin, a few tips,
1.always run as administrator (right click on icon>run as administrator)
2.Odin runs better without sim card and SD card. You can take them out before entering download mode
3.NEVER EVER interrupt a flashing process,its a guaranteed soft brick.It takes about 10 minutes. If you're impatient, walk away. Also for paranoia,better to have a ups.
4. Perform factory reset before and after flashing. * Menu* Settings* Privacy* Factory data reset* Reset phone& Erase everything. Before and after.
If your rom doesn't boot try this
http://forum.xda-developers.com/showthread.php?t=1660596
Sent from my U8150 using XDA
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
xmond said:
Would someone help me? I just installed CM10 Jelly bean for Iconia A500 and flashed the corresponding GApss right after. Now I'm stuck on Acer logo and can't go to recovery. Help.
Click to expand...
Click to collapse
Ask here for better assistance
http://forum.xda-developers.com/forumdisplay.php?f=1211
Sent from my U8150 using XDA
Thanks
Allanitomwesh said:
Redownload the rom with a stronger internet connection, flash it again.
Sent from my U8150 using XDA
Click to expand...
Click to collapse
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
lcharrisej said:
Thanks for your response, I however cannot access my Kindle Fire. It shows up on my computer as 'G:' drive. I can go to TWRP on the device but there's nothing to restore. I think I wiped out everything. There is a message that says "E:failed to mount /sdcard (Invalid argument)" I'm Bricked for good aren't I?
Click to expand...
Click to collapse
Not necessarily, but it does sound like you went abit overboard with clearing data.
Try and restore stock rom on your kindle. The method where you lose root preferably.
Sent from my U8150 using XDA
OK, So I followed ALL the instructions given here: http://forum.xda-developers.com/showthread.php?t=1575199 (wipe/factory reset, wipe partition cache, wipe dalvik cache, install rom from sd card).
Got to the part of flashing the ROM to my phone, I downloaded all the files given on that page onto my sd card. In Clockwork Mod I kept getting an error saying "Unable to open file, aborting." Yeah that's right, Clockwork couldn't open the file (and yes I have the latest version). So I used the Rom Manager app to do the flashing. Apparently the Eaglesblood ROM failed to recognize the G'Apps version that is listed on eaglesblood page (when you click to download it gives you a different version than what you need) so it installed the ROM without G'Apps. Now, whenever I boot my phone I get the Eaglesblood logo and the phone shuts off. WTF?!!! This ROM totally F ***ed up my phone, Anyone help please? Seriously, I've never had problems of this magnitude with Android before. I've never completely F ***ed up my system to the point where it wouldn't boot, ever. But holy S *** this takes the cake!! Full restore it is, and I don't think I'll ever touch an Eaglesblood rom again...
famouswolfe said:
OK, So I followed ALL the instructions given here: http://forum.xda-developers.com/showthread.php?t=1575199 (wipe/factory reset, wipe partition cache, wipe dalvik cache, install rom from sd card).
Got to the part of flashing the ROM to my phone, I downloaded all the files given on that page onto my sd card. In Clockwork Mod I kept getting an error saying "Unable to open file, aborting." Yeah that's right, Clockwork couldn't open the file (and yes I have the latest version). So I used the Rom Manager app to do the flashing. Apparently the Eaglesblood ROM failed to recognize the G'Apps version that is listed on eaglesblood page (when you click to download it gives you a different version than what you need) so it installed the ROM without G'Apps. Now, whenever I boot my phone I get the Eaglesblood logo and the phone shuts off. WTF?!!! This ROM totally F ***ed up my phone, Anyone help please? Seriously, I've never had problems of this magnitude with Android before. I've never completely F ***ed up my system to the point where it wouldn't boot, ever. But holy S *** this takes the cake!! Full restore it is, and I don't think I'll ever touch an Eaglesblood rom again...
Click to expand...
Click to collapse
I didn't have any problems. Did you try redownloading the file to make sure the zip wasn't corrupt? Did you format /system along with what you mentioned? The page links to the April 29 ICS GApps which is correct I don't see what issue you are having there. Can you not even boot to CWM anymore? This will resolve the boot issues putting the stock ROM back on: http://forum.xda-developers.com/showthread.php?t=1248644
If CWM couldn't open the zip what made you think using ROM Manager was the best thing to do? Seems more like user error that you're just blatantly blaming on the ROM
famouswolfe said:
OK, So I followed ALL the instructions given here: http://forum.xda-developers.com/showthread.php?t=1575199 (wipe/factory reset, wipe partition cache, wipe dalvik cache, install rom from sd card).
Got to the part of flashing the ROM to my phone, I downloaded all the files given on that page onto my sd card. In Clockwork Mod I kept getting an error saying "Unable to open file, aborting." Yeah that's right, Clockwork couldn't open the file (and yes I have the latest version). So I used the Rom Manager app to do the flashing. Apparently the Eaglesblood ROM failed to recognize the G'Apps version that is listed on eaglesblood page (when you click to download it gives you a different version than what you need) so it installed the ROM without G'Apps. Now, whenever I boot my phone I get the Eaglesblood logo and the phone shuts off. WTF?!!! This ROM totally F ***ed up my phone, Anyone help please? Seriously, I've never had problems of this magnitude with Android before. I've never completely F ***ed up my system to the point where it wouldn't boot, ever. But holy S *** this takes the cake!! Full restore it is, and I don't think I'll ever touch an Eaglesblood rom again...
Click to expand...
Click to collapse
When CWM couldn't open the file, you probably just had a bad download, the zip was probably corrupt or something you probably just needed to redownload. And you used what pretty much every user in the G2x advises NOT to do, and that's use ROM Manager, it simply does NOT work on our phones and that is probably what messed your phone up and NOT the Eaglesblood ROM. just use this http://forum.xda-developers.com/showthread.php?t=1248644 and it should fix your problem.
BTW next time don't bash a ROM if you didn't know what exactly is the cause of messing your phone up, in this case it was just pure user error. Try reading up next time, trust me it helps..
Sent from my LG-P999 using xda app-developers app
famouswolfe said:
OK, So I followed ALL the instructions given here: http://forum.xda-developers.com/showthread.php?t=1575199 (wipe/factory reset, wipe partition cache, wipe dalvik cache, install rom from sd card).
Got to the part of flashing the ROM to my phone, I downloaded all the files given on that page onto my sd card. In Clockwork Mod I kept getting an error saying "Unable to open file, aborting." Yeah that's right, Clockwork couldn't open the file (and yes I have the latest version). So I used the Rom Manager app to do the flashing. Apparently the Eaglesblood ROM failed to recognize the G'Apps version that is listed on eaglesblood page (when you click to download it gives you a different version than what you need) so it installed the ROM without G'Apps. Now, whenever I boot my phone I get the Eaglesblood logo and the phone shuts off. WTF?!!! This ROM totally F ***ed up my phone, Anyone help please? Seriously, I've never had problems of this magnitude with Android before. I've never completely F ***ed up my system to the point where it wouldn't boot, ever. But holy S *** this takes the cake!! Full restore it is, and I don't think I'll ever touch an Eaglesblood rom again...
Click to expand...
Click to collapse
You do realize that we have literally tens of thousands of people running this ROM right? I can tell by your freakout post that you must be panicking however rest assured this is only a simple case of end-user error. If you'd like me to walk you through the installation steps I'd be more than happy to: [email protected].
Otherwise you may find more helpful support by posting this on the OP that has nearly 100 pages of user activity: http://forum.xda-developers.com/showthread.php?t=1575199
A device failing to boot is nothing to worry over; I intentially do it to mine, on purpose, several times a week. If you can't access CWM Recovery then that means you didn't install that properly either. If you hotFlashed your recovery using RomManager then this is way you can't quickly recover from a failed boot... You need to install CWM Recovery using the NVFlash tool http://forum.xda-developers.com/showthread.php?t=1054492
The next time you softbrick yourself you'll have no trouble booting up into Recovery.
Sorry to see you're 1st post on XDA had to be a bad one, well welcome to the forum anyway. Hang in there bud, its frustrating for even the best of 'em when you first start off with custom ROMs; you'll be coaching others like yourself in no time. Once you're collected and feel like installing it properly go ahead and email us, I will respond. Tell me who you are when you email and I'll remember. ...just say you're the freakout guy from xda and I'll know who. LOL I'm just messin' with you man, I'll take care of you. -b0xer
This guys must have been a noob lol
Sent from my LG-P999 using xda premium
sickkside13 said:
This guys must have been a noob lol
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Had to be. Everybody that actually reads before rooting knows that you never use rom manager to flash anything on this phone. Research before you blame someone else for your mistake. At least boxer was cool enough to offer guidance.
oOo B0XeR oOo said:
You do realize that we have literally tens of thousands of people running this ROM right? I can tell by your freakout post that you must be panicking however rest assured this is only a simple case of end-user error. If you'd like me to walk you through the installation steps I'd be more than happy to: [email protected].
Otherwise you may find more helpful support by posting this on the OP that has nearly 100 pages of user activity: http://forum.xda-developers.com/showthread.php?t=1575199
A device failing to boot is nothing to worry over; I intentially do it to mine, on purpose, several times a week. If you can't access CWM Recovery then that means you didn't install that properly either. If you hotFlashed your recovery using RomManager then this is way you can't quickly recover from a failed boot... You need to install CWM Recovery using the NVFlash tool http://forum.xda-developers.com/showthread.php?t=1054492
The next time you softbrick yourself you'll have no trouble booting up into Recovery.
Sorry to see you're 1st post on XDA had to be a bad one, well welcome to the forum anyway. Hang in there bud, its frustrating for even the best of 'em when you first start off with custom ROMs; you'll be coaching others like yourself in no time. Once you're collected and feel like installing it properly go ahead and email us, I will respond. Tell me who you are when you email and I'll remember. ...just say you're the freakout guy from xda and I'll know who. LOL I'm just messin' with you man, I'll take care of you. -b0xer
Click to expand...
Click to collapse
Lmfao! The way you said everything so sweetly and made the guy look like a complete idiot. Best pwn I've seen in a while.
On a serious note, dude don't freak out. Not that you can't brick a g2x, but it's incredibly difficult. If you're not staring at an s/w upgrade screen, you're probably fine.
Sent from my LG-P999 using xda app-developers app
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Dr. Light said:
Anyone know of, or or have a link to a factory rom (hell any rom would do at this point) that I would be able to flash with the stock S3 recovery? Just trying to unbrick my phone. Story of what happened below:
I'm running stock 4.1.1 rooted touchwiz. I wake up this morning to a notification saying I had an update on my phone. Should have definitely waited but without thinking I went ahead and updated, which of course soft bricks? The phone. (boots up, and but hangs at the 4Glte, flash screen)normally this would be an easy fix, I could Odin back to stock or something but I'm down in Mississippi till Monday for training and do not have access to my pc.
I can access the factory recovery on the phone but that's it, have no clue where CWM is. I've tried flashing some backups but the factory recovery says that it's not a signed package or whatever. Anyone have any idea how I can get this sucker booted up and running using just an android tablet?
What about reflashing CWM so I can access my backups? Could I somehow flash CWM with factory recovery?:
Click to expand...
Click to collapse
first of all you can't flash anything on a stock recovery hence the need of a custom recovery. Second you don't accept the OTA when rooted as it can cause the exact issue that you have. Last there isn't a way to fix your problem via another android device that I know of.
U are going to need a pc and then u will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery. Then you can access your backups.
Always_Jonezen said:
U will need to download Odin http://forum.xda-developers.com/attachment.php?attachmentid=1165122&d=1340993443 and u can get the official software from here on XDA http://hotfile.com/dl/182822657/9f6...WBLK3_381038_REV09_user_low_ship.tar.md5.html this is the 4.1.1 software. Here is a link to some official pre rooted software http://forum.xda-developers.com/showthread.php?t=1984436 all of these software's you can install though Odin just look up here on XDA on how to use Odin and you will be fine once your phone is up and running again then you will need to get you a custom recovery.
Click to expand...
Click to collapse
He doesn't have access to his PC PLUS he already knows what to do on that end.
jmxc23 said:
He doesn't have access to his PC PLUS he already knows what to do on that end.
Click to expand...
Click to collapse
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Thanks for all of advice guys. I'll prob just wait it out till Monday. Thanks again.
Always_Jonezen said:
Just trying to help out but of course someone always has to criticize. I don't see you giving him any advice.
Click to expand...
Click to collapse
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
jmxc23 said:
He was asking if he can use an android tablet to fix his phone. He doesn't have access to PC at least until Monday it says so in his post. I wasn't even criticizing you at all. Unless he knows someone with a PC in Mississippi or someone here knows how to use one android device to flash something on another android device he sadly will have to wait until he gets home to fix his phone. You didn't do anything to be criticized for trying to help all I did was point out the info that you missed without personally attacking you making it a critique.
Click to expand...
Click to collapse
hey all, I've been reading , downloading etc for hours trying to get back into my GS3.. i was as usual roaming around and saw a post that said something to this effect "do ya need to get back to stock?" and figured yes i need to so i jumped in with both feet ..i had my boot loader unlocked and for some reason locked the darned thing remembering it was locked before i rooted and then i get the screen that says ie: "System software not authorized ~~~~~~~~~~~~" with a yellow triangle over it with an "!" mark in it..
all would have been ok except the line up of the way to do things was kinda outta line.. after i had locked bootloader "which is the way the GS3 came" i thought. at any rate i am now where i said i was and if i can be helped it would be appreciated.. and no repeated.. next time i'll read their whole line up first.. so help me if ya can and i am game right now for about anything ..
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
CreativeSin said:
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
Click to expand...
Click to collapse
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to . Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
CreativeSin said:
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to .
Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
Click to expand...
Click to collapse
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
CreativeSin said:
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
Click to expand...
Click to collapse
Well now that you're back and rooted, if you're planning on doing any more flashing any time soon then I recommend you install boot menu manager. If you've previously installed safestrap or bootstrap, clear their data and uninstall them before installing bmm.
With that done, you've just made your phone a little safer from bricking because bmm allows multi rom booting, which are somewhat independent of the primary system. Refer to this thread for more info on how to make systems, etc.: http://forum.xda-developers.com/showthread.php?t=2115715
The first thing you'd want to do is make sure your apps/data is always backed up at all times with apps like titanium backup. Create 2 or more systems so that you can try the bmm compatible custom ROMs which are in the dev section if you want to try any of them. But please, read all instructions, warnings, requirements, etc. carefully before attempting any flashing in general.
The thread I posted in my earlier post above will have links to the specific custom ROMs. If you're doing any other kind of flashing, make sure to again, read instructions carefully and take your time with learning all of this.
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
kunal2711 said:
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
Click to expand...
Click to collapse
Use boot menu manager instead of bootstrap recovery
Sent from my MB865 using XDA Premium 4 mobile app