Database Users

[A70B/IT2 HC][3.2.81 update] Enabling SDE and rooted firmware package

First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.

*reserved*

Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!

Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again

LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.

Hi mrew42,
Thanks a lot! Much appreciated!

Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81

Letama, can you may be make the same for 3.2.81?

Yes, it will come soon...

3.2.81 is up and instructions on first post updated if you upgrade.

Great
http://www.jbmm.fr/?p=27601
{
"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"
}

cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!

Thanks, will try it out soon.

Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.

ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.

I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?

No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.

Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!

hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!

lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.

[UTILITY][RUU IMITATE]Easy Installer - Install your rom's like an RUU[HTC only]

Easy Installer​
{
"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"
}
What is Easy Installer?
Easy installer is a windows RUU imitate that helps you as user to install your Rom's with only 2 clicks. Fully automated!
For devs Easy installer helps to provide Rom's alternate to the recovery zip archive.
Click to expand...
Click to collapse
How does Easy installer work?
Thats easy. The developer create a system img file of his rom and configure Easy installer easily with one config file. The package can provide like a normal rom.
The user run a little exe-file and the RUU installs the rom fully automated! If something runs false, the RUU gives the user an error and a explanation what he can to do now.
Click to expand...
Click to collapse
What i need for Easy installer
For now, Easy Installer works only with image files, so you need your Rom as a image file. You can create a image file of your rom easily with mkyaffs.arm (find in attachements).
The config file is easy to understand. An example here (found in package too):
Code:
;The config file is neccessary for the RUU. Here you define all file namens.
[functions]
;imgfile specify, if you want to flash a image or a zip file (0=zip-file, 1=img-file). For now, only img files working, sry :(
imgfile=1
;waitbl set the time the RUU wait for the bootloader (fastboot). Some devices take a while to reboot to bootloader. Set the time here, in generally the time 10 is enough
waitbl=10
;the img-name specify the name of the image file without the file extension!
img-name=system
;zip-name is for one of the next versions, when it is possible to flash zip files. If you want, you can delete this
zip-name=HC_MIUI3.2
;boot-name specify the name of the boot.img without extension.
boot-name=boot
;set the name of the clockworkmod recovery file for your device here.
cwm-name=cwm
;rec-name is the original recovery of HTC that must be inserted for img-files. Put the name here without extension
rec-name=recovery
[labels]
;specify the shown rom-name in the RUU
rom-name=.sense
;the device name is the full name of the device the rom is for
device-name=Wildfire S
;some devices has more versions (marvel, marvelc, marvelct e.g.). Specify for what device your rom is.
device-code=marvel
The picture in the RUU is namend "PHONE.bmp" in package, you can replace with your own.
Click to expand...
Click to collapse
How to create the system.img?
Well, thats is easy
1. Install your Rom you want to use in Easy Installer at your phone via the Recovery (don't start the Rom!!!)
2. Go to recovery, connect your phone via USB-Cable to computer
3. Download the mkfs.arm.zip (see attachements)
4. Create a new directory in your SD-Card (example: "build")
5. Copy the extracted file "mkfs" of the downloaded archive into the folder "build"
6. Insert the SD-Card into the phone
7. In recovery go to: "mounts&storage->mound /sdcard" or run following adb-command: adb mound /sdcard
8. run the following commands in adb one after one:
adb shell
cd /sdcard/build
./mkfs /system /sdcard/build/system.img
9. Wait for the "Build OK."-message
10. Exit the adb shell via exit command and turn off the phone
11. Take the SD-Card of the phone and insert it into your PC
12. in the SD-Card's folder /build you will find a "system.img". Use this file for the easy installer
Click to expand...
Click to collapse
Changelog
v0.0.1
- first version, basic install function
Click to expand...
Click to collapse
Download
See the attachements (WSWizard.zip)
Click to expand...
Click to collapse

Will this work for all devices?
Any chances of bricking? Because many of users of Micromax A70 bricked their phone by a chinese flashing tool.
Burned from my laser torch using pencil cells

Sorry, i see now, that i posted this in false section. In genarally it works only for HTC devices which are unlocked or S-OFF, not for others!

How can I use the mkfs.arm?

it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use

Would like to know if this would work to ONelll123
Wipe everything
Flash Rom
Make Nandroid
Use Nandroid as ROM's Images
It seems much easier to me than having to go to shell and all Not meant to be an insult, just a recommendation/question

Hmm, it ia qn idea, but idk in what filesystem the backups are saved. If it is yaffs2 it can be that this works.
But you must do shell commands too. Its for secruity reasons and that this method used works.
Sent from my HTC Wildfire S A510e using XDA

ONeill123 said:
it works only on ARM-based devices, like the HTC phones.
You must copy the file onto your sd-card e.g.:
adb push mkfs.arm /sdcard/build
After this you install your Rom on the device or copy the /system-files to the sd-card. Now you run following command:
adb shell
cd /sdcard/build
./mkfs.arm /system /sdcard/system.img
ODER
./mkfs.arm /sdcard/build/system /sdcard/system.img
Then the file will build a system.img and copy it onto the sdcard for next use
Click to expand...
Click to collapse
Thanks I will be try this when htc one x gets adb working recovery

[How To] Root [I9100][ROM 4.1.2] With Stock Recovery

Root FJ10 Without Custom Kernel​
As we all know FJ10 has been released and is floating around the internet, and iv'e decided to share the way i rooted the leak (International SGS II) using stock samsung recovery
Credits
Chainfire CWM-Supersu
Sextape Leak​rwilco12 Continue to hosting leak
What you need
PC/MAC/Linux
ADB
USB Cable
Phone
CWM-SuperSU-v0.97.zip
There is two ways to flash the root package in custom recovery (sorry i keep forgetting the other way)
Thank You Sh4Dy for reminding me
Flash Trough Update
1) Download CWM-SuperSU-v0.97.zip
2) Rename CWM-SuperSU-v0.97.zip > update.zip
3) flash as an update
Instructions
1) Enter Recovery mode by holding power+volume up.
2) Connect USB Cable to the phone and PC
3) Choose Install Update with adb
now
4) Now in your terminal/CMD write adb sideload CWM-SuperSU-v0.97.zip
5) Look at the screen and you will see the update package being installed
Congratulations you got now a rooted FJ10 leak without flashing a custom kernel
Proof
{
"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"
}

