Related
Hey everyone I have the Canadian bell carrier galaxy s3 which is rooted and I had used couple rooms such as Miui which I loved but was very buggy but recently been trying to load up roms and after it completes the install I click reboot nothing happens the screen is black so I have to boot to recovery and restore from backup tried multiple ones and same thing
1 I backed up on clockworkmod
2 performed factory reset, cleared Caches, cleared dalvik
3 installed from zip
Rebooted and nothing am I doing something wrong. Any advice would be appreciated thanks I just wanna run a stable version of the Nexus rom so I can just use it permanently
As far as I'm aware, that's an international ROM and impossible to flash.
The phone is rooted and clockwork mod to but someone told me the bootloader is Prolly not unlocked how do I find out if it's unlocked
I just tried to install the cynogen rom stable version and it said everything completed I rebooted and screened stayed black does anyone have a idea
With an issue like that I would do the following.
1. Wipe everything and I mean EVERYTHING!.
2. Return your phone back to stock/unrooted
3. Root your phone again and install your custom recovery (I like TWRP better as I've had less issue with it)
4. Before you flash whatever ROM, wipe everything again and then install your ROM
If that all doesn't work, I don't know what else will.
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
ThePedigree said:
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
Click to expand...
Click to collapse
need to reformat /system as well.
dipole said:
need to reformat /system as well.
Click to expand...
Click to collapse
..,before or after I flash it?
ThePedigree said:
..,before or after I flash it?
Click to expand...
Click to collapse
Before, you need to clear out remnents of old rom, reformat cache, dalvik, data (not sd) and system then flash rom and gapps if needed. Reboot.
dipole said:
Before, you need to clear out remnents of old rom, reformat cache, dalvik, data (not sd) and system then flash rom and gapps if needed. Reboot.
Click to expand...
Click to collapse
Thank you for your advice. I wish I had better news...
I Wiped the parts you mentioned. Installed ROM. Cleared Cache and Dalvik using the TWRP button that shows after installation. Rebooted, and there was no different result.
Tried it with both ROMs. Same results both times, except the non-stock ROM gives up and reboots in recovery mode after about three minutes. The stock ROM just stays stuck at Google logo.
Restore from backup still works.
Any other ideas, folks?
ThePedigree said:
Thank you for your advice. I wish I had better news...
I Wiped the parts you mentioned. Installed ROM. Cleared Cache and Dalvik using the TWRP button that shows after installation. Rebooted, and there was no different result.
Tried it with both ROMs. Same results both times, except the non-stock ROM gives up and reboots in recovery mode after about three minutes. The stock ROM just stays stuck at Google logo.
Restore from backup still works.
Any other ideas, folks?
Click to expand...
Click to collapse
Did you convert to GPE? If so you can't flash back to sense just yet
Also, check md5 of your download, might be corrupted
ThePedigree said:
I've got an AT&T M8 devices, and have installed the stock Kitkat version of Android on it. I found myself missing the (IMO superior) HTC camera app, and decided to flash either the stock Sense 6 rom or something based on it, like Android Revolution 5.
I booted into TWRP, backed everything up, and flashed the rom. When flashing was done, I cleared the Dalvik and Cache. The system then boots to a Google Logo with an unlocked lock at the bottom of the screen, and stays there until I do a hard reboot into TWRP. From there, I AM able to restore from backup, thankfully.
I thought I might not be waiting long enough for the ROM to do its magic, so I set a timer and let it stay on the Google Logo for a full 10 minutes. Still nothing.
I have tried this with the Stock Sense 6 AND the Android Revolution 5 ROMs with the same result.
Phone is S-Off. I'm coming from IOS for the last 3 years, so am probably missing something obvious, but can't seem to figure out what that is.
Does anyone have any ideas?
Thanks very Much.
Click to expand...
Click to collapse
Did you flash a gpe rom or convert using ruu?
an0ther said:
Did you flash a gpe rom or convert using ruu?
Click to expand...
Click to collapse
Converted using ruu. Thanks for your interest!
ThePedigree said:
Converted using ruu. Thanks for your interest!
Click to expand...
Click to collapse
You have to convert back to sense. The gpe partitions are the incorrect size for a sense rom. Follow steps in post #2 in this link to get back. Next time just flash a gpe rom. The only advantage to converting is ota updates, which in a rom, they will update those too.
http://forum.xda-developers.com/showthread.php?t=2708589
if you get lost let me know, when it says flash firmware, you have to use the "fastboot oem rebootRUU" mode that you used in the conversion
ThePedigree said:
Converted using ruu. Thanks for your interest!
Click to expand...
Click to collapse
HOW TO RETURN TO SENSE:
-Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
(fastboot oem rebootRUU, fastboot flash zip (whatever you name it).zip FLASH TWICE 1ST WILL FAIL )
-Boot Into OS
-Get Decrypt Error
-Boot back into Bootloader
-Flash TWRP- http://techerrata.com/file/twrp2/m8/...2.7.0.2-m8.img
(fastboot flash recovery recovery.img)
-Boot into Recovery
IMPORTANT!!!!!!
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
charlieb620 said:
HOW TO RETURN TO SENSE:
-Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
(fastboot oem rebootRUU, fastboot flash zip (whatever you name it).zip FLASH TWICE 1ST WILL FAIL )
-Boot Into OS
-Get Decrypt Error
-Boot back into Bootloader
-Flash TWRP- http://techerrata.com/file/twrp2/m8/...2.7.0.2-m8.img
(fastboot flash recovery recovery.img)
-Boot into Recovery
IMPORTANT!!!!!!
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
Click to expand...
Click to collapse
Thanks for your continued attention and generous efforts.
By "Boot into OS" do you mean simply reboot after the flash? I've done that and it shows the animated Google logo with the four squares of moving color. It seems to stay there for as long as I let the phone sit.
When does the Decrypt Error come into play?
Thank you!
ThePedigree said:
Thanks for your continued attention and generous efforts.
By "Boot into OS" do you mean simply reboot after the flash? I've done that and it shows the animated Google logo with the four squares of moving color. It seems to stay there for as long as I let the phone sit.
When does the Decrypt Error come into play?
Thank you!
Click to expand...
Click to collapse
Fastboot reboot
Also if that doesn't work, try wiping everything with Philz recovery
Sent from my HTC One_M8 using Tapatalk
charlieb620 said:
Fastboot reboot
Also if that doesn't work, try wiping everything with Philz recovery
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Just to clarify.... after flashing ROM I simply "fastboot reboot". How long (approx) should I wait and watch the Google logo before I assume things didn't work? Is more than 10 minutes normal?
Thanks much!
Less than 3 mins. If nothing change recoveries and start the process over. Try Virtuous rom fresh flash
Sent from my HTC One_M8 using Tapatalk
charlieb620 said:
Less than 3 mins. If nothing change recoveries and start the process over. Try Virtuous rom fresh flash
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Charlie, just curious, I'm happy with GPE conversion, but with your instructions are you saying that you reset the partitions back to sense? Or are you simply forcing the sense ROMS to use the GPE partitioning scheme?
dipole said:
Charlie, just curious, I'm happy with GPE conversion, but with your instructions are you saying that you reset the partitions back to sense? Or are you simply forcing the sense ROMS to use the GPE partitioning scheme?
Click to expand...
Click to collapse
Putting the partitions back where they belong if you want to go back to sense.
Sent from my HTC One_M8 using Tapatalk
whew thanks for this thread
I flashed a rom and then this problem started happening since. My phone tries to go to the samsung boot animation screen but never goes through it, it vibrates and then reboot, i tried installing stock rom, etc, i can now go to recovery and download mode.
You might need a jtag
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
errusdan said:
But if i can go through recovery and download mode, maybe there is something i could do to fix this issue?
Click to expand...
Click to collapse
I Can install firmware through download mode.!""
Me too, i tried installing stock firmware and all that. Even i am able to use the aroma filemanager from recovery, to see all my files, and when i delete system, preload, data, cache, etc i can see that in fact the device deletes them correctly.
Sorry I miss understand, you can go in download and recovery, my bad.
Have you tried factory reset, Flash original firmware, factory reset, let it boot
What was your original firmware which file(s) did you use?
When the thing you said happened i went on the store and Luckly they replaced my phone. Your phone probably ruined thats what happens when you play with it:cyclops:
Yeah i know that there are risks when you install another roms and such. I've read that it can corrupt your internal sd card, maybe that is what happened to me? because i tried installing different firmwares, kernels, recoveries, wipe data, wipe cache, wipe dalvik cache, wipe system, wipe preload, etc, even i tried installing boot animations, and it stucks at the boot animation screen samsung galaxy, it tries to load but then it vibrates and restart like a loop.
I am now with the russian 4.4.2 rom, and yes i know that i cannot downgrade because of the bootloader version. But i tried installing modified roms with zip (like cm 11) in recovery, and it installs correctly without errors, the problem is with the bootloop.
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Did you boot into recovery and do a factory reset in there. Sometimes that works.
jsgraphicart said:
Did you boot into recovery and do a factory reset in there. Sometimes that works.
Click to expand...
Click to collapse
Yep, every time I try to restore something I wipe everything. Also tried to lock and unlock the bootloader. No Luck.
Also tried wipe and erasing every partition possible, flashing an older 6.0.1 build.
Am I SOL? I tried anything google would give me....
Hey, I'm currently in the very same situation. Was on 6.0.1 stock rooted, applied 7.0 OTA using the beta program. Then for various reasons wanted to roll back to where I was with 6.0.1, but now the device just constantly reboots. I have wiped everything I can, tried to flash the factory images multiple times, but nothing seems to do the trick.
same problem here
i was on rooted android n preview 5 with twrp recovery and root, i applied 7.0 ota and then it bricked
now it starts up till bootscreen with the 4 coloured dots it freezes and goes in a bootloop but fastboot and recovery working fine
flashed a factory image wiped everything tried diffrent things restored a twrp backup but nothing
now im going to try to flash 7.0 ota again
Also in the same situation :crying:. Gets to the boot animation for 1 second then freezes and restarts.
Updated to 7.0 and got stuck in a bootloop.
Then tried restoring my TWRP backup to no avail.
Then tried flashing 6.0.1 factory image and still no luck.
Done factory resets, wiped system, data partitions etc, and still same problem.
If anyone has any other ideas that would be greatly appreciated!
this is what i tried so far
-wiped and restored 3 diffrent backups
-full wipe and flashed diffrent roms
-flashed factory image 6.0 and 6.0.1
-flashed 7.0 ota zip in twrp (extracted and flashed system.img and vendor.img )
-flashed factory image and used stock recovery to flash 7.0 ota.zip trough ADB sideload
i think im going to relock the bootloader and just send it back to google for a repair
I'm on the same situation
32 hours after updating to final 7.0 from stock dp5 the device turned off and stuck on boot animation
it seems like google did something wrong...
Looks like some people with the 6P are having the same issue as well. Still no fix either.
http://forum.xda-developers.com/nexus-6p/help/botched-nougat-install-phone-boot-loop-t3445709
I've had the same problem. I was coming from from a Pure Nexus install and thought i'd have a look at 7 so I made a full backup in TWRP then installed the lastest TWRP (twrp-3.0.2-1-bullhead). Then did a full wipe all bar internal storage and flashed radio/bootloader zip and Stock+ rom from the tupac4u thread which worked fine. Upon deciding there were a few dealbreakers for me I decided to go back to PN. So I booted back into TWRP, wiped again and restored the previously made backup. that's when I was getting the boot to 4 dots and reboot bootloop. I tried everything flashing various MM roms, and flashing 7 again, different roms / vendor images / full wipes including int storage, all via TWRP and ADB to no avail.
Though this evening I decided to go to an even earlier version of TWRP (twrp-3.0.0-1-bullhead) and try everything again. I flashed that and tried the repair filesystem on all the partitons I could, one of them gave an error I can't remember what it was. After doing that I did a full wipe and restored my PN backup, everything ticked. I then rebooted with everything crossed and it worked, it booted without any problems! (apart from the fact i'd forgot to remove the pin security before backing up so had to reflash anyway! which also worked). I can't be sure which part of that fixed it but if it helps anyone else that's great!
People with this problem - Does flashing new Factory Image 7.0.0 (NRD90M) fix something?
Just curious.
zeesyl said:
People with this problem - Does flashing new factory image 7.0.0 (NRD90M) fix something?
Just curious.
Click to expand...
Click to collapse
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
MiePx3 said:
Background:
1. Was on the latest Resurrection Remix. Made a Backup with TWRP.
2. Went back to stock [MTC20F] using this.
3. Updated to 7.0 using this threads 7.0 OTA.
4. Made a Backup in TWRP.
I restored the backup from point 1, but now my phone won't boot anymore.
It shows the boot animation for about 1 second. Goes black and reboots.
I tried restoring to 6.0.1 using the method in point 2 -> same problem.
Tried restoring to 7.0.0 using the same method -> same problem.
After that, I tried restoring from both of my TWRP backups. Neither of them get any further.
So, no matter what I do I cant get past the first second of the boot animation.
I'm out of ideas, any help is greatly appreciated!
TWRP version 3.0.2.1
Click to expand...
Click to collapse
Type fastboot -w flash falsh vendor vendor.img then restore from your twrp backups
neaznc021 said:
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
this worked for me
neree said:
Nope, changed nothing in my case at least. At this point I'm just going to use the warranty card to get out of this mess, as nothing seems to revive the device.
Click to expand...
Click to collapse
Did that yesterday (With my N6P), will see what will come out of it. (Service guys said, that ''Oh, it's nothing serious, tomorrow (today) you will get your phone back (hopefully in working condition)''. I'm not so sure about that
(EDIT: Before I took my phone to warranty service, I flashed latest MM factory image and locked bootloader, maybe it was unnecessary, but I wanted to be sure, that phone looks fresh, maybe it was a big mistake.)
I had the same Bootloop issue, and it's all because of TWRP 3.0.2-1 !!! I have just reverted back to TWRP 3.0.2-0, and my backup restored just fine. There's no point for all that flashing. Just revert the TWRP.
Oh my... Guess what? My backup is corrupted...
Edit: maybe this can help, before bricking with full factory image, I flashed bootloader, radio, boot, vendor, system, Elementalx and supersu, wiped data and booted and work.
But I had problems with suspersu installed as systemless (it didn't work), so I flashed factory image. And bootlooped.
So, I'd say that what's causing issue is userdata, recovery or cache.
As i told in the title. I absolutely can't boot any rom but one. I have AICP on but i can't switch to any other rom. Even Stock roms!
Everytime i flash a rom, it gets flashed, i reboot the phone, i get the one plus logo and then the phone turns off and reboots back into twrp. i tried booting stock roms with stock recovery too and that did not work either. device is decrypted. nothing i do seems go work. Help would be appreciated asap.
Try backing up all of the stuff on the /sdcard partition, do a superwipe, flash stock recovery, then sideload OOS
That's what I do if I get a brick. OnePlus made their phones easy to fix
Make a backup of your data (/data, download, pictures, camera, etc). Move it onto your pc/otg drive. Format your internal storage via TWRP. Flash your rom of choice. Post back results.
Flash dm-verity at the end of the sequence, after ROM, Gapps, etc...
https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144