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.
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
Code:
su
echo 1 > /sys/module/qpnp_smbcharger_extension/parameters/start_id_polling
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
[STRIKE]https://www.androidfilehost.com/?fid=745425885120730219[/STRIKE]
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
------------
Some screenshots:
Oh. You need also replace wifi calibration file here: /system/etc/firmware/wlan/bcmdhd/bcmdhd.cal and reboot
It's forgotten to be added.
Updated fixed version at yandex disk.
Thanks for this. It is exactly what I am looking for and I hope my tech skills are up to the task.
BTW, this link comes up "404 not found. Can't find it!"
https://www.androidfilehost.com/?fid=745425885120730219
Would you have another we can try?
Thats because kv123 removed version with wifi buggy.
Use my mirror link or this.
https://www.androidfilehost.com/?fid=817550096634767960
alex009988 said:
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
https://www.androidfilehost.com/?fid=745425885120730219
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
Click to expand...
Click to collapse
Hi, could you please add some screenshots?
Ok. Added to the top.
need rom for SG712 please...
Thanks for sharing. SGP712 build would be great
Charsher47 said:
Thanks for sharing. SGP712 build would be great
Click to expand...
Click to collapse
Kv123 told me that he's gonna build the rom for 712 too.
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
kv123 said:
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
Click to expand...
Click to collapse
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Phil_Libra said:
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Click to expand...
Click to collapse
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
alex009988 said:
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
Click to expand...
Click to collapse
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
Sorry if I have missed something obvious, but are you attempting to flash LineageOS? In which case I am confused as to why you are flashing the Sony Rom 32.A.2.33?
For my part I am gearing up to attempt the LineageOS install but would like to have a backup copy of the Sony firmware in case it goes wrong.
Assuming you installed an English version, which one did you select from here:-
https://xpericheck.com/device/SGP771
Indeed, if you try something especially unchecked, better to have a backup.
But you also need to have last sony rom(any of android 7.0) in order to update bootloader and have last twrp working.
alex009988 said:
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Click to expand...
Click to collapse
Androplus‘ recovery need a modified boot.img so I wonder if the same as the recovery in yandex disk?
And recovery from https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265 is the same as Androplus’ recovery.
Ok. If you've done everything right I guess 712 dosent work with 771 recovery. I'll tell about it to kv123 and you can say it on your own on 4pda.
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
alex009988 said:
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Click to expand...
Click to collapse
I'm seeing the same results. Tried the same recoveries to no avail.
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?
Hello xda developers this is my second thread sorry for the first one that i made yesterday, I am having a problem with my lenovo k4 note a7010a48
after rooting successfully I proceed to flash rr 7.1.2 but did not flash the gapps now my problem is how to go back on recovery mode to start over again
I already used the power button followed by the volume up down buttons but it is not working like before it is nougat. I only need to get to recovery mode. Please help and thankyou in advance. More power
Does u have root access now and which version of rr u flashed
yes the phone is rooted already and flashed with rr 7.1.2 only need to open recovery mode which is I have no idea
Contact in telegram app 9032015333 I will tell u
i dont know that or how to do that can you teach me please thank you
I have the same issue. Can't enter into recovery and the phone is unable to start.
Same Issue || Don't Know How To Fix
Hi,
I am searching for a possible solution from a day. But could not find a working solution.
After successfully flashing RR-N-5.8.5 (Android N)
Unable to go into recovery.
PROBLEM DESCRIPTION:
1. When Press Vol Up + Vol Down + Power Up
2. Recovery is not loading up
3. Instead it goes in boot loop
4. Normal boot mode and fast boot mode are working perfectly fine
SOLUTIONS TRIED:
1. Flashing recovery again using fastboot mode
2. Flashing different recovery, i.e updated version of recovery
As all recoveries which were available were for marshmallow version. I am not sure but have doubt as android version is updated so the kernel so do recovery also become obsolete in this case ?
Any help is welcome and appreciated
Thanks
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
jaineshjain said:
Contact in telegram app 9032015333 I will tell u
Click to expand...
Click to collapse
Whole concept of this platform is sharing your knowledge
Don't you think it would be better if you discuss here itself ?
for fastboot mode and for recovery mode yes i tried it also but thats the problem no recovery mode. I will wait for the solution when it comes i will just store my phone for a while.
Hi Developers,
Is it possible to reset the phone at hardware level? I can't even connect the phone to PC as it keeps on rebooting.
Please note: upgraded to Nougat and wanted to do the second recovery as suggested by mohancm in the post. When the phone rebooted (before flashing the second recovery), the problem started.
Please let me know if any one has a fix/workaround for the issue.
Thanks,
Srihari
1.Download TWRP recovery unzip files.
https://drive.google.com/file/d/0B1CKVcdcbHFPUzFCODVMN0ZfTW8/view
2.Now in folder TWRP\img\ there is the file recovery.img.
3.Download the second recovery for nougat recovery-Nougat.img and put in the TWRP\img folder.
https://androidfilehost.com/?fid=673368273298981920
4.Rename it as the original, recovery.img and replace it.
5.Then connect your phone to usb and select the 3th option from usb debugging message
"Transfer photos(ptp)"
6.run TWRP_Install.bat from TWRP folder
And you are done, had the same problem and I figure this solution, hope it will help.
I cannot locate the transfer photos(ptp)
ok I already done the part I am now on the recovery mode thanks. new problem of mine is after flashing the rom gapps and recovery after reboot it goes back to recovery mode did I miss something on flashing?
ok so i already passed this problem thanks for the help xda community thank you very much but I have this bootloop problem maybe I did a mistake flashing before rebooting sorry i am a noob in this kind of upgrade specially in mobile phones. I will be careful next time after I passed this problem I hope you will help me once again, my phone in bootloop is killing me.
I have same issue... I flashed gapps and my phone is working smoothly... The issue is i can't go into recovery mode... I tried some one tap reboot to recovery apps but all whats happening is phone restarting normally.
For those who can't access recovery mode. You were supposed to flash updated recovery image after flashing rrn rom.
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Should work.
Worst case, restore by flashing stock rom using SP flash tools. And then start all over again.
If you face any issues ping me. Even I had faced this issue and fixed it after a lot of struggle. I can try to help you.
Or you could download Official Twrp App directly from play store, then find A3000 (Air Row) in 'select device' and flash that to recovery, (if your phone is rooted) then you are good to go, go to recovery mode and thats all, your twrp is now has been flashed.
Thank me later??
MisledMew said:
Enter into fastboot mode by using adb shell.
Flash the updated recovery image
Now try rebooting into recovery.
Click to expand...
Click to collapse
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
firelmnt said:
This really worked for me. Many thanks man.
Well it got me some time to find the right recovery image for my ROM so I decided to give you link for anyone going through the same.
My configuration at that time was: DotOS 1.2 and TWRP 3.1.1 (or so).
On the DotOS thread was enclosed link to wrong recovery image file (or its version was changed as of 28.12.2018) but after small investigation I found this file recovery-mohan-N.img.
Note: This recovery worked for TWRP and Android Nougat and I'm not an expert to suggest this will work for your case either.
Thank you again and have a nice time
Click to expand...
Click to collapse
Glad it helped
Hello everyone, first of all am a newbie and I am trying to flash my Note3 with custom rom, I installed twrp using Odin, first I faced an error that Everytime Odin will say pass but phone will boot normal, how ever I find the solution by unchecking auto reboot in Odin, after pass I'll unplug the device, pull off battery then restart and it will get me to term recovery and it works fine afterwards. I tried installing few custom ROMs like magma nx, dark lord x etc but after everything done phone get stuck in bootloop. First I did the same and got stuck then I did a stock rom flash and got the phone working again, how ever I tried flashing again with magma nx and it got away from Samsung logo to pyeongchang edition logo and got stuck there, all the roms I tried give me same error. Am using twrp 2.8.7.0. I had also rooted using SuperSU, how can I get past this? Any help will be appreciated.. thank you
What phone model ??
Bootloop read the thousands of bootloop posts use roms SEARCH THREAD box bootloop .
Difficult to know what you are doing wrong without more information .
Model is a Note 3 N9005,
I have gone through most of the threads but I am not finding a solution yet, as I said :-
1) Installed TWRP using Odin
2) Rooted the device
3)Placed few Custom ROMs in SD
4)Flashed using TWRP (followed instructions)
5) Flashing finished successfully
6) Reboot
7) Bootloop
Stuck here, can I provide any other details?
3)Placed few Custom ROMs in SD
As in what rom one only not multiples .
4)Flashed using TWRP (followed instructions)
Right twrp wrong twrp ??
7) Bootloop
What did rom thread say about bootloop ??
Updated bootloader >>when required .
Magma has full instructions and full faqs .
---------- Post added at 02:02 PM ---------- Previous post was at 01:43 PM ----------
mAGMA
SEARCH THREAD Bootloop
https://forum.xda-developers.com/search/thread/3508672?query=bootloop
FAQ
Q: I have bootloop right after I flash the ROM
2. In first boot, when asked to "Consent for Diagnostic Report", you forgot to uncheck it. As written in OP, you have to "uncheck" the Consent for Diagnostic Report.
To solve it:
1. Power off phone
2. Remove sim card
3. Boot to ROM.
4. Go to settings/general management
5. Disable "Report Diagnostic Info"
6. Power off Device.
7. Insert sim card.
8. Boot up phone and continue using it
Managed to make them work already, thanks for the help bro.. appreciate it
I managed to work around the issue of bootloop bro, it had something to do with the kernal , I already flashed to magma and it is working now, how ever I was curious that each time when I restart the phone, it took a bit time to load up, like note 3 logo first, then magma note 8 logo, then after that it says optimizing apps and actually it shows around 240 apps or so, is it normal or is there any workarounds for the same? (How ever, boots up fine but boot up time is around 7-12 min approx)