Trouble flashing back to stock kernel - HTC One V

I'm selling an HTC One V and I would like to flash the kernel back to stock (it's currently on Titanium).
I've tried the All In One Toolkit kernel flash option, wiped cache and davlik (and even full factory wipe), tried restoring from my CWM nandroid backup.
Restoring always seems to go OK with no errors, but whenever I got to About in phone settings it still shows the kernel as Titanium.
Any ideas?

britbloke said:
I'm selling an HTC One V and I would like to flash the kernel back to stock (it's currently on Titanium).
I've tried the All In One Toolkit kernel flash option, wiped cache and davlik (and even full factory wipe), tried restoring from my CWM nandroid backup.
Restoring always seems to go OK with no errors, but whenever I got to About in phone settings it still shows the kernel as Titanium.
Any ideas?
Click to expand...
Click to collapse
did you relock the bootloader 1st?

Hi
Relock bootloader and use the RUU
Thats IMHO the easiest to get it back to stock
Regards
max

No, I didn't relock the bootloader. I'm a noob at kernel flashing so I didn't realize that I had to do that.
There's no RUU for my Canadian Koodo One V, so I can't revert to stock that way.

britbloke said:
There's no RUU for my Canadian Koodo One V, so I can't revert to stock that way.
Click to expand...
Click to collapse
Sorry - didnt know that
regards
max

britbloke said:
No, I didn't relock the bootloader. I'm a noob at kernel flashing so I didn't realize that I had to do that.
There's no RUU for my Canadian Koodo One V, so I can't revert to stock that way.
Click to expand...
Click to collapse
contact football he might be able to get you the RUU might cost you 11euro's though

Related

Laggy / Slow Note 2 even after stock restore

