Database Users

[Q] Milestone 2 - CM11 - Update Failure - Phone not booting up

A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David

Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!

Thanks
Darth said:
Hi,
Your best option is to ask for help in the thread you downloaded the rom from.
Good luck!
Click to expand...
Click to collapse
Thanks. Unfortunately the site won't let me post there. I'm a new member.

Ah, There's no Q&A section. Normally now if you post in a development thread it automatically creates or posts in a thread in your device section Q&A.... But this won't work cause your section has no Q&A.
I will have your thread moved to your devices General section.
Good luck!

More on 'bricked' Milestone 2
datatone said:
A year or two so ago I updated my Motorola Milestone 2 to CyanogenMod, Android 4.1 I think, with no trouble.
I though that I'd take advantage of the CM11 (cm-11-20141003-UNOFFICIAL-milestone2.zip) and I attempted to upgrade to this.
I found that, after booting to the recovery utility, that would not accept this zip file. I noticed that czechop says:
Install my CM10.2 version >= 07.11.2013 first
So I installed cm-10.2-20140312-UNOFFICIAL-milestone2.zip and that went like a breeze. The phone booted up with the new version of Android. I then booted this into the recovery utility and found a new style of this ('Teamworks', I think) with a graphical interface. I found that this liked the cm11 zip file and it installed it without any apparent problem - it reported success and gave me two options - 'clear cache dalvik' (or something very similar), and 'reboot'. I opted for the clear cache, and that seemed to go OK, then I opted for 'reboot'.
This is where my heart sank, because the phone started to boot with the Motorola 'M' logo, then that faded out, then back in, then out. I see no little coloured LED light, and the phone seems to cycle around with the 'M' display, never getting anywhere.
What should I do now? I tried to boot the phone into the original Motorola recovery, holding down the keyboard 'X' key whilst switching on, but that just brings up a little picture of an orange triangle with a '!' in it.
Regards,
David
Click to expand...
Click to collapse
I am going to journal my experiences with this, in the hope that it will be useful to someone else.
Possibly the mistake that I made when flashing the CM11 (see above) is that I didn't put the md5 sum file onto the SD card with the archive. Note that all downloads have a .zip and a .zip.md5sum file. The phone output a message to say that it couldn't find a checksum, but that it was going ahead anyway. Possibly, had I put the md5sum file in, a fault with the zip file would have been detected and I may have been saved from this issue.
I have found references to a 'Motorola factory cable' which is a cable that is wired to persuade the phone not to worry about battery state and to operate the flashing utility from the usb cable power. this is obviously useful in the factory for programming the phone without a battery. See this link for information:
[unfortunately the site didn't allow me to attach a url to 'www dot droidforums dot net' where you might find a posting 'how-why-to-make-your-own-motorola-factory-cable', which is a well-writen and informative article]
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
My technique for putting the archives onto the SD card is to take the card out of the phone and put it into my laptop, so that I can simply manage the files on it with standard Windows file browser.
I can get to a very promising recovery utility by holding down the 'X' key on the keyboard whilst switching the phone on. The Motorola 'M' logo comes up and the screen then displays a 3D orange triangle with an exclamation mark and a little green Android man. If I press the keyboard '@' at this point, I jump into a recovery menu.
The recovery menu has options:
* 'reboot system now'
* 'apply sdcard:update.zip'
* 'wipe data/factory reset'
* 'wipe cache partition'
The 'apply sdcard:update.zip' seems to offer the promise of recovery.
I have tried placing both:
* cm-10.2-20140312-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
and
* cm-11-20141003-UNOFFICIAL-milestone2 (.zip and .zip.md5sum)
onto the sdcard (renamed as 'update.zip' and 'update.zip.md5sum').
In both cases the recovery utility says:
---
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
-- Install from sdcard...
Finding update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
---
If I remove the update.zip.md5sum file, the result is identical. Therefore I don't think that this utility is using the md5sum for archive file verification. The problem that I seem to have at the moment is that I need an archive in the right format for the factory recovery utility.
I will be researching this and will add to this thread when I find an answer.
As a little bit of extra information, whilst fiddling about with the buttons during power up, I did manage to get a screen that said:
---
Bootloader
70.12
Battery OK
OK to Program
Connect USB
Data Cable
---
I guess that this is a lower stage in the bootloader chain, and suggests that there is hope if your phone is screwed up to the extent that you can't get the factory recovery utility. Thankfully, I don't seem to need to investigate what is required at the PC end to make use of this low level programming aid. (If anyone knows, it would be good to hear the details, for future reference and help to others).
Alas, I'm not sure what I did to bring this screen up - I fiddled with the volume, camera, and power buttons whilst the phone was starting up.
Regards,
David

Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.

Progress
rabinhood said:
Hello.
1. You don't need no 'factory cable'. All you need to come back to stock ROM is PC, RSDlite software, generic USB<->micro USB cable, and a stock ROM sbf file. The question what to do with a bricked phone was answered here plenty of times. Almost always the best way to bring a dead phone back to life is to flash a stock ROM (with bootloader version >= of version of current one).
2. You seem to have an older bootloader (the latest is 70.13 included in Ginger Bread ROMs), but you don't have to flash a newer one. Just remember, that bootloader is locked and cannot bet downgraded, so if you flash a newer one, you will never be able to flash generic ROMs with an older version. For example after I flashed 70.13 GB, a was unable to flash Froyo ROM over it (but you'll still be able to flash Froyo based CM7 with some tricks).
3. If you can access TeamWinRecovery (the graphicac one), you can simply clear system/cache partitions, and flash any custom ROM zip (for example Czechop's 10.2).
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key). What you can do there is try to clear cache/data (factory reset). Sometimes some information in /data is preventing ROM from booting, if you changed ROM.
5. What You described is called a 'bootloop' - rebooting endlessly.
Click to expand...
Click to collapse
Thank you very much. I have spent all day researching this.
I have discovered 'RSD Lite' and the ability to get the phone into the bootloader mode that I described by starting the phone and keeping the camera and volume buttons pressed.
I can boot to the stock recovery mode by powering up with the 'X' key pressed and then pressing '@'
I don't think that I can access TeamWinRecovery. There may be some way to do this that I don't know.
I did do a complete 'Nandroid?' backup of the system before I started this, so I guess that if I can get TeamWinRecovery or clockworkmod recovery back, I can restore to my previous working state.
What I have tried is 'G.O.T.’s OpenRecovery' to get a recovery installed. I put the OpenRecovery folder and the update.zip onto the SDcard and tried to flash it with the stock recovery utility. I got the "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. I read that this means that I am not properly rooted (I thought I was) and I need to install 'vulnerable recovery' using an sbf file and RSD Lite. I have tried 'vulnerable_recovery_only_RAMDLD90_78.sbf' but the process errors, and what I read suggests that this might be due to the older bootloader version.
I tried to find an old stock android sbf for the phone, but all the links to such things seem to be dead.
I did try the factory reset from the stock recovery as a means to fix the bootloop. It didn't work.
You clearly know a lot about this. I would appreciate help to get back to something that works, maybe the last backup that I did.
I am also puzzled by why the upgrade to the CM11 from the CM10.2 failed. Did I do something wrong, or is there some compatibility issue with my phone? I never had a problem updating from the original motorola software to the cyanogenmod, then to the CM10.2.
I think I became a little over-confident.
Thank you in anticipation,
David
---------- Post added at 06:20 PM ---------- Previous post was at 05:59 PM ----------
rabinhood said:
Hello.
4. The stock recovery (with an exclamation mark, then you press both vol up and down to access menu) doesn't allow to flash unsigned zip images (and none of custom ROMs is signed with Motorola key).
Click to expand...
Click to collapse
Ah! the penny drops. The stock recovery that I can access will only install archives signed by Motorola. Hence the signature errors that I get when I try anything else. So I understand that if I can only get to the stock recovery, I can only use it to reinstall a stock android.
So the problem is where to find a stock sbf file to reinstall Motorola android as a first step to getting back to CM.
I guess that this is the only way to get back to clockworkmod recovery or teamwin recovery?
If I can get one of these recoverys running, I can simply restore to the last working system, I guess?
Regards,
David
---------- Post added at 07:07 PM ---------- Previous post was at 06:20 PM ----------
david.datatone said:
My phone is in a state that the charger will operate to charge the battery as normal when the charger is plugged in with the phone off. It still shows the image of a battery filling up. Therefore I can keep my battery in good condition between recovery attempts, and I don't think I'll need any special cables.
Click to expand...
Click to collapse
I realise that I was mistaken about this. There is no image of a battery filling up. The white LED by the USB socket lights when the charger is plugged in, but I can't be sure that the battery is charging.

Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.

1000 Thanks
rabinhood said:
Are you sure you're trying to flash a proper recovery? I remember there was a 'vulnerable recovery' for milestone 1, but no such thing for MS2. As you wrote, signature errors while trying to flash zips from stock recovery are due to lack of Motorola signature, not to problems with root. Root access has nothing to do with recovery, it is something much later/higher in system.
So again, what to do to unbrick the MS2:
1. Get a stock ROM - I suggest lates European one with 70.13 bootloader. There are also later Latin America ROMs, but they lead to more problems with custom ROMs. SBF's were published somewhere in these forums. If you cannot find them, write, and I'll upload one to some file sharing servers if I have time (I'll be staying at work for next 30 hours or so).
2. Get RSD lite and latest Motorola USB drivers (they're on the web), install. Before flashing remember you cannot use an USB 3 port - the best way is to turn USB 3 support off in computer BIOS.
3. Enter the flash mode in MS2. Connect is with generic USB cable to PC.
4. Run RSD lite, flash SBF, wait until phone reboots - it can take several minutes. If it freezes - try to enter stock recovery and wipe data/cache.
After these steps you should have a clear installation of stock ROM. Then you have to root, install Droid2 Bootstrap, install CM 10 or 10.1 -> 10.2 -> 11. If you have problems with these, write, and I'll write more detailed instructions.
PS. By the way, to enter TWR or CWM recovery you have to press vol down while a blue led is lit for a short time during reboot.
Click to expand...
Click to collapse
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David

david.datatone said:
I can't thank you enough. I'm currently downloading your stock ROM. I already have what I think is the latest verion of RSD Lite (6.1.6) installed on my Windows 8.1 laptop (I've read about problems with more contemporary versions of Windows, but I have successfully connected to the phone before now, just haven't had joy with flashing the file that I tried). I am fingers crossed that all will go well, and I'll certainly note that here. Otherwise I very much appreciate your offer of further help.
Bets regards,
David
Click to expand...
Click to collapse
recommend you return the original rom using RSDlite and start doing it all over again putting the rom CM10 and then cm11

[Q] OS fail (stopped working) on every app at boot up

Hello guys,
I got myself in a big problem trying to change the SuperUS app that go installed with [GT-I9500] CF-Auto-Root method.
I was able to root my S4 i9500 following the "[GT-I9500] CF-Auto-Root" threat a few days ago and everything was good.
Then for some reason (I still want to remember what was the reason) I decided to change the superUS app with Superuser clockworkmod app (I am a noob and I deserve this I know). anyway I downloaded the other app from google play and when I opened it say it has to instal the binaries, I said ok and the phone reset and went directly to download mode I believe.
It was doing something but whatever it did it failed. So I said ok not big deal I will reset the phone and end of story. However now when I boot up the phone when it passes the samsung logo and start to load up the OS every single app fails to load, "unfortunaly xxxxx has stopped" I press ok and then it goes to the next "unfortunaly yyyyyy has stopped" and the next and the next and the OS never loads. The screen just remain black until I press power and gave me the option to power off, reset, airplane mode, etc.
IS there a way to fix o revert this. I am able to get to download mode but ODIN does not detect the phone (odin detects the phone when the phone is in normal mode tho???)
I am able to get to the stock recovery too. Can i fix this from sd card?
any guidance would be appreciated.

بلتبمبامبيس
أرسلت من sm-g530h بإستخدام تاباتلك

eyaker said:
Hello guys,
I got myself in a big problem trying to change the SuperUS app that go installed with [GT-I9500] CF-Auto-Root method.
I was able to root my S4 i9500 following the "[GT-I9500] CF-Auto-Root" threat a few days ago and everything was good.
Then for some reason (I still want to remember what was the reason) I decided to change the superUS app with Superuser clockworkmod app (I am a noob and I deserve this I know). anyway I downloaded the other app from google play and when I opened it say it has to instal the binaries, I said ok and the phone reset and went directly to download mode I believe.
It was doing something but whatever it did it failed. So I said ok not big deal I will reset the phone and end of story. However now when I boot up the phone when it passes the samsung logo and start to load up the OS every single app fails to load, "unfortunaly xxxxx has stopped" I press ok and then it goes to the next "unfortunaly yyyyyy has stopped" and the next and the next and the OS never loads. The screen just remain black until I press power and gave me the option to power off, reset, airplane mode, etc.
IS there a way to fix o revert this. I am able to get to download mode but ODIN does not detect the phone (odin detects the phone when the phone is in normal mode tho???)
I am able to get to the stock recovery too. Can i fix this from sd card?
any guidance would be appreciated.
Click to expand...
Click to collapse
Try to save all your internal data to your pc (conected the device on your pc when the screen of your device just remain black) and then:
1. Go to Stock Recovery.
2. Select Wipe data/Factory Reset. Volume buttons for move and Power button for select. Select "Yes--delete all user data".
3. "Reboot system now" option.
4. Done. Tell me if it worked

mshajryi said:
بلتبمبامبيس
أرسلت من sm-g530h بإستخدام تاباتلك
Click to expand...
Click to collapse
Mod Edit
May I remind you of the XDA RULES
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Thank you
malybru
Forum Moderator

Yoga Tablet 2 - 1050F Lollipop Ota - Return to stock KK

I captured the lollipop update that came out today. I have a nandroid backup and I'm going for the update. We will see if the new tethered CWM works to get root back... Stay tuned.
Turns out rooted users will need to return the tablet to KitKat stock. I found this info in 2-3 places in various languages. Here is hopefully a clear step-by-step to get back to KK stock and then take the OTA.
This can BRICK your device, so use at your own risk. Files are supplied as a courtesy and not mine
1) Download - This - AFH - kitkat-YT2-1050F_S0198_150422_ROW.7z (This updated readme file here)
2) Extract the zipfile to a directory on PC somewhere
3) Goto "tools" folder and install the exe's in this order
a) PhoneFlashTool_4.4.4.1_external_win32.exe​b) iSocUSB-Driver-Setup-1.2.0.exe​c) IntelAndroidDrvSetup1.5.0.exe​4) Start PhoneFlashTool and select settings (Upper left corner)
5) Tick "force sparcing" and change size to 500mb
6) Power off tablet and connect with usb
7) From off, hold volume up and power until tablet vibrates and release power (still holding volume up)
8) Tablet should now be in "Droidboot" and PhoneFlashTool should list it on the top
9) In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
10) WAIT!!! until you see "Result okay" on tablet AND "Flash Sucess" in PhoneFlashTool
11) Reboot
12) When Android starts skip all dialogs (tablet is going to factory reset anyway)
13) Select Contacts from desktop and make 1 dummy contact
14) In the search bar type "####6020#" and then select your country
15) Tablet reboots and you are on stock KitKat again and should receive an update notice for Lollipop
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2

i got the 830F Update today, But i got Problems!
830F Update Log:
- It stays for 8min. at 100%. I leave it alone...
- Then 4 chinese Buttons showed up.
- I pressed the first (reboot i think)
- it reboots, it shows the white lenovo text, then black screen with background light on.
- i waited 10min., no change or start into OS.
- then i pressed 15sek power off, light goes off.
- if i power on, again white lenovo text, then black screen with background light on. nothing... ???
- i reboot into recovery and wiped cache, nothing.
i think i will make update from SD card again... see if something happend
Edit: Update from SD dont work! it says:
"/system/app/Chrome.apk" has unexpected contents...
E: Error in /sideload/package.zip
830F Update Log END

5m00v3 said:
i got the 830F Update today, But i got Problems!
830F Update Log:
- It stays for 8min. at 100%. I leave it alone...
- Then 4 chinese Buttons showed up.
- I pressed the first (reboot i think)
- it reboots, it shows the white lenovo text, then black screen with background light on.
- i waited 10min., no change or start into OS.
- then i pressed 15sek power off, light goes off.
- if i power on, again white lenovo text, then black screen with background light on. nothing... ???
- i reboot into recovery and wiped cache, nothing.
i think i will make update from SD card again... see if something happend
Edit: Update from SD dont work! it says:
"/system/app/Chrome.apk" has unexpected contents...
E: Error in /sideload/package.zip
830F Update Log END
Click to expand...
Click to collapse
Are you rooted? If so you need to "unroot". That can be done as simply as going into the settings of SuperSU and selecting - full upnroot. Or you may need to flash back to original stock...

Have you done the Update without problems?
Can i flash back original 4.4.2 without brick my YT2?
Edit: i have no ROOT

5m00v3 said:
Have you done the Update without problems?
Can i flash back original 4.4.2 without brick my YT2?
Edit: i have no ROOT
Click to expand...
Click to collapse
It keeps failing. I'm going to try flashing the original firmware, but probably not until the weekend. I have too much on my plate to deal....

SUCCESS, LOLLIPOP IS WORKING!!!
I Have restored original KitKat ROM via "PhoneFlashTool" with this ROMs / Tutorial:
http://www.android-hilfe.de/thema/tu...ianten.697884/
This time i´ve made the "Country Setting" via ContactApp ####6020# to "DE" befor download and upgrade!
And i have aborted the automatic PlayStore updates for Chrome etc...
Lollipop upgrade reboots into recovery and stays 5min. at 100%.
Then reboots into some intel-flash mode and stays for 4min.
After it reboots into Lollipop OS...

I have the same problem, only that I had the first Lollipop version for 1050F with root and then got the new Lollipop update. The Kitkat version fails to flash. But here is what helped:
Go to this post
http://forum.xda-developers.com/thi...-8-10-13-3-t2930428/post60490907#post60490907
and download the LtoKKxml.7z and copy the files into the kitkat firmware folder and then flash using flash-LtoKK-PVT-810.xml
I had to remove the parts of the XML that erase and format data. Then it worked
After that I could flash KitKat!!

@ matshias
thx, good to know...

5m00v3 said:
SUCCESS, LOLLIPOP IS WORKING!!!
I Have restored original KitKat ROM via "PhoneFlashTool" with this ROMs / Tutorial:
http://www.android-hilfe.de/thema/tu...ianten.697884/
This time i´ve made the "Country Setting" via ContactApp ####6020# to "DE" befor download and upgrade!
And i have aborted the automatic PlayStore updates for Chrome etc...
Lollipop upgrade reboots into recovery and stays 5min. at 100%.
Then reboots into some intel-flash mode and stays for 4min.
After it reboots into Lollipop OS...
Click to expand...
Click to collapse
matshias said:
I have the same problem, only that I had the first Lollipop version for 1050F with root and then got the new Lollipop update. The Kitkat version fails to flash. But here is what helped:
Go to this post
http://forum.xda-developers.com/thi...-8-10-13-3-t2930428/post60490907#post60490907
and download the LtoKKxml.7z and copy the files into the kitkat firmware folder and then flash using flash-LtoKK-PVT-810.xml
I had to remove the parts of the XML that erase and format data. Then it worked
After that I could flash KitKat!!
Click to expand...
Click to collapse
Well, I got as far as extracting the original kk firmware, installing Intel phone tool and drivers with no problems. My issue is the tablet is recognized by the Intel phone tool while the tablet is in Android but when I reboot to fastboot it isn't.
This is in a virtual machine because I don't do Windows on hardware, only VirtualBox.
I may have to take an old rig and install Windows temporarily...
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2

VitualBox maybe a problem, but why it works when in Lollipop OS and not in droidboot?
Firewall? ADB in developer-options enabled?
Try check your device manager in fastboot-mode if there is some "Unknown device" and install ADB driver...

5m00v3 said:
VitualBox maybe a problem, but why it works when in Lollipop OS and not in droidboot?
Firewall? ADB in developer-options enabled?
Try check your device manager in fastboot-mode if there is some "Unknown device" and install ADB driver...
Click to expand...
Click to collapse
Yea, I got it to work through VB. I went to upgrade and the upgrade failed and now it won't boot.
I'm going to try flashing the KK firmware again.
Edit: Flashing again now...

workdowg said:
Yea, I got it to work through VB. I went to upgrade and the upgrade failed and now it won't boot.
I'm going to try flashing the KK firmware again.
Edit: Flashing again now...
Click to expand...
Click to collapse
Lollipop won't update for me. I had a TWRP backup so I am right back where I was. Could it be the "country code" I saw in the instructions? If so what is the dial code for US? us?Duh, it brings up a selection box... Chinese but readable.

workdowg said:
Lollipop won't update for me. I had a TWRP backup so I am right back where I was. Could it be the "country code" I saw in the instructions? If so what is the dial code for US? us?Duh, it brings up a selection box... Chinese but readable.
Click to expand...
Click to collapse
Guess that was it.. Updating to Lollipop now.

workdowg said:
Guess that was it.. Updating to Lollipop now.
Click to expand...
Click to collapse
I am glad that you made it!
So ROOT next?

5m00v3 said:
I am glad that you made it!
So ROOT next?
Click to expand...
Click to collapse
Root - no problem - Trigger 4

Update successful to YOGATablet2-1050F_S100067
Mine was a pleasant suprise.
LenovoPad YOGA Tablet 2-1050F
I already had installed Lollipop YOGATablet2-1050F_S100031 and rooted.
When advised there was a new OTA update, I did the following:
1. From within SuperSU Pro settings "Full unroot"
2. Reboot
3. Connect to PC
4. Run Lenovo Smart Assistant
5. Update was available, which downloaded to my PC
6. Lenovo Assistant began to transfer the update to the tablet, but ultimately (2 mins?) reported "Update failed"
7. Disconnected tablet from PC and turned it off
8. Simultaneously pressed volume down and power button, released volume key on vibration
9. Black screen quickly followed by the Android icon processing the update
10. Update successful to YOGATablet2-1050F_S100067
11. All data intact
12. Re-rooted using T4 (above.)
One happy camper! :laugh:
Oh, and Xposed-v67-sdk21-x86.zip successfully installed with this version!

workdowg said:
I captured the lollipop update that came out today. I have a nandroid backup and I'm going for the update. We will see if the new tethered CWM works to get root back... Stay tuned.
Turns out rooted users will need to return the tablet to KitKat stock. I found this info in 2-3 places in various languages. Here is hopefully a clear step-by-step to get back to KK stock and then take the OTA.
This can BRICK your device, so use at your own risk. Files are supplied as a courtesy and not mine
1) Download - This - AFH - kitkat-YT2-1050F_S0198_150422_ROW.7z (This updated readme file here)
2) Extract the zipfile to a directory on PC somewhere
3) Goto "tools" folder and install the exe's in this order
a) PhoneFlashTool_4.4.4.1_external_win32.exe​b) iSocUSB-Driver-Setup-1.2.0.exe​c) IntelAndroidDrvSetup1.5.0.exe​4) Start PhoneFlashTool and select settings (Upper left corner)
5) Tick "force sparcing" and change size to 500mb
6) Power off tablet and connect with usb
7) From off, hold volume up and power until tablet vibrates and release power (still holding volume up)
8) Tablet should now be in "Droidboot" and PhoneFlashTool should list it on the top
9) In PhoneFlashTool click browse and select flash.xml from the "target_bin" folder
10) WAIT!!! until you see "Result okay" on tablet AND "Flash Sucess" in PhoneFlashTool
11) Reboot
12) When Android starts skip all dialogs (tablet is going to factory reset anyway)
13) Select Contacts from desktop and make 1 dummy contact
14) In the search bar type "####6020#" and then select your country
15) Tablet reboots and you are on stock KitKat again and should receive an update notice for Lollipop
From my LG-G3 running Jasmine8.0/Skydragon Kernel 4.2
Click to expand...
Click to collapse
Thanks a lot for your description. I've been postponing this for a long time. I finally did the upgrade today. 100% successful.

HELP!!! Phone not booting and vibrating continuously after short intervals

I was trying to flash a custom ROM in my Lenovo A6000. I rooted the phone with KingRoot. Then using Rashr I flashed the twrp img. I went to recovery and then I made a backup using TWRP's Backup option. I rebooted the phone and again went to recovery Then tapping the Wipe option I went toAdvanced Wipe where I checked the boxes next to Data, System, Cache, Dalvik. After that I went to the Install option where I chose the ROM.zip file from the sd card. The installation failed, I tried to install again but it failed again ( I must have had a bad copy of the file ). Since I had already wiped the system I went to the Restore option, chose the backed up file to restore. The restore was successful. But when I tapped the Reboot button after a couple of seconds the device screen went off and the phone kept on vibrating continuously after short intervals. I tried pressing the POWER button for a long time--> keeps on vibrating. I tried going to recovery by pressing the hardware keys--> still keeps on vibrating. I tried connecting to the computer after taking out the battery and replacing it. NOthing seems to work. It keeps showing the same problem. Please Help...

Abhishek Hamal said:
I was trying to flash a custom ROM in my Lenovo A6000. I rooted the phone with KingRoot. Then using Rashr I flashed the twrp img. I went to recovery and then I made a backup using TWRP's Backup option. I rebooted the phone and again went to recovery Then tapping the Wipe option I went toAdvanced Wipe where I checked the boxes next to Data, System, Cache, Dalvik. After that I went to the Install option where I chose the ROM.zip file from the sd card. The installation failed, I tried to install again but it failed again ( I must have had a bad copy of the file ). Since I had already wiped the system I went to the Restore option, chose the backed up file to restore. The restore was successful. But when I tapped the Reboot button after a couple of seconds the device screen went off and the phone kept on vibrating continuously after short intervals. I tried pressing the POWER button for a long time--> keeps on vibrating. I tried going to recovery by pressing the hardware keys--> still keeps on vibrating. I tried connecting to the computer after taking out the battery and replacing it. NOthing seems to work. It keeps showing the same problem. Please Help...
Click to expand...
Click to collapse
First of all " don't panic ", its nothing. First remove your battery and then insert it. Now press "VOL UP + VOL DOWN + POWER KEY" together and leave the " POWER KEY " once the lenovo logo shows up. You'll enter into recovery. Now, wipe the cache, dalvik and reboot. If still doesn't boot, then wipe data, android secure too (not system). This will surely do.
And, mention the error you faced while installing the new ROM, like Error 6 or anything. If you were on stock kk earlier, then to flash Lollipop ROMs, you'll have to flash stock LP ROM first.

sasukay said:
First of all " don't panic ", its nothing. First remove your battery and then insert it. Now press "VOL UP + VOL DOWN + POWER KEY" together and leave the " POWER KEY " once the lenovo logo shows up. You'll enter into recovery. Now, wipe the cache, dalvik and reboot. If still doesn't boot, then wipe data, android secure too (not system). This will surely do.
And, mention the error you faced while installing the new ROM, like Error 6 or anything. If you were on stock kk earlier, then to flash Lollipop ROMs, you'll have to flash stock LP ROM first.
Click to expand...
Click to collapse
I had tried that too. But the only response I get are those continuous vibrations. The screen does not light up at all. No, its not a display problem. I can't do anything with the phone, can't enter recovery. The only response to whatever I do plug in power supply, press the power key, press the key combination to go into recovery, plug into laptop and such are those vibrations.

Abhishek Hamal said:
I had tried that too. But the only response I get are those continuous vibrations. The screen does not light up at all. No, its not a display problem. I can't do anything with the phone, can't enter recovery. The only response to whatever I do plug in power supply, press the power key, press the key combination to go into recovery, plug into laptop and such are those vibrations.
Click to expand...
Click to collapse
Can you enter fastboot by pressing vol down + power key..?

No. I can't. As I said, the only response I get from the phone is those vibrations. No matter what I do.
Sent from my Micromax Q380 using XDA-Developers mobile app

Abhishek Hamal said:
No. I can't. As I said, the only response I get from the phone is those vibrations. No matter what I do.
Sent from my Micromax Q380 using XDA-Developers mobile app
Click to expand...
Click to collapse
Follow THIS TUTORIAL and first try the third method. If that doesn't work then try the second one.

sasukay said:
Follow THIS TUTORIAL and first try the third method. If that doesn't work then try the second one.
Click to expand...
Click to collapse
after vol down + Power connect with usb cable
dowload https://drive.google.com/open?id=0B8jgOvQH8xoaSDJ5RTQ2Qi1Ib0U
and run "fix brock device And Partations And every thing.bat"

Same problem with me, I was browsing facebook and suddenly my phone's screen blacks out. I can access recovery ,my device is detected by PC normally and can access all files, but display blacks out and I cannot see anything.
If I boot phone normally, It starts vibrating periodically. Maybe, because of Bootloops.
(Funny thing is, I can feel everything but cannot see anything on my phone)

Which version of Android was before?

