Related
good night friends!
I'm here asking for this help not for lack of looking for the solution, sorry my bad english, I'm from Brazil and I
defy caught in a bootloader, I tried almost everything I found here in the forum, but most of the problems is
reset solved by making the recovery, but in my defy the recovery does not open, the flash works only power + vol up, already
I spent several roms to no avail, could someone help me run my recovery? grateful heart
list of roms flashead
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FFJORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbfz
JORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbf
JRDNEM_U3_2.34.1_DEBLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA02B.0R_USAJORDANRTCEE_P029_A019_HWp3_Service1FF.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTHKTW_P021_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_3.4.2_164-003_VFBLUR_SIGN_SIGNED_USAJRDNEMARAB1B8VFFR03A.0R_PDS03C_USAJRDNFRYOVFFR_P028_A014_M004_HWp3_Service1FF.sbf
Motorola_Defy_Nu___Android_2.2_FroYo
shadow_defy_2.3.3_85_Orange
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
mmec2 said:
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
Click to expand...
Click to collapse
I really can not, no way to go to the screen with the robot android! he goes right on the logo motorola M!
can it be hardware problem?
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
farsight73 said:
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
Click to expand...
Click to collapse
I'm using motorola rsd 4.9 with updated drivers, what happens is install the rom normal after reboot gets stuck in the Motorola M logo, the software update site does not recognize my phone, do all these roms that I would be no my phone?
im tried this roms now
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
3.4.3_11-Stock.UKTmobile_BLUR
but no results!
don't worry about it, dude.
maybe you can try the way followed:
1.power off your defy;
2.remove the battery from the phone;
3.plug the usb cable into the phone without battery;
4.open RSD and chose one of the roms your listed, but 3.4.2-177-005 NORDIC prefered,
5.take the battery into your phone, now your can see the "connected" on RSD;
6.click the "start" button to flash;
7.wait the phone reboot completely, usually it'll reboot.
if not reboot, remove and on your battery, power on your phone, then press the "volume - and power" botton together, you can enter the robot screen, press volume up and down botton together, usually you can enter the recovery, then chose wipe 3 and 4, totally you can save your defy~~
Be sure to have enough battery while flashing..
Get the phone into bootloader (hold volume down when switch on) and flash an SBF like one from the list you've attached using RSD lite. Surely you have used RSD Lite before?
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
jdearauj said:
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
Click to expand...
Click to collapse
This same friend, I have the same problem, is this a hardware problem? I move the roms but not normal
Vol I login recovery - + Power key
http://forum.xda-developers.com/showthread.php?t=966537
Try flashing nordic, if fails arabic, if fails, 2.3.3, if fails probably corrupt nand broken hardware.
Before and after every flash always try to access recovery (volume down) and WIPE. reboot and wait crossing fingers, if it fails to boot flash next sbf, try to go recovery + wipe; reboot, cross more fingers; if fails to boot try next sbf and repeat.
The reason for this is that you can flash a lower version but it wont boot, so you have to flash a higher and higher version until you get one that works.
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
zyxwvut said:
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
Click to expand...
Click to collapse
OMG Exactly!!!! i have same problem and nobody seems to be able to tell me what to do, they keep saying same thing about trying various SBF's and Vol down + power method. No matter what SBF file I successfully flash with, i cannot get into boot recovery mode.
I have heard before from desperate users that they were able to revive their phone by flashing a full 2.3.4 sbf. This however comes with downsides of not being able to downgrade to froyo by flashing ANY froyo sbf's. There is a way to downgrade back to froyo but its a dirty method. Even after downgrade you can't just flash a sbf, you will always need to restore nandroid and flash fixed sbf
A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?
The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.
I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf
You can't hold volume down and power button to enter recovery?
Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.
it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom
OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!
http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.
Thanks buddy. On my way to grab the files now
I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.
Hello XDA-devs forums,
I'm having an issue since yesterday.
I have rooted my Huawei Ideos X5, and it ran fine for a day or so.
However, when my battery ran out it shut down into a completely blue screen.
When I tried booting it again, this just showed me a blue screen as well.
Now, I fixed this issue by connecting the phone to my PC after booting it with the Vol+ and Vol- pressed.
(So you get the pink/purple screen)
However, when I opened the phone on my PC, all I saw was a "239 MB" "empty" space, and it should have ~2GB..
I placed a backup copy I saved of my "image" folder in that 239 MB storage, and it booted.
However, today I hooked it up to my PC again to see if it magically changed..
And I couldn't access the 239 MB space anymore.
When I tried fixing the issue with a reboot of the phone, that just caused it to get stuck in a booting loop.
So now I'm stuck with a phone that keeps trying to boot itself,
and I can't access it on my windows PC.
I can, however, access 4 different folders of the phone on my linux notebook.
Now, my question is: can someone with a good understanding of problems like these please help me out?
I'm getting kind of fed up with it, as I've only got the phone for 2 days now.
Thank you in advance, and thank you for taking the time to read this.
Have you tried removing the battery for 5 minutes and then putting it back in?
After this, what happens when you press VOL+ and Power?
How about if you press VOL+, VOL- and Power, without the USB cable?
Hello Katu, thank you for posting.
Regarding your questions:
Yes, I have tried to take out the battery for 5+ minutes- it didn't change anything to the situation unfortunately..
If I press VOL+ and Power at the same time, the device boots into recovery mode.
In this I have tried to format the device in order to reset it to factory defaults, but this did not help either.
When I press VOL+, VOL- and Power, the phone boots into the pink/purple screen.
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
PlanDreaM said:
Can you try a custom recovery and a custom rom? I want to see if your onboard flash is borked.
u8800,cm7,[email protected]
Click to expand...
Click to collapse
Well, I used an original ROM:
U8800 V100R001C00B136(Overseas General version)
And that resulted in the boot.img being corrupted, so I can't even overwrite that anymore.
Also, this is what I see when I hit VOL+, VOL- and Power at the same time to boot into safe mode, and connect it to my PC.
img69 [dot] imageshack [dot] us/img69/244/10101191548pm.png
julle131 said:
I had the same when my phone got f*ucked up. Put the image folder, than download official rom, like b138 and install it. then check your imei. There is a change that it will be 0.
Click to expand...
Click to collapse
I installed the official B136 rom, and after it rebooted, it would just hang on a black screen.
(it used to show the IDEOS or Android logo when it booted)
Hmm mine came with this Rom
U8800 V100R001C00B135SP01 ( general )
Looking at your name you're from the Netherlands ( so am I )
where did you get this 136 version from ?
I would try to put this one on it
You have to put the 'dload' folder into the root of your SD Card,
then boot into boot-loader, after that it'll automatically flash back to the stock Rom.
1 Format SD card
2 On the SD card, create "dload" folder
3 Put the unzipped Rom into "dload" folder
4 Then boot to bootloader (pink screen)
Yes, mine came with that version as well.
However, I couldn't find it anymore and thus downloaded the version I said earlier.
Also, I did everything as you described, except step 4.
You have to boot to recovery instead of bootloader. (VOL+ and Power)
Anyways, I managed to get ClockworkMod's recovery.img on my phone,
and from there on install a custom ROM on the phone, which magically got it working again - even though it didn't work earlier.
Thank you for reading my thread and taking the time to reply to it.
My issue has been resolved.
just for the record, flashing a stock rom is different from flashing a custom rom..
the 4 steps described by Gman2oo6 is the correct way to flash a stock rom (and it is written clearly in the document that is in the stock rom zip file)
[edit]
step (1) is not a necessary step though..
Yeah, I noticed that.
What I did was format my SDcard with FAT32,
and put a custom rom (update.zip) on the SDcard.
I then booted ClockworksMod Recovery and installed the custom rom from the SDcard.
When I tried installing the stock rom, I just followed the PDF file's instructions that came with the stock rom.
hey i udated to GB 2.3.4 (official)and i didnt like the it cuz the wifif ddnt work and the bluetooth also the DATA so itryed to downgrade to 2.2.2 original official and it did the 2/2 steps intalled and when it restarted it did not want to turn on all that happened was it vibrated and thats all so i left it on like that and when the battery died i plugged it in to the AC and the LED turned on red and the touch kkeys also but not the screen so i really NEED help!
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
i tryed it
nope nothin good happened all that happens is a blank screen with nothin on ,LED is off and the touch keys are off. it justz vibrates and when i put the battery it turn the LED on to red and the touch keys turn on but then like 5 min later the LED and keys turn off
astewart said:
Try to turn it on with lead connected but no battery and see if you can start it.
My battery also went dead flat this morning and I couldn't get it started at all till I tried this. Once I got it started the only thing I could do was quickly pop in the batery and let it charge. Just leave off the cover till you get it going.
I have to add that I did not have the problem of a failed update to deal with but it may at least get you started
Click to expand...
Click to collapse
ok heres what i did i wanted to upgrade my phone to the newest version GB 2.3.4.So what i did was download the update and i followed the installation steps i successfully updated to Gb 2.3.4. so like i was checking how it look and the new feature but when i wanted to go on the android market i went to setting and turn on the wifi and it said Error and then i tried the Bluetooth and it said Error also so then i put my SIMs card in and i was like imma use DATA then and when i restarted my phone it had service but no HSPA+ or Edge or GPRS so like i just hatted my phone from their so then i was trying to root it but iddnt know how to do that so like i read this website and i got the UPDATE.APP or 2.2.2 AT&T did the same steps of the installation of BG 2.3.4 and it went to the process and 1/2 stepp good it passed and then 2/2 also passed it installed it and when it said Successively Installed it said Restarting and the scrren turn of and it vibrated and thats all that happened and i left it like that for the whole days and nothing happened
Do u got any idea?
When i connect it to my laptop it says installing drivers .then its says sucesfully installed drivers ready to use. so then i got to Device Manger and i check what has been installed and their it said USB Human interface device and HID-compliant device WHAT DOES THAT MEAN??
Not sure about the HID (human interface device) probably just the way windows sees the device for interfacing with it. With regards to the not booting I have read a lot of people saying that you need to factory reset and clear cache after the upgrade/downgrade. With the phone off, turn it on by long pressing volume+ and power on button till you get the blue recovery screen and from there you can reset factory/ data and also clear the cache. from what I see this should clear up the problem and start up. Please read this thread, it may help you somehow..... http://forum.xda-developers.com/showthread.php?t=1420728
Hope this helps a little
U mean Boot recovery and imma try it and thanks ill check it out
Sent from my MB300 using XDA App
all that i know is that if u customized your partition, it'll bootloop,
so go back to stock-partition ^^
How do I do that got like the steps or video?
Sent from my MB300 using XDA App
when i downgraded to 2.2.2 i installed this V100R001C00B138SP04CUSTC185D002
http://forum.xda-developers.com/showthread.php?t=1251250 got it from that link
Looks like you are not having much luck. Did you try to factory reset?
astewart said:
Looks like you are not having much luck. Did you try to factory reset?
Click to expand...
Click to collapse
well how do i do that do i need to got to the purple/pink screen or bot recovery cuz i cannot access that my phone doesn't do anything pretty much
I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
derviansoul said:
I have a stock unmodified defy updated to 2.2.2, recently the phone started constantly rebooting, usually it stays on for about 2-5min before it goes off or reboots, either plug-in or not. I thought it would be some problem with apps or something like that, so i reset the phone to factory settings and the same kept happening. The phone never reboots in bootloader mode or in recovery mode.
Since this wasnt working i decided to install a custom rom or even the stock roms in wiki in this forum.
Through the times i flashed the phone i only used the custom recovery once, do i have to use it for each time i flash it? It is really hard to keep the phone on long enough to install the bootloader each time.
the phone was a stock uk unlocked debranded version i got from expansys.
Now I installed a 4.5.1-112 Orange GB 2.3.3 with MotoBlur stock sbf version
All i done to this version load the bootloader and install it. the phone is dead now with no response connection to rsd lite or white led. (which i am about to try to sort it).
All i wonder is if it is me installing the sbfs wrong and because of that it is not fixing the reboot problem, or if this has happened to more people and does anyone knows a solution for it?
I have installed 2.2.1, 2.2.2 (stock) and modified from a tutorial in here and now 2.3.3 as mentioned above.
I would appreciate if anyone could help me.
Click to expand...
Click to collapse
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
farsight73 said:
Now you're in 2.3.3. Have you try boot into stock recovery and do total wipe of cache/data, and reboot again??
A lot of people forget this step when they do the flashing and restoring process..
Click to expand...
Click to collapse
I left the phone overnight without the battery on, and this morning for some reason i could reboot to 2.3.3 at first the phone stayed on without rebooting for about 30mins, but soon it started doing the same constant rebooting now it doesnt even go past the moto sign.
I have wipeout now the cache also and no changes.
dlcookie said:
you need to have custom recovery , wipe data and cache , then try or else search this forum (defy) for fixed sbf of your choice and flash that and then root and load your rom
Click to expand...
Click to collapse
What do you mean for a fixed sbf? That is a new term for me. It is really hard install the bootmenu thing because the phone doesnt stay on for long in the android os!!Is there any other way to connect to adb?
I got a fixed sbf and attempted to follow all the steps stricly, but when i dowgraded from gingerbread 4.5.1-112 Orange GB 2.3.3 with MotoBlur to Uk 3.4.2 froyo stock sbf from here
http://forum.xda-developers.com/showthread.php?t=933555
my phone this time gone really weird:
All i managed to do with this sbf was to root it with superclick, before it gone off again.
yesterday Saturday 03-12
-When I put the battery in, the phone refuses to go on, or to get in bootloader/recovery, after a few minutes the boots automatically and gets stuck in the moto logo (sometimes it goes off sometimes just stays there for 5min or more).
- If i plug the phone sometimes it stays off with the white led on, but rsd doesnt detect it, neither it goes on bootloader/recovery and sometimes it boots automatically sometimes doesn't come on at all.
Today:
- Tried to get the phone on this morning, it wouldnt go on or go into bootloader/recovery, then eventually it started up on its own and got stuck on the moto logo, i took the battery off and tried again, the phone wouldnt come on again, but eventually it started on its own and went to the bootmenu, where for the first time it crashed there, and it didnt recognise usb cable. I tried again and the phone booted up on its own with the usb cable to the bootloader,it gave the ok status for the usb connection but rsd lite never recognise it. Now it wont go on at all.
Please note that i have a desk charger and all this was done with a nearly full or full battery.
Does anyone know if the phone is completly dead now or if there is anything else I can do?
Thanks for the replies.
Mine just rebooting too
Dear derviansoul (",)
Hope all is well with you.
I just have the rebooting issue, like what you said (stayed on for 2-5mins before it goes off to reboot; phone never reboots in bootloader or recovery mode).
What i did was:
- i fell in love with Cyanogen mod 7.1.0-11 & 7.2-rc1 recently (thanks to Quarx & all in CM for your hard work);
- i had 32gb microsd card & decided to spent my hard-earned $ on a 64gb microsd card for this wonderful phone (due to CM, not Motorola);
- Sandisk microsd 64gb works AFTER erasing in Settings -> Storage;
- then, using Symantec Ghost 8.2 to clone my 32gb microsd card into 64gb;
- after putting in the clone-completed 64gb microsd card, the phone starts rebooting as described above;
- i tried to put back my own original 32gb microsd card, but the rebooting still happens!?!;
- in Recovery mode, i "wiped cache" & then go to "advanced", select "wipe dalvik cache", but problem remains;
- i formatted the the 64gb from Recovery mode, and manually copied the contents of the 32gb to 64gb using my WinXP computer, but the problem still remains!;
- (my solution) in bootloader mode, i go to "Tools" -> "share sd card", then from my WinXP computer, i can see the microsd card as Mass storage device, i deleted ONLY the folder ".android_secure" which is more than 2GB large.
- now there is no rebooting, and i just need to reinstall my apps from the Play Store, & my settings and data are all still there *sweet*.
Hope this helps.
Motorola Defy (red lens) cm7.2-rc1
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
DaFrenchTaco said:
Basically my phone fails to boot or do anything, power button is broken, it turns on when conneted to a charger. When its connected it vibrates and thats it, screen doesn't turn on nothing happens.
So basically the following happened I accidentally deleted "system/usr" but i had a copy and tried to copy back but was unable to do so. So i rebooted the phone, seemed to boot up normally however on the att boot up screen the phone froze.
I removed the battery and booted up the phone but it would freeze in the same att screen (I repeated this about 3 times)
After no results I booted my phone up in Safestrap recover which worked perfectly, in recovery I used the file manager to supposedly copy "usr" to "system" which supposedly did go through So i reboted the phone using reboot system option .
(Repeated this process about 3 times) still got stuck at last boot screen on the att logo.
So after this I repeated the process of copying "usr" to "system". But this time i rebooted to recovery thinking it would boot back to Safestrap,however it booted to stock android recovery.
In stock recovery I was able to navigate but I couldnt select anything (due to broken power button) so I removed the battery. This is when it all went bad the phone now wont boot. Only vibrates when connected to charger but the screen remains black.
EDIT: the phone boots back up to safestrap, however it still wont boot up. Still gets stuck on att boot screen (im suspecting because of the removed "usr" file) is there a way i can use The command terminal in safestrap to copy back the "usr" file.
Click to expand...
Click to collapse
Just reflash the rom you are on without wiping. That should fix it.
Is the phone an i337? If it is, you're in the wrong s4 forum.
GDReaper said:
Maybe, and just maybe, you could use ADB.
Otherwise you might have to somehow try and get download mode booting and re-flash stock rom.
Click to expand...
Click to collapse
Okay and suppose i could get adb working how would i copy the "usr" file back to the "/system"
audit13 said:
Is the phone an i337? If it is, you're in the wrong s4 forum.
Click to expand...
Click to collapse
Yea it is the i337 my bad i didnt noticed can it be moved?
Contact a moderator and ask him or her to move your thread.
Lennyz1988 said:
Just reflash the rom you are on without wiping. That should fix it.
Click to expand...
Click to collapse
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
DaFrenchTaco said:
Thank you this seemed to work, however my sd card wont mount.
Nor does my wifi turno on.
Click to expand...
Click to collapse
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Lennyz1988 said:
In cases like this it's best to backup everything you want and then perform a full wipe.
ps if you are still on 4.2.2. that means you don't have an locked bootloader right? Then why are you using safestrap? I thought that's only for when you have a locked bootloader.
Click to expand...
Click to collapse
I think AT&T and Verizon phones always had locked bootloaders, just that the earlier versions were easier to hack.
if its hard bricked, try jtag
thnx to everyone in this thread you were all of help my phone is now working even better then it did before much appreciated