Hey Guys,
Before i start let me explain that i use to cook roms for my magic, so i know what im doing with this stuff.
Anywho i have been having a weird issue where whenever i flash a rom, it will not boot to either the rom or back into the recovery. my only option is to relock the bootloader and flash back to the stock ruu, and reinstall recovery.. right now im stuck on the stock rom and i hate it!
btw the device is s-off and unlocked bootloader, so wth, if anyone has any advice please let me know!
Did you try reflashing the recovery? Or a different recovery ? had a problem once with my pc antivirus blocking certain files and was causing the zip to be corrupted , just some thoughts
shael said:
Hey Guys,
whenever i flash a rom, it will not boot to either the rom or back into the recovery.
Click to expand...
Click to collapse
All you get is the white HTC screen when you reboot?
What about when you boot into HBOOT, then choose recovery manually?
As you mentioned, you're used to this stuff, so this part probably isnt helpful - do you do the 4 wipes when flashing? (data/cache/dalvik/system?)
I wonder if (even though you are S-OFF), the kernel portion of the rom isnt flashing? This can cause your phone not to boot and just sit there... i.e. your phone hasn't experienced a stockish/insecure kernel flash first, so recovery is having trouble flashing the custom recovery that comes with the rom.
See this thread for more info (it helped another user):
http://forum.xda-developers.com/showthread.php?p=30658376#post30658376
Also - to what Bigtjmc is saying - in the link above, I mention the recovery I use (which has not let me down at all!) Maybe you want to try it (if you're not using it already?)
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
Try Wildchild's Recovery (by far MY most favorite)
And if it's not passing verificiation, like the other user said check your anti-virus and check the MD5 Checksum to make sure you have a complete good download, wipe all data cache and blah blah blah then with fastboot "fastboot flash boot <Insert kernel file name here>.img
hmm, well in the past ive always flashed kernel with fastboot... its almost like my chip timed out and wont let me flash the kernel anymore :s
If recovery is crashing you might need to relock the bl and run the stock ics ruu to get you back up and running then try n start over , I used the tool kit just this morning for the same troubles and got back where I wanted to be in just a few minutes .
shael said:
so, yes i have reflashed the recovery and if i select the recovery from the hboot (as i always do, its starts to load the recovery then reboots too the white screen.... and hmm ill give that link a look and see, because to me the problem seems something with the kernel causing the crashes and corruption with the recovery as well... also weirdly enough the .zip isnt passing the verification.... weird?
Click to expand...
Click to collapse
This happened to me as well... can't remember what script it was that was running but there is a script that is associated with a rom (vague I know) that is messing up the cache partition. If I remember correctly I also might be associated to the recovery you are using... but I can't remember. Anyway, If you do a fastboot erase cache command from the bootloader and re-flash the recovery of your choice you should be back to normal.
Awesome, thanks for you help guys, unfortunatley i dont have easy access to a pc, so i gotta wait a bit before i can try this... thanks again though
OMG!!!!! you guys are simply amazing, thank you everyone for your help! wiping the cache from fastboot, then flashing stockish kernel, then flashing cwm recovery, then wiping cache, and factory reset, then flashing my rom worked!!! <3
Related
Okay, so I have everything flashed and Cyanogen's mod is working. However I decided to flash the radio as well. On entering recovery, it is now stuck at the loading screen (with the 4 color X's). Is this normal after flashing radio? I read that you are supposed to be patient and not remove the battery after flashing radio. How long does it usually take? It has been on this screen for about 20 minutes now.
How did u flash the radio? Did u do it from recovery? Normally after initiating flashing radio through recovery, it will extract the package, then reboot and install the new radio, THEN reboot again.
It's hard to say where u might have gone wrong without more info.
I flashed from fastboot using "fastboot flash radio radio.img". It said done on the two lines (Flashing and writing?). Anywho, I decided to go ahead and boot to the recovery to install my gapps. This is when it got stuck on the 4 color logo X. It is still there.
Can you go into the bootloader, or the recovery console? I just want to know if you have bricked your phone or not, if you haven't - then I recommend you just try wiping everything (as usual) and reflashing the ROM. If that doesn't work, at least I tried to be helpful.
Well I haven't removed the battery and tried rebooting yet. Should I?
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
cicrockets said:
Okay... I can get into the bootloader. So I just redo everything from step 1? Interesting... After removing the battery and trying again, it seems to boot into recovery mode fine. Just finished installing gapps. Boots fine now. I guess it was just a one time flaw. Phew... The radio doesn't seem to have been flashed. Under settings, baseband version has not changed.
Click to expand...
Click to collapse
I would recommend downloading the radio in a .zip format made to flash through recovery... that's the most reliable in my experience...
Thanks, I might try that next time. Too much suspense in one day pour moi.
I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.
Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App
fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.
fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU
I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos
Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.
I have no idea what happened, my Hero has been rooted for over a year now and never had any problems. I flashed a herodeck rom version 1.2 and after that I could not flash any more roms but could restore all my nandroids. So I used this, RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.rar, to go back to stock and installed unrevoked, and all went well. I then flashed this TeamHeroC-2.3.5-01OCT-CM-V2.zip and finally it worked and was working great until last night my battery went dead and when I plugged it in to charge it powered up to the white HTC screen and has been stuck there since. I have tried to reflash , restore nandroids, and even hboot a HERCIMG and that is when I noticed S-ON. and since this has happened every file I try to flash comes up corrupt and the latest CM rom came up no signature, and I keep getting errors such as this. So right now all I can do is boot into recovery or Hboot. Please someone help me with this. I love this phone!
williams1978 said:
I have no idea what happened, my Hero has been rooted for over a year now and never had any problems. I flashed a herodeck rom version 1.2 and after that I could not flash any more roms but could restore all my nandroids. So I used this, RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.rar, to go back to stock and installed unrevoked, and all went well. I then flashed this TeamHeroC-2.3.5-01OCT-CM-V2.zip and finally it worked and was working great until last night my battery went dead and when I plugged it in to charge it powered up to the white HTC screen and has been stuck there since. I have tried to reflash , restore nandroids, and even hboot a HERCIMG and that is when I noticed S-ON. and since this has happened every file I try to flash comes up corrupt and the latest CM rom came up no signature, and I keep getting errors such as this. So right now all I can do is boot into recovery or Hboot. Please someone help me with this. I love this phone!
Click to expand...
Click to collapse
Check md5sums of the zips in your sd card to verify no corrupt files. Also make sure signature verification is not toggled in CWM.
dastin1015 said:
Check md5sums of the zips in your sd card to verify no corrupt files. Also make sure signature verification is not toggled in CWM.
Click to expand...
Click to collapse
Thanks for the advice, I will check the Md5sums but I am actually using darchstar's RA recovery at the moment. Also I have formatted my sd card a couple of times and ran disk check on it and also downloaded the roms and files several times.
Hi,
If u have the time, unroot the same way again and then reroot but this time use ROM manager(free version). Update to latest recovery and then
Start over.
It sucks but without the proper knowledge its difficult to fix some issues. So starting over is easiest.
Good luck
V'sHERO on Tapatalk
I'm having the same problem but I cant even flash the stock ROM.
blacksapphire08 said:
I'm having the same problem but I cant even flash the stock ROM.
Click to expand...
Click to collapse
Can u flash anything else?
If so, u may just have a bad download or u have to do at least a factory reset b4 flashing anything.
Good luck
Unroot zip file is also EZ if u just want stock out of the box back on ur phone.
V'sHERO on Tapatalk
vidaljs said:
Hi,
If u have the time, unroot the same way again and then reroot but this time use ROM manager(free version). Update to latest recovery and then
Start over.
It sucks but without the proper knowledge its difficult to fix some issues. So starting over is easiest.
Good luck
V'sHERO on Tapatalk
Click to expand...
Click to collapse
Again thanks for the advice but I can't even do that now as I am stuck on the HTC screen and all I can do besides look at a white HTC screen is boot recovery (darchstars RA recovery) and boot into bootloader. Everything I try to flash will not verify for some reason or another(corrupt or unsigned or something crazy like that) and the RUU will not connect to the phone because it is stuck at the white HTC screen. This one has really stumped me as I have brought this phone back from some bad predicaments, or at least I thought they were. I did get it to try and flash a hercimg of an extracted RUU that is on this forum but it ends up saying no image found and just goes back to the bootloader menu.
williams1978 said:
Again thanks for the advice but I can't even do that now as I am stuck on the HTC screen and all I can do besides look at a white HTC screen is boot recovery (darchstars RA recovery) and boot into bootloader. Everything I try to flash will not verify for some reason or another(corrupt or unsigned or something crazy like that) and the RUU will not connect to the phone because it is stuck at the white HTC screen. This one has really stumped me as I have brought this phone back from some bad predicaments, or at least I thought they were. I did get it to try and flash a hercimg of an extracted RUU that is on this forum but it ends up saying no image found and just goes back to the bootloader menu.
Click to expand...
Click to collapse
Try downloading a recovery from Dastin's thread. Rename it HERC.IMG and place in the root of the SD card. Bootloader and flash. Power down then hold home and power back up to see if recovery worked. See if you can get any recovery flashed at all and if you do you can fix anything then.
¦¦self proclaimed resident prick¦¦
I finally got clockwork recovery 2.5.0.7 by using adb to push to sd card and then flashing from adb. Still can not do anything else, it is still acting the same.
http://forum.xda-developers.com/showthread.php?t=1063843
Try this there's alot of good links.
Sent from my DROID3 using xda premium
You might want to try getting s-off via darch's method. Then flash the eng-spl. Then do a fastboot erase system -w. Then reflash your recovery to see if that helps. If you need any of the files mentioned just pm me and I'll send you a dropbox link. You should be able to get back up and running this way. Good luck.
Locked & Loaded
""Shooter on Deck""
laie1472 said:
You might want to try getting s-off via darch's method. Then flash the eng-spl. Then do a fastboot erase system -w. Then reflash your recovery to see if that helps. If you need any of the files mentioned just pm me and I'll send you a dropbox link. You should be able to get back up and running this way. Good luck.
Locked & Loaded
""Shooter on Deck""
Click to expand...
Click to collapse
Ok I downloaded 1 of the zip files for darch's eng spl because the first link sems to be down. But I transfered the zip onto my sd card with card reader/writer and computer and then flashed it with clockwork 2.5.0.7 and I now have s-off again finally. So before I do anything else I am going to wait and se what you guys think I should do now. Thanks for all the help guys
williams1978 said:
Ok I downloaded 1 of the zip files for darch's eng spl because the first link sems to be down. But I transfered the zip onto my sd card with card reader/writer and computer and then flashed it with clockwork 2.5.0.7 and I now have s-off again finally. So before I do anything else I am going to wait and se what you guys think I should do now. Thanks for all the help guys
Click to expand...
Click to collapse
Are you formatting boot, system, cache, and data before flashing any of these roms? I do it 3x for each partition to make sure everything is wiped clean.
I have always thought that unrevoked was a permanent s-off unlike darch's which is temporary. I have both. I have always felt that if i can get into recovery, I'm golden. Make sure everything is wiped (not just data and cache) before you flash a new Rom.
Sent from my wildheroc using XDA App
Drunkpilot said:
Are you formatting boot, system, cache, and data before flashing any of these roms? I do it 3x for each partition to make sure everything is wiped clean.
I have always thought that unrevoked was a permanent s-off unlike darch's which is temporary. I have both. I have always felt that if i can get into recovery, I'm golden. Make sure everything is wiped (not just data and cache) before you flash a new Rom.
Sent from my wildheroc using XDA App
Click to expand...
Click to collapse
Yes, a couple of times, manually and with Light's format and Caulkin's format. and also I tried to fastboot hercimg.zip of the extracted RUU and all was going well and it actually finally asked if I wanted to apply the update like it is suppose to and it started loading and then when it finished it rebooted hboot and tried to install it again and also at this point I had s-on again. So I redone everything and am now back to s-off.
williams1978 said:
Yes, a couple of times, manually and with Light's format and Caulkin's format. and also I tried to fastboot hercimg.zip of the extracted RUU and all was going well and it actually finally asked if I wanted to apply the update like it is suppose to and it started loading and then when it finished it rebooted hboot and tried to install it again and also at this point I had s-on again. So I redone everything and am now back to s-off.
Click to expand...
Click to collapse
Are you still on a stock "sense" rom right now? What is your PRL, Radio, and PRI? Make sure everything is updated and you should be ready to go now. Since you are S-off now, I would place a HERCIMG.zip on your sd card of a recovery (I've been liking the 4.0.1.4 Orange Lantern that Dastin compiled (which is an unofficial CWM) just so that I have it at the ready in case anything goes south.
If your s-off again make a nand if you can. Also like dp asked what rom, radio, are you on???. Also imo you should flash Ra1.7 untill your back up and running for this process and just revert back when all this is done. Also you should do a fast boot erase system -w to clear everything out. Then backup your sd to your pc and format it as well. Once threw your pc and restore the defaults and then threw your recovery. Which is y I suggest Ra it makes it quick and easy. Ill check back here to see were your at threw out the day.
Edit: Pm sent.
Locked & Loaded
""Shooter on Deck""
The last rom I was on was [ROM][03-OCT-2011][TeamHeroC-2.3.7 - 2.6.35 Kernel] but I am stuck at the white HTC screen right now has been all day. When you say RA 1.7 recovery are you talking about Darchstar's RA 1.7?
Still no luck everything I try to flash fails, I kept getting an error 5 in clockwork recovery when trying to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 (9 Oct 2011).
williams1978 said:
The last rom I was on was [ROM][03-OCT-2011][TeamHeroC-2.3.7 - 2.6.35 Kernel] but I am stuck at the white HTC screen right now has been all day. When you say RA 1.7 recovery are you talking about Darchstar's RA 1.7?
Still no luck everything I try to flash fails, I kept getting an error 5 in clockwork recovery when trying to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 (9 Oct 2011).
Click to expand...
Click to collapse
Yes, I am.
Locked & Loaded
""Shooter on Deck""
Okay I switched recoveries to RA 1.7. I have tried several times to flash CyanogenMod 7 for the HTC Hero (CDMA) :: V7.1.0 and each time a different file comes up corrupt but I have been checking the md5's after it is on the sd card and they have been good. It is crazy, I can flash everything but Roms.
You should do a fastboot erase system -w.
Locked & Loaded
""Shooter on Deck""
Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz
Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.
okay, first of all i will say that im sorry if what im writing is full on faulty language. enlgish isnt my best. aaaanuslut i got my brothers old gt n7000 with a broken touchpad and screen for free. i repaired that with 160€ and my brother said that the phone was rooted. i found out he had allso overclocked the device. But after a few restarts to the phone it just said something what i think was in spanish or something "bla bla bla dos sistema". After that came not your old samsung logo, but purple blueish circles just circling. Ant thats it, it would not start. So i read about bricked devices, and as much as i understood i had a soft brick. so i was looking aroun the forum for some easy fixes becasue im totally stranger to this kind of hacking. i finaly found this http://www.youtube.com/watch?v=F97qo1moAR4 and i downloaded custom jb N7000XXLSZ_N7000OPSLS6_N7000XXLSO_HOME.tar. it did work but again after i tried to restart the phone it was stuck.
So since i dont want any custom stuff i think to my self why not stock rom. so i found this http://forum.xda-developers.com/showthread.php?t=1424997. But since i dont like JB as much as ICS i will try ICS. Her is the question: i allready did the factory reset and cache wipe but this instruction says not to FROM ICS.
Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM
Does that mean that i have allready gone wrong or does that mean that you have to have ICS on youre phone and then you cant do any of those things? its really confusing and i dont want to fk up my phone.
Did you make a wipe on stock ICS recovery?
zai89 said:
Did you make a wipe on stock ICS recovery?
Click to expand...
Click to collapse
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
orizont said:
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
Click to expand...
Click to collapse
can your phone boot to recovery mode now?
zai89 said:
can your phone boot to recovery mode now?
Click to expand...
Click to collapse
Yes i can
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Allright, thankyou, since i am new to all this stuff i will try to locate a tutorial. i dont have any idea for instance, what is recovery phils kernel.
at own risk, here http://forum.xda-developers.com/showthread.php?t=1901191. Download zip, keep zipped and put on external sd. Reboot recovery and flash via install from sd option.
Since we are going to wipe latest version will do fine. However if you plan to reflash the original Samsung rom one that is same or likewise version is best to quickly root after flashing rom, so you can flash speedmod kernel (better battery life) after. Find in original dev thread of this forum.
Remember, via factory format on phills kernel recovery(reboot in recovery) you have the option to do a wipe for new rom.
Otherwise on Phills kernel recovery do factory, cache wipe. In advanced dalvik cache, in mounts all(warning take out external sd before so you dont wipe that)
Then your phone is clean, you shouldnt have to wipe efs anyway, so dont tick that option ever in pc odin when flashing rom with odin.
This is the cleanest way to get rid of All leftovers and generally the way to go before flashing any new rom. However risk of loosing photos and whatever you have not backed up. In general backing up is bad as old files/db/etc are put back (risk of unforeseen stuff happening) Check one of my 5 threads for what backups there are. Via my profile you find them
Enjoy!
Sent from my GT-N7000 using Tapatalk 2
Okay, im thankful for all this information, useful stuff, got the PhilZ-cwm6-XXLT6-XSA-5.06.1-signed.zip.
let us know how it went, ok?
OOOKAY! so i finaly did what baz77 described. and rooted with another phils kernel witch i chose after my downloaded rom. Did root it, and after powering down and waiting about 3-5 sec. i started it, and it worked, no more getting stuck on gt n7000 screen and so on. and i also downloaded emmc check app, but unfortunatley it said. Brick bug: YES. Insane Chip.
sorry for double post, how do i delete? all i can do is use edit/delete button but it only edits the post, how can i delte it?
You cant but thats ok.
all n7000 have the brickbug to my knowledge, the test should state if the bug has been triggered, if not then super, if it has, best to secure the broken emmc sectors. Tricky.
I think having it clean now should eliminate earlier issues Enjoy your n7000
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
orizont said:
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
Click to expand...
Click to collapse
not sure how that is happening. Maybe a logcat (logfiles) shows whats happening when it happens. Could be app. Maybe rom issue. Method of elimination counts here.
On safe kernel, try dalvik cache, cache wipes and fix permissions in recovery, reboot and check if reoccurs.
Otherwise, updated versions, clean install I would recommend.
You can check also before with that emmc app if there are bad sectors. I dont expect it but you never know
Okay, its been a long time since i did that stuff. And it worked allirght. i got my phone working and rooted. Great stuff here
Sorry for updating old topic. Since people who have helped me with my phone allready are familiar with my case. I was wisiting a friend of mine in england and after i returned home my phone is f**ked. Everything works okay, but when i turn on mobile data or wifi it instantly freezes. Takes about 15-20 sec. and then phone does an automatic restart which restarting gets into boot loop. I have to hold down bower button to reboot again. When it asks me for sim unlock code, i have to be quick when im inserting it because i need to turn off mobiledata/wifi as soon as ia get my phone running again, otherwise it will freeze and crash again. Can it be somekind of virus or something? Is it most likely that i have to again format and install philz kernel and all that stuff? Thanks in advance.
that would be the best way to start..IMO
I really dont have the time or opportunity to format and reflash, but i guess its really difficult, near imbossible to tell whats wrong with my samsung. Bust still, any other suggestions?