Related
The simple method to revert back to stock ICS from a custom ROM on an A100.
+++Locked bootloader, no custom recovery, no root. Full stock .014 rom. It will recieve OTA updates to latest Acer version.+++
Get Ready
1) Download this flashable Stock recovery zip, and place in your normal flashing location, - Thx 4 help pio
http://db.tt/VLmnMCzq
Also uploaded below
2) Download the Official .014 Stock ICS rom
The stock ICS zip from zeronull. http://forum.xda-developers.com/show....php?t=1611696
Here is a second link to it. http://ubuntuone.com/7DZtbNqZzOk7qsaQxNk99a - thx zleto
3) Rename the Stock ICS rom to "update.zip", no quotes (make sure you have "hide known file extensions" UNCHECKED, in the folder options). And place it on the root of your microSD card. This will allow you to see the file extension to verify that it is named properly.
Get it Done
1) Flash the Stock recovery zip with your custom recovery. Then wipe cache, davlik cache, and wipe data/factory reset.
2) Reboot to system.
3) Allow it to sit for 5 minutes or so.
4) Then Power off.
5) Update from the microSD card by holding down the power and volume rocker closest to the corner at the same time, until you see "erasing cache .".. ect, ect. The stock rom install should start by itself, dont touch anything, wait for it to reboot.
****** If it won't boot do a factory reset (with the hardware buttons, see below) and/or try to reflash the ics rom one more time. ******
To perform a Factory Data Reset use the following steps:
1.Place the rotation lock switch in the up position (tablet held in portrait). Or to the left if held in landscape.
2.Press and hold the Volume down button, which is located farthest from the corner (it is volume up, if held in landscape).
3.With the Volume down button held, press and hold the Power button for 3 seconds then release it. Continue holding the Volume down button.
4.Once the tablet vibrates, switch the rotation lock on and off repeatedly while still holding the Volume down button.
5.Release the Volume down button and stop switching the rotation lock once the "Erasing Userdata..." message appears in the upper left corner of the screen
Click to expand...
Click to collapse
If you want you can go to settings > about tab and check for updates, it should update at least one time. At the moment I believe the latest build # is .037. It may take a few days for it to find the update/s.
Enjoy.
Sticky this!
Works great! This should be stickied!
Nice.
Hope i never need it though. Lol
Sent from my LG-P999 using xda premium
:laugh:
xda_rulz said:
Works great! This should be stickied!
Click to expand...
Click to collapse
Thx, your post made me get working on it, I've been thinking about it for a while. Just made up the flashable stock recovery. It makes it alot easier. Thx to pio for his help.
All you man, picking up my slack lol
Edit: did you want a host for it? I can put it on goo or something for you.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Do you loose root by flashing this?
Sent from my A200 using xda app-developers app
cowboyv said:
Do you loose root by flashing this?
Sent from my A200 using xda app-developers app
Click to expand...
Click to collapse
Yes, you will lose root when you flash the stock ROM. Gaining root again is as simple as re-running zeronulls root tool.
Romman0 said:
Yes, you will lose root when you flash the stock ROM. Gaining root again is as simple as re-running zeronulls root tool.
Click to expand...
Click to collapse
Will this lock the bootloader or will it remain unlocked?
Kalmarin said:
Will this lock the bootloader or will it remain unlocked?
Click to expand...
Click to collapse
Locked bootloader, no custom recovery, no root. Full Stock.
I tried the guide here to return to stock but the update will not install, I was able to install the recovery but every time I try to install the update.zip it hangs in the screen with the android and has a red triangle inside of it. It stays on that screen for about 2 minutes and then reboots to my current rom
SPIK3 said:
I tried the guide here to return to stock but the update will not install, I was able to install the recovery but every time I try to install the update.zip it hangs in the screen with the android and has a red triangle inside of it. It stays on that screen for about 2 minutes and then reboots to my current rom
Click to expand...
Click to collapse
Check to make sure you have 'hide known file extensions' unchecked in the folder options. And verify the stock ICS file is named update.zip, and not update.zip.zip.
Romman0 said:
Check to make sure you have 'hide known file extensions' unchecked in the folder options. And verify the stock ICS file is named update.zip, and not update.zip.zip.
Click to expand...
Click to collapse
I checked and it is named just update.zip, I also tried re formatting the sd card and re downloaded the update but still no luck.
SPIK3 said:
I checked and it is named just update.zip, I also tried re formatting the sd card and re downloaded the update but still no luck.
Click to expand...
Click to collapse
Bad download and/or transfer to the SD card, its extremely picky about it.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Bad download and/or transfer to the SD card, its extremely picky about it.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
I keep trying, thanks.
SPIK3 said:
I keep trying, thanks.
Click to expand...
Click to collapse
Updated OP to include a reboot to system after installing the stock recovery, let it sit for a few minutes. Then power off. Reboot to recovery by pressing power and volume rocker closest to the corner at the same time, release after it starts reporting Erasing cache... ect, ect... The update should begin. Give it 5-10 minutes, it should reboot.
I just did this procedure on my tab, running TWRP 2.2.2.1, gmv2.0 kernel and CM10. Now I have to unlock again, and restore, lol.
-
-
Edit back up and running after restore.
Romman0 said:
Updated OP to include a reboot to system after installing the stock recovery, let it sit for a few minutes. Then power off. Reboot to recovery by pressing power and volume rocker closest to the corner at the same time, release after it starts reporting Erasing cache... ect, ect... The update should begin. Give it 5-10 minutes, it should reboot.
I just did this procedure on my tab, running TWRP 2.2.2.1, gmv2.0 kernel and CM10. Now I have to unlock again, and restore, lol.
-
-
Edit back up and running after restore.
Click to expand...
Click to collapse
That's dedication there dude. I don't risk flashing anything but roms/kernels.
Scared of emmc death.
G2x-temasek CM7 build135.3 w/faux 054 kernel
Romman0 said:
Updated OP to include a reboot to system after installing the stock recovery, let it sit for a few minutes. Then power off. Reboot to recovery by pressing power and volume rocker closest to the corner at the same time, release after it starts reporting Erasing cache... ect, ect... The update should begin. Give it 5-10 minutes, it should reboot.
I just did this procedure on my tab, running TWRP 2.2.2.1, gmv2.0 kernel and CM10. Now I have to unlock again, and restore, lol.
-
-
Edit back up and running after restore.
Click to expand...
Click to collapse
Thanks, this worked. :good:
SPIK3 said:
Thanks, this worked. :good:
Click to expand...
Click to collapse
Yw. Don't forget to check for updates in the settings > about tablet. I think the latest update build is .037.
I tried this stock restore out of necessity. I tried a downgrade to HC. seems like the update took successfully. It self rebooted but wouldn't get past the bootloader screen. It said "bootloader (some version) unlocked ICS" with white ACER logo clean in the middle.
I tried zn's stock ics restore and worked like a charm. (saved my butt is what it did)
Now that I'm back to stock 4.0, how can I downgrade to 3.2 from here? There are some good things in 3.2 like acersync and other.
I'd like to be able to switch between versions when I need to.
I have no problem upgrading to some custom version, if needed first.
Thanks for any help.
ponjanek said:
I tried this stock restore out of necessity. I tried a downgrade to HC. seems like the update took successfully. It self rebooted but wouldn't get past the bootloader screen. It said "bootloader (some version) unlocked ICS" with white ACER logo clean in the middle.
I tried zn's stock ics restore and worked like a charm. (saved my butt is what it did)
Now that I'm back to stock 4.0, how can I downgrade to 3.2 from here? There are some good things in 3.2 like acersync and other.
I'd like to be able to switch between versions when I need to.
I have no problem upgrading to some custom version, if needed first.
Thanks for any help.
Click to expand...
Click to collapse
You can downgrade from stock ICS to stock HC. But make sure your ICS is completely stock. You need to factory reset after flashing the HC update. I made a post about it as while back, with a hc ROM link.
http://forum.xda-developers.com/showpost.php?p=29871277&postcount=14
Had my note 2 for several months now on Wind Mobile. I woke up this morning and it was working fine, went out for a walk and 5 minutes into the walk my phone was stuck in the boot loop. I never flashed or rooted my phone. Its stuck where the samsung logo comes up and the blue and purple halo circles it. I have access to both the volume up+home button+power button menu, aswell and the volume down menu. I already cleared the system cache and was wondering what to do?
If possible i would like to be able to extract my data before doing a factory reset. Any help would be great!
It doesnt seem that wiping data will fix your problem it looks like system corruption try flashing new software
Sent from my GT-N7100 using xda premium
Note2Dan said:
Had my note 2 for several months now on Wind Mobile. I woke up this morning and it was working fine, went out for a walk and 5 minutes into the walk my phone was stuck in the boot loop. I never flashed or rooted my phone. Its stuck where the samsung logo comes up and the blue and purple halo circles it. I have access to both the volume up+home button+power button menu, aswell and the volume down menu. I already cleared the system cache and was wondering what to do?
If possible i would like to be able to extract my data before doing a factory reset. Any help would be great!
Click to expand...
Click to collapse
You will have to factory reset your device not sure if there is a possible way to recovery Data as its not booting.
aukhan said:
You will have to factory reset your device not sure if there is a possible way to recovery Data as its not booting.
Click to expand...
Click to collapse
cleared cache, flashed new stock rom, and wipred all data. still stuck in boot?
Note2Dan said:
cleared cache, flashed new stock rom, and wipred all data. still stuck in boot?
Click to expand...
Click to collapse
SIMPLE goto stock recovery and do a factory reset that will boot up your device.
aukhan said:
SIMPLE goto stock recovery and do a factory reset that will boot up your device.
Click to expand...
Click to collapse
Did this multiple times, also when i go to that menu it says cannot mount efs
Note2Dan said:
Did this multiple times, also when i go to that menu it says cannot mount efs
Click to expand...
Click to collapse
this seems to a new level let me check on this.
Note2Dan said:
cleared cache, flashed new stock rom, and wipred all data. still stuck in boot?
Click to expand...
Click to collapse
have u tried using odin flashhttp://www.nobutaka.es/web/index.php/component/jcomments/feed/com_content/203.html
shhbz said:
have u tried using odin flash
Click to expand...
Click to collapse
Yes i used odin to flash the stock rom, did not work.
Note2Dan said:
Yes i used odin to flash the stock rom, did not work.
Click to expand...
Click to collapse
give this a try translate using google translator http://www.nobutaka.es/web/index.php/component/jcomments/feed/com_content/203.html and follow the procedure
shhbz said:
give this a try translate using google translator and follow the procedure
Click to expand...
Click to collapse
Ok, will try in the morning. Google translate doesnt seem to give a very clear translation of the page but i will try my best.
shhbz said:
give this a try translate using google translator and follow the procedure
Click to expand...
Click to collapse
Im trying to follow this guide but it gets confusing, ive manage to download adb + fastboot but im not sure where i go from here.
Note2Dan said:
Im trying to follow this guide but it gets confusing, ive manage to download adb + fastboot but im not sure where i go from here.
Click to expand...
Click to collapse
well u need to set up adb in windows and make sure its connecting with your device
u need to flash stock then chainfire auto root
check if its entering recovery now then proceed with adb hopefully u have efs backup .tar file safe in pc or anywhere ,search google how to set adb
it seems to be an issue with efs partition,
i blv this can be even done by flashig pit file http://d-h.st/Dlv here and then the stock firmware.
and since u have never rooted use ur warranty and give it to service guys if not able to solve
edit:read this thread in english hope u understand now http://forum.xda-developers.com/showthread.php?t=2204960
the solution lies here http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
u can get some idea on setting up adb from a very old thread of mine http://forum.xda-developers.com/showthread.php?t=1038338 read part installing custom recovery and how to make adb work
I was trying to convert my 5.0.1 GPE (already converted a couple months ago) back to Sense using the MaximusHD ROM and following the Youtube guide below.
All went well until I flashed firmware 1.54.401.5, found in this thread (http://forum.xda-developers.com/showthread.php?t=2733523). Now, the phone only reboots to the red exclamation mark every few minutes and the only thing I can do is Volume up + Power into the stock Android recovery. I'm not sure if it's possible to even power off since it only reboots to the red exclamation. ADB also does not detect the device in stock recovery, although the "device connected" tone plays through my PC speakers
Is there any solution to this? Any help would be appreciated.
Rango85 said:
I was trying to convert my 5.0.1 GPE (already converted a couple months ago) back to Sense using the MaximusHD ROM and following the Youtube guide below.
All went well until I flashed firmware 1.54.401.5, found in this thread (http://forum.xda-developers.com/showthread.php?t=2733523). Now, the phone only reboots to the red exclamation mark every few minutes and the only thing I can do is Volume up + Power into the stock Android recovery. I'm not sure if it's possible to even power off since it only reboots to the red exclamation. ADB also does not detect the device in stock recovery, although the "device connected" tone plays through my PC speakers
Is there any solution to this? Any help would be appreciated.
Click to expand...
Click to collapse
Red eclamation mark is stock recovery, volume up and power to access the menu, so its normal, complete the rest of returning to stock, just follow that guide, not the youtube video.
After firmware flash
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP recovery - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
Seanie280672 said:
Red eclamation mark is stock recovery, so its normal, complete the rest of returning to stock, just follow that guide, not the youtube video.
After firmware flash
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
Click to expand...
Click to collapse
How do I get into bootloader if the phone is constantly boot looping to a red exclamation?
Rango85 said:
How do I get into bootloader if the phone is constantly boot looping?
Click to expand...
Click to collapse
just hold volume down + volume up + power until the phone goes off, takes about 15 to 20 seconds to go off, then quickly release all 3 buttons and hold volume down only until in the phone boots to the bootloader.
Seanie280672 said:
just hold volume down + volume up + power until the phone goes off, takes about 15 to 20 seconds to go off, then quickly release all 3 buttons and hold volume down only until in the phone boots to the bootloader.
Click to expand...
Click to collapse
It worked! Now in bootloader, gonna flash recovery now and post an update.
Seanie280672 said:
just hold volume down + volume up + power until the phone goes off, takes about 15 to 20 seconds to go off, then quickly release all 3 buttons and hold volume down only until in the phone boots to the bootloader.
Click to expand...
Click to collapse
Ok, I flashed the latest TWRP file (twrp-2.8.6.0-m8.img) in Fastboot but when I try to boot into TWRP, it stalls on the "Entering Recovery" screen. Any ideas as to what is causing this?
Rango85 said:
Ok, I flashed the latest TWRP file (twrp-2.8.6.0-m8.img) in Fastboot but when I try to boot into TWRP, it stalls on the "Entering Recovery" screen. Any ideas as to what is causing this?
Click to expand...
Click to collapse
fastboot flash recovery recovery name.img
fastboot erase cache
fastboot reboot-bootloader
Now try enter recovery again.
Seanie280672 said:
fastboot flash recovery recovery name.img
fastboot erase cache
fastboot reboot-bootloader
Now try enter recovery again.
Click to expand...
Click to collapse
Same problem . I can, however, browse my internal storage and micro sd card on my PC in the stalled "Entering Recovery" screen. I can try to flash a stock recovery and then re-try flashing TWRP?
Or are there any alternative methods I can use to get a working OS installed?
Rango85 said:
Same problem . I can, however, browse my internal storage and micro sd card on my PC in the stalled "Entering Recovery" screen. Should I flash a stock recovery and re-try flashing TWRP?
Or are there any alternative methods I can use to get a working OS installed?
Click to expand...
Click to collapse
Did you factory reset in stock recovery ?
Seanie280672 said:
Did you factory reset in stock recovery ?
Click to expand...
Click to collapse
Yes, I'm afraid.
Rango85 said:
Yes, I'm afraid.
Click to expand...
Click to collapse
Strange, try another version of twrp, like the one recommended 2.7.?.?
Thanks man, v2.7.0.2 worked Doing a full factory reset now and will keep you updated.
Ok, update: After a lengthy 1st reboot after the install, I'm finally running the ROM . However, the WiFi doesn't seem to work as well as the camera.
Any solutions to this?
Rango85 said:
Thanks man, v2.7.0.2 worked Doing a full factory reset now and will keep you updated.
Ok, update: After a lengthy 1st reboot after the install, I'm finally running the ROM . However, the WiFi doesn't seem to work as well as the camera.
Any solutions to this?
Click to expand...
Click to collapse
First of all, looks like the newer twrp didn't work due to the old first edition firmware and I would say if you have flashed a lollipop rom, it's the same problem, the old 1xxxxx firmware, as your s-off, just update your firmware, I'd recommend flashing a 2xxxx package first, then a 3xxxxx then 4xxxxxx you will then have to flash the latest version of twrp as you'll have stock recovery back on your phone.
Firmware is here -
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
Seanie280672 said:
First of all, looks like the newer twrp didn't work due to the old first edition firmware and I would say if you have flashed a lollipop rom, it's the same problem, the old 1xxxxx firmware, as your s-off, just update your firmware, I'd recommend flashing a 2xxxx package first, then a 3xxxxx then 4xxxxxx you will then have to flash the latest version of twrp as you'll have stock recovery back on your phone.
Firmware is here -
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
Click to expand...
Click to collapse
I ended up installing a stock rooted Lollipop 5.1 ROM (http://forum.xda-developers.com/showthread.php?t=2706441) instead of MaximusHD. Camera is now functional and everything appears to run fine EXCEPT for the WiFi which simply won't turn on to scan available networks. Might update the firmware to 4xxxxxxx a bit later, but wouldn't that wipe the OS again?
Rango85 said:
I ended up installing a stock Lollipop 5.1 ROM (http://forum.xda-developers.com/showthread.php?t=2706441) instead of MaximusHD. Camera is now functional and everything appears to run fine EXCEPT for the WiFi which simply won't turn on to scan available networks. Might update the firmware to 4xxxxxxx a bit later, but wouldn't that wipe the OS again?
Click to expand...
Click to collapse
If you ran a stock ruu then your firmware should of gone to the latest, just noticed you ran a gpe ruu, I thought you were trying to get back to sense ?
Seanie280672 said:
If you ran a stock ruu then your firmware should of gone to the latest, just noticed you ran a gpe ruu, I thought you were trying to get back to sense ?
Click to expand...
Click to collapse
I converted to GPE RUU w/ OTA updates from stock Sense back in January of this year. Only yesterday I've decided to convert back to Sense using a ROM based on it (MaximusHD in this case) and ran into these problems. I then installed a 5.1 ROM instead (not 5.1 RUU) from graffix's thread last night when I installed the TWRP 2.7.
So correct me if I'm wrong, the method is (in bootloader):
fastboot oem rebootRUU
Click to expand...
Click to collapse
then
fastboot flash zip 4.16.401.10.zip
Click to expand...
Click to collapse
Correct?
Rango85 said:
I converted to GPE RUU w/ OTA updates from stock Sense back in January of this year. Only yesterday I've decided to convert back to Sense using a ROM based on it (MaximusHD in this case) and ran into these problems. I then installed a 5.1 ROM instead (not 5.1 RUU) from graffix's thread last night when I installed the TWRP 2.7.
So correct me if I'm wrong, the method is (in bootloader):
then
Correct?
Click to expand...
Click to collapse
Yes that's correct, but don't forget to run the flash command twice as the first time will fail, however, that is a sense firmware not a gpe firmware.
You were doing alright with your convert back to sense and just needed to flash the latest firmware to bring your phone up to speed.
Seanie280672 said:
Yes that's correct, but don't forget to run the flash command twice as the first time will fail, however, that is a sense firmware not a gpe firmware.
You were doing alright with your convert back to sense and just needed to flash the latest firmware to bring your phone up to speed.
Click to expand...
Click to collapse
I understand, but if I want to use a 5.1 GPE ROM (like http://forum.xda-developers.com/showthread.php?t=2706441); is it ok to use the 4.16.401.10 firmware or would I need another GPE specific firmware?
Rango85 said:
I understand, but if I want to use a 5.1 GPE ROM (like http://forum.xda-developers.com/showthread.php?t=2706441); is it ok to use the 4.16.401.10 firmware or would I need another GPE specific firmware?
Click to expand...
Click to collapse
I'd recommend the gpe firmware.
Seanie280672 said:
I'd recommend the gpe firmware.
Click to expand...
Click to collapse
Is there any link to the GPE firmware? There's so many files when I do a search that I don't know which specific one is needed.
EDIT 1: 4.16.401.10 seemed to work fine and I also managed to update to the latest TWRP recovery.
EDIT 2: The OS took quite some time to reboot after the first install but I'm inside 5.1 now and WiFi seems to work
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Wrong section
Hacker101 said:
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Click to expand...
Click to collapse
So you have tried booting into the bootloader and entered "fastboot boot twrp.img" in adb?
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Alcolawl said:
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Click to expand...
Click to collapse
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Hacker101 said:
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Click to expand...
Click to collapse
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
TheBobMiller said:
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
Click to expand...
Click to collapse
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Hacker101 said:
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Click to expand...
Click to collapse
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
TheBobMiller said:
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
Click to expand...
Click to collapse
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
Don't worry about the Thanks, cause I'm sure others have contributed more. Sorry I'm not more familiar with the Linux instructions!
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
TheBobMiller said:
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
Click to expand...
Click to collapse
Yes I was on May.. Do you have link to Verified Signer?
jkashuba07 said:
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Yes I was on May.. Do you have link to Verified Signer?
Click to expand...
Click to collapse
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
Thank you, and will do.. yes chainfire has done a lot of good work, definitely have appreciated him over the years
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Hacker101 said:
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Click to expand...
Click to collapse
Correct. Only the may bootloader requires the extra zip file to be flashed. I am still on April but I have heard people not having any problems and some having nothing but problems from May. I think I'm going to give it a try tomorrow and see how it goes.
Edit: Tried the May bootloader and couldn't get it to boot a custom rom or TWRP, so I went back to April after flashing the Android O Beta and playing with it for a couple of hours. I feel that the Beta is still too early for a daily driver, but it was nice to mess around with some of the features we will have once this OS is released.
Seeing lot of users struggling while going back to stock due to one or the other needed feature on custom ROM missing, few of them are dual SIM not working, MTP, camera or others. Even if they come back to stock by restoring the stock the ROM via TWRP, sound is not working for many of them. I flashed recent LOS, RR, AOSP and returned back to stock without any problem. I made the traditional backup (yeah not followed the instruction of TWRP backup given in ROM thread ) I will quickly brief on the method. There are 2 methods for the same.
Method 1:
Before flashing the custom ROM
Boot to TWRP
Click on backup
You will bunch of options/partition to backup.
Select only - boot, data, system and vendor and no other partition. (can change the name of TWRP to the Date-Time-BXYZ)
Let TWRP finish the backup (time taken will depend on your data size)
Now again click on backup and this time select only - cust, prod and version (can change the name to Date-Time-others or a per your wish)
Flash custom ROM and enjoy
IF you face any issues and want to return back to stock, refer below.
Return to stock-
Boot to TWRP
Click on Wipe
Wipe System, Boot, Data
Click on Restore
Select the backup media (internal memory/external memory/USB etc)
Chose the 1st back up only i.e boot, data, system and vendor (Date-Time-BXYZ)
Chaneg the file system to F2FS (it was channged to EXT4 while moving to Custom ROM, remember )
Boot to system.
It should have all sound and other stuff working without any issue.
Method 2:
Use dload method to restore to full stock.
Link here - https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
In worst case If you have anything non working, like FM, theme etc, flash the small data file via TWRP.
Link here- https://forum.xda-developers.com/honor-6x/how-to/guide-solution-to-themes-fm-app-manual-t3712002
Try to use the same build number's file for this.
Good luck.
I have been trying to relock the boot loader on my honor 6x BLN-L24C567B365 with no luck. It has de factory rom on it, it has twrp an root installed (magisk). I tried the dload method with the same software version it has (BLN-L24C567B365), but i get "software install failed", I want to remove twrp, root, and afther that relock the boot loader. If i try to relock in the actual state, it boots in to fastboot mode, to boot correctly again i have to unlock again de bootloader. Can you give me some advice please.
Thanks in advance.
vcetina said:
I have been trying to relock the boot loader on my honor 6x BLN-L24C567B365 with no luck. It has de factory rom on it, it has twrp an root installed (magisk). I tried the dload method with the same software version it has (BLN-L24C567B365), but i get "software install failed", I want to remove twrp, root, and afther that relock the boot loader. If i try to relock in the actual state, it boots in to fastboot mode, to boot correctly again i have to unlock again de bootloader. Can you give me some advice please.
Thanks in advance.
Click to expand...
Click to collapse
Try flashing b360
shashank1320 said:
Try flashing b360
Click to expand...
Click to collapse
It worked!!!, thank you
Hey, I am currently on lineage and want to go back to stock. I really cant do it. It always fails or the download link is wrong. Can you help me?
Overmind123 said:
Hey, I am currently on lineage and want to go back to stock. I really cant do it. It always fails or the download link is wrong. Can you help me?
Click to expand...
Click to collapse
Model, build number etc please.
Overmind123 said:
Hey, I am currently on lineage and want to go back to stock. I really cant do it. It always fails or the download link is wrong. Can you help me?
Click to expand...
Click to collapse
Check all the files I have given in PM and share the results.
I tried going back to nougat from stable gsi linage os by using huru updater flasing via recovery and it resulted in a bootloop.
I can only enter the three options section -1-press power button to continue. 2- Volume up key to enter erecovery... and 3- The device will continue to boot after 5secs...
I cannot get into the erecovery at all, not even flashing another erecovery since I thought it was corrupted but no. I try to press volume buttons simultaneously with the power button and it doesn't work either. It also doesn't seem to stop rebooting.
I TRIED DLOAD and I had NO result but the same unstopping reboots.
Also I can ONLY enter that three options section by plugging in the device via pc while pressing volume up at the same time while plugging it in the USB.
Flashed recoveries for both nougat and oreo and never worked. I'm worried. Help please
evjgl98 said:
I tried going back to nougat from stable gsi linage os by using huru updater flasing via recovery and it resulted in a bootloop.
I can only enter the three options section -1-press power button to continue. 2- Volume up key to enter erecovery... and 3- The device will continue to boot after 5secs...
I cannot get into the erecovery at all, not even flashing another erecovery since I thought it was corrupted but no. I try to press volume buttons simultaneously with the power button and it doesn't work either. It also doesn't seem to stop rebooting.
I TRIED DLOAD and I had NO result but the same unstopping reboots.
Also I can ONLY enter that three options section by plugging in the device via pc while pressing volume up at the same time while plugging it in the USB.
Flashed recoveries for both nougat and oreo and never worked. I'm worried. Help please
Click to expand...
Click to collapse
Was dload successful?
shashank1320 said:
Was dload successful?
Click to expand...
Click to collapse
It wasn't I used DC Phoenix as last resort and fasttbooted the frimware
shashank1320 said:
Was dload successful?
Click to expand...
Click to collapse
Volume down and plugging in sync cable to computer won't put you in fastboot? Phone should be powered down and then this combo should get you adb access....