Related
Hey guys,
My situation is that I'm trying to get a working ICS rom working, but I get a black screen on bootup for both Virtuous Quattro and Ice Cold Sandwich. I've also tried different kernels, but the same thing happens.
What I did:
Reboot into ClockworkMod Recovery
Backup
Wipe data
Wipe cache
Wipe dalvik cache
Install zip from sd card > Choose zip > Picked my zip here > Confirm
The actual rom installs with no errors or anything... then when I try to reboot, I get the white screen with "htc" in green font, as normal, then it just goes to a black screen. The backlight is on, but the screen is black... softkeys are not lit, either. Like I said, I've reflashed multiple times to no avail. I've seen videos of people on YouTube flashing on IncS, but their devices go straight to the bootloader animation after the htc logo screen.
Anybody encountered this before or know how to fix it? Thanks in advance.
anonymousthing said:
Hey guys,
My situation is that I'm trying to get a working ICS rom working, but I get a black screen on bootup for both Virtuous Quattro and Ice Cold Sandwich. I've also tried different kernels, but the same thing happens.
What I did:
Reboot into ClockworkMod Recovery
Backup
Wipe data
Wipe cache
Wipe dalvik cache
Install zip from sd card > Choose zip > Picked my zip here > Confirm
The actual rom installs with no errors or anything... then when I try to reboot, I get the white screen with "htc" in green font, as normal, then it just goes to a black screen. The backlight is on, but the screen is black... softkeys are not lit, either. Like I said, I've reflashed multiple times to no avail. I've seen videos of people on YouTube flashing on IncS, but their devices go straight to the bootloader animation after the htc logo screen.
Anybody encountered this before or know how to fix it? Thanks in advance.
Click to expand...
Click to collapse
Your phone must be rooted before this and also verify your downloaded zip file with checksum to make sure about proper download.
I actually encountered the same problem a few days ago. I realized it was because I flashed an incompatible Kernal zip file. So I reflashed the ROM and rebooted without flashing any kernals and it worked for me.
I have rooted, and have superuser access. I have also redownloaded and checked the md5 sums. I'll try to download it again and test...
I just redownloaded and rechecked the md5 sums, and I still get the black screen. I've also tried no kernel, and tiamat and still nothing :S
anonymousthing said:
I just redownloaded and rechecked the md5 sums, and I still get the black screen. I've also tried no kernel, and tiamat and still nothing :S
Click to expand...
Click to collapse
have u converted you filesystem to ext4?
btw, what rom was previous? stock one or custom?
and i recommend you to use 4ext recovery instead of CWM
I have to use CWM for now, since I don't have access to fastboot right now (i'll download it later), but how do I check if it's ext4 or not in CWM? And if its not, do you know how to make it ext4?
And i'm using CM7, not stock
anonymousthing said:
I have to use CWM for now, since I don't have access to fastboot right now (i'll download it later), but how do I check if it's ext4 or not in CWM? And if its not, do you know how to make it ext4?
And i'm using CM7, not stock
Click to expand...
Click to collapse
if u have CM7 ur filesystem already converted )))
i think the reason of crashes on boots is old version of recovery. try to upgrade urs CWM or install the latest 4ext recovery
It's very easy to change CWm to 4ext: go to http://4ext.net/ and download 4EXT Recovery Updater, install it. With its help u will instal 4ext
Are you s-off?
Sent from my Incredible S using xda premium
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
anonymousthing said:
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
Click to expand...
Click to collapse
i'm afraid s-on is the reason of ur problems
I completely agree s-on does matter always.
I have the same problem on Quattro.
If you are s on you have to flash via fastboot the boot.img inside the Rom.zip from your wanted rom after flashing Rom via recovery.
Fastboot flash boot boot.img
Sent from my HTC Incredible S using xda premium
Indeed sniper is correct. However what I would do, get a rom working then look into becoming s-off. Its so much easier to mod your phone after.
Sent from my Incredible S using xda premium
Okay, thanks guys! I'll try it out later and see how it goes by flashing boot.img using fastboot.
Thanks guys, it works!
For people who come here looking for answers, basically just open the new ICS rom zip, extract boot.img, cd to that folder in cmd, and type:
fastboot flash boot boot.img
and it should now boot properly.
anonymousthing said:
Thanks guys, it works!
For people who come here looking for answers, basically just open the new ICS rom zip, extract boot.img, cd to that folder in cmd, and type:
fastboot flash boot boot.img
and it should now boot properly.
Click to expand...
Click to collapse
Or just make s-off one time and flash roms without any necessity to flash boot.img manually
Sent from my Incredible S using Tapatalk
I have HBOOT 2.0, sadly I accidentally updated my original htc and it updated HBOOT as well... and I can't be bothered to downgrade now lol
I'll do it later when I have the time to download the downgrade toolkit
anonymousthing said:
I'm not S-OFF, but my bootloader is unlocked... i think it doesn't really matter much in this case if I have/can flash CM7 without issues
I'll try another version of CWM or try 4ext recovery tomorrow sometime
Click to expand...
Click to collapse
I had a issue with something on my SD card after i wiped my SD and tried the re install it worked.
let me know if that helped.
Hey guys,
when I tried flashing CWM on my new HTC One it just booted in normal mode over and over.
I tried every recovery-image available and it nerver worked.
While playing around I finally got it working without flashing the recovery image to the boot partition!
No need to copy root files and CFW files before flashing the recovery!
Instructions
Unlock your device at http://www.htcdev.com/bootloader/
Reboot into bootloader
> fastboot flash boot boot.img - thanx to Paul O'Brien
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img - thanks to Flyhalf205
> fastboot erase cache
After this you should be able to enter recovery via bootloader or 'adb reboot recovery'.
The recovery image is CWM Touch 6.0.2.8 which worked great for me, didn't try the other ones right now.
I hope I could help
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Nekromantik said:
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Click to expand...
Click to collapse
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
zantekk said:
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
Click to expand...
Click to collapse
Ah ok.
only issue for me now is aroma freeze issues.
Nekromantik said:
Ah ok.
only issue for me now is aroma freeze issues.
Click to expand...
Click to collapse
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
zantekk said:
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
Click to expand...
Click to collapse
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Device still rebooting
Can't flash recovery
same here - no access to recovery so far
Same for me too
Why ?
Got a HTC One from Orange france, and NO RECOVERY seems to stick. That thing boots, but i cannot enter recovery
I've tried using the AiO-Kit to flash CWM touch and normal as well as TWRP as well as the two CWMs manually and then this method. Still can't get access to recovery though
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Lothaen said:
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you mean clearing the cache as mentioned in that thread I've tried it with no success
SoLdieR9312 said:
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Click to expand...
Click to collapse
Had the same problem again and again flashing TrickDroid on my HTC One (M7). Can confirm, that avoiding touch will relieve things but freezes can still occur. A few times I even could not reset the phone long-pressing the power + volume up buttons, means I was completely stuck on the frozen aroma screen (since a battery pull is not possible with this device). For anybody who may be in the same situation, try the "[FONT="Courier New]fastboot reboot[/FONT] command, this still came through and rebooted the device.
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
pwr2wh8 said:
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
Click to expand...
Click to collapse
Yes, worked for me. I had the same issue. While flashing Renovate rom, Aroma crapped out right at the end where it was installing the kernel. I was then stuck on boot image until i found this thread.
Also, for what it's worth, i thought I'd flash the boot image again after i got my device running again but it killed my wifi. I had to reflash the rom as wifi in settings was `out of order`....
//edit: okay. i've been able to reproduce the crashing. seems it's an aroma/rom issue (i couldn't tell one way or the other). what matters here is flashing boot image with the provided image does the trick. whatever magic it does, i'm able to flash cwm recovery 6.0.3.1 but I have to flash boot image before, else flashing recovery is fruitless.
anyways, thanks. this thread help me solve what i thought was `bricked` device.
So yeah i bricked my phone, its stuck in a damn bootloop and i cannot enter recovery no matter which one i install.
I even flashed stock rom via odin and tried both flashing twrp and cwm, none worked, whichever rom is installed i still get in a damn bootloop and i cannot boot into recovery (blank screen).
Is there anything i can do for my phone?
Thank you all in advance
Try to flash Dorimanx Kernel using Odin (v9.34 for JB Roms, v8. for Stock Roms)
I will upload a guide tomorrow for people facing problems with their recovery. I will edit this when its finished.
EDIT: Here it is: http://forum.xda-developers.com/showthread.php?t=2441940
Sent from my GT-I9100 using xda app-developers app
Hit Thanks please
OverkillSRB said:
So yeah i bricked my phone, its stuck in a damn bootloop and i cannot enter recovery no matter which one i install.
I even flashed stock rom via odin and tried both flashing twrp and cwm, none worked, whichever rom is installed i still get in a damn bootloop and i cannot boot into recovery (blank screen).
Is there anything i can do for my phone?
Thank you all in advance
Click to expand...
Click to collapse
can you tell me what did you do to caused that ? or do you have download mode ?
anyway it seems to me a hard break . probably you messed your boot . you got two options:
1.use "RescuePDA" (you can find the thread and every thing in galaxy mini II development)
2.take it to a service center
dlb4all said:
can you tell me what did you do to caused that ? or do you have download mode ?
anyway it seems to me a hard break . probably you messed your boot . you got two options:
1.use "RescuePDA" (you can find the thread and every thing in galaxy mini II development)
2.take it to a service center
Click to expand...
Click to collapse
Download mode is the only thing that works, as i said recovery wont boot and any rom i install is getting into a bootloop. ((
I used triangle away, the problems started after that. I had cwm and cm 10.1 08/18
Is there any way to factory reset using odin?
I have the same exact problem.
I follow the discussion with interest.
zeruel857 said:
I have the same exact problem.
I follow the discussion with interest.
Click to expand...
Click to collapse
Zeruel, i seem to have somehow fixed the problem, however not entirely.
I downloaded some random recovery rom, flashed it with odin and wiped everything (cache, factory reset, dalvik cache), and reinstalled cm 10.1.
Then i flashed back the thewhisp's recovery and booted into cm with no problem.
However now i cannot boot into recovery using volume+- and home and power button, i have to boot to it from the cm.
That i dont know how to solve, but at least my phone works fine
Thank you, but I think to have solved the problem with RescuePDA.
A big thanks go to dlb4all, thank you a lot mate.
zeruel857 said:
Thank you, but I think to have solved the problem with RescuePDA.
A big thanks go to dlb4all, thank you a lot mate.
Click to expand...
Click to collapse
no problem man . my pleasure :good:
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Medarioth said:
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Click to expand...
Click to collapse
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
JasSingh93 said:
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
Click to expand...
Click to collapse
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Medarioth said:
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Click to expand...
Click to collapse
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
JasSingh93 said:
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
Click to expand...
Click to collapse
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
The link you gave redirect me for a post of yours.
Medarioth said:
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
Click to expand...
Click to collapse
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
JasSingh93 said:
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
Click to expand...
Click to collapse
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Medarioth said:
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Click to expand...
Click to collapse
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
JasSingh93 said:
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
Click to expand...
Click to collapse
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Medarioth said:
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Click to expand...
Click to collapse
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
JasSingh93 said:
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
Click to expand...
Click to collapse
ok will try and keep you updated
Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
Ok, you shouldn't have any problems anymore :fingers-crossed:
Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Medarioth said:
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Click to expand...
Click to collapse
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
JasSingh93 said:
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
Click to expand...
Click to collapse
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Medarioth said:
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Click to expand...
Click to collapse
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
JasSingh93 said:
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
Click to expand...
Click to collapse
done. waiting in progress ....... :fingers-crossed:
Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
It should definitely work this time! I've actually just flashed TWRP recovery, and I can already say I prefer it over ClockWorkMod!
Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Medarioth said:
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Click to expand...
Click to collapse
Yayyy!!! Nice one! Good teamwork we got there in the end! Happy to help
Have fun!!
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
panamera2011 said:
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
Click to expand...
Click to collapse
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
bfürbanane said:
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
Click to expand...
Click to collapse
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
panamera2011 said:
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
Where does it say to install SuperSU? How would that be possible when Android is not booting.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
I'm sorry but it's really strange, never had installation issues with any version of this rom
Have you tried this kernel to install the rom?
https://www.androidfilehost.com/?fid=24052804347829437
Sent from my H60-L02 using Tapatalk
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Sorry but I confused the message with the MIUI 6.2.12 thread [emoji16]
Sent from my H60-L02 using Tapatalk
AutumQueen92 said:
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
Click to expand...
Click to collapse
I tried that. I went to samsung-updates.com and downloaded a version that I believe is compatible with my baseband version. Is there any way to check what baseband version my phone has? Then I flashed with odin and was stuck in a bootloop. I then flashed PhilZ recovery and the boot hangs at the samsung logo.
bfürbanane said:
Is there any way to check what baseband version my phone has?
Click to expand...
Click to collapse
Settings>about phone>
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
The phone is not booting.
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
Doh! sorry not reading what's in front of me. I did once read that you can get phone number via ADB, maybe the same will work for baseband?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
N00b... said:
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
Click to expand...
Click to collapse
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
bfürbanane said:
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
Click to expand...
Click to collapse
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Condox18 said:
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Click to expand...
Click to collapse
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
same problem
bfürbanane said:
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
Click to expand...
Click to collapse
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Condox18 said:
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Click to expand...
Click to collapse
Thanks for the pointer. I subscribed myself to that thread.