Database Users

[TUTORIAL] Remounting/restoring/backup the /EFS partition

/EFS partition contains a lot of information about your phone, f.e: wifi/bt mac address and your IMEI (nv_data.bin).
It's highly recommended to backup the whole partition, or at least copy the files from the efs directory.
CORRUPTED OR NOT?
You can check if the efs is mounted or completly damaged with this command:
adb shell
mount
You will see something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Red part means /efs is mounted.
IF YOUR PHONE HAVE CORRECT EFS PARTITION:
1, Root your phone - there are several methods to do this.
2, Install root explorer or Estrongs file explorer and copy /efs dir to your sdcard - this will copy the files.
or
2, Make a backup from the whole partition -this is better if you flash a phone with wrong ops, the only way to restore using this backup.
Backup:
adb shell
su
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
Restore:
Add efs.rfs to an unix compatible tar and flash with odin as efs file:
IF YOUR PHONE /EFS IS CORRUPTED:
Flash the included /efs tar with odin:
This will remount your efs partition and (if you have a backup or fixed nv_data.bin) you just need to overwrite files with a file explorer.

confirm WORKING 100% ... all you just need later is the nv_data.bin fixed
Thanks so much for your efforts

I am using I5801 JPB (with restored bootscreen and Rooted via SuperoneClick)
while using "adb shell" command at Better terminal its showing "adb: not found"
I flashed my I5801 from JP9, JPA and JPB till date..
is it possible to restore the backup now..??

Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.

Szaby59 said:
Because you need adb.
If you do on phone (Terminal emualtor) adb shell not needed, just su and the other commands.
Click to expand...
Click to collapse
many thnx..
BTW i am not able to get the snaps u attached..

sirtbhopal said:
many thnx..
BTW i am not able to get the snaps u attached..
Click to expand...
Click to collapse
google about install ADB for android phone, so you can follow TUT here... good for you now and future..., long journey to go, m8!

how to make .tar file because backup file is .rfs format help me i want my imei back

ok, using the dd method i made the backup of my /efs to a efs.rfs file that have ~4 MB
But when i go to the efs folder (on / ) or see the copy i've made to my SD card, there is no files at all on this folder. How can we "see" those files (nv_data.bin) ?

Hi
For backup I simply copied my /efs folder to SD card using root explorer.
Then I modified nv_data files to get unlocked.
there was no SSNV in the files.
I have a working unlocked phone now but the problem is that IMEI is all zeros like 000000000!
Can I use that folder to restore my files?

dhruvasoni said:
how to make .tar file because backup file is .rfs format help me i want my imei back
Click to expand...
Click to collapse
Download the Tar Utility from GnuWin32's SourceForge Page.
Code:
hxxp://sourceforge.net/projects/gnuwin32/files/tar/1.13-1/tar-1.13-1-bin.exe/download
(change it to http)
It'll install the tar.exe executable and required dlls in C:\Program Files\GnuWin32\bin
Copy those to where you have your rfs (or you can add the bin folder to your PATH Environment Var, google for help on how to do that)
Now type:
Code:
tar -cf efs.tar efs.rfs

Yes, you can, just copy nv_data to /efs.
Windows users can use IZARC to create tar files.

hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!

burak721 said:
hey guys
i havn´t backuped my file but i have now imei 0000000000000
i need help help me please!!!
Click to expand...
Click to collapse
If you use a I5801 flash a stock firmware of 2.1...the same applies even if you use I5800...
Sent from my GT-I5800 using XDA App

i have done it but my imei is allways 00000000
pleas help

Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version

FadeFx said:
Burak, what kernel do u use? There was a bug in older fugumod version where eds was not propperly mounted or read, thus the phone displayed bad imei, if u use older fugumod please update to latest version
Click to expand...
Click to collapse
I have used fugomod kernel 2.4
Sent from my GT-I5800 using XDA App

my imei is also showing ooooooo.....plss help mee dudes plss

i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?

huzo said:
i dont have imei at all!!! and sim card is not recognized,and no signal,phone unknown ....what am i supposed to do?
Click to expand...
Click to collapse
Pray ...

LOL good answer

[Q] Bricked Phone

I bricked the phone.Anyway, how i did?
1) I flashed B526
2) i edited cust.img but even they are same size, i couldn't copy new to /.cust_backup folder.So i deleted the original one.
3) i thought, i should give a try to Aurora 4.03 from dzo
4) I got into recovery, wiped data, wiped cache, wiped dalvik cache etc.
5) I couldn't install it, anyway then i thought i have to flash B526 again
6) But it stopped around %50 and it said "update failed" but i started the phone, 2 times.
7) With root explorer, i got into /.cust_backup folder but there was only amss.mbn, cust.img with higer size, emmcboot.mbn and boot.img but there wasn't any sign of recovery.img
8) I tried to copy 5.5.0.4 recovery file but there wasn't enough space for it so i deleted cust.img again but after i deleted it, "there isn't enough space" said root explorer nothing changed
9) i deleted amss.mbn, managed to copy recovery.img
10) Restarted phone but then i realized i can't get into recovery mode or start phone normally.
11) Because Huawei blocked bootloader mode, now i have a bricked phone.I tried 5 or 6 times flashing stock rom but update failed again and again
12) Packed up the phone, will send technical support tonight.
- I tried flashing without battery
- I tried mounting with ubuntu
Nothing changed
Any ideas?

Already sent.Thanks, who helped me and who wanna help but couldn't do it

Hi
Space is not enough to flash any ROMs;
Bootloader is locked,you could not edit that sector.
So is there a special ROM that is very small and allows to edit the bootloader?
Here is the MINI ROM: (thread is from anzhi,only copy the download url.)
115,com/file/clyzgmw1
(replace " , " by ". ")
Click the "电信下载“ right besides the red link"VIP ...."
Flash it than edit the bootloader~
NOTICE: I format the whole sector ,and the file including IMEI was missing
'Cause I don't know how to edit recovery or other system files like .mbn,
so just delete the abnormal big file and you would be able to flash any ROM s

shuiyunxingzuo said:
Hi
Space is not enough to flash any ROMs;
Bootloader is locked,you could not edit that sector.
So is there a special ROM that is very small and allows to edit the bootloader?
Here is the MINI ROM: (thread is from anzhi,only copy the download url.)
115,com/file/clyzgmw1
(replace " , " by ". ")
Click the "电信下载“ right besides the red link"VIP ...."
Flash it than edit the bootloader~
NOTICE: I format the whole sector ,and the file including IMEI was missing
'Cause I don't know how to edit recovery or other system files like .mbn,
so just delete the abnormal big file and you would be able to flash any ROM s
Click to expand...
Click to collapse
Hi, Thank you for this, gonna try it now
Hope it works.
*EDIT: I'm having a problem downloading this file. It is extremely slow to download and once downloaded it is corrupt. I've tried 3 times now. Any chance anyone who has downloaded could upload it to a European or US host?
Thanks in advance.

shuiyunxingzuo said:
Hi
Space is not enough to flash any ROMs;
Bootloader is locked,you could not edit that sector.
So is there a special ROM that is very small and allows to edit the bootloader?
Here is the MINI ROM: (thread is from anzhi,only copy the download url.)
115,com/file/clyzgmw1
(replace " , " by ". ")
Click the "电信下载“ right besides the red link"VIP ...."
Flash it than edit the bootloader~
NOTICE: I format the whole sector ,and the file including IMEI was missing
'Cause I don't know how to edit recovery or other system files like .mbn,
so just delete the abnormal big file and you would be able to flash any ROM s
Click to expand...
Click to collapse
Where were you 3 days ago I have already sent my phone to technical service
xmsnx said:
Hi, Thank you for this, gonna try it now
Hope it works.
*EDIT: I'm having a problem downloading this file. It is extremely slow to download and once downloaded it is corrupt. I've tried 3 times now. Any chance anyone who has downloaded could upload it to a European or US host?
Thanks in advance.
Click to expand...
Click to collapse
Here but i think it is for cwm

Thanks, it needs unzipping. In there is a UPDATE.APP file

xmsnx said:
Thanks, it needs unzipping. In there is a UPDATE.APP file
Click to expand...
Click to collapse
What?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Tmp341 said:
What?
Click to expand...
Click to collapse
Woohoo, after having a brick on my desk for about 6 weeks, I've finally got my phone up and running again. Even the IMEI didn't mess up
Instructions

xmsnx said:
Woohoo, after having a brick on my desk for about 6 weeks, I've finally got my phone up and running again. Even the IMEI didn't mess up
Instructions
Click to expand...
Click to collapse
You couldn't reach bootloader before, could you?

No I couldn't.
Sent from my Galaxy far, far away!

I looked technical service's web site and it shows that my phone is within the warranty I hope it won't change
Update : They say, my phone's motherboard is going to change. They are waiting for it

[TOOL] PoshADB - PowerShell ADB & Fastboot GUI Tool for Windows!

I have been diving further and further into PowerShell, so I challenged myself to create an Android Developers Bridge (ADB) and Fastboot Tool built on PowerShell.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's simple, but easy to use. Simply extract and run the PoshADB.exe (right click - Run as Administrator if UAC is enabled)
Requires: PowerShell (included with Windows 7 and newer)
Code:
[B]Current Features:
[I]ADB[/I]
[/B]Push/Pull from Device
Install APK
Reboot / Bootloader / Recovery
[B][I]Fastboot[/I][/B]
Flash update, boot or recovery images
Unlock/Lock Bootloader
Reboot / Reboot Bootloader
Code:
[B]Changelog:[/B]
7/17/2013 - Added WiFi ADB
4/25/2013 - Added source code to the ZIP file under _source directory
4/24/2013 - Added Fastboot!!!
4/24/2013 - Initial Release
DOWNLOAD HERE
Let me know what you think, or if you have any issues.

Download and try!!!

Working great for me Win7 and Win8. (note on Win8 you need to install .Net 3.5)
Awesome tool is awesome!!!!
REQUEST: Merge fastboot into this as well and most of my typing would be gone!!!

slimdizzy said:
Working great for me Win7 and Win8. (note on Win8 you need to install .Net 3.5)
Awesome tool is awesome!!!!
REQUEST: Merge fastboot into this as well and most of my typing would be gone!!!
Click to expand...
Click to collapse
Will do! That was part of my future plans

J33per said:
Will do! That was part of my future plans
Click to expand...
Click to collapse
Added Fastboot abilities! Let me know if there are any other features/commands you would like to see!

Minor "update" (if you can consider it that). I have added the source code to the Zip file under the _source directory in case anyone wants to play around with the "guts". Feel free to modify it as you see fit, just remember to give credit if you distribute it

J33per said:
Added Fastboot abilities! Let me know if there are any other features/commands you would like to see!
Click to expand...
Click to collapse
I will update my install today and let you know how the app works for me.
Sent from my Nexus 7 using XDA Premium HD app

Bump!

some suggestions
hey i like your app some things i would like added are:
1. i use adb over wifi can you please add an option to run "adb connect x.x.x.x" at the start.
2. with both push and pull the source/destination being able to select a folder from the computer as adb supports whole folder push/pull of contents.
3. some way to ls the directory tree of the android device.

nonato said:
hey i like your app some things i would like added are:
1. i use adb over wifi can you please add an option to run "adb connect x.x.x.x" at the start.
2. with both push and pull the source/destination being able to select a folder from the computer as adb supports whole folder push/pull of contents.
3. some way to ls the directory tree of the android device.
Click to expand...
Click to collapse
Thanks for the suggestions! I have added ADB WiFi (please test it) and also, if you select a file inside a directory, then edit the path, removing the file, it will push the directory.
Enjoy!
TechJeeper

I get a sig verify error when trying to flash boot
---------- Post added at 11:00 PM ---------- Previous post was at 10:35 PM ----------
also i noticed under ADB there are no devices shown.....there are under fastboot though?

saeker said:
also i noticed under ADB there are no devices shown.....there are under fastboot though?
Click to expand...
Click to collapse
Then that means your in your bootloader - where there is only Fastboot....

The download link on first post is still active
My Norton 2014 says its suspicious,
Mods certainly need to check this upload for threats.

ghpk said:
My Norton 2014 says its suspicious,
Mods certainly need to check this upload for threats.
Click to expand...
Click to collapse
it's just a false positive detection..

Can't flash system.

How to use it!
Can you please illustrate the steps.

POSHADB not responding
J33per said:
I have been diving further and further into PowerShell, so I challenged myself to create an Android Developers Bridge (ADB) and Fastboot Tool built on PowerShell.
It's simple, but easy to use. Simply extract and run the PoshADB.exe (right click - Run as Administrator if UAC is enabled)
Requires: PowerShell (included with Windows 7 and newer)
Code:
[B]Current Features:
[I]ADB[/I]
[/B]Push/Pull from Device
Install APK
Reboot / Bootloader / Recovery
[B][I]Fastboot[/I][/B]
Flash update, boot or recovery images
Unlock/Lock Bootloader
Reboot / Reboot Bootloader
Code:
[B]Changelog:[/B]
7/17/2013 - Added WiFi ADB
4/25/2013 - Added source code to the ZIP file under _source directory
4/24/2013 - Added Fastboot!!!
4/24/2013 - Initial Release
DOWNLOAD HERE
Let me know what you think, or if you have any issues.
Click to expand...
Click to collapse
POSHADB not responding

good tool

della96 said:
Download and try!!!
Click to expand...
Click to collapse
Hi thanks but the link is not working for me ?

Parrynormal said:
Hi thanks but the link is not working for me ?
Click to expand...
Click to collapse
It works with a download manager like 1DM, tested personally

G4 Root (Testing)

This is a test root method for the G4. It is based off of the original root method for rooting LG devices. The original method showed modified in the boot loader but it didn't have su. This a modified script to push su correctly and the su used by the H815.
Note: On the H815 If you would like root all you have to do is unlock boot loader, flash twrp for G4 then flash the supersu.zip
WARNING: USE AT YOUR OWN RISK!!
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 features included in this ROM
before flashing 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.
Click to expand...
Click to collapse
This is a new method that i discovered. Instead of rooting we are just going to flash TWRP then we can root through the recovery. I have tested this on my G3 and i can confirm that you are able to flash recoveries through download mode.
The Recovery used in this is TWRP for H815 and I am not sure of how compatible it is with other variants but if it gives you root then its worth testing.
Files:LGG4_rFLASH.zip
Drivers:HERE
Step 1: Enable USB Debugging
Step 2: Download G4 Flasher and unzip, Also Install Drivers
Step 3: In unzipped folder open a new command prompt window (Shift+Right click)
Step 4: Run this command
adb.exe push recovery.img /data/local/tmp/
Click to expand...
Click to collapse
Step 5: Enter Download Mode (Hold Volume Up While plugging in Usb Cable)
Step 6: Check Device Manager> Serial Port (Windows) and make sure your Phones COM is set to 41, if not then change it. After changing it you may have to unplug usb, pull battery and then reboot into download mode.
Step 7: Open a new Command prompt window just like before. in the folder you extracted.
Step 8: Run this Command
Send_Command.exe \\.\COM41
Click to expand...
Click to collapse
.
Step 9: Run this to Backup your current recovery
dd if=/dev/block/platform/f9824900.sdhci/by-name/recovery of=/data/local/tmp/recoverybak.img
Click to expand...
Click to collapse
Step 10: It will now show a # then run this
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/recovery
Click to expand...
Click to collapse
Step 11: Then run this
dd if=/data/local/tmp/recovery.img of=/dev/block/platform/f9824900.sdhci/by-name/recovery
Click to expand...
Click to collapse
Step 12: Pull battery and try to boot into recovery
Step 13: Flash Supersu.zip
Note:: to restore original Recovery all you have to do is pull it
adb pull /data/local/tmp/recoverybak.img \
Rename it recovery.img (you might have to delete or rename the one that was extracted from the zip earlier because the can only be one recovery.img in a folder )
then rinse and repeat all the steps

I've got a Verizon version coming tomorrow. Can't wait to give this a try. Thanks.
Edit - Just tried to download the root zip, and I got a message that it's infected with a virus.

cant download G4_Rootbeta1.zip
her it is

hytin said:
cant download G4_Rootbeta1.zip
Click to expand...
Click to collapse
This is the error we get when attempting to download it:
Code:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
EDIT: See my post below for a copy of the ZIP

i think i found a way will upload it later

Does anyone tried this method on the T-Mobile G4 H811?

I was able to use a web-based ZIP extractor to extract then compress it. I have done no scanning for viruses, I simply extracted and repackaged the files.
G4_Rootbeta1
ZIP - https://www.dropbox.com/s/wmbz005aqs52r9j/G4_Rootbeta1.zip?dl=0
7z - https://www.dropbox.com/s/tnmnbak62zdrgu6/G4_Rootbeta1.7z?dl=0

hytin said:
cant download G4_Rootbeta1.zip
Click to expand...
Click to collapse
New link... I uploaded to drop box. Google drive acts funny when it come to certain files.

geoff5093 said:
This is the error we get when attempting to download it:
Code:
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
EDIT: See my post below for a copy of the ZIP
Click to expand...
Click to collapse
New link available

do we still need to enable oem unlock?
Sent from my LG-H815 using Tapatalk 2

deejay6901 said:
do we still need to enable oem unlock?
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I think I am unlock is only for unlocking the boot loader not rooting

So I tried this on the H811 (T-Mobile) version.
Everything worked just as described UNTIL the part where I needed to run the root script.
After I paste the SH command, it thinks for a moment, and returns me to the # line...
Not sure how to continue from here, but will be happy to be a guinea pig if someone can tell me what to try.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

madhouze said:
So I tried this on the H811 (T-Mobile) version.
Everything worked just as described UNTIL the part where I needed to run the root script.
After I paste the SH command, it thinks for a moment, and returns me to the # line...
Not sure how to continue from here, but will be happy to be a guinea pig if someone can tell me what to try.
Click to expand...
Click to collapse
Same here on H815 ?!
My Bootloader ist Locked. Is that the reason ??? Do i have to unlock it ?

it´s for the G3 on 5.02 not lollipop 5.1

hytin said:
it´s for the G3 on 5.02 not lollipop 5.1
Click to expand...
Click to collapse
This is modified for g4

Masta_Gee81 said:
Same here on H815 ?!
My Bootloader ist Locked. Is that the reason ??? Do i have to unlock it ?
Click to expand...
Click to collapse
Try doing the command without dummy1

Hi macdaddie87
Thanks for your job! :good:

Looking forward to people with Verizon giving this a shot first!

macdaddie87 said:
Try doing the command without dummy1
Click to expand...
Click to collapse
Same result . Nothing happens ?
this is my input : sh /data/local/tmp/root_g4.sh/data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
it stays on # nothing more?!

looks like device is not attaching when connected to download mode even if adb.exe devices is executed

Lost ~180mb of RAM after flashing custom rom? Solution here.

This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!

Here is a file in an archive. Extract it to ADB folder.

correction
Star_king12 said:
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvboot+nvboot1 nvboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!
Click to expand...
Click to collapse
Please, may be do you have a little error in last command line?.
where you put: fastboot flash nvboot+nvboot1 nvboot.bin
I must use: nvtboot in all words

JAMELGO said:
nvtboot in all words
Click to expand...
Click to collapse
Fixed.

Star_king12 said:
Fixed.
Click to expand...
Click to collapse
Ok!

Thanks for the guide

is this for mi pad 1 ????

ayushagarwal9753 said:
is this for mi pad 1 ????
Click to expand...
Click to collapse
Yup ;-;

Works! RAM went from 1.7 to 1.9Gigs.
Remember to unzip the file to get the .bin version.

not able
my device is not found in adb devices..kindly upload the required drivers for mi pad and clearly explain the procedure..whether the mi pad is to be put in fastboot or not..

rj4jhtconev said:
my device is not found in adb devices..kindly upload the required drivers for mi pad and clearly explain the procedure..whether the mi pad is to be put in fastboot or not..
Click to expand...
Click to collapse
I will not upload drivers here. The procedure is explained as clearly as possible.

Great!
Star_king12 said:
This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
Code:
adb devices
If it shows device status as 'device' everything is OK.
B)
Code:
adb reboot bootloader
If you see a rabbit on the screen, than everything is OK.
C) Write
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
C) Check the cmd's output, if you see OKAY there two times, than everything is OK.
D) Reboot.
E) ...
F) Profit!
Click to expand...
Click to collapse
It worked! :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

edconocerte said:
This guide is for Mipad 1(mocha)
Download DiskInfo, if it says that you have only 1.8 GB of RAM, than this guide is for you.
1. You need to have ADB and fastboot drivers installed.
2. Download the nvboot.bin file, that is attached.
3. Put it into your ADB folder.
4. Enable USB debug on your device.
5. Open cmd in ADB folder and
A) Check if your device is attached properly.
If it shows device status as 'device' everything is OK.
B)
If you see a rabbit on the screen, than everything is OK.
C) Write
It worked! :fingers-crossed:
Click to expand...
Click to collapse
Having 1.9GB and not 2GB is normal in custom ROM?

Jankev said:
Having 1.9GB and not 2GB is normal in custom ROM?
Click to expand...
Click to collapse
Yep. Stock and custom ROM show 1.9GB.

Star_king12 said:
Fixed.
Click to expand...
Click to collapse
If the system1 and 2 are merged what should I use of below?
Code:
fastboot flash nvtboot+nvtboot1 nvtboot.bin
Code:
fastboot flash nvtboot nvtboot.bin