Related
Here is my story:
My Boss at work drunk one night ordered the P6 from China and it was delivered. To his surprise Google Play did not work.
Being a proud owner of 3 rooted devices with custom ROMS I offered my services to install a custom ROM on his P6 that would here in the UK.
However when using adb to boot into fasboot mode in order to flash a custom recovery nothing happened, I was left with a stuck logo screen.
The phones details are as follows:
kernel: 3.0.8-00796-g97d2208 [email protected] # 1
build: B113SP02
This particular build came with SuperSU already installed. I say already installed as I done a factory reset and it was still there.
I have copied over the beta kit kat zip in the hope that installing this from the stock recovery will help things, I need to wait for an sdcard though.
Am I going done the right path and if not could I be steered in the right path?
Any help will be greatly appreciated.
mediaman123 said:
Here is my story:
My Boss at work drunk one night ordered the P6 from China and it was delivered. To his surprise Google Play did not work.
Being a proud owner of 3 rooted devices with custom ROMS I offered my services to install a custom ROM on his P6 that would here in the UK.
However when using adb to boot into fasboot mode in order to flash a custom recovery nothing happened, I was left with a stuck logo screen.
The phones details are as follows:
kernel: 3.0.8-00796-g97d2208 [email protected] # 1
build: B113SP02
This particular build came with SuperSU already installed. I say already installed as I done a factory reset and it was still there.
I have copied over the beta kit kat zip in the hope that installing this from the stock recovery will help things, I need to wait for an sdcard though.
Am I going done the right path and if not could I be steered in the right path?
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Never touch the phone of your boss.
XDAvatar said:
Never touch the phone of your boss.
Click to expand...
Click to collapse
You may be right LOL, any advice though...........?
mediaman123 said:
You may be right LOL, any advice though...........?
Click to expand...
Click to collapse
Push the recovery of a official chinese firmware on it and try updating from there.
XDAvatar said:
Push the recovery of a official chinese firmware on it and try updating from there.
Click to expand...
Click to collapse
So your saying that trying to update my current build through the stock recovery to the latest kit kat build is the way to go?
I cant actually push any recovery images to the device as fastboot mode fails to initialize, hence why I am hoping an official update through stock recovery and sd card may solve that problem.
My aim is to get the latest kit kat TWRP installed, back up the stock build, then install a custom ROM.
mediaman123 said:
So your saying that trying to update my current build through the stock recovery to the latest kit kat build is the way to go?
I cant actually push any recovery images to the device as fastboot mode fails to initialize, hence why I am hoping an official update through stock recovery and sd card may solve that problem.
My aim is to get the latest kit kat TWRP installed, back up the stock build, then install a custom ROM.
Click to expand...
Click to collapse
Yes, sdcard is the solution.
XDAvatar said:
Yes, sdcard is the solution.
Click to expand...
Click to collapse
Ive been looking at various posts regarding the kit kat update and it makes reference to the B132 build and how its essential your on this first before updating to the B510 Kkit kat build.
Should I update to the B132 first?
mediaman123 said:
Ive been looking at various posts regarding the kit kat update and it makes reference to the B132 build and how its essential your on this first before updating to the B510 Kkit kat build.
Should I update to the B132 first?
Click to expand...
Click to collapse
Yes if you want the KK released by HUAWEI Romania. If you use the other BETA you must be on B125.
XDAvatar said:
Yes if you want the KK released by HUAWEI Romania. If you use the other BETA you must be on B125.
Click to expand...
Click to collapse
what other kit kat build is available?
what would you recommend?
I realize i will be putting a cutom ROM anyway, but jut so a stable nandroid backup can be made of an official build.
Thanks so far, you have been really hlepful........
Through more investigation it seems that the B510 kit kat update includes Google Play so it may be wise to install that and therefore the B132 first....
couldnt get the b132 build on or the b520, there were errors........
decided to flash twrp for JB and then install a custom rom....
will i ever be able to update to a KK rom now
XDAvatar said:
Yes.
Click to expand...
Click to collapse
Does it require updating to a stock build through stock recovery....
mediaman123 said:
Does it require updating to a stock build through stock recovery....
Click to expand...
Click to collapse
Yes. Of course.
XDAvatar said:
Yes. Of course.
Click to expand...
Click to collapse
That is a pain.........it will do for now I suppose......
I haven't heard of anyone else on here mentioning the B113 build, only B132 and so on...
Do you think this is an issue? Should I be updating to another build before trying B132?
Does the stock recovery need to match up with the OS build?
hi Have you done anything with your mobile?, I got the same Chinese B113SP06 with TWRP Recovery. I'm just looking for to update to official KitKat as on rooted device cannot run some apps.
mediaman123 said:
That is a pain.........it will do for now I suppose......
I haven't heard of anyone else on here mentioning the B113 build, only B132 and so on...
Do you think this is an issue? Should I be updating to another build before trying B132?
Does the stock recovery need to match up with the OS build?
Click to expand...
Click to collapse
If you still need a help look here http://forum.xda-developers.com/ascend-p6/general/huawei-p6-u06-chinese-rom-help-t2864228
I have same chinese mobile but it's back to international now.
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Norcalz71 said:
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Click to expand...
Click to collapse
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then let TWRP install SU. I actually just did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
I'm pretty sure it works the same for lollipop now too. Originally you needed to flash a special kernel, but I think now you can root it the same way as Kit Kat, ie. via recovery. Someone can correct me if I'm wrong but I don't think I am.
_MetalHead_ said:
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then TWRP install SU. I did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
Click to expand...
Click to collapse
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Norcalz71 said:
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Click to expand...
Click to collapse
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
_MetalHead_ said:
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
Click to expand...
Click to collapse
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Norcalz71 said:
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Click to expand...
Click to collapse
No prob bud. One of the big benefits of Nexus devices is that they are super simple to root. Heck, they are super simple to do pretty much anything on. That's the only reason why I decided to start from scratch yesterday, because it's like nothing to do. The longest part was re-downloading all my apps, but still the whole process took about 30 min start to finish. If you're not downloading a ton of apps, it'll take you 5 minutes.
There are lots of guides to rooting the Verizon LG G3. Many of them are older and have problems working on the 24B software version of Android 5.0.1. I guess I have 2 questions: 1) Is there presently a method to root this phone? 2.) TWRP says, "you must be rooted and vulnerable to BUMP to use TWRP on this device." I don't know what vulnerable to BUMP means. Yes, I know I could try to Google it, but I haven't been very successful at finding an answer that I understand.
EDIT: Root achieved. Still looking for a reliable install process for TWRP
Have you had any luck getting TWRP on stock 24B? The only option I've seen is to bump TWRP to 23C and use JasmineROM 8.0.
aork said:
Have you had any luck getting TWRP on stock 24B? The only option I've seen is to bump TWRP to 23C and use JasmineROM 8.0.
Click to expand...
Click to collapse
I was able to get TWRP on my rooted 24B with a new version of autorec @bender_007 used the firmware from my phone to build it. Where else can you get service like that! When you use 24B version from that page, you may be on TWRP 2.8.6.1 If he hasn't had a chance to update it yet. You can go to 2.8.7.0 if you want, but be certain to use the version from 777jon thread and NOT directly from TWRP. In all cases just double check you are getting the correct version for your phone. You should be able to run TWRP with no errors, and the install could not be easier. Just follow the instructions on the OP. Enjoy!
dweezle said:
I was able to get TWRP on my rooted 24B with a new version of autorec @bender_007 used the firmware from my phone to build it. Where else can you get service like that! When you use 24B version from that page, you may be on TWRP 2.8.6.1 If he hasn't had a chance to update it yet. You can go to 2.8.7.0 if you want, but be certain to use the version from 777jon thread and NOT directly from TWRP. In all cases just double check you are getting the correct version for your phone. You should be able to run TWRP with no errors, and the install could not be easier. Just follow the instructions on the OP. Enjoy!
Click to expand...
Click to collapse
Perfect! Thanks a ton to you and @bender_007 both!
I have rooted my SWR50 previously and was trying to reflash stock in order to upgrade to 5.1.1, When I ran into the problem that lots of people have had with flashing stock. I don't know why, but when I tried installing STOCK LWX48P with 5.0.1, It said it was expecting different test keys than what was on my system. It needed tetra KNX01V 4.4.2 or tetra LWX48P 5.0.2, and it said I have omni_tetra 5.0.2 LRX22G which it is not compatible. I have tried many things and flashed quite a few "stock" roms and bootloaders for my smartwatch trying to get it back to stock, and it is possible one of the things I flashed was wrong for my system. I tried this same method with STOCK LWX48P 5.0.2 and 5.1.1 (5.1.1 being the update I'm trying to install in the first place). I had an idea to install KNX01V being the base firmware that the later firmwares build and patch off of, but I can't find a working download. If you have any ideas to fix my problem it would be much appreciated. Thanks in advance!
P.S. - Just wanted to note that I did read http://forum.xda-developers.com/smartwatch-3/help/wrong-test-keys-ota-update-failed-t3186118, and still had the same problem because rollback didn't work either and the Sony Update Companion says there is no update for my smartwatch when I tried .
Here is some of the resources I used:
Stock zip and recovery IMG download - http://forum.xda-developers.com/smartwatch-3/development/rom-repacked-stock-rom-swr50-version-t2988087 & http://www.carbontesla.com/2014/12/smartwatch-3-lwx48p-android-5-0-1-lollipop/
Forum I used to root and put TWRP recovery on my system in the first place - http://forum.xda-developers.com/smartwatch-3/development/recovery-twrp-2-8-3-0-sony-smartwatch-3-t2986907
And rollback I tried - http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
j.c1998 said:
I have rooted my SWR50 previously and was trying to reflash stock in order to upgrade to 5.1.1, When I ran into the problem that lots of people have had with flashing stock. I don't know why, but when I tried installing STOCK LWX48P with 5.0.1, It said it was expecting different test keys than what was on my system. It needed tetra KNX01V 4.4.2 or tetra LWX48P 5.0.2, and it said I have omni_tetra 5.0.2 LRX22G which it is not compatible. I have tried many things and flashed quite a few "stock" roms and bootloaders for my smartwatch trying to get it back to stock, and it is possible one of the things I flashed was wrong for my system. I tried this same method with STOCK LWX48P 5.0.2 and 5.1.1 (5.1.1 being the update I'm trying to install in the first place). I had an idea to install KNX01V being the base firmware that the later firmwares build and patch off of, but I can't find a working download. If you have any ideas to fix my problem it would be much appreciated. Thanks in advance!
P.S. - Just wanted to note that I did read http://forum.xda-developers.com/smartwatch-3/help/wrong-test-keys-ota-update-failed-t3186118, and still had the same problem because rollback didn't work either and the Sony Update Companion says there is no update for my smartwatch when I tried .
Here is some of the resources I used:
Stock zip and recovery IMG download - http://forum.xda-developers.com/smartwatch-3/development/rom-repacked-stock-rom-swr50-version-t2988087 & http://www.carbontesla.com/2014/12/smartwatch-3-lwx48p-android-5-0-1-lollipop/
Forum I used to root and put TWRP recovery on my system in the first place - http://forum.xda-developers.com/smartwatch-3/development/recovery-twrp-2-8-3-0-sony-smartwatch-3-t2986907
And rollback I tried - http://forum.xda-developers.com/smartwatch-3/general/guide-roll-watch-to-previous-software-t3176801
Click to expand...
Click to collapse
Well I had millions if problems when I rooted latest version now my watch just seems to disconnect randomly and I can't figure out the problem I also had custom kernel and twrp but now even with locked bootloader and non of that stuff apps unsync and I tried PC companion but it also throws an error for me too no update try again later I hope someone can help us
same problem lrx22g error when trying to flash...anyone can upload a 5.1.1 zip rom? or at least a twrp backup on it,and ill try make the zip flashable rom...ty
---------- Post added at 03:05 PM ---------- Previous post was at 02:09 PM ----------
ok people,i nailed it until end...u need to flash stock recovery 5.0.1 for those who got ota flash error....and reset device,then search for updates,and it will be fine....finaly
Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.