I bought a new Nexus 4 from the Playstore and I updated it from 4.2.2 to 4.3 when I first got it, used it for a day or two and when I restarted the phone it was stuck in a bootloop on the X screen. After further research I found that this was a common problem with the 4.3 update and I've tried a few solutions to no avail.
I've put it in the fastboot mode and recovery mode and tried to wipe the cache and factory reset the phone via recovery mode but I'm still stuck in the X screen.
Please note I can't turn on usb debugging or developer options because I can't access the phones operating system and also its stock not rooted.
I don't want to send it to google if there's a way to fix the software via flashing the rom because I was planning on doing that anyways, this is the first time I'm trying to customise software on a non Samsung Device (Galaxy S1, Note 2, Ace).
Any response would be appreciated.
Since you already know how to access the fastboot screen, you just need to connect the phone, install the adb/fastboot driver and flash the factory stock image. Check this guide (its in the stickies): http://forum.xda-developers.com/showthread.php?t=2010312
(The download the platform-tools attached in the post, it has the adb and fastboot software you need to do the flashing.)
Also make sure to post in Q&A section next time.
Related
Hi Guys,
I brought my LG G2 D802 32GB last week and I believe it's possibly hard bricked if not soft bricked so let me start by saying that anyone who can help me get my brand new G2 working will be receiving some beer money!
I've owned over 15 android devices over the years and i'd say i'm a competent flasher but I've never had such a problem flashing any of those devices as I have on the G2!
So here's what I did:
1) Updated Phone to 4.4.2 and rotted using IOroot method (Root was successful)
2) Install LG USB Drivers
3) Flashed CWM 6.0.4.4 (Flashed successful and CWM was working fine with Root access on ROM)
I then decided to put TWRP as the recovery because after much research it seemed to be the most popular choice.
4) Downloaded D802_AutoRec.apk (I believe this was the correct recovery for my device)??
here's what happened:
After using AutoRec to flash TWRP recovery I rebooted and the phone displayed:
450 Fastboot mode started
500 udc_started()
Plugging in the USB cable then adds the following lines:
660 -reset-
670 -portchange-
740 fastboot; processing commands
Note that Download mode WAS available at this point.
I then tried flashing CWM recovery again through fastboot which showed as successful but still stuck in fastboot after rebooting. The same happened for TWRP.
I then went to the LG website, put in my IMEI number and downloaded the stock ROM (D80220C_00). I used the G2 extractor to extract the kdz to a DZ file then extracted the aboot/boot & laf.img. Since I did this I have lost download mode!
It's interesting to note that fastboot shows attached device as:
? fastboot
and ADB shows no attached devices.
I'm not sure this is relevant as I still seem to be able to push commands to the phone through fastboot?
I then tried to flash the stock ROM (D80220C_00) using LG Flash Tool however it gets to 27% and says "cannot connect to the phone
So as it stands at the moment all I have is the option to flash using fastboot, I have no download mode, no recovery or no working ROM. Have I completely bricked my phone or is there anything else I can try to get the stock ROM back on there?
Any help is massively appreciated!
Hello!
Try this, I hope it helps!
http://forum.xda-developers.com/showthread.php?t=2477595
thank you but I have and I still can't get into download mode....fastboot only
vPro97 said:
Hello!
Try this, I hope it helps!
Click to expand...
Click to collapse
Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks
start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Have you tried Download mode ( vol - home button and power button) ?
Viesuliss said:
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Click to expand...
Click to collapse
Just download official firmware and flash with odin. (Make sure not to downgrade os version. )
go to downloadmode, be sure drivers are installed, COM must be green,flash firmware with odin "only PDA", return into bootlader after reboot, flash twrp, boot into recovery mode done
Same thing happened to me.
Don't search for any file, the solution is very simple: download Samsung Smart Switch (only Windows, Mac version didnt work for me).
On menu click "Others" then "Emergency software recovery". Write A510F and then your phone Serial Number. Wait 30/60 mins ?
Sent from my SM-A510F using XDA-Developers Legacy app
Here's another rooting guide for SM-J530F/DS (Dual Sim) stock ROM. Even with Lineage OS my hardware model (ordered March 2018, EU SIM card only) tends to mute the main speaker after rooting. This rooting method works for me and is based on the work of others, especially ananjaser1211 and Abdullah_a86.
Make a backup of everything and make sure that the backup is usable. You are responsible if following this description and flashing bricks your phone. It did work for me which does not mean that it also works for you.
Enable Developer options. (Settings, About phone, Software information, tap a few times on Build number)
OEM unlock the phone. (Settings, Developer options, OEM UNLOCK: enable - otherwise you will bootloop)
Reboot into download mode.
Flash J530F_TWRP_3.2.1.0.tar (in AP) with Odin.
Now TWRP is installed and you should be able to use your phone as usual or to boot into TWRP recovery.
Rooting will erase everything, verify your backup again unless this is a new phone.
Reset the phone. (Open Settings, About Phone, (Looking for something else?) RESET, Factory data reset, Reset, DELETE ALL)
Reboot into recovery, a cleanup script will run and reboot after a few seconds.
Reboot into recovery again, install SuperSu and reboot (wipe nothing).
Starting takes a little time, after running the initial setup SuperSU is installed and the speaker works as expected.
I started here a few times after no-sound, no-root and/or bootloop experiences with LineageOS, CF-Autoroot and Magisk. If you upgrade to this firmware version you can no longer downgrade to a previous firmware version. Follow this only if you break something, want to un-root, update your firmware and/or start from scratch:
Force a reboot if necessary and then boot into download mode. All data on the phone will be lost.
Flash the J530FDBT2ARB3 firmware with Odin (AP*, BL*, CP* and CSC*. Do not use HOME_CSC*).
Now you have again a phone with stock firmware without root.
Links:
Odin (3.12.3): https://samsungodin.com/download/
TWRP (3.2.1-0): https://forum.xda-developers.com/ga...twrp-samsung-j5-pro-twrp-3-1-10-v2-0-t3728233
SuperSU (2.82): https://forum.xda-developers.com/ga.../guide-root-samsung-galaxy-j5-pro-sm-t3720446
Optional (also older firmware or a firmware backup may be used):
Firmware (Android7 J530FDBT2ARB3 2018-02-08): https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/DBT/download/J530FXXU2ARB3/210251/
Hints:
Power+Home+VolumeUp = Recovery
Power+Home+VolumeDown = Download Mode
Power+VolumeUp+VolumeDown = Force Reboot
PS: If a mod wants to move the thread to https://forum.xda-developers.com/ga...17-roms-kernels-recoveries--other-development please just do it and remove this comment. My reputation is too low to post there.
Hello, could you help me ? Odin doesn't recognize it, pc shows drivers being installed, but nothing shows up on odin, tried different version of odin.
aofthe said:
Hello, could you help me ? Odin doesn't recognize it, pc shows drivers being installed, but nothing shows up on odin, tried different version of odin.
Click to expand...
Click to collapse
Enable OEM unlock and USB debugging in developer options
garylawwd said:
Enable OEM unlock and USB debugging in developer options
Click to expand...
Click to collapse
Yeah, they were already enabled.
Hello again, i managed to fix Odin problem, it installed Twrp and said pass, with green, but when i tried to enter recovery mode, it went downloading, and the no command, phone boots normally, but i got no recovery, any suggestions ?
Download Mode Fix
aofthe said:
Hello again, i managed to fix Odin problem, it installed Twrp and said pass, with green, but when i tried to enter recovery mode, it went downloading, and the no command, phone boots normally, but i got no recovery, any suggestions ?
Click to expand...
Click to collapse
I think this might fix you booting into download mode problem try this post. Read "how to fix" near the bottom. Please Thank us if it does. This same thing happened to me and I wish I stumbled across this earlier because I figured this out on my own by just messing around going from recovery to download mode and it eventually fixed itself.
Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Kamen911 said:
Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Click to expand...
Click to collapse
same problem. stuck on bootloop on stock recovery
https://www.youtube.com/watch?v=cDRsEsI0qBY
Have you guys tried this method, yet?