Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
ThuanBui said:
Hi all,
First time posting on here (but I read the forums often - for guides etc).
Bought the Nexus 4 and I unlocked the bootloader and rooted the device. Kept to the stock Android (JB 4.2) however I locked the bootloader again.
The boot loop occurred after a restart after I did the following things:
1. Used Battery Calibration to calibrate the battery. Left the battery to drain and then charge to 100%.
2. Used VM Heap to change the amount and restarted the phone. Boot loop ocurred.
I have tried many things after reading this forums and other forums but there seems to be no answer to this issue.
Things I've tried are:
1. Booted into recovery mode and wipe data/factory reset many times - still has boot loop
2. Used Nexus Root Toolkit and tried the various functions on there. Fastboot doesn't detect the device (even though its in fastboot mode) in order for me to unlock the bootloader again and flash it with the stock ROM. Windows (8) does detect it but can't load drivers for it. Been through all the instructions on the Nexus Root Toolkit - reinstall drivers, cleared the device from device manager, cleared it from usb list etc. Fastboot just won't detect it to allow me to unlock!!
3. Let the battery drained and tried factory resetting but doesn't work (not tried fully charging it and then resetting though)
4. Been trying various other things which I read on the forum(s) but nothing seems to work!:crying:
Literally spent the whole day trying so many different things. Seems like I discovered a whole new unique problem to causing boot loop on the Nexus 4. I don't want to have to send this back to Google for a replacement if they give me one - hopefully with the locked bootloader and the data cleared, they won't know I've rooted, not to mention its micro-sim and my backup feature phone doesn't take micro-sim :crying:
Has any one had this issue before and fixed it!? Would really appreciate the help/guidance!
My first time rooting a phone, didn't do it before on other phones because thought knowing my luck I'd brick it beyond repair! Luck would have it, that exactly what has happened.
Appreciate the replies and help on this!
Click to expand...
Click to collapse
I'm having the same problem!
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
andr0idfreak said:
For the toolkit to see the device, you need to put your device to fastboot mode by pressing vol (-) and then the power button (the phone should be in powered off mode to do this).
Click to expand...
Click to collapse
I've done this many times but still no luck
ThuanBui said:
I've done this many times but still no luck
Click to expand...
Click to collapse
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
monkeying. around said:
I had a boot loop issue. It was stuck on Google logo - the white logo.
I couldn't go into recovery either.
My fix was to flash the stock recovery.IMG
I too couldn't detect the device however I kept trying.
If you face a problem getting into fast boot mode try pressing vol up + vil down + power. Didn't work for me but worked for some.
Let me know how it goes I'm glad to help out if I can
Click to expand...
Click to collapse
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
sideloading 4.4.2 and stuck on boot loop
ThuanBui said:
Didn't fix it in the end...no matter what I tried. I got a replacement from Google (thankfully they didn't charge me for the new one!).
BTW the batch of Nexus 4 released in end of Jan/early Feb has a much better battery life than the one I got from the batch released in early Dec. Won't be rooting the new Nexus 4 in case sh*t happens again but no doubt will get tempted again somewhere down the line!
Thank you to everyone who replied!~ :good:
Click to expand...
Click to collapse
bro mime nexus 4 has stuck into boot loop after upgrading from 4.4 to 4.4.2 .i was sideloading the zip dont know whats the issue ......i was rooted but went to stock via nexus roottool kit to get OTA . any suggestion
joshnichols189 said:
Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT.
Click to expand...
Click to collapse
all you got to do is download the toolkit and flash the software your phone is using and put it in fastboot and begin
:good::good::good::good::good::good::good:
Hi,
My SM-N910F is stuck on the samsung logo after rebooting. This happend after I flashed it with a new stock image N9005XXUENC2_N9005VFGENA4_VDI (My provider is Vodafone in Ireland) and now it is stuck on the samsung logo.
I can get into download mode but not in recovery despite having flashed PhilZ's recovery. I have let the battery run down to zero and then tried to reflash it but that didnt help. I have tried to flash with the box ticked to erase everything but no joy. I get through the flashing fine but when it reboots after having gone into recovery it hangs on the logo and I cant get it to go further. Can anyone help?
(ps I did have a look through the other threads first)
Cheers
P
The clue is in the question, N910F/N9005.
You flashed a Note 3 firmware.
Sent from my SM-N910F
Nice catch JagDave!
RESOLVED!!!
1) I removed the battery
2) reinserted it
3) Booted into Recovery (volume up, home and power).
4) Wiped all cache
5) Reset the device to Factory settings
6) Rebooted and other than a basically new device no harm done!
Goodluck!
PR
PS: I was reminded of this by http://androidjinn.com/install-n910fxxu1anj4-android-4-4-4-kit-kat-firmware-galaxy-note-4-sm-n910f-2.html
JagDave said:
The clue is in the question, N910F/N9005.
You flashed a Note 3 firmware.
Sent from my SM-N910F
Click to expand...
Click to collapse
My Bad because I copied the name from my back up Phone's newly downloaded update, because i tried after I posted here with a note 4 rom
But I agree good catch!
Hello, i just grabbed a semi used Nexus 7 2012 .. it was running on android 5.1.1. i didnt like it thats why i tried to downgrade it to kitkat, everything was fine but when i tried flashing the ROM, an error popped up, I Decided to power off but when i tried turning it on, it wont anymore,
Before the incident, the only thing i did was to unlock the bootloader, wipe cache wipe data etc. is there any solution now in this problem? i cannot enter fastboot . adb it was all black even when i tried to charge the tab... any help would be appreciated , thhanks,,,
any replies please?
Charge over night. Make sure battery's not low.
Sorry.
Hi all!
Here is a little problem that i didn't solved.
i have a N910F Note 4 that likes to boot loop . I received it as it is and don't know what caused it(i suppose that was a rooting issue because had the knox value 1)
During the all time, PC and MAC were unable to recognize the Note 4, despite of repeatedly reinstalled drivers(older and newer versions) , Keys and Smart Switch were unable to recognize the device, PC is failing to install the MTP driver for some reason. I changed the USB ports,restarted,updated drivers,updated windows etc. -NO RESULT. BUT : Somehow Keys is able to run recovery and initialization and install it on the device while saying Connecting device... , phone also doesn't appear in device manager or file explorer as external drive.NOTHING! Odin and Jodin says ''added!'' and starts the job with no comments
1. I tried different versions of boot loaders with different versions of ROM (all for my specific model) with no result.
The end of the boot is when Samsung logo ,sound and graphic appears but freezes before actually starting OS, then restarts. IT keeps restarting until battery goes off(even while connected to pc by usb!!! ). Then starts to charge the battery normally.
It boots in recovery and download mode with no problems, it did every time i flashed it…
2. I tried different versions of boot loaders with stock roms , custom kernels etc...and the problem was the same
3. I tried to flash with Odin the stock 4.4.4 without problems but….the problem was the same
4.I tried Device recovery and initialization with Keys and here something interesting happened:
First time when i did it, it went over the samsung logo and booted. I selected language,i skipped wifi network selection and i accepted the user agreement. No matter how fast i was moving, the boot loop didn't went over the user name selection which is after the user agreement. Then freeze and boot again.
Second time when recovered with Keys (tried more stuff in the mean time) it went over the logo and started to update like…''updating applications 2of 17'' the max reach point was ''3 apps of 17'' and then freeze and reboot
I am out of ideas so i suspect that the battery might be dead because it gets empty even if is charging while phone is ''boot looping''. I ordered a battery,should arrive soon.
If that don't work…i am gonna spend some cash and sent it to Samsung for repairs (i bet that it won't be cheap because they will probably tell me that is the motherboard fried so they make you pay for being a bad boy and tried to root). Far as i know is not a brick as long as download mode and recovery works just fine.
Is here someone that has any new ideas for bringing this phone to life? Any help is well received , maybe i skipped something….
Thank you in advance.
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Battlehero said:
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Click to expand...
Click to collapse
That was the first thing i tried , cache wiped also. After every rom when booting failed.
UPPME said:
That was the first thing i tried , cache wiped also. After every rom when booting failed.
Click to expand...
Click to collapse
Uninstall Kies, and install Samsung USB drivers: https://www.androidfilehost.com/?fid=24052804347849220
Take the battery out, leave it for approximately 10 seconds, enter the battery back in.
Hold volume down key + Home key and power on the device.
Then plug the mobile phone into the computer.
Run Odin as Admin: https://www.androidfilehost.com/?fid=24052804347851815
Then flash the firmware in the AP section.
Make sure that the firmware is for your region, you can download it from Sammobile or SamFirm.
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
kerbiii said:
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
Click to expand...
Click to collapse
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
UPPME said:
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Click to expand...
Click to collapse
if you can stay in recovery mode and download mode for more than 10mins i think its not battery problem, i think i have corrupted system files, i left my note 4 to samsung service center a while ago i will get it tom, i just hope they wont charge me too much for it,
uldyzjan said:
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
Click to expand...
Click to collapse
nah it doesnt work thats the first thing I do, that only work on ordinary bootloop
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
kerbiii said:
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
Click to expand...
Click to collapse
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
guts100 said:
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
Click to expand...
Click to collapse
yes thats the good thing and its under warranty even though im already rooted, with knox 01 and custom binary haha, i was already expecting to pay a huge amount of money but they said they will cover it, so its a blessing, but i hope the OP fixed his problem.
So 2 nights ago I decided to switch from a stock based 7.1.0 mi favor 5.0 rom back to lineage os.
Backed up all my goodies, went into twrp wiped out everything. moved my few flashable zips back onto storage and attempted to install
Every time I try to flash any rom at this point It refuses to complete (I tried a few other roms) I also tried to go back to the stock based rom and failed.
flashed bootstack and modem again as supplied in the lineage os page and I am certain I used the files for my phone.
got trapped in edl mode.
used the axon 7 toolkit to recover back to stock. stock wont boot (waited 20 minutes and gave up on boot screen)
got twrp installed again.
twrp cant see internal storage SDcard but my computer can. I had no way to flash any files without going and buying an actual sd card
get into edl mode and recover to stock again (still wont boot) so Installed twrp
twrp can see sd card again so I tried to flash lineage once more (still wont complete) after 10 minutes I give up and reboot
twrp wont mount a few partitions now cache etc.
My next move would be to boot to edl and restore to stock again and get twrp working.
My problem is I expect twrp will still fail to flash any rom.
am I missing something big here? am I just an idiot with a pretty paperweight?
Is it possible that there is some deeper problem with my phone? its been exposed to extreme cold/heat dropped many times, magnets, steel dust etc. over the last 2 years.
I will try any good suggestions anyone has, if anyone is willing to help me.
Also feel free to call me an idiot for any of the many dumb things I did (not making a backup etc.)
Just flash stock version with miflash and EDL.
Gesendet von meinem ZTE Axon 7 mit Tapatalk
^ just that. I did couple stupid moves trying out Oreo and ended up with blank system, but since bootloader was unlocked and EDL mode is independent of everything else and we have nice tools to just flash using it - viola.
marcus.linkenbach said:
Just flash stock version with miflash and EDL.
Gesendet von meinem ZTE Axon 7 mit Tapatalk
Click to expand...
Click to collapse
That's the thing. I did that. The first time it flashed but wouldn't get past the first axon screen (before the "your bootloader is unlocked" screen) and the second time it just wouldn't complete a boot. After 20 minutes I gave up. I guess I'll try again and give it a few hours for first boot time if I need too...
@masong397 get it into EDL .. power off and then power on holding vol up & down plus power for 15 seconds until you get a black screen and hear your pc bing that a device is connected .. then run miFlash and refresh so you see COM4 for example then select it and flash "ZTE_AXON_7_BOOTLOADER_UNLOCK_IMAGES_BY_TURKDEVS" This will at least get a bootloader working for you again