I had disabled some system apps that were sucking a lot of battery and they didn't seem to be that important, to me :silly: , now it gets stuck at boot animation, no looping.(can't edit title)
The device is running 4.4.2 Kitkat and is a mtk device.
I thought about replacing the file that contains info about disabled apps, but I don't know which file is that.
Recovery is stock, garbage, throws installation aborted error on flashing.
Any way I can flash custom recovery image? (fastboot is not working, tried with adb too)
Can you suggest any other way to solve the problem without resetting user data or flashing stock rom?
Thanks,
moneydesigner said:
I had disabled some system apps that were sucking a lot of battery and they didn't seem to be that important, to me :silly: , now it gets stuck at boot animation, no looping.(can't edit title)
The device is running 4.4.2 Kitkat and is a mtk device.
I thought about replacing the file that contains info about disabled apps, but I don't know which file is that.
Recovery is stock, garbage, throws installation aborted error on flashing.
Any way I can flash custom recovery image? (fastboot is not working, tried with adb too)
Can you suggest any other way to solve the problem without resetting user data or flashing stock rom?
Thanks,
Click to expand...
Click to collapse
Try flashing stock firmware with SP-Flasher.
I just flashed the recovery with sp-flasher, made a cwm backup, flashed different partitions and figured out that the boot animation was creating the problem.
I had replaced boot animation before and it had only one part with a lot of frames, divided the boot animation into three parts and restored everything back and everything is working .
Thanks,
Glad to hear that!
Related
Hi,
Due to HTC's special touches, the recovery image doesnt stay flashed, and on normal boot its flashed over (meaning if i try to go to recovery after a normal boot, i get the red triangle stuff, and have to pull the battery). I was wondering if this would potentially cause troubles if i was trying to flash a custom ROM from recovery? in other notes, i do find sometimes i have to pull the battery 4 or 5 times to get it to normally boot (thats without holding the buttons >.>).
Thanks in advance.
HTC HERO recovery image flashing problems
I am having exactly the same problem!
I did a quite a bit of research on how to root, backup and flash my HERO and every guide I found describes the process using Universal AndRoot + Rom Manager and it seems there should be no problems. I already rooted my phone successfully, installed Rom Manager and flashed either ClockworkMod 2.5.0.1 or RA Recovery 1.7.0.1 which are able to boot but only once. The next time I reboot I get the red triangle warning and it loads into stock recovery (by pressing vol_up + powroff buttons), so the custom recovery lasts only one boot cycle. I was able to backup but I don't want to risk to wipe and flash since there is a chance it might stuck in the bootscreen loop afterwards and I won't be able to do anything.
There is a thing with s-off and SPrecovery which helps to resolve the problem but it doesn't look like there is anything for HERO.
Any help would be appreciated.
ps I tried to manually flash recovery from inside the phone and from windows command line with the same result.
forum.cyanogenmod.com/topic/8182-how-to-root-your-hero
posted some similar comments over there, and the only init script that i can find when in recovery.
Yeah I posted my question there too.
I was able to find some information about the issue (he is talking about Villain ROM but I think it doesn't really matter):
pulser_g2:
Repeat the process again, as I think stock ROMs try and overwrite the recovery each time they boot. When you finish the process, immediately nandroid and flash VR12. That will then flash a new recovery, AmonRA 1.6.2a, and you will be sorted
Click to expand...
Click to collapse
So it looks like we should just go ahead and flash a custom rom which, in theory, will eliminate the problem.
yeah was tempted to just flash, but sending duck my system img for him to dissect anyway.
yeah worked fine, running cm6.1 now
Yeah once you root you have to flash a custom rom before reboot or u loose the root
I learnt it after lots of reboots and re roots.
but now I wanted to know if I could save the original rom which i have as nand backup to make as an update.zip like custom rom for safe keepimg
I flashed CM6.1 -based TastyFroyo 1.2 and I can confirm custom recovery stays flashed now.
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
r.darwish said:
I just tried to flash a ROM and it ended up strangly. As a disclaimer: this is not a "MY PHONE IS BROKEN PLZ HELP ME!" post. I managed to get around this somehow, but I want to realize what technically happened in order to deepen my knowlage about the Android boot process. I come from a background of a Linux PC developer, but I didn't develop anything for Android yet.
So this is the boot process as I understand it, please correct me where I'm wrong:
When you turn on the device, the first thing that happens is that the CPU executes the Radio. The Radio allows the software to preform basic communication with the hardware, and is similar to the PC's BIOS. The Radio can be replaced, but if replaced with a problematic Radio, there's nothing you can do with home equipment to restore it (meaning a full brick).
Once loaded, the Radio executes the boot loader from the flash memory. The boot loader is like GRUB on a PC Linux system. It is the one that traps magic keys like "Volume up + Home" and decides, whether to boot the ROM, the recovery console or just "boot itself".
Both the ROM and the recovery software reside in differents partitions, and the bootloader chooses which partition to boot from.
In normal boot, the bootloader chooses to load the Linux kernel from the system partition and pass the execution to it. The Linux kernel loads Java, which loads the launcher, etc etc...
As I understand, a normal boot process doesn't involve the recovery software at all, and each ROM comes with its own custom-compiled Linux kernel.
The recovery software is like another operating system, which allows you replace the operating system in the system partition (AKA the ROM). Is the recovery software based on the Linux kernel too, or is it an independed software written in C/Assembly? If it is based on the Linux kernel, does it share a kernel with the ROM, or does it have its own version of the Linux kernel?
Now, this is what happened when I tried to flash Cyanogenmod 10 into a Galaxy S device running Cyanogenmod 7. I booted into recovery, backed up and wiped. To my understanding, backup means creating images of the system and data partition, storing these image files in the SD card and sign them with MD5.
When I tried to install the ROM, it warned me that my current partition layout won't fit to the new ROM, and I need to install again to confirm.
Now, when installing an OS in a PC, you can alter the partitions because the OS installation runs from a CD or a DOK, but if the recovery software runs from the disk too, how can it alter the partition table?
Anyways, once I confirmed, the phoned crashed and entered a boot loop. As I understood, flashing a ROM doesn't do anything to the recovery partition, so in any case I can always boot back to recovery and restore the backup. I was probably wrong, because when I tried to boot into recovery I found out that I have a different recovery software (The previous one had the Clockwork icon and a black background, and the new one had gray background and the Android Logo. I tried to restore the backup using the new recovery software but it failed, complaining that it can't format the system partition and that there's a problem with "MTD" (What's that?). I tried to reformat the system partition from the recovery software, but doing so caused it just to return to the main recovery screen without preforming anything or complaining about errors. Same thing when I tried to preform factory reset.
After some failed attemps, what I tried is to flash the old CM7 ROM, not from a backup, but from a clean zip. The recovery console claimed that it succeeded, but it did it too fast to be true, and there were almost no prompts beside the one that says that it succeeded.
I tried to restart, and got into a boot-loop again. This time, however, in each boot I could see my prevoius Clockwork recovery software for a second before the phone restarted again. I booted again into recovery mode to find my previous old recovery software. I tried to restore the backup and it succeeded. Now, I don't really understand what happened:
1. How come flashing ROMs changed the recovery software? I though that I zip containing a ROM contains only a ROM (A Linux kernel, Java JVM etc etc...), not a recovery software.
2. After I tried to flash CM7 back I could see the recovery screen in the boot-loop. Why did I see that screen if I didn't choose explicitly to boot into recovery?
3. How can the recovery software change the partition layout of the memory that it resides on by itself?
4. How come that the previous recovery software managed to restore that backup? As I understood, I ruined the partition layout, so what magic did the old recovery software that the new one couldn't do?
Thanks for the help
Click to expand...
Click to collapse
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
nerot said:
1.A recovery could have been packaged in the zip (i use zips to install recoveries too).
2.Im not sure about this but it could be that your bootloader got messed up and didn know what to load.
3.I think this is possible since recovery loads itself into ram and works from there allowing the partition to be changed.
4. I don't know about this one
Also the recovery has it's own kernel it doesn't share it with the rom one(ex. if touch doesnt work in a rom due to its kernel it can work in recovery)
Sent from my LG-P350 using xda premium
Click to expand...
Click to collapse
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
r.darwish said:
Thank you for the answer
Maybe someone can confirm if Cyanogenmod is shipped with a recovery software?
Click to expand...
Click to collapse
Official builds do not contain the recovery.
Sent from my LG-P350 using xda premium
oneovo establish
I used official builds for both 10 and 7.
Hey guys!
Since I tried building Firefox OS -Boot2Gecko- on my Samsung Galaxy S2 (i9100) (FYI: I followed this walkthrough) , I'm having quite a hard time making my phone boot on any ROM I try to install. I still have an access to CWM Recovery and to the Download mode
* After failing to flash B2G's Gaia on my phone, I tried to flash the kernel back to the original one and to restore the CM 10.1 NIGHTLY backup I made before doing all this mess. No changes: stuck at CM's boot screen.
* Tried to get back to a stock firmware and ROM, stucks at boot screen ("Samsung Galaxy S II GT-I9100" screen), even after a wipe data/factory reset, wipe cache and wipe dalvik cache.
(In fact, I achieved to boot on a stock ROM once, but after some other manipulations to get my CM 10.1 back, I now can't get it to boot on any of them anymore.)
* I tried to follow the rooting + CyanogenMod walkthrough on CM's wiki, but the same happens: stucks on boot screen. However, after a wipe data, I reach CM's boot animation, which runs indefinitely.
* Right now I tried flashing with Siyah's Kernel, since the flash counter is not any of my concerns anymore. Whatever I try, I can't get anything to get past the "Booting the primary ROM" message.
However, I installed a stable CM9 on the secondary ROM and... it actually works. But even when cloning 2nd ROM to the 1st ROM, can't get the first to boot anyway.
I am not an expert in Android OS architecture, but could it be related to some kind of modifications made by B2G's build & flashing? Maybe some files in the /data or /system partitions have been altered and are not replaced when fllashing, leading to ROMs not loading up?
Any advice on this is welcome.
PS: English is not my main language, sorry if things aren't explained clearly. Tell me if you need any clarifications about it!
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
Sakujou_Kei said:
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Click to expand...
Click to collapse
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
TheATHEiST said:
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=1363738 (Kernel) and this one http://forum.xda-developers.com/showthread.php?t=2100558&highlight=script (ROM) ?
Ok so I tried the cleaning scripts I linked on my previous message, no changes. I can still boot on Siyah's second ROM, but can't get past the "Booting primary ROM" message.
Ideas anyone?
Plugged in my old Captivate the other day to charge, and when I came back to it, was stuck in CWM. And would not boot into OS. I have some pics and videos I would like to pull off of it. I tried flashing to stock with Odin, but no love. Tried various kernels and CWM's and non of them will mount /sdcard. As far as I know it hasn't been wiped, as everything I've done says it can't mount /sdcard. Thought it was on CM11 but the boot logo looked like CM10.
Have been trying this http://howtorecover.me/data-recovery-internal-storage-android-phone-guide, but I am stuck at the "Making an image of Android internal storage". And not even sure this will work because I have to do everything in Recovery.
Can log into ADB and do some stuff while in Semaphore_KK_3.4.2c with "adb device= 3935DD422FE700EC recovery"
managed to get "list_of_partitions.txt" (attached)
Is there anyway to repair mount without wiping or retrieve my files?
Boot Into Recovery
BigB42078 said:
Plugged in my old Captivate the other day to charge, and when I came back to it, was stuck in CWM. And would not boot into OS. I have some pics and videos I would like to pull off of it. I tried flashing to stock with Odin, but no love. Tried various kernels and CWM's and non of them will mount /sdcard. As far as I know it hasn't been wiped, as everything I've done says it can't mount /sdcard. Thought it was on CM11 but the boot logo looks like CM10.
Have been trying this http://howtorecover.me/data-recovery-internal-storage-android-phone-guide, but I am stuck at the "Making an image of Android internal storage". And not even sure this will work because I have to do everything in Recovery.
Can log into ADB and do some stuff while in Semaphore_KK_3.4.2c with "adb device= 3935DD422FE700EC recovery"
managed to get "list_of_partitions.txt" (attached)
Is there anyway to repair mount without wiping or retrieve my files?
Click to expand...
Click to collapse
Hi there,
Well if you're able to boot into the custom recovery then you can use the adb feature to make up a backup of all the files
KIBS2173 said:
Hi there,
Well if you're able to boot into the custom recovery then you can use the adb feature to make up a backup of all the files
Click to expand...
Click to collapse
Great, so can you direct to a way to do it? Stuck on the above guide. Was stuck on SU privileges but aftter finding my current recovery and flashing su.zip every rime I boot the phone. Seem to be passed that. When I get to abd try to copy image it doesn't work.
Also I have read in some the posts that restore in recovery doresn't wipe personal files. Is that true?
BigB42078 said:
Great, so can you direct to a way to do it? Stuck on the above guide. Was stuck on SU privileges but aftter finding my current recovery and flashing su.zip every rime I boot the phone. Seem to be passed that. When I get to abd try to copy image it doesn't work.
Also I have read in some the posts that restore in recovery doresn't wipe personal files. Is that true?
Click to expand...
Click to collapse
Yeah there is a way before I say it What phone are you using again?
well in some cases and on some phones when you change the recovery to a custom one all data will be destroyed
so can you actually boot the phone and does it goes into the homescreen?
KIBS2173 said:
Yeah there is a way before I say it What phone are you using again?
well in some cases and on some phones when you change the recovery to a custom one all data will be destroyed
so can you actually boot the phone and does it goes into the homescreen?
Click to expand...
Click to collapse
It's a Samsung Captivate sgh-i897, will not boot into OS. Everything I've tried flashing was with Odin. tried a couple one-click stock odin installers. But even those would get blocked by mount error when the phone would reboot to install the OS.
Try this
BigB42078 said:
It's a Samsung Captivate sgh-i897, will not boot into OS. Everything I've tried flashing was with Odin. tried a couple one-click stock odin installers. But even those would get blocked by mount error when the phone would reboot to install the OS.
Click to expand...
Click to collapse
Hi there,
Okay so have you tried using Samsung Keis software it should help you to restore that phone however I'm not sure that you could the recover your old files on that phone but you can try various phone recovering software
Kies won't let me connect through recovery or download. Tried doin factory reset in recovery and that doesn't work either.
Hello,
I am pretty sure that the old Android phone cannot give your data back if you have saved any files after losing old data. New data might have overwritten the previous deleted files and you cannot retrieve them again. But if you have not saved any files after deleting then I must say, you can restore the files using a recovery program (androiddata-recovery.com/android-phone-recovery.php).
Going through this will allow you to get back every data deleted from your old Android phone without any backup. It is easy to use and one of the best reliable software to recover lost files from Android phone.
Hi there,
Not sure what happened - I'm using my Tab S3 (SM-T820) for ages in the same (stable) configuration - rooted Stock, no changes/installations for months.
This morning it was in Odin/Download mode and I cannot boot into system.
I can get into recovery (TWRP), but I cannot boot into system from there either, it always returns to Odin (tried wiping Cache/Dalvik, didn't help).
For now my only idea is to let it completely discharge, charge again and give it another try.
No buttons appear to be stuck.
Any ideas or suggestions, eg sth I could check in TWRP to see what's going on?
(hopefully nothing wrong with the system partition).
Note - I'm only familiar with the typical TWRP functions needed to install custom firmware, haven't used it for much else. Obviously would prefer not to destroy my (stable) setup and spent a full day re-installing everything
Thanks a lot for your help everyone!
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
bmwdroid said:
@Whoooo? Backup whatever possible with TWRP onto external storage (SD or OTG).
Check if file manager can access download/DCIM folders and save them as well.
Although the charging thing might help I wouldn't set my hopes to high.
Probably somethings wrong with system or boot partitions or any file needed by them.
I'm afraid you will have to reflash stock via Odin, root again and try if restoring TWRP saved Data works.
That would reduce setting up time.
Click to expand...
Click to collapse
Hi there,
Thanks a lot for your reply - yes, I will try that once the complete discharge is finished.
Reflashing stock - could cause this any troubles as it's already unlocked/rooted?
Or is there a chance dirty flashing the Tweaked Stock ROM could work, too?
Tablet was still on the original Stock it came with, but rooted with magisk and manually debloated...
Thanks again!
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
bmwdroid said:
I think Odin won't care about unlocked bootloader.
But might be necessary to unlock again.
Dirty flashing afaik only works with TWRP so only flashing of zip or img files possible.
Except you sideload although Idk if that's possible on Samsungs.
Dirty flashing of a before the problem arose made backup might work.
Did you debloat while already installed or externally?
What file format does it have?
My T825 uses the debloated ROM by rorymc628 which can be flashed with TWRP as it's a zip file.
Click to expand...
Click to collapse
Hi there and thanks again -
Took me a while to try everything but finally it's working again.
Complete battery drain didn't help, but dirty flashing did - once I got the correct version.
Basically made a nandroid backup, then flashed the tweaked rom over my existing one, starting with newer versions down to older ones.
So, flash, reboot - didn't work, restore nandroid (all), flash slightly older rom....
Till it started booting with v2.0 (probably matching my existing rom close enough).
Had to reflash Magisk as the 2.0 Rom included didn't match my Magisk Manager, but now my Tab S3 is working again!