Database Develop

[Q] Updating rooted device to 5.1?

So i got a nexus 6 and i need to update it to android 5.1.0 ?
Status: Unlocked though ADB rooted though c.f auto root and recovery though adb. encrypted stock 5.0.1 rom.
And i want to install chroma rom with android lollipop 5.1.0? how do i do that? do i need some sort of new bootloader or radio as i heard someone talking about?
Thx.

XDAcube said:
So i got a nexus 6 and i need to update it to android 5.1.0 ?
Status: Unlocked though ADB rooted though c.f auto root and recovery though adb. encrypted stock 5.0.1 rom.
And i want to install chroma rom with android lollipop 5.1.0? how do i do that? do i need some sort of new bootloader or radio as i heard someone talking about?
Thx.
Click to expand...
Click to collapse
If you unlocked the boot loader, rooted and have TWRP custom recovery, you just need to :
1. Download rom and gapps to your phone. Links should be found in the OP of the ROM's thread. If you wish Google to restore your apps be sure you have selected the backup-auto restore in settings.
2. Do unencryption now if you wish.
3. Boot into TWRP recovery and wipe a couple times.
4. From TWRP, install the rom and gapps.
5. Reboot system, sign into your Google account and let it download and restore your apps.
6. Reboot system once more & you should be gtg.

wtherrell said:
If you unlocked the boot loader, rooted and have TWRP custom recovery, you just need to :
1. Download rom and gapps to your phone. Links should be found in the OP of the ROM's thread. If you wish Google to restore your apps be sure you have selected the backup-auto restore in settings.
2. Do unencryption now if you wish.
3. Boot into TWRP recovery and wipe a couple times.
4. From TWRP, install the rom and gapps.
5. Reboot system, sign into your Google account and let it download and restore your apps.
6. Reboot system once more & you should be gtg.
Click to expand...
Click to collapse
So i dont need to wipe? or flash a bootloader and radio since im coming from 5.0.1? you know like vanillapop 5.1 requires you to flash bootloader and radio if coming from 5.0.X?

XDAcube said:
So i dont need to wipe? or flash a bootloader and radio since im coming from 5.0.1? you know like vanillapop 5.1 requires you to flash bootloader and radio if coming from 5.0.X?
Click to expand...
Click to collapse
Should be in the Chroma OP or close thereby as to whether you need the boot loader.
I would think for sure a wipe or two. Boot loader, maybe. Radio, at your discretion.

wtherrell said:
Should be in the Chroma OP or close thereby as to whether you need the boot loader.
I would think for sure a wipe or two. Boot loader, maybe. Radio, at your discretion.
Click to expand...
Click to collapse
Cool we look in there again later thx for help

XDAcube said:
Cool we look in there again later thx for help
Click to expand...
Click to collapse
I checked. Instructions and prerequisites are in the OP of the Chroma thread.

I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!

wtherrell said:
I checked. Instructions and prerequisites are in the OP of the Chroma thread.
Click to expand...
Click to collapse
So no need to flash bootloader or radio then?

XDAcube said:
So no need to flash bootloader or radio then?
Click to expand...
Click to collapse
Doesn't appear so.

thijsniehof said:
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
Click to expand...
Click to collapse
Well thats stock rom right? i want something custom and cool
wtherrell said:
Doesn't appear so.
Click to expand...
Click to collapse
Okay thanks will look into it!

XDAcube said:
Well thats stock rom right? i want something custom and cool
Okay thanks will look into it!
Click to expand...
Click to collapse
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.

wtherrell said:
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
Click to expand...
Click to collapse
Will do thanks great device! i just got it from criagslist today already flashing! i have something to play with tonight!

XDAcube said:
Well thats stock rom right? i want something custom and cool
Click to expand...
Click to collapse
Yup stock indeed... Stock ROM, stock recovery..

thijsniehof said:
Yup stock indeed... Stock ROM, stock recovery..
Click to expand...
Click to collapse
Just what i thought!

wtherrell said:
Checkout 2nd post in that thread. Also check out the other exciting rom choices in the Nexus 6 android development threads.
Click to expand...
Click to collapse
Do i need the android 5.1 bseband for chroma?
And the bootloader wasn,t need right? scared to brick it

XDAcube said:
Do i need the android 5.1 bseband for chroma?
And the bootloader wasn,t need right? scared to brick it
Click to expand...
Click to collapse
Oooook... I'm confused too. I'm on dirty unicorns 5.0.2.. I want to upgrade to 5.1... Some instructions say to flash the unencrypted kernel and I also have looked into the boot img and baseband thread.. But when would I need to do all of this? I need someone willing to explain it like I'm five how and when to update the baseband, etc.. I already backed up my internal storage so I'm ready to do whatever I have to to flash Chroma or any other non stock 5.1 ROM.

kaslopis said:
Oooook... I'm confused too. I'm on dirty unicorns 5.0.2.. I want to upgrade to 5.1... Some instructions say to flash the unencrypted kernel and I also have looked into the boot img and baseband thread.. But when would I need to do all of this? I need someone willing to explain it like I'm five how and when to update the baseband, etc.. I already backed up my internal storage so I'm ready to do whatever I have to to flash Chroma or any other non stock 5.1 ROM.
Click to expand...
Click to collapse
Well can you be my guinea pig and flash chroma without doing everything else? worst thing that could happen is it not boot into the rom and wrong radio will just make your phone not pickking up signel intil you flashed radio. but chroma dont say anything about flashing bootloader so i dont think its needed.
BTW ims still on rooted stock 5.0.1.

Bump!

dm verity boot error cb9 fixed..

I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249

First flash this file and then Rom. That's right?? Or its other way around

karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..

Wouldn't this procedure downgrade some performance on the device?

Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..

Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted

Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..

Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?

cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.

I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs

Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk

puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..

snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..

This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.

cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice

cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.

snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?

cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus

snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk

it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)

Oneplus 3t oos lags

Hey, sooo my oneplus 3t lags in every oos version (stable/open beta) and it mostly appears when i pull down the notification panel and the quick settings. tried clean flashing/ using the unbrick tool to go back to completely stock. the problem dosen't appear on any custom Rom that i have used so far but i do want to stay stock for now. any suggestions?

Skybutuguy said:
Hey, sooo my oneplus 3t lags in every oos version (stable/open beta) and it mostly appears when i pull down the notification panel and the quick settings. tried clean flashing/ using the unbrick tool to go back to completely stock. the problem dosen't appear on any custom Rom that i have used so far but i do want to stay stock for now. any suggestions?
Click to expand...
Click to collapse
It happens after you start installing apps? or does it happen as soon as it boots up for the first time after clean flashing?

blanco2701 said:
It happens after you start installing apps? or does it happen as soon as it boots up for the first time after clean flashing?
Click to expand...
Click to collapse
As soon as it boots up. Even the setup is laggy after clean flash

Skybutuguy said:
As soon as it boots up. Even the setup is laggy after clean flash
Click to expand...
Click to collapse
That's weird. If it happens even after a clean flash then I think you have hardware problems my friend.

blanco2701 said:
That's weird. If it happens even after a clean flash then I think you have hardware problems my friend.
Click to expand...
Click to collapse
i dont think its a hardware problem because on custom roms everything works smoothly. (even hydrogen 8.0)

Skybutuguy said:
i dont think its a hardware problem because on custom roms everything works smoothly. (even hydrogen 8.0)
Click to expand...
Click to collapse
Uhmm you must be jumping a step or something going back to stock... Try doing a factory reset from stock recovery AFTER you flash the stock rom.

blanco2701 said:
Uhmm you must be jumping a step or something going back to stock... Try doing a factory reset from stock recovery AFTER you flash the stock rom.
Click to expand...
Click to collapse
what do you recommend to do? clean flash the latest oos version or use the unbrick tool to go back to stock and then update from the ota?

Skybutuguy said:
what do you recommend to do? clean flash the latest oos version or use the unbrick tool to go back to stock and then update from the ota?
Click to expand...
Click to collapse
I've never used any unbrick tool. Just be sure to check "allow oem unlock" in the developer settings in case anything goes wrond.

Xiaomi Mi 8 China to Global Rom

Hi,
I had a bricked phone and I have managed to fix it.
At the moment I have China rom installed which I don't really want to use. It has no Google services and a lot of Chinese apps.
So I just want to double check.
1. I unlock bootloader with the Mi unlock app.
2. Then simply flash global rom with Mi Flash and definitely make sure to only select cleanall.bat and not cleanall_lock.bat.
Is that all I have to do? Some posts recommend different things and some just say do this so I want to make sure.
Thanks,

No.. you cannot simply flash Global if your phone chinese version.
Read... so much thread about it and people have brick because of it.
Sent from my MI 8 using Tapatalk

Danielandg said:
Hi,
I had a bricked phone and I have managed to fix it.
At the moment I have China rom installed which I don't really want to use. It has no Google services and a lot of Chinese apps.
So I just want to double check.
1. I unlock bootloader with the Mi unlock app.
2. Then simply flash global rom with Mi Flash and definitely make sure to only select cleanall.bat and not cleanall_lock.bat.
Is that all I have to do? Some posts recommend different things and some just say do this so I want to make sure.
Thanks,
Click to expand...
Click to collapse
That's the wrong forum to post.

Vuska said:
No.. you cannot simply flash Global if your phone chinese version.
Read... so much thread about it and people have brick because of it.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
There's like one guy on YouTube that basically says to do this.
Then there's some on a forum that days to do a lot of things.
There's just so much random stuff from many threads that it is hard it know what should be done... That's why I ask here for definite answer.

Dude I have a Chinese version Mi8 and after unlocking the bootloader I used the eu.miui pie rom and then jumped straight to the custom roms. Also i did format my data by typing yes in twrp after flashing the eu,miui and lost all the stuff on the internal storage, which really did not matter as I had just unlocked the bootloader and everything had been wiped clean anyways.
Been using two Xiaomi phones and have never flashed any MIUI roms only eu.miui and never had any problems

Doesn't matter. Gotta wait 15 days before I can unlock it and flash. Strange as my account was approved some years back to do the same with a Redmi but oh well. I guess I will wait 15 days...

Danielandg said:
Doesn't matter. Gotta wait 15 days before I can unlock it and flash. Strange as my account was approved some years back to do the same with a Redmi but oh well. I guess I will wait 15 days...
Click to expand...
Click to collapse
Share with us your final results, succeed or fail? In case of succeed tell us how you did it. thks.

i've just flashed a chinese mi 8. Just unlock the bootloader, flash TWRP and flash the rom.
i used xiaomi.eu rom for the last one. Now i've a Mi8 explorer edition in my hands and need to wait for the 15 days are gone than i'll flash xiaomi.eu rom here too.
BUT never re-lock the bootloader again after you've flashed a other rom than the orignal rom, your device will brick.

Flash-User said:
i've just flashed a chinese mi 8. Just unlock the bootloader, flash TWRP and flash the rom.
i used xiaomi.eu rom for the last one. Now i've a Mi8 explorer edition in my hands and need to wait for the 15 days are gone than i'll flash xiaomi.eu rom here too.
BUT never re-lock the bootloader again after you've flashed a other rom than the orignal rom, your device will brick.
Click to expand...
Click to collapse
Me too! Waiting for those 15 days. Thanks!

Question cant get back yo stock from pixel experience ?

can someone help pleasae , i have pixel experience on my redmi note 10 pro and trying to go back to stock but its failing . when tring miflash the progress bar speeds to green in like 1 second and nothing is flashed and mi pc suite cant detect phone
whats best way to get back to stock please

Simple, do the same as for every other custom rom. Put your Stock rom on your sdcard and go into recovery(process as usual a full wipe), then install stock rom. You have to install TWRP/Pixel-Recovery again ofc.

Sorted it now . Thanks anyway . I had to delete a few lines of a batch file that was preventing rollback and did it in miflash

garny68 said:
Sorted it now . Thanks anyway . I had to delete a few lines of a batch file that was preventing rollback and did it in miflash
Click to expand...
Click to collapse
Maybe you can help me by telling me the lines and where to find them! I am stuck! Please

kazi69 said:
Maybe you can help me by telling me the lines and where to find them! I am stuck! Please
Click to expand...
Click to collapse
Watch this video . I followed the steps but it kept failing to flash .around the 10 min mark he will talk about the anti rollback feature . Follow his steps on deleting the lines in the text file and it worked 1st time for me

garny68 said:
Sorted it now . Thanks anyway . I had to delete a few lines of a batch file that was preventing rollback and did it in miflash
Click to expand...
Click to collapse
That's a safety check. Bypassing that increases the risk to brick this device.

[email protected] said:
That's a safety check. Bypassing that increases the risk to brick this d
Click to expand...
Click to collapse
[email protected] said:
That's a safety check. Bypassing that increases the risk to brick this device.
Click to expand...
Click to collapse
I didn't know that as he never said in tutorial . As I won't be installing an other ROMs and everything is working fine would I be ok to leave it as it is or should I download the ROM to my phone and install original ROM over the top via local storage ?
[email protected] said:
That's a safety check. Bypassing that increases the risk to brick this device.
Click to expand...
Click to collapse
Doesn't mention that in the video and was only way I could get to install the ROM and get back to original . Everything seems fine now it's installed . As I won't be installing anymore ROMs would it be safe to leave as is or would you recommend doing something ? .thanks

garny68 said:
I didn't know that as he never said in tutorial . As I won't be installing an other ROMs and everything is working fine would I be ok to leave it as it is or should I download the ROM to my phone and install original ROM over the top via local storage ?
Doesn't mention that in the video and was only way I could get to install the ROM and get back to original . Everything seems fine now it's installed . As I won't be installing anymore ROMs would it be safe to leave as is or would you recommend doing something ? .thanks
Click to expand...
Click to collapse
Xiaomi has implemented anti rollback to prevent switching to old builds. Recovery ROMs don't have this safety check but fastboot ROMs do have. Bypassing this might brick the device like many Note 5 pro owners bricked their devices by flashing older recovery rom which bypassed the safety check. If they'd have flashed fastboot rom their devices could have been saved.

[email protected] said:
Xiaomi has implemented anti rollback to prevent switching to old builds. Recovery ROMs don't have this safety check but fastboot ROMs do have. Bypassing this might brick the device like many Note 5 pro owners bricked their devices by flashing older recovery rom which bypassed the safety check. If they'd have flashed fastboot rom their devices could have been saved.
Click to expand...
Click to collapse
I put phone into fastboot mode then flashed with the mi flash tool . Obviously I deleted the text out of the file in the tutorial but as I'm up and running on latest firmware would it be safe to say all is good my end ? . I flashed with a fastboot ROM latest one

garny68 said:
can someone help pleasae , i have pixel experience on my redmi note 10 pro and trying to go back to stock but its failing . when tring miflash the progress bar speeds to green in like 1 second and nothing is flashed and mi pc suite cant detect phone
whats best way to get back to stock please
Click to expand...
Click to collapse
Different question: Did you like the custom pixel rom? Is it worth to change it or should stick to stock rom? What issues you found there?

It's a good ROM the pixel ROM . Nothing up with it at all . I just felt I'd keep it stock . I didn't encounter any problems with it. Each to there own as they say . You may love it . Plenty of tutorials on YouTube reviewing it on note 10 pro

garny68 said:
I put phone into fastboot mode then flashed with the mi flash tool . Obviously I deleted the text out of the file in the tutorial but as I'm up and running on latest firmware would it be safe to say all is good my end ? . I flashed with a fastboot ROM latest one
Click to expand...
Click to collapse
Yes, fine. ARB index should either be same or greater. Since it was same you're safe. All's fine. But be sure to check that index before doing this.

Thanks for that pal

ARB is not present with custom rom (aosp and miui) right ?

garny68 said:
I put phone into fastboot mode then flashed with the mi flash tool . Obviously I deleted the text out of the file in the tutorial but as I'm up and running on latest firmware would it be safe to say all is good my end ? . I flashed with a fastboot ROM latest one
Click to expand...
Click to collapse
May I know the version numbers..