Related
First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.
I accidently deleted my back-up and now I'm left with TWRP 2.2 and everytime I try to install a tom it fails halfway through. So I looked and most say ignore and wipe Dalvik cache, so I do. Reboot, then it just boots to TWRP.
Kindle Fire Utility will not detect my Fire either.
I'm at a loss, please help.. :\
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
Click to expand...
Click to collapse
Do a factory reset again and then flash.
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
Do a factory reset again and then flash.
Click to expand...
Click to collapse
I followed your instructions explicitly and they were to no avail, as they relinquished the same results in my latter post.
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
soupmagnet said:
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
Click to expand...
Click to collapse
I had first tried 2.0 then updated to 2.2.
Thanks
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
soupmagnet said:
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
Click to expand...
Click to collapse
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
JerzyLW said:
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
Click to expand...
Click to collapse
Lemme see what I can do...
---------- Post added at 12:17 AM ---------- Previous post was at 12:12 AM ----------
Gimme time to flash something create a backup and upload it stick around It won't be posted for long...
Thepooch said:
Lemme see what I can do...
Click to expand...
Click to collapse
It is much appreciated! :highfive:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Maybe your just doing it wrong.
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Flash rom zip (in zip form)
6. Flash gapps zip (in zip form)
7. Reboot then system if prompted....
If your doing all this and it fails make sure you have zip signature verification and md5 verification unchecked, still failing sounds like a twrp problem..
Also twrp should be throwing you some errors would be nice to know what they are?
Thepooch said:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Click to expand...
Click to collapse
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
JerzyLW said:
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
Click to expand...
Click to collapse
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
kinfauns said:
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
Click to expand...
Click to collapse
Thanks I'll take a look.
JerzyLW said:
Thanks I'll take a look.
Click to expand...
Click to collapse
No matter what I do, I cannot get my computer to recognize my Kindle. In device manager it says it is there with a yellow triangle, so I click update it doesn't work, I check my Android SDK downloader and it says I have the drivers downloaded so I manually searched for them in the extras folder in the sdk folder, still no go. I get an error. I am now at ends I have no idea what to do, and it is very aggravating to say the least.
Thanks for your help guys!
Instead of letting it boot by itself manually select normal boot in the boot menu if that doesn't work rewipe restore the backup again this time skip the dalvik and cache wipe after the restore...
My computer can't find my kindle fire and it's mounted on twrp
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Thepooch said:
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Click to expand...
Click to collapse
Yes they are but the computer wont find it. Do you know how to get the computer to find the kindle via adb?
if you cant mount your sdcard there is more at play than meets the eye look at this thread http://forum.xda-developers.com/showthread.php?t=1877567
:highfive:Just saw this over on androidpolice, wanted.to give everyone a heads up.
http://www.androidpolice.com/2012/0...s-for-the-sony-xperia-ion-now-live-at-get-cm/
This needs an unlocked bootloader? Or would it be possible use this with the stock kernel?
424aca said:
i messaged them about it...waiting for reply
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
question: if you do need an unlocked bootloader( i dont) and i flash...what is the worst that can happen?
Click to expand...
Click to collapse
Don't really know but I'd guess a brick. Probably have to go through the whole power drain flashmode process.
I was under the impression we could have roms, but with a locked bootloader we'd have to use the stock kernel. Now I don't know if a Rom has to be cooked in a way to allow for this and/or if the cm9 nightly will be packaged without a kernel. I'm thinking if the answers are "no" and "yes" we may have a shot.
424aca said:
i messaged them about it...waiting for reply
---------- Post added at 07:39 PM ---------- Previous post was at 07:38 PM ----------
question: if you do need an unlocked bootloader( i dont) and i flash...what is the worst that can happen?
Click to expand...
Click to collapse
Pretty sure it just won't flash. Just like if you tried to flash the lleaked ICS in the first couple pages of the stock firmware thread (not in the first post) with a locked bootloader. Just errored during flashing and nothing happened.
Sent from my Sony Xperia S
Spectre51 said:
Pretty sure it just won't flash. Just like if you tried to flash the lleaked ICS in the first couple pages of the stock firmware thread (not in the first post) with a locked bootloader. Just errored during flashing and nothing happened.
Sent from my Sony Xperia S
Click to expand...
Click to collapse
I have try this ROM...but when flashing it says Error Status 7
If I were you, I would not flash it cause it needs format system, but the current cwm is not able to format system. If you still try it, you may brick you phone.
siuming720 said:
If I were you, I would not flash it cause it needs format system, but the current cwm is not able to format system. If you still try it, you may brick you phone.
Click to expand...
Click to collapse
Lol it will not bricked ur phone......because only system will be format....if we change kernel sometimes will brick it....but for rom it will not...u still can use seus,flashtool or pcc to restore back
did anyone test this rom? Dose it work ?
faiisfaizal said:
Lol it will not bricked ur phone......because only system will be format....if we change kernel sometimes will brick it....but for rom it will not...u still can use seus,flashtool or pcc to restore back
Click to expand...
Click to collapse
Right, so a soft brick requiring a battery drain to shut off, then recharge to get into flasmode for restoring...a 24-36 hour process. Done it once before, would rather not do it again.
I think we need to figure out the system format issue and if we can flash this Rom on our stock kernel.
Raxtinhax said:
did anyone test this rom? Dose it work ?
Click to expand...
Click to collapse
I test it already with LT28h unlock bootloader..... but something went wrong when start to flash with CWM recovery,,with error status 7
jeriku said:
Right, so a soft brick requiring a battery drain to shut off, then recharge to get into flasmode for restoring...a 24-36 hour process. Done it once before, would rather not do it again.
I think we need to figure out the system format issue and if we can flash this Rom on our stock kernel.
Click to expand...
Click to collapse
Nah....u should not wait your battery drain just do nandroid backup using CWM recovery... if you got problem when flashing it just restore the backup back...
Great news. I'll be waiting for a more stable release. :good:
jeriku said:
Right, so a soft brick requiring a battery drain to shut off, then recharge to get into flasmode for restoring...a 24-36 hour process. Done it once before, would rather not do it again.
I think we need to figure out the system format issue and if we can flash this Rom on our stock kernel.
Click to expand...
Click to collapse
Tried already, without success.
On the xperia S forum, I found how to flash it.
1. Flash the Cm9 zip
2. Flash Gapps zip.
3. Clear cache & Dalvik Cache.
4. Flash the boot.img from the Cm9 zip using fastboot
fastboot flash boot boot.img.
I could do the first three steps, but could not complete the 4th step.
But phone does not go into Soft Brick. Just Go to flash mode and flash the firmware again and restore backup.
ganeshbiyer said:
Tried already, without success.
On the xperia S forum, I found how to flash it.
1. Flash the Cm9 zip
2. Flash Gapps zip.
3. Clear cache & Dalvik Cache.
4. Flash the boot.img from the Cm9 zip using fastboot
fastboot flash boot boot.img.
I could do the first three steps, but could not complete the 4th step.
But phone does not go into Soft Brick. Just Go to flash mode and flash the firmware again and restore backup.
Click to expand...
Click to collapse
As what i experience...i just flash thet zip through CWM recovery and it should done....but is say build.prop error...they need to modified it back.....but that build.prop match mine.... i dont know why it failed to flash
faiisfaizal said:
As what i experience...i just flash thet zip through CWM recovery and it should done....but is say build.prop error...they need to modified it back.....but that build.prop match mine.... i dont know why it failed to flash
Click to expand...
Click to collapse
I removed the assert line from the updater script and was able to flash it.
But never went beyond Cyanogen mod logo.
ganeshbiyer said:
I removed the assert line from the updater script and was able to flash it.
But never went beyond Cyanogen mod logo.
Click to expand...
Click to collapse
No wonder lol...hahah but u didnt pass to bootanimation right?
Yes ... No Luck ....
Try to follow this thread.
http://forum.xda-developers.com/showthread.php?t=1782771
ganeshbiyer said:
Yes ... No Luck ....
Try to follow this thread.
http://forum.xda-developers.com/showthread.php?t=1782771
Click to expand...
Click to collapse
I followed those thread just now....but i got bootloop....damn i guess they need to rebuild this rom properly....
ganeshbiyer said:
I removed the assert line from the updater script and was able to flash it.
But never went beyond Cyanogen mod logo.
Click to expand...
Click to collapse
have you tried to go on CWM recovery flash the zip file, fix permissions?
yesterday I was having some hard time with flashing a CM10 on a SG2 and the only solution to have it without any problem was to fix permissions after flashing the ROM.
From my understanding, with my experiences with my old x10, you need the ability to flash the fxp kernel. Since we don't have a way to bypass the stock kernel yet, we probably can't use this on a locked bl.
Sent from my LT28at using xda premium
dizarmstrong said:
From my understanding, with my experiences with my old x10, you need the ability to flash the fxp kernel. Since we don't have a way to bypass the stock kernel yet, we probably can't use this on a locked bl.
Sent from my LT28at using xda premium
Click to expand...
Click to collapse
That what im thinking when this rom is not working.....i think its really need custom kernel.....i unlock my bootloader but no custom kernel to be flash
So weird phenomenon started happening yesterday. I was on cm10.1 RC5 and hadn't done anything new to my phone but randomly throughout the day it would just go black and not respond to unlock and basically looked like it was in power off mode. Only way to get it back up is to reboot but then it will freeze in 5 mins to an hour and power off again.
I thought it was a rom issue at first so I flashed to cm10.2 the most stable one right now but it happened again. So I tried to restore to stock and after I fianlly got it to stock on android 4.12 and then when I was setting up the phone it happned again.
One thing though, I booted phone into recovery and kept it on for more than 2 hours without any random shutoffs or freezes which leads me to believe its still a software issue. Any help?
Ftwpker said:
So weird phenomenon started happening yesterday. I was on cm10.1 RC5 and hadn't done anything new to my phone but randomly throughout the day it would just go black and not respond to unlock and basically looked like it was in power off mode. Only way to get it back up is to reboot but then it will freeze in 5 mins to an hour and power off again.
I thought it was a rom issue at first so I flashed to cm10.2 the most stable one right now but it happened again. So I tried to restore to stock and after I fianlly got it to stock on android 4.12 and then when I was setting up the phone it happned again.
One thing though, I booted phone into recovery and kept it on for more than 2 hours without any random shutoffs or freezes which leads me to believe its still a software issue. Any help?
Click to expand...
Click to collapse
How are you wiping the phone? Which recovery are you using? it does sound ROM related, because you say it stays up in recovery. It could be what edfunkycold talked about before, Sudden Death Syndrome
joeyhdownsouth said:
How are you wiping the phone? Which recovery are you using? it does sound ROM related, because you say it stays up in recovery.
Click to expand...
Click to collapse
I'm wiping the phone through TWRP recovery. Cleaned out the cache,data,storage,system, factory reset basically.
Ftwpker said:
I'm wiping the phone through TWRP recovery. Cleaned out the cache,data,storage,system, factory reset basically.
Click to expand...
Click to collapse
When you say storage are you talking about internal or external? You should not wipe internal storage, some of these files are needed for the Operating System. It's not sudden death syndrome.
joeyhdownsouth said:
When you say storage are you talking about internal or external?
Click to expand...
Click to collapse
Its all internal. I only just put in an external sd card to flash the rom from. I flashed the stock using this method: http://forum.xda-developers.com/showthread.php?t=1904099. Don't know if that makes any different then say restoring from another method.
Ftwpker said:
Its all internal. I only just put in an external sd card to flash the rom from. I flashed the stock using this method: http://forum.xda-developers.com/showthread.php?t=1904099. Don't know if that makes any different then say restoring from another method.
Click to expand...
Click to collapse
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
mm shoot I didn't know that. Since its already wiped does that effect anything? I dont think wiping internal created the problem though since it was present before I started flashing to stock.
Ftwpker said:
mm shoot I didn't know that. Since its already wiped does that effect anything? I dont think wiping internal created the problem though since it was present before I started flashing to stock.
Click to expand...
Click to collapse
Before you flashed to stock, were you wiping internal, like when you flashed CM?
joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
joeyhdownsouth said:
Before you flashed to stock, were you wiping internal, like when you flashed CM?
Click to expand...
Click to collapse
Ya i did wipe the internal at least two times when I was flashing different CM roms.
Ftwpker said:
Ya i did wipe the internal at least two times when I was flashing different CM roms.
Click to expand...
Click to collapse
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
joeyhdownsouth said:
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
Click to expand...
Click to collapse
When you flashed billiard's OTA stock, did you keep stock or you flashed custom recovery, and did you keep root? From my understanding, only stock recovery will erase and rewrite internal storage. I would try it again, and do not flash custom recovery or root access. Let the phone boot up without flashing root or custom recovery. If it boots, and doesn't freeze and die for awhile, then proceed with rerooting and installing custom recovery again.
joeyhdownsouth said:
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
Are you saying that is causing the phone to randomly die? Or do you mean its another problem?
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
When you flashed billiard's OTA stock, did you keep stock or you flashed custom recovery, and did you keep root? From my understanding, only stock recovery will erase and rewrite internal storage. I would try it again, and do not flash custom recovery or root access file.
Click to expand...
Click to collapse
I flashed custom recovery because I wasn't sure if I would be able to reflash or go into recovery again if the stock rom didnt work. Also I didn't root either.
Ftwpker said:
I flashed custom recovery because I wasn't sure if I would be able to reflash or go into recovery again if the stock rom didnt work. Also I didn't root either.
Click to expand...
Click to collapse
The only thing I can tell you is to try flashing again, without custom recovery, it should wipe and reformat internal storage for you. I don't think custom recovery allows internal storage to be rewritten. As long as you can get into download mode, you can always use ODIN to reflash stock image, should anything happen and the stock ROM didn't work. If your not familiar with ODIN, you can try mskip's toolbox here.
joeyhdownsouth said:
The only thing I can tell you is to try flashing again, without custom recovery, it should wipe and reformat internal storage for you. I don't think custom recovery allows internal storage to be rewritten. As long as you can get into download mode, you can always use ODIN to reflash stock image, should anything happen and the stock ROM didn't work. If your not familiar with ODIN, you can try mskip's toolbox here.
Click to expand...
Click to collapse
Do you have a link on how to use odin to reflash? Want to have it handy in case I get stuck in a bootloop again.
Ftwpker said:
Do you have a link on how to use odin to reflash? Want to have it handy in case I get stuck in a bootloop again.
Click to expand...
Click to collapse
Try the toolbox I posted above. It will open ODIN and flash the needed files for you. YOU MUST FOLLOW DIRECTIONS VERY CAREFULLY. The thing most people miss when using this toolbox, is make sure your phone's serial number shows up, before trying anything else this toolbox will do.
Or you can watch this video from QBKING77 https://www.youtube.com/watch?v=nHpqK6D3P_Y&feature=youtube_gdata_player
Sent from the future via Tapatalk 4
edfunkycold said:
Or you can watch this video from QBKING77 https://www.youtube.com/watch?v=nHpqK6D3P_Y&feature=youtube_gdata_player
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Totally forgot about this
joeyhdownsouth said:
Totally forgot about this
Click to expand...
Click to collapse
Alright thanks. Will try if needed. Can i install custom recovery if everything woks?
Ftwpker said:
Alright thanks. Will try if needed. Can i install custom recovery if everything woks?
Click to expand...
Click to collapse
Yes, root 1st, then custom recovery. But, to me, the easier way, toolbox will do all these things for you. Let me know how it goes!
joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
Incorrect, nothing that the OS uses gets stored on the internal storage, it all goes to system... It is completely safe to wipe your internal storage when moving between ROMs, I and many others do it with every flash
flastnoles11 said:
Incorrect, nothing important that the OS uses gets stored on the internal storage, it all goes to system... It is completely safe to wipe your internal storage when moving between ROMs, I and many others do it with every flash
Click to expand...
Click to collapse
I fixed your post for you
Hi all. I just got a Verizon Htc One M7. I bought it used and it was already updated to 4.4.2 Kit kat and sense 5.5. I am new to rooting and unlocking and I am running into issues I am hoping someone can help me with. I successfully unlocked, rooted, and got S-off. A am trying to get a custom kernel on the phone so I can have tap to wake and swipe to wake. I installed TWRP recovery 2.7.0.0. Everything appears to be working I boot into bootloader mode and it say unlocked and s-off on top of the screen. I started recovery and it appears to be working fine. I created a backup and that works. So I tried 2 different kernels elementalx and elite lunar. Both appear to install fine but when I reboot the phone gets stuck in a boot loop on the HTC screen. I then have to go back into recovery and revert back to my saved backup. The phone will then boot up fine. Not sure if I'm doing something wrong or what. I am running the stock ROM. Any help will be greatly appreciated.
Forgive and help a noop!!!!
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Reubster24 said:
No one knows? I also just noticed that on the bootloader screen there is no numbers after OS. Which would appear to mean i have no OS. But the phone boots and operates just fine. Any suggestions? Thinking I should get it back to factory and start over and flash the NuSenseSIX rom. If anyone could please help me out here it would be greatly appreciated!!!! I attached a picture of what my bootloader screen looks like.
Click to expand...
Click to collapse
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
synisterwolf said:
it's the rom you are on, if you go back to stock build you will see the OS-build number correctly displayed. if you are on a custom rom, and its not built correctly, it will not display properly.
you dont need to worry about it. all the info in hboot is for diagnostic purpose and wont effect you in any way.
Click to expand...
Click to collapse
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Reubster24 said:
Ok I appreciate the response. I am still on the stock ROM. Just have it rooted, unlocked and s-off with twrp custom recovery installed. Any ideas as to why I'm not able to get it to boot after installing a custom kernel? Can I just try to flash the NuSenseSIX ROM in the phones current state or should I start over?
Click to expand...
Click to collapse
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
ok, here we go.
Flash the attached zip in recovery.
wipe dalvik and cache (2x for good measure)
reboot the phone.
then try to flash a custom kernel and see if you boot loop. Let me know what happens. please have a working backup before trying any of this.
(credit to @buckmarble and @brymaster5000)
kernel source
synisterwolf said:
if you would like to try NuSense i would make sure you have a good backup or do one before. you'll need to wipe system - data - cache - dalvik in twrp and then install the rom.
---------- Post added at 01:36 PM ---------- Previous post was at 01:29 PM ----------
After some discussion with fellow dev's, i think you havent flash the insecure boot.img that allows you to write to /system. this should stop the kernel bootlooping you.
Click to expand...
Click to collapse
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Reubster24 said:
I have everything backed up google drive with titanium backup as well as backed up in TWRP. When I wipe it doesn't remove the TWRP backup right? I have not flashed any boot.img. I am new to this and don't really know what that is. How would I find the boot.img I need. I think I'll just move forward with the NuSense Rom. Can I just download the zip for the NuSense ROM then wipe and flash it using TWRP and I'm good to go or is there other stuff I need to do?
Click to expand...
Click to collapse
the boot.img zip above will allow you to write to the /system part of the phone.
TWRP will not wipe your backup. that is stored in a location its not allowed to wipe unless you do a "factory reset"
flash the zip above first. let it boot then flash NuSense. I'm not to familiar with that rom so i cant for sure say it will have said insecure boot.img.
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Reubster24 said:
Ok I flashed that file and the phone boots up fine. But it has a weird N flashing at the top of the screen now. I'll try a kernel this evening and see what happens. Any idea what the N is? Attached a zipped video of what its doing.
Click to expand...
Click to collapse
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
synisterwolf said:
That icon is for NFC. idk why its flashing but make sure its off if you dont use it.
its under settings.
Click to expand...
Click to collapse
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Reubster24 said:
Ok. It is off in settings. Tried to turn it on and it won't let me. I'll flash a kernel later and see what happens and if it stops doing it. Is there another insecure boot.img I can try?
Click to expand...
Click to collapse
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
synisterwolf said:
only need to do it once. flash any kernel that is meant for your rom or switch roms. you should be good to go.
Click to expand...
Click to collapse
Awesome thanks for all your help. I think I'm gonna flash a Rom. Any suggestions? I would like something close to the stock Rom.
Thank you for all your help!! I successfully installed the NuSense Rom.
Reubster24 said:
Thank you for all your help!! I successfully installed the NuSense Rom.
Click to expand...
Click to collapse
congrats man, you can PM me if you have anymore questions or post in the Q/A thread and i will try to help
:highfive: