Database Users

updateing to cyanogenmod update-cm-4.2.7.1

Hallo,
I've been trying to install the updated to update-cm-4.2.7.1-signed.zip.
I've been able to install first the signed-dream_devphone_userdebug-ota-14721.zip and imediatly after that, without reboot, the update-cm-4.2.7.1-signed.zip. Only I was unable to sign in to google right after that so I rebooted and then I was unable to boot it any longer...
Ok so then I retried the whole process but now after flashing the first signed-dream_devphone_userdebug-ota-14721.zip, wich goes ok, the second update-cm-4.2.7.1-signed.zip aborts the installation...
Next to it the installation of signed-dream_devphone_userdebug-ota-14721.zip isn't stable at all... after max one minute the phone crashes, so I'm unable to do anything....
I'm feeling extremely NOOOOOOBY!!!...
Which is probably how I'm supposed to feel...
Uuuugh....
Anyways is there anyone with hints about what I'm doing wrong here?
Thanks!
Greetings,
Geert

did u do a full wipe from CM recovery before putting on the google updates then cyanogen??? i had this issue and it fixes it?

Sorry for the late reply...
I tried to flash the recovery image of cyanogen but itś not possible anymore....
There is no flash_image tool on signed-dream_devphone_userdebug-ota-14721.zip...

Also using fastboot, it says < waiting for device > till eternity...

my advice would be to start from scratch, get dreaming.nbh on ur sdcard. follow the instructions @ cyanogens wiki
i was having a world of **** on my G1 and just went back to RC29/RC7 and started again. if you have the files already on the SD card (CM recovery, official google, latest cyanogen mod) its simply a case of a few key presses.
dont forget to do the telnetd stage. i did and then wondered why i didnt have root access lol
ive never bothered with fastboot, usually just use ADB!
r|ktk|ng

[Q] Nexus 10 stuck in boot after attempting root

Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?

Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s

Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.

jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.

Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked

Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.

nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom

tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck

[Q] After 4 1/2 yrs on XDA I am finally stuck! Bricked No download mode, No OS.

Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.

Have you tried to reflash bootloader? If not, do that and reflash cloudy right away

wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?

jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?

euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.

Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?

euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.

My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.

euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...

You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.

Deleted

D802: [720] Fastboot Mode Started

Hi All,
I realise you guys must be sick of these kind of posts but just thought that one of you would be able to point me in the right direction before I do something else wrong!
I was rooted on d802, Cloudy 3.3 with TWP 2.8.6.1 installed. I was trying to get magisk to work but after flashing the various zips etc I left my phone for a few minutes and a toddler came along and swiped the install superSU prompt on TWRP that comes up before rebooting :/:/:/.
So now I am stuck in this "[720] Fastboot mode started". When I plug it into my computer I get a few other things popping up and on device manager it comes up as "Android Bootloader Interface", Device type Kedacom USB Device.
Before messing around with all these things I made a full backup with TWRP so if I can just get back to that I am hoping I will just be able to restore it? At the moment I am unable to get to recovery mode, it just keeps rebooting quickly showing the LG logo and proceeding to fastboot mode. I have tried the holding down power and vol d button but it happens so fast and doesnt seem to do anything.
Where should I go from here? There seem to be a lot of different methods and various things, the more I search the more ways I find!! What is best in my particular situation?
Also could somebody definitively tell me if Magisk will work with cloudy 3.3? I can find no mention anywhere on the internet of someone saying they have done it/got it to work.

amishra123 said:
Where should I go from here?
Click to expand...
Click to collapse
Hi!
This way > http://forum.xda-developers.com/lg-g2/help/fixing-fastboot-mode-started-t2930963
And if it doesn't work I would make this > http://forum.xda-developers.com/lg-g2/help/noob-friendly-recovery-download-mode-t3112805
And you can find a list with all fixes right here > http://forum.xda-developers.com/showpost.php?p=63327417&postcount=4
Good luck!

Thank you very much for your prompt reply !!
I kept trying with the power and volume down and managed to somehow get back into recovery, and then I recovered using the backup!! All back to normal now !
I've since updated to the latest twrp and that all went smoothly aswell.
Any word on whether magisk V9 will work with cloudy g2 3.3 ? I'm tempted to give it another go...
Use the unsu zip , uninstall xposed using the zip , then flash magisk , phh superuser and finally the cbump. I'm really tempted to try again but not sure if it was doing that , that messed it up last time or if it was twrp trying to install super su (Im quite sure it is probably the latter though). Any thoughts ?
EDIT: incase this helps anyone else, I think what I did was to keep the power and vol down held for a long time , if I remember correctly it seemed to cycle a few times through logo and then the fastboot screen until it finally switched off. Prior to this as soon as I thought it was off it would just start again. This time though it went through into the factory reset screen and then recovery.

amishra123 said:
All back to normal now !
Click to expand...
Click to collapse
Nice to here that. :good:
amishra123 said:
Any word on whether magisk V9 will work with cloudy g2 3.3 ?
Click to expand...
Click to collapse
That's a question for the CloudyRom-thread. I bet you're not the first with this question.

Trying to install TWRP and Lineage . . . vbmeta is in the way

I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.

vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!

vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.

Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).

MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it

I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM

I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.

vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.