When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
vespa70 said:
When I try to uppgrade with cm12.1 and others, I always
get "signature can't veryfy....", and then reboots.
What iis wrong? I'm new at this so I need some
guide please.
Click to expand...
Click to collapse
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
RAZERZDAHACKER said:
Welcome to the Android comuntiy!
I will try to guide you step by step on how to get your phone rocking cyanogenmod 11 (cm11 is kitkat but it is the same procedure for any other ROM, just replace the cm11 file cm12)
What you'll need;
The CyanogenMod ROM
A custom recovery, otherwise you'll get the signiture verification error
ROOT!
Adb and fastboot
adb drivers
Google Apps
-------------------------
We are going to use The custom recovery I provided in this post and not the one provided in the description of the video. The steps below is assuming that you have succesfully rooted your device and have enabled usb debugging and authorized your pc.
-------------------------
1. Connect your phone to your pc, wait for the drivers to install and once they have installed continue on.
2. Click start and open devices and printers, you should see your device, right-click it and hit properties and then you should see different "devices", choose the one who has a type from SAMSUNG and then up next to the corners you should see 2 options, general and one more, hit the second one and hit properties at the bottom right.
3. It should open a new window, in that window there is and option to change setting, click it then select drivers at the top and hit update.
4. Click choose an update already availible on the computer, then click let me pick and wait.
5. Then there is an option to choose compatible drivers or something like that and make sure it is not ticked! Find a driver from ClockworkMod and to the right you should see android adb interface, click it and hit install after that is complete you should have the adb drivers.
6. Open minimal adb and fastboot that you downloaded and type "adb devices" and wait, it should show your device and you might get a popup window on your phone saying to authorize the pc, hit always trust and hit allow and your device should be seen in adb and it should say device next to the serial number.
7 Turn off your phone.
8. Boot into recovery by pressing power + volume up + home button.
9. Click advanced
10. Click adb sideload and make sure that when you type adb devices in minimal adb and fastboot you should see your device and it should say sideload next to the serial number. If you don't, repeat the steps for installing the drivers just this time do it in adb sideload mode.
11. Once you got the driver working in adb sideload you should press the home button and click wipe, then select advanced wipe and select, dalvik, system, data, internal storage, cache and preload. This will wipe your data!
12. Once that is done go to adb sideload and connect your phone to the pc.
13. Move the downloaded ROM to the minimal adb and fastboot folder adn then in the command line type adb sideload <filename>. DON'T REBOOT!!!
14. Once flash is done it is time to move the google apps to the minimal adb and fastboot, remember, DON'T REBOOT!!
15. Type adb sideload <googelappsfilename>. Wait till it is done and now you can finally reboot.
--------------------
It should boot perfectly, remember, the first time boot might take a lot of time and the device might overheat but just leave it there for a couple of mnutes until it boots.
All credits to the cyangenmod development team and that guy from youtube!
If I helped you, hit thanks!
If you encounter any problems (ROM Not booting or device won't show up in adb), please post them here!
Click to expand...
Click to collapse
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
vespa70 said:
Hello! Thank's for your help! But I'm stuck at item nbr 9. There is no "advanced" .
Right now I can't go anny further.
Click to expand...
Click to collapse
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
RAZERZDAHACKER said:
I wrote that we are not going to use the recovery the guy in the video used, replace it with the recovery I provided, remember to read the whole post.
Click to expand...
Click to collapse
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
vespa70 said:
Hi! Shall I first install "TWRP...md5" with Odin?
The phone is rooted, I used Kingroot.
Item 5, can't find "ClockworkMod".
Click to expand...
Click to collapse
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
RAZERZDAHACKER said:
Yea, twrp and you should see the clockworkmod in the list, make sure the box is not ticked if you downloaded and installed the .exe driver file that I provided.
Click to expand...
Click to collapse
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
vespa70 said:
yes, ther is 5 in the list and i looked at all of them.
There is a lot of manufacturers but not Clockwork.
Click to expand...
Click to collapse
If you have an sdcard you can put the files on there and flash via sdcard.
RAZERZDAHACKER said:
If you have an sdcard you can put the files on there and flash via sdcard.
Click to expand...
Click to collapse
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
vespa70 said:
Yes I have a sdcard. If I copy all the files from you to
the card, how do I procid from there?
The cam is rooted so how do I go on?
Click to expand...
Click to collapse
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
RAZERZDAHACKER said:
Put the cyanogenmod rom on the sdcard and the google apps. Assuming you have the recovery I provided here boot into it. Hit install then select storage then select your sdcard. Make sure the files are there and exit out and wipe as I said in the instructions. Make sure not to wipe the micro sdcard. Then install the rom then the google apps.
Click to expand...
Click to collapse
I am a little confused about this. This is what I have on the sdcard:
cm-11-20160603-UNOFFICIAL-kylepro.zip, TWRP.S7580.tar.md5, HDPI_gapps-kk-20160526-signed.zip.
I have done TWRP.. with Odin, is that what you mean "boot into it"??
"Hit install", where?? Wipe: Shall I "wipe cache partition"??
There is "wipe data/factory reset", but then everything is gone.
Please, can you show me point by point what to do, so I don't brick it all.
You know what, I stumbled across this video and it is basically a full tutorial! Lycka till med ditt flashande!
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
vespa70 said:
Hi!!!! It''s working now 4.4.4 kitkat is up
and running!! I don't belive it, but it's true.
I had to,in Odin, untick "autoreboot and F.Reset time". That maked the the damn thing not to reboot.
After that it worked.
Anyway, Many thank's for your hep!!
Bye
Click to expand...
Click to collapse
Ha, jag visste det från alla utropstecken , hoppas att allt funkar bra och om du får några bugg eller så rapportera det här.
Related
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
robboy said:
Okay so I'm new to Android. I have been trying to update to a new rom but have pretty much got stuck at the first hurdle. I have been trying to follow http://forum.xda-developers.com/showthread.php?t=552591
MoDaCo Custom ROM is here (2 versions based on the 'new update')!
As stated in the first thing to do for a newbie is to Download the patched recovery image linked above and install as detailed in that post.
I have not been able to get pasted this stage
Please please please can someone write an idiots guide for this as by the end of tonight I’m going to be bald as I’m pulling my hair out.
Click to expand...
Click to collapse
1. make a full nandroid backup
2.download the recovery image
3.turn off your phone and turn on by pressing the on button+the back key (to get into bootloader)
4.open a terminal from the folder which contains the recovery image.
5. type 'fastboot boot cm-hero-recovery.img'
6.type 'adb shell mount /sdcard'
7.type 'adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img'
8.type 'adb shell flash_image recovery /sdcard/cm-hero-recovery.img'
now whenever you want to access the recovery console, you just have to switch your phone on+home key and u'll enter.
To install the rom,
9. download the radio and rom from modaco
10. plug in ur usb and mount sd card
11. copy radio into sd card and rename to update.zip.
12. switch off phone and enter recovery console
13.if you never upgraded the phn , then a wipe is necessary
14. then, select update.zip..
15. u repeat the steps from step9 onwards the same way to update the rom.
hope ie helped.
i mentioned nandroid backup as from step 1 itself.
just came to realise that maybe u have never accessed recovery image from pc.
well dont worry, u can ignore step one but be sure to make the backup after step 8 ..... before installing the new rom
cheers and good luck
Okay so number 4 is my problem. Do o do this from the phone or pc?
robboy said:
Okay so number 4 is my problem. Do o do this from the phone or pc?
Click to expand...
Click to collapse
From the pc. A DOS terminal, if you are on windows.
should I allready have partitioned my sd card before i do this?
This is the error message i get
robboy said:
This is the error message i get
Click to expand...
Click to collapse
As far as I can see, you opened the command-line in the system32 dir from youre PC?! You should open the commandline in the dir where the image-file is. Should look like C:\SDK\tools
See this post to guide you further.
http://forum.xda-developers.com/showpost.php?p=4257045&postcount=38
robboy said:
This is the error message i get
Click to expand...
Click to collapse
To open a terminal( command prompt) from a folder,
1.go to accesories in Windows, copy the command prompt.
2. Go to your folder and paste it there.
3.right click on the command prompt, go on prope
rties.
4. U will find a line containing ' start in : %homedrive%%homepath....'
5. Delete that line so that 'start in' remains blank
6. Apply. And u r good to go
By the way. I supposed u already installed HTC sync right.
okay I thought HTC sync might be causing me problems so i removed it
robboy said:
okay I thought HTC sync might be causing me problems so i removed it
Click to expand...
Click to collapse
You will need to install HTC sync cause it contains the drivers for you phone.
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
okay so now when I'm in the bootloader my device connects as a ADB Interface - HTC Bootloader.
BTW I'm on Vista and i selected the driver that was in x86 folder that I was advised to download. However still no device found
robboy said:
Okay so I have put HTC sync back on. My hero connects to the sync in normal mode as an android USB devices - My HTC . What I'm unsure of now is when I press 'on and back buttons to go into bootloader' should the hero still sync as My HTC or should it be syncing to a different driver. I have been going round in circles all day. I have also removed the android development software as before the hero was syncing as and adb device??
When going to the cdm I now get the error device not found. USB debugging is selected on my device.
I think I’m on the brink of giving up.
Click to expand...
Click to collapse
Yes if your device is recognised as adb ... it's good.
That's how it should be.
Try installing HTC sync before plugging ur phone, then enter bootloader on the phn, plug it in, and then perform the command from the prompt.
P.s try entering bootloader first and only afterwards u plug in ur phone
Try to get the latest driver HTC sync from HTC site. If that doesnt work, try downloading the latest sdk plus drivers. U can find it somewhere on the forum . I think that there is a link on the rooting guide by daysee
I'm a total noob at Android too but theunlockr.com was the easiest and fastest way for me to install the custom Modacco ROM. Check out their site; it'll show you step by step with videos :]
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Uberjim said:
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Click to expand...
Click to collapse
Thanks for the reply. I appreciate the info given. Will try to use the tool now since the rom file is no longer saved in the tablet.
Will update soon.
Thanks.
I'm just done installing the Knivesandforks on my win7. After that, the system automatically install the phyton. I dont know what its function, but as i follow this steps, i get error with cmd which shown as below:
Code:
c:\users\pc>adb reboot
error: device not found
i think i didn't miss any steps. Anybody here could help me with this?
Thanks in advance.
* my tablet is still in cmw main page and not showing anything even has been connected to the PC. i think that's the reason why the error occurs - device not found. anybody who could give some ideas on this will much appreciated.
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Uberjim said:
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
Click to expand...
Click to collapse
i did those steps again, but it seems like not helping. the script is only rebooting the tablet instead of giving me the option to flash the rom. i don't know if i did wrong. but as i know, i did as posted here.
* frust to see the cmw recovery for the whole day
Striatum_bdr said:
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Click to expand...
Click to collapse
i did follow this tutorial
at first, install universal naked drivers - done
Now do the following:
Make sure your Prime is in Recovery mode (CWM) - YES
Open a cmd line on your pc - DONE
Type: "adb shell" - DONE
You should see a "#" now - YES
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] - Ok. This part was very difficult. I see the "#" but to type all those command, I can't. Why? Because the line in cmd instantly extended to a new line of command. I mean it just like I press the ENTER button. So, the line move to below and i can't finish typing all those command.
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
titanbullet said:
i did follow this tutorial
at first, install universal naked drivers - done
Click to expand...
Click to collapse
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Striatum_bdr said:
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Click to expand...
Click to collapse
this is my first time, so i don't know if that was strange. ha ha. well, it's not about the command line which is extended or not. but the line itself creating a new line, as i said - just like i press the ENTER button.
i try to use copy-paste function (ctrl + c and ctrl + v). but i don't think it functions in cmd.
please help..
[Solved]
What i do?
I follow this step again
Installing the ADB again
And the most important thing is, pushing ROM into /sdcard should be like this:
Code:
adb push rom.zip /sdcard/rom.zip
And right-click copy paste function solving my strange cmd
Then i just follow the steps by installing the zipped rom thru cwm when my screen did not stuck at splash screens
Thanks for your kindness
My TF is now back to normal
THANKS!
This is now DEPRECATED and NOT SUPPORTED ANYMORE since there is an easier method to do it! Links won't get updated! You can still use the written info!
If you want rooted kitkat head to my friend's thread @maxx_hr (THANK YOU FOR ALL YOUR WORK!) HERE: http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/development/kk-kk-kdz-p710-root-t2950532
Hello to you all!Warning:
Code:
[COLOR="Red"][SIZE="4"]Your warranty is now void. I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about all contained in this tutorial
before you follow it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
But since i'm a nice dude i will try to guide you anyway:)[/SIZE][/COLOR]
In this tutorial we will learn how to:
- achieve root on our L7 II (Both single and dual-sim, so P715/P710 and all the derivated phones from them) by LG running a Custom Rom or Stock KK Rom.
FOR THIS FOLLOW ALL STEPS.
- unbrick/flash to a specific firmware using Lg Flash Tool (In this tutorial there are only 2 KDZ files stock JB for P710 and P715. If you want to recover from a brick or want a different KDZ file you can find them over here: http://lg-phone-firmware.com/)
FOR THIS FOLLOW STEP 1 AND STEP 2 (install all drivers including adb and download the files that are needed at Step 2).
- flash with CWM (There are 3 methods I describe. Use the one that suits you the best. You can flash any *.zip that is suitable for your device.)
FOR THIS FOLLOW STEP 5.
Save your data you need, you will lose all data so backup with Titanium Backup or a program you like the info you need.
ALL DOWNLOADS ARE AT THE BOTTOM OF THE POST!
This tutorial will be split in steps as the following:
1. Preparing the Windows machine with the right drivers and software.
2. Reverting back to Jellybean Stock Rom.
3. Rooting on Stock Rom (Jellybean).
4. Installing Unlocked Bootloader and ClockWorkMod Recovery (CWM).
5. Flashing KitKat or a Custom Rom through CWM.
6. Flashing Root through CWM.
So let's start the job.
1. Preparing the Windows machine with the right drivers and software.
Uninstall everything related to LG from Control Panel (Drivers, PC Sync etc).
Restart your PC.
Download and unrar the archive "LG Drivers.rar".
Install both files inside and restart your computer.
Download "adb-setup-1.4.2.exe" and install it (answers should be y y y and install the drivers when prompted).
Download "Framaroot-1.9.1.apk".
Download "LG Flash Tool 2014.rar".
Download "Free LG P710.rar"
Download "P710 Stock KK.zip". -> Stock KK image with Stock KK kernel in it made from the original V20 KDZ (Open Europe).
Download SuperSU
*Download "P715 Stock KK.zip" and "LG P715 (JellyBean).kdz" if you are running a dual-sim version of the phone.
*Download all the files you need!
From now on I will consider you have this files and I will just call their names when to use them.
2. Reverting back to Jellybean Stock Rom.
Open the back cover of your phone and pull the battery out. Wait about 10 seconds. Put the battery back in.
While HOLDING (keep pressed) the VOLUME DOWN BUTTON insert the USB Cable in the phone (you need to have your USB cable inserted in an USB 2 port from the back of your PC).
When you see the yellow screen with emergency mode stop pressing the button.
Unplug the USB from the phone and then plug it in again.
Unrar "LG Flash Tool 2014.rar" and open "LGFlashTool2014.exe" with right-click Run As Admin.
*If you cannot open this program you need to install "VC_RedistInstaller.exe". You are missing some libraries of visual C++*
*IF YOU HAVE ANOTHER PHONE (another LG or P715) DO THE SAME INSTRUCTION AND REPLACE JUST THE KDZ FILE ON "Select KDZ File" TO THE ONE YOU DOWNLOADED AND IS SUITABLE FOR YOUR OWN DEVICE.
Move PhoneMode from DIAG to EMERGENCY. Select KDZ File: you have a file called "V10J_00.kdz" in the same folder as the tool. Select that. Press CSE Flash (CAUTION!!! This will reflash the phone and YOU WILL LOSE ALL YOUR DATA SO BE WARNED).
Another screen will open and press START.
Another screen will open once again press OK.
At a point you will get an error like "Offline BLA BLA". DON'T DO ANYTHING DO NOT PRESS OK.
Wait until your phone reboots and then you can close this tool.
Remove USB cable.
IMPORTANT STEP:
Pull out the battery. Wait 10 seconds put it back. While holding VOLUME DOWN + HOME BUTTON press POWER BUTTON. Wait until you see LG logo and stop pressing POWER. Keep pressing the other 2 until you see android robot doing things. Wait until the phone boots.
CONGRATZ you are on JELLYBEAN (Or the KDZ you chose).
3. Rooting on Stock Rom (Jellybean).
When you see the welcome screen just fast forward everything.
Go to system settings->security->tick Unknown sources->OK.
Go to system settings->developer options->OK->tick USB debugging->YES.
With an SD card reader or with your USB connected as Media Sync (MTP) copy the "Framaroot-1.9.1.apk" to your SD Card.
Using the phone's FILE MANAGER go to external_SD and click the Framaroot you just copied. Run it using Package Installer Just Once and Install.
When finished press OPEN. At the first choice choose Install SuperSU and then press on "Gandalf". You will get Success. Press OK and reboot.
You will see SuperSU in you apps.
YAY! IT'S DONE.
4. Installing Unlocked Bootloader and ClockWorkMod Recovery (CWM).
*SAME FILE YOU NEED FOR LG P715
Earlier you have download "Free LG P710.rar" and in the first step you installed ADB. We will use that now.
Unrar the "Free LG P710.rar" and place the 2 files ON THE ROOT (only on root) of the SD card using device mounted in MTP mode or SD card reader. Put back the card if you use the second option.
WARNING!!!
This can mess up you device so just do what i say step by step!
Plug the USB Cable in the Phone once again and use MTP connection mode.
Click Start+R type CMD and press ENTER.
Run the Following with copy paste to CMD.
Code:
adb devices
You will see your device.
*IF YOU CANNOT MAKE YOUR DEVICE BE RECOGNIZED IN "adb devices" do this:
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=ro
Open terminal and continue with the steps down below.
Code:
adb shell
You will see something ending with $.
Code:
su
Unlock the dvice if it is locked and your phone will ask for superuser permission press GRANT.
Code:
dd if=/storage/external_SD/APPSSBL.bin of=/dev/block/mmcblk0p5
This will copy the unlocked bootloader to the bootloader partition.
Code:
dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
This will copy the CWM to recovery partition.
Code:
reboot recovery
This will reboot your phone in CWM if you followed all steps correctly.
GREAT SUCCES we have an unlocked bootloader and CWM.
Close your CMD.
Unplug USB.
5. Flashing KitKat or a Custom Rom through CWM.
*IF YOU WANT TO FLASH ANOTHER ZIP FILE OR YOU ARE ON P715 JUST USE THE ARCHIVE YOU NEED AS REFERENCE, NOT "P710 Stock KK.zip". CHOOSE THE FILE THAT IS MOST SUITABLE OR YOU THINK IT'S BEST FOR YOU
I made "P710 Stock KK.zip" you downloaded. This is the stock image for KK Open Europe. Here you can either flash mine or search for a Custom Rom for your device. Either way you will follow the exact same steps but with a different archive. I will take for reference the "P710 Stock KK.zip".
Plug USB in.
You Navigate using Volume Up Button (UP) and Volume Down Button (DOWN). The Power Button is OK.
Do this:
- Go to "wipe data/factory reset" and OK. Go to YES then OK. Wait until done.
- Go to "mounts and storage" and do the following: "format /cache" and "format /system" everytime with YES as second option. Press "go back" once.
- Go to "advance" and then "wipe dalvik cache" and YES. Press "go back".
Here you have 3 options.
OPTION 1.
Use an SD card reader copy the Zip file to the root of the SD card or copying using CWM. Using CWM you navigate with Volume Up and Volume Down to "mounts and storage" press POWER BUTTON (OK). Go to "mount USB storage" and your SD card will appear in windows and you can copy. After that you press "go back" 2 times to get to the main menu.
Go to "Install zip" and then "choose zip from sdcard". Search for the zip file and press OK then go to "YES" and press OK. Wait until done.
Go to "wipe data/factory reset" and OK. Go to YES then OK. Wait until done.
Press "Reboot System Now" and "yes" if asked (if you are asked about some fix or anything after you press reboot now choose the positive thing like the answer that is not no).
OPTION 2.
Copy the file using adb push. Open a CMD window in Windows (Start+R type CMD press ENTER). Copy this:
Code:
adb push
With the space. After space go where you downloaded the zip file highlight it and drag it in the CMD. Leave a space after that and type /sdcard (without space after).
Wait until done and close CMD.
After you copied the file to your sdcard go to "install zip" -> "choose zip from sdcard" -> search for the "P710 Stock KK.zip" press OK then go to "YES" and your installation will beging. Wait until it is done. Go to "wipe data/factory reset" and OK. Go to YES then OK. Wait until done.
Press "Reboot System Now" and "yes" if asked (if you are asked about some fix or anything after you press reboot now choose the positive thing like the answer that is not no).
NOTE: In the zip i made i don't know why i couldn't sideload it but usually you do not have to copy to SD card to flash something. You can sideload it. All you have to do is:
-Go to "install zip" -> "install from sideload"
On your computer open a CMD and copy this :
Code:
adb sideload
Copy with space and after what you copied grab the zip you want to flash and drag it to CMD. Hit ENTER. Sideload will send the zip to phone and process of flashing will start. After it is done reset to factory again.
Press "Reboot System Now" and "yes" if asked (if you are asked about some fix or anything after you press reboot now choose the positive thing like the answer that is not no).
CONGRATZ YOU ARE NOW ON KITKAT. I HONESTLY THINK THAT YOU SHOULD GO FOR THIS CUSTOM ROM OVER HERE BECAUSE IT IS LIKE 10 TIMES BETTER THAN THE STOCK KK. TO INSTALL JUST DOWNLOAD THE ZIP FILE FROM THERE (V2) AND FOLLOW THE TUTORIAL WITH JUST REPLACING THE ZIP WITH THE OTHER ZIP.
LINK TO ROM: http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/development/l7-ii-p710-amigakitkat-t2890092
LINK TO DOWNLOAD: http://d-h.st/GSh
6. Flashing Root through CWM.
On some ROMS root will not be there. To avoid this we will flash the SuperSU zip.
To get to recovery you have 2 ways:
- From you ROM connect USB as MTP or in a way that ADB recognizes it (device gets detected by adb devices) type adb reboot recovery.
- Close your phone. At the same time press VOLUME DOWN + HOME BUTTON + POWER BUTTON. When you see the LG logo stop pressing POWER BUTTON. Keep the others 2 until you are in CWM.
Install the SuperSU zip with one of the ways you learnt at step 5.
You are rooted now.
Hope everything worked out fine for you and you are happy. Have a really nice day.
CREDITS:
riskey95 -> his work for CWM recovery and Hacked Bootloader
Chainfire -> for making SuperSu possible
Snoop05 -> for the amazing 15 seconds ADB Installer
alephzain -> making Framaroot, such an easy root method
santhoosh -> for the tutorial of making CWM flashable zip from KDZ
Amiga500 -> for super cool KK Rom
airidosas252 -> best kernel on the market
ME -> for putting everything together and writing this
Everyone i forgot just PM me
Lg Flash Tool 2014 : http://tinyurl.com/kggahet
P710 Stock KK.zip: http://tinyurl.com/p7q7d75
P715 Stock KK.zip: http://tinyurl.com/nllkxfm
P713_CIS_KK.zip: http://tinyurl.com/nv3uzop
LG P715 (JellyBean).kdz: http://tinyurl.com/lwv29xr
adb-setup-1.4.2.exe: http://tinyurl.com/qca8abd
VC_RedistInstaller.exe: http://tinyurl.com/n98r7wg
LG Drivers: http://tinyurl.com/l3mgf49
CHANGELOG:
- added support for P715
- added P713 CIS
- added new version of SuperSU
This is fantastic! I've been looking for how to convert KDZ to a CWM Zips because of trouble rooting the P713 Firmware
Dennydap said:
This is fantastic! I've been looking for how to convert KDZ to a CWM Zips because of trouble rooting the P713 Firmware
Click to expand...
Click to collapse
Does P713 have NFC?
This method actually works for dual sim too,you just have to use P715 kdz's.
KWG V2 said:
This method actually works for dual sim too,you just have to use P715 kdz's.
Click to expand...
Click to collapse
Yeah it does. Maybe this weekend I will mod it. It is usefull for recoverying from soft bricks also just Step 1 and 2.
it was great till i get stuck on boot loop ,,, now how to solve ?
thanks for the useful guide.
I have a problem though, I cannot go after kdz extraction.
LG Tools stops with an cryptic error like [009.400.120.120.120]PC????? and looking at the log it seems there are troubles in unpacking the kdz file.
I have tried with different roms but still the same.
Does anyone has the same problem ?
xak-fr said:
it was great till i get stuck on boot loop ,,, now how to solve ?
Click to expand...
Click to collapse
Where exactly did you get a boot loop?
thanks for the useful guide.
I have a problem though, I cannot go after kdz extraction.
LG Tools stops with an cryptic error like [009.400.120.120.120]PC????? and looking at the log it seems there are troubles in unpacking the kdz file.
I have tried with different roms but still the same.
Does anyone has the same problem ?
Click to expand...
Click to collapse
Did you run as administrator? Do you have drivers installed? Tell me exacly what you did and what happened.
xak-fr said:
it was great till i get stuck on boot loop ,,, now how to solve ?
Click to expand...
Click to collapse
the problem is on V10J,, i dont know where you find it but it stucks,,, i used the lg flashtool for flashing kit kat i got the original one and the phone starts running but the thing that made me curious is that nothin on phone changed,, it is the same as it was when i had stock kit kat,, no factory reset, no nothing,,, can anyone explain please ?
xak-fr said:
the problem is on V10J,, i dont know where you find it but it stucks,,, i used the lg flashtool for flashing kit kat i got the original one and the phone starts running but the thing that made me curious is that nothin on phone changed,, it is the same as it was when i had stock kit kat,, no factory reset, no nothing,,, can anyone explain please ?
Click to expand...
Click to collapse
I can't really understand you. The point of this guide is to get root on kitkat so flashing with lg flashtool will not work if you want kit kat rooted. I tested that V10J on my own l7 2 (p710). Also if you flashed Jellybean did you press CSE Flash not Normal Flash?
scholars nxperan
christi9503 said:
I can't really understand you. The point of this guide is to get root on kitkat so flashing with lg flashtool will not work if you want kit kat rooted. I tested that V10J on my own l7 2 (p710). Also if you flashed Jellybean did you press CSE Flash not Normal Flash?
Click to expand...
Click to collapse
sorry for my english ,, let me explain,, i had stock kit kat on my P710,, I flashed JellyBean (V10J that was on flashtool folder). after the flash (CSE Flash) finishes i got stuck on boot loop,, so after many tries to revive the phone i used to flash the stock kit kat again and the phone started working but in the phone nothing changed like nothing happened ,, i know it is not rooted , i flashed stock kit kat (V20A.KDZ)
so the problem is the boot loop i got after flashing V10J i found in folder,,,
xak-fr said:
sorry for my english ,, let me explain,, i had stock kit kat on my P710,, I flashed JellyBean (V10J that was on flashtool folder). after the flash (CSE Flash) finishes i got stuck on boot loop,, so after many tries to revive the phone i used to flash the stock kit kat again and the phone started working but in the phone nothing changed like nothing happened ,, i know it is not rooted , i flashed stock kit kat (V20A.KDZ)
so the problem is the boot loop i got after flashing V10J i found in folder,,,
Click to expand...
Click to collapse
What model you have P710?
christi9503 said:
What model you have P710?
Click to expand...
Click to collapse
yes, Lg optimus L7II P710
xak-fr said:
yes, Lg optimus L7II P710
Click to expand...
Click to collapse
Ok do that step again. Flash with that tool using the image i provided. After the last ok. Even when you get the offline error don't touch it until phone reboots. If you get bootloop do this.
1. Pull out battery. Wait 10 seconds. Push battery back in.
2. While holding POWER DOWN + HOME BUTTON press POWER BUTTON. Wait until you see LG logo then stop presing POWER. You will get to see android guy doing stuff. Then tell me if it's ok.
christi9503 said:
Ok do that step again. Flash with that tool using the image i provided. After the last ok. Even when you get the offline error don't touch it until phone reboots. If you get bootloop do this.
1. Pull out battery. Wait 10 seconds. Push battery back in.
2. While holding POWER DOWN + HOME BUTTON press POWER BUTTON. Wait until you see LG logo then stop presing POWER. You will get to see android guy doing stuff. Then tell me if it's ok.
Click to expand...
Click to collapse
yes, i get the boot loop but after the reset is ok,, now will go on other steps ,, thank you
xak-fr said:
yes, i get the boot loop but after the reset is ok,, now will go on other steps ,, thank you
Click to expand...
Click to collapse
Don't forget to press the thx button it's in the right . I will add this to the tutorial I didn't need it but who knows.
I managed to do the "root" step, but somehow cannot proceed with the next step.
When I check "USB debugging", the phone doesn't connect to the computer for some reason. I tried multiple computers, with no luck. The "adb devices" says just empty "List of devices attached".
If I disable the USB debugging, the phone gets connected just fine, if I enable it again, it gets stuck on "Connected as installer", and doesn't connect as MTP....
Any idea how to fix this?
Do you have drivers installed? Also when you press MTP cancel if your phone wants to install anything.
Sent from my LG-P710 using XDA Free mobile app
christi9503 said:
Do you have drivers installed? Also when you press MTP cancel if your phone wants to install anything.
Click to expand...
Click to collapse
I tried everything, without luck. I ended just using terminal emulator to copy the files on phone directly (might be cool to add this to your tutorial, as someone else can also have this problem). So, now I'm on Amigas ROM - makes a HUGE difference! Thanks, looking forward for some other custom ROMs for this phone..
vasikgreif said:
I tried everything, without luck. I ended just using terminal emulator to copy the files on phone directly (might be cool to add this to your tutorial, as someone else can also have this problem). So, now I'm on Amigas ROM - makes a HUGE difference! Thanks, looking forward for some other custom ROMs for this phone..
Click to expand...
Click to collapse
Strange huuummm. I don't know. Yeah i will add Terminal Emulator also in weekend. Never happened to any of my phones before... Maybe driver conflict on your PC or something like that.
Ok, so I attempted to root a Nabi 2 so I could use the SD card to hold apps since the onboard memory is terrible and I bricked the dang thing. I unlocked root supposedly using a one click app method, then I was able to attempt to update using the updater already on the Nabi. During the reboot, thats when it bricked. It is stuck in a constant boot loop mode that eventually ends up on a dead android screen.
My main problem is I know there has got to be a way to restore a stock rom/os on it, but every how to guide out there assumes that I already know what the hell they are talking about. SDK, ADB, HIV, STD, its irritating. Also, I tried TWRP, ADB, etc. but since the Nabi is in a constant boot loop and dead android screen, I can't get my PC to recognize it for more than 5 seconds. Is there a step by step guide to what I need to do for a novice? Like step 1. "since your PC can't recognize the device in the first place this is where you start". Step 2, use "this program, then this, and this is why".
Can anyone out there help me get pointed in the right direction? I am tech savvy but the existing guides assume too much, have broken links, and don't say anything about what to do when you can't even get your device to be recognized.
Thanks
Aaron
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Higher-Primate said:
I am pretty sure TWRP is the way to go but it isn't able to manipulate the Nabi, and I can't install drivers, etc or do anything else due to the constant reboot.
Click to expand...
Click to collapse
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
aicjofs said:
So what version of software was the Nabi running? There are 3 different versions of TWRP depending on if you were on Ice Cream Sandwich, Jellybean, or Kitkat.
First of all to stop the bootloop can you get to the bootloader screen? Power up by holding the power and vol - (or maybe vol + I never pay that much attention). You should see a screen with little lines of text that say "fastboot protocol, recovery kernel, forced recovery, etc). If you can get there then we need to get TWRP on the device. You will need to have tablet plugged in to computer and select fastboot protocol. Now go to windows device manager and see if you see "android device" or only an unknown device. For unknown device you can try these drivers http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
See if this will detected the device once you have fastboot running and we can work from there. NablabGUI installer. http://nabtabhacks.com/nabilabgui2015/publish.htm
If the fastboot devices button give you a device number then you can try and install TWRP.
Click to expand...
Click to collapse
I want to say it was running 4.1 or 4.2 but I'm not positive. Stupid me should have written it down. Is it possible to load any of the versions now that I have wiped it? I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen. From there I did a - and + and got an option to side load recovery or boot to ADB I think it was. So since I can at least get there, is there anything I can do? Other than that, TWRP won't recognize it and says no drivers are loaded. I'm assuming because I can't get the Nabi to stay stable long enough to actually load anything on to it? The device recognizes for a few seconds then disappears.
Higher-Primate said:
I was able to go to the kernal mode using + and pwr, then from there I got the dead android screen.
Click to expand...
Click to collapse
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
aicjofs said:
At the screen where you selected "kernel mode", select "fastboot protocol" instead. With the tablet plugged in go to your computer and open "device manager". Look for the device. You will need to have drivers loader for fastboot before you can do anything. Once you get the drivers loaded you will need to get TWRP on device. Lets just get fastboot working first.
This is something I am working on too that might be helpful
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119/post63390550
Click to expand...
Click to collapse
Ok, I tried fastboot, but it doesn't really do anything. Once I go into fastboot, I have more options. Bootloader, continue, reboot bootloader, reboot, and power off. None of the options allows the Nabi to show up as a device in device manager. Everything just takes me to the dead android unfortunately.
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Higher-Primate said:
So I guess my next question would be, how do I get drivers loaded for a device that can't show up?
Click to expand...
Click to collapse
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
aicjofs said:
Have you installed these drivers yet? Nabilab driver for 32 or 64 windows? http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
The part you did where it just had bootloader, continue, etc is the correct screen you want to be in. Install the drivers and then go back to the fast boot protocol again.
Click to expand...
Click to collapse
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Higher-Primate said:
Geeze, my bad! Sorry about that. I must have not seen that part. Ok, with the fastboot menu sitting there and the 64 bit drivers installed, I am able to see "android device" in the device manager, and it shows up as a fastboot device in NabiLab GUI and Tools. Now I'm excited! Whats next?
Click to expand...
Click to collapse
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
aicjofs said:
If you are in NabiLab2015. Go in to the Nabi2 screen. There should be an option to select which version you are using(ICS, JB, KK, etc) You can cycle though install the 3 different TWRP's until you find the one that boots. Normally it needs to be in Android or TWRP not in the fastboot bootloader but I think it will still install.
If not you can go back to main screen open a command window and type.
fastboot flash recovery 2/new/recvoery/recovery.img
fastboot flash recovery 2/JB/recovery/recovery.img
fastboot flash recovery 2/ICS/recovery/recovery.img
Each line you type is a separate attempt, meaning you will have to get back to the fastboot screen each time.
Or if you are feeling frisky it should have an option to return to stock. You will lose your data doing it that way, there might be another way where you can save it.
Click to expand...
Click to collapse
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Higher-Primate said:
It recognizes the Nabi in the device manager, and when I click Fastboot - bootloader - Devices on the Tools section of NabiLab2015, but when I go under NV7A Disney/Nick (which I think this one is) or NV7A - US, it won't show the device under either Nabi Product Tab. Also, from the command prompt for all 3 commands, I get "C:\Users\aaronf\AppData\Local\Apps\2.0\R81BWYH1.9HO\2X87EK1X.KEM\nabi..tion_0000000000000000_0001.0000_ecfca16b310dc7a8>fastboot flash recovery 2/ICS/recovery/recovery.img
error: cannot load '2/ICS/recovery/recovery.img'"
Not sure what to do next. I feel we are really close though, but the program still can't truly "see" my device I don't think.
Click to expand...
Click to collapse
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
aicjofs said:
Oh. I'm an idiot. I was doing this from memory. I swapped it around should be
Fastboot flash recovery 2\recovery\ICS\recovery.img
Change the other 2 accordingly
Click to expand...
Click to collapse
No problem at all. Ok, that seemed to have done something. I put in the exact one you just changed above, and I rebooted normally, now I have a TWRP screen on the Nabi display. Now, what instructions do I need to follow? Do I still use NabiLab2015, if so the Disney/Nick or NV7A - US? Both now say "TWRP +mount:mounting /system on ext4 failed: no such file or directory.
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Higher-Primate said:
Also, here is this if it helps. This now shows up under ADB - Android/TWRP - devices:
List of devices attached
0123456789ABCDEF recovery
NABI INFORMATION
-----------------------------------------------------------------------------
Device=[Full
Android Version= [4.1.2]
Build Date=[Dec 28 2013]
Bootloader=[unknown]
Nabi Serial=[]
Click to expand...
Click to collapse
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
aicjofs said:
Good. Progress.
Let's try the other TWRP's. The /system not mounted sounds like a wrong TWRP version.
In TWRP go to the reboot tab, and select reboot bootloader.
In NabiLab command prompt try
fastboot flash recovery 2\recovery\JB\recovery.img
EDIT: Also let me know, do you want to try and save your data or just start fresh with latest Nabi software.
Click to expand...
Click to collapse
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Higher-Primate said:
Ugh, it seems the only one that will do anything is the first one: Fastboot flash recovery 2\recovery\ICS\recovery.img. That one at least gave me something under devices. The other two android versions JB and KK didn't show up as a device at all. Also, when trying to open the NabiGUI program now, it crashes out. So maybe its the program causing the issue of not seeing the other two versions of Android? I dunno. Also, a fresh start with the latest Nabi software would be just fine. This whole thing started out with me wanting to utilize expandable SD card storage for apps so if that can actually be done, awesome! But bottom line, if this thing just works again I am cool with that too.
Click to expand...
Click to collapse
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
aicjofs said:
If the program is crashing open windows task manager and see if any ads.exe are running or try rebooting the computer.
So let's get back to what worked. Use the same commands as you did to get it working the first time.
In TWRP on tablet. Try going to wipe tab and do a factory reset. Just to see if it will wipe the system.
Click to expand...
Click to collapse
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Higher-Primate said:
Ok, I tried the Fastboot flash recovery 2\recovery\ICS\recovery.img command again, it worked, then I went into the TWRP on the tablet, did a complete wipe, and now it is stuck on the Nabi logo screen. About all I can do to it now is reboot it into fastboot and nothing else.
Click to expand...
Click to collapse
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
aicjofs said:
-Best done with external SD card.
-Boot to TWRP by booting tablet to bootloader menu. (With tablet powered down press and hold both Vol- and power)
-Select recovery kernel with vol keys
-Do a back up of just the boot partition in TWRP. Just check "boot" and nothing else. Make sure you are backing up to external storage(MicroSD card)
Install 3.0.13 ROM and bootloader.
- Download 3013 stock ROM https://drive.google.com/file/d/0B08qqrSbn4djOFQ1a0cwQjVEV2M/view?usp=sharing
- Put SD card in computer. Navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
- Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
- Unzip the 3013stock.zip file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. This should set you up for the 3.0.13 ROM.
- Download the KK3013bootloader zip https://drive.google.com/file/d/0B08qqrSbn4djcnVTYjI0dTJSQjA/view?usp=sharing.
- Copy it to the SDcard. This will be for the bootloader update.
- Put sdcard in Nabi
- Boot to TWRP
- Go to restore tab, and find the backup under the "yourfolder" you made on the external SD card and unzipped the files to.
- You should be able to select boot, system, and addon and skip the others.
- If everything restores then go to TWRP "install tab", find the KK3013bootloader.zip you downloaded and install it.
- Reboot
Click to expand...
Click to collapse
What happens if it won't let me create the backup folder? It errors out and says it can't create one.
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh: