Related
So I have my HTC One S, I tried flashing a custom rom a while back and it just simply didn't work, i don't remember a lot of details this was a while ago but I've been doing a bunch of stuff recently to try and revert back to stock, I just want to use an RUU and go full 100% stock again, these are my getvar details in the picture.
So my question is, how the hell can I get this phone running again? Should I find my stock RUU or could someone walk me though how to possibly get back using a stock rom or something? Please note i have no access to anything, I can't even seem to access the phone storage via usb.
Also I attempted to use this RUU "RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed"
before posting here, not sure if this tells anybody something but I figured I'd post it, if anyone needs anymore information please ask me and I'll try to find whatever you need.
I can help. Maybe.
HazyPreston93 said:
So I have my HTC One S, I tried flashing a custom rom a while back and it just simply didn't work, i don't remember a lot of details this was a while ago but I've been doing a bunch of stuff recently to try and revert back to stock, I just want to use an RUU and go full 100% stock again, these are my getvar details in the picture.
So my question is, how the hell can I get this phone running again? Should I find my stock RUU or could someone walk me though how to possibly get back using a stock rom or something? Please note i have no access to anything, I can't even seem to access the phone storage via usb.
Also I attempted to use this RUU "RUU_Ville_U_ICS_40_S_BM_2.40.666.1_Radio_1.09ts.50.02.04_10.08g.50.04L_release_280275_signed"
before posting here, not sure if this tells anybody something but I figured I'd post it, if anyone needs anymore information please ask me and I'll try to find whatever you need.
Click to expand...
Click to collapse
Hi HazyPreston93
I see that you replied to my post on my emergency thread.
I just wanted some information before I give instructions. What is the current state of your phone. You saw on the One S emergency thread what I have written. Just give me background information about your phone
Template:
s=on or off
Bootloader unlocked?
Is there a recovery installed?
Custom kernel?
S4 or S3 processor
Custom rom installed or attempted to install
If you need to feel free to contact me at [email protected]
griddn said:
Hi HazyPreston93
I see that you replied to my post on my emergency thread.
I just wanted some information before I give instructions. What is the current state of your phone. You saw on the One S emergency thread what I have written. Just give me background information about your phone
Template:
s=on or off
Bootloader unlocked?
Is there a recovery installed?
Custom kernel?
S4 or S3 processor
Custom rom installed or attempted to install
If you need to feel free to contact me at [email protected]
Click to expand...
Click to collapse
S=on
Bootloader is locked currently i believe
not sure about the kernel, i think the whole phone is erased so probably stock.
s4
no custom rom tried installing stock RUU
i think the recovery is twpr the phone is dead currently so I have to let it charge to find out for sure.
hi all.
like so many others, Xiaomi forced update 6.1.14 on to my phone which locked the bootloader. i even thought i had stopped the phone from auto updating, but it seems i was wrong. since then, i have been put on to the latest 2 updates. i want to get off of the rom i am on but cant do anything now with the phone in the installing rom dept because regardless of whether i try to use the 'Updater' to put a Chinese dev rom on the phone or any other rom, or if i rename a rom and put it on the root of the phone, i cannot update. i always get a message saying Unable to verify rom and the phone simply stops. when trying to go into recovery mode, as i am unable to get to TWRP, i have even been locked out of that. i applied for an unlock code, but haven't received anything and with Chinese New Year fast approaching, bringing a holiday, i can see Xiaomu ignoring those who asked for a code even longer than they have. i haven't read of a single person being sent the code at all, which is very bad on Xiaomi's part.
i was really pleased with this phone. it worked well for me and did all i wanted but now i have a door stop, to all intents and purpose. such a shame as the way things have gone, i wont be buying from them again.
does anyone have any solution to this problem?
many TIA,
Prettygrim
Download stable ROM - http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
Update your phone to that ROM
You will lost all data and setting (/sdcard is safe)
Bootloader unlocked
Flash CM13
cowithgun said:
Download stable ROM - http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
Update your phone to that ROM
You will lost all data and setting (/sdcard is safe)
Bootloader unlocked
Flash CM13
Click to expand...
Click to collapse
And stay away from dev ROMs unless you have an unlock code.
hi and tnx for the replies.
to cowithgun:
unfortunately, i cannot update to that or any other rom, as i stated above. trying to do so via the 'Updater' and all i get is 'Unable to verify rom', that is after being told i must connect to the WLAN. the speed of that is almost non-existent.
if i try to do so by putting the rom in the root of the drive, renaming it 'update.zip' i again get told 'unable to verify rom'. because of the failure to be able to do anything 'conventional' was the reason i asked for help. i have even tried Kingroot and Kingoroot but both have failed.
to qtotter:
one of the methods i was asked to try was to try to use a Chinese dev rom, but i cant even get one of those on the phone (my wife is Chinese, so no language issues).
with the upcoming Chinese New Year, i can see Xiaomi using that as an excuse to delay giving out unlock codes, if it intends doing so at all. i am extremely p****d off at what they have done and in my case, they have turned a phone that i really liked into half a phone. such i stupid stunt to pull when the 'unlocked' was a feature used to actually make the phone a more attractive sale. really disappointed
should have asked guys, what method would you suggest i try to get this rom, (if the blasted phone doesn't give me the same message as before about cant verify it) installed on the phone? bear in mind i have no official recovery and obviously no TWRP.
TIA
Prettygrim said:
hi and tnx for the replies.
to cowithgun:
unfortunately, i cannot update to that or any other rom, as i stated above. trying to do so via the 'Updater' and all i get is 'Unable to verify rom', that is after being told i must connect to the WLAN. the speed of that is almost non-existent.
if i try to do so by putting the rom in the root of the drive, renaming it 'update.zip' i again get told 'unable to verify rom'. because of the failure to be able to do anything 'conventional' was the reason i asked for help. i have even tried Kingroot and Kingoroot but both have failed.
to qtotter:
one of the methods i was asked to try was to try to use a Chinese dev rom, but i cant even get one of those on the phone (my wife is Chinese, so no language issues).
with the upcoming Chinese New Year, i can see Xiaomi using that as an excuse to delay giving out unlock codes, if it intends doing so at all. i am extremely p****d off at what they have done and in my case, they have turned a phone that i really liked into half a phone. such i stupid stunt to pull when the 'unlocked' was a feature used to actually make the phone a more attractive sale. really disappointed
should have asked guys, what method would you suggest i try to get this rom, (if the blasted phone doesn't give me the same message as before about cant verify it) installed on the phone? bear in mind i have no official recovery and obviously no TWRP.
TIA
Click to expand...
Click to collapse
I tested it myself, it should work. More precisely, I did this:
1. Download this into your computer: http://bigota.d.miui.com/V7.0.16.0.LXKCNCI/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
2. Connect phone to computer via USB, copy the zip into your phone, say /sdcard/downloaded_rom/miui_MI4c_V7.0.16.0.LXKCNCI_cba5b6c4a8_5.1.zip
3. Start Updater, press the "..." on upper right and select "Choose update package", select the ROM.
4. Installing older developer ROM will causes the error you mentioned, but if you have 6.1.14, installing stable 7.0.16 is OK and tested working. Not sure what is changed but if it still wont work, try the latest 7.1.6 stable instead.
5. It will warn you of losing setting. Please YES.
6. When it's done, you will have a MIUI ROM but bootloader no longer lock.
7. Install CM13 as soon as you can!
Sounds like the problem is your recovery. You said you have no official recovery.
Sent from my Mi-4c using Tapatalk
just tried it and no luck, i'm afraid. still getting the message 'Cant verify update'. also tried moving the file to root of phone, renaming it to 'update.zip' and still no luck, still getting the same message. it seems that the phone is well and truly locked down so it wont even take one of Xiaomi's own official updates, unless it is a progression from the present rom. that in my view is well over the top!!
tnx for trying and if you or anyone has another idea, please let me know. it appears that the thing to turn off is the verification of the rom. is that possible, and if so, how?
one thing i have noticed in the settings -->developer options is 'verify apps over USB. could this be anything to do with the rom verification failure? the txt for that is greyed out with the button on (redish) but i cant see how to change the setting. worth a try maybe? anyone know how to change it?
Ulver said:
Sounds like the problem is your recovery. You said you have no official recovery.
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
you may well be right, but if that's the case, it was done by Xiaomi. is there a way of getting it to work? how do i actually check it isn't working? as stated before, when 'booting into recovery', i get an image of the phone on screen with the USB cable either connected or disconnected, depending on the actual state and nothing else happens. i have to do a reboot holding the start button to achieve this
Prettygrim said:
bear in mind i have no official recovery and obviously no TWRP.
Click to expand...
Click to collapse
I'm still waiting for my mi4c to come from China, and this is the reason why I'm gonna flash the latest (unlocked) official "stable" ROM first only to update the recovery and radio partitions right after I receive the phone. Resellers in China sometimes put their custom ROMs, recovery images or malware in the phones.
I don't think I'd flash twrp right away. I'd install cm12.1 or cm13 by "fastboot boot recovery.img" leaving the official recovery left in the phone so that I could go back to the official ROMs in the official way, and confirm if everything works as expected before flashing twrp.
What I don't understand is why people flash the dev (locked) ROMs as they are downloaded. What they need is just boot.img and /system, isn't it?? I'd replace "firmware-update" folder, where bootloader, radio and recovery images are located, in the dev ROM with the one from the stable ROM if I wanna try dev ROMs. Or I'd replace boot.img and system.* in the stable ROM with the ones in the dev ROM. Those modded ROMs should be able to be flashed with twrp...
the main reason for using the Chinese dev roms is because they are supposed to bee already rooted. once any of these roms is on the phone, according to what else i read, any rom going over the top would keep root. personally, i didn't find any rom that had root already and had to root my phone, following instructions i found on the MIUI and other sites. the built in recovery on my phone does nothing.
i had issues with TWRP when first using it, but put that down to being a novice. i found the files needed and the procedure to get out of the constant TWRP loop, which meant the phone was basically soft bricked and all was good. however, even that method fails now with the message something like 'phone is locked, cannot continue.
i have put an official complaint into Xiaomi about the bootloader locking and also about the time being taken to issue unlock codes, which is much longer than 3-21 days in some cases.
if i get anywhere, i'll post what i'm told
Since the latest miui ROMs are all based on Android 5.1.1, it's really easy to root mi4c yourself even on official standard ROMs. You don't have to flash dev ROMs or flash custom recovery like twrp. You can just run twrp on the fly like "fastboot boot twrp.img" to flash SuperSU.zip as long as bootloader is unlocked.
I'd say it's more dangerous to flash dev ROMs only for rooting especially if it's for your wife, not for yourself... Dev ROMs are for people who want to try new functions and designs still under development.
Anyway, I hope you will get an unlock SMS from xiaomi soon!
Had same Problem
search for miui_MI4c_V7.1.6.0.LXKCNCK_1debc127a9_5.1.zip
Hope it helps
So if the bootloader is locked, you can unlock it by flashing an older dev rom?
ermacwins said:
So if the bootloader is locked, you can unlock it by flashing an older dev rom?
Click to expand...
Click to collapse
No. Older Developer ROM will not work. Updater will refuse to update it. I tested a few of them back then, only by flashing the latest stable ROM back then (7.0.16) work.
cowithgun said:
No. Older Developer ROM will not work. Updater will refuse to update it. I tested a few of them back then, only by flashing the latest stable ROM back then (7.0.16) work.
Click to expand...
Click to collapse
And now flash the lastest developer and try roll back one o two a time (this work for my with the original recovery) and later use one rom from xiaomi.eu that one has not locked bootloader .
Sorry for my bad english.
i'm probably being real thick here guys. please bear with me. i am, as i said before, new to all this stuff with phones.
remember too that i have an unlocked bootloader now, courtesy of Xiaomi.
so, just to be clear, i am using miui_MI4c_5.12.31_5d6537a0b8_5.1.zip. to remove the possibility of Xiaomi doing something else to the phone that i dont want, i would like to get on to the xiaomi.eu_multi_libra roms. how do i go about doing this in idiot-proof steps, please? also, if i manage to achieve what i want, how do i stop the phone taking official updates? there must be a setting in the phone somewhere that can be disabled and prevent it updating to what i dont want. i found the one in the 'updater settings' but am of the opinion there is another somewhere that i cant find.
hope someone will be gentle with me
TIA
If you're already on Xiaomi.EU ROMs, you won't get OTA updates directly from Xiaomi that will lock your bootloader.
Sent from my Mi-4c using Tapatalk
i am on
miui_MI4c_5.12.31_5d6537a0b8_5.1.zip
which is an official rom, i believe. hence the questions in my former posts. i want to get on to the libre eu roms but am unsure how to go about it. i have read about using various roms first but i believe doing so is under certain circumstances, ie, bootloader locked, phone not rooted. my phone has the bootloader unlocked now by Xiaomi and i have rooted the phone. this is where my confusion comes in that i was hoping someone could clarify
You have unlock permission from xiaomi now, which means you don't need to worry about updates. You can unlock your phone again anytime you want. It's not one time only thing.
well that's a relief! tnx, qtotter! i didn't want to have to go through all this again, just because the maker decided i hadn't actually bought the phone, i had just bought permission to use it, as long as it was how he wanted me to use it!
bloody USA judge who decided that must have been paid a small fortune to rule in favour of this! just what the entertainment industries and others wanted!! didn't care what the implications were or ow the industries would take the p**s out of customers!!
iPioneer Stock v1 for LG Aristo (LGMS210)(10i)
Disclaimer:
/***
* Your warranty is void now (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
This rom is a stock rom and is almost 100% stock but it comes without dm-verity to avoid boot problems in case you want to preserve your custom recovery.
This rom is meant to be used in case of emergency, give a fresh start to your device, restore your device in case of corruption or just to play around.
I have tested this rom on my own device and everything is working properly.
Please check the specifications at the end of this op.
Requisites:
New assert-fixed twrp version forked from messi's twrp
Note: All the credit for twrp goes to @messi2050, this is just an assert revision of the current twrp made from messi. It will be deleted as soon as we get an updated version with the right assert tags.
Installation steps
Download the new assert-twrp version and flash it as you would normally do it.
Standard Wipe (factory reset) and Format Data are optional (unless you have a non-stock based rom installed already). If you want a full fresh start you should format data, reboot into recovery again and do an standard wipe x3.
Install the rom.
Download files:
New assert-fixed twrp version: https://www.androidfilehost.com/?fid=889764386195921266
Rom: https://www.androidfilehost.com/?fid=817550096634786356
Device: LG Aristo
Model: LGMS210
Code Name: lv3
Carrier: MetroPCS
Android version: 7.0
Software version: MS21010i
Patch level: April 1, 2017
#####
Update
------------
Please read requisites and download the new file using the new link.
With this new assert-fixed version of the current twrp made from messi we can now avoid issues flashing the original iPioneer Rom.
NOTE: This will only work on MetroPCS, not sure about tmobile, I will try to make it for both carriers...
Reserved 1...
Reserved 2...
Screens if you can?
bwinbig_87 said:
Screens if you can?
Click to expand...
Click to collapse
I think you mean screenshot right??
I usually don't take screenshots on my stock roms, basicly because there is nothing new/fancy to show. It is stock and it'll look the same as when you buyed your phone, with the same default wallpaper and apps...
I take screenshots in my slim versions (wich I will start soon).
For some reason doing the Vol - and Power does the same wipe problem as in Messi's V1 of twrp for me. Am i doing something wrong?
Lgms210 custom roms
My name is red208 and I just want to know if there is a custom ROM for MetroPCS LG ms210 preferably like Resurrection Remix I also want to know if this stock
ROM right here is at all any different form the way metro does it? Im really trying to bypass the 8 gig hotspot restrictions that metro has so it can be a truly unlimited hotspot and i know the easiest way to do that is too just Flash a custom rom plz help me??!!?
bwinbig_87 said:
For some reason doing the Vol - and Power does the same wipe problem as in Messi's V1 of twrp for me. Am i doing something wrong?
Click to expand...
Click to collapse
You mean that you power off your device and the use the Volume Key and Power hit yes twice, right???
If that is the case you could try flashing DM-Verity or SuperSu again to avoid that little bootloop. Or you can just stick (like me) to do and ADB REBOOT RECOVERY.
Please notice that I never mentioned that the bug-fixed twrp was intended for this bootloop/reset issue, it just correct some asserts problems that block our devices from installing this rom and any other room with the right and original asserts.
red208 said:
My name is red208 and I just want to know if there is a custom ROM for MetroPCS LG ms210 preferably like Resurrection Remix I also want to know if this stock
ROM right here is at all any different form the way metro does it? Im really trying to bypass the 8 gig hotspot restrictions that metro has so it can be a truly unlimited hotspot and i know the easiest way to do that is too just Flash a custom rom plz help me??!!?
Click to expand...
Click to collapse
Question 1: There is not at the moment, I will start with Leaneage OS after doing my slim version. I don't know how many time it will take as this is my second device and I am just playing around with it (my V20 give me more pleasure).
Question 2: Stock means Stock... Nothing new nor fancy, same setup, apps, etc.... I mention on the OP what this rom porpuse is.
Hotspot issue: not all the time depends on a custom rom, this is my first device with metropcs service, I don't know if they sync your hotspot usage with their servers. If they do you are not going to be able to bypass that. Any ways my slim version it would get rid of plenty of bloatware and it may work if they depend on the main app on the device.
red208 said:
My name is red208 and I just want to know if there is a custom ROM for MetroPCS LG ms210 preferably like Resurrection Remix I also want to know if this stock
ROM right here is at all any different form the way metro does it? Im really trying to bypass the 8 gig hotspot restrictions that metro has so it can be a truly unlimited hotspot and i know the easiest way to do that is too just Flash a custom rom plz help me??!!?
Click to expand...
Click to collapse
The hotspot will be monitored regardless of if you're using a stock room or custom. The only difference being that on a custom rom, you won't receive a notification stating you went over 8 gigs. Once you hit the 8 gig limit, your hotspot speed will be slowed down.
Also, when you go over your 8 gigs of high-speed hotspot it won't reset at the beginning of your pay period, but exactly a month (to the day) after you went over.
So say your pay period is the 5th and you go over your limit on the 4th. You'd have to wait until the 4th of the following month before you get high speed back.
---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------
xtremelora said:
Question 1: There is not at the moment, I will start with Leaneage OS after doing my slim version. I don't know how many time it will take as this is my second device and I am just playing around with it (my V20 give me more pleasure).
Question 2: Stock means Stock... Nothing new nor fancy, same setup, apps, etc.... I mention on the OP what this rom porpuse is.
Hotspot issue: not all the time depends on a custom rom, this is my first device with metropcs service, I don't know if they sync your hotspot usage with their servers. If they do you are not going to be able to bypass that. Any ways my slim version it would get rid of plenty of bloatware and it may work if they depend on the main app on the device.
Click to expand...
Click to collapse
I was just about to ask if your slim rom would be a debloat, but now I know. So good look there.
Also, if and when you get down on lineage. I'll be more than happy to test, I had been working on it myself before I blew up my hard drive. So I'd rather help then be a sponge.
Im also willing to test.
Ufffff...
Ok guys... After several days testing / building the slim version I am getting really frustated and dissapointed...
Everytime something goes wrong there is no way to boot into recovery mode using hard keys, that only makes twrp wipe and reboot but not entering on the complete twrp options. So everytime that I flash the test .zip of the slim version and I get an error before actually booting completely into the normal system I have to go to Mocosoft (windows) and use LGUP to flash the .kdz and start from scratch all over.
I hate to have to reboot my laptop and use Mocosoft, I really hate not been able to reboot in recovery mode as in other LG devices with the hardkeys.
I guess is another limitation of the actuall twrp version that we have, maybe we will have to wait for an updated twrp version to avoid all this trauma.
Right now I feel like I'm done with this device, I have used LGUP around 15 times in 3-5 days just because I can no go into twrp.
If this is happening with a stock based slim version I don't want to think about building/testing lineageos.
If you know an option to go to twrp version after a corrupted/incomplete system tell me about please. I have used the followings procedure but not success:
1.- Hardkeys (just makes twrp wipe the system).
2.- Fastboot boot twrp.img (command fails).
3.- Flashing original twrp (from messi) and then the flashing back the bug-fixed twrp (forked from messi) and trying to reproduce the first boot taking out the battery and using hardkeys (no luck, still wipes the system and reboot by it self).
Sorry guys, I think I will stop for a few days... Maybe I need to go out and have a little fun and come back...
Lgms210
any luck?
n33b said:
any luck?
Click to expand...
Click to collapse
Actually yes...
@messi2050 already builded an updated twrp version avoiding problems with the Hardkeys...
So now I can continue with the test and after that with Lineage if no body build it first... :laugh:
xtremelora said:
Actually yes...
@messi2050 already builded an updated twrp version avoiding problems with the Hardkeys...
So now I can continue with the test and after that with Lineage if no body build it first... :laugh:
Click to expand...
Click to collapse
I hope you can success with lineage 14.1, i wasn't able to make it boot on the stylo 2 plus since ms210 and ms550 are almost the same if you managed to boot it then I'm sure it will work on the stylo too, good luck.
I know it's really late, but I was just gonna say build a version of your rom with the flags for Messi's twrp and just use that to flash.
Either way, I'm glad you managed to sort the shiz out and I'm wishing you the best of luck with development.
ninjasinabag said:
I know it's really late, but I was just gonna say build a version of your rom with the flags for Messi's twrp and just use that to flash.
Either way, I'm glad you managed to sort the shiz out and I'm wishing you the best of luck with development.
Click to expand...
Click to collapse
???
I don't get it?
You mean the asserts right?
I haven't test the new twrp version of messi (no free time), so you are telling me that the new version still have the wrong flags?
I usually don't remove the CORRECT flags from my roms (a Tmo user could flash the metropcs and cause a brick/softbrick for example) to avoid user's mistakes/misread...
xtremelora said:
???
I don't get it?
You mean the asserts right?
I haven't test the new twrp version of messi (no free time), so you are telling me that the new version still have the wrong flags?
I usually don't remove the CORRECT flags from my roms (a Tmo user could flash the metropcs and cause a brick/softbrick for example) to avoid user's mistakes/misread...
Click to expand...
Click to collapse
The new version has the correct flags. I never said it didn't.
I'm saying that a twrp can be created with unified flags allowing a room to be shared between devices without having to build between the lv3 and the aristo. Sorta like what had been done with the LG Leon a couple years ago.
Instead of using the h or Ms flags relating to model number, you can use the consistent board config as the basis.
Either way, the only way someone could brick or soft brick from this method is if it were like the S4 situation where you have to flash the carrier specific kernel version for the device. Like using the At&t rom on the Verizon s4 will cause a soft brick until you flash the Verizon s4 kernel.
This is only just an idea in response to you having to go back and forth (before you got the updated twrp) on recovery versions during your tests
OP updated to link and point to the new and updated twrp version from messi.
You guys no longer need the bug-fixed twrp version as before.
Sent from my LGMS210 using Tapatalk
xtremelora said:
OP updated to link and point to the new and updated twrp version from messi.
You guys no longer need the bug-fixed twrp version as before.
Sent from my LGMS210 using Tapatalk
Click to expand...
Click to collapse
Can you do me a solid, sorry if I'm turning into an annoyance. Add "lg aristo" into either the thread tags or into the thread name itself. It'll add the thread into the Aristo board for easier access and make this easier to find. I recommended your rom to another user who had no idea what I was even talking about. (So I shared the link if you don't mind me doing so)
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk
Good day everyone, just got my note pro WiFi version? Already rooted and has custom kernel civz, tablet feels slow so I'm planning on changing rom maybe lineageOS but I'm concerned about the procedure because I'm not sure where I'm standing with every change done to this device, any help is appreciated I just don't want to brick this device trying to flash a new rom.
Currently it's running stock rom 5.0.2, 3.4.39 civz kernel and knox 2.3, if someone could provide a step by step on what should I do or check in this device to be on the safe road id really appreciate it. Btw I don't even know what recovery I have or how do I access it.
Bump
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
xxjahasotoxx said:
honestly most samsung devices are the same so id suggest getting the full stock system and using odin to revert to stock, from there start by getting a custom recovery and seeing what else you need to set up your rom
someone correct me if im wrong
heres the page for official stock "images"
https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P900/
Click to expand...
Click to collapse
someone told me that I just need to install twrp as it is and start flashing roms, dont know if this the best way to do it what do you think?
It could work just keep in mind that you don't know exactly what the previous owner did to it so if they installed a custom kernel you'll be stuck with that, could be a good thing could be a bad thing
You could always give it a shot and if it gives you problems go back to stock then TWRP then start rom-ing