So, a while ago I started to root my atrix HD and like everybody else I started to try new roms and stuff, I always backed up my stock rom, but one day I accidentally deleted a file from a folder that clockworkMod recovery created, and then when I wanted to return to my stock rom, well it didn't let me do it!
I've tried to go back to stock with RSDlite and myth tools but I simply can't do it (maybe the virtual world hates me)
So I was wondering if any of you could send a me a backed up stock at&t unlocked rom that I could flash with clockwork recovery?
Or can I go back to stock with any other method?:crying:
Axelgux said:
So, a while ago I started to root my atrix HD and like everybody else I started to try new roms and stuff, I always backed up my stock rom, but one day I accidentally deleted a file from a folder that clockworkMod recovery created, and then when I wanted to return to my stock rom, well it didn't let me do it!
I've tried to go back to stock with RSDlite and myth tools but I simply can't do it (maybe the virtual world hates me)
So I was wondering if any of you could send a me a backed up stock at&t unlocked rom that I could flash with clockwork recovery?
Or can I go back to stock with any other method?:crying:
Click to expand...
Click to collapse
Did you unlock bootloader?
How did Myth Tools show you when it cannot help you?
Axelgux said:
So, a while ago I started to root my atrix HD and like everybody else I started to try new roms and stuff, I always backed up my stock rom, but one day I accidentally deleted a file from a folder that clockworkMod recovery created, and then when I wanted to return to my stock rom, well it didn't let me do it!
I've tried to go back to stock with RSDlite and myth tools but I simply can't do it (maybe the virtual world hates me)
So I was wondering if any of you could send a me a backed up stock at&t unlocked rom that I could flash with clockwork recovery?
Or can I go back to stock with any other method?:crying:
Click to expand...
Click to collapse
Uninstall anything Motorola driver related and once that's done let Myth install the drivers for you. With Windows & Myth, drivers are usually the problem when stocks won't flash. Running RSD as admin as well as disabling UAC can help.
What error does CWM give you? Depending on what it gives and what you deleted, this might be a simple fix.
devilsking said:
Did you unlock bootloader?
How did Myth Tools show you when it cannot help you?
Click to expand...
Click to collapse
Yes I unlocked bootloader right away with root, It just doesn't progress or anything
skeevydude said:
Uninstall anything Motorola driver related and once that's done let Myth install the drivers for you. With Windows & Myth, drivers are usually the problem when stocks won't flash. Running RSD as admin as well as disabling UAC can help.
What error does CWM give you? Depending on what it gives and what you deleted, this might be a simple fix.
Click to expand...
Click to collapse
I'll try that, thanks.
CWM just say can't flash *name of m backup*
If i remember well I deleted something like this /clockworkmod/.recovery_version
or something related to the backup
skeevydude said:
Uninstall anything Motorola driver related and once that's done let Myth install the drivers for you. With Windows & Myth, drivers are usually the problem when stocks won't flash. Running RSD as admin as well as disabling UAC can help.
What error does CWM give you? Depending on what it gives and what you deleted, this might be a simple fix.
Click to expand...
Click to collapse
UPDATE
I managed to flash stock jellybean with the updated myth tool but now I'm stuck in motorola logo
why is that?
Axelgux said:
UPDATE
I managed to flash stock jellybean with the updated myth tool but now I'm stuck in motorola logo
why is that?
Click to expand...
Click to collapse
You probably need to factory reset. If you let Myth install Philz CWM, just boot into there and do that. If not, install Philz then continue on. If your bootloader is locked and you can't install Philz, all you can do is a factory reset from stock recovery. If you're unlocked, do what's in the next paragraph else go to the end.
If you were on a custom rom before this (any rom that's Android 4.2 and above) you need to format the internal sd, change the mount point to /data/media, reboot back into recovery, format the internal sd again. Doing a full format of /data after doing all of that probably won't hurt.
There's also the following commands you can also run in fastboot mode. Myth doesn't do the erase tombstones command, but it does the rest.
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Myth also doesn't do the fastboot erase modemst1 or modemst2, but that only matters when changing stock Android versions or going from ICS to JB to a custom rom...
skeevydude said:
You probably need to factory reset. If you let Myth install Philz CWM, just boot into there and do that. If not, install Philz then continue on. If your bootloader is locked and you can't install Philz, all you can do is a factory reset from stock recovery. If you're unlocked, do what's in the next paragraph else go to the end.
If you were on a custom rom before this (any rom that's Android 4.2 and above) you need to format the internal sd, change the mount point to /data/media, reboot back into recovery, format the internal sd again. Doing a full format of /data after doing all of that probably won't hurt.
There's also the following commands you can also run in fastboot mode. Myth doesn't do the erase tombstones command, but it does the rest.
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Myth also doesn't do the fastboot erase modemst1 or modemst2, but that only matters when changing stock Android versions or going from ICS to JB to a custom rom...
Click to expand...
Click to collapse
Mygoooooood I really appreciate your help, I did all that and still the same, yes i was in carbon rom kitkat 4.4, and I did all that but still the same :/
skeevydude said:
You probably need to factory reset. If you let Myth install Philz CWM, just boot into there and do that. If not, install Philz then continue on. If your bootloader is locked and you can't install Philz, all you can do is a factory reset from stock recovery. If you're unlocked, do what's in the next paragraph else go to the end.
If you were on a custom rom before this (any rom that's Android 4.2 and above) you need to format the internal sd, change the mount point to /data/media, reboot back into recovery, format the internal sd again. Doing a full format of /data after doing all of that probably won't hurt.
There's also the following commands you can also run in fastboot mode. Myth doesn't do the erase tombstones command, but it does the rest.
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
Myth also doesn't do the fastboot erase modemst1 or modemst2, but that only matters when changing stock Android versions or going from ICS to JB to a custom rom...
Click to expand...
Click to collapse
sorry to bother again but I think I totally hard bricked my AHD, now in the recovery it says can't mount E:/ and I can't flash any rom :/ thanks for all your help I really appreciate it
Axelgux said:
sorry to bother again but I think I totally hard bricked my AHD, now in the recovery it says can't mount E:/ and I can't flash any rom :/ thanks for all your help I really appreciate it
Click to expand...
Click to collapse
Flash a stock fastboot, RSD, manually, Myth, whatever works (manually should always work unless you really are bricked), flash the lastest msm8960 Philz cwm (look in the razr hd dev forums), after all that, possibly take a look at post 7...I'm gusssing your a Windows user...but for me, Linux has had better results than Windows flashing stock Motorola phones.
Related
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
Awesome if you do manage to find it please post it
crunchyHTC said:
I'm not too experienced in flashing roms so please have some patience with me.
I recently installed the ota update from htc and then unlocked the bootloader through the official htcdev site. I then flashed clockworkmod recovery through fastboot and flashed cm7 through CWM. I'm still running cm7 at the moment.
However, I am now not able to restore my phone back to the stock rom. I tried to restore the stock rom through a backup I did on nandroid in CWM. It went through all the steps and told me that the backup has been successfully restored. But after choosing the reboot phone option, the screen shows the white HTC screen, followed by a black screen for a couple of seconds, then the white HTC screen again, and then it finally brings me to CWM.
I'm not sure what I can do to restore my phone to stock rom. I went back to cm7 and tried to restore using ROM manager but it didn't work out too.
Help please!
Hboot 2.00
Radio 3822.10.08.28_M
(I'm not sure what other info might be needed so just let me know and i'll post it on here)
Click to expand...
Click to collapse
fallenwout said:
I have the same issue, I have a feeling about the cause but it is just a brainstrom. I could be wrong.
It might have something to do with ext4 vs ext3 file system. Custom roms usually format your phone in ext4 format while the stock rom only supports ext3
I would try and search a a format script that formats in ext3. (zip file format so you can flash it through clockwork or something)
Click to expand...
Click to collapse
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
crunchyHTC said:
Okay that method worked a charm. Just flashed back the stock rom.
Thanks for much for that!
Click to expand...
Click to collapse
Weird, didnt work for me. Dit you manually flashed the boot.img extracted from the nandroid backup?
Yup. So i took the backup from my sd card and put the backup onto my computer. Then I used clockworkmod recovery to restore the backup, and then used fastboot on the computer to manually flash boot.img through usb.
Hope that helps
Cannot restore with the procedure.
I have been trying to restore stock rom but I'm unable to do it.
I flashed boot.img using command prompt.
Restored it via Clockworkmod recovery but after restoring when i reboot the phone, it again takes me to recovery mode.
What should I do?
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
NicOsol said:
Maybe it is because you have changed the backup name.. I heard that if you change the stock from backup name you will wreck the md5sum ...
___________________________
Device: HTC Incredible S
Bootloader: S-OFF - ENG
Rom: ARHD 2.2.0
Android for life!
Click to expand...
Click to collapse
No..I have not changed anything.
I even tried formatting it in ext3 using Touch recovery and then tried to back up..but it didn't work.
It just keeps on taking me to recovery mode when I reboot.
Why don't you guys get s-off? I'll post a link when I'm on my PC on how to do it. That way, you won't have to flash the boot.img each Time you install a new rom...
Sent from my HTC Incredible S using XDA
tpbklake said:
With the unlocked bootloader, when the device is in recovery mode, it cannot overwrite the boot.img partition. So when you flash a custom ROM in CWM, you must manually extract the boot.img file from the zip file and flash it manually in Fastboot mode using the command:
fastboot flash boot boot.img
In the case when you are attempting to restore a previous backup, the same is true, except in this case you would manually flash the boot.img from the CWM backup folder in Fastboot mode.
This should solve both of the situations you have encountered.
Click to expand...
Click to collapse
Hello, I tried with "fastboot flash boot boot.img" took the boot.img from the backup and then I did a restore but it always goes into recovery mode, what else can I do?
so i was reading the instructions for the ARHD 10.1 rom and there was one part that was bugging me, the part that said you need the firmware package but it also says(recommended but not needed for now), but i went ahead and flashed it. it also said "There is no need to flash latest hboot!". so to be safe i backup everything. now after i flashed the rom everything was running smoothly but then i decided to go back into recovery. when i reboot into recovery, the screen said entering recovery then it went it cwm touch and then it existed then boot back to the htc start-up screen. this happens every time i flash something. but this time its different. i usually flah the twrp recovery then flash back the cwm recovery and it is fixed but it seems that since my phone is running 4.2.2 its not working..please help. i was thinking of using fastboot to flash the recovery 2.17.401.1..... please help
fastboot erase cache
skinsfanbdh said:
fastboot erase cache
Click to expand...
Click to collapse
i will do it now, lets hope it works
so.... did it work?
skinsfanbdh said:
fastboot erase cache
Click to expand...
Click to collapse
Thanks! This really helped me as it would flash the TWRP splash screen and then trip up.
Cheers!
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Two problems: First, I cannot use ADB, as it does not detect his phone. When I plug in his phone, it says drivers failed to install for HTC MTP device. I also have an HTC One, unlocked, S-Off, etc., and when I plug mine in, it's detected and ADB works just fine like always (so it's not that I need to reinstall drivers).
Problem 2: the phone seems to hang trying to do a factory reset from the bootloader menu, or from the stock recovery menu. It will start the reset, reboot to the white HTC screen then hang. I left it for more than an hour twice. Nothing doing.
Is there a way to reflash/restore his phone without wiping his sdcard? He's OK losing the data partition, but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard, as will unlocking his bootloader to try to install a custom recovery. Just not really sure what tools I have at my disposal with a stock recovery and no adb. Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Shott3r said:
This is for my friend's ATT One. Bone stock, unrooted, S-On, no changes made to the device from the store. He took the OTA for Kit Kat and was running fine, then his phone rebooted on him a couple days later and won't go past the white HTC boot screen.
Click to expand...
Click to collapse
Did you tried wiping /cache?
Shott3r said:
Two problems: First, I cannot use ADB, as it does not detect his phone.
Click to expand...
Click to collapse
ADB can only be used when phone is booted+usb debug on or via custom recovery
Shott3r said:
He's OK losing the data partition
Click to expand...
Click to collapse
I hope so, factory reset is a /data wipe... probably already wiped from your first attempt to factory reset
Shott3r said:
but wiping sdcard is last resort. Using an RUU .exe will wipe his sdcard
Click to expand...
Click to collapse
And the available ruu.exe for at&t is a downgrade in version so it will require s-off.
Shott3r said:
Will fastboot flashing a rom.zip extracted from the ATT RUU also wipe his sdcard? Or does that only happen with the RUU .exe? Any ideas appreciated..
Click to expand...
Click to collapse
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
easy way:
flash twrp custom recovery
flash guru reset rom for your version
or
flash twrp custom recovery
flash and use arhd rom
or the long way:
flash twrp
flash arhd
s-off
flash ruu.zip
alray said:
Did you tried wiping /cache?
...
you can't flash a rom directly from fastboot. You can flash a rom via a custom recovery or flash a ruu.zip from RUUmode (fastboot oem rebootRUU).
Unfortunately I think there is no way to save /sdcard. You will need to unlock bootloader to flash a custom recovery.
...
Click to expand...
Click to collapse
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Shott3r said:
I did erase cache first thing. Regarding flashing the ruu.zip from RUUmode, my question is whether flashing the ruu.zip will erase the sdcard? Also does it even matter, since he has KK firmware, and is S-On? Will the ruu.zip from Jellybean 4.3 even flash on his (current) KK firmware?
Any ideas on why the factory reset would hang? Cuz that's best case scenario is to simply factory reset, but it seems not to work presently.
Click to expand...
Click to collapse
ruu will wipe everything.
and no you can't use ruu with s-on because its a downgrade in version.
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Shott3r said:
Is there any way that you know of to get access to the sdcard in the circumstance I've described to try to rescue some files before I set about with the rescue? Doubt it, but just asking.
Click to expand...
Click to collapse
maybe you could use remote recovery booting (booting a custom recovery without installing it). Not sure if it still can be done (think it was disabled in 4.2.2)
fastboot boot name_of_recovery.img
then use adb from recovery to copy sdcard content to your computer
adb pull /sdcard C:\somefolder
If you can't boot from a remote recovery, then I think you can say goodbye to those files in your /sdcard
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
mobone32 said:
Yes, another one of these threads, but I need some help.
I got the bootloader unlocked, flashed twrp into recovery using fastboot. Unfortunantly the device rebooted into stock which I'm reading got rid of twrp. One problem is I can't figure out how to get twrp on there, and to stay on there, so I can use it.
Ignoring this issue I just continued. The guide simply said flash cm11. I searched around for a little bit on how to do this with fastboot (since my twrp wasnt working), but ended up doing the stupid thing of running:
fastboot flash system cm-11-20141115-SNAPSHOT-M12-ghost.zip
I know my problem is that I flashed the system with just a zip update file. I should've performed an update.
But now I can't figure out how to find the stock system image for my phone, the actual img file, so I can flash the system again. I have a sprint moto x.
Thanks for any help!
Click to expand...
Click to collapse
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
mobone32 said:
Update. I got it up and running again on stock. But am still confused about the flashing twrp so it sticks and the flashing cm11. Thanks again
Click to expand...
Click to collapse
you should be able to install TWRP by using the command, "mfastboot recovery twrp.img"
regarding CM11, I don't think is needed anymore to go from CM10 to CM12. it was at one time, but I believe CM or TWRP made some updates so that step is no longer necessary.
but before we can help you further, let us know what ROM you are on now and what ROM you want to be on next.
also, this thread is very helpful: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
Ok I got TWRP on there. Now I would like to get to lolipop 5.1 one way or another. I've always liked CyanogenMod (of course) but want to try CyanHacker. http://forum.xda-developers.com/moto-x/development/rom-cyanhacker-lollipop-ghost-t3033367
Right now I'm on a stock sprint rom I got with kitkat 4.4.4
Here's what I was going to do: (copied from forum)
1. mfastboot flash the latest TWRP if you aren't already at that point. I won't help you on fastboot things as you should already know- look around in the forums for info.
2. BACKUP YOUR STUFF- don't want to lose things without being able to get them back, right?
3. Flash the downloaded CM11 snapshot.
(Heres where I'm stuck. This is where I soft bricked it last night. I tried just now to apply the update using twrp and it just fails. It also fails at rooting my phone.)
4. Let CM11 fully boot and go through the setup screen- just skip everything and get to the homescreen.
5. Reboot into Recovery and wipe EVERYTHING- system, data, dalvik cache, cache, etc.
6. Flash your Lollipop ROM.
7. Flash PA-gapps.
8. Flash SuperSU.
9. Wipe cache/dalvik cache.
10. Reboot.
11. ???
12. Profit.
Thanks for any help!
Hello everyone,
so here is my configuration:
-latest TWRP (3.0.2) with F2S support
-bootloader unlocked
-the N6 is rooted
-ROM: AICP MM
2 days ago I tried to reboot to recovery to flash a more recent version of my AICP ROM. I just had the time to see the TWRP boot logo and then the phone rebooted to load the system. I can't access anymore to my recovery. I tried to rename the twrp directory on the internal SD but it does not change anything.
I reflashed TWRP with ADB and fastboot, but it didn't resolve the problem.
The only change I made recently was to flash a new radio to try to improve my connectivity.
I flashed 5.34 with the new bootloader in fastboot. Then I tried 5.32 without changing the bootloader and finally the 5.36 with the latest bootloader. So I don't know when the problem occured but now my phone even reboots randomly !
So if anyone has a solution you're welcome !
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Had this Problem on an other device . No recovery flash with fastboot . Dont no how , but Trwp manager APP from playstore did it .
you have to flash twrp right.. if you use a toolkit or flash the recovery with fastboot boot(instead of fastboot flash) then it will only boot into twrp 1 time, then you will need to flash it again if you want to use it again.
Strephon Alkhalikoi said:
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Click to expand...
Click to collapse
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
marcp39 said:
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
Click to expand...
Click to collapse
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
simms22 said:
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
Click to expand...
Click to collapse
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
marcp39 said:
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
Click to expand...
Click to collapse
sounds like you need to clear the recovery partition, then flash twrp again.
simms22 said:
sounds like you need to clear the recovery partition, then flash twrp again.
Click to expand...
Click to collapse
With "fastboot erase recovery" ?
marcp39 said:
With "fastboot erase recovery" ?
Click to expand...
Click to collapse
honestly, i dont remember how.
So here are my last attempts:
-I've tried to clean the cache with "fastboot erase cache", I thought it could be corrupted. BIG MISTAKE ! This time the phone is bootlooping when lauching the ROM...
And of course, I'm making some backups but they are on the "internal sd"... So I can't access my files anymore !
-I've also tried "fastboot erase recovery" and reflashed recovery. No improvement.
-I've downgraded the bootloader from 71.21 to 71.18. Nothing changed.
-I was asking myself if last time I didn't enter a wrong command in typing "fastboot flash boot bootloader.img" instead of "fastboot flash bootloader bootloader.img". So even if I've added benzocore on my AICP ROM, I decided to flash the boot.img from AICP zipfile on the boot partition (+ erase boot). So this time no more bootlooping of the ROM, because I'm stuck on the google logo :crying:...
I've never encounter such a desperate situation ! I don't even understand why I can't boot in recovery...
I could reflash a factory image on my phone, but this would erase all my datas !
Do you think I could reflash a factory image (except the data partition), just to be able to get a valid recovery, and access my files from the computer ? Then I could erase data partition, and reflash a new ROM ?
I don't want to precipitate the next actions because I don't have any joker... and with this stupid idea of not putting any µSD slot in most phones nowadays we're captive of the situation when the phone is bricked ! We can't recover data easily, even with adb pull (which does not work in my case of course).
So please share your ideas, they'll be welcome ! I've read A LOT of posts on XDA and others, but no solution until now....
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
marcp39 said:
I could reflash a factory image on my phone, but this would erase all my datas !
Click to expand...
Click to collapse
Don't use FlashAll, it's usually broken, anyway. But rather unpack the zip, flash boot and system. And either flash cache or erase it. It does the same.
HueyT said:
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
Click to expand...
Click to collapse
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
marcp39 said:
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
Click to expand...
Click to collapse
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
Click to expand...
Click to collapse
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
Click to expand...
Click to collapse
Yeah unfortunately we can do it with adb (like this http://stackoverflow.com/questions/8650407/how-to-copy-selected-files-from-android-with-adb-pull) but not with fastboot. Tomorrow I'll try to flash each *.img from MOB30M separately and see if I can recover a working recovery to access to my datas ! Thanks for your answer btw.
Hello everyone !
So here are the last news...
I've tried an older TWRP like 2.8.x.x same problem.
I've flashed all the *.img from MOB30M except data, but my recovery was still not accessible !!!
So I was resigned to format my data and flash the *.img on it.
This time it worked, my N6 was coming back to life !!! Then I had to root it, flash the recovery, remove encryption and format data with F2FS !
I still don't understand how a corrupted (?) data partition could block the running of recovery, that's strange !
So now I have to restore the data from a TWRP image dated 04-16 I had on my NAS...I can tell you that in the future I won't let my recent backups only on internal storage !
Will you believe me if I tell you that the same problem is occuring again :crying: ?
Several days ago, it started when the impossibility to enter the recovery but this time it does not reboot in bootloader, just stuck... Now I got random reboots and stange behaviour from applications !
I NEVER had a serious problem like that with my N6 before. So I don't understand how can I get data corruption like this ? Last time I was using Benzo kernel, now DeYuS kernel but with no exceptional settings, no overclocking.
I've just disabled "forceencrypt" and convert data to F2FS (no problem before).
So does anyone have a clue about this problem ?