Thanks, but I get stuck at 3.
I go to search -> cmd and then I type adb sideload CWM-SuperSU-v0.97.zip in it. I think this is wrong but I never worked with ADB.

how it works now? i don't get it also

dajumper said:
how it works now? i don't get it also
Click to expand...
Click to collapse
Works fine here
You need to install adb then cd to the adb directory, then type the command.

Why is it even in dev section?

Spyr0s said:
Works fine here
You need to install adb then cd to the adb directory, then type the command.
Click to expand...
Click to collapse
Will try that tomorrow!
Verstuurd van mijn GT-I9100 met Tapatalk

dajumper said:
how it works now? i don't get it also
Click to expand...
Click to collapse
Make sure you have adb installed on your pc
after that begin with step 1

Doesn't work at 4th step for me, I check devices in adb devices and it shows my device but some large-ass thing comes n it doesn't install the SuperSU zip for some reason

Same thing here

wrong thread. plz delete

ssilviu said:
Same thing here
Click to expand...
Click to collapse
did you also use the supersu provided in op?
Sh4Dy said:
Doesn't work at 4th step for me, I check devices in adb devices and it shows my device but some large-ass thing comes n it doesn't install the SuperSU zip for some reason
Click to expand...
Click to collapse
did you use: http://download.chainfire.eu/267/SuperSU/CWM-SuperSU-v0.97.zip

Hey guys, Just apply the .zip from external card via recovery, the .zip in OP, worked for me
Edit: Yes mate, I used that file only, you copied it from Sprint S2's JB thread? Coz I can see the screenshot is of Oct 11 firmware.

Sh4Dy said:
Hey guys, Just apply the .zip from external card via recovery, the .zip in OP, worked for me
Edit: Yes mate, I used that file only, you copied it from Sprint S2's JB thread? Coz I can see the screenshot is of Oct 11 firmware.
Click to expand...
Click to collapse
yes i did, as i know this will work with it too

Buy mobile odin, flash the rom, then you will get root. Quite simple.
I love new rom.
But it wipe all my data system apps...

bogdan1980 said:
Buy mobile odin, flash the rom, then you will get root. Quite simple.
I love new rom.
But it wipe all my data system apps...
Click to expand...
Click to collapse
that isn't mobile odin problem, its wiped automatically

Yeh man, it should work with this too, but idk, flashing zip did the job for me. Try it yourself

Sh4Dy said:
Hey guys, Just apply the .zip from external card via recovery, the .zip in OP, worked for me
.
Click to expand...
Click to collapse
failed to mount sdcard

Sh4Dy said:
Yeh man, it should work with this too, but idk, flashing zip did the job for me. Try it yourself
Click to expand...
Click to collapse
i added your instructions to OP and added you as credit for reminding me :highfive:

ssilviu said:
failed to mount sdcard
Click to expand...
Click to collapse
This is why adb sideload is powerful (as on sprint we were never able to access sdcard)

If you want, I can give proof, I'm currently restoring apps from Ti Backup Pro

[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

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