Hi guys, so I have a problem with my Note II. I installed a rom yesterday which is where these problems seem to start from. The phone is glitchy, and when the screen is left of for more than 2 minites or so, it wont turn on unless I remove the battery. Also, after I re-boot the battery level is normally 10% less than before. Another issue I had is that I couldn't boot into recovery after flashing this rom however I have no fixed this by using Odin to re-flash CWM recovery.img. But even after going back to by stock backup I made in CWM before I flashed this rom, the problem still persistes (Laggy, freezes)
All I can think of is that this Rom (Omega 3.0) uses AROMA to install, could that be a issue?
Any Ideas anyone? Im not worried about any of the files on the device just want to get it sorted!
Thanks
JustArchiee said:
Hi guys, so I have a problem with my Note II. I installed a rom yesterday which is where these problems seem to start from. The phone is glitchy, and when the screen is left of for more than 2 minites or so, it wont turn on unless I remove the battery. Also, after I re-boot the battery level is normally 10% less than before. Another issue I had is that I couldn't boot into recovery after flashing this rom however I have no fixed this by using Odin to re-flash CWM recovery.img. But even after going back to by stock backup I made in CWM before I flashed this rom, the problem still persistes (Laggy, freezes)
All I can think of is that this Rom (Omega 3.0) uses AROMA to install, could that be a issue?
Any Ideas anyone? Im not worried about any of the files on the device just want to get it sorted!
Thanks
Click to expand...
Click to collapse
I think you must ask in Omega's thread. With stock rooted lj1 dont have any of the above
JustArchiee said:
Any Ideas anyone? Im not worried about any of the files on the device just want to get it sorted!
Thanks
Click to expand...
Click to collapse
I recomment a full wipe using Odin...
It will definitely get it sorted... full wipe, then install the stock rom...
No way this wont work :good:
Jamal Ahmed said:
I recomment a full wipe using Odin...
It will definitely get it sorted... full wipe, then install the stock rom...
No way this wont work :good:
Click to expand...
Click to collapse
Ahh okay thanks ... ummm i've come from a Nexus device so I have no experience in Odin. Is it difficult to do?
JustArchiee said:
Ahh okay thanks ... ummm i've come from a Nexus device so I have no experience in Odin. Is it difficult to do?
Click to expand...
Click to collapse
Not at all its as easy as a cupcake
Just know the terms for it
Would you hear a brotherly advice (which i would do myself?)
Use the superwipe script from Android Revolution HD and install mike's ROM. It should have the same effect as odin wipe, only better...
Mike's roms are known to be the best ever. They are totally stock! just extreme perfomance...
So its better thsn going back to stock
Not at all its as easy as a cupcake
Just know the terms for it
Would you hear a brotherly advice (which i would do myself?)
Use the superwipe script from Android Revolution HD and install mike's ROM. It should have the same effect as odin wipe, only better...
Mike's roms are known to be the best ever. They are totally stock! just extreme perfomance...
So its better thsn going back to stock
Click to expand...
Click to collapse
Right okay that sounds like a plan, I dont know if I will be able to keep the phone on long enough to download all thta and as I cant connect it to the computer unless its in download mode :/ I could give it a go though, could you post a link to what I need please? Yes, im a complete noob
Put the ROM of your choice on internal sdcard (I also put the same zip on the external just in case something goes wrong)
Make the appropriate backups of apps, data, contacts, sms, pictures and whatnot.
Reboot into recovery and do a full wipe, explained here: http://forum.xda-developers.com/showthread.php?t=1909868
Flash ze ROM.
Edit: In CWM, this is how I do a full wipe.
Format system
Format data
Format cache
Format preload
Wipe data/factory reset
Wipe cache
Wipe dalvik cache
Sometimes I also do the "fix permissions" at this point.
Then I flash the ROM.
Sent from my GT-N7100 using xda premium
Kiahnlliya said:
Put the ROM of your choice on internal sdcard (I also put the same zip on the external just in case something goes wrong)
Make the appropriate backups of apps, data, contacts, sms, pictures and whatnot.
Reboot into recovery and do a full wipe, explained here: http://forum.xda-developers.com/showthread.php?t=1909868
Flash ze ROM.
Edit: In CWM, this is how I do a full wipe.
Format system
Format data
Format cache
Format preload
Wipe data/factory reset
Wipe cache
Wipe dalvik cache
Sometimes I also do the "fix permissions" at this point.
Then I flash the ROM.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Well that was my initial thought, im just trying to download a rom before the phone freezes. Thanks
The revolutiom HD ROM i was talking about is here
http://forum.xda-developers.com/showthread.php?t=1925402
You can find the superwipe script from this forum too...
But be sure to put your downloaded rom on SD card, not internal SD...
Well thats my way which i told you you have two choices...you can follow the one of the boy above to see if it helps too?
Jamal Ahmed said:
The revolutiom HD ROM i was talking about is here
http://forum.xda-developers.com/showthread.php?t=1925402
You can find the superwipe script from this forum too...
But be sure to put your downloaded rom on SD card, not internal SD...
Well thats my way which i told you you have two choices...you can follow the one of the boy above to see if it helps too?
Click to expand...
Click to collapse
Ahh more problems, I dont have a SD card, as in not one that can be removed. Is that a issue?
Jamal Ahmed said:
The revolutiom HD ROM i was talking about is here
http://forum.xda-developers.com/showthread.php?t=1925402
You can find the superwipe script from this forum too...
But be sure to put your downloaded rom on SD card, not internal SD...
Well thats my way which i told you you have two choices...you can follow the one of the boy above to see if it helps too?
Click to expand...
Click to collapse
Still the same problem! Maybe not quite as bad but still there. Locked the screen and then was unable to turn it back on again with out removing the battery. Like, what? :S
JustArchiee said:
Still the same problem! Maybe not quite as bad but still there. Locked the screen and then was unable to turn it back on again with out removing the battery. Like, what? :S
Click to expand...
Click to collapse
Hmmm....that seems to be a prob!
Because superwipe wipes anyyyything! On the phone. Anything.
It couldnt be sofrware issue...
Try to go back up on stock rom, restore your EFS (if you backed it up!) and claim warranty? there must be a solution with sammy for this...
This isnt normal... you can try :good:
I think thats what im gonna have to do I did try superwipe and still nothing. Is there a easy way to go back to stock? Using odin? Will I have to delete CWM for this? :S
JustArchiee said:
I think thats what im gonna have to do I did try superwipe and still nothing. Is there a easy way to go back to stock? Using odin? Will I have to delete CWM for this? :S
Click to expand...
Click to collapse
Yes yes deleting CWM is important for that.
And i just found the backup/restore EFS tool for you http://forum.xda-developers.com/showthread.php?t=1922473
Yup you have to go to stock using ODIN...
Try to flash ALIH? I dunno...i thinkthat would be better and less suspicious
Jamal Ahmed said:
Yes yes deleting CWM is important for that.
And i just found the backup/restore EFS tool for you http://forum.xda-developers.com/showthread.php?t=1922473
Yup you have to go to stock using ODIN...
Try to flash ALIH? I dunno...i thinkthat would be better and less suspicious
Click to expand...
Click to collapse
So restoring EFS will erase CWM is that correct? And then find a stock rom to flash yeah?
JustArchiee said:
So restoring EFS will erase CWM is that correct? And then find a stock rom to flash yeah?
Click to expand...
Click to collapse
Im not so sure about that...
But atleast stock rom should?
Atleast first flash stock rom from sammobile.com (not the rooted ones here)... And then restore EFS...
Then apply check: try to start cwm recovery :good:
Jamal Ahmed said:
Im not so sure about that...
But atleast stock rom should?
Atleast first flash stock rom from sammobile.com (not the rooted ones here)... And then restore EFS...
Then apply check: try to start cwm recovery :good:
Click to expand...
Click to collapse
Why restoring EFS?? Also i dont think that restoring EFS is ging to erase cwm
Stock roms from sammobile (full roms) include recovery.img, so after flashing with Odin he is going to have stock recovery.After that through stock recovery, wipe cache+wipe data/factory reset.
And before visiting repair center, flash stock rom from sammobile and check your phone if problem is still there. I think that somehow with the custom rom and restoring cwm backup you f***ed up software
afilopou said:
Why restoring EFS?? Also i dont think that restoring EFS is ging to erase cwm
Stock roms from sammobile (full roms) include recovery.img, so after flashing with Odin he is going to have stock recovery.After that through stock recovery, wipe cache+wipe data/factory reset.
Click to expand...
Click to collapse
Restoring EFS because he is going to give his Note in warranty...
Until you backup and restore your original EFS, samsung keeps the track of the number of times you flash so it does not accept warranty.
Restoring EFS is the only chance to claim warranty.
restoring EFS doesnt remove recovery.. hmmm...
Is there any way to remove recovery?
Jamal Ahmed said:
Restoring EFS because he is going to give his Note in warranty...
Until you backup and restore your original EFS, samsung keeps the track of the number of times you flash so it does not accept warranty.
Restoring EFS is the only chance to claim warranty.
restoring EFS doesnt remove recovery.. hmmm...
Is there any way to remove recovery?
Click to expand...
Click to collapse
In order to remove cwm recovery, just flash a full stock rom with pc odin
Are you sure about warranty and EFS? In order to backup/restore original EFS you need root, so one way or another you need to flash one or more times
Are you 100% sure?
Jamal Ahmed said:
Im not so sure about that...
But atleast stock rom should?
Atleast first flash stock rom from sammobile.com (not the rooted ones here)... And then restore EFS...
Then apply check: try to start cwm recovery :good:
Click to expand...
Click to collapse
Right thats done. I rung them (3 UK) and they said they can just exchange it for a new one ... might be cheeky and ask for the grey model ... so its all good. Thanks for your help anyway mate really appreciate it

Rooted, no LTE / Insanely slow signal

exactly as title states.
S-offed, rooted, flashed a ROM, now I'm having trouble getting connected to VZW 4g...
EDIT - I'm restoring to my base stock nandroid. everything is force closing (GP store, everything). Dont really know what to do right now...
crazyg0od33 said:
exactly as title states.
S-offed, rooted, flashed a ROM, now I'm having trouble getting connected to VZW 4g...
EDIT - I'm restoring to my base stock nandroid. everything is force closing (GP store, everything). Dont really know what to do right now...
Click to expand...
Click to collapse
Flash a new ROM clean. Hey at least you got past soff finally. Good chance your nandroid is corrupt. Just download a new ROM and flash it. Perhaps a bad download on the other one or perhaps you have an outage near you.
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
Flash a new ROM clean. Hey at least you got past soff finally. Good chance your nandroid is corrupt. Just download a new ROM and flash it. Perhaps a bad download on the other one or perhaps you have an outage near you.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
my nandroid is fine - immediately loaded up 4g no problem. I'm now on the GPE and it's working better. may have been a bad install. May flash to an AOSP tomorrow though since it's got more customization than the GPE rom...
crazyg0od33 said:
my nandroid is fine - immediately loaded up 4g no problem. I'm now on the GPE and it's working better. may have been a bad install. May flash to an AOSP tomorrow though since it's got more customization than the GPE rom...
Click to expand...
Click to collapse
That's good to hear. Hopefully the rest of those having issues get them worked out.
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
That's good to hear. Hopefully the rest of those having issues get them worked out.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
yeah I'm flashing LiquidSmooth right now, best I've tried so far (havent tried CM 10.2 yet, may do that next) but We'll see if this one runs better for me now
crazyg0od33 said:
exactly as title states.
S-offed, rooted, flashed a ROM, now I'm having trouble getting connected to VZW 4g...
EDIT - I'm restoring to my base stock nandroid. everything is force closing (GP store, everything). Dont really know what to do right now...
Click to expand...
Click to collapse
I am having the exact same problem, except i dont have a nandroid of Stock ROM because a i bought the phone with everything done, and no nandroid of the stock system.
I am currently on a Stock rom (http://forum.xda-developers.com/showthread.php?t=2485319)
Deodexed and debloated.
But i have tried every ROM out there for the Verizon model.
Im upset about it, cuz i was so excited to get off the Gnex and on to something new,
but no 4G just sucks :\
Can someone please help?
Thanks
collinjm01 said:
I am having the exact same problem, except i dont have a nandroid of Stock ROM because a i bought the phone with everything done, and no nandroid of the stock system.
I am currently on a Stock rom (http://forum.xda-developers.com/showthread.php?t=2485319)
Deodexed and debloated.
But i have tried every ROM out there for the Verizon model.
Im upset about it, cuz i was so excited to get off the Gnex and on to something new,
but no 4G just sucks :\
Can someone please help?
Thanks
Click to expand...
Click to collapse
flash back to a sense rom, it should reset the LTE signal (did for me) and then flash another AOSP if you want an AOSP rom
crazyg0od33 said:
flash back to a sense rom, it should reset the LTE signal (did for me) and then flash another AOSP if you want an AOSP rom
Click to expand...
Click to collapse
I am on stock rom, no LTE still
I am on Vzw :\
I have run into this problem before going from sense to AOSP on the One, the Rezound also suffered from this. I have done this multiple times for both devices with 100% success, unfortunately a full wipe is required.
-Change your custom recovery to the stock recovery
-Factory reset from H-Boot, I usually do this twice
-This at least for me clears up data issues, and for some reason only factory reset from H-Boot seems to work. Custom recoveries do not clear the affected radio caches
lancasterv3 said:
I have run into this problem before going from sense to AOSP on the One, the Rezound also suffered from this. I have done this multiple times for both devices with 100% success, unfortunately a full wipe is required.
-Change your custom recovery to the stock recovery
-Factory reset from H-Boot, I usually do this twice
-This at least for me clears up data issues, and for some reason only factory reset from H-Boot seems to work. Custom recoveries do not clear the affected radio caches
Click to expand...
Click to collapse
Thats what i am unsure of, I dont know how to do this.
I have flashed a Radio RUU and custom roms on recovery on
this phone. But the phone already had all this done.
Pointing me in the right direction would be Super helpful
Thanks
collinjm01 said:
Thats what i am unsure of, I dont know how to do this.
I have flashed a Radio RUU and custom roms on recovery on
this phone. But the phone already had all this done.
Pointing me in the right direction would be Super helpful
Thanks
Click to expand...
Click to collapse
The radio RUU is just that only the Radio's, if you have received this handset with most of the work done (S-Off) I would assume it had not been factory reset from Hboot after doing this. I had read that the S-Off process could affect data and it was good practice to factory reset from Hboot after completing S-Off. All that being said I have always been on a Sense ROM when doing this, as a warning back up anything you cherish...... for this wipes **INTERNAL STORAGE!!**
Go to Zarboz's decrypted RUU
http://forum.xda-developers.com/showthread.php?t=2437436
-Download either .08 or the .10 DECRYPTED RUU
-Unzip it and find the recovery signed.img file
-Replace your custom recovery (CWM, TWRP) with the above recovery.
-Go to Settings>Power> Deselect the fast-boot option.
-Reboot into HBoot
-Select Factory Reset from the options
-Let it do its thing, when the One boots up do not worry about setting up accounts or anything because you are going to boot back into HBoot and do another factory reset, again uncheck fast-boot. I know this seems like overkill but considering you have already gone through all of this why not just wipe it again for good measure.
-Once all of this is done push your custom recovery
-Flash away and enjoy.
-Now this method will not help if you have fried your SIM card by doing a tower update (*228).
lancasterv3 said:
The radio RUU is just that only the Radio's, if you have received this handset with most of the work done (S-Off) I would assume it had not been factory reset from Hboot after doing this. I had read that the S-Off process could affect data and it was good practice to factory reset from Hboot after completing S-Off. All that being said I have always been on a Sense ROM when doing this, as a warning back up anything you cherish...... for this wipes **INTERNAL STORAGE!!**
Go to Zarboz's decrypted RUU
http://forum.xda-developers.com/showthread.php?t=2437436
-Download either .08 or the .10 DECRYPTED RUU
-Unzip it and find the recovery signed.img file
-Replace your custom recovery (CWM, TWRP) with the above recovery.
-Go to Settings>Power> Deselect the fast-boot option.
-Reboot into HBoot
-Select Factory Reset from the options
-Let it do its thing, when the One boots up do not worry about setting up accounts or anything because you are going to boot back into HBoot and do another factory reset, again uncheck fast-boot. I know this seems like overkill but considering you have already gone through all of this why not just wipe it again for good measure.
-Once all of this is done push your custom recovery
-Flash away and enjoy.
-Now this method will not help if you have fried your SIM card by doing a tower update (*228).
Click to expand...
Click to collapse
Dude you are freaking amazing!!!
Funny thing, i used Flashify to to flash the img
file and rebooted the system, it showed
a phone with a loading bar, it did its thing,
then rebooted, went into the OS and 4G
is working!
Thank you so much man!
Flashify eliminates pushing ,a great tool. If you have Flashify and also Meenova SD card reader you never have to mess with adb and fastboot again. Two great tools.
sent from my HTC One
collinjm01 said:
Dude you are freaking amazing!!!
Funny thing, i used Flashify to to flash the img
file and rebooted the system, it showed
a phone with a loading bar, it did its thing,
then rebooted, went into the OS and 4G
is working!
Thank you so much man!
Click to expand...
Click to collapse
no problem i am glad this took care of it for you.
Sent from my HTC6500LVW using Tapatalk
jbh00jh said:
Flashify eliminates pushing ,a great tool. If you have Flashify and also Meenova SD card reader you never have to mess with adv and fastboot again. Two great tools.
sent from my HTC One
Click to expand...
Click to collapse
I used flashify for it, I love that app
Sent from my HTC6500LVW using xda app-developers app

[Q] Will OTA return to S-ON and relock bootloader?

My M7 had quite the meltdown yesterday, highlighted by what seems to be a corruption of my cache partition. Long, long story short, I was able to use the ruu to 2.10.605, where everything seemed fine. Funny enough, I kept s-off and an unlocked bootloader through the process.
I was content to keep the phone as is, since my f'ing with it surely caused the cache issue. But, to be safe, I rerooted, installed CWM (TWRP will not install for me, despite a dozen efforts), and backed up. Then, to see if the problem had been solved, I tried to wipe cache, but no dice. I won't be installing original ROMs anymore, it seeems. Not a huge deal since I at least have a functional phone, but now it has downloaded 4.4 and wants to update. A couple of questions:
Should I assume that the update will likely run into cache-related issues?
Will the update relock the bootloader and/or return the phone to S-on?
If either of these is a yes, I'm thinking about using the 2.10 ruu again, returning everything as was, and then installing santod's OTA killer. I can live with 4.3 on this phone for another year - not ideal, but considering the alternatives...
Thanks in advance to anyone who might have an idea about all this.
dmdubois said:
My M7 had quite the meltdown yesterday, highlighted by what seems to be a corruption of my cache partition. Long, long story short, I was able to use the ruu to 2.10.605, where everything seemed fine. Funny enough, I kept s-off and an unlocked bootloader through the process.
I was content to keep the phone as is, since my f'ing with it surely caused the cache issue. But, to be safe, I rerooted, installed CWM (TWRP will not install for me, despite a dozen efforts), and backed up. Then, to see if the problem had been solved, I tried to wipe cache, but no dice. I won't be installing original ROMs anymore, it seeems. Not a huge deal since I at least have a functional phone, but now it has downloaded 4.4 and wants to update. A couple of questions:
Should I assume that the update will likely run into cache-related issues?
Will the update relock the bootloader and/or return the phone to S-on?
If either of these is a yes, I'm thinking about using the 2.10 ruu again, returning everything as was, and then installing santod's OTA killer. I can live with 4.3 on this phone for another year - not ideal, but considering the alternatives...
Thanks in advance to anyone who might have an idea about all this.
Click to expand...
Click to collapse
Question for you...
Where did you get your Recoveries from that you installed or tried to install?
Did you grab the versions for the m7vzw in our Verizon HTC One Original Development section?
Or did you install one intended for the International m7?
santod040 said:
Question for you...
Where did you get your Recoveries from that you installed or tried to install?
Did you grab the versions for the m7vzw in our Verizon HTC One Original Development section?
Or did you install one intended for the International m7?
Click to expand...
Click to collapse
Yes, I got them from this site, under that section. I just installed Phil's CWM, which booted, and allowed me to clear the cache (!), but now I can't install a rom. I tried your NuSense Max and your odexed 4.42....in both cases I got a status 7 error. (Before I tried either one, I updated the firmware, fyi.)
Fortunately Phil's CWM backup process is simpler and faster. Unless there are other suggestions, I think I'll tried flashing your OTA killer and live with 4.3
Thanks again.
dmdubois said:
Yes, I got them from this site, under that section. I just installed Phil's CWM, which booted, and allowed me to clear the cache (!), but now I can't install a rom. I tried your NuSense Max and your odexed 4.42....in both cases I got a status 7 error. (Before I tried either one, I updated the firmware, fyi.)
Fortunately Phil's CWM backup process is simpler and faster. Unless there are other suggestions, I think I'll tried flashing your OTA killer and live with 4.3
Thanks again.
Click to expand...
Click to collapse
Twrp 2.6.3.3 or 2.6.3.4 will install those Roms.
You can always do fastboot erase cache
That will clear the cache.
Until a newly installed recovery has booted into the OS once, it usually won't clear cache.
Sent from my HTC6435LVW using Tapatalk
santod040 said:
Twrp 2.6.3.3 or 2.6.3.4 will install those Roms.
You can always do fastboot erase cache
That will clear the cache.
Until a newly installed recovery has booted into the OS once, it usually won't clear cache.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
It worked.
I don't know what in the hell I've been doing (I swear that's the same TWRP file I've been using) but, just like that, it booted, and successfully installed your NuSense Max Rom. No more 4.3, no cache issues, no more worry about OTAs. You're the man!
Thanks a million.

Can't install 3.28.401.6 OTA

I have a SIM free M8 running stock 2.22.401.5 (inc recovery) but S-Off.
Got the OTA notification and selected to install it. It reboots to stock recovery but after a few seconds when the green progress bar is about a 1/3 full, it stops and a red warning triangle appears.
After a couple more minutes the phone reboots and is still on the old version. Tried again but the same result.
Any advice would be warmly welcomed.
Any errors messages?
HTC One M8
Elisha said:
Any errors messages?
HTC One M8
Click to expand...
Click to collapse
None at all.
I dont believe it matters as the last OTA was successful, but I am also superCID and bootloader unlocked.
I've also just wiped the cache partition using stock recovery but still no dice.
Did you installed any system mods? Like H/K sound mod or custom kernel?
K-a-M-u-Z-u said:
Did you installed any system mods? Like H/K sound mod or custom kernel?
Click to expand...
Click to collapse
No. I haven't even rooted since the previous ota.
stuart0001 said:
No. I haven't even rooted since the previous ota.
Click to expand...
Click to collapse
maybe a stupid question, but do you have enough free space on the device?
K-a-M-u-Z-u said:
maybe a stupid question, but do you have enough free space on the device?
Click to expand...
Click to collapse
Yep, 6GB of internal free.
I feel a factory reset impending.
stuart0001 said:
Yep, 6GB of internal free.
I feel a factory reset impending.
Click to expand...
Click to collapse
If you are going to do a factory reset, you can save all your data easily.
you can flash TWRP recovery, make a backup of DATA partition, Wipe factory reset and reflash Stock recovery, apply the OTA.re flash TWRP recovery again and Restore only DATA partition backup.after that you can revert back to stock recovery if that your wish.
this way you will have all you user data with a clean SYSTEM partition without having to install and reconfigure all your system from scratch.
K-a-M-u-Z-u said:
If you are going to do a factory reset, you can save all your data easily.
you can flash TWRP recovery, make a backup of DATA partition, Wipe factory reset and reflash Stock recovery, apply the OTA.re flash TWRP recovery again and Restore only DATA partition backup.after that you can revert back to stock recovery if that your wish.
this way you will have all you user data with a clean SYSTEM partition without having to install and reconfigure all your system from scratch.
Click to expand...
Click to collapse
That's great advice Thank you. [emoji106]
I'm still getting the same issue after a factory reset. Any ideas?
Do I need to relock my bootloader?
stuart0001 said:
I'm still getting the same issue after a factory reset. Any ideas?
Do I need to relock my bootloader?
Click to expand...
Click to collapse
Your phone is not rooted?
Edit: I read the previous posts and i think is because u have SuperCID, i think u must have your original CID.
same here.. i also flashed the 3.xx update. im on s-off, supercid and my custom rom was viperone 2.5... when i was flashing the update, error 24 appeared. im already on supercid so i wonder why would it fail. so i reflashed the previous firmware which is 2.22.401.5.. it went well but then when im alrady on my homescreen, i notice that i don't have a signal from my mobile network and after a few minutes the phone restarts. could you help me?
I'm officially a dumbass. I managed to open the stock recovery right after it failed and saw the issue. It said.
platform.xml unexpected content
This was from when I applied a previous SD card write fix patch.
After reflaahing a stock ROM it updated fine.
A couple of things puzzle me though. Why did the system restore not revert this file to original and why did the last OTA go through ok when I'd had the patch installed prior to that also.

[Q] Question about mk2 bootloader? Can I flash any aosp rom?

Recently tried several times to flash cm or other aosp roms. Always get stuck on boot screen. Only roms that boot are tw based. So are aosp roms not possible on my locked bootloader? Is my bootloader locked lol?
Did you do a full wipe before you flashed?
Full wipe / factory reset.
Only way to go from TW to cm.
Pp.
Yes. Using twrp. Used the standard wipe method. Also tried wiping caches and the system. Ive even formatted my system. Still always stuck on boot screen. It is the CM boot screen however.
PanchoPlanet said:
Full wipe / factory reset.
Only way to go from TW to cm.
Pp.
Click to expand...
Click to collapse
So it is possible to go to a CM rom even with the MK2 bootloader. Can anyone confirm this?
Take a look at this,
Galaxy S4 How To Install CyanogenMod 11 CM 11 Kit…: http://youtu.be/gUhlLgMA-cA
Pp.
Looks like only TW roms for me.......Thanks everybody.
Cm isn't as bad on a device that doesn't need to be super reliable, like my phone, I need it to be on point at all times having a disabled child in school and never knowing when the school may call for whatever reason. I do run it on my Gal Tab 2 and it runs great, no issues and great battery life.
Pp.
Alex1212 said:
So it is possible to go to a CM rom even with the MK2 bootloader. Can anyone confirm this?
Click to expand...
Click to collapse
I have a T-Mobile S4 with MK2 and I've been running CM since I bought it.
Sent from my SGH-M919 using XDA Free mobile app
Seriously? Weird. Are u sure its not your modem thats mk2?
Alex1212 said:
Seriously? Weird. Are u sure its not your modem thats mk2?
Click to expand...
Click to collapse
Bootloader or modem doesn't make a difference, even with NH7 bootloader you should be able to flash any rom
Now I'm confused...So then what's the big deal about locked/unlocked bootloaders? Any idea why aosp roms won't boot on my phone? I'm fairly positive I've done every wipe and my twrp is the most recent one....thanks in advance
Alex1212 said:
Now I'm confused...So then what's the big deal about locked/unlocked bootloaders? Any idea why aosp roms won't boot on my phone? I'm fairly positive I've done every wipe and my twrp is the most recent one....thanks in advance
Click to expand...
Click to collapse
We don't have locked bootloaders.. Don't know, try different kernel after you flash or another recovery like cwm or philz
I thought they locked them with the mk2 bootloader when they added knox. Ill try again ive tried flashing kt kernel after flashing rom and gapps(made sure it wasnt the tw version). Ill try with cwm recovery. Thanks for trying to help. Ill make a backup of my current rom and try again.
Alex1212 said:
I thought they locked them with the mk2 bootloader when they added knox. Ill try again ive tried flashing kt kernel after flashing rom and gapps(made sure it wasnt the tw version). Ill try with cwm recovery. Thanks for trying to help. Ill make a backup of my current rom and try again.
Click to expand...
Click to collapse
If they were locked you wouldn't have been able to flash a custom recovery
Locked bootloaders are seen on the Verizon and att varients of the S4 , that's where safestrap comes into play. Locked means you can't flash a recovery/custom Roms etc. T-Mobile comes with unlocked BL allowing us to customize our phones. NH7 doesn't allow to you to downgrade BL's, not the same as locked BL. Its a Knox thing, and that only messes with warranty.
Pp. ?
Tried flashing liquidsmooth last night and again stuck at boot screen. Wiped phone flashed rom then gapps. Also tried wipe rom, gapps, kt kernel. Waited 30 minutes then just went back to backup. Thanks for clearing this up guys. Any suggestions?
Alex1212 said:
Tried flashing liquidsmooth last night and again stuck at boot screen. Wiped phone flashed rom then gapps. Also tried wipe rom, gapps, kt kernel. Waited 30 minutes then just went back to backup. Thanks for clearing this up guys. Any suggestions?
Click to expand...
Click to collapse
Can you state exactly what you wipe?
In twrp I use the standard wipe. I forget what it's called but it's the top right button. Brings you to a screen that says that this is all u need to wipe for flashing a new rom. I think it's basically a factory reset. In addition to that I go in advanced wipe and do both caches. I've also even tried wiping system and a few times I've even formatted my data which I think deletes absolutely everything. I tried using Odin to go back to complete stock and re root then Odin twrp. Still sits at boot screen unless I flash a tw style rom...... I'm starting to think it might not even be worth it anymore, not even sure what I'm missing out on honestly. It's just really bugging me that aosp roms won't boot.
That is rather odd, they boot.. Only other thing to try is to flash a different kernel or switch recovery to cwm or philz

Categories

Resources