sasukay said:
Follow THIS TUTORIAL and first try the third method. If that doesn't work then try the second one.
Click to expand...
Click to collapse
I am telling you, it's not working. Thanks for your help though.
Sent from my Micromax Q380 using XDA-Developers mobile app

Abhishek Hamal said:
I am telling you, it's not working. Thanks for your help though.
Sent from my Micromax Q380 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you installed the Qualcomm drivers mentioned in that post..? And was your device listed in Device Manager on pc, as "Qualcomm Predloader stuff..."... ??

I've experienced the same problem. I simply headed to the service centre ang got my display changed for free.(as under warranty)
Sent from my Lenovo A6000 Plus

in my experience, if your PC can recognize the device as qualcom.. you should go with the file.
if your device still vibrating countinuosly.. you should do test point
if test point not working. please go to lennove service center.

I also faced that problem when doing an ota update of MiUi and the I had to change the motherboard . Since it was under warranty I got it replaced for free.

did you got any solution
Abhishek Hamal said:
I was trying to flash a custom ROM in my Lenovo A6000. I rooted the phone with KingRoot. Then using Rashr I flashed the twrp img. I went to recovery and then I made a backup using TWRP's Backup option. I rebooted the phone and again went to recovery Then tapping the Wipe option I went toAdvanced Wipe where I checked the boxes next to Data, System, Cache, Dalvik. After that I went to the Install option where I chose the ROM.zip file from the sd card. The installation failed, I tried to install again but it failed again ( I must have had a bad copy of the file ). Since I had already wiped the system I went to the Restore option, chose the backed up file to restore. The restore was successful. But when I tapped the Reboot button after a couple of seconds the device screen went off and the phone kept on vibrating continuously after short intervals. I tried pressing the POWER button for a long time--> keeps on vibrating. I tried going to recovery by pressing the hardware keys--> still keeps on vibrating. I tried connecting to the computer after taking out the battery and replacing it. NOthing seems to work. It keeps showing the same problem. Please Help...
Click to expand...
Click to collapse
i am also facing same problem , after installing nought rom successfully , i rebooted but it doesnot boot nor going to recovery or download mode , earlier i have unbricked using qcom downloader 2 times succesfully. but this time it won't go to download or recovery mode, not dectecting on pc . Now is there any solution

I am facing exact same problem.... but no one does help .Did you find any solution?
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
aravindmj said:
I also faced that problem when doing an ota update of MiUi and the I had to change the motherboard . Since it was under warranty I got it replaced for free.
Click to expand...
Click to collapse
O MY GOD DONE EXACT SAME THING. How dumb I am. But there is no solution out there?, I don't want to pay the cost of the phone again for motherboard replacement

XTutorials said:
I am facing exact same problem.... but no one does help .Did you find any solution?
---------- Post added at 11:53 AM ---------- Previous post was at 11:51 AM ----------
O MY GOD DONE EXACT SAME THING. How dumb I am. But there is no solution out there?, I don't want to pay the cost of the phone again for motherboard replacement
Click to expand...
Click to collapse
Don't know any other way bro!

aravindmj said:
Don't know any other way bro!
Click to expand...
Click to collapse

FIX!
I have found a way to unbrick the phone with these simptoms! Check my guide in the guides section!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
aravindmj said:
I also faced that problem when doing an ota update of MiUi and the I had to change the motherboard . Since it was under warranty I got it replaced for free.
Click to expand...
Click to collapse
I HAVE FOUND A WAY TO UNBRICK THE PHONE WITH THESE SIMPTOMS! CHECK MY GUIDE IN THE GUIDES SECTION!
Too bad you replaced it. At least was in warranty

same problem
Abhishek Hamal said:
I was trying to flash a custom ROM in my Lenovo A6000. I rooted the phone with KingRoot. Then using Rashr I flashed the twrp img. I went to recovery and then I made a backup using TWRP's Backup option. I rebooted the phone and again went to recovery Then tapping the Wipe option I went toAdvanced Wipe where I checked the boxes next to Data, System, Cache, Dalvik. After that I went to the Install option where I chose the ROM.zip file from the sd card. The installation failed, I tried to install again but it failed again ( I must have had a bad copy of the file ). Since I had already wiped the system I went to the Restore option, chose the backed up file to restore. The restore was successful. But when I tapped the Reboot button after a couple of seconds the device screen went off and the phone kept on vibrating continuously after short intervals. I tried pressing the POWER button for a long time--> keeps on vibrating. I tried going to recovery by pressing the hardware keys--> still keeps on vibrating. I tried connecting to the computer after taking out the battery and replacing it. NOthing seems to work. It keeps showing the same problem. Please Help...
Click to expand...
Click to collapse
i'm also dealing with the same problem whether you fixed it or not if you did please tell me what to do????? plzzz help me....

How to: install TWRP 3.1.1 [SM-T520]

i'm not responsible for anything that goes wrong!
Everything happens at your own risk!
Installing the latest TWRP version (3.1.1.1-0) seems to be a problem on this tablet in some cases, I also had some.
But after some time I found a way to install it.
However, this requires a Windows computer with admnistrator rights and a USB cable to connect the tablet to the PC.
As mentioned above, I'm not responsible for anything that doesn't work as desired or makes the tablet useless! Everything is your responsibility, and I can't promise that it will work for everyone. All I can say is that it worked out for me without any problems.
I anticipated root! If the device is not rooted yet, click here!
First, we need to make some preparations.
Install Samsung Drivers from here
Download "Odin" from here and unpack it.
Download the latest TWRP version, from here.
YOU HAVE TO DOWNLOAD THE "*. TAR"-FILE!
Plug the USB cable into your computer and enjoy it.
(Really, plug it in!)
Let's begin:
1. enable Android debugging from the developer settings at your tablet
2. start "Odin" at your Windows PC and disable "auto re-boot" in the options tab (on the left side)
3. turn off your tablet
4. If it's off, hold the volume-down button, home button and the power button of your device until it shows a warning, press Volume-up to accept booting in "download mode" (starts in "download mode" now)
5. plug the USB cable into your device
You should now see the message that a device has been plugged in in the "Log"-tab of "Odin".
6. tick in "Odin" the box in front of the "CP-button".
7. click on the "CP-button" in "Odin"
8. now select the TWRP file (file extension ". tar"!!) you downloaded before
9. Click on "Start" in "Odin".
The "Log"-tab should now show the message that the installation has started.
After a short time the message (if everything has been done correctly) is displayed that the installation was successful.
Now start the recovery on your device, BEFORE booting the system again (That could take a few seconds, don't get nervous immediately).
TWRP 3.1.1-0 should now be shown.
Congratulations, you have installed the latest TWRP version! :good:
If you have any questions or problems please do not hesitate to contact me. Just leave a comment!
Have a nice day!

So far is your guide alright.
Important thing, disable autoreboot on Odin.
After flashing , boot manualy with the 3 Buttons into the Recovery, if the Tab boot into system it is possible that the Stockrecorvery will restore.

Yep, forgot that point.
I will edit my post.
Thanks!

Is there any benefit in updating TWRP to the latest version?
I only use it to backup current state then flash a ROM...which had become a very rare thing on our device.
But thanks for this tutorial!

In the new version bugs were fixed.
For example the "reboot after flashing" button works fine now.

I'm sticking with 3.0.2 and recommend other to do the same. Newer versions have problems! Version 3.1.0 never even booted for me and this 3.1.1 always cause random reboots while using it.

Oh, I'm sorry to hear that.
I never experienced something like this.
On my tablet is Lineage OS 14.1 installed without problems.

hello
3.1.x installed:
boot extralong
impossible to install os completely (apps)
impossible to install opengapps commplletely
back to 3.0.x
regards

Oh, I'm sorry.
Tried it on the discribed way, worked without problems, for others too.

Thanks for that tip. I found I was getting the same problem with 3.1.1

Rapha88 said:
I'm sticking with 3.0.2 and recommend other to do the same. Newer versions have problems! Version 3.1.0 never even booted for me and this 3.1.1 always cause random reboots while using it.
Click to expand...
Click to collapse
I'll second that.
I started with TWRP 3.1.1 but couldn't do a backup: Experienced random reboots during backup.
Rolled back to TWRP 3.0.2 and could then complete a backup.
Don't know if relevant, but with 3.1.1 I saw CPU temperature go above 80 degrees C. With 3.0.2 CPU temperature never got above 73 degrees C, even when doing a compressed backup.

Hi, I can't get into recovery after trwp installation. What is the right key combination? Does anyone have 3.0.2.0 image.tar?

telnet05 said:
Hi, I can't get into recovery after trwp installation. What is the right key combination? Does anyone have 3.0.2.0 image.tar?
Click to expand...
Click to collapse
Power off, then hold the Home key + Volume Up, then press Power (Home key + Volume Down gets you into Download mode instead).

Nice..thanks!!!

In Odin CP-Button is for (Core Processor): We call it Modem? In old Odin version we used PDA, AP (Application Processor or PDA): Android Why don't used AP now? Thanks.
@JanHolst
Uncheck compression and no reboots during backup.

@JanHolst
Uncheck compression and no reboots during backup.[/QUOTE]
Thanks for the suggestion. I actually did that, since I thought that would prevent the CPU temperature from getting too high. It still rebooted halfway through the backup though.

I'm getting the same issue, random rebooting through either an installation or recovery process. This started immediately after I had updated to latest version. Any guidance about how to roll back ? Odin?

I installed the latest version of Odin (3.12), and reinstalled my original version of TWRP 3.1.1-0, following the instructions above. However, I continue to have the random reboot during installation or recovery. Any other suggestions? Install an older version?

hi
i have installed twrp on sm-t520 when i try to backup files it restarts to the system as anybody had this issues if so
how do i fix it
from oliver

Can you please address this someone need help