Related
Hi,
if i am on CM9 and i want to restore a back up of a sense rom, will i then have to flash the corresponding fastboot.img again or will that be restored automatically?
/regards
Sent from my HTC One X using xda premium
Hapsnykel said:
Hi,
if i am on CM9 and i want to restore a back up of a sense rom, will i then have to flash the corresponding fastboot.img again or will that be restored automatically?
/regards
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
if you already have the backup then the answer is no..you do not need to flash the corresponding boot.img restored many times my custom rom which is based on sense and never needed to flash a boot.img
Wrong.
You need to flash the correct boot.img for the ROM you are using. It isn't flashed in a nandroid restore.
nobnut said:
Wrong.
You need to flash the correct boot.img for the ROM you are using. It isn't flashed in a nandroid restore.
Click to expand...
Click to collapse
then how comes i never had any problem then..flashed from Leedroid back to my old Ivysaur which i restored and did not needed to flash the boot.img
I don't know and don't really care
I didn't say it wouldn't work. I said that they should match. If the ROM chef provides a specific boot.img, you should use it... otherwise flash the stock boot.img.
Plus you have overlooked the part about nandroid being unable to flash a boot.img.
nobnut said:
I don't know and don't really care
I didn't say it wouldn't work. I said that they should match. If the ROM chef provides a specific boot.img, you should use it... otherwise flash the stock boot.img.
Click to expand...
Click to collapse
then the best thing for the OP is to try himself and he can tells us then. and always the happy delight that you are i see..and i go by what i know and tried. i restore my backup and never once had to flash a boot.img afterwards.
Those words make no sense. Maybe you could rearrange the order.
Anyway, I'm done here.
nobnut said:
Those words make no sense. Maybe you could rearrange the order.
Anyway, I'm done here.
Click to expand...
Click to collapse
Adios...Nice to see we have some happy campers here today
---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------
and it is simple. he can restore his backup sense rom he has. now if he restores it and it does not bootloop then we have a winner. if he faces bootloops then he goes to thread of the rom he restored he gets the boot.img stick the phone in bootloader turn on the fastboot usb mode and flash the boot.img and job done. Nice to see we have some real happy people today here.
Tried restoring, ended up in loops - downloaded the corresponding boot.img and applied it through fastboot.
Thanks for your help.
Hapsnykel said:
Tried restoring, ended up in loops - downloaded the corresponding boot.img and applied it through fastboot.
Thanks for your help.
Click to expand...
Click to collapse
i must have a super smart phone honestly i restored a nandroid and did not had to restore the boot.img hence why i advised that in the start..anyways it was two ways and you sorted it...glad to have helped..not like some
Hapsnykel said:
Hi,
if i am on CM9 and i want to restore a back up of a sense rom, will i then have to flash the corresponding fastboot.img again or will that be restored automatically?
/regards
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, you will need to. Unless you're S-OFF, recovery can't write to the boot partition. Which means when you restore your backup your boot.img won't be restored. And a Sense ROM with a cm9 kernel/ramdisk most definitely will not work. Your nandroid backup folder will contain a boot.img, you can just flash that via fastboot when you've restored the ROM.
Goku80 said:
then how comes i never had any problem then..flashed from Leedroid back to my old Ivysaur which i restored and did not needed to flash the boot.img
Click to expand...
Click to collapse
Because all of the Sense ROMs on here at the minute are all modifications of the same base, so unless the dev has done something drastic to their boot.img you shouldn't see too many problems using one with a different ROM (although you'll miss out on any tweaks specific to that ROM). So when you restored your Ivysaur, you've been using it with Leedroid's boot.img - potentially missing out on anything that Ivysaur has in the ramdisk which Leedroid doesn't, but that probably isn't enough to cause bootloops or other major issues. You need to manually restore the boot.img from the backup you made in order to use the ROM as it was intended.
Everyone happy?
nobnut said:
Those words make no sense. Maybe you could rearrange the order.
Anyway, I'm done here.
Click to expand...
Click to collapse
Did someone set fire to your Tampon? Cos' you seem a little grumpy..
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.
Hi, I recently did a nandriod restore to go back to stock to get the 4.4.3 update, however, not only am I not getting the update despite being CID_001 I have god duplicated shortcuts in my dropdown shortcut box and my phone no longer recognises my sim card number, for my contact card, the phone works fine in all other ways.
is there anything I can do to fix this.
is it possible with a custom recovery to wipe the phone blank and then reinstall the nandriod back up rather than trying to restore over the old one?
Before you restore anything you always have to do the factors reset through custom recovery!!! And yes it is possible you can see it directly if you boot into the recovery...ALWAYS if you restore do the factory reset/ wipe cache, data, system and dalvik cache!
One-M8-Master said:
Before you restore anything you always have to do the factors reset through custom recovery!!! And yes it is possible you can see it directly if you boot into the recovery...ALWAYS if you restore do the factory reset/ wipe cache, data, system and dalvik cache!
Click to expand...
Click to collapse
using philz touch, can see factory restore, done, wipe cache, done,
I can see another option which is delete content for new rom install, I dont need to do this if I am restoring a back up as this isnt a rom correct?
thanks for the prompt reply
That's enough
One-M8-Master said:
That's enough
Click to expand...
Click to collapse
just tried it, same issue
wonder if its the back up thats faulty
conan_troutman said:
just tried it, same issue
wonder if its the back up thats faulty
Click to expand...
Click to collapse
You can also install a full stock Rom to get the ota as long as you install back the needed stock recovery
One-M8-Master said:
You can also install a full stock Rom to get the ota as long as you install back the needed stock recovery
Click to expand...
Click to collapse
im just researching that at the minute, never done it before so a bit nervous... but I have two zip files one seems to contain the full odexed rom the other appears to be a firmware update same software number on the files but they arent the ones I have installed so I am worried i have the wrong ones
If you have the 2.22.401.3/4 firmware you can flash it and as long as you have the stock Rom 2.22.401.4 it will all work
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
Firmware will be flashed if you boot into fastboot and while phone is connected to pc open a command window in the location where the fastboot files are and type in fastboot oem rebootRUU
You also need to put the firmware.zip in that location but be sure some firmware.zip also wipes the internal storage, so please just look into the zip and please let me know which files are inside so I can say if it wipes the internal storage...it will also do it only if your phone is still s-on
One-M8-Master said:
If you have the 2.22.401.3/4 firmware you can flash it and as long as you have the stock Rom 2.22.401.4 it will all work
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
Firmware will be flashed if you boot into fastboot and while phone is connected to pc open a command window in the location where the fastboot files are and type in fastboot oem rebootRUU
You also need to put the firmware.zip in that location but be sure some firmware.zip also wipes the internal storage, so please just look into the zip and please let me know which files are inside so I can say if it wipes the internal storage...it will also do it only if your phone is still s-on
Click to expand...
Click to collapse
i think my firmware is 1.54.401.10
I have the rom for 2.22.401.4 as zip
but I am not confident that how to flash that rom over my existing rom...
I think I can fastboot (fastboot boot Trecovery.img) into pilz touch, clear the phone for rom install and then install the zip using the custom recovery....???
the recovery for 2.22.401.4 is already flashed
conan_troutman said:
i think my firmware is 1.54.401.10
I have the rom for 2.22.401.4 as zip
but I am not confident that how to flash that rom over my existing rom...
I think I can fastboot (fastboot boot Trecovery.img) into pilz touch, clear the phone for rom install and then install the zip using the custom recovery....???
the recovery for 2.22.401.4 is already flashed
Click to expand...
Click to collapse
You flash the Rom like all others, just do the factory reset there, flash the stock Rom and yea it should be fine, but it's better if you flash the 1.54.401.10 stock Rom, otherwise updates won't work if you use a Rom which needs a newer firmware are flashed on a device with older firmware...therefore either take the older stock Rom or take the stock 2.22.401.3/4 firmware.zip and flash it too but then you don't need to use stock recovery as you are then on latest base and you can flash then mods too as it will be annoying to always use the command to boot the recovery always if you want to flash anything
when I do "fastboot oem rebootRUU"
I see a grey HTC logo
I then do "fastboot flash firmware.zip" I get an error unknown partition firmware.zip
should this be "fastboot flash zip firmware.zip"?
So I have succesfully installed the new rom , and flashed the fitting firmware, but the problem is still there, when I pull down the notification bar and switch to quick settings, then edit settings i am still seing multiple duplicates of the shortcuts, and in setting about where it pulls my phone number from the sim card it still reports my number to be 000000000000 this is all very strange in deed
did a full system scrub twice and a new rom install and a factory reset...
guess I will have to live with it
conan_troutman said:
So I have succesfully installed the new rom , and flashed the fitting firmware, but the problem is still there, when I pull down the notification bar and switch to quick settings, then edit settings i am still seing multiple duplicates of the shortcuts, and in setting about where it pulls my phone number from the sim card it still reports my number to be 000000000000 this is all very strange in deed
did a full system scrub twice and a new rom install and a factory reset...
guess I will have to live with it
Click to expand...
Click to collapse
That are problems where I really can't help now...for phone number the SIM card could be bad . Can you call someone so mobile network etc all is fine?
One-M8-Master said:
That are problems where I really can't help now...for phone number the SIM card could be bad . Can you call someone so mobile network etc all is fine?
Click to expand...
Click to collapse
everything technically works, phone emails sms the lot, one you set the 12 choices in quick menu you dont worry about the duplicates as you dont see them ever again unless you go to edit it.
its just I am a bit anally retentive about every thing being as it should be and not working despite the hicups
It would be really better to post screenshots of it xD
Please see attached:
first three are the quick menu options
the last is my phone number store option which effects things like contact card, and adding my number directly into apps like facebook and whatsapp
Anyone knows the solution to this multiple same things in quick settings?
CrazyCypher said:
Anyone knows the solution to this multiple same things in quick settings?
Click to expand...
Click to collapse
after a lot of messing around, and resetting, I think I know the cause.
I will test for definite in about 8 hours when I get home, I believe its when you use htc back up and restore to restore setting after a factory reset.
I will be looking at putting developer ROM back on when I get home as today it rebooted and deleted system apps associated with rooting such as flash light
I find this odd considering I did not root this rom
Hey guys, hope someone can help me. A few days ago i've flashed the new android m gpe rom and everything was fine. Then somehow i lost root access and tried to fix it. Unfortunately, i'm not even able to flash the fixed rom that was posted a few days later, so i decided to come back to the skydragon sense rom. And for some reason i can't. I try to flash the .zip, it opens in aroma installer, everything goes fine until the installation itself starts. The rom starts to flash, comes to ~20% and then the system just reboots. I've tried both twrp and filz touch, nothing helps.Also supersu doesn't flash properly. I'm not really professional in this, so i might just do somethng wrong, hope someone can help:crying:
Btw i'm s-on.
UPD: I've made an advanced wipe and the everything works now, so if you have the same problem then just try to do the same, see if works.
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
redpoint73 said:
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
Click to expand...
Click to collapse
I just flashed the GPE ROM, i'm s-on as i said.
Would this ROM work on Verizon HTC One M8
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Are you still able to go into TWRP recovery and are you also rooted?
crispinsaro said:
Are you still able to go into TWRP recovery and are you also rooted?
Click to expand...
Click to collapse
Who was this question adreed to? If you asked me, then i am able to get into recovery, but the supersu doesn't seem to flash, at least i don't get the root.
Miramontes said:
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Click to expand...
Click to collapse
Well, the problem is that i'm s-on, so i hope there is any other solution for this
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
paulmartyn said:
I've tried both twrp and filz touch, nothing helps.
Click to expand...
Click to collapse
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
Miramontes said:
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue
Click to expand...
Click to collapse
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
Will try to erase everything later,maybe tomorrow. Twrp says everything's fine, and aroma doesn't say about any issues, just reboots. Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is. Anyway, thanks for an advice, will try that and tell if it helps or not
redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
I tried filz just to check, because on skydragon everything was fine.
I use twrp 2.8.7.0
hboot 3.19.0.0000
radio 1.25.21331147a1.o6g(if that's what baseband is)
tomorrow i'll try everything you guys advised, see if there is a solution. thanks for the support man
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
well, i've tried to make an adwanced wipe as you advised and it worked thanks man, i thought i'll stay on that rom 4ever.
flashing skydragon now:victory:
crispinsaro said:
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
Click to expand...
Click to collapse
guess the problem was caused by different android versions
redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
So i've tried to make a FULL wipe and finally it worked, everithing works fine now, installin' skydragon and waiting for a better 6.0 ROM
Guess i can close the thread now as my problem is resolved.
paulmartyn said:
Guess i can close the thread now as my problem is resolved.
Click to expand...
Click to collapse
Happy that solved your issue, it is normally said that to install a new rom you have to do a full wipe before hand, glad it worked for you though
paulmartyn said:
Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is.
Click to expand...
Click to collapse
You mean flashing SuperSU after Skydragon (you don't specify)? If so, its not necessary, as all custom ROMs are pre-rooted unless explicitly noted.
Also, older versions of SuperSU won't work on Lollipop, so depending on what version SuperSU you tried (again, you don't specify), that may have been the reason for failure.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
crispinsaro said:
I am sure you factory reset through recovery before installing the new ROM
Click to expand...
Click to collapse
I wouldn't be so sure, if the OP didn't state it.
crispinsaro said:
I normally go on advanced wipe and tick all the boxes
Click to expand...
Click to collapse
I would caution users about following this device literally. It is not necessary to wipe internal storage and/or SD card when flashing a ROM (although particular users may have reason to do so for specific reasons). And if the user has their nandroid or ROM.zip on that partition (and they must have the ROM on one of those, unless they intend to sideload it), its going to get wiped out; causing some confusion and probably panic.
The advice I normally give is: Its called "Advanced" for a reason, and don't wipe it unless you know what the result will be; and you have a legitimate reason to do so.
For instance, I've lost count of the times folks have posted that they wiped system, and don't understand why the phone will no longer boot into OS. Or they wiped internal storage or SD card; and didn't know that it would wipe out their nandroids.
The TWRP default wipe (data, cache and Dalvik) says "most of the time, this is the only wipe you will ever need" and it says that for a reason. If one runs into problems flashing a ROM, they might elect to wipe system. So like I said, a legitimate reason to wipe a particular partition.
But on the other hand, I've done a countless number of ROM flashes on a number of devices (including Skydragon), and never wiped any partition outside the "default wipe", and never had any such issues. Even wiping system (which many swear by) I suspect is often a placebo. When you flash a ROM, system will be wiped by definition, so doing it manually is redundant.
I suspect the failure by the OP was not wiping data and/or cache (they never specified they did that originally or not).
Thats true yes, i dont think I made it clear to do the default TWRP wipe first to see if it would solve anything and then try advanced wipe if all fails, but again with caution.
After reading a litte I've got one question...So if I want GPE rom do I need to convert my phone to GPE or just to flash the rom ?!
Don't have much time here but wanted to get this out
Here's My First Roms for the Huawei Ascend XT
Flashing instructions.. You Must already be on B150 firmware.
You must Mount - System / Cust and Data in TWRP before you start the install.
After install wipe cache / dalvik and reboot
Note if you not on B150 firmware I have a guide here -> https://forum.xda-developers.com/showthread.php?t=3555254 on how to update
Downloads
H1611.STOCK.ROOTED.NOVA.B150.ROM
H1611.B150.Debloated.Rom​
The stock rooted nova has a lot of apps disabled
the Debloated Rom actually removes a bunch of stuff
As Always Make a Backup before you flash Anything ... Factory reset is not required but you may loose some stuff so be aware
Reserved
I re-uploaded H1611.STOCK.ROOTED.NOVA.B150.ROM with the correct /cust in it
the first one had the debloated /cust in it by mistake
It's not something I will use personally but thank you for your efforts. it is appreciated!
Just installed this and it changed my IMEI number. Luckily I had a backup and was able to fix it. Thanks anyways
How much is the free space with the debloated version?
CyberManiaK said:
How much is the free space with the debloated version?
Click to expand...
Click to collapse
I believe the free space remains the same no matter what the debloating consist of. With EMUI the 8GB (approx) usable space remains, the rest is dedicated to the system/phone partition.
Ugh! How did you fix the IMEI?
Daiison said:
Just installed this and it changed my IMEI number. Luckily I had a backup and was able to fix it. Thanks anyways
Click to expand...
Click to collapse
Daiison said:
Just installed this and it changed my IMEI number. Luckily I had a backup and was able to fix it. Thanks anyways
Click to expand...
Click to collapse
Sorry but it must have been something else you flashed or restored the Rom doesn't contain any partitions that hold the IMEI
divineBliss said:
Ugh! How did you fix the IMEI?
Click to expand...
Click to collapse
The efs1 and efs2 partitions hold your IMEI and Serial Number ...flashing the roms will not affect those
That's what I thought, and obviously since you know that, you would not post a ROM with those two files, I presume, so I wonder how OPs IMEI changed?
I've read that one should not even restore their own EFS backups unless absolutely necessary, as doing that may lead problems/corruption.
clsA said:
.. .. The efs1 and efs2 partitions hold your IMEI and Serial Number ...flashing the roms will not affect those
Click to expand...
Click to collapse
divineBliss said:
That's what I thought, and obviously since you know that, you would not post a ROM with those two files, I presume, so I wonder how OPs IMEI changed?
I've read that one should not even restore their own EFS backups unless absolutely necessary, as doing that may lead problems/corruption.
Click to expand...
Click to collapse
I'm not sure what they did. I know all the TWRP backups I have uploaded have the efs partitions removed for just that reason
Sent from my Nexus 6P using Tapatalk
clsA said:
Sorry but it must have been something else you flashed or restored the Rom doesn't contain any partitions that hold the IMEI
The efs1 and efs2 partitions hold your IMEI and Serial Number ...flashing the roms will not affect those
Click to expand...
Click to collapse
All I did was mount the data, system, cust, and microsdcard (where I put the ROM zip) partitions then hit install - h1611 debloated, wiped cache, and then rebooted. Tried it a second time and it still changed the IMEI to mod edit: IMEI deleted.
Note: I don't have a SIM card in the phone as I'm still using my other phone for now but I don't know if that makes a difference. The phone is SIM unlocked. I updated the firmware to B150 before the rom install using your other post and had the stock_b150_pre_root recovery loaded. That is what I used to restore the original IMEI.
---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------
One thing that it did do was remove a lot of the AT&T bloatware even after the stock_b150_pre_root restore so I'm happy with how it turned out.
@clsA,
A little bird told me that the IMEI Daiison posted below belongs to your phone, so if indeed your OP files don't contain EFS partition backups, then it's very interesting how Daiison's phone now has your IMEI # after following OP instructions, isn't it .
Daiison said:
All I did was mount the data, system, cust, and microsdcard (where I put the ROM zip) partitions then hit install - h1611 debloated, wiped cache, and then rebooted. Tried it a second time and it still changed the IMEI to mod edit: IMEI deleted.
Note: I don't have a SIM card in the phone as I'm still using my other phone for now but I don't know if that makes a difference. The phone is SIM unlocked. I updated the firmware to B150 before the rom install using your other post and had the stock_b150_pre_root recovery loaded. That is what I used to restore the original IMEI.
---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------
One thing that it did do was remove a lot of the AT&T bloatware even after the stock_b150_pre_root restore so I'm happy with how it turned out.
Click to expand...
Click to collapse
divineBliss said:
@clsA,
A little bird told me that the IMEI Daiison posted below belongs to your phone, so if indeed your OP files don't contain EFS partition backups, then it's very interesting how Daiison's phone now has your IMEI # after following OP instructions, isn't it .
Click to expand...
Click to collapse
Yeah I pulled the download links till I figure out what's going on... I'm really starting to dislike this phone more and more
Sent from my Nexus 6P using Tapatalk
Daiison said:
All I did was mount the data, system, cust, and microsdcard (where I put the ROM zip) partitions then hit install - h1611 debloated, wiped cache, and then rebooted. Tried it a second time and it still changed the IMEI to mod edit: IMEI deleted.
Note: I don't have a SIM card in the phone as I'm still using my other phone for now but I don't know if that makes a difference. The phone is SIM unlocked. I updated the firmware to B150 before the rom install using your other post and had the stock_b150_pre_root recovery loaded. That is what I used to restore the original IMEI.
---------- Post added at 06:12 PM ---------- Previous post was at 06:08 PM ----------
One thing that it did do was remove a lot of the AT&T bloatware even after the stock_b150_pre_root restore so I'm happy with how it turned out.
Click to expand...
Click to collapse
Thanks for reporting this, it's really not supposed to work like that. I'll try and hunt down what went wrong
Sent from my Nexus 6P using Tapatalk
I did use your other thread to update from B140 to B150, and my original IMEI is still intact. I don't think I used your TWRP data image, so that might be a factor. I doubt the boot or system images are a factor because @dabadguycr and I compared checksums for our backups of those two IIRC , and we had identical checksums, so my suspect is the data image - but I didn't think that's where the IMEI is stored - very confusing .
clsA said:
Yeah I pulled the download links till I figure out what's going on... I'm really starting to dislike this phone more and more
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
clsA said:
Yeah I pulled the download links till I figure out what's going on... I'm really starting to dislike this phone more and more
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sorry, I did not mean to post your IMEI. I thought it was just some random number or the default one for Huawei phones. I tried the install a third time with the SIM card installed and it didn't make a difference.
Well, how would you know that? And it's a good thing you were observant and noticed the IMEI changed. The SIM card should not make a difference, and it has nothing to do with the IMEI number getting set on the phone.
Daiison said:
Sorry, I did not mean to post your IMEI. I thought it was just some random number or the default one for Huawei phones. I tried the install a third time with the SIM card installed and it didn't make a difference.
Click to expand...
Click to collapse
Daiison said:
Sorry, I did not mean to post your IMEI. I thought it was just some random number or the default one for Huawei phones. I tried the install a third time with the SIM card installed and it didn't make a difference.
Click to expand...
Click to collapse
divineBliss said:
Well, how would you know that? And it's a good thing you were observant and noticed the IMEI changed. The SIM card should not make a difference, and it has nothing to do with the IMEI number getting set on the phone.
Click to expand...
Click to collapse
Uploading fixed files now .. i need a tester
Daiison said:
All I did was mount the data, system, cust, and microsdcard (where I put the ROM zip) partitions then hit install - h1611 debloated, wiped cache, and then rebooted. Tried it a second time and it still changed the IMEI to mod edit: IMEI deleted.
Note: I don't have a SIM card in the phone as I'm still using my other phone for now but I don't know if that makes a difference. The phone is SIM unlocked. I updated the firmware to B150 before the rom install using your other post and had the stock_b150_pre_root recovery loaded. That is what I used to restore the original IMEI.
Click to expand...
Click to collapse
OK here's where I have a problem you say you restored your stock IMEI by restoring the stock_b150_pre_root
All this restores is Stock
Boot.img
Recovery.img
System.img
and an Empty /data
None of these partitions could restore your correct IMEI so what is going on ?
The rom's contain
Boot.img (custom rooted)
cust.img (debloated or Stock depends on which rom)
data.img (so root works and some apps are preinstalled)
system.img
As you can see nothing in the Rom has any IMEI info in it many of us have flashed the different /cust backups and never had the IMEI affected so I don't see /cust being the problem ...So is it possible no roms can be flashed to this phone ?
Did anyone else that downloaded the Rom's actually flash it and have your IMEI changed ?