I have a GT-I9000, rooted using CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1.tar, running a beta of Cyanogenmod 9. It worked flawlessly for a long time. I do not know the exact Cyanogenmod version currently, but I could find out in a few days if necessary.
Two days ago, the phone got stuck in a boot loop after its battery died and I subsequently connected the wall charger.
Since I can get into download mode but not into CWM Recovery, I decided to flash a kernel with included recovery. I tried flashing CF-Root and the Devil kernel using "heimdall flash --kernel zImage" (without repartitioning) from Linux. All kernel flashes had the same outcome: download mode still possible, recovery mode still not possible, and, since the first flash, a hang on the Samsung logo instead of the boot loop. Also, all the time since the boot loop, the phone is not detected by adb anymore.
I could try to go back to stock - from what I have read that would probably work - but I would also lose all data on the device since the last backup (is that true?).
Since I am only interested in getting recovery working again so that I can use adb to transfer data off the phone, here's my question:
What part of the stock image is needed to restore recovery mode? Will it be enough to flash the primary bootloader using heimdall?
polartec said:
What part of the stock image is needed to restore recovery mode? Will it be enough to flash the primary bootloader using heimdall?
Click to expand...
Click to collapse
I would also be grateful for any information about what happens on the i9000 until recovery mode is reached, and in particular which files / parts of the flash are involved in this process.
I would guess that recovery modes are executed by the kernel, in place of the distribution's init, and are stored either somewhere in the root filesystem or in an initramfs.
Related
Hello all,
[DEV][RC2]ICSSGS Source [Android 4.0.3]
I have tried to flash my phone with the ICS....I made a mistake at the starting...instead of wiping out the data I have tried to flash it directly and i got blank screen showed up.....
Then, I have downloaded oneclikc ODIN and flashed it with speedmode kernel.....and able to start recovery mode...but I am not able to flash ICS from my SD(external card) and I have tried to reboot the phone and it got stuck on reboot screen......
But I am able to got to recovery mode using KEY combination and download mode using key combination and USB cable.......
I really need a way to fix this.....
Please tell me how to at least get access to external SD card from recovery screen....
Thank you......
Flash a kernel with CWM 5.x. It has the option to install zips from the external SD. Most roms now require CWM 3.x or newer to flash. I believe Speedmod uses 2.x. If your recovery menu is green, you need a newer recovery and thus, a newer kernel, to flash.
Sent from parts unknown.
Boraltis said:
Flash a kernel with CWM 5.x. It has the option to install zips from the external SD. Most roms now require CWM 3.x or newer to flash. I believe Speedmod uses 2.x. If your recovery menu is green, you need a newer recovery and thus, a newer kernel, to flash.
Sent from parts unknown.
Click to expand...
Click to collapse
Thank you for your help...
I have tried flash different kernals....but still when i entered the recovery mode i am still seeing speedmod kernal....(green Color)....I am not sure of what to do...
here is what I am doing....
I am connecting the phone to Computer in Download Mode using ODIN....
then using PDA I am updating the kernal....most of the times it said success....
and when I go back to recovery I can still see the green menu.......
I am not able to access ICS, please help me out with this.....
Thanks
By any chance have a update.zip in your sdcard?
no I don't think so.....i tried to do it couple of times...... but it said that there is no such file
Seems you just might have flashed a very old stock rom. I recommend just flashing stock KH3 w/ boogs kernel. That's always worked wonderfully for me.
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
User_99 said:
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
Click to expand...
Click to collapse
I have the Stock Samsung Android 4.1.2 installed. I'll try it again with an older kernel. Thanks for your help.
nokiamodeln91 said:
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
Click to expand...
Click to collapse
I tried it several times, also after removing the battery. no success. Is is necessary to use ODIN? I use Heimdall as I mentioned, because I am running Mac OS.
I'll try it with a different kernel and report back here about my results. Thanks a lot.
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
What
grosserzampano said:
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
Click to expand...
Click to collapse
Install terminal emulator and try the command
su
reboot recovery.
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
grosserzampano said:
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
Click to expand...
Click to collapse
May be the recovery partition is messed up due to the usage of rom manager earlier. Try to flash a stock rom.
grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
go to download mode and flash stock rom of note 1 via odin then after successful installation u can go to recovery mode and install this zip ur phone will be rooted and phliz touch will be installed
for any help u can PM me
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/
Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan
the galaxy tab 8.9 is quite aged so i thought that i could pump some newer juice in it. bad luck, it got bricked. stuck at the samsung logo, bootlooping over n over
it started when i tried to install twrp, my current recovery is cwm. currently, i can only boot into download mode. so, i tried flashing back cwm, twrp and even stock recovery but all of it failed. i also tried flashing another stock rom but it also failed. odin didnt even tried, it stucked at "SetupConnection"
can anyone hand out a helping hand?
when i tried to reboot it back now, it asks me to "select recovery from kies" something like that about an error.
?*
bumayang said:
the galaxy tab 8.9 is quite aged so i thought that i could pump some newer juice in it. bad luck, it got bricked. stuck at the samsung logo, bootlooping over n over
it started when i tried to install twrp, my current recovery is cwm. currently, i can only boot into download mode. so, i tried flashing back cwm, twrp and even stock recovery but all of it failed. i also tried flashing another stock rom but it also failed. odin didnt even tried, it stucked at "SetupConnection"
can anyone hand out a helping hand?
Click to expand...
Click to collapse
I have a similar problem. I am waiting for tablet to die (battery dead) then plug into wall charger and it should bring up download mode.
Do you have the LTE model?
droiduzr2 said:
I have a similar problem. I am waiting for tablet to die (battery dead) then plug into wall charger and it should bring up download mode.
Do you have the LTE model?
Click to expand...
Click to collapse
im afraid i dont
Going to necro this because I've had the same problem as the OP (but not 2nd message).
I had CWM 5, tried to flash TWRP (so I could get Nougat), ended up with no recovery bootable. Can anyone help me get back with a recovery?
Tried to flash TWRP 3 but stuck at "failed". The tab was stuck in like 2% status, and wouldn't respond to Odin commands to flash again, so I had to reboot it.
Then there was no recovery I could boot into (icon would just flash when I tried to enter recovery from bootloader menu).
If I don't try to boot into bootloader menu, it sometimes would show the message "Software update failed", but would still accept Odin flashing.
I tried flashing via odin TWRP 2.6, 2.7, 3.0, CWM 5.5, Stock recovery and all did not work. TWRP <=2.7 and CWM would flash OK but still could not enter it, icon would just flash the icon but not change screen.
It doesn't display "Software update failed" screen anymore, but when I try to boot it normally with power button, it will always go into bootloader mode. If I restart with power + vol -, it would go into bootloader menu for you to choose between recovery and bootloader mode.
What should I do next to get a recovery back?
I haven't tried from Odin flashing a full stock image since I can't find a working download link anymore since hotfiles and devhost are down. Does anyone have a .tar or .tar.md5 for Odin flashing they could link me?
Never mind. I managed to find a stock image flashable by odin, flashed that and recovered stock recovery (and a stock ROM). I used the stock recovery to flash TWRP and then used TWRP to flash a new ROM, and all seems to be well now!
pd12 said:
I used the stock recovery to flash TWRP and then used TWRP to flash a new ROM, and all seems to be well now!
Click to expand...
Click to collapse
It is not possible with Stock recovery to flash the TWRP Recovery.
I think your Stock image has an CWM Recovery ( its a modified Stock Recovery ) and it is possible to flash TWRP.
pd12 said:
I managed to find a stock image flashable by odin, flashed that and recovered stock recovery (and a stock ROM).
Click to expand...
Click to collapse
Hi, that's great news! Would you be able to share where you got the ROM from and what version of Odin you used (and where you got it) please?
I am stuck on the boot screen with my GT-P7300. The stock images I have found so far don't flash through Odin and also fail in the recovery.
Many thanks in advance
dertobes
Hello, just bought an used i8190. Since last friday i have been trying to flash a custom recovery on this phone via Odin, but after i flash it returns to the default recovery on next boot.
Yes, i have unchecked the "Auto-reboot" option on Odin. I turn off the phone and then manually enter recovery but with no results. I rooted the phone pretty easily and installed both TWRP and CWM apps to flash from android, but they don't work either (twrp crashes always and CWM just gives me an error.
Mi baseband model is XXAll2
kernel is 3.0.31 [email protected] (root name seems weird)
I searched the forum and found similar cases with the baseband, but even so i haven't found a concrete solution.
I even flashed a new pre-rooted rom from this thread: https://forum.xda-developers.com/showthread.php?t=2030282
Mi compilation number has changed to XXAMG1 but the baseband remains the same. I can't flash a recovery whatever i try.
I hope someone can give me an answer, cause i really want to use this phone feautures to it's fullest
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Glass_Arcana said:
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Click to expand...
Click to collapse
Flash the stock rom as it will fix bootloops and bricked devices. Make sure to have the right ROM and flash it with Odin. The os may take longer on first boot and make sure to factory reset it as data may cause bootloops, then try flashing the recovery.
I flashed twrp 3.1.1 through Odin