Related
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
point here.
phorcus said:
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
Click to expand...
Click to collapse
Same happened with me phone doesn't boot... Can't install recovery...
Nothing works tried all possible ways like hard reset
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
zipalign said:
point here.
Click to expand...
Click to collapse
thank you for your help so i was on mokee 7.1 when i flashed only this hydrogen modem v1.1 and when i booted i did not find any volte option, so i went back to latest twrp recovery and tried flashing h2os v2.5 but since 20 minutes i was seeing this ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png ) so i switched off my phone midway and then i installed oxygen os v3.1.0 although it got into a boot loop but when it booted there was no wifi, no imei no, no baseband and many more and when i tried installing mokee or cm14.1 again although they got flashed but when i booted my device i saw oneplus logo and for a few seconds i also saw cm logo and the device continuously kept rebooting in a loop also i am only able to flash oxygen os v3.1.0 that too with no wifi, no imei etc. whereas cm14.1 and mokee wouldnt even boot but they do get flashed and h2os wouldnt even flash , please help :crying:
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Rohandd said:
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
Click to expand...
Click to collapse
i am using twrp-3.0.2-2-oneplus2.img but h2os takes forever to install, but i did flash h2os v2.5's modem v1.1 before flashing h2os v2.5.
i am also seeing this message in twrp " Failed to mount /system (invalid argument) " please help guys
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
I didnt try the seraph build.. Will try it! Thank you
phorcus said:
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Click to expand...
Click to collapse
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
can you please check this screenshot ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
shravansp24 said:
I didnt try the seraph build.. Will try it! Thank you
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Click to expand...
Click to collapse
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
phorcus said:
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
Click to expand...
Click to collapse
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
shravansp24 said:
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
Click to expand...
Click to collapse
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
phorcus said:
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
Click to expand...
Click to collapse
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
shravansp24 said:
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
Click to expand...
Click to collapse
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
phorcus said:
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
Click to expand...
Click to collapse
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
shravansp24 said:
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
Click to expand...
Click to collapse
everything is back to normal on my phone, actually i visited the service center today and they told me that my phone is dead and that i would need to pay 17k to change the motherboard :laugh:
problem here is that H2OS 2.5 messed up all our modems, and who has not made OOS EFS backup via terminal is in trouble now.
when problem popped up in all forums [XDA, and OnePlus one mainly] there have been proposed several solutions, like flashing H2OS modem .zip via recovery, after installing OOS.
so now many users have different scenarios to approach, and a working allwide solution seems not to be found 'til now.
personally I have official TWRP 3.0.2-2 and all my flashings have been made with it.
started from OOS 3.1.0 I had on my phone in the last week, 100% working, then flashed H2OS 2.5. seen the new ROM, decided to get back to something more familiar, so I wiped all and flashed latest nightly of CM13. it was working like a charm, but I had bluetooth issues with my xiaomi mi band [like I always had with OP2 and CM13], so I decided to flash back OOS 3.1.0 wiping data.
OOS 3.1.0 booted up, but without connectivity.
then I realized my modems have been messed up, and started looking for a solution.
the only one I'd try is to fastboot flash OOS 3.0.2 .zip [kindly uploaded by Spannaa], and see if my phone starts working again like it should.
'til now, I will stay with H2OS 2.5 which works perfectly. but when I have time, I'll empty my phone backupping all my stuff [fastboot flashing the .zip mentioned above will wipe userdata too, so I'd lose all my stuff] and try the fastboot thing [I already did it a few months ago, no issues at all].
for those who are in big trouble, that cannot flash anything from recovery, I'd suggest to try to fastoboot flash OOS 3.0.2 with the .zip linked above.
if this solution still doesn't come to an happy ending, then you have to try with the unbrick tool from Qualcomm and see what will happen.
the most important thing is and always will be: don't do anything until you are not aware of what you're actually doing to your phone.
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
i am on zui 2.3.045
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
i am on zui 2.3.045 tell me full installation process if possible
Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Can i flash in fastboot or install Lineage os recovery?
Mikuzukz1 said:
Can i flash in fastboot or install Lineage os recovery?
Click to expand...
Click to collapse
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
+∆bhijith said:
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
Click to expand...
Click to collapse
it's showing error that way
Mikuzukz1 said:
it's showing error that way
Click to expand...
Click to collapse
Even now? Even after rebooting to recovery via ADB?
+∆bhijith said:
Even now? Even after rebooting to recovery via ADB?
Click to expand...
Click to collapse
I don't know how to boot via adb ijust wiped all partitions in twrp
got it working finally....installed it over cm13.0 and done
Mikuzukz1 said:
got it working finally....installed it over cm13.0 and done
Click to expand...
Click to collapse
Wonderful ! Good to go for any 7.x.x rom now...
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Because i faced same problems before and searched in XDA and that is the solution available right now.
Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
I think file is not completely downloaded...
Once same happened when I checked I chose wrong file wwhich was half downloaded.. Check it
i'm facing the same problem. i don't know how to use adb boot.
isn't there any other way.
also i checked the file was completely downloaded
and i'm on zui 2.5
I also have problem when flash nuclearom from cm13. I have some zuk devices but got problem with 2
First, it has bootloop
I have to flash China ROM then it works
I can flash CM 13
But up to 14 or 7.x will have bootloop again
Pls help
Has anyone tried or found any unofficial version of linageos os that works for this model?.
I have mine rooted, twrp, xposed, but I would really like to change the stock OS. Linage would be awesome.
https://forum.mantab.me/thread/9412/custom-rom-nougat-71-lenovo-phab-2-unofficial-lineage-os.xhtml
Ifound this. But model is different, may u try search on that site
dlsega said:
Has anyone tried or found any unofficial version of linageos os that works for this model?.
I have mine rooted, twrp, xposed, but I would really like to change the stock OS. Linage would be awesome.
Click to expand...
Click to collapse
broo could u write a thread or link how u rooted it? im looking on the rusian site
i have been unsucess full 5 time gave up hope (havent retried since 4 months)
i would love to ****ing rootthis phone and have leagos thing
btw found this also http://lenovo-forums.ru/topic/21441-lenovo-phab-2-исходный-код-ядра/
source code
sushil888 said:
https://forum.mantab.me/thread/9412/custom-rom-nougat-71-lenovo-phab-2-unofficial-lineage-os.xhtml
Ifound this. But model is different, may u try search on that site
Click to expand...
Click to collapse
i tried, but avast shows the site as a security risk. I supose you found something for the pb2-650M?
reggiexp said:
broo could u write a thread or link how u rooted it? im looking on the rusian site
i have been unsucess full 5 time gave up hope (havent retried since 4 months)
i would love to ****ing rootthis phone and have leagos thing
btw found this also http://lenovo-forums.ru/topic/21441-lenovo-phab-2-исходный-код-ядра/
source code
Click to expand...
Click to collapse
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Idlsega, i m bit Confused!!
U r pointing towards 650 Y model to reggie....
Looking for 650 m model custom rom?
Which is yr model ?
And reggie... Is using which model ??
sushil888 said:
Idlsega, i m bit Confused!!
U r pointing towards 650 Y model to reggie....
Looking for 650 m model custom rom?
Which is yr model ?
And reggie... Is using which model ??
Click to expand...
Click to collapse
M and Y are same? i mean i didnt find any difference. only different country same phone
---------- Post added at 08:45 PM ---------- Previous post was at 08:37 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:52 PM ---------- Previous post was at 08:45 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------
dlsega said:
i followed this guide for rooting
https://forum.xda-developers.com/phab-2/how-to/how-to-root-phab-2-pb2-650y-t3524305
The only trouble I had was unlocking the bootloader, and this step wasn't mentioned it the guide. Before flashing the code to unlock bootloader, in the developer options, (in the phone) I didn't checked the OEM unlocking. After I checked it, flashed the unlock bootloader code successfully, the phone restored to factory, then flashed the TWRP. Just as it's described in the guide. The only difference I noticed is that dlto enter recovery mode after twrp is install you have to push at the same time vol down button + power button.
if after you have root and install twrp you want to install xposed framework, just look for the xposed installer for android 6 arm64 devices.
i used this one here.
http://dl-xda.xposed.info/framework/sdk23/arm64/
choose the newest file
Click to expand...
Click to collapse
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
reggiexp said:
M and Y are same? i mean i didnt find any difference. only different country same phone
---------- Post added at 08:45 PM ---------- Previous post was at 08:37 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:52 PM ---------- Previous post was at 08:45 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:52 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
---------- Post added at 08:53 PM ---------- Previous post was at 08:53 PM ----------
i tried that last time impossible to boot recovery even after flashing :/ its keepos booting stock recovery :/
Click to expand...
Click to collapse
They're pretty much the same, the difference is on the LTE bands, the M has works with more I think. (besides the retail region).
I had a similiar problem, and the issue was that the bootloader wasn't being unlocked flashing the commands. It turns out that the thing keeping the bootloader from unlocking was that little OEM UNLOCK check in the DEVELOPER OPTIONS. After I checked that one, tried again, and this time it worked, I first noticed it because the phone started wiping to a factory reset automatically. After that I just put it into fastboot mode, flashed TWRP. And done.
I don't know if this is the same issue you're having. But for me it was a little frustrating trying and trying without success, until I noticed that little detail and that was it.
At the moment I have it rooted with xposed working just fine. The only issue (don't know if it's only me), is when recording a video using 3rd party apps like instagram or snapchat, the audio is garbage, like some noise cancellation going wrong.
im sure i had that ticked but i guess not. will retry once i fix my xiaomi redmi note 3 who has a memory failure (same on my mom's phone redmi note 3) both crashed 2weeks apart from each other. they boot but as soon as u download 5apps thr phone bootloops... and now im trying to get mi flash to work but its been a long time and i can't figure it out... so now using this massive phone fr 3months its a good phone but damn that quad core is slow... and apps close way to quick on back ground. anyway i will try and root again some dag and install linea os.
reggiexp said:
im sure i had that ticked but i guess not. will retry once i fix my xiaomi redmi note 3 who has a memory failure (same on my mom's phone redmi note 3) both crashed 2weeks apart from each other. they boot but as soon as u download 5apps thr phone bootloops... and now im trying to get mi flash to work but its been a long time and i can't figure it out... so now using this massive phone fr 3months its a good phone but damn that quad core is slow... and apps close way to quick on back ground. anyway i will try and root again some dag and install linea os.
Click to expand...
Click to collapse
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
frankbonatelli said:
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
Click to expand...
Click to collapse
didn't even try.
it's my majn phone still so not really wanna mess with it. still to lazy to flash RR on my redmi note 3
frankbonatelli said:
Did you manage to get lineage to run?
Sent from my Lenovo PB2-650Y using Tapatalk
Click to expand...
Click to collapse
still not switch phone? any one got any updates on the roms??? like this forum is dead.././
Custom rom for lenovo pb2-650m
I request the developers to provide custom rom for lenovo pb2-650m.
subal kumar mahato01 said:
I request the developers to provide custom rom for lenovo pb2-650m.
Click to expand...
Click to collapse
it are the same phones anyway i just cant figur out the unlock and twrp flash
subal kumar mahato01 said:
I request the developers to provide custom rom for lenovo pb2-650m.
Click to expand...
Click to collapse
Were you able to find any custom rom for lenovo pb2-650m?
Good Morning everybody,
so yesterday was a rough day and when it eventually end i recive the october security update on the phone, without thinking i installed it and the phone does not boot up , instead i face my recovery (TWRP 3.1.1-0).
Of course i've made a mess because i was on stock rooted 7.0 on my retEU XT1572 phone with unlocked bootloader and status 3
i've tryed to restore a previous nandroid backup wihtout success, so today i downloaded the new RESURRECTION REMIX v5.8.4 (4 december wich is based on stock android 7) but i have no luck even with that...
Do i miss something?is there any rom to try with now? or i have to make a downgrade of my firmware to make it work again?
thanks in advice!
UPDATE:
phone boot now but always in recovery and after rebooting in bootloader i can reboot system from there.. it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
LAST UPDATE:
boot fixed by using this command in twrp recovery
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work (the rom is the same that you linked page40 post #397 )
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
dzidexx said:
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
Click to expand...
Click to collapse
Husky34 said:
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
Click to expand...
Click to collapse
1. I think so. 3.2.x will be needed for future builds.
1a. You flashed RR for MM modem.
2. No, but this is only way to get ota update.
"swearing in italian" it was a twrp bug.. after a backup restore if you hit restart the phone restart in recovery, you need to boot into bootloader and reboot system from there -.-
thanks to all of you guys!!
strange fact, now if i turn off the phone and again on i'm still on recovery, i have to reboot bootloader and system from there.
i think something is pointing at the recovery instead system..
edit: it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
dzidexx said:
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
Click to expand...
Click to collapse
just tried but wihout luck.. maybe i can wait someone make the flashable update but i don't think this fix the issue
Flash uploaded stock.
dzidexx said:
Flash uploaded stock.
Click to expand...
Click to collapse
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Husky34 said:
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Click to expand...
Click to collapse
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
pshadoww said:
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
Click to expand...
Click to collapse
you can also use link2sd to disable the update app so it doesn't bother you,
or wait untill someone create a zip of the update and flash it into recovery.
thanks, that worked for me as well.
File was located at /dev/block/platform/soc.0/f9824900.sdhci/by-name/misc
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data
gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob
anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?