Hi all, I have tried to flash all of the roms available and none aside from aokp 6.11 will boot. TWRP seems to flast the rom but I get a boot loop. Tried the new version of aopk 11.16 and same issue, I get a boot loop. Within TWRP I cannot factory reset as TWRP cannot mount /cache however erasing all partitions using fastboot does not seem to make any difference (I am not sure if erasing using fastboot is the same as the factory reset through TWRP). I have tried to flash back to stock and I get the green robot but then the device just reboots. To get back to stock I've extracted the recovery.img from the update zip and flashed using fastboot, then put the dload folder on the sdcard etc and as said I just ge a reboot.
The only rom that works is aokp 6.11 and even then wifi does not work and the power button just reboots the device.
I am about to give up. I've spent hours messing with the thing but to no avail! Does anyone have any ideas/solutions?
Related
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
Have u tried these fastboot commands
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
Okay, I've done that and then I flashed CWM Recovery through fastboot. I then booted into CWM and flashed the jokersax's CM9 ROM and rebooted. What I still get is:
No OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Available Modes are:
1 RSD
2 Fastboot
3 NvFlash
etc. etc.
It isn't detecting an OS still, and I don't get a boot icon just that menu. What would you suggest?
I'm thinking of trying this: http://forum.xda-developers.com/showthread.php?t=1421522
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
1. Re: CWM wipe and spazzed out touch screen: Sounds like you erased your PDS partition. If you made a back up, flash it. Otherwise search for a thread titled PDS Partition Fix (or something similar) here in the Q&A section for an alternative fix.
2. I don't recall if doing the PDS fix will also fix the missing boot logo. If not, you can find a stock replacement in the Themes section. You're looking for logo.bin.
That fixed it, thanks! I did a full wipe of those partitions then restored from my CWM restore. That didn't fix the screen but I tried that fix you suggested and everything is perfect now. Thanks for the help.
i am bricked with the kind of brick where i can boot into recovery and use fastboot, but cant boot into a rom. i tried using fastboot to reinstall twrp, but my internal sd is wiped and i am trying to push a rom to flash using adb push but it gives and error- read only file system even though i am pushing it to /sdcard. i tried going into adb shell and mount -o remount rw /sdcard, which works for small files, but the rom ive tried to push still has the same error any ideas? i really wish i backed up with nvflash, never thought i would get myself into this mess...
i am using this (http://forum.xda-developers.com/showthread.php?t=1773280) and it appears to be working... am installing the stock .28 blob...
am booting now... waiting... please... work... didnt work. ill try a different rom
I had a similar issue where I was stuck in CWM Recovery after selecting "Reboot to Recovery" from EOS ROM. I followed these steps: (http://forum.xda-developers.com/showthread.php?t=1514088) and my prime fully booted once again.
Have you looked into that thread?
i had similar problem after trying to update my prime. instead of updateing it booted recovery and keept doing that. the thread from last post helped me to fix this and flash a fresh rom.
ya i got it fixed in the end from that thread but i had to do extra steps because wiping data alone didnt do the trick. i had to go into fastboot, flash the linux boot img, flash a new recovery, and then because i wanted to go as close to stock as i could i flashed a stock rom for unlocked devices, then i did a data wipe and it booted. thanks for your help
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
Hi I have a SM-N910F model which is proving extremely difficult to flash. I firstly flashed the latest Marshmallow UK BTU firmware on it which resulted in a boot loop. I cleared cache partition and wiped data/factory reset in the stock recovery (and TWRM recovery) but this did not fix the problem. So I flashed the phone again and this time it was stuck in a boot loop with the text "recovering booting..." at the top left. Tried the same as before and still didnt fix it.
So I then tried a different stock rom - Lollipop UK BTU firmware. This gave me the exact same problems as before. However on a few occasions, I also got an error on the recovery screen saying cache could not be mounted. I cleared the cache partition, tried reformatting cache using TWRM but none of this worked. Eventually I reflashed and it went away but the boot loop doesnt go.
Lastly I tried an even older firmware - Kitkat UK BTU firmware. This again gave me a boot loop problem. It also kept displaying the cannot mount cache error as well. I tried using PIT file to repartition the device and eventually the error went but the device would still be on boot loop. However on two occasions the phone did go past the Samsung logo and show the first setup screen (where you select initial settings like Wifi etc). After like 10-15 seconds it would just switch off and then go back into boot loop. I havent managed to get to the first setup screen again.
I have tried flashing with various different Odin versions but still no luck.
I feel like I have exhausted my options and not sure what to do. Do you think I should try a custom rom? If so, for the sake of getting it to start, which is a good lightweight rom?
Does anyone know what I can do to make these infinite boot loops and/or "cannot mount cache" error go away?
Anyone? I could really do with some help..
I think you have problem with motherboard, try to find original stock frimeware, by country. If not help try custom rom. I suggest any AOSP rom such as Lineage OS or CM.
Tried 3 different stock roms. Like I said it will either be in a boot loop, recovery loop, or give an cache mounting error. Im hoping that the motherboard is not faulty because it is not always the same problem
Hi , I think is because You have FRP (Factory Reset Protection) On which means you can't flash property your phone .
What U can try is to extract recovery.img from latest stock firmware for your Region .
Now use this script to transform recovery.img to recovery.tar.md5
here is how to do :
https://forum.xda-developers.com/showthread.php?t=2446269
Put your phone in download mode click on AP: and choose recovery.tar.md5
After that click on Start .
If the flashing was OK , put again your phone in Download mode and flash completely the same firmware with original recovery.img inside it.
Good Luck
One guy from forums.androidcentral.com posted it work on sm-n910t, Android 6.0.1 .
